Problems adding Hue Bridge

[brekkjen]

Hi, I'm trying to add a Hue Bridge to HS4 but the plugin is saying "No New bridges found."
When I try to specify the IP of the bridge I get the same message.

In the logs I see this:
1.19.2021 22:08:07 JowiHue Debug Debug: (Bridgescan) :End search for bridges
1.19.2021 22:08:03 JowiHue Info UPNP-backdoor no valid response from IP in INI file, Please check IP seems to be bridge, but not a correct response (is bridge updated to latest level?)
1.19.2021 22:08:03 JowiHue Debug Debug: (BridgeCheckIP) :IP address 192.168.xxx.xxx not responding: Den eksterne serveren returnerte feilen (404) File not found.

I have contact with the bridge from the Hue app on my phone and can control the light from there without problems

JowiHue version: 4.0.3.8
HS4 Pro Edition 4.1.10.0 (Windows)

What should I try?

Thanks in advance

[brekkjen]

I did a reset of the Hue Bridge and was then able to add it to HS.....

[iiidmaxer]

Is the Hue Bridge part of deCONZ deployment? How did you reset it?

[w.vuyk]

The Philips Hue bridge is not a deCONZ gateway, but this plugin supports both.

[iiidmaxer]

I'm using the Conbee II. If I changed over to the Hue bridge, would I no longer need the deCONZ software/Phoscon gateway? From what I have read, people seem to recommend the Conbee over the hue bridge, any thoughts on which works better with your plugin?

[upstatemike]

I'm using the Conbee II. If I changed over to the Hue bridge, would I no longer need the deCONZ software/Phoscon gateway? From what I have read, people seem to recommend the Conbee over the hue bridge, any thoughts on which works better with your plugin?

How do people who only use Conbee update the firmware on their Hue bulbs?

[TC1]

How do people who only use Conbee update the firmware on their Hue bulbs?

I get out my Hue bridge once a year or so to check.

Rough procedure from memory, this is so you don't have to exclude the bulbs and reset your events, etc.....

1. Plugin your Hue Bridge, connect to it through the Hue app on your phone/tablet.
2. Let the bridge update it's own firmware, if necessary.
3. Pick the first bulb you want to update, you need to note its unique 6-character identifier on the side of the base of the bulb.
4. In the Hue app add bulb/device, but since the bulb is not in inclusion mode, you need to pick the option to input its serial number.
5. Hue app will find it and pull it into the Hue Bridge network (you're basically doing a Zigbee binding).
6. Let it sit, it takes time but the bridge will eventually pull down new firmware if the bulb/device needs it. You then choose to update the bulb.
7. After bulb is updated, use the Hue app to exclude the bulb from the bridge.
7. In JowiHue, use the Scan function to find new devices on network. It will find the bulb, but since it was never excluded from JowiHue/HS4/ConBee, the device will be right back in place it was before.

The only thing I would change about this method is that I was doing one bulb at a time, and it takes at least 30 minutes for steps 5 - 6. Next time I'm going to pull all the bulbs into the bridge and then try to do the firmware on all of them at the same time.

[upstatemike]

I get out my Hue bridge once a year or so to check.

Rough procedure from memory, this is so you don't have to exclude the bulbs and reset your events, etc.....

1. Plugin your Hue Bridge, connect to it through the Hue app on your phone/tablet.
2. Let the bridge update it's own firmware, if necessary.
3. Pick the first bulb you want to update, you need to note its unique 6-character identifier on the side of the base of the bulb.
4. In the Hue app add bulb/device, but since the bulb is not in inclusion mode, you need to pick the option to input its serial number.
5. Hue app will find it and pull it into the Hue Bridge network (you're basically doing a Zigbee binding).
6. Let it sit, it takes time but the bridge will eventually pull down new firmware if the bulb/device needs it. You then choose to update the bulb.
7. After bulb is updated, use the Hue app to exclude the bulb from the bridge.
7. In JowiHue, use the Scan function to find new devices on network. It will find the bulb, but since it was never excluded from JowiHue/HS4/ConBee, the device will be right back in place it was before.

The only thing I would change about this method is that I was doing one bulb at a time, and it takes at least 30 minutes for steps 5 - 6. Next time I'm going to pull all the bulbs into the bridge and then try to do the firmware on all of them at the same time.

OK so why is this easier than just using the bridge as the interface for Hue stuff and Conbee for non-Hue Zigbee?

[TC1]

OK so why is this easier than just using the bridge as the interface for Hue stuff and Conbee for non-Hue Zigbee?

It's personal preference, here are my reasons, YMMV:

• The Hue Bridge is it's own separate Zigbee network, so that means the Hue bulbs do act as repeaters/routers for all my other Zigbee device. I'd rather have one strong mesh/network for my Zigbee devices.
• As of today, the Hue Bridge integration is polled, HS4 only knows something changed based on polling. The Conbee controller and deconz software/api use a webhook, so all device status changes are real-time.

That being be said, the new Hue Bridge API will add webhook/push notifications, at that point I will strongly consider moving my bulbs back to the bridge. But that's probably not going to be ready for at least an 6 - 12 months.

[upstatemike]

It's personal preference, here are my reasons, YMMV:

• The Hue Bridge is it's own separate Zigbee network, so that means the Hue bulbs do act as repeaters/routers for all my other Zigbee device. I'd rather have one strong mesh/network for my Zigbee devices.
• As of today, the Hue Bridge integration is polled, HS4 only knows something changed based on polling. The Conbee controller and deconz software/api use a webhook, so all device status changes are real-time.

That being be said, the new Hue Bridge API will add webhook/push notifications, at that point I will strongly consider moving my bulbs back to the bridge. But that's probably not going to be ready for at least an 6 - 12 months.

Makes sense. I just don't like radio usb dongles that attach direct to Homeseer in the basement server room as it is a major effort to build out a the mesh from there to the first device I actually want to control, I wish there was a network version of the Conbee similiar to the Hue Bridge (Not the Rasbee that requires a Ras Pi, enclosre, etc, etc) Maybe the new API will allow more Zigbee devices to use the Hue Bridge as an interface.

[TC1]

Makes sense. I just don't like radio usb dongles that attach direct to Homeseer in the basement server room as it is a major effort to build out a the mesh from there to the first device I actually want to control, I wish there was a network version of the Conbee similiar to the Hue Bridge (Not the Rasbee that requires a Ras Pi, enclosre, etc, etc) Maybe the new API will allow more Zigbee devices to use the Hue Bridge as an interface.

Not sure why you're against the RaspBee? It's just like a Zigbee version of the HS Z-Net. It's a piece of cake to setup and Dreseden makes a complete bootable image for an SD card to get the RaspBee going.

The new Hue API is strictly for the application interface and has nothing to do with device support (AFAIK). If you think about it, Philips Hue have their own ecosystem of Zigbee devices and there's no financial incentive for them to be more inclusive of devices that might compete with their own brand. Hence why they have their "Friends of Hue" business program which allows them to lock down and control their ecosystem.

[upstatemike]

Not sure why you're against the RaspBee? It's just like a Zigbee version of the HS Z-Net. It's a piece of cake to setup and Dreseden makes a complete bootable image for an SD card to get the RaspBee going.

Maybe but it seems like a lot of time and fiddling. I didn't set up Home Assistant until I could buy a litttle plug and play blue box. I just prefer to focus my time on cool automation events and minimize any time or effort spent on controllers and infrastructure. I like intuitive stuff. If you actually have to read the directions I will likely never find time for it.