-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Error "Cannot add a bridged Accessory with the same UUID" #217
Comments
The uniqueid is the ZigBee mac address followed by the ZigBee endpoint. The Pee lights above should be exposed as a single accessory, with multiple Lightbulb services. See my homebridge-hue plugin. |
I am using the homebridge-hue plugin :) The error I'm getting is:
|
Sorry, my bad.
Service, not Accessory. This is unrelated to #4. The issue is that services of the same accessory need to be a different type or a different subtype. Currently, I only set the subtype for the dresden elektronik ballast. I want to set it regardless (see homebridge-hue/lib/HueLight.js Line 318 in 7252e40
I’m currently traveling, but if you uncomment the above line, it should work. When I return, I can add the logic for the Pee lights, adding them to the list of known lights as well. What ranges of colour and colour temperature do they support? Do you connect them using a Hue bridge? What bridge firmware? |
Yes, I'm connecting them through the Hue bridge -- latest firmware. The Pee lights are not really lights per-se. It's a custom firmware (with a custom vendor id and a custom device id) for Depending on which firmware you flash on the chip, it supports a different number of light endpoints. I could change the manufacturer and model id to whatever I want, but most people that do this will use the existing firmware created by Peter Visser (which has the manufacturer id He created 5 firmware versions for dimmable lights (no color temperature selection), with 1 through 5 endpoints and 9 firmware versions for RGB lights (1 through 4 endpoints, inverted [common anode] and regular [common cathode] plus one original version for a single common anode RGB endpoint). So, in total, he created 14 different versions of firmware that expose a different amount of light endpoints with different capabilities (RGB and regular dimmable). You can differentiate by the Philips Hue service type ( Personally, I'm using the one with 4 dimmable non-RGB endpoints (which is why you see 4 endpoints in the |
Thanks for pointing me in the right direction! I added the subtype conditionally: if (this.obj.modelid === "PeeVeeOne") {
this.config.subtype = this.obj.uniqueid.split('-')[1];
} That seems to work fine for now! I do get some warnings, but that is to be expected!
|
I made a PR: #218 |
Odd, I haven’t seen this version nor
Thanks, I’ll have a look when I’ll be back. |
Well🙈 You should not see this version in the wild yet! |
Thanks for accepting the PR. Once you release |
Did some more testing. HomeKit still recognises the same Accessory (so room assignment remains intact), but sees a different Service (so scene and automation assignments are lost). This change will have to wait for the next major release. For now, v0.5.46 adds the subtype to the |
Thank you! Works perfectly! |
I have almost the same issue as #14
I'm building some Hue-compatible lights myself (they work perfectly) but the Philips bridge only makes Philips-lights compatible with Homekit. Everything else is not synced to Apple Home.
Unfortunately, Homebridge fails with the "Cannot add a bridged Accessory with the same UUID" error on my custom lights.
Here is the full list of my lights:
Since #4 is still open, could you please add an exception for lights with the
PeeVeeOne
model id? ThePeeVeeOne
firmware is for NXP chips and is open-source, so I'm sure more people will use it in the future!The text was updated successfully, but these errors were encountered: