SphtKr / homebridge-zway

Homebridge plugin for (better) HomeKit support of RaZBerry and Z-Way Server
ISC License
85 stars 38 forks source link

Homebridge hangs when initializing Zway Server accessory. #123

Closed zama36 closed 6 years ago

zama36 commented 6 years ago

Running Homebridge on a Raspberry Pi with nodejs v8.11.3.

It seems like homebridge is hanging during the device initialization phase. The last device to be registered is #35. There is no device #36, 37 because I could never get a full interview on the First Alert ZCombo alarms. #38 is a door sensor which is just like the others that did register. I changed the tag to Homebridge.skip to see if there was something funky about it but no luck.

You can see in the log the server sees device 38 during the loading but it never initializes it.

20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Got grouped device ZWayVDev_34-0 consisting of devices: Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer ZWayVDev_zway_34-0-48-1 - sensorBinary.General purpose Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Got grouped device ZWayVDev_35-0 consisting of devices: Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer ZWayVDev_zway_35-0-48-1 - sensorBinary.General purpose Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Got grouped device ZWayVDev_38-0 consisting of devices: Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer ZWayVDev_zway_38-0-48-1 - sensorBinary.General purpose . . . Jun 20 20:33:43 raZberrypi homebridge[1297]: [2018-6-20 20:33:43] [ZWayServer] Initializing platform accessory 'South Window'... Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_34-0-48-1" Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Configured Characteristic "Contact Sensor State" for vdev "ZWayVDev_zway_34-0-48-1" Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Found and configured Service "ContactSensor" for vdev "ZWayVDev_zway_34-0-48-1" with typeKey "sensorBinary.General purpose" Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Loaded services for South Window Jun 20 20:33:43 raZberrypi homebridge[1297]: [2018-6-20 20:33:43] [ZWayServer] Initializing platform accessory 'East Window'... Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_35-0-48-1" Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Configured Characteristic "Contact Sensor State" for vdev "ZWayVDev_zway_35-0-48-1" Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Found and configured Service "ContactSensor" for vdev "ZWayVDev_zway_35-0-48-1" with typeKey "sensorBinary.General purpose" Jun 20 20:33:43 raZberrypi homebridge[1297]: Thu, 21 Jun 2018 03:33:43 GMT ZWayServer Loaded services for East Window pi@raZberrypi:~ $

Can't pull the accessories since HAP isn't being advertised.

zama36 commented 6 years ago

This issue is a duplicate of Issue #112. I had two contact sensors named "East Window" in two different rooms.