Hi, everyone! I realize a lot of users are patiently waiting for 2.5, but I still want to keep 2.4 fed and watered
The two changes people will probably notice the most in 2.4.18 are (1) the addition of a new /api/events/wake websocket endpoint for reacting to a wake word detection, and (2) speaking a voice command will cause the intent to show up in the web UI (no need to use the buttons). Enjoy!
Added
/api/listen-for-wake accepts โonโ and โoffโ as POST data to enable/disable wake word
/api/events/wake websocket endpoint reports wake up events
Now the backlight of my TV turns blue when i wake rhasspy - when it recognizes an intend it flashes green and when not red
/api/events/text socket was not working in my case - maybe i did something wrong.
i also noticed in /api/events/wake siteId gets reported as "siteId": null - does it need to be set as something different than default for it to be recognized ?
since iโm only using one device with no satellites, it doesnt matter anyways
@Sikk, that is an awesome idea, I would never have thought of something like that. iโm wondering what your setup is like and how did you perform this?
hey @TinyDoT
the backlight is just an old IR led strip iโm controlling through a broadlink rm3 IR-blaster.
The logic is done through Node-red
Basically just one websocket for /api/events/text and two mqtt in nodes for hermes/nlu/intentNotRecognized and hermes/intent/#
and then lots of clutter for different cases, like backlight already on, tv off but backlight is synced setting is on, what was the previous color and so on