My #AtomEcho arrived... Tried the "$13 voice assistant for #HomeAssistant " instructions, but #esphome just installed a do-nothing firmware that did nothing. So I tried a yaml from the "esphome/firmware" repo, which made the device uncontactable.

Turns out, ever since a commit a few days ago, the Atom Echo doesn't work because the firmware's too big: https://github.com/esphome/firmware/issues/227

๐Ÿ˜Œ

So much for all the pushing for a voice assistant in the blogs and updates. Knocked it outta the park again! ๐Ÿ˜Œ

M5 Stack Atom Echo VA firmware does not install locally since a79c9fa - image too big. ยท Issue #227 ยท esphome/firmware

Environment: ESPHome 2024.6.6 on HA OS. Raspberry Pi 4 - I can also re-create the issue in docker 2024.6 on windows. M5 Stack Atom Echo. Related: esphome/issues#5714 (comment) Another user with the...

GitHub

@indigoparadox i just removed the timer functionality and added my own function that routes the response to a google in the same room without hardcoding the media player.

I haven't had a chance to work on the video. But if you need a firmware config that works I can send you one.

@slackerlabs I *thiiink* I'm most of the way there by reverting to the commit in the bug I linked... Just a little more shuffling things around to find out. ๐Ÿ˜Œ

EDIT: Yay! It works! How exciting.

@indigoparadox nice. Yea. I got bit by that one this week too.

And I think it was really unnecessary. The big change was including the timer functionality from what I can see. And I don't understand why that's hardcoded in the firmware.

Like you can't event change the timer chime without updating the firmware. That seems like a bad pattern to me

@slackerlabs I guess I spoke too soon... it works for a while and then... stops working... I see a "Packet write failed OUT_OF_MEMORY errno=11" on one attempt, but another reboot gave a "Component i2s_audio.microphone set Error flag: unspecified" before not working and... it's difficult to say if either error is truly related...

Oh well!