somber marlin
I am running openwakeword in docker for local wake word detection on my mac mini, I tested using postman that I can connect uising 127.0.0.1:10400 and the terminal in the docker container shows connected/disconected.
when I run 'script/run' for the sattelite it doesnt seem to connect to the local wake word service, and none of the queue wav files play.
any ideas?
lyric flume
you would connect that service to your assist pipeline
in HA it has to be added via the Wyoming integration
somber marlin
for local wake detection? satellite docks say you run an instance of a wake word detection service
cd wyoming-openwakeword/
script/run \
--uri 'tcp://0.0.0.0:10400' \
--preload-model 'ok_nabu'
then include the flag for when you run the satellite
cd wyoming-satellite/
script/run \
--name 'my satellite' \
--uri 'tcp://0.0.0.0:10700' \
...
--wake-uri 'tcp://127.0.0.1:10400' \
--wake-word-name 'ok_nabu'
--awake-wav awake.wav
but it doesnt seem to connect to the openwakeword service and the wav never plays
they are likely unrelated issues though since the wav should play whether its connected to remote or local wake word detection as I understand it
lyric flume
hm, maybe something special with wyoming satellite specifically, I know for the HA inbuilt satellites they get that info from the pipeline through the wyoming protocol. Not familiar with the wyoming satellites, hopefully someone else can chime in 😅
Oooh wait
127.0.0.1 is loopback IP, nothing external will ever be able to talk to that
it has to be the network address of the server running the service
or are you running these all on the same physical machine?
somber marlin
Yes
lyric flume
Then you are probably being bit by the docker networking
I;ve seen some users in the past running docker on something like docker desktop run into issues where the docker network isn't externally exposed
something to do with the network bridging
somber marlin
And 10040 is mapped to 10040 in docker. If I use postman to 127.0.0.1:10040 docker acknowledges the connection, but the satellite service doesn't even seem to attempt a connection
lyric flume
though if you are using postman externally to hit it then I don't see why that issue would be happening..
Yeah, guess someone familiar with these will need to chime in here 😄
Maybe silly question, but the service itself for openwakeword isn't showing any errors I assume?
somber marlin
Thanks for trying 😅 running it from osx already seems to be pretty uncommon, I had to use Sox and ffmpeg instead.
And no, No errors, it connects to home assistant fine and I can send voice commands but it's a bit flaky and no acknowledgement that I spoke to it until after it runs the command
lyric flume
openwakeword connects to home assistant? Or you mean the satellite?
somber marlin
the satellite does.
I was trying to run it all from the same machine but thats not working seemingly. Gonna try on my rasp pi see if it works there.
lyric flume
Yeah was curious if the openwakeword service had anything weird in its logs that might indicate that it is running but in an errant state
gaunt wraith
Wyoming Satellite is intended to use OWW installed on satellite itself. You just install OWW to the Pi. Then you will be able to use 127.0.0.1 in Wyoming Satellite Service command.
somber marlin
Wyoming Satellite is intended to use OWW installed on satellite itself. You just...
I am trying to use my mac mini as the satellite, since its already set up with home assistant and its always on anyway i just hooked up a mic to it.
I have the satellite service running on the mac mini, and on the same mac mini the oww is running in docker forwarding port 10040 to 10040 in docker. so 127.0.0.1:10040 is accessible from the mac mini to docker confirmed with postman. it seems like the sattelite is just not attempting the connection at all
somber marlin
Couldn't get it to work properly using MacOS, downloaded linux on a zotac nano ive got and installed it there and now it is working.