[RELEASE] CoCoHue: Hue Bridge Integration (including scenes!)

Thanks! I’m going to try to migrate this weekend. I’ve been with Cocohue since I started with Hubitat! I’d be sad to switch.

Is there anything the built in hue integration doesn’t have? I use scenes as switches extensively for holidays

No, I can't think of anything. There are actually more features, such as contact sensors and (as you know) MotionAware.

1 Like

Couple of days ago I went from CocoHue to built in Hue app and I have to say that Motionaware works really well and is really useful for home automation needs on Hubitat. Anyway thanks @bertabcd1234 for all the support with Cocohue. :heart:

4 Likes

How easy was it to switch? I envisage a traumatic few hours that results in nothing working anymore and my family banning me from the house :joy:

What are the actual steps to migrate?

You can run both at the same time if you wish. So you can take all the time you need with the migration without causing problems to the wifey. I added bridge to built in app. Then went through all my webcore pistons and changed those to use bulbs from new integration. Then removed cocohue. Next day opened hubitat log to see if there is errors or missing devices in wc pistons. Everything was good.

2 Likes

Thanks. I took the plunge - chose a time when everyone was in bed, which was a risky move as there was always the chance that room lighting would randomly blast the lights on when updating something :rofl:

It took me nearly 3 hours, but I emerged unscathed. I think everything is switched over and still working - pray for me over the next few days :face_with_peeking_eye: :sweat_smile:

4 Likes

I'm on the edge of migrating to the built-in app.Right now my hue bulbs have a device type CoCoHue CT or RGBW. Will I need to change that after I select them in the built-in app. I see that there is a hue bridgebulb.... device type. Or should I change to that before migrating to the built-in.?

You shouldn’t have to change any of the automatically selected device drivers. Of course they’re going to be different drivers from the ones you are currently using with CocoHue, since the drivers are for child devices of the built-in Hue integration. You can’t just change the CoCoHue drivers for the built-in and expect them to work. You will have to create all new Hue devices and then replace the old devices with the new ones from the built-in integration.

2 Likes

i'm having a hard time with the order of operations. i have 100 lights and each is tied to approximately 4 different automations. i really don't want to manually change 400 automations. am i screwed?

Should i combine the bridges into the pro hub first? Then do the built in integration, then the devices?

or switch to the built in integration first? then ill have two apps, one for each old hub?