I submitted a ticket this weekend to Hubitat on this. How long typically before they get to it? (I ask because SmartThings never looked at tickets, so curious as to whether it was an exercise in futility.)
Huh?, I've never seen a Zigbee device that presents it self and joins as two separate and independent zigbee nodes, how are we coming to the conclusion that the device operates this way?
Huh?, I've never seen a Zigbee device that presents it self and joins as two separate and independent zigbee nodes, how are we coming to the conclusion that the device operates this way?
Well, you could follow the link in the original post, to the product page which clearly states, "For RGBW/RGBW devices you will find two SSIDs. One for white/warmwhite, the other for RGB.".
Their support also states so, as do the comments and the manual.
1 Like
yeah, I could along with all the other things I have to do...
In short, we/I already have a number of devices in Q that aren't implemented in some bizarre fashion, those are going to take precedence...
How do you take this as "bizarre", other than not having seen it before? It's just presenting two devices for discovery, which apparently the other hubs handle well but not HE.
I would suspect that this won't be an edge case for long, if it even is now. Complex devices will wind up presenting as several, and if HE is crapping out where other hubs work on this, what makes you confident this isn't just a firmer exposure of an underlying bug that, once fixed, will clear up multiple issues?
sure we can start there, having written dozens of ground up zigbee drivers from dozens of different manufacturers, I can say this is bizarre.
There is flat out no reason on gods green earth to implement a device this way, zigbee provides 8 bits of endpoint address space specifically for this reason.
So yeah, I'm not going to spend much time right now figuring out how to accommodate this device.
Hubitat is able to join multiple.devices simultaneously tho, right? I've seen that mentioned before and is apparent in the join page. So it seems strange to me that this single device with 2 ID's isn't able to be seen by the system.
My guess is that it's presenting both too closely together and Hubitat HE is temporarily not listening right upon receiving one new device. It's not terribly important though, given that @mike.maxwell has stated it won't get supported. I'll find a different strip controller.
Yeah, it's a shame because I have one about to be delivered so it's bucks down the drain. Sigh. I bought it upon seeing a positive comment on the forum but now we find this issue with the 2-ID one. May try the 1-ID one instead. The saving grace is they are quite cheap anyway.
@mike.maxwell So one big advantage of the Giderwel / Gledopto 2-ID Controller approach, over the RGBGenie 1025 approach, is that the Giderwel allows full control of the white channels distinct from the RGB channel. You can toggle which white (cool vs warm) is on, and how bright.
The RGBGenie only supports four, not five, channels, so there is no "toggle" option anyhow, but it also cannot have just the RGB on, without the white. The Giderwel can.
None-the-less, I've switched to the RGBGenie and compatible strips, to be HE compatible. But, for future support...
1 Like
According to this YouTube it looks like Hue supports the 2-ID unit...
"Just a few words" taking over four minutes! Sheesh!
TL;DR: SmartThings doesn't see the 2 IDs either, but if you spring more for the Hue, you can get there. Uggah.
1 Like
Yeah. Will try to source a cheap 2nd Hue Hub v2.1 off eBay. Actually the hub is a lot cheaper than the shipping to Asia sigh. Or maybe @mike.maxwell will recant his hatred of poorly implemented Zigbee protocols and get these working with Hubitat eventually! 
Unlikely I think 
I think this is probably just a bad translation. I've found discussion elsewhere stating that it is two endpoints, which makes a lot more sense. I have one coming this week that I'm going to play around with since I am apparently a glutton for punishment.
Yeah, but if HE won't see and allow connection to the 2nd ID/Endpoint when initially connecting the device, then there is nothing we can do, right? And from what Mike has said, Gledopto's employed a strange approach that he's not interested in prioritising for HE.
(I assume) the generic drivers are just not written to take a 2nd endpoint into account. If it really is just an extra endpoint, then I should be able to write a driver to deal with that (child devices, I'm thinking). At least I could on that other platform. We will see!
I'm bored and haven't had a chance to write a useful driver since the keypad on ST, so I'm hoping that I'm right 
1 Like
@mitchp Possibly, but it never seemed to pick up the other endpoint for me. If it had, I could have configured it as two devices
It would appear to be one device. The driver would need to know to either create child devices for each or would have to handle which commands went to which endpoint. The Iris Keyfob, for example, is a multi-endpoint device (one per button) that appears as a single device.
Just wanted to voice my support for the 2ID Gledopto. I too got the color channel working but the white channel is absent from my HE. If I could avoid the Hue Hub it would be a huge win!
No promises, but mine comes tomorrow and, time and SO allowing, I'll be banging away on it tomorrow after work.
2 Likes
