09-10-2017 04:09 AM - edited 09-10-2017 04:10 AM
Everything setup with echo dot and when asked to turn light on it responds with a sucess and the WeMo APP on the phone turns the light green but the actual light does not turn on.
I can make it work by telling echo to turn light on. Then I have to use the phone app to turn it off. Then tell echo to turn it off. Then it will work as it should after that but I have to repeat this process every day.
Any clues to whats going on?
Thanks for any advice offered.
Solved! Go to Solution.
09-10-2017 03:22 PM
Hi, Kennyh327. Allow us to check on this further. What Wemo device are you using? Make sure that the Wemo app is running on its latest firmware. Also, place the Wemo device to a location where it can get at least 2-3 signal bars from the router.
09-11-2017 04:42 PM
09-11-2017 05:01 PM
Besides wemo app I'm also using Automation Manager but problem persists with that uninstalled as well.
That's disconcerting - the "uninstalled" part I mean .
Are you using the dimming or sleep functions? That bulb behavior is a bit tricky and the last time I checked (which admittedly was quite some time ago) the belkin app didn't handle it properly, it's possible the echo isn't either. If so, try changing the brightness level after turning on the bulb, or using the brightness control to turn it on. If it works that could confirm it as a belkin or echo bug.
I think the wemo link is reporting the bulb state is on 'cause the belkin app is showing it as green (that is the symptom of the fade bug - reporting on but it's not), if there's any doubt you can also confirm looking in AutomationManager UI and at its log which will show the state being reported.
09-12-2017 07:21 PM
09-14-2017 09:48 AM
Doesn't look like belkin is ready to "help you with this challenge"...
An alternative is to use AutomationManager as a hub (WemoServer) if you've got a spare android phone. Once it's running in WemoServer preferences enable "Echoi/Dot discovery", then you can use the "Manage Devices" menu item to bridge the wemo bulbs. Run Alexa discovery to find them and it'll be able to control the bulbs locally rather than going through the belkin cloud service.
09-15-2017 02:35 PM
09-16-2017 07:18 PM
Interesting - that's a symptom of that same issue. If I were to guess it'd be that belkin implemented the echo skill for bulbs to dim them to 0 over a short period vs toggling them off immediately. Poor testing on their part not to catch the original as a bug, really poor testing not to catch the "turn back on" problem!