Hue Pro bridge warning

[DaveL17]

@davel17. Any thoughts on Home Assistant vs Indigo? Seems like it supports the devices I use (hue, cameras, etc) but while open source is cool I’m concerned about longevity and keeping up with the flood of IoT changes.

Not informed opinions to be honest. I've never used it.

[kw123]

just finished migration one of my four to hue bridge pro (one ethernet)

First every thing needed to be upgraded (lamps bridges ..) that took ~ 4 hours.
The the actual migration of the hues devices took about 30 minutes.
The std hue lamps and switches worked fine.

Issues:
A) friends of hue switch could not be migrated. The offered migration did not work. ( 1 hour)
1. delete in hue,
2. reset switch manually (press top left, then press and hold top right for 10 seconds, followed by pressing the top right and bottom left at the same time, and finish by pressing the top left again.)
3. add switch in hue app
4. reconfigure all buttons.

B) one 3rd party zigbee lamp (fancy ceiling lamp.. looks like stars) : There was an option to re-adopt the light, but that did not work (tried ~ 1 hour)
then
1. in hue app: delete
2. lamp had to be reset ( on for 10 secs, off/on quickly 4 times until blinking .. needed 4 tries)
3. in Hue app: added and reconfigure, and reconfigure dimmer switches

The next step is to add hue bridge pro to the plugin. I guess the first version will be > 1 week.
THE PLUGIN CURRENTLY DOES NOT SUPPORT HUE BRIDGE PRO

But I shall wait for the option to migrate additional bridges. I SHALL NOT manually migrate all the rest
And I have one bridge with four 3rd party lamps, eight friends of hue switches. .. that one will go last and I shall wait for at least the next bridge software update.

Karl

[kw123]

after some struggle I get the first data back from the hue pro bridge.

and it can return the data in the old format !!


curl -H 'hue-application-key:<key>' -X GET 'https://ip/ /clip/v2/light
returns the new format

vs the old http url:
curl https://ip//api/<key>/lights
returns old format

that makes the whole thing much easier at least for the time being to just get something from the new pro bridge

Karl
now time to go to bed

[kw123]

status update:

my new pro bridge is detected (manually) by plugin, adopted and I can set / read lights, groups

this was much easier than I thought. .
BUT NO NEW FUNTIONALITY YET.. just old functions and one bridge migrated.

needed to change in the plugin
1. https instead of http
2. add: to get.. .put... requests(..... , >> verify=False<< )
the new hue bridge wants https only but does not encrypt -> verify=False
you could add its own certificate to the hue bridge then verify=false would be verify = true

now I need to make the process "easy":
1. adoption is a little different
2. device from old bridge should just stay as they are - that works, but you have to follow a certain process: new bridge has to take the old bridge number(0-4)
must not be a different bridge number in the plugin.

anyone wants to test - in ~ 1-2 days ?

Karl

[jroach]

@kw123, I already migrated back to the old hub but I have a few other hubs: guest residence and landscaping. Landscaping has about 20 or so lights. I could migrate that hub to Hue Pro and then test the plug-in. Any special instructions or business as usual:)

[kw123]

See the other post how to migrate.


Sent from my iPhone using Tapatalk

[kw123]

viewtopic.php?t=28635

[kw123]

SUCCESS!!

could migrate two v2 bridges to one new hue pro bridge.

the second v2 bridge had only 2 dimmers and 2 lights, but it worked fine.

The dimmers and lights become new indigo devices. You can though migrate them in the menu to the old indigo devices.

steps:

1. open hue app.
2. go to setting / bridge, select bridge to be migrated and follow screen steps.
.. that will take some time .. and do NOT reset the old bridge yet
Dimmers will be migrated, but if you did not use the Phillips hue app the config does not migrate - I used "hue essentials" to configure the dimmers

3. in indigo hue plugin (there will be some error message complaining about old v2 bridge not reachable)
hue menu / move ...
fill out the from to and click <execute...> for each light sensor ..

4. Indigo hue menu config delete old v2 bridge (top) of config
5. now the hardware reset on the old bridge

Karl
ps 2 more bridges to go, but they have lots of devices and friends of hue switches that do not move so easily

[kw123]

I now have migrated 3 bridges to the pro bridge (47 lights 29 switches, 21 groups). One bridge left to go (19 lights, 23 switches)

it seems to work ok, but not everything is automatic.

1. non hue devices will not migrate, ie"Friends of Hue" and non Hue lights
2. devices (ie switches) that have been configured by other apps will loose their config
3. I got once an error message "Bridge is full", but ofter reboot that went away and I added several devices after that w/o problems

to do the migration:
a: setup new bridge, update all devices
b: correct any items you should have fixed for some time( ie names, make sure they are unique = do not appear on other bridges)
c: execute move as advised by hue. !!!do not reset old bridge yet!!!
d: in indigo
- add new bridge in config
- you should see all the devices that have been moved added (you now have 2 for each)
- use menu move device(s) to
= keep old device and overwrite old device with parameters from new device and delete new device
!!! first do a "Print device matches" to check if all devices are id-ed correctly!!! the do the "move all devices"
you could also move one after the other manually
Now reset the old bridge, and delete the old bridge in indigo / config

Karl