Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue setting bri and color (ct/xy) simultaneously in IKEA trådfri lights #895

Closed
lbschenkel opened this issue Oct 22, 2018 · 5 comments
Closed
Labels

Comments

@lbschenkel
Copy link
Contributor

lbschenkel commented Oct 22, 2018

Please check #894 for reference about the setup. I'm reporting here what it looks like a different firmware bug.

In IKEA lights, if you set bri and color (ct or xy) simultaneously in the same REST call, the light changes to the requested configuration for a fraction of a second but then goes back to the previous bri and only the color "sticks". Setting it separately works. Strangely, if you set both and also specify transitiontime of 0 or 1, then it works.

My understanding is that setting bri and xy is not possible within the same Zigbee message, so deCONZ must be sending two when they're specified simultaneously. The fact that a transition of 0 works makes me speculate that the light has a firmware bug in which when it gets two messages in quick succession, the second overwrites the state of the first when the light is still transitioning from the first message. Setting a shorter transition than the light default (which seems to be a bit over 100ms) works because the light finishes changing state before the next message and the race condition is avoided.

As with the other issue, I'm reporting this to check if it's possible to implement some sort of workaround in the deCONZ side to address this firmware bug (at least partially) and hopefully help getting one implemented.

Potentially related issues: #753, #445, #81

@stale
Copy link

stale bot commented Feb 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 19, 2019
@lbschenkel
Copy link
Contributor Author

@stale stale bot removed the stale label Feb 24, 2019
@stale
Copy link

stale bot commented Jun 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 24, 2019
@manup
Copy link
Member

manup commented Jun 24, 2019

To my knowledge the bug still isn't fixed. Hopefully the new device revisions which will be released in August (?) have improved firmware.

@stale stale bot removed the stale label Jun 24, 2019
@stale
Copy link

stale bot commented Oct 22, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 22, 2019
@stale stale bot closed this as completed Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants