After a recent update to ESPHome, my ATOM Echos no longer show a wake word in Home Assistant and the wake word field isn’t even editable:

And indeed they aren’t responding to me speaking the wake word.

Has anyone encountered this? Does anyone know of a fix or has a suggestion?

  • @[email protected]English
    7•3 days ago

    I know almost nothing about this, I’ve only done a few hours of testing with HA and nothing with ESPHome, but a quick search of “esphome wake word disabled” shows a lot of forum chatter since early December. So, you aren’t alone, and I can’t help you, but there are a lot of resources out there that might.

    • Mike WooskeyOPEnglish
      2•3 days ago

      Thanks for the suggestion, https://lemmy-tesseract.thewooskeys.com/u/[email protected], but I’m not able to find anything recent about this issue. I found a couple mentioned of this issue and of similar-ish issue from 6 months and a year ago but they’re using way older versions of ESPHome and so their solutions don’t work for me.

      If you can share any of the links you found, I’d appreciate it.

      • @[email protected]English
        2•3 days ago

        Here’s the search I used, with a six month range on it. There are a variety of issues shown with the wake word with different versions, etc., but I don’t know your exact specs. There are also some for mini wake word, which may or may not be relevant to you. That’s about all the help I can give, unfortunately.

  • @ikiddEnglish
    1•3 days ago

    Flash again and leave the log running. I had this going on, took a few reboots to get it to not display some error it was throwing in the log. It seems like it’ll work for a while and start again requiring another power cycle or three.

    I went back on old version of ESPHome and that didn’t help. IDK if these Atoms just mile out after a while or what.

    • @spitfireEnglish
      1•2 days ago

      It’s a matter of config, not hardware. I was putting my own together (based on the „official” one) and it is working. Maybe they’ve changed something there

      • @ikiddEnglish
        1•2 days ago

        Mine worked fine for months, then suddenly started doing this. It was shortly after an update so I thought I’d go back to a previous firmware but no luck. It’s been working for a couple weeks now but it took a few reboots before it “caught”.