Can't install voice assistant into ATOM Echo

[jlatvala]

I had a voice assistant working in ATOM Echo but then its entities greyed out in the HA UI.
Didn't have time or will to start investigating so I decided to install it again from the scratch using the installation procedure in https://www.home-assistant.io/voice_control/thirteen-usd-voice-remote/
(note: this same procedure worked fine in the first run few months ago)

This time the installation goes through fine but it never ever asks to type in the wifi SSID and password. The next button in the installation UI just doesn't open the SSID/password dialog.
If I try again, it again just re-flashes the SW, but again doesn't ask SSID/password.

Then I tried through this page:
https://esphome.io/projects/
Same problem, no luck.

Windows & Chrome.

USB drivers etc. are totally fine, because I can install "dummy" (but working) configuration into ATOM Echo using HA's ESPHome Device Builder add-on and web.esphome.io. This "dummy" configuration can be connected into wifi and it becomes visible into HA. I can also reflash it again using wifi, so the wifi component in ATOM Echo works.

I also tried to install this yaml
https://github.com/esphome/wake-word-voice-assistants/blob/main/m5stack-atom-echo/m5stack-atom-echo.yaml
manually using HA's ESPHome Device Builder add-on and web.esphome.io.
It installs fine, but I never ever get it to work or connected to wifi.
Tried to modify the yaml also a little, for example removing name_add_mac_suffix: true, using on_connect - delay 5s in wifi-configuration, with and without ap, ...

Sometimes the ATOM Echo makes some kind of continous ticking noise after plugging it into powers (maybe "trying to connect and failing" sound?)

When trying to use this github's m5stack-atom-echo.yaml, I tried to use the very same !secret wifi_ssid & password, which works in the above-mentioned "dummy" configuration, so the problem should not be the invalid SSID/password.

Tried about 20 times and the gave up and ended up writing this ticket.

[Mariusthvdb]

yes, I went through all of that the last 2 days....

I finally managed to refresh it via readymade projects attached to the computer, and after that, with some manual editing in the config flow, adopted the device into the Esphome dashboard.

Mind you, an edit and install now takes 30 minutes or so.... it's way beyond ridiculous.

imho, the firmware has one way and beyond the devices reliable possibilities, and should be made smaller, not including all new developments.

It worked ok-ish before, but ever since the move to voice assistants, has been nothing but trouble.

like you, it updates allright, but seems to nt connect to wifi, or complain about encryption modes, all of which just worked before.
it a horrific experience...

======================== [SUCCESS] Took 1878.19 seconds ========================
INFO Successfully compiled program.
INFO Resolving IP address of m5stack-atom-echo.local in mDNS
INFO Resolving IP address of m5stack-atom-echo.local
ERROR Error resolving IP address of m5stack-atom-echo.local. Is it connected to WiFi?
ERROR (If this error persists, please set a static IP address: https://esphome.io/components/wifi.html#manual-ips)
ERROR Error resolving IP address: Error resolving address with mDNS: Did not respond. Maybe the device is offline., [Errno -5] No address associated with hostname

end rant

[Mariusthvdb]

@jlatvala did you check the name of the actual device, and the mentioned named in the log?
notice, like in my logging there is no extension after the m5stack-atom-echo part in the m5stack-atom-echo.local
while the device is called m5stack-atom-echo-a82d10 in my config... making the MDNS fluke on that.

If you reflash the device, at some point during the addition to Home Assistant, the flow will ask for the name of the device, make sure that is the full name.

It fixed the connection for me, with help from @BigBobbas on Discord, much appreciated.

[jlatvala]

I spent some time playing with ESPHome Devide Builder and from a quick look it looks like that the media_player section in
https://github.com/esphome/wake-word-voice-assistants/blob/main/m5stack-atom-echo/m5stack-atom-echo.yaml
breaks the config. Didn't spend too much on it, so the root cause might be somewhere else.
Atom Echo can connect to my wifi and is thus visible in HA without media_player section
(of course I had to tweak the config in other areas as well to be able to remove media_player)

[github-actions]

As there has been no activity on this issue for 30 days, I am marking it as stale. If you think this is a mistake, please comment below and I will remove the stale label.

[jlatvala]

Tried again yesterday, still not working