All,
I just updated my hue bridge pro, and my entire hue network (85 devices and lights) went unresponsive after the update. I thought it would be safe.... it wasn't. I went through all the troubleshooting steps with their support and now they are advising me to factory reset the entire network and the bridge and start from scratch....
@bobbyD is there an easy way to swap out devices from the native hue integration like there is for zigbee and z-wave? I remember swapping child devices for other child devices was an issue in the past
rebuilding 5 years worth of automations today is my nightmare
I read something yesterday about this. I think it has something to do with recent Apple updates. What I read was that theres no way around relinking Hue Bridge Pro to Apple Home via matter and setting it all up again....
Still not possible, AFAIK.
i dont use the the apple home -> hue integration. i run everything from hue-> Hubitat->apple home
2 Likes
Most child devices still can't be swapped, owing to the relationship they have with the parent app or device; platform 2.4.4. introduced a few exceptions where the parent app is basically just there to facilitate adding the devices but doesn't really have any role in operation. Unfortunately, Hue devices do not work like that, as the parent app is an important part of its operation.
That being said, if you can convince your current Hue integration app that it's your "new" bridge after you get that set up (and that should be possible -- just use the options in the app to either select a new bridge or reauthenticate), you can probably make things work by adding the devices and swapping the "old" DNI for the "new" DNI for each device. You'll still need to do that much, but as long as the "new" DNI ends up on the existing device, the integration should think they're the same, and you'll just have to do this on the child devices of the integration app and not have to touch every single app you use the device in on your hub. Sort of a manual swap for each device. That being said, the latter is definitely the safer option -- I just know the former should at least work for everything I can think of. 
3 Likes
Damn.. alright, heres to an entire day of resetting bulbs and and even more time individually fixing automations and rules. I fell like theres a lesson in chasing updates here for me
IS there a smarter way to get after this? so if it happens in the future im not so screwed? use the native groups app to make groups that have the child hue devices in them? some elvel of abstraction so i dont have to rebuild rules and automations in the future?
I don't think so. I'm not sure I'd go through a level of abstraction on Hubitat just to avoid this in the future. It's pretty unlikely (sorry to hear of the Hue Bridge troubles, though!) and the time you'd spend doing one seems about the same as the time you'd spend doing the other, with the disadvantage of making things more complex on the hub -- but that's just my opinion.
The DNI trick I mentioned above should work if you don't want to do manual swaps, though. May be some quirks afterwards, but I can't think offhand what they'd be.
Got it, thats fair enough. Looks like my bridge is shot in some way. even after factory resetting it, it cant find any lights. so im in it to win it with uncontrollable bulbs throughout the house until a new bridge can get here.
