tiptronic
commented
7 months ago Hi @HDClown the differences you see are likely related to the fact that the plugin communicates with the bridge over HTTP, which is nowhere near realtime. But you're invited to try out our current early access beta version, where we try to address all these issues. That one is still not realtime, but should be much better than this version... You can safely install this version alongside the old plugin and see if the changes work for you and join the discussion if you like.
HDClown
This was mentioned in (issue 40) when brightness for room/group was added.
If you turn the knob to fast the brightness percentage on the display will bounce back/forth between the numbers it's trying to set. There can also be extensive delay between a quicker knob turn and the lights applying the settings. This behavior is worse if you do it with a room or group, but it's not quite as bad for an individual light.
I observe the following differences in behavior with the Hue mobile app:
I'm just spit balling here, but this seems like the mobile app may be sending a large/quick change as single command (hue lights, now change from current brightness to 100 brightness) and the slower changes are sent as individual commands (hue lights, now change from current brightness to 30, now change from current brightness to 35, now change from current brightness to 40, etc).
Could this type of behavior be replicated in the knobs? If you are slowly turning the knobs it sends every tick, but if you spin the knobs "fast", the command to change to the new brightness isn't sent until it has been observed that the knob hasn't spun for 0.5-1 second?