any teasers is it all wake word | Home Assistant | Page 1

rocky inlet Sep 27, 2023, 12:42 AM

#

yep 🙂

#

it's not running inside ESPHome

#

via Wyoming we run the wake word either as an add-on or as a container

#

We are launching with OpenWakeWord but other wake word engines can be used too

worthy marsh Sep 27, 2023, 11:23 AM

#

Can't wait 🤩

#

Btw have you considered bluetooth (not smart) speakers?

fluid jackal Sep 28, 2023, 4:02 AM

#

rocky inlet via Wyoming we run the wake word either as an add-on or as a container

Does this mean this is going to be functioning on Oct 12 or just talking about it?

#

~~Currently Wyoming Protocol doesn't seem to connect to the Wyoming-OpenWakeWord docker container.~~

rocky inlet Sep 28, 2023, 4:06 AM

#

Try the beta

fluid jackal Sep 28, 2023, 4:06 AM

#

I see the container was updated 11 hours ago will do!

#

Also your last coverage of voice was super short (I maybe missed reasoning) I kind of felt disappointed how rushed it was. I love when you guys do longer live videos just talking about all the random things people are working on or working with or highlighting creative things people made. I really look forward to these videos. Thank you for doing them.

#

Success!
Created configuration for openwakeword.

❤️

#

Note not sure if this only affected me with portainer but run.sh has --uri 'tcp://0.0.0.0:10400' pre defined

cat run.sh
#!/usr/bin/env bash
python3 -m wyoming_openwakeword \
    --uri 'tcp://0.0.0.0:10400' "$@"

which prevents the docker from running when you try to define it again in the example shown:

docker run -it -p 10400:10400 rhasspy/wyoming-openwakeword \
    --model 'ok_nabu' \
    --model 'hey_jarvis' \
    --model 'hey_rhasspy' \
    --model 'hey_mycroft' \
    --model 'alexa' \
    --preload-model 'ok_nabu' \
    --uri 'tcp://0.0.0.0:10400' <====

#any teasers is it all wake word