Motion Sensor (Multi-Sensor) FGMS001 & Homebridge about homebridge-zway HOT 8 CLOSED

Almost certainly a duplicate of #57. Fixes for this class of issues are already done and merged, I'm trying to fix one more issue before making a beta release.

from homebridge-zway.

Fine, I'm happy, but what is no beta release?

from homebridge-zway.

It's out now, do npm upgrade -g homebridge-zway (or npm install -g [email protected] if you're not on the pre-release channel) and see if it fixes your problem (it became a release candidate instead of a beta).

from homebridge-zway.

Set update (sudo npm install -g [email protected]), homebridge start his sensor appeared, everything is OK. But the latter option (charging) is not displayed correctly, which is correct?

from homebridge-zway.

Yet I found a mistake in the file /var/log/homebridge.err:

Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Adding Characteristic "Name" failed with message "Cannot add a Characteristic with the same UUID as another Characteristic in this Service: 00000023-0000-1000-8000-0026BB765291". This may be expected.

Full 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
Fri, 11 Nov 2016 19:11:15 GMT ZWayServer Fetching Z-Way devices...
Fri, 11 Nov 2016 19:11:16 GMT ZWayServer Authenticating...
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Authenticated. Resubmitting original request...
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Got grouped device BatteryPolling_7 consisting of devices:
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer BatteryPolling_7 - battery.Battery
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer WARN: Didn't find suitable device class!
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Got grouped device ZWayVDev_8-0 consisting of devices:
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer ZWayVDev_zway_8-0-48-1 - sensorBinary.General purpose
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer ZWayVDev_zway_8-0-49-1 - sensorMultilevel.Temperature
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer ZWayVDev_zway_8-0-49-3 - sensorMultilevel.Luminiscence
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer ZWayVDev_zway_8-0-128 - battery.Battery
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Got grouped device ZWayVDev_9-0 consisting of devices:
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer ZWayVDev_zway_9-0-37 - switchBinary
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer ZWayVDev_zway_9-0-38 - switchMultilevel
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_8-0-48-1"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Contact Sensor State" for vdev "ZWayVDev_zway_8-0-48-1"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_8-0-128"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Adding Characteristic "Name" failed with message "Cannot add a Characteristic with the same UUID as another Characteristic in this Service: 00000023-0000-1000-8000-0026BB765291". This may be expected.
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Found and configured Service "ContactSensor" for vdev "ZWayVDev_zway_8-0-48-1" with typeKey "sensorBinary.General purpose"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_8-0-128"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Battery Level" for vdev "ZWayVDev_zway_8-0-128"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Charging State" for vdev "ZWayVDev_zway_8-0-128"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Configured Characteristic "Status Low Battery" for vdev "ZWayVDev_zway_8-0-128"
Fri, 11 Nov 2016 19:11:17 GMT ZWayServer Found and configured Service "BatteryService" for vdev "ZWayVDev_zway_8-0-128" with typeKey "battery.Battery"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_8-0-49-1"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Current Temperature" for vdev "ZWayVDev_zway_8-0-49-1"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Found and configured Service "TemperatureSensor" for vdev "ZWayVDev_zway_8-0-49-1" with typeKey "sensorMultilevel.Temperature"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_8-0-49-3"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Current Ambient Light Level" for vdev "ZWayVDev_zway_8-0-49-3"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Found and configured Service "LightSensor" for vdev "ZWayVDev_zway_8-0-49-3" with typeKey "sensorMultilevel.Luminiscence"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Loaded services for Fibaro PIR (8.0.48.1)
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Name" for vdev "ZWayVDev_zway_9-0-38"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Current Position" for vdev "ZWayVDev_zway_9-0-38"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Target Position" for vdev "ZWayVDev_zway_9-0-38"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Position State" for vdev "ZWayVDev_zway_9-0-38"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Configured Characteristic "Hold Position" for vdev "ZWayVDev_zway_9-0-38"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Found and configured Service "WindowCovering" for vdev "ZWayVDev_zway_9-0-38" with typeKey "switchMultilevel.blind"
Fri, 11 Nov 2016 19:11:18 GMT ZWayServer Loaded services for Fibaro Blind (9.0)
Fri, 11 Nov 2016 19:11:18 GMT EventedHTTPServer Server listening on port 51826
Fri, 11 Nov 2016 19:11:20 GMT EventedHTTPServer [::ffff:192.168.10.11] New connection from client
Fri, 11 Nov 2016 19:11:20 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP server listening on port 40656
Fri, 11 Nov 2016 19:11:20 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP request: /pair-verify
Fri, 11 Nov 2016 19:11:20 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify
Fri, 11 Nov 2016 19:11:20 GMT HAPServer [CC:22:3D:E3:CE:30] Pair verify step 1/2
Fri, 11 Nov 2016 19:11:20 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP Response is finished
Fri, 11 Nov 2016 19:11:20 GMT EventedHTTPServer [::ffff:192.168.10.10] New connection from client
Fri, 11 Nov 2016 19:11:20 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP server listening on port 40245
Fri, 11 Nov 2016 19:11:21 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP request: /pair-verify
Fri, 11 Nov 2016 19:11:21 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify
Fri, 11 Nov 2016 19:11:21 GMT HAPServer [CC:22:3D:E3:CE:30] Pair verify step 2/2
Fri, 11 Nov 2016 19:11:21 GMT HAPServer [CC:22:3D:E3:CE:30] Client 54EBDA2C-BBA2-438B-ACF8-38E4283CA54A verification complete
Fri, 11 Nov 2016 19:11:21 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP Response is finished
Fri, 11 Nov 2016 19:11:21 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP request: /pair-verify
Fri, 11 Nov 2016 19:11:21 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify
Fri, 11 Nov 2016 19:11:21 GMT HAPServer [CC:22:3D:E3:CE:30] Pair verify step 1/2
Fri, 11 Nov 2016 19:11:21 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP Response is finished
Fri, 11 Nov 2016 19:11:21 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP request: /accessories
Fri, 11 Nov 2016 19:11:21 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /accessories
Fri, 11 Nov 2016 19:11:21 GMT EventedHTTPServer [::ffff:192.168.10.11] HTTP Response is finished
Fri, 11 Nov 2016 19:11:23 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP request: /pair-verify
Fri, 11 Nov 2016 19:11:23 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify
Fri, 11 Nov 2016 19:11:23 GMT HAPServer [CC:22:3D:E3:CE:30] Pair verify step 2/2
Fri, 11 Nov 2016 19:11:23 GMT HAPServer [CC:22:3D:E3:CE:30] Client 54EBDA2C-BBA2-438B-ACF8-38E4283CA54A verification complete
Fri, 11 Nov 2016 19:11:23 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP Response is finished
Fri, 11 Nov 2016 19:11:23 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP request: /accessories
Fri, 11 Nov 2016 19:11:23 GMT HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /accessories
Fri, 11 Nov 2016 19:11:23 GMT EventedHTTPServer [::ffff:192.168.10.10] HTTP Response is finished

from homebridge-zway.

Okay, both of those are expected.

The HomeKit spec requires anything with a battery to also include a charging characteristic, so I include one but it's always false. The Fibaro motion sensor can't charge its battery, right? (Mine can't). Some of the Aeon Labs multi-sensors actually can run off a USB line, so I'll have to look at that for them, but I don't have one to test. Anyway, charging = No is correct.

The message you noticed, "Adding Characteristic "Name" failed ... This may be expected." is okay. In some combinations of devices this happens, and it was difficult to prevent it, so I just ignore the second "name" that it tries to set. The names are mostly a convenience anyway, you can rename all the devices in HomeKit if they're not right. In any case, as long as your device(s) are showing up as expected, you can ignore that message.

from homebridge-zway.

Also, you'll probably want to add a tag (in Z-Way) to the motion sensor device so that Homebridge knows what it really is--right now it's showing it as a contact sensor. See the documentation for more info.

from homebridge-zway.

I think the original issue here is fixed, and the other issues resolved...closing, reopen if needed.

from homebridge-zway.