I have the following scene.
The bulbs are Hank and use the OOB Hank RGBW driver. When the scene activates it successfully turns all of the lights off (and sets the bulb colors) but it doesn't turn the bulbs on.
@mike.maxwell Is this a bug in the scenes app or in the Hank RGBW driver?
Thanks in advance!
easy for you to test, when the bulb is off and you set hue/color in the driver does it turn on?
No, it doesn't turn on. Is it supposed to? I don't have any other RGB devices that I didn't write the device drivers for. I actually would prefer that setting HSL doesn't turn the bulb on though. It opens possibilities of adjusting it while it's off without turning it on (for example if you wanted it to follow a circadian cycle and you didn't want it to flash the two or more times a day that you adjusted it). Either way, from my perspective this test still wouldn't tell me what is broken I don't think.
In the scene we don't just specify the hue and saturation. We also have fields to specify switch state and level. The scene app isn't doing anything with those values or if it is... the driver isn't sending them correctly to the bulb (because maybe the bulb can't consume them fast enough and needs a pause for example).
@mike.maxwell Following up on this because I would like some traction on this bug. Using setColor in the driver does not turn on the bulb. Is it supposed to? If so, can you please fix the "Hank RGBW LED Bulb" driver so that it does? If it's not, can you please get the scene app fixed so that it also turns on bulbs when setColor is called?
I'm experiencing this same issue. I have a Sylvania OSRAM Lightify RGBW bulb and I'm using the "Generic Zigbee RGBW Light" driver. I did some testing using a scene with RGB and one with CT using the same bulb. The CT scene turned the bulb on and set the color temp. The RGB scene sets the color but never turns on the bulb.
I don't know if it's a bug in the setcolor function of the device code or the scene code that's not firing the bulb to turn on.