homebridge-hue: Workaround for IKEA lights that don't update multiple state attributes
Several IKEA lights have a firmware bug, where they don’t execute a second command received from the Hue bridge or deCONZ gateway, when the previous command is still in transition. Typically when setting both bri and ct or both bri and xy in one API call, the colour (temperature) changes, but the brightness does not. This is especially noticeable when adaptive lighting is enabled, as this changes the colour temperature when changing the brightness.
The usual workaround is to add a transitiontime of 0 to the API call. As of v0.12.3, Homebridge Hue does this automatically. The trade-off is, of course, that the transition is less smooth than usual. Because of this, the lights with the firmware bug need to be whitelisted, so well-behaving lights don’t suffer unnecessarily.
Currently the following models are whitelisted:
TRADFRI bulb E27 CWS opal 600lm;TRADFRI bulb E27 WS opal 980lm.
Please reply to this issue when you have another model with the firmware bug. I need the precise (case sensitive) modelid to whitelist the light, including any spaces and unprintable characters. Best attach the debug dump file, or run ph get /lights/xx/modelid and copy/paste the output.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (6 by maintainers)
Commits related to this issue
- Update HueLight.js Whitelist more IKEA lights, see #830. — committed to ebaauw/homebridge-hue by ebaauw 4 years ago
- Update HueLight.js #830 — committed to ebaauw/homebridge-hue by ebaauw 4 years ago
- Update HueLight.js - Support `colorloopspeed` through new `ColorLoopSpeed` characteristic (deCONZ only); - Support `effectSpeed` and `effectColours` for LIDL Xmas light strip; - Apply workaround for ... — committed to ebaauw/homebridge-hue by ebaauw 4 years ago
That’s a lot of models with the firmware bug. Are there any IKEA lights that don’t have this bug? I might be easier just to enable the workaround for all IKEA lights…