I can't change colors of BTF-Lighting RGB+CCT LED strip using Hue Hub, C05Z controller and CoCoHue

🛎️ Get Help Integrations
1

Hi, I have the BTF-Lighting connected to C05Z Zigbee 3.0 Controller, have a Hue Hub, which found it and controls it well, colors and all. BUT, I can't change colors from Hubitat Devices. It says device is in RGB mode and I think it must be in HSL mode, is that right? I don't know how to force it into HSL mode. When I pick a color and Set Color, it seems to change but never reflects what I chose. For example, choose blue and press Set Color and it doesn't change. I can see in Hue app, there's no change either. But turning light on or off works, for example. I turn it off in HE and Hue app shows it move to off. Turn on in Hue app and HE shows it's on. But, colors just don't seem to be setting in HE, nor sync with HUE app. What am I doing wrong? I've tried lots of combinations of setting HSL in HE and that changes the strip, but I can't get the colors I want for some reason. Seems like I should just be able to Set Color off the picker in HE and see it change the LED strip color. Without this, I can't setup the rules I want, which was going to modify colors of the strip for different conditions. I tried without CoCoHue package first and same result.

How do I get HE to direct the Hue Hub to set those colors on the strip. No issue doing it with the Hue app by itself.

2

So the Hue app doesn’t show them correctly either? That would be indicative, most likely of the bulb not reporting colors back to the network. If the app/bridge shows the correct colors, I could see if maybe the device was an XY color mode instead of HS (hue/saturation, reported as RBG and easily convertible to exactly that) color mode, which is not well supported on Hubitat.

it sounds like this is a third-party device, and I haven’t found one that entirely fails on Hue, but I guess some odd behavior is possible (and that I have seen in general).

3

Thanks for response. The Hue App works well and setting color there accurately results in the strip reproducing the chosen color. It seems to work as intended. And, if I turn off the strip in Hue app, the HE devices panel toggles to off to show the accurate state of the strip. And, if in HE I toggle back to ON the strip goes on and the HUE app toggles to show it on. It's the color part that isn't translating from HE to the strip.

It seems to me that the HE simply needs to tell the Hue Hub to modify colors in the same way the Hue app can accurately run the Hue hub. So I would have expected HE to be able to communicate to the Hue Hub and direct it to modify a color of any connected and working Hue device (whether generic or not). In this case, yes, it's a third-party LED strip made by BTF-Lighting and connected via C05Z controller, but HUE Hub runs it perfect. So something is just not communicating between HE and the HUE Hub. Wouldn't it be that simple in theory? I added the CoCoHue integration because I understood it to have better color integrations, but still no luck. NOTE: It does modify the strip when I use HSL in HE but I can't seem to get the colors I want. And, I'm puzzled as to why I can't just use Set Color directive and have it work.

I read something about 1DI vs. 2DI controllers and the fact that with strips that do RGB and CCT that only one channel can be controlled at a time but that's not verified. I just wonder if I'm accurately controlling only CCT (color temperature) in HE, which does seem to work but for some reason can't control colors. Just to be clear, if I click the CCT control on Hue app and drag the icon to a different color temperature, the HE Devices panel shows that update AND, if I set Color Temperature in HE, it works as expected and the Hue App updates too. There's some reason why Color Temperature (the CCT) part works fine, but RGB or HSL type color seems not synchronizing. Would a 2DI controller make some difference? Or, can I somehow flip the mode control so that I can modify RGB color and leave color temp uncontrollable...is it one or the other?

4

This is strongly suggestive of the device only supporting or reporting XY and not HS color values. This does not work well on Hubitat because Hubitat's native color model, including the ones the "Current States" report, is HS. (I am looking into conversion, but it is not easy--or at least not reliable.)

But this can't be said without seeing the actual data. Enabling debug logging for the bridge device and the device in question will tell you more about the data that's coming in (including the actual JSON, or the Groovy object parsed out of that--this is key) and how it's being handled.

It's still not clear exactly what is and isn't working as you expect (what commands from where actually work or not and where you do or don't see the real-world state reflected as expected). The above would explain colors showing correctly in the Hue app but not Hubitat when set from Hue, colors possibly working (or not) when sent from Hubitat but possibly (likely) not reflected in Hubitat after the command, and any number of things for CT depending on if the device also supports CT or just XY color.

5

Not sure if this will help, it's a smattering of logs from the Light strip device and Hub device, both after applying CoCoHue and before CoCoHue. I notice a line in there like: "ignoring command, device not in HS mode."

At Device (LED Strip)
dev:3372024-08-17 07:58:52.876 PMinfoExtended color light 1 (Hue Bulb) colorMode is RGB
dev:3372024-08-17 07:58:52.872 PMinfoExtended color light 1 (Hue Bulb) colorMode is RGB
dev:3372024-08-17 07:58:52.870 PMinfoExtended color light 1 (Hue Bulb) colorName is Orange
dev:3372024-08-17 07:58:52.859 PMdebugMap after ignored keys removed: [hue:6189, sat:140,
transitiontime:4]
dev:3372024-08-17 07:58:52.853 PMdebugPreparing to create events from map: [on:true, hue:6189, sat:140, transitiontime:4, bri:127]
dev:3372024-08-17 07:58:52.852 PMdebug Bridge response valid; creating events from data map
dev:3372024-08-17 07:58:52.845 PMdebugChecking if valid HTTP response/data from Bridge...
dev:3372024-08-17 07:58:52.843 PMdebugResponse from Bridge: 200
dev:3372024-08-17 07:58:52.810 PMdebug-- Command sent to Bridge! --
dev:3372024-08-17 07:58:52.802 PMdebugsendBridgeCommand([on:true, hue:6189, sat:140, transitiontime:4, bri:127])
dev:3372024-08-17 07:58:52.801 PMdebugReturning: [:]
dev:3372024-08-17 07:58:52.800 PMdebuggetPrestagedCommands(true)
dev:3372024-08-17 07:58:52.796 PMdebugsetColor([hue:34, level:50, saturation:55])
At CoCoHue Hub
dev:3362024-08-17 08:03:53.828 PMdebugparse: data: [{"creationtime":"2024-08-18T00:03:51Z","data":[{"dimming":{"brightness":100.0},"id":"95e4450e-6af0-4b40-8b0b-5249862a1df5","id_v1":"/groups/81","owner":{"rid":"8786099c-b844-4071-8ba7-9487b798cc8c","rtype":"room"},"type":"grouped_light"},{"dimming":{"brightness":100.0},"id":"b47f88f9-6b5e-4316-abca-6f2b48f53405","id_v1":"/groups/0","owner":{"rid":"ce536733-7116-473a-8d58-02e918a3ec76","rtype":"bridge_home"},"type":"grouped_light"}],"id":"cd85d737-f188-41ee-8de7-f7c18af8da74","type":"update"}]
dev:3362024-08-17 08:03:53.823 PMtraceno data parsed from message: id: 1723939432:0
dev:3362024-08-17 08:03:53.817 PMdebugignoring line: id: 1723939432:0
dev:3362024-08-17 08:03:53.802 PMdebugparse: id: 1723939432:0
dev:3362024-08-17 08:03:52.864 PMdebugparse: data: [{"creationtime":"2024-08-18T00:03:51Z","data":[{"dimming":{"brightness":100.0},"id":"89adc4b0-cc0a-4003-b28c-3667872e5b51","id_v1":"/lights/1","owner":{"rid":"70c728da-2585-4ed8-97fa-5da4fc46b8c5","rtype":"device"},"service_id":0,"type":"light"}],"id":"7e018bad-f3b5-4ea3-aba5-10ff257435a0","type":"update"}]
dev:3362024-08-17 08:03:52.856 PMtraceno data parsed from message: id: 1723939431:0
dev:3362024-08-17 08:03:52.855 PMdebugignoring line: id: 1723939431:0
dev:3362024-08-17 08:03:52.801 PMdebugparse: id: 1723939431:0
But, here's from HUE HUB non CoCo device earlier in Day
dev:3342024-08-17 05:14:12.576 PMinfoExtended color light 1 saturation was set to 20%
dev:3342024-08-17 05:14:12.572 PMinfoExtended color light 1 hue was set to 7%
dev:3342024-08-17 05:14:12.568 PMinfoExtended color light 1 level was set to 11%
dev:3342024-08-17 05:14:05.482 PMwarnrefresh disabled, refresh is controlled by the Hue bridge integration
dev:3342024-08-17 05:14:04.438 PMinfoExtended color light 1 saturation was set to 17%
dev:3342024-08-17 05:14:04.434 PMinfoExtended color light 1 hue was set to 10%
dev:3342024-08-17 05:14:04.430 PMinfoExtended color light 1 level was set to 55%
dev:3342024-08-17 05:13:51.691 PMinfoExtended color light 1 hue was set to 38%
dev:3342024-08-17 05:13:44.105 PMinfoExtended color light 1 was turned on

More Misc from Device non CoCoHue
dev:3372024-08-17 08:04:21.113 PMinfoExtended color light 1 (Hue Bulb) saturation is 55
dev:3372024-08-17 08:04:21.107 PMdebugSkipping colorMode and color name event creation because light not in hs mode
dev:3372024-08-17 08:04:21.103 PMinfoExtended color light 1 (Hue Bulb) colorMode is CT
dev:3372024-08-17 08:04:21.099 PMinfoExtended color light 1 (Hue Bulb) colorName is Horizon
dev:3372024-08-17 08:04:21.095 PMinfoExtended color light 1 (Hue Bulb) colorMode is CT
dev:3372024-08-17 08:04:21.092 PMdebugPreparing to create events from map from Bridge: [alert:select, bri:254, colormode:ct, ct:200, effect:colorloop, hue:0, mode:homeautomation, on:true, reachable:true, sat:140, xy:[0.3857, 0.2548]]
dev:3372024-08-17 08:03:52.982 PMinfoExtended color light 1 (Hue Bulb) level is 100%
dev:3372024-08-17 08:03:52.978 PMdebugcreateEventsFromSSE([dimming:[brightness:100.0], id:89adc4b0-cc0a-4003-b28c-3667872e5b51, id_v1:/lights/1, owner:[rid:70c728da-2585-4ed8-97fa-5da4fc46b8c5, rtype:device], service_id:0, type:light])
dev:3372024-08-17 08:03:52.842 PMinfoExtended color light 1 (Hue Bulb) colorMode is RGB
dev:3372024-08-17 08:03:52.838 PMinfoExtended color light 1 (Hue Bulb) saturation is 100
dev:3372024-08-17 08:03:52.824 PMinfoExtended color light 1 (Hue Bulb) colorMode is RGB
dev:3372024-08-17 08:03:52.821 PMinfoExtended color light 1 (Hue Bulb) colorName is Red
dev:3372024-08-17 08:03:52.818 PMinfoExtended color light 1 (Hue Bulb) hue is 0
dev:3372024-08-17 08:03:52.814 PMdebugMap after ignored keys removed: [hue:0, sat:254, transitiontime:4]
dev:3372024-08-17 08:03:52.807 PMdebugPreparing to create events from map: [on:true, hue:0, sat:254, transitiontime:4, bri:254]
dev:3372024-08-17 08:03:52.805 PMdebug Bridge response valid; creating events from data map
dev:3372024-08-17 08:03:52.798 PMdebugChecking if valid HTTP response/data from Bridge...
dev:3372024-08-17 08:03:52.796 PMdebugResponse from Bridge: 200
dev:3372024-08-17 08:03:52.733 PMdebug-- Command sent to Bridge! --
dev:3372024-08-17 08:03:52.725 PMdebugsendBridgeCommand([on:true, hue:0, sat:254, transitiontime:4, bri:254])
dev:3372024-08-17 08:03:52.724 PMdebugReturning: [:]
dev:3372024-08-17 08:03:52.723 PMdebuggetPrestagedCommands(true)
dev:3372024-08-17 08:03:52.720 PMdebugsetColor([hue:0, level:100, saturation:100])
dev:3372024-08-17 08:03:21.099 PMdebugSkipping colorMode and color name event creation because light not in hs mode
dev:3372024-08-17 08:03:21.093 PMdebugPreparing to create events from map from Bridge: [alert:select, bri:127, colormode:ct, ct:200, effect:colorloop, hue:6189, mode:homeautomation, on:true, reachable:true, sat:140, xy:[0.3857, 0.2548]]
dev:3372024-08-17 08:02:21.094 PMdebugSkipping colorMode and color name event creation because light not in hs mode
dev:3372024-08-17 08:02:21.088 PMdebugPreparing to create events from map from Bridge: [alert:select, bri:127, colormode:ct, ct:200, effect:colorloop, hue:6189, mode:homeautomation, on:true, reachable:true, sat:140, xy:[0.3857, 0.2548]]
dev:3372024-08-17 08:01:21.127 PMdebugSkipping colorMode and color name event creation because light not in hs mode
dev:3372024-08-17 08:01:21.092 PMdebugPreparing to create events from map from Bridge: [alert:select, bri:127, colormode:ct, ct:200, effect:colorloop, hue:6189, mode:homeautomation, on:true, reachable:true, sat:140, xy:[0.3857, 0.2548]]
dev:3372024-08-17 08:00:21.107 PMdebugSkipping colorMode and color name event creation because light not in hs mode
dev:3372024-08-17 08:00:21.101 PMdebugPreparing to create events from map from Bridge: [alert:select, bri:127, colormode:ct, ct:200, effect:colorloop, hue:6189, mode:homeautomation, on:true, reachable:true, sat:140, xy:[0.3857, 0.2548]]
dev:3372024-08-17 07:59:21.257 PMdebugSkipping colorMode and color name event creation because light not in hs mode
dev:3372024-08-17 07:59:21.240 PMinfoExtended color light 1 (Hue Bulb) colorMode is CT
dev:3372024-08-17 07:59:21.208 PMinfoExtended color light 1 (Hue Bulb) colorName is Horizon

Hope the above may be revealing in some way. Thanks.

6

According to the logs, your device is in CT (color temperature, or shades of white) mode and not any sort of color (HS or XY) mode. So, it's simply taking the "ct" value as reported in the logs as the representation of the current state. That data is coming from the bridge, so if that's wrong, the device is reporting it wrong or not at all for some reason.

If you didn't have the device in some sort of color mode, of course, that would be the other explanation. (I'm assuming that's not it given how unhelpful you'd likely have assumed it is for demonstrating this problem, but if not...)

7

Thanks. So do you mean HE "sees" the device in CT mode only? But, the Hue hub "sees" that it is a color capable device. Actually the Hue app has two circles for control - one circle, when clicked, shows a CT globe and swiping it works. The other circle shows a RGB type globe and swiping around it works/changes color. So, the Hue system is controlling it fine. What would account for HE connecting to a Hue Hub via integration but "seeing" an attached device as only a CT device? Why doesn't it just sort of hand off the commands to modify color to the Hue hub and let the hub do the rest? Is there some integration issue where the Hue Hub is misinforming HE that it's working with a RGB capable device? But then there are RGB (color type) controls shown in HE devices interface, suggesting HE thinks its a color capable device. I notice a few posts that discuss "Forcing a controller to use RGB and CT at same time." Not sure if that explains it. But, they discuss the need for two controllers....?? My goal was just an under cabinet kitchen led strip that illuminates when working in kitchen, but which can change color according to rule machine for certain conditions in the home (e.g. garage door open, water in basement..etc.). Not sure if it's my choice of hardware that's making this difficult. Would a different LED strip or different controller, two controllers, 2DI controller etc..make this use case do-able?

8

No, unless you have the wrong driver selected (that is easy to verify).

What I mean is that the device is reporting its current state as being in CT mode as opposed to HS or XY mode. This is similar to how RGBW bulbs behave on Hubitat: they are either in RGB (color) or CT (whites) mode. In your case, the data returned from the bridge show that it is in CT mode:

As such, the "ct" value also reported is the one that matters for how the current state is determined:

or 5000 Kelvin for this particular example (those are mireds in the raw data).

Isn't this how all "White and Color Ambiance" (RGBW or color plus color temperature) bulbs work in the Hue app? That works expected for other devices I have used.

For the first part of your question, I again don't think that's what's happening.

For the second part, Hubitat just sends the commands to the Hue bridge in hue/saturation color per the parameters to the "Set Color" command you issue from the hub. Whether the bulb actually responds to those is up to the bulb and its firmware. If it only takes XY color --that's my guess based on all of the above, despite the fact that I do not see any examples of this in the log entries you provided -- then that would explain why it does not respond to hue/saturation commands. Neither my integration, Hubitat itself, nor the Hue bridge will do any conversion. I have never seen any Hue bulbs that do not support all color modes. The only bulbs I have seen not are some Ikea color bulbs, and possibly only early generations (I have not re-tested). I don't know if this is to spec or not, but it's quite unusual either way. Yours might be yet another example.

9

I was able to find controller directly with HE and the colors worked (taking Hue Bridge out of the config.). Then, I purchased the more common LM052 controller and linked to HE without Hue bridge and that too sets colors properly. This allowed me to use the WR01RF wireless wall switch too, so that if the internet goes down, I can control the hub (and thus LED strip) to turn on and off, color, dimming etc. Seems to work fine and the wall switch seems to work even when paired with HE too. So, that's good. I think I can do what I want using this config, but just funny that so many folks say how well thing work with Hue Hub but in this case, removing that hub and linking just with HE allowed for proper control of the strip, whereas with the Hue Hub, it wasn't doing what I needed. For now, I'll use this approach. Thanks for your input.