Hue Bridge Group Discovery Bug?

🛎️ Get Help
1

I think I'm hitting a (new?) bug with group (re)discovery in the Hue Bridge integration.

  1. Create a room/zone in the Hue app w/ a unique name - add lights/bulbs
  2. Refresh group discovery w/in HE Hue Bridge integration - Group discovered no problem
  3. Delete room/zone from Hue app
  4. (After removing any RM dependencies) remove HueBridgeGroup device w/in HE.
  5. Create a room/zone w/in Hue app w/ same name as deleted room/zone - add lights/bulbs
  6. Refresh group discovery w/in HE Hue Bridge integration - Group never discovers

Any advice on how to get the HueBridgeGroup devices back into HE? I suppose I could manually create a device of HueBridgeGroup driver type, but I'm unsure what the HE to Hue binding is based on.

Thanks!

2

@wbcoyote3.public, i have a hue bridge, but to be honest i don't pass any groups through from hue. I do all grouping within hubitat. I don't know if this will help out in any way but I found some odd stuff in my old Hub (Wink) with hue groups as well, so back then I just pulled out all the Hue groups and did all the grouping in HE. By the way welcome to the community!!! :slight_smile:

3

I was going to suggest "Refresh Group Discovery," but it sounds like you already tried that. Based on what I can see, it appears Hubitat is using the Hue-assigned group ID when it fetches these from the Bridge, so I'd assume the fact that the name matches is just incidental at that point, but I'm not sure what else it might do with this information (have you verified that a group with a new name also discovers if this one won't?).

If you just want a quick solution to the problem, you could add an arbitrary group and then modify its "Device Network ID" (on the device page) to match your actual group. The DNI is in the format "hueGroup:123/4", where the "4" in this is example is the Hue-assigned ID of this group, Unfortunately, I don't know of any easy way to get the group ID unless you are familiar with the Hue API (the /debug/clip.html interface would be one way)--the app can show you bulb IDs, but I don't see group IDs anywhere. If nothing else, I suppose you could guess until you got it right. :slight_smile: (Manually creating a HueBridgeGroup device without using the Hue Bridge Integration app won't work, BTW--it has to be created by the app, which establishes a parent/child relationship between the app and device, which this needs to work correctly.)

(I'll resist the urge to mention a custom Hue Bridge integration I wrote, but I can tell you that if you used that and it didn't work, I'd be willing to troubleshoot. :laughing: )