Closed philhawthorne closed 7 years ago
Do you have a transition specified somewhere? See https://github.com/home-assistant/home-assistant/issues/6295
@janLo yes, yes I do. Thank you!
So, looks like if you have a transition anywhere for that light, the exception is thrown and you can't use it. Looks like I'll wait for 0,40 or apply your patch for now :)
Thanks again!
Hey @janLo after upgrading my version to the latest limitlessled library (1.0.5) I'm still seeing problems controlling lights that contain a transition
. Wondering if the fix hasn't worked.
I havn't upgraded my limitlessled as I let HA pull its needed dependencies. I applied the patch as I wrote earlier and the problem is gone. Can you post the error/exception you get?
@balloob can we please release a bugfix release as more and more people run into this regression? Also the clarification for the docs need still to be merged.
@philhawthorne The patch is definitely in the 1.0.5 tarball.
Yeah that's what I thought too.
Okay I'll dig some more. Maybe my instance has reverted for some reason. I'll double check when I can to make sure it's on the right version and retest everything.
Home Assistant release (
hass --version
): 0.39.3Component/platform: LimitlessLED
Description of problem: Since the upgrade to 0,39, Home Assistant loses the ability to control my second LimitlessLED Wifi Bridge.
When restarting Home Assistant, all my LimitlessLED lights turn off during the reboot phase. After the reboot, I am able to control my lights on the first bridge as expected.
However, at random points in time, Home Assistant loses the ability to control my second LimitlessLED bridge. This means the lights attached to them are stuck off/on depending at what time Home Assistant loses the ability to control that bridge.
Expected: I should always be able to control my lights. Previous versions of Home Assistant did not have this issue.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):