Echo & Alexa Forums
General Category => Echo Technical Support => Topic started by: ahwman on January 05, 2016, 08:44:10 pm
-
I have 48 devices set up using a hue bridge. Intermittently when issuing an on/off command to any of my devices, I get back "That command doesn't work on that device". Issuing the exact same command again works as usual with "Ok" returned as a response. Has anyone else noticed this lately? I tried forgetting all of my devices and rediscovering them to see if that makes any difference. I'm wondering if this is a cloud issue or something local...
Chuck
-
Yes, occasionally I experience the same thing. Not so much with the Hue hub ad in general. I have no idea why.
Meantime, the last few days I've sensed some funny things going on with Alexa. Several times I've failed to get a response at all from her, even after trying half a dozen times. I'm assuming something going on at the cloud level, but that's just a guess.
-
Thanks for the confirmation. Hopefully it will be fixed soon...
-
Has anyone approached Amazon about this? I did via email and got a response suggesting that this wasn't a known issue and I needed to call in for advanced tech support. It happened MANY times this evening to the point where I gave up and started using the physical switches. It almost seems that it has to do with busy times of day..,
-
Whatever software update that Amazon pushed out today (or yesterday) broke my entire home automation setup. Whenever I ask Alexa to turn on/off a Wemo device, it says "That command doesn't work on that device."
-
Starting on or about Jan 7 or Jan 8 I'm having the same problem with my Philip Hue bulbs. Echo says it can't find my group names or that the "command doesn't work with that device". After several failures, things work about 10% of the time. If I reboot The Echo it works but then after 15 minutes the problem returns. I suggest everyone who has this issue call tech support like I did. They claim no one else reported this problem. They spent 45 min troubleshooting with me and then asked permission to pull data from my Echo. They supposed to get back to me on Tuesday.
-
Starting on or about Jan 7 or Jan 8 I'm having the same problem with my Philip Hue bulbs. Echo says it can't find my group names or that the "command doesn't work with that device".
Found this thread on a Google search and signed up to mention I have the same issue. Starting a couple days ago my Hue commands get the same "cannot find a group by that name" response you are seeing.
I have tried everything I can think of. I rebooted the Echo and Hue hub and also removed the Hue device from the Alexa iOS app and paired the Hue again and made new lighting groups... still the same thing.
I'll report this to Amazon today. Hopefully the more of us that report it, will get this issue some attention.
-
I have noticed this too. I'm curious if the problems are from the update Philips has pushed out that "fixed" the blocking of non Hue lights.
Sent from my SM-T807V using Tapatalk
-
It's really bad for me tonight, sometimes having to repeat commands anywhere from 5 to 10 times to get them to work properly. This seems to be related to load/high traffic times. I just wish we could get a confirmation from Amazon that they are aware of the issue and are working on resolving it.
-
I have noticed this too. I'm curious if the problems are from the update Philips has pushed out that "fixed" the blocking of non Hue lights.
Sent from my SM-T807V using Tapatalk
I don't think so, at least for me. I have the Hue 2.0 bridge and the last update firmware update was December 21, and my Hue lights worked fine with Echo after that. My trouble only started a couple days ago.
I emailed a trouble report for Amazon and they replied they have forwarded this to engineering and asked me to call to discuss further. I plan to do that today.
http://www2.meethue.com/en-us/release-notes/
-
Please let us know what they say. Thanks!
Sent from my SM-T807V using Tapatalk
-
Woot! I got mine sorted out thanks to a tip on Reddit.
My Hue group name setup on the Echo was "living room" and saying "Alexa turn on the living room lights" has always worked. I just tested with "Alexa turn on the living room" and it worked! So I renamed the group in the Alexa iOS app to "living room lights" and now I have my old behavior back and it works every time.
So it looks like Amazon changed something so that it looks strictly for the group name and saying "lights" after the group name breaks it, unless of course you change the group name to include lights at the end like I just did.
Edit: I just saw this blog post linked on Reddit that mentions the same thing I found.
http://betanews.com/2016/01/10/using-amazon-echo-to-control-your-home-theres-a-minor-change-you-need-to-know-about/
-
Woot! I got mine sorted out thanks to a tip on Reddit.
My Hue group name setup on the Echo was "living room" and saying "Alexa turn on the living room lights" has always worked. I just tested with "Alexa turn on the living room" and it worked! So I renamed the group in the Alexa iOS app to "living room lights" and now I have my old behavior back and it works every time.
So it looks like Amazon changed something so that it looks strictly for the group name and saying "lights" after the group name breaks it, unless of course you change the group name to include lights at the end like I just did.
Edit: I just saw this blog post linked on Reddit that mentions the same thing I found.
http://betanews.com/2016/01/10/using-amazon-echo-to-control-your-home-theres-a-minor-change-you-need-to-know-about/
I'm happy to hear your setup is now working correctly. That said however, it doesn't explain why many of us are still getting the "That command doesn't work with that device" response. I really hope Amazon gets to the bottom of this quickly as I don't feel like I can depend on it at this time...
Chuck
-
when you get "that command does not work" response, did you look in your logs to see what Alexa heard you say?
-
when you get "that command does not work" response, did you look in your logs to see what Alexa heard you say?
Yes and in each case it's exactly as I spoke it...
-
I'm happy to hear your setup is now working correctly. That said however, it doesn't explain why many of us are still getting the "That command doesn't work with that device" response. I really hope Amazon gets to the bottom of this quickly as I don't feel like I can depend on it at this time...
Chuck
It does seem related though given the symptoms and timing of all this. I passed on my fix to Amazon and they replied assuring me they have passed this along up the chain.
-
Having to alter the spoken command to exclude the word "lights" is a symptom. Changing the group name to include "lights" is only a workaround and not a "fix". Amazon broke something, plain and simple.
-
Having to alter the spoken command to exclude the word "lights" is a symptom. Changing the group name to include "lights" is only a workaround and not a "fix". Amazon broke something, plain and simple.
I think we are in complete agreement and I don't see anything I said that would have made you believe otherwise.
-
As of Sunday night, everything appears to be working properly as it did prior to this problem.
I don't know what Amazon did to mess up everyone's home automation devices, but it seems that they either fixed it or undid what they were attempting to do.
-
Can you confirm that you can say "Alexa, turn off the living room lights" without Alexa saying that she can't find a group or device called "living room lights". If that doesn't work then they didn't fix the problem 100%. I was able to include the word "lights" in my sentence for all groups created prior to 1/7/16. I will test when I get home today.
-
I was still experiencing some hiccups Sunday evening with "That command doesn't work on that device".
-
I was reading an article yesterday where there were some recent changes to the echo command. for example, if you have a light called bedroom and you have been saying "alexa turn on the bedroom light" then it may not work anymore. You have to say "alexa turn on bedroom" leaving off the light.
http://betanews.com/2016/01/10/using-amazon-echo-to-control-your-home-theres-a-minor-change-you-need-to-know-about/
-
That's unfortunate. It makes no sense actually. It ruins the "star trek computer" experience completely because saying "lights" was so natural. Thanks for the info.
-
Looks like someone came to their senses at Amazon and backed out the code that screwed everything up about a week ago. Also I can now use the word "lights" in a sentence without altering the names of my groups as suggested. "Everything's under control, situation normal".
-
Alexa Error That Command Doesn't Work
My name is Willie Colón (Cologne) www.williecolon.com @williecolon facebook.com/thewilliecolon I have solved the Alexa device problem! Please get back to me if it works for you WACCO1@LIVE.COM. Get a piece of paper to write this down... Make sure your echo is connected and working. Tel Alexa "Discover devices" DONE!
-
I am having this exact problem. New to Smart home and Echo. I've have about half my home setup, and it's frustrating when you get "that command doesn't work on that device...", or Echo & Dot awakes on the command and then goes back to sleep almost immediately. I will be following this thread closely and trying some of the suggestions made here. Thanks to all for you input and help.
M. Small
-
Restart ALL your Alexa devices by unplugging them for 5 minutes and then plug them back in. If after they are rebooted, check everything again. If all work fine, great, and if not, problem is likely with devices you are trying to control. So, check forums for those devices.