[SOLVED] Vision Door/Windows sensor zd2102 open/close and tamper are not triggered to different events


(Chris Jackson) #80

Yes, you would need to delete the things and add them back…

So, from the above can we say it’s working as expected (and as required?)? It looks like the only issue is the external switch - I don’t remember how that is reported - if it’s a different event, then we should also be able to detect it.


(Scott Rushworth) #81

For the WADWAZ-1, yes. But most of the other devices will likely require a cleanup in the database. Check the spreadsheet here. That post also had some info for the external switch, which would be great if it could report, because I have about 20 of them setup as leak sensors using the external switch, otherwise I’ll need to scrape the log or set them up in ST :face_vomiting:.


(Chris Jackson) #82

What does “most other devices” mean? There are hundreds of notification devices in the database - if you are expecting them to have to change, well, good luck… :wink:

The way the binding is written, any devices that use the notification command class (properly!) should not have a high dependency on the database. Only the channel name is used - the events etc that are managed for each channel are defined directly in the binding. This was a change I made a while ago to get around the fact that previously we had to specify the event numbers for every device - that is no longer necessary in most cases.

Now that I’ve said that, you’ll probably tell me it WAS necessary here. That is because this device is not using the notification command class, and the definition of alarms is not well defined (unlike notifications).


(Scott Rushworth) #83

The other door/window sensors referenced in the spreadsheet… the database entries are all jumbled up.


(Chris Jackson) #84

Sorry - I’ve not been able to view the spreadsheet yet as it’s blocked by most systems I’m using :frowning: . I guess you are just referring to devices that you personally have then?


(Scott Rushworth) #85

Oh wow… the forum can display this. Lost the fancy colors though.

Info From Zwave Alliance DB Info From Zwave ThingType DB
Manufacturer Name Manufacturer ID Model Type ID Zwave Plus Security Notes Zwave Alliance Name Unique Reference Zwave DB Type:IDs Notes Zwave DB
Zipato 0131 ZD2102US-5 2001 0106 Yes Yes https://products.z-wavealliance.org/products/1864/ ZD2102 zd2102 2001:0106 http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/713
Vision Security 0109 ZD2102US-5 2001 0106 Yes Yes Same as Zipato. https://products.z-wavealliance.org/products/1705/ N/A N/A N/A This device needs to be added, but identical to Zipato except for Manufacturer ID N/A
Anchor 032B ZD2102US-5 2001 0106 Yes Yes Same as Zipato. https://products.z-wavealliance.org/products/2249 N/A N/A N/A This device needs to be added N/A
Vision Security 0109 ZD2102EU-5 2001 0105 Yes No Does not have security. https://products.z-wavealliance.org/products/988 N/A N/A N/A This device needs to be added N/A
Linear 014F WADWAZ-1 2001 0102 No No https://products.z-wavealliance.org/products/1033 WADWAZ-1 wadwaz1 2001:0102 http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/9
Monoprice 0202 10795 2001 0102 No No Same as WADWAZ. https://products.z-wavealliance.org/products/1121/ N/A N/A N/A This device needs to be added, but identical to WADWAZ-1 except for Manufacturer ID N/A
Vision 0109 ZD2102 2001 0102 No No Same as WADWAZ. Info from XML. https://products.z-wavealliance.org/products/111/ ZD2102 zd2102 2001:0102,2001:0105,2001:0106 Remove 2001:1006 and 2001:1005. Correct CCs. http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/105
Vision 0109 ZD2102 2001 0101 No No Not the same as 10795 and WADWAZ-1 (does not have ALARM CC). N/A N/A N/A N/A This device needs to be added N/A

Requesting owner's experiences with WADWAZ-1 Door & Window Sensors
OH2 Z-Wave refactoring and testing... and SECURITY
ZD2102-5 Door Window Sensor Battery Not Reporting
I need two contacts .... for a Catflap . Idea?
(Chris Jackson) #86

Thanks - so this is all the different versions of the same device from different “manufacturers”? Then yes, they will all need to be updated - I don’t really see any way around that as this is really custom functionality for this device.


(Scott Rushworth) #87

Correct.

I’ll start cleaning them up then. :+1: I only have the WADWAZ-1 though, so it would be nice to get some helpers who have the other devices and test them out after the changes. The Vision ZD2102 should be easy, since it looks like @B34N has one. I’ll look through this and other threads to try and find people to test. This should correct a lot of issues people have reported for these types of devices.


(Scott Rushworth) #88

The WADWAZ-1 has the sensor_door channel marked for treat as basic and it is working. Is this needed, or should I set them all like this?

Also, the Sensor_Binary and ALARM;type=BURGLAR, event=2 are both reporting exactly same thing (sensor open/closed). Are there other devices that report the same information through different CCs? If so, how has this been handled as far as choosing a Channel… can both be put on the same one (sensor_door)?


(Chris Jackson) #89

I think it’s needed. I recall that one of the sensors at least was sending BASIC commands for some events.

Yes - it’s very common.

Ideally I would prefer to only have a single channel - it avoids the inevitable question of why there are two channels! However, this then often requires the device to be configured in a specific way to ensure that the correct CC is used (often there’s a parameter, or an association that configures this). This then requires the user to understand all this - here is the problem…

Something I’ve been wanting to add to the database is a kind of “configuration profile” that allows parameters to be specified as a specific value so that we can configure into a known configuration, but I’ve not had the time to do this.

No - at least not at the moment. Maybe this is possible with a bit more magic in the database and it might be an option to solve the above issue, but at the moment you’d end up with two channels with the same name, and probably an error when the device is instantiated.


(Scott Rushworth) #90

I’ll add it to the others then.

That would be cool… but would not help these devices. They always report both.

Bugger… well… Sensor_Binary comes in about 20ms sooner, so it is at least my preferred CC to use, so I’ll keep that as sensor_door and use alarm_entry for Alarm. Same as the WADWAZ-1, currently.


(Chris Jackson) #91

If they always report both, then just pick one :wink:


(Scott Rushworth) #92

I’ll pick the one that uses sensor_door, since that’s the only Channel that’s OPEN/CLOSE. :wink:


(Scott Rushworth) #93

Is alarm_tamper a legit channel? I don’t see it in here, but a lot of devices are using it.

Nevermind… I found it.


(Chris Jackson) #94

If you type in an invalid channel name, you’ll get a big red error across the top of the screen (ie the database entry summary page).


(Scott Rushworth) #95

I think this is all done. I didn’t publish anything, so you can review and approve/reject…

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/713
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/816
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/9
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/817
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/105


Z-Wave Switches vs Contacts, and the database
(Chris Jackson) #96

Thanks - I’ll probably look at this Friday night or Saturday once I’m back home…


(Mark Bean) #97

I updated last night and readded the devices. The battery level shows and the tamper works.

Remove Magnet:

2018-03-07 13:03:55.209 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3079 to 3080
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:03:55.209 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 18 03 20 01 FF 37 
2018-03-07 13:03:55.217 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:03:55.221 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 18 03 20 01 FF 37 
2018-03-07 13:03:55.225 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 18 03 20 01 FF 37 
2018-03-07 13:03:55.228 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 18 03 20 01 FF 
2018-03-07 13:03:55.232 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Application Command Request (ALIVE:GET_CONFIGURATION)
2018-03-07 13:03:55.237 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Incoming command class BASIC
2018-03-07 13:03:55.240 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Received Basic Request
2018-03-07 13:03:55.244 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Basic Set sent to the controller will be processed as Basic Report
2018-03-07 13:03:55.251 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Basic report, value = 0xFF
==> /var/log/openhab2/events.log <==
2018-03-07 13:03:55.256 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3080 to 3081
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:03:55.258 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 18 0A 71 05 07 FF 00 FF 07 02 00 00 8F 
2018-03-07 13:03:55.259 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-03-07 13:03:55.262 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-03-07 13:03:55.265 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2018-03-07 13:03:55.268 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=24, callback=102, payload=18 03 70 05 01 
2018-03-07 13:03:55.270 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:03:55.273 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 18 0A 71 05 07 FF 00 FF 07 02 00 00 8F 
2018-03-07 13:03:55.276 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 18 0A 71 05 07 FF 00 FF 07 02 00 00 8F 
2018-03-07 13:03:55.278 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 18 0A 71 05 07 FF 00 FF 07 02 00 00 
2018-03-07 13:03:55.280 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Application Command Request (ALIVE:GET_CONFIGURATION)
2018-03-07 13:03:55.282 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Incoming command class ALARM
2018-03-07 13:03:55.284 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Received ALARM command V2
2018-03-07 13:03:55.286 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Process NOTIFICATION_REPORT V2
2018-03-07 13:03:55.288 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: NOTIFICATION report - 7 = 255, event=2, status=255
2018-03-07 13:03:55.290 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Alarm Type = BURGLAR (7)
2018-03-07 13:03:55.291 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-03-07 13:03:55.294 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-03-07 13:03:55.295 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-03-07 13:03:55.297 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:03:55.299 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 2, type OnOffType
2018-03-07 13:03:55.301 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:03:55.304 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=24, callback=102, payload=18 03 70 05 01 

Replace Magnet

2018-03-07 13:04:24.771 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 18 03 20 01 00 C8 
2018-03-07 13:04:24.784 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
==> /var/log/openhab2/events.log <==
2018-03-07 13:04:24.786 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3081 to 3082
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:04:24.788 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 18 03 20 01 00 C8 
2018-03-07 13:04:24.791 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 18 03 20 01 00 C8 
2018-03-07 13:04:24.794 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 18 03 20 01 00 
2018-03-07 13:04:24.796 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Application Command Request (ALIVE:GET_CONFIGURATION)
2018-03-07 13:04:24.798 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Incoming command class BASIC
2018-03-07 13:04:24.800 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Received Basic Request
2018-03-07 13:04:24.801 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Basic Set sent to the controller will be processed as Basic Report
2018-03-07 13:04:24.803 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 24: Basic report, value = 0x00
2018-03-07 13:04:24.806 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-03-07 13:04:24.807 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-03-07 13:04:24.809 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
2018-03-07 13:04:24.812 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=24, callback=102, payload=18 03 70 05 01 
2018-03-07 13:04:24.821 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 18 0A 71 05 07 00 00 FF 07 02 00 00 70 
==> /var/log/openhab2/events.log <==
2018-03-07 13:04:24.821 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3082 to 3083
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:04:24.828 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:04:24.831 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 18 0A 71 05 07 00 00 FF 07 02 00 00 70 
2018-03-07 13:04:24.833 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 18 0A 71 05 07 00 00 FF 07 02 00 00 70 
2018-03-07 13:04:24.836 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 18 0A 71 05 07 00 00 FF 07 02 00 00 
2018-03-07 13:04:24.838 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Application Command Request (ALIVE:GET_CONFIGURATION)
2018-03-07 13:04:24.840 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Incoming command class ALARM
2018-03-07 13:04:24.843 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Received ALARM command V2
2018-03-07 13:04:24.845 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Process NOTIFICATION_REPORT V2
2018-03-07 13:04:24.847 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: NOTIFICATION report - 7 = 0, event=2, status=255
2018-03-07 13:04:24.849 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Alarm Type = BURGLAR (7)
2018-03-07 13:04:24.851 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-03-07 13:04:24.853 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-03-07 13:04:24.856 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-03-07 13:04:24.858 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:04:24.860 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 2, type OnOffType
2018-03-07 13:04:24.862 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:04:24.865 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=24, callback=102, payload=18 03 70 05 01 
2018-03-07 13:04:25.431 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 1E 03 20 01 FF 31 
==> /var/log/openhab2/events.log <==
2018-03-07 13:04:25.433 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3083 to 3084
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:04:25.437 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:04:25.443 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 1E 03 20 01 FF 31 
2018-03-07 13:04:25.445 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 1E 03 20 01 FF 31 
2018-03-07 13:04:25.447 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 03 20 01 FF 
==> /var/log/openhab2/events.log <==
2018-03-07 13:04:25.454 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3084 to 3085
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:04:25.457 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 30: Application Command Request (ALIVE:DONE)
2018-03-07 13:04:25.453 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 1E 0A 71 05 07 FF 00 FF 07 02 00 00 89 
2018-03-07 13:04:25.462 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 30: Starting initialisation from DONE
2018-03-07 13:04:25.464 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@96710e already registered
2018-03-07 13:04:25.466 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 30: Incoming command class BASIC
2018-03-07 13:04:25.468 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 30: Received Basic Request
2018-03-07 13:04:25.470 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 30: Basic Set sent to the controller will be processed as Basic Report
2018-03-07 13:04:25.472 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 30: Basic report, value = 0xFF
2018-03-07 13:04:25.474 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-03-07 13:04:25.476 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-03-07 13:04:25.478 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2018-03-07 13:04:25.480 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Updating channel state zwave:device:cab10335:node30:sensor_binary to ON [OnOffType]
2018-03-07 13:04:25.483 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Transaction not completed: node address inconsistent.  lastSent=24, incoming=255
==> /var/log/openhab2/events.log <==
2018-03-07 13:04:25.488 [vent.ItemStateChangedEvent] - FF_Office_PIR_Motion changed from OFF to ON
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:04:25.491 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:04:25.494 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 1E 0A 71 05 07 FF 00 FF 07 02 00 00 89 
2018-03-07 13:04:25.498 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 1E 0A 71 05 07 FF 00 FF 07 02 00 00 89 
2018-03-07 13:04:25.501 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 1E 0A 71 05 07 FF 00 FF 07 02 00 00 
2018-03-07 13:04:25.505 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 30: Application Command Request (ALIVE:DONE)
2018-03-07 13:04:25.508 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 30: Starting initialisation from DONE
2018-03-07 13:04:25.511 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@96710e already registered
2018-03-07 13:04:25.514 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 30: Incoming command class ALARM
2018-03-07 13:04:25.517 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: Received ALARM command V2
2018-03-07 13:04:25.520 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: Process NOTIFICATION_REPORT V2
2018-03-07 13:04:25.523 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: NOTIFICATION report - 7 = 255, event=2, status=255
2018-03-07 13:04:25.526 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: Alarm Type = BURGLAR (7)
2018-03-07 13:04:25.529 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-03-07 13:04:25.532 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-03-07 13:04:25.535 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-03-07 13:04:25.538 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:04:25.540 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 2, type OnOffType
2018-03-07 13:04:25.543 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Updating channel state zwave:device:cab10335:node30:alarm_burglar to ON [OnOffType]
2018-03-07 13:04:25.550 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Transaction not completed: node address inconsistent.  lastSent=24, incoming=255

Remove Cover:

2018-03-07 13:06:30.894 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 18 0A 71 05 07 FF 00 FF 07 03 00 00 8E 
==> /var/log/openhab2/events.log <==
2018-03-07 13:06:30.898 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3106 to 3107
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:06:30.909 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:06:30.916 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 18 0A 71 05 07 FF 00 FF 07 03 00 00 8E 
2018-03-07 13:06:30.921 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 18 0A 71 05 07 FF 00 FF 07 03 00 00 8E 
2018-03-07 13:06:30.926 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 18 0A 71 05 07 FF 00 FF 07 03 00 00 
2018-03-07 13:06:30.928 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Application Command Request (ALIVE:GET_CONFIGURATION)
2018-03-07 13:06:30.930 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Incoming command class ALARM
2018-03-07 13:06:30.932 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Received ALARM command V2
2018-03-07 13:06:30.935 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Process NOTIFICATION_REPORT V2
2018-03-07 13:06:30.937 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: NOTIFICATION report - 7 = 255, event=3, status=255
2018-03-07 13:06:30.939 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Alarm Type = BURGLAR (7)
2018-03-07 13:06:30.942 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-03-07 13:06:30.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-03-07 13:06:30.948 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-03-07 13:06:30.950 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:06:30.952 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2018-03-07 13:06:30.954 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Updating channel state zwave:device:cab10335:node24:alarm_tamper to ON [OnOffType]
2018-03-07 13:06:30.962 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
==> /var/log/openhab2/events.log <==
2018-03-07 13:06:30.963 [vent.ItemStateChangedEvent] - FF_Garage_Entry_Tamper changed from OFF to ON
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:06:30.965 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=24, callback=106, payload=18 03 70 05 01 
2018-03-07 13:06:33.041 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 2B 03 20 01 00 FB 
==> /var/log/openhab2/events.log <==
2018-03-07 13:06:33.049 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3107 to 3108
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:06:33.055 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:06:33.060 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 2B 03 20 01 00 FB 
2018-03-07 13:06:33.063 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 2B 03 20 01 00 FB 
2018-03-07 13:06:33.066 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 2B 03 20 01 00 
2018-03-07 13:06:33.070 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 43: Application Command Request (ALIVE:DONE)
2018-03-07 13:06:33.071 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Starting initialisation from DONE
2018-03-07 13:06:33.073 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1099bb0 already registered
2018-03-07 13:06:33.075 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 43: Incoming command class BASIC
2018-03-07 13:06:33.076 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 43: Received Basic Request
2018-03-07 13:06:33.078 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 43: Basic Set sent to the controller will be processed as Basic Report
2018-03-07 13:06:33.080 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 43: Basic report, value = 0x00
2018-03-07 13:06:33.081 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-03-07 13:06:33.083 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-03-07 13:06:33.085 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
2018-03-07 13:06:33.087 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating channel state zwave:device:cab10335:node43:sensor_binary to OFF [OnOffType]
2018-03-07 13:06:33.089 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Transaction not completed: node address inconsistent.  lastSent=24, incoming=255
2018-03-07 13:06:33.110 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 2B 0B 71 05 07 00 00 FF 07 00 01 08 00 48 
==> /var/log/openhab2/events.log <==
2018-03-07 13:06:33.115 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3108 to 3109
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:06:33.118 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-03-07 13:06:33.120 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 04 00 2B 0B 71 05 07 00 00 FF 07 00 01 08 00 48 
2018-03-07 13:06:33.123 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 11 00 04 00 2B 0B 71 05 07 00 00 FF 07 00 01 08 00 48 
2018-03-07 13:06:33.125 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 2B 0B 71 05 07 00 00 FF 07 00 01 08 00 
2018-03-07 13:06:33.126 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 43: Application Command Request (ALIVE:DONE)
2018-03-07 13:06:33.128 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Starting initialisation from DONE
2018-03-07 13:06:33.130 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1099bb0 already registered
2018-03-07 13:06:33.132 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 43: Incoming command class ALARM
2018-03-07 13:06:33.133 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: Received ALARM command V4
2018-03-07 13:06:33.135 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: Process NOTIFICATION_REPORT V4
2018-03-07 13:06:33.136 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: NOTIFICATION report - 7 = 0, event=0, status=255
2018-03-07 13:06:33.138 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: Alarm Type = BURGLAR (7)
2018-03-07 13:06:33.140 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-03-07 13:06:33.142 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-03-07 13:06:33.143 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-03-07 13:06:33.145 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-03-07 13:06:33.147 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2018-03-07 13:06:33.149 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating channel state zwave:device:cab10335:node43:alarm_burglar to OFF [OnOffType]
2018-03-07 13:06:33.152 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Transaction not completed: node address inconsistent.  lastSent=24, incoming=255
==> /var/log/openhab2/events.log <==
2018-03-07 13:06:33.156 [vent.ItemStateChangedEvent] - FF_Kitchen_PIR_Alarm changed from ON to OFF
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:06:33.199 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 2B 03 80 03 FF A6 
2018-03-07 13:06:33.203 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
==> /var/log/openhab2/events.log <==
2018-03-07 13:06:33.207 [vent.ItemStateChangedEvent] - zwave_serial_zstick_cab10335_serial_sof changed from 3109 to 3110
==> /var/log/openhab2/openhab.log <==
2018-03-07 13:06:33.209 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 2B 03 80 03 FF A6 
2018-03-07 13:06:33.211 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 2B 03 80 03 FF A6 
2018-03-07 13:06:33.213 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 2B 03 80 03 FF 
2018-03-07 13:06:33.216 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 43: Application Command Request (ALIVE:DONE)
2018-03-07 13:06:33.218 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 43: Starting initialisation from DONE
2018-03-07 13:06:33.221 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1099bb0 already registered
2018-03-07 13:06:33.223 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 43: Incoming command class BATTERY
2018-03-07 13:06:33.225 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 43: Received Battery Request
2018-03-07 13:06:33.228 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 43: Battery report value = 255
2018-03-07 13:06:33.230 [WARN ] [ommandclass.ZWaveBatteryCommandClass] - NODE 43: BATTERY LOW!
2018-03-07 13:06:33.232 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-03-07 13:06:33.234 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-03-07 13:06:33.236 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 0
2018-03-07 13:06:33.239 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 43: Updating channel state zwave:device:cab10335:node43:battery-level to 0 [DecimalType]
2018-03-07 13:06:33.245 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 24: Transaction not completed: node address inconsistent.  lastSent=24, incoming=255

(Scott Rushworth) #98

The changes I made will hopefully help you and others. For your device, the BASIC was not linked to anything, and IIRC the channel for ALARM was hooked up wrong too. That’s probably why the channels are not being updated.


(Chris Jackson) #99

I’m travelling at the moment - back home on Friday night so I’ll do an update on Friday night or Saturday morning. Let’s see if that resolves the issues…

(and thanks @5iver for the database updates :wink: ).