Hi,
I’m using a customizable/programmable remote control to control some of my Hue lights.
I have implemented a dimming function that works by issuing a POST request to /api/services/light/turn_on with the entity_id and brightness_step_pct: [-]nn as payload.
The actual step percentage varies, but usually is 5 or 10 (it’s created by a jog dial type controller).
In a real-life scenario, when dimming a light, the remote would issue a series of maybe 5-10 of those requests one immediately after another.
This used to work pretty good until recently, maybe a few weeks ago.
Currently, while e.g. dimming down a light, the brightness is reduced, then jumps back up a few percent again, is reduced again, jumps back up etc.
The light can eventually be dimmed down to zero, but it’s no smooth process like it used to be.
Could it be that somehow the light.turn_on service is also using the absolute brightness value determined from HA’s current state (which could be slightly delayed and not reflect the state after executing the latest dimming command)?
Does anyone with a knowledge of the Hue integration’s internals have an idea what’s going on here?
Is this a bug or a feature? 
Any help figuring this out would be appreciated.
Sebastian