Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best practice for adding more than one Hue Bridge to the plugin? #37

Closed
leoneleone opened this issue Jan 4, 2017 · 18 comments
Closed
Labels

Comments

@leoneleone
Copy link

Hi,

I'm just wondering if anyone has added more than one Hue Bridge to their config.json file. I have three I want to add, but I'm trying to avoid having to reset my homekit configuration or deleting homebridge if anything goes wrong.

Any advice or pitfalls to look out for, or indeed a working process for adding more than one Hue Bridge via this plugin?
Your help is much appreciated.

@ebaauw
Copy link
Owner

ebaauw commented Jan 4, 2017

Hi @leoneleone , homebridge-hue should discover and connect to multiple bridges automatically, once they've registered themselves at the meethue portal. You can only specify a single bridge in config.json using the host parameter. You need to press the linkbutton on each bridge and add each username to config.json.
I've run homebridge-hue with also my old v1 bridge connected to my home network, in addition to my v2 bridge without any problems. I haven't tried more than two bridges, but that should work. Be aware of the HomeKit limit of 99 accessories per HomeKit bridge (i.e. homebridge instance), though, see Caveats in the README.
Your concern about having to reset HomeKit or remove/repair homebridge, losing your HomeKit setup, is very real, unfortunately. To minimise that risk, I create a second home in HomeKit for testing and use a different homebridge instance. See README: you can run that different instance on the same machine. Using multiple homebridge instances is also the only workaround for the 99 bridged accessories limit, afaik.

@ebaauw ebaauw added the question label Jan 4, 2017
@leoneleone
Copy link
Author

@ebaauw
Thanks for the info. I only plan on adding my Hue Motion sensors and not the lights, so I'll be safely under the 99device limit.
Good point about creating a new Home just for testing. Totally didn't think of that but it seems so obvious now 🙂 👍🏼

@leoneleone
Copy link
Author

@ebaauw
So I got this working with my 3 Hue Bridges without any problem.
Regarding the Hue Sensors: is there any way to expose only the Hue Motion Sensors without having the Hue Taps appear in HomeKit? I don't really have any use for the Other Hue sensor types and only want to see the Hue Motion Sensor in my HomeKit configuration (Home app)

@leoneleone
Copy link
Author

@ebaauw
It would be great if one can specify which Hue Sensor types (Motion, Tap, Dimmer) to include and which to exclude

@ebaauw
Copy link
Owner

ebaauw commented Jan 8, 2017

@leoneleone , yes it would - please see issue #7 and let me know your thoughts there.

@ebaauw ebaauw closed this as completed Jan 8, 2017
@rickdhoy
Copy link

rickdhoy commented Dec 3, 2022

Hi, I am trying to add a second Hue bridge to my Homekit and experiencing issues.

Firstly I want to reiterate my thanks for all he work you have done over the years on this plugin and I have personally been using it nearly since its inception.

Although I am not that technically adept I have managed to set up my home using it and other platform to get a house which is relatively stable.

I have now gone over the hard limit that the Hue Bridge offers of 62 devices and I am trying to add a second hub as I said before and experiencing issues.

I add the second Hue Bridge to the homebridge-Hue plugin and all the devices in Apple Homekit stop responding.

If I delete the configuration and restart the server they all start working again.

Config I am using is as follows:

{
"name": "Hue",
"anyOn": true,
"effects": true,
"heartrate": 2,
"hosts": [
"192.168.1.45",
"192.168.1.70"
],
"lights": true,
"nativeHomeKitLights": true,
"nativeHomeKitSensors": false,
"resource": true,
"sensors": true,
"users": {
"ECB5FAFFFE0245E7": "FPYxb9S5ewcTijAFFnsxjHyfe0k2Kbl9jDPtKIMo",
"001788FFFEA9A46E": "1ymAr5baFsm3DT5CEPBQGjvGTW-lv59m8I-eT1fC"
},
"wallSwitch": false,
"platform": "Hue"
}

Further information:

Homebridge Hue version: 0.13.49
Homebridge UI: 4.50.2
Node version: 18.12.1
homebridge v1.6.0

Moving forward I have tried to understand your information at: #1070 but I am unsure of what this will do to my setup moving forwarding what steps I should be taking.

I would appreciate any assistance you can give.

Thank you.

@rickdhoy
Copy link

rickdhoy commented Dec 3, 2022

Sorry please see log attached.
homebridge.log.txt

@ebaauw
Copy link
Owner

ebaauw commented Dec 4, 2022

Best open a new issue, rather that resurrecting one that’s been closed for almost 6 years.

I see a few weird things in your log file, but not related to your issue:

  • You’ve named both bridges the same, which makes it hard to distinguish them;
  • The builtin Daylight sensor on the second bridge hasn’t been configured;
  • I see a lot of devices marked reachable false by the first Hue bridge. Could simply be that the bridge doesn’t play nice with non-Hue devices; could also indicate an issue with radio interference. Are you running the second bridge on a different Zigbee channel?

I add the second Hue Bridge to the homebridge-Hue plugin and all the devices in Apple Homekit stop responding.

What do you mean by “all devices”? Those exposed by Homebridge Hue? By other plugins? Native devices?

What do you mean by “stop responding”? Do the tiles show No Response? Do they change in HomeKit, but not in real-life? Does HomeKit reflect the state when a sensor changes or when you control a light from the Hue app?

Did you try different Apple devices? Different HomeKit apps?

@rickdhoy
Copy link

rickdhoy commented Dec 4, 2022 via email

@ebaauw
Copy link
Owner

ebaauw commented Dec 4, 2022

I don't think this is related to Homebridge Hue. Instead it's just the regular blues of HomeKit not liking configuration changes. As you can still control the accessories from the Homebridge UI, Homebridge itself and the plugins are working properly. The issue is between Homebridge and HomeKit on your Apple devices.

Best try and power-cycle your home hub. If you have an Apple TV, make sure that's the active home hub, by powering down your HomePods. Make sure all your apple devices, incl. the home hubs are on the latest OS version. And be patient: especially on larger homes, it might take a couple of minutes for configuration changes to propagate over iCloud to all your Apple devices.

@rickdhoy
Copy link

rickdhoy commented Dec 6, 2022 via email

@ebaauw
Copy link
Owner

ebaauw commented Dec 6, 2022

Could you please capture and attach the debug log file and also attach the debug dump file (when configured for the two bridges)? See the Wiki how to obtain these. Please make sure to run Homebridge in DEBUG mode.

In theory it’s possible that HomeKit blocks Homebridge for non-compliance (e.g. exposing a Lightbulb without the On characteristic), but I’ve never seen that issue with Homebridge Hue. Did you try and run Homebridge Hue in a child bridge, or separate Homebridge instance?

@ebaauw ebaauw reopened this Dec 6, 2022
@rickdhoy
Copy link

rickdhoy commented Dec 6, 2022 via email

@rickdhoy
Copy link

rickdhoy commented Dec 8, 2022 via email

@rickdhoy
Copy link

rickdhoy commented Dec 8, 2022 via email

@ebaauw
Copy link
Owner

ebaauw commented Dec 9, 2022

Please find attached what I hope you have been looking for

Please attach, do not copy/paste large amounts of log output.
I need the DEBUG log from when Homebridge starts - this is where Homebridge Hue logs what resources it found and how it exposes them. Also, I need the debug dump file.

The Daylight sensor is a sensors resource on the Hue bridge (typically /sensors/1). I think the Hue app configures it based on your current location, but then the Hue app needs to have permissions to access that. If not, you can configure it manually through the Hue API.

@rickdhoy
Copy link

rickdhoy commented Dec 9, 2022 via email

@ebaauw ebaauw closed this as completed Dec 10, 2022
@rickdhoy
Copy link

rickdhoy commented Dec 14, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants