Hit Connect, selected proper COM port, & hit Install.
A couple minutes later, I had a working voice assist satellite device, with working mic, speaker, and cutesy display.
I immediately asked it “Hey Nabu, turn off XX lights”
And much to my surprise, without doing any other config, IT DID IT!
(+ other voice requests)
I haven’t really played with it much since, & don’t know if it’ll have any issues with newest ESPHome code.
But I was absolutely flabbergasted that it came up so easily.
I’m still doing HA voice control here with Alexa and/or Siri. But I’m now convinced that HA Voice Assist is much farther along than I had thought, & I can seriously think about starting to move to it anytime.
Follow-up: If anyone uses the Ready Made Projects to build a voice satellite with M5Stack Atom Echo device, I’d have to agree that unit is more toy like. Almost un-hearable speaker volume. And no wake word – you have to push its button for Push-to-Talk functionality (apparently not enough horsepower to process wake word on device). And mic didn’t always seem to pick up voices clearly.
But even so, it IS a functional voice assist satellite, which worked immediately after loading firmware. (And is cheap way to experiment)
I had a similar issue on Arch Linux. So this may not be relevant to you. I found that after the device got flashed the permissions on the USB reverted back and I didn’t have access anymore. As a hack I opened a background terminal and did:
while :; do chmod 666 /dev/ttyACM0; sleep 2;done
Replace ACM0 with your device name. Keep it running until you’re all done then ctrl+c
This is really disappointing, there is a lot of blabla going on about voice assist, so I bought this very nice exp32 S3 box 3(the m5stack echo was a rather disappointing experience), got the yaml code into esphome in HA, and I end up with a non-working speaker. It does process voice commands, not as good as Google, but that’s oke for now.
While compiling the code, the log screen is flooded with messages / warnings / errors. How can this be unnoticed by the creators ?
I followed the advice from @smcnaught to switch back to the esp framework version: 4.4.6, that works for me, for now
Hello, where exactly should I write these few lines that restore ESPHOME to the previous version?
Does /homeassistant/esphome/esp32-s3-box-3-5a93fc.yaml match the beginning or the end?
Speaker doesn’t work. Known issue and I’ll try downgrading firmware to 4.4.6 as recommended above.
Microphone is pretty bad. I tried talking to it from 2m away in a quiet room and it didn’t hear me. I had to be 0.5m away and even then it didn’t hear me sometimes. Is this also a bug in recent firmware?
It takes aaaaaaaaaaages to acknowledge my command. I know my back-end (whisper & piper) is fine because if I trigger Assist on my phone and say “turn on lights”, it takes 3-4s at most. When I do it via my ESP32-S3-BOX-3, it takes around 20s! Could this be a configuration issue or just the way it is?
Appreciate any guidance with this!
EDIT: Setting ESP32 framework version to 4.4.6 broke my microphone too, until I downgraded my ESPHome docker container to version 2024.4.2. Now both mic and speaker work, and it takes 4-5s to complete a simple command, which is comparable to using my phone.
So the primary issue I’m left with is the wake word. It just doesn’t seem responsive at all, I always have to say it about 5-6 times even when only 20cm away. Any tips for this?
Late June and I’m stuck in exactly the same frustrating position. Bought an S3-Box-3 because HA were effectively pushing it on the site. Voice Assistant initially worked, then after an hour or so the microphone stopped responding. I managed to get the temperature, humidity and (terrible) presence sensors working, but nothing I do seems to bring back a functional microphone. So frustrating.
Much better, now there is a touchscreen with controls.
Thank you, will play with it and configure buttons.
Voice however is not working still, I’m beginning to think the HASS / Openwakeword or something there is bugged at the moment on my side.
Either way, I always wanted it to be a control screen primarily. Was disappointed to see that the HASS Voice firmware was a pure screen only with no templates like this firmware has.
Appreciated.
I’ve been having the same issues. On their demos it seems to work flawlessly, I wonder if there are other things that are running that are taking up memory.
Additionally for me, when I changed the wake word model it did this weird thing where it wouldn’t respond to ‘hey Jarvis’, but I had to say ‘ok Nabu’ right after saying hey Jarvis to get it to start listening, if I kept repeating either of those commands or wouldn’t work.
