[SOLVED] GE/Jasco ZW6302 (34193) zwave motion sensor events ignored

Using 2.4.0-SNAPSHOT (2.4.0.201810221250). This simple, widely-used GE/Jasco sensor just doesn’t work. It’s sending notification as seen below, but no channel is updated, neither alarm_general or sensor_binary. I am on 2.4 snapshot for the secure association support for a door lock, which is working.

2018-10-24 15:23:39.474 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 18 09 71 05 00 00 00 FF 07 08 00 61
2018-10-24 15:23:39.483 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 09 71 05 00 00 00 FF 07 08 00
2018-10-24 15:23:39.490 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 09 71 05 00 00 00 FF 07 08 00
2018-10-24 15:23:39.494 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-24 15:23:39.498 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2018-10-24 15:23:39.502 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2018-10-24 15:23:39.506 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-10-24 15:23:39.510 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2018-10-24 15:23:39.514 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-10-24 15:23:39.517 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-10-24 15:23:39.521 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Alarm Type = BURGLAR (0)
2018-10-24 15:23:39.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-24 15:23:39.530 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-24 15:23:39.534 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter processing NOTIFICATION
2018-10-24 15:23:39.538 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-10-24 15:23:39.542 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter NOTIFICATION event is 8, channel alarm_general is not implemented.
2018-10-24 15:23:39.546 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2018-10-24 15:23:39.550 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12fc89.
2018-10-24 15:23:39.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:23:39.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:23:39.561 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-24 15:23:39.565 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

And when the motion timeout clears:

2018-10-24 15:23:39.474 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 18 09 71 05 00 00 00 FF 07 08 00 61
2018-10-24 15:23:39.483 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 09 71 05 00 00 00 FF 07 08 00
2018-10-24 15:23:39.490 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 09 71 05 00 00 00 FF 07 08 00
2018-10-24 15:23:39.494 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-24 15:23:39.498 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2018-10-24 15:23:39.502 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2018-10-24 15:23:39.506 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-10-24 15:23:39.510 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2018-10-24 15:23:39.514 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-10-24 15:23:39.517 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-10-24 15:23:39.521 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Alarm Type = BURGLAR (0)
2018-10-24 15:23:39.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-24 15:23:39.530 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-24 15:23:39.534 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter processing NOTIFICATION
2018-10-24 15:23:39.538 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-10-24 15:23:39.542 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter NOTIFICATION event is 8, channel alarm_general is not implemented.
2018-10-24 15:23:39.546 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2018-10-24 15:23:39.550 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12fc89.
2018-10-24 15:23:39.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:23:39.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:23:39.561 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

Item configuration follows, if it’s of any help.

Group:Switch:OR(ON,OFF) gGarage_Motion (gMotion_Sensors)
Group Garage_Sensor_1
Switch Garage_Sensor_1_Motion "Garage Motion 1" <motion> (Garage_Sensor_1, gGarage_Motion) { channel="zwave:device:1668e6f6599:node24:sensor_binary" }
Number Garage_Sensor_1_Battery "Garage Sensor 1 Battery" <battery> (Garage_Sensor_1, gBattery) { channel="zwave:device:1668e6f6599:node24:battery-level" }
Switch Garage_Sensor_1_Alarm "Garage Sensor 1 Alarm" <alarm> (Garage_Sensor_1) { channel="zwave:device:1668e6f6599:node24:alarm_general" }

Occasionally it will change state on sensor_binary channel if there was a recent motion event and it’s been awakened for poll. Its buddy, a Fibaro FGMS001, is working fine. It’s updating both alarm_motion via notification report, and sensor_binary channels via basic set.

2018-10-24 15:33:10.252 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 16 09 71 05 00 00 00 FF 07 08 00 6F
2018-10-24 15:33:10.258 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 09 71 05 00 00 00 FF 07 08 00
2018-10-24 15:33:10.261 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 09 71 05 00 00 00 FF 07 08 00
2018-10-24 15:33:10.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-24 15:33:10.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:REQUEST_NIF)
2018-10-24 15:33:10.267 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-10-24 15:33:10.268 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY NOT required on COMMAND_CLASS_ALARM
2018-10-24 15:33:10.270 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT
2018-10-24 15:33:10.272 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 22: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-10-24 15:33:10.273 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 22: Alarm Type = BURGLAR (0)
2018-10-24 15:33:10.275 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-24 15:33:10.277 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-24 15:33:10.279 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter processing NOTIFICATION
2018-10-24 15:33:10.281 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-10-24 15:33:10.283 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:device:1668e6f6599:node22:alarm_motion to ON [OnOffType]
2018-10-24 15:33:10.287 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter processing NOTIFICATION
2018-10-24 15:33:10.289 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 22: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-10-24 15:33:10.290 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.
2018-10-24 15:33:10.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6ab834.
2018-10-24 15:33:10.294 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:33:10.295 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:33:10.297 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-24 15:33:10.298 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-24 15:33:10.645 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 16 03 20 01 FF 39
2018-10-24 15:33:10.650 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 03 20 01 FF
2018-10-24 15:33:10.652 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=22, callback=0, payload=00 16 03 20 01 FF
2018-10-24 15:33:10.655 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-24 15:33:10.657 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:REQUEST_NIF)
2018-10-24 15:33:10.660 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2018-10-24 15:33:10.662 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY NOT required on COMMAND_CLASS_BASIC
2018-10-24 15:33:10.665 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2018-10-24 15:33:10.668 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 22: Basic report, value = 255
2018-10-24 15:33:10.670 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-24 15:33:10.673 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 255
2018-10-24 15:33:10.676 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:device:1668e6f6599:node22:sensor_binary to ON [OnOffType]
2018-10-24 15:33:10.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.
2018-10-24 15:33:10.695 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@5fec39.
2018-10-24 15:33:10.697 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:33:10.700 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:33:10.703 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-24 15:33:10.705 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-24 15:33:10.737 [WARN ] [eclipse.smarthome.model.script.rules] - garageMotion ON

I tried changing the ge/jasco sensor to send basic set instead of notification, but it’s also ignored:

2018-10-24 15:38:31.609 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 18 03 20 01 FF 37
2018-10-24 15:38:31.613 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 20 01 FF
2018-10-24 15:38:31.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 20 01 FF
2018-10-24 15:38:31.617 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-24 15:38:31.619 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2018-10-24 15:38:31.621 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2018-10-24 15:38:31.623 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2018-10-24 15:38:31.625 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2018-10-24 15:38:31.627 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_BASIC V1 BASIC_SET
2018-10-24 15:38:31.628 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Basic report, value = 255
2018-10-24 15:38:31.631 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-24 15:38:31.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 255
2018-10-24 15:38:31.636 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2018-10-24 15:38:31.638 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@cadb51.
2018-10-24 15:38:31.640 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:38:31.642 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-24 15:38:31.643 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-24 15:38:31.645 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

I tried, poorly, to build a new jar from source, hoping I could get it to accept basic set, but I am having issues getting openhab to reliably load the bundle from the addons folder. Not sure where to go from here.

I will update the database and this will hopefully fix the problem. The issue is that the channel name is incorrect as this should be alarm_motion. The new binding uses the channel name to automatically decide which notifications to process.

Thank you. That’s what I was trying to do with building from source, but I wasn’t doing it right. I’ll look for your commit to learn where I failed. I was hoping to leave you with a pull request. :wink:

Side question: I got the custom jar bundle to load once, where I changed the xml to alarm_motion. It didn’t load at first, and not sure how it finally happened. I restarted everything at one point, after removing /var/lib/openhab2/tmp/mvn/…/org.openhab.bindings.zwave.*.jar, but that no longer seems effective. I also found I had to uninstall the old bundle, when two were listed. I couldn’t reproduce that situation. I haven’t found a good doc on how this is supposed to work, or a way to explicitly load a jar (tried file:// url).

p.s. Do you think this is going to be an issue for other devices with the binding refactor?

The change needs to be made in the database, not on github…

You will need to delete the thing and add it back so that it picks up the new definition.

I’m not sure exactly what you’re doing. If you are using the snapshot version, then you don’t need to load custom JARs - just reinstall the binding.

Yes, it’s quite likely. There’s no automatic way to update this unfortunately.

Okay. I don’t know how I would build the xml tree from database, or how I would make a local copy of it so I could test.

Trying to compile a modified jar and get it loaded. First pass, I had modified the xml to declare alarm_motion instead of alarm_general, then built a jar with maven. My issue was getting the one I dropped into /usr/lib/openhab2/addons to actually get loaded as a bundle. I’m not going to do that again for this issue, but it wasn’t working as expected.

Needing to re-add the thing makes a lot of sense. I’ll do that when I pull your next snapshot build.

You just need to export the changed database file from the database and update the file in your repository and compile as normal. That said, all I’ve done is changed the channel name which is the same as you have done manually, so it will work ok like this too.

This is where I’m seeking guidance, for a new OH2 user, on what you’re actually saying to do. Need definition of “database”, and “update the file”, and “export”. All I know of “the database” right now is that it exists here and I can download a json dump.

the online database here.

The file that you export from the database needs to be placed into the binding in the things folder (see the ESH developper documentation on these definition files).

There’s a button on the database page called export -:

Pressing this will “export” “the file” from “the database” :slight_smile:

1 Like

This may give you some more info… and no IDE needed.

1 Like

Confirmed the db update makes this sensor functional again, using alarm_motion channel.

1 Like

Hi @chris

Did the updated DB made it into 2.4.0~M5.1? I ask because I’m using 2.4.0 Milestone 5, along with two GE/Jasco 26931/SW4006 “smart switches”.

image

I noticed I’m only getting “switch_binary” changed events in the events.log. This is in spite of the fact that I have the “binary sensor” and “motion sensor” channels active

2018-11-11 11:38:55.189 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from OFF to ON
2018-11-11 11:43:55.183 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from ON to OFF
2018-11-11 11:50:55.254 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from OFF to ON
2018-11-11 11:56:55.149 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from ON to OFF
2018-11-11 12:15:55.261 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from OFF to ON
2018-11-11 12:16:11.247 [vent.ItemStateChangedEvent] - zwave_laundry_room_a_switch_binary changed from OFF to ON
2018-11-11 12:22:11.246 [vent.ItemStateChangedEvent] - zwave_laundry_room_a_switch_binary changed from ON to OFF
2018-11-11 12:22:55.191 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from ON to OFF
2018-11-11 12:30:55.187 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from OFF to ON
2018-11-11 12:31:11.279 [vent.ItemStateChangedEvent] - zwave_laundry_room_a_switch_binary changed from OFF to ON
2018-11-11 12:35:55.236 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from ON to OFF
2018-11-11 12:36:11.242 [vent.ItemStateChangedEvent] - zwave_laundry_room_a_switch_binary changed from ON to OFF
2018-11-11 12:44:55.144 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from OFF to ON
2018-11-11 12:45:11.242 [vent.ItemStateChangedEvent] - zwave_laundry_room_a_switch_binary changed from OFF to ON
2018-11-11 12:49:55.180 [vent.ItemStateChangedEvent] - zwave_laundry_room_b_switch_binary changed from ON to OFF
2018-11-11 12:50:11.246 [vent.ItemStateChangedEvent] - zwave_laundry_room_a_switch_binary changed from ON to OFF

Here are the items as they appear in Habadmin

image

Regards,
Burzin

The database was updated a day before M5 was released, so anything approved at that time was included.

The database will not have any impact on what the device sends. Either the device is misconfigured, or possibly the channels aren’t configured to decode the data, but you need to check the logs to see this.

Hi @chris,

I just realized that I have different device from the OP. At any rate, I enabled debug logging and I see the following in the openhab.log. From what little I can gather, the “binary sensor” and the “motion sensor” are being polled. How do I further interpret the logs?

2018-11-11 13:29:55.055 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling zwave:device:512:node4:sensor_binary
2018-11-11 13:29:55.058 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling zwave:device:512:node4:config_decimal_param6
2018-11-11 13:29:55.060 [DEBUG] [onverter.ZWaveConfigurationConverter] - NODE 4: Generating poll message for COMMAND_CLASS_CONFIGURATION, endpoint 0
2018-11-11 13:29:55.063 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 4: Creating new message for application command CONFIGURATIONCMD_GET
2018-11-11 13:29:55.064 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2018-11-11 13:29:55.067 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured
2018-11-11 13:29:55.069 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2018-11-11 13:29:55.072 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 1291 to queue - size 1
2018-11-11 13:29:55.074 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-11-11 13:29:55.077 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 04 02 25 02 25 03 E2
2018-11-11 13:29:55.080 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 4: Sending REQUEST Message = 01 09 00 13 04 02 25 02 25 03 E2
2018-11-11 13:29:55.083 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-11-11 13:29:55.085 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.088 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-11-11 13:29:55.088 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2018-11-11 13:29:55.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-11-11 13:29:55.092 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 1292 to queue - size 1
2018-11-11 13:29:55.092 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-11-11 13:29:55.095 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.095 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-11-11 13:29:55.097 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-11-11 13:29:55.099 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-11-11 13:29:55.101 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-11-11 13:29:55.105 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2018-11-11 13:29:55.107 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2018-11-11 13:29:55.108 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2018-11-11 13:29:55.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.111 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-11-11 13:29:55.113 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 13 03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 48
2018-11-11 13:29:55.112 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.114 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2018-11-11 13:29:55.115 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: sentData successfully placed on stack.
2018-11-11 13:29:55.116 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1291: Advanced to WAIT_REQUEST
2018-11-11 13:29:55.116 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=3, payload=03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00
2018-11-11 13:29:55.117 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: TID 1291: Transaction not completed
2018-11-11 13:29:55.119 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=3, payload=03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00
2018-11-11 13:29:55.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1291: [WAIT_REQUEST] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.122 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-11-11 13:29:55.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1291: [WAIT_REQUEST] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 1291: (Callback 3)
2018-11-11 13:29:55.126 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 04 03 25 03 FF BC 00 92
2018-11-11 13:29:55.126 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-11-11 13:29:55.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 1291: callback 3
2018-11-11 13:29:55.128 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=3, payload=03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00
2018-11-11 13:29:55.129 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 25 03 FF BC 00
2018-11-11 13:29:55.130 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: SendData Request. CallBack ID = 3, Status = Transmission complete and ACK received(0)
2018-11-11 13:29:55.131 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2018-11-11 13:29:55.132 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1291: Advanced to WAIT_DATA

Regards,
Burzin

What device do you have? It’s kind of important to know these things so we can interpret what is, or isn’t, happening :wink:

Sorry, I posted it in my original post.

I have two GE/Jasco 26931/SW4006 “smart switches”. They are recognized as this:

image

In the events log I only see evidence that the “switch_binary” is being tripped. With debug enabled, I see the “binary sensor” and the “motion sensor” are being polled, but I can’t make sense of the rest.

2018-11-11 13:29:55.055 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling zwave:device:512:node4:sensor_binary
2018-11-11 13:29:55.058 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling zwave:device:512:node4:config_decimal_param6
2018-11-11 13:29:55.060 [DEBUG] [onverter.ZWaveConfigurationConverter] - NODE 4: Generating poll message for COMMAND_CLASS_CONFIGURATION, endpoint 0
2018-11-11 13:29:55.063 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 4: Creating new message for application command CONFIGURATIONCMD_GET
2018-11-11 13:29:55.064 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2018-11-11 13:29:55.067 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured
2018-11-11 13:29:55.069 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2018-11-11 13:29:55.072 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 1291 to queue - size 1
2018-11-11 13:29:55.074 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-11-11 13:29:55.077 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 04 02 25 02 25 03 E2
2018-11-11 13:29:55.080 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 4: Sending REQUEST Message = 01 09 00 13 04 02 25 02 25 03 E2
2018-11-11 13:29:55.083 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-11-11 13:29:55.085 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.088 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-11-11 13:29:55.088 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2018-11-11 13:29:55.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-11-11 13:29:55.092 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 1292 to queue - size 1
2018-11-11 13:29:55.092 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-11-11 13:29:55.095 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.095 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-11-11 13:29:55.097 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-11-11 13:29:55.099 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-11-11 13:29:55.101 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-11-11 13:29:55.105 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2018-11-11 13:29:55.107 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2018-11-11 13:29:55.108 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2018-11-11 13:29:55.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.111 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-11-11 13:29:55.113 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 13 03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 48
2018-11-11 13:29:55.112 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1291: [WAIT_RESPONSE] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.114 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2018-11-11 13:29:55.115 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: sentData successfully placed on stack.
2018-11-11 13:29:55.116 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1291: Advanced to WAIT_REQUEST
2018-11-11 13:29:55.116 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=3, payload=03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00
2018-11-11 13:29:55.117 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: TID 1291: Transaction not completed
2018-11-11 13:29:55.119 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=3, payload=03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00
2018-11-11 13:29:55.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1291: [WAIT_REQUEST] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.122 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-11-11 13:29:55.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1291: [WAIT_REQUEST] priority=Get, requiresResponse=true, callback: 3
2018-11-11 13:29:55.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 1291: (Callback 3)
2018-11-11 13:29:55.126 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 04 03 25 03 FF BC 00 92
2018-11-11 13:29:55.126 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-11-11 13:29:55.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 1291: callback 3
2018-11-11 13:29:55.128 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=3, payload=03 00 00 02 00 BC 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00
2018-11-11 13:29:55.129 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 25 03 FF BC 00
2018-11-11 13:29:55.130 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: SendData Request. CallBack ID = 3, Status = Transmission complete and ACK received(0)
2018-11-11 13:29:55.131 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false

Regards,
Burzin

Oh, I realized the alarm_motion channel is defined as a switch type. Is there a reason it wouldn’t be contact? This seems to be a pattern. My other motion sensors, and even zigbee leak sensors, are showing their channels as Switch.