Closed aegjoyce closed 3 years ago
Sorry for the late response, I have been a long way from all my smart home gear since the start of lockdown! It seems like this would be a pretty easy fix; just checking the state in the Python command for turning the light on. If you are confident with Python I would happily accept a working pull request, otherwise I can have a go reasonably soon, though I would need to send the code to you for testing before pushing out the update, as I have no way of testing it myself at the moment
Hmm... weirdly enough, testing it today on 0.114.3, I can't seem to replicate the error - looks like there has been a backend fix for it! I'll close this for now and reopen if it starts happening again.
Minor issue with the Ambilight component - if the Ambilight is already off and a light.turn_off service is passed to it, the following error occurs:
This appears to be an issue with the Ambilight component and the way it handles light service calls - for any other light, if it is already switched off and a light.turn_off service is called, no error occurs.
This is running on HA 113.2 on an rPi 4 using HassOS.
Unfortunately this breaks a few automations for me - I have an automatically-generated group.all_lights which won't accept a homeassistant.turn_off command because of the ambilight error.
Otherwise an excellent component that works perfectly with the Wakelock app on my 55OLED804. Many thanks!