[Talking to a Google Display:] "Hey Google, lights!"
"Playing lights on YouTube."
[Fuck! That's not what I wanted. I wanted it to turn on the lights. The display starts playing music.]
[Still talking to the same display:] "Hey Google, stop!"
"Okay, stopping the Chromecast."
:headache:
Now, for the love of everything sacred, please explain to me why when I ask the display to "stop," it decides that I don't want it to stop playing the bloody music it just started playing and instead thinks that I want to stop what's playing on my Chromecast?
:why:
This is not the first time the scenario above happens.
I used to say "turn on the lights" but then I was playing roulette, because once in a while the device would hear an "all" in there and would turn on all the lights in the house. When I still lived with my ex-wife, it was super fun to ask the device to turn off all the lights I did not want on.
So I switched to just "lights", which eliminates the problem I just mentioned, but sometimes the display thinks I want to play some stupid song.
:catangry:
I'm just waiting for the M5Stack ATOM Echo Smart Speaker to be available again (link below), and I'm going to start experimenting with voice recognition in Home Assistant. I expect it is going to be a bit rough going at first, but meh... I cannot be worse than the shit that Google peddles.
https://shop.m5stack.com/products/atom-echo-smart-speaker-dev-kit?ref=NabuCasa
#Google #GoogleDevices #GoogleIsShit #Chromecast #HomeAutomation #HomeAssistant