has anyone else noticed that if you send say a color temp of 6500 the bulb shows 6535 as the current color temp. incrementing down the command gets a different result on the status. all the way down at 1900 its a bit closer with it showing as 1901. Any idea of a fix for this? I like to keep my bulbs synced to a specific CT and this mismatch will cause unnecessary zigbee traffic with constant ct commands being sent due to the mismatch.
Thanks!
There is always a small difference between what's sent vs what's reported, it seems to vary by manufacturer.
A human can't resolve a difference of 35 Kelvin, so while possibly annoying it really doesn't matter.
that's what I was thinking - I guess I'll just need to add a 'deadband' for the check rather than a flat equality check. Thanks!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
