node-red-contrib-homekit-bridged: [Bug]: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: undefined
Describe the bug Difficult to reproduce, I have it currently.
I have had this running successfully for a long time, then (all of a sudden, no changes, yeah- I know) and I was getting “no response”, I removed the bridge from home.app but now cannot re-add the bridge, it doesn’t appear in the home.app at all
To Reproduce not sure
Desktop (please complete the following information):
- OS: Rpi
- Node version: v12.19.0
- NPM version: 6.14.8
- NodeRed version: v1.1.3
- NRCHKB Plugin Version: 1.2.0
Additional context running debug
DEBUG=NRCHKB*,HAP-NodeJS*,Accessory,HAPServer,EventedHTTPServer node-red
I get a lot of these first in the debug output:
NRCHKB:HAPServiceNode Starting Parent Service Pool 1 +6ms
NRCHKB:AccessoryUtils Looking for accessory with service subtype '172f1edd-389b-4c45-96d4-47e37a130118'... +0ms
NRCHKB:AccessoryUtils ... didn't find it. Adding new accessory with name 'Pool 1' and UUID '1316cdc7-e142-4a55-9a93-fea8fce35aa5' +0ms
NRCHKB:HAPServiceNode Starting Parent Service Pool 2 +6ms
NRCHKB:AccessoryUtils Looking for accessory with service subtype 'fd02bca6-d5c5-4777-9d45-73cea71e4b6d'... +0ms
NRCHKB:AccessoryUtils ... didn't find it. Adding new accessory with name 'Pool 2' and UUID '4a78594b-60fa-470d-a192-cb14e75910e6' +1ms
Then a lot of these:
(node:30289) UnhandledPromiseRejectionWarning: Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: undefined
at Bridge.Accessory._this.addBridgedAccessory (/home/pi/.node-red/node_modules/hap-nodejs/dist/lib/Accessory.js:286:27)
at Bridge.Accessory._this.addBridgedAccessories (/home/pi/.node-red/node_modules/hap-nodejs/dist/lib/Accessory.js:311:23)
at Object.getOrCreate (/home/pi/.node-red/node_modules/node-red-contrib-homekit-bridged/build/lib/utils/AccessoryUtils.js:80:20)
at configure (/home/pi/.node-red/node_modules/node-red-contrib-homekit-bridged/build/lib/HAPServiceNode.js:118:40)
at preInit.init (/home/pi/.node-red/node_modules/node-red-contrib-homekit-bridged/build/lib/HAPServiceNode.js:38:13)
at /home/pi/.node-red/node_modules/node-red-contrib-homekit-bridged/build/lib/HAPServiceNode.js:28:18
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:30289) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 21)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 22 (10 by maintainers)
Oh sorry, sure. I haven’t tested, but if there are any issues with it, we just raise another ticket.
On Sun, 28 Mar 2021 at 8:23 am, Tadeusz Wyrzykowski < @.***> wrote: