Homeseer MS-100+ appears to have misassigned events

[will_stewart1a (Will)]

I have multiple HS-MS110+ motion sensors that appear to have different behavior. On top of that, the assignment of the events appears to be mixed up, with the motion sensing event coming through the burglary alarm event, which is intended to alert whenever the motion sensor is experiencing physical movement.

One motion sensor succeeds in firing a motion event;

2018-09-22 19:40:56.976 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Application Command Request (ALIVE:DETAILS)
2018-09-22 19:40:56.976 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 16: Incoming command class ALARM
2018-09-22 19:40:56.976 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Received ALARM command V5
2018-09-22 19:40:56.977 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Process NOTIFICATION_REPORT V5
2018-09-22 19:40:56.977 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 16: NOTIFICATION report - 0 = 0, event=0, status=255
2018-09-22 19:40:56.977 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Alarm Type = BURGLAR (0)
2018-09-22 19:40:56.977 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-09-22 19:40:56.978 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-09-22 19:40:56.978 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-09-22 19:40:56.978 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-09-22 19:40:56.978 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2018-09-22 19:40:56.979 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Updating channel state zwave:device:1645796be4b:node16:alarm_burglar to OFF [OnOffType]

Another one does not;

2018-09-22 19:40:44.629 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DETAILS)
2018-09-22 19:40:44.629 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class ALARM
2018-09-22 19:40:44.629 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Received ALARM command V5
2018-09-22 19:40:44.629 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Process NOTIFICATION_REPORT V5
2018-09-22 19:40:44.629 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: NOTIFICATION report - 0 = 0, event=0, status=255
2018-09-22 19:40:44.629 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Alarm Type = BURGLAR (0)
2018-09-22 19:40:44.629 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent

In the first one, event=8. In the second, event=0. It’s not clear to me how I can solve this.

Is is best to fix the misassignment of events first? If so, what is the process?

[5iver (Scott Rushworth)]

Did you include them at different times, with different versions of the binding? If so, delete the Thing and rediscover (this does not mean exclude.include) and it will pull in the updated Thing definition from the binding. That should make them consistent. Node 18 looks to be using a newer Thing defintion, but may not have the associations set.

[will_stewart1a (Will)]

They were included with the same version of the binding. Now this morning, the alarm conversion that was remiss is now showing the same behavior as the previous one, so I am obtaining an event based upon motion. This was not based on any update to the thing, as the last current update is from Thursday at 22:22:46

However, one issue still remains: The motion event is being sent as a burglar alarm intended to identify when the sensor was being physically manipulated, not when motion was sensed. What is the process for correcting the .xml file for this thing?

[5iver (Scott Rushworth)]

In looking at your logs again, I’m not sure what I was seeing that made me think that one was outdated. Sounds like 18 was just not initialized yet. Glad it’s working for you now.

@will_stewart1a

What is the process for correcting the .xml file for this thing?

If the information here…

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/802

… is incorrect, then read through the instructions here…

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

… and update the device. The device database is exported once or twice a week. This is included in the build, which you’ll need to update to, and then you’ll need to update your Things!

[will_stewart1a (Will)]

From the procedure, it appears I need to pull in @chris , the information on both the messages and on HABmin are (possibly) incorrect. For example, I should be getting motion alerts via the binary sensor, and physical movement (tampering) via the burglar alerts. However, the motion alerts are coming through the burglar (tamper) alarm.

The MS100+ specs have the motion event coming through a Notification Report (Group 1) and the Basic Command Class (Group 2, with 8 for motion detected and 0 for motion ceased, which is correct, though the messages being received show “ALARM command V5”.

Caveat: I’m no Z-Wave expert, so everything I say is from a dilletante perspective

In looking at the Z-Wave specs, it appears that the alarm command class is deprecated, and it appears to go up to V2 (don’t see a V5), though this may refer to an application specific Alarm Type. There is a deprecated V5 Notification Command Class, though that seems mostly unrelated.

Are the following first five lines strictly from Homeseer MS100+? If so, they are a tad unclear, and you have done an excellent job of making sense out of ambiguous messages. That being said, what needs to be adjusted to show the motion and tampering elements correctly in HABmin?

[ssage.ApplicationCommandMessageClass] - NODE 16: Incoming command class ALARM
 [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Received ALARM command V5
 [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Process NOTIFICATION_REPORT V5
 [.commandclass.ZWaveAlarmCommandClass] - NODE 16: NOTIFICATION report - 0 = 0, event=0, status=255
 [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Alarm Type = BURGLAR (0)
 [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
 [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Got an event from Z-Wave network: ZWaveAlarmValueEvent
 [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
 [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
 [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
 [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Updating channel state zwave:device:1645796be4b:node16:alarm_burglar to OFF [OnOffType
~~~

[chris (Chris Jackson)]

@will_stewart1a

In looking at the Z-Wave specs, it appears that the alarm command class is deprecated, and it appears to go up to V2 (don’t see a V5), though this may refer to an application specific Alarm Type. There is a deprecated V5 Notification Command Class, though that seems mostly unrelated.

The notification class is not deprecated - V5 is just not the latest version. The Alarm class just got renamed to notification at V2 - since the binding just handled everything in one class, this is irrelevant.

What version of the binding are you using? Please ensure that you’re using the latest snapshot.

[will_stewart1a (Will)]

PaperUI says I’m running 2.3.0, though I have 2.4.0 loaded in the /usr/share/openhab2/addons/ folder, and walked through this explanation to load it.

[chris (Chris Jackson)]

Looking at the logs, I’m not convinced you are using the latest version, although I can’t be 100% sure from the logs. I don’t see anything in there logging the transaction manager though.

[will_stewart1a (Will)]

After accessing the console, here’s what it says I’m running;

openhab> bundle:list | grep ZWave
238 │ Active │ 80 │ 2.4.0.201807010828 │ ZWave Binding

[chris (Chris Jackson)]

Please ensure you update to the latest snapshot version - hopefully it will solve your issue.

[will_stewart1a (Will)]

Now operating with latest Snapshot and have restarted twice.

openhab> bundle:list | grep ZWave
238 │ Active │ 80 │ 2.4.0.201809231018 │ ZWave Binding

Here is the output now;

2018-09-23 17:05:10.759 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Application Command Request (ALIVE:REQUEST_NIF)
2018-09-23 17:05:10.760 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 18: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-09-23 17:05:10.760 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 18: SECURITY not supported
2018-09-23 17:05:10.760 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 18: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2018-09-23 17:05:10.760 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: NOTIFICATION report - 0 = 0, event=9, status=255, plen=0
2018-09-23 17:05:10.760 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Alarm Type = BURGLAR (0)
2018-09-23 17:05:10.760 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Commands processed 1.
2018-09-23 17:05:10.760 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 18: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@52b84877.
2018-09-23 17:05:10.760 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-23 17:05:10.760 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

However, no Z-Wave events are being generated and all of the Z-Wave things in HABmin have question marks beside them, as shown below;

Are more restarts required or some other approach?

[chris (Chris Jackson)]

Did you delete all things and reinstall them? This is required to get the updated definitions - see the following thread -:

ZWave binding updates

I have now merged the development version of the ZWave binding into master, so it will be available in the 2.4 snapshot version. If you are using the ZWave binding, please read this post as the binding contains some breaking changes so you will need to manually update your configuration. Firstly though - the major enhancements (there are tons more smaller updates) -: Security has been added using the S0 security class. This should allow all devices supporting security to be included into the…

[will_stewart1a (Will)]

Ok, have completed this process, am back to normal with all other sensors and effectors, and yet am still having issues with all of the MS11+ motion sensors generating events (not just one or two). They do generate reports, though those are not turning into events;

MS110+ motion sensor

2018-09-29 06:56:02.007 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Application Command Request (ALIVE:DONE)
2018-09-29 06:56:02.007 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: resetResendCount initComplete=true isDead=false
2018-09-29 06:56:02.007 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-09-29 06:56:02.007 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: SECURITY not supported
2018-09-29 06:56:02.008 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 23: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT
2018-09-29 06:56:02.008 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 23: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-09-29 06:56:02.008 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 23: Alarm Type = BURGLAR (0)
2018-09-29 06:56:02.008 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-09-29 06:56:02.008 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-09-29 06:56:02.008 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 23: Alarm converter processing NOTIFICATION
2018-09-29 06:56:02.008 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 23: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 06:56:02.008 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Commands processed 1.
2018-09-29 06:56:02.008 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 23: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@2a423973.
2018-09-29 06:56:02.008 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 06:56:02.009 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 06:56:02.009 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-09-29 06:56:02.009 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Yet both my Zooz 4 in 1 motion sensor and Aeon Gen2 4 in 1 motion sensors motion reports are being recognized as motion events;

Aeon Gen2

2018-09-29 06:44:20.572 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)
2018-09-29 06:44:20.572 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false
2018-09-29 06:44:20.572 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2018-09-29 06:44:20.572 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY not supported
2018-09-29 06:44:20.572 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2018-09-29 06:44:20.572 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Unknown, value=255
2018-09-29 06:44:20.573 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2018-09-29 06:44:20.573 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 255
2018-09-29 06:44:20.573 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:1645796be4b:node7:sensor_binary to ON [OnOffType]
2018-09-29 06:44:20.573 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.
2018-09-29 06:44:20.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6dc3f993.
2018-09-29 06:44:20.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 06:44:20.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 06:44:20.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-09-29 06:44:20.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Resulting event;

2018-09-29 06:44:20.574 [vent.ItemStateChangedEvent] - KitchenMotionSensor changed from OFF to ON

I have restarted OH2 every day for the last several days (as battery powered sensors can take time to fully initialize), but this behavior has not resolved. What would be the best thing for me to do next?

[chris (Chris Jackson)]

I will update the database to resolve this. Before I do, can you confirm if there is also a tamper alarm with this device, and if so can you provide the same log you did for the MS100 above.

Thanks

[will_stewart1a (Will)]

I believe this represents the tamper alarm, though I am rushed to get out the door;

2018-09-29 09:38:22.158 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:UPDATE_NEIGHBORS)
2018-09-29 09:38:22.158 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 19: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-09-29 09:38:22.158 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 19: SECURITY not supported
2018-09-29 09:38:22.158 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 19: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT
2018-09-29 09:38:22.158 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 19: NOTIFICATION report - 0 = 0, event=9, status=255, plen=0
2018-09-29 09:38:22.158 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 19: Alarm Type = BURGLAR (0)
2018-09-29 09:38:22.158 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-09-29 09:38:22.158 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 19: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-09-29 09:38:22.159 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 19: Alarm converter processing NOTIFICATION
2018-09-29 09:38:22.159 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 19: Alarm converter NOTIFICATION event is 9, type OnOffType
2018-09-29 09:38:22.159 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 19: Alarm converter NOTIFICATION event has no notification for BURGLAR
2018-09-29 09:38:22.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 19: Commands processed 1.
2018-09-29 09:38:22.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 19: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3305e480.
2018-09-29 09:38:22.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 09:38:22.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

[will_stewart1a (Will)]

And for some reason, the Zooz 4 in 1 tamper alarm may be in a similar situation. While it does not seem to be showing up explicitly after I pick it up and move it around, I do receive multiple alarms in short succession (the latter of which is timed to when I actually picked it up), which it is not configured to do, as trigger interval is set to 60 seconds;

2018-09-29 09:53:29.525 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-09-29 09:53:29.525 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-09-29 09:53:29.525 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-09-29 09:53:29.525 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-09-29 09:53:29.525 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-09-29 09:53:29.525 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 7 = 255, event=8, status=255, plen=0
2018-09-29 09:53:29.525 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (7)
2018-09-29 09:53:29.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-09-29 09:53:29.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-09-29 09:53:29.526 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-09-29 09:53:29.526 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 09:53:29.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:1645796be4b:node2:alarm_motion to ON [OnOffType]
2018-09-29 09:53:29.527 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-09-29 09:53:29.527 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 09:53:29.527 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-09-29 09:53:29.527 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@4cd93486.
2018-09-29 09:53:29.527 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 09:53:29.527 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

then

2018-09-29 09:53:38.448 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-09-29 09:53:38.448 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-09-29 09:53:38.449 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-09-29 09:53:38.449 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-09-29 09:53:38.449 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-09-29 09:53:38.449 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 7 = 255, event=8, status=255, plen=0
2018-09-29 09:53:38.449 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (7)
2018-09-29 09:53:38.449 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-09-29 09:53:38.449 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-09-29 09:53:38.449 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-09-29 09:53:38.449 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 09:53:38.449 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:1645796be4b:node2:alarm_motion to ON [OnOffType]
2018-09-29 09:53:38.450 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-09-29 09:53:38.450 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 09:53:38.450 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-09-29 09:53:38.450 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6a3e0c8b.
2018-09-29 09:53:38.450 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 09:53:38.450 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

then

2018-09-29 09:53:47.752 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-09-29 09:53:47.752 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-09-29 09:53:47.752 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-09-29 09:53:47.752 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-09-29 09:53:47.752 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-09-29 09:53:47.752 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 7 = 255, event=8, status=255, plen=0
2018-09-29 09:53:47.752 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (7)
2018-09-29 09:53:47.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-09-29 09:53:47.753 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-09-29 09:53:47.753 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-09-29 09:53:47.753 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 09:53:47.753 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:1645796be4b:node2:alarm_motion to ON [OnOffType]
2018-09-29 09:53:47.754 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-09-29 09:53:47.754 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-09-29 09:53:47.754 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-09-29 09:53:47.754 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@2cf36b11.
2018-09-29 09:53:47.754 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-29 09:53:47.754 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

[chris (Chris Jackson)]

Unless I missed one, they are all the same event 8, which is motion alarm.

I will update the MS-100 tamper alarm as well - thanks.

[will_stewart1a (Will)]

Ok, I believe the multiple motion alarm reports are due to the fact that I associate the Node 2 Zooz with light nodes 17 and 20, both of which acknowledge they receive and act on the commands. Wife is dragging me out the door physically now, so…

[chris (Chris Jackson)]

@will_stewart1a

I believe the multiple motion alarm reports are due to the fact that I associate the Node 2 Zooz with light nodes 17 and 20,

It shouldn’t cause this as those commands will go directly to the respective devices. However, what will cause it is if you have the binding in more than 1 association group.

I’ve updated the binding and once the CI checks are complete I’ll merge and kick off a build, so you should be able to update once your wife allows you to return

Note that the channel changed to alarm_motion, and I’ve also added alarm_tamper. You will need to delete this thing, and add it back again so that the binding gets the updated thing configuration (don’t exclude the device - just delete/add).

Add new tamper notification type and update MS-100+

[Miguel_De_Anda]

i’ve having issues with the ms-100+ devices using 2.5.0.M1. i added the devices fine and they update when i tap the button 4 or 5 times to wake them up. i think i’ve tried every combination of “basic set value” and “enable disable basic set” and “motion timeout interval” and “wakeup interval” i feel is reasonable and while i see the blue led light up on motion, it doesn’t seem to get logged in oh2. how did you enable such verbose logging?