Cannot add a bridged Accessory with the same UUID as another bridged Accessory about homebridge-homeassistant HOT 10 CLOSED

looking at your logs it seems that all your z-wave switches have the same friendly name (display name). home assistant might given them a different id by appending numbers but friendly name is the one used by siri to recognise your switch and have to be unique. (UUID is generated using the name not ID that's why you are having this problem)

you could try to assign friendly_name / homebridge_name in the home assistant's customisation config.

e.g.

homeassistant:
   customize:
    switch.living_room:
      homebridge_name: 'Living Room Floor Light'
    switch.living_room_2:
      homebridge_name: 'Living Room Downlight'

Restart homebridge and it should pick it up.

from homebridge-homeassistant.

Nobody has an idea about this?

from homebridge-homeassistant.

Apparently the dev doesn't have more than 1 z-wave device of any particular type, or maybe he has no z-wave devices at all, so maybe he isn't able to test and realize the problem. I have 8 Aeotec z-wave switches, all with the exact same name other than the z-wave node id as well as 3 Everspring switches, again, all with the same names other than the node id.

It looks like this is most likely a problem with HomeBridge itself in the hap-nodejs module. It looks like it is dropping the node number off the backend of the device name causing the following:

These 2 devices:
switch.everspring_an157_plugin_appliance_module_switch_17
switch.everspring_an157_plugin_appliance_module_switch_37

are both seen as:

'Everspring AN157 Plug-in Appliance Module Switch'

So it is using that as the UUID and seeing them as duplicate names.

I've had to bypass using direct linking to my Home Assistant devices and instead I am foregoing this plug-in and instead I setup a copy of HA Bridge (a software virtual hue bridge) and used that with the hue bridge plugin of Home Bridge so that I can set my own names of the devices and simply call the Home Assistant api to turn them on and off. It is the only way I am able to control my Home Assistant devices through Siri as HomeBridge will never work correctly with this plugin-in unless the plug-in author can find a way of naming them so that HomeBridge doesn't whine about duplicate UUIDs

from homebridge-homeassistant.

I don't have this issue. I have 4 of the exact same model Linear switches on my Z-Wave network. @maddox can you weigh in?

from homebridge-homeassistant.

To me it seemed as the device names get truncated maybe?

from homebridge-homeassistant.

I don't have multiple z-wave devices of the same type, and I'd have to look up how the UUIDs are being generated 😝

from homebridge-homeassistant.

I was having this same problem because I had several friendly names that were the same (didn't matter in Home Assistant UI). Setting unique homebridge_name params for them worked.

from homebridge-homeassistant.

Closed via #54

from homebridge-homeassistant.

I'm having an issue with wink2 plugin with invalid UUID. I'm running this on raspberry Pi3.
Below is my config file and log

{
"bridge": {
"name": "Homebridge",
"username": “ab:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [
{
"platform": "Wink2",
"name": "Wink2",
"username": “[email protected]",
"password": “xyzzy”,
"client_id": “xxxxxxx”,
"client_secret": “xxxxxxx”,
"hide_groups": ["garage_door", "thermostat"],
"hide_ids": [],
"fan_ids": []
}
]
}

LOG

*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
[6/11/2017, 12:59:57 PM] Loaded plugin: homebridge-liftmaster2
[6/11/2017, 12:59:57 PM] Registering platform 'homebridge-liftmaster2.LiftMaster2'
[6/11/2017, 12:59:57 PM] ---
[6/11/2017, 12:59:58 PM] Loaded plugin: homebridge-nest
[6/11/2017, 12:59:58 PM] Registering platform 'homebridge-nest.Nest'
[6/11/2017, 12:59:58 PM] ---
[6/11/2017, 1:00:00 PM] Loaded plugin: homebridge-wink2
[6/11/2017, 1:00:00 PM] Registering platform 'homebridge-wink2.Wink2'
[6/11/2017, 1:00:00 PM] ---
[6/11/2017, 1:00:00 PM] Loaded config.json with 0 accessories and 1 platforms.
[6/11/2017, 1:00:00 PM] ---
[6/11/2017, 1:00:00 PM] Loading 1 platforms...
[6/11/2017, 1:00:00 PM] [Wink2] Initializing Wink2 platform...
[6/11/2017, 1:00:00 PM] [Wink2] Wink2 Init - Version 2.0.8
Load homebridge-liftmaster2.LiftMaster2
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

┌────────────┐     
│ 031-45-154 │     
└────────────┘     

[6/11/2017, 1:00:00 PM] [Wink2] Reclaiming: Akshar's Light - ID 297278 - TYPE binary_switch
[6/11/2017, 1:00:00 PM] [Wink2] Reclaiming: Akshar's Fan - ID 297279 - TYPE binary_switch
[6/11/2017, 1:00:00 PM] [Wink2] Reclaiming: Media Room - ID 299589 - TYPE binary_switch
[6/11/2017, 1:00:00 PM] [Wink2] Reclaiming: Media Room - ID 299590 - TYPE binary_switch
[6/11/2017, 1:00:00 PM] [Wink2] Reclaiming: Bottom Light Load - ID 470043 - TYPE binary_switch
[6/11/2017, 1:00:00 PM] [Wink2] Reclaiming: Top Light Load - ID 470044 - TYPE binary_switch
[6/11/2017, 1:00:00 PM] [Wink2] Direct Access NOT Enabled. Add direct_access:true to your config if you which to use direct access on Wink.
[6/11/2017, 1:00:00 PM] [homebridge-liftmaster2.LiftMaster2] Please setup MyQ login information!
[6/11/2017, 1:00:00 PM] Homebridge is running on port 51826.
[6/11/2017, 1:00:01 PM] [Wink2] Wink Authentication Successful.
/usr/local/lib/node_modules/homebridge/lib/platformAccessory.js:17
if (!uuid.isValid(UUID)) throw new Error("UUID '" + UUID + "' is not a valid UUID. Try using the provided 'generateUUID' function to create a valid UUID from any arbitrary string, like a serial number.");
^

Error: UUID '924f20c0-eb15-0131-e510-1e5449afed4e' is not a valid UUID. Try using the provided 'generateUUID' function to create a valid UUID from any arbitrary string, like a serial number.
at new PlatformAccessory (/usr/local/lib/node_modules/homebridge/lib/platformAccessory.js:17:34)
at Wink2.addAccessoryCharacteristics (/usr/local/lib/node_modules/homebridge-wink2/index.js:133:24)
at Wink2.addAccessory (/usr/local/lib/node_modules/homebridge-wink2/index.js:123:10)
at winkapiv2._deviceReceiptProcessor (/usr/local/lib/node_modules/homebridge-wink2/lib/winkapi.js:222:22)
at winkapiv2. (/usr/local/lib/node_modules/homebridge-wink2/lib/winkapi.js:119:28)
at ClientRequest. (/usr/local/lib/node_modules/homebridge-wink2/lib/winkapi.js:361:17)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:186:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

from homebridge-homeassistant.

I ran into this problem after adding a bunch of zwave devices to my collection at home. Adding homebridge_name: attribute to each exposed entity in Home Assistant fixed it. Thanks @javefang!

Here is what I have for each of the entity/item that I expose to both alexa using emulated_hue and Apple Home using homebridge in the customize section.

light.family_room:
  friendly_name: Family Room Lights
  emulated_hue: true
  emulated_hue_name: Family Room Lights
  homebridge_hidden: false
  homebridge_name: Family Room Lights

I wish the error messages are a bit more friendly. Hopefully this will help someone!

from homebridge-homeassistant.