Setting Level, Hue, Saturation & Color giving inconsistant results?


#1

1) Give a description of the problem
Prior to creating this piston I recorded what the settings were in IDE and my goal was to create a piston which ‘reset’ 3 bulbs to their previous accepted colours. However, when doing this via WebCore, the variables were different. The bulbs are Osram RGB Lightify ones if that helps?

2) What is the expected behavior?
I essentially just want the bulbs to be set to the settings I put into my WebCore piston.

3) What is happening/not happening?
Completely different settings after running the piston:

RGB Bulb 1 =

switch: on
level: 100
hue: 17
saturation: 100
color: #FFFFFF

RGB Bulb 3 =

switch: on
level: 100
hue: 17
saturation: 100
color: #FEFF4C

RGB Bulb 4 =

switch: on
level: 100
hue: 17
saturation: 100
color: #F5FF25

4) Post a Green Snapshot of the pistonimage

5) Attach any logs (From ST IDE and by turning logging level to Full)
(PASTE YOUR LOGS HERE BETWEEN THE MARKS)

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.


#2

Anyone have any idea here - I’m really clutching at straws! I’m using the ZigBee RGB Bulb device handler if it helps?


#3

Just guessing here that when you set the Color it overrides your HSL values. According to color picker I plucked out of google #f5ff25 == 63,100,57 HSL


#4

Is anybody else having trouble with Osram Lightify bulbs where you set level but it never makes it all the way to the level you set? Is this the same problem as above?

I’m seeing behaviour like:

bulb at level 60
my webcore piston issues set level 30
bulb ends up at level 52 or 38 or 49 etc…

I thought blasting it with the correct set level command might help but it doesn’t.


#5

Do you have an image of the code that sets the levels.


#6

I think I figured it out. Seems like the device can’t handle 2 simultaneous commands. If I put this 1/2 sec (could be less haven’t tried) wait in there, it works as expected.

11 AM