I’m just starting to dabble in Zwave devices, and I’ve successfully connected several different devices to my openhab (native install, linux, recent upgrade to 2.5.4-snapshot). There’s quite a lot I still don’t understand, so it’s hard for me to tell whether the problems I have with an aeotec recessed door sensor 7 (ZW187) are me or the binding. Here’s what I do know after my testing, self-education, and forum searching:
-
ZW187 was added to the (very awesome!) zwave database only recently but the binding has updated since then and recognizes the device. The device is s2 compliant but my controller is not (Aeotec Gen 5) and I’ve included it in my network via Habmin’s interface. I take the fact that it is recognized by openhab as evidence that the device is properly and fully added to my network.
-
Battery level channel does work.
-
None of the other channels receive any data from the device (Binary sensor, Alarm (system, access, power)).
Number Sensor_MF_K_MudroomDoorBat "Mudroom Door [%.1f%%]" <batterylevel> (ZW_Battery) {channel="zwave:device:5368c88b:node18:battery-level"}
Switch Sensor_MF_K_MudroomDoorSB "Mudroom Door [%s]" <door> {channel="zwave:device:5368c88b:node18:sensor_binary"}
Switch Sensor_MF_K_MudroomDoorAS "Mudroom Door [%s]" <door> {channel="zwave:device:5368c88b:node18:alarm_system"}
Switch Sensor_MF_K_MudroomDoorAA "Mudroom Door [%s]" <door> {channel="zwave:device:5368c88b:node18:alarm_access"}
Switch Sensor_MF_K_MudroomDoorAP "Mudroom Door [%s]" <door> {channel="zwave:device:5368c88b:node18:alarm_power"}
Here’s what I suspect (not yet knowledgeable enough to be sure): Alarm command class is not the correct database configuration. On triggering the sensor, the debug log reports that the alarm system and alarm access channels are not implemented.
2020-04-07 21:45:39.867 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Application Command Request (ALIVE:DONE)
2020-04-07 21:45:39.868 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 18: resetResendCount initComplete=true isDead=false
2020-04-07 21:45:39.869 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 18: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2020-04-07 21:45:39.869 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 18: SECURITY NOT required on COMMAND_CLASS_ALARM
2020-04-07 21:45:39.870 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 18: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2020-04-07 21:45:39.871 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: NOTIFICATION report - 0 = 0, event=22, status=255, plen=0
2020-04-07 21:45:39.871 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Alarm Type = ACCESS_CONTROL (0)
2020-04-07 21:45:39.873 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2020-04-07 21:45:39.874 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2020-04-07 21:45:39.874 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter processing NOTIFICATION
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter NOTIFICATION event is 22, type OnOffType
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter NOTIFICATION event is 22, channel alarm_system is not implemented.
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter processing NOTIFICATION
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter NOTIFICATION event is 22, type OnOffType
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter NOTIFICATION event is 22, channel alarm_access is not implemented.
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter processing NOTIFICATION
2020-04-07 21:45:39.875 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 18: Alarm converter NOTIFICATION event is 22, type OnOffType
2020-04-07 21:45:39.876 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Commands processed 1.
2020-04-07 21:45:39.876 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@418c34d0.
2020-04-07 21:45:39.876 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-04-07 21:45:39.876 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
Here’s what I don’t know/understand:
- Why is this device configured with the alarm command class? The alarm command class does show up in the xml auto-generated by the binding on inclusion
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_INDICATOR</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_BATTERY</commandClass>
<commandClass>COMMAND_CLASS_SENSOR_BINARY</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
<commandClass>COMMAND_CLASS_ALARM</commandClass>
<commandClass>COMMAND_CLASS_WAKE_UP</commandClass>
<commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
</nodeInformationFrame>
but alarm is not listed (as far as I can tell) as a supported command class in the documentation pdf listed for this device on the database page. Is my failure to get a proper alarm channel connected to this device something I’m doing or an error in the database implementation?
- Even if the alarm command class is not functioning properly, why don’t I see any activity, debug or otherwise, from the binary sensor channel?
