Dev who made the 0.92 changes is looking into it
https://github.com/home-assistant/home-assistant/issues/23514#issuecomment-490934843
Dev who made the 0.92 changes is looking into it
https://github.com/home-assistant/home-assistant/issues/23514#issuecomment-490934843
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.
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.
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!!
Back to 0.91.3, no trouble with Alexa but now my Amcrest camera switch has been deprecated. Something else to work on.
Testing is easier said than done, often things like this will pass the automated tests, then get merged without any complaints.
It’s not until it actually gets used by a few people that bugs like these are found, I’m glad new versions are released frequently, so usually bugs like this are patched pretty quickly.
I wouldn’t recommend mixing python files from different versions, while it may work now it could lead to issues later on.
Yes, I understand it passing automated tests, I am more speaking of the code itself not being tested in the real world before making the commit, to ensure it actually works as intended.
In this particular case, this wasn’t a significant change that had to be made (from what I can tell) to ensure the device continued to work, it was an adjustment to provide additional functionality. It wasn’t time sensitive, so could have been real world tested before being merged.
Again, not an attack, just an observation. Perhaps I am wrong in my observation.
This is the nature of the beast. I’ve working in software for 10+ years. It’s impossible to test for all scenarios and intermittent issues will always surface. You also have to remember that emulated hue isn’t just for alexa, it’s to emulate a hue bridge and in regards to testing, it works perfectly. The gets and sets place the correct information in all places and the API works as expected. The interface with Alexa doesn’t need to check to see if the information was set, but it does. That’s all on the alexa side and that is one application out of 100s of possible applications.
I can also confirm the ‘fix’ is working! thanks!
The switches are indeed working, but input_booleans don’t appear to be. They work in 91.4 but not after that as best I can tell. I’ve tried 0.92.2, 0.93.1 and 0.93.2. With the rather limited testing I’ve done Alexa is unable to turn on input_booleans in any of these recent updates.
That’s because you aren’t using the fix listed in this thread. The fix has not been merged in any version yet. Apply the fix in the thread and you won’t get the messages. I’m assuming the fix will be added soon.
By the looks of it this fix should be in 0.93.2
Nope, at least not in the container on docker hub for 0.93.2…
Yep, looks like it will be 0.94.0
Confirmed. Fixed in 0.94.0
I beg to differ…I have upgraded to 0.94 and still have the same issue…
Using Sonoff Plugs with Tasmota 6.1.1c…They all work controlled directly from HassIO but with emulated hue and Alexa I get very strange results
For my setup the issue is fixed with 0.94:
Zigbee / deConz switch Osram smart plug.