I want warm white, and dimmable. Colors aren’t necessary.
I currently have a crappy old florescent fixture, which is controlled by a regular light switch. I want remove that and wire these LED strips to the light switch, which I would replace with a GE Z-Wave dimmer switch (which we know operates with no problems with ST!) And then add a ST Motion Sensor, so the counter lights fade up when I walk in.
This of course ignores the fact that the strips are DC, and the GE Switch takes AC. The tech guy at Super Bright LEDS pointed me to this power supply:
…but he couldn’t guarantee it would all work if I wired that thing to a GE dimmer switch. If I cut power on the AC switch side, it might not dim the LED strips on the DC side. But I’d rather not mess with all of these unsupported devices-- I’d much rather get it all to work with a GE dimmer.
It might work if the WiFi controller is similar to the ‘Limitless’ controller and the various other brands that copy each other but otherwise, you’re probably not going to have a good time of it. At the moment the two favoured controllers are the Dresden FLS-PP IP (ZigBee and may require a Philips Hue Bridge):
Hi, Scott. The White LEDs do not operate at all when connected to the white channel. If I swap the white wire with one of the RGB channels, they do operate. I tried the Osram device type as you suggested, as well as the ZigBee RGBW bulb, and neither of these made a difference. The RGB functions work fine in all cases. Any other ideas? Thanks!
One more. Can you look at the device screen and post what is in the Data and Raw Description areas? If those aren’t populated, could you reset and re-pair the device while running live logging?
I have a hunch that the W channel is operating on a 2nd endpoint with separate on/off/dim control. Not many devices have usable functions on 2 different endpoints, and it’s not something ST natively handles, but it is something we can accommodate with custom code.
It doesn’t list whether there is a 2nd endpoint. You up for resetting/re-pairing to get the live logs? If you paired it recently, you could check your hub’s events for the join info.
It would look like the screenshot in this post. You can see that this device had 2 endpoints and you can see the raw description for each. If we at least get the other endpoint number, we can code for it since I know what the clusters should be.
To confirm that is the white channel, try replacing the ${endpointId} in the on(), off() and setLevel() commands with 0x0B to address that secondary endpoint directly.
If that works, then it’s just a matter of deciding how you want the white channel to work. Should it have its own separate controls for on/off/dim using custom commands? Should we turn it on in conjunction with the RGB by adding a 2nd “st cmd” line to each of on/off/setLevel?
Edited to add: I’m going to be unavailable until Fri or so, but I can help you work up the final devicetype then.
