if I create a routine in the alexa app to turn on and off the switch, it works without alexa complaining. it’s a pain to do that for 15 switches, but it is a work around.
1 Like
An easier work around would be to use this platform to change all your switches into lights:
There are other similar issues with Emulated Hue:
https://github.com/home-assistant/home-assistant/issues/23435
Thanks… I was thinking of trying that also - the switches are sonoffs with tasmota on them although I do have one esphome sonoff switch, listed as a light and have the same issue. but worth a shot.
tried the light: platform: switch for the sonoff(tasmota) device - no change - turn on - device is not responding - device does turn on. turn off - alexa responds ‘ok’ switch turns off.
Unless you desperately need something that was added in 0.92.x, roll back to 0.91.x and the issue goes away.
I’ve seen the same, it does indeed go away.
Yep I rolled back to a 0.91.3 snapshot I had and everything works perfect again. They’ll figure it out here soon and I’ll upgrade.
Having said that I have no new stuff in my home for quite some time now, I probably could have stopped upgrading in the 0.50 world or something 
One of these days I’ll lock it down and make a spare SD card or two
1 Like
Same results for me, HA back to 0.91.3 Hassbian and Alexa quit complaining.
1 Like
Same problem, joining the “wait for the fix and roll back” group
1 Like
The problem seems to be that switches and input_booleans are report as type “Dimmable light”.
Also the attributes for brightness, hue and saturation are provided even that they arn’t support.
If you instead report “On/Off light” as type and don’t provide the attributes , the error doesn’t occur.
You can give it a try by using this version as custom_components:
http://www.mediafire.com/file/adttclvxa4ro2xb/emulated_hue.zip/file
Greetings
That makes sense and ties in with the change that was made in the 0.92.x update adding in dimming functions.
FWIW - Something I noticed that may be related is that the URL http://hassio:8300/api/pi/lights would return a ‘bri’ (brightness?) value of null for switches that had this problem. And it was somewhat sporadic. I have since reverted to 91.4 and brightness never seems to be null in the above response.
Dev who made the 0.92 changes is looking into it
https://github.com/home-assistant/home-assistant/issues/23514#issuecomment-490934843
1 Like
Same issue for me. Devices turn OK without any errors, but when I turn them off the Echo says ‘check network connection’ however the device still turns off.
I’ll add my info to github if I can find any logs from emulated_hue
Not to make any sort of attack on a dev, but it surprises me that something like this slips through testing. I would have thought if the code was tested before release, this would have popped up and not passed.
Again, not an attack on any dev, I really appreciate the work everyone does.
1 Like
I can confirm the code change made HERE works and resolves the issue.
I edited the hue_api.py file in my 0.93.0 docker container, restarted, and tested. Problem resolved.
1 Like
Everything is working Raspberry PI Hassbian HA 0.93.1. Thanks for all your hard work!!
the pull hasn’t been merged yet. You need to add it as a custom component. I don’t think it will make it into the 0.93 build.
My Hassbian installation is still on my original All-In-One Installer on a Raspberry PI and still works great. I placed the modified hue_api.py here /srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/components/emulated_hue/hue_api.py. I tried the Hassio installation could not get all of my systems working. I also updated to 0.93.1 and still working. Thanks again for all of your work correcting the confusion with Alexa!!