Open tomchapin opened 8 years ago
I did a bit more experimenting, and it looks like the amazon echo will still let me control a number of my virtual hue devices via the intensity commands.
For example, I can say, "Alexa, turn on netflix", and it complains, but when I say, "Alexa, set netflix to 100%", it triggers the netflix activity, passing it an intensity of 100.
Weird. I wonder if Amazon is blocking certain words or something?
It seems to be doing it for other random, generic words, too, though?
Having the same issue. All commands affected: Turn on HBO Turn on Showtime Turn on Details Turn on CNN - This command now sets off the news briefing.
Is there a fix?
Pretty sure Amazon is blocking it. Running regular commands and the emulator is picking it up. Run some of the commands listed in previous comment and I get a double beep. Run made up commands (Turn on banana) and it tells me does not see that device listed.
I've been meaning to thank Arm Suwarnaratana for his excellent job but appears he hasn't been active in the project for weeks. I found this "follow up/alternative" that I've been using ever since: https://github.com/bwssytems/ha-bridge The code has been kept updated and is working fine as today (Apr 11,2016). Hope this helps you solve the problem!
I'm having the same issue with "turn on netflix", but "turn on netflix lights" works just fine. I wonder if amazon is about to release some additional control features (e.g., integration with fire TV?) and that is why they are blocking certain words? It would be nice if amazon was a bit more transparent about keywords that are blocked.
I noticed that "Tivo" doesn't work ether, gives me hope they are planning to integrate there too. I have about 25 things setup on the bridge, many words are slightly changed to get around the blocked words.
Strange--"tivo", "CNN", and "HBO" all work for me when I create them as a group and point them to the virtual hue devices. "Netflix" still doesn't work though. Anyone know how we can get a list of words that are "reserved"? It is a pain to debug and usually I end up with some command that is not very natural.
Kodi
not working for me
My echo just updated.....all commands working now.
I've been running echo-bridge for about a year now and it has been rock solid; Alexa on the other hand does update itself some times and then it "forgets" the echo-bridge devices but it fixes itself automatically after some time. So in summary I believe the temporary forgetfulness is a byproduct of firmware update from Amazon, I just let it re-learn without intervention and it eventually does.
Amazon just recently rolled out a new update for the Amazon Echo and now any time I attempt to control my virtual hue devices, the Echo just gives me a two-tone failure chime (even though it sees the devices in the "Smart Home" section).
Anyone have any ideas on how to fix it? Is anyone else having the same issue?