Hue not set correctly

[willem4ever]

Not sure if this has to do with rest-plugin or deconz itself, or maybe just the ballast-pp. Anyway here is the issue. I send bri, hue and sat to the bridge using the rest api. All parameters are acknowledged with success, however the ledstrip shows the wrong colour. Sending just the single parameter with the hue value sets the colour right. The behaviour seems only to apply to ballasts, philips hue spots seems to respond fine.

Using The colour control cluster in the deconz guy and doing an exec enhanced move to hue sets the colour also right in one go, but I guess this is comparable with just sending a hue command thru the rest api.

[manup]

Hello Willem,
thanks for the report after a some testing with a FLS-PP I can confirm the behaviour.
The issue is within the ballast firmware (version 14010400).

As workaround the commands could be send seperated into two sets:

• bri, on [, transitiontime]
• hue, sat [, transitiontime]

The second command shall be send after a delay of transitiontime which defaults to 4 (400 ms).

The problem is that a API command like { "on": true, "bri": 200, "hue": 0, "sat": 224, "transitiontime": 10 }
is translated into two ZigBee commands and the internal state of the ballast is not correctly updated if the first command is not finished (transitiontime) while the second command is received and processed.

The next firmware release which will be updated via over-the-air-update (OTAU) will fix the issue.

[willem4ever]

thanks for analysis of the problem, looking forward to the updated firmware.

[willem4ever]

hi is the updated firmware available - it has been 4 months now -

[manup]

Hi William, I'm afraid the firmware is not available yet it will be released together with the new version of deCONZ which is scheduled in July.

[willem4ever]

Any news here ?

[willem4ever]

disappointing there is still no update for this ....

[dwaldhans]

Hello there!

I just found this thread because I am having exactly the same problem with my FLS-PP devices. Are there any news on this bug?

Kind regards,
David

[manup]

Closing the oldest issues for know to tidy up the tracker and duplicates in newer issues.