-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Description
Expected Behavior
Issuing a command to a Deconz extendedcolorlight color channel does not update the item state.
As far as I can tell this worked in the 4.1.X version, but the behavior changed with 4.3.5.
Current Behavior
The item state is not the same as the issued command.
Setting the value to 13,97,10
makes the item state go to 15.641,87.13100,100.00
and after a short delay it becomes 21.749,87.37800,52.781
. The light itself is dimmed to (whats seems to be) 10% and stays that way. It never has a brightness of 100% (which would be the first state after issuing the command) nor does it change its brightness in anyway after the initial dimming.
Issuing the same command again will not change the state to 13,97,10
either.
Steps to Reproduce (for Bugs)
Thing:
extendedcolorlight Light_LED_Office "LED-Streifen Büro" @ "Office" [ id="16" ]
Item:
Color Light_LED_Office_Color "LED-Streifen Büro Farbe" {channel = "deconz:extendedcolorlight:homeserver:Light_LED_Office:color"}
- Send command
13,97,10
- Check state -> it is
15.641,87.13100,100.00
- Check state after 1 second again -> it is
21.749,87.37800,52.781
Context
I noticed this because I have rules that set the light value and then change it back after a while if it has not changed. This check now fails, because the expected value (the command issued) will always differ from the current state.
Your Environment
openHABian with 4.3.5 on a Raspberry Pi