this post was submitted on 09 Nov 2023
36 points (100.0% liked)

homeassistant

12084 readers
4 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago
MODERATORS
[email protected]
36
What's your experience with the new openwakeword? (lemmy.d.thewooskeys.com)
submitted 1 year ago by [email protected] to c/homeassistant
17 comments fedilink hide all child comments
 

I got some Atom Echos, configured them, and they work! I even customized my own wakeword and it worked on the first try. Thanks, Home Assistant team, for such an awesome product as Home Assistant and for fantastic documentation.

Though the Echos and voice recognition works, I'm waiting about 28 seconds between speaking and having Home Assistant respond. "OK Nabu, do the thing"...then I wait ~28 seconds and then at the same time I hear the Echo say "Done" and Home Assistant responds.

Is the delay due to the Echos being small/cheap/slow processors? They react instantly to the wakeword, but perhaps that requires less processing power because it's trained. Is the delay due to forwarding the audio content of my spoken word over the network to Home Assistant so Whisper can process it? I'm able to transfer other content over my network very quickly, and I doubt the data size of a few spoken words is very large. Is the delay in Whisper processing my spoken command?

What has your experience been with the Echos and openwakeword?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago

I changed the VM's CPU type in Proxmox and gave the VM more resources (most of the hosts's RAM and CPU cores) and the delays cut in half to around 16 seconds. So I know what's causing my delay (or probably most of it). I guess I need a beefier box.