One thing detected by z-stick but Openhab does almost nothing with it

Tags: #<Tag:0x00007f4342783070>

Here is the log in DEBUG mode (leran that yeah!). I understand It goes on and after off but I don’t get where where the signal gets lost between that the info log from OH stating it changed state (and my rule still doesn’t work).

I checked the items for this device (in Habmin) and they look normal as they are similar (type switch category motion)

21:07:09.848 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 FF 0C
21:07:09.867 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 FF 0C
21:07:09.876 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
21:07:09.885 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
21:07:09.893 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
21:07:09.902 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
21:07:09.910 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
21:07:09.918 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
21:07:09.926 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
21:07:09.935 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
21:07:09.943 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Motion, value=255
21:07:09.951 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
21:07:09.959 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 255
21:07:09.969 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
21:07:09.977 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@2fdd7c64.
21:07:09.985 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
21:07:09.994 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
21:07:10.002 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
21:07:10.010 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
21:07:25.150 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 18 04 30 03 00 0C D2
21:07:25.153 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_7a2a2811_serial_sof changed from 4530 to 4531
21:07:25.160 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 00 0C
21:07:25.173 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 00 0C
21:07:25.181 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
21:07:25.189 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
21:07:25.197 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
21:07:25.207 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
21:07:25.214 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
21:07:25.222 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
21:07:25.230 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
21:07:25.240 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
21:07:25.248 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Motion, value=0
21:07:25.256 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
21:07:25.264 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 0
21:07:25.274 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
21:07:25.282 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@22c69508.
21:07:25.290 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
21:07:25.298 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
21:07:25.307 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
21:07:25.315 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Is this the device you have -:

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

If so, the database is configured to use the ALARM / NOTIFICATION reports, but your device is sending a more basic report from what I see in this log. My assumption is that the database is working fine for most people and that your device needs some configuration changing so that it sends the right reports.

This is part of the ZWave fun - there are often many ways for a device to send the same report…

1 Like

Yes, this is exactly my device!

In the Habmin, category is listed as motion instead of alarm but from what I understand from the documentation it is just data for tagging and user interface. And I have another brand of motion detector (working) and parameters in configuration are the same so I don’t understand where to look at now.

From line 21:07:09.959 I understand it send the data as a switch but I can’t understand where to look and change after and where it shows.

What is my next step?

Probably there’s a configuration parameter that allows you to select what commands the device will send - I’d start by reading the manual to see if that describes anything. It’s possible the database is wrong, but then this device would never work for anyway which I think is unlikely.

I don’t see anything like that on the manual.
https://homeseer.com/wp-content/uploads/2018/01/HS-MS100v1b.pdf

This is the log of my other type of motion sensors that is working:

11:08:12.533 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=20, callback=0, payload=00 14 0A 71 05 00 00 00 FF 07 00 00 00
11:08:12.538 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=20, callback=0, payload=00 14 0A 71 05 00 00 00 FF 07 00 00 00
11:08:12.542 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
11:08:12.546 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DONE)
11:08:12.554 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 20: resetResendCount initComplete=true isDead=false
11:08:12.558 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 20: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
11:08:12.562 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 20: SECURITY not supported
11:08:12.566 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 20: Received COMMAND_CLASS_ALARM V3 NOTIFICATION_REPORT
11:08:12.571 [DEBUG] [l.commandclass.ZWaveAlarmCommandClass] - NODE 20: NOTIFICATION report - 0 = 0, event=0, status=255, plen=0
11:08:12.575 [DEBUG] [l.commandclass.ZWaveAlarmCommandClass] - NODE 20: Alarm Type = BURGLAR (0)
11:08:12.579 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveAlarmValueEvent
11:08:12.583 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 20: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
11:08:12.588 [DEBUG] [nternal.converter.ZWaveAlarmConverter] - NODE 20: Alarm converter processing NOTIFICATION
11:08:12.592 [DEBUG] [nternal.converter.ZWaveAlarmConverter] - NODE 20: Alarm converter NOTIFICATION event is 0, type OnOffType
11:08:12.596 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating channel state zwave:device:7a2a2811:node20:alarm_motion to OFF [OnOffType]
11:08:12.601 [DEBUG] [nternal.converter.ZWaveAlarmConverter] - NODE 20: Alarm converter processing NOTIFICATION

I see the alarm notification you’re talking about. It doesn’t seem to be an option with the Home seer.

I went to the Homeseer forum about this device and nothing, it seems to be a quite new motion as the forum is not that old (2 years).
https://forums.homeseer.com/forum/homeseer-products-services/homeseer-z-wave-products/hs-ms100-motion-sensor

We can’t really compare what different devices do as, well, that are different :wink:

Can you provide the XML file for this node from the {userdata}/zwave folder.

1 Like

Here it is:

network_e7007344__node_24.xml (11.0 KB)

Thanks. One last question before I make a decision on this… Can you get a log where you cause the tamper alarm to trigger?

Here it is:

12:03:39.899 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_7a2a2811_serial_sof changed from 6127 to 6128
12:03:39.902 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 FF 08
12:03:39.907 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 FF 08
12:03:39.912 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
12:03:39.916 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
12:03:39.920 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
12:03:39.924 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
12:03:39.928 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
12:03:39.932 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
12:03:39.970 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 8
12:03:39.975 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Sensor Type is TAMPER
12:03:39.979 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Tamper, value=255
12:03:39.983 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
12:03:39.988 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 255
12:03:39.992 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
12:03:39.996 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@11b2306c.
12:03:40.000 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
12:03:40.005 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
12:03:40.009 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
12:03:40.013 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
12:03:45.342 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 18 04 30 03 00 08 D6
12:03:45.346 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_7a2a2811_serial_sof changed from 6128 to 6129
12:03:45.350 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 00 08
12:03:45.355 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 04 30 03 00 08
12:03:45.359 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
12:03:45.363 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
12:03:45.368 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
12:03:45.372 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
12:03:45.376 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
12:03:45.381 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
12:03:45.387 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 8
12:03:45.391 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - Sensor Type is TAMPER
12:03:45.395 [DEBUG] [ndclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Tamper, value=0
12:03:45.400 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
12:03:45.404 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 0
12:03:45.409 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
12:03:45.413 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6dd4a2a9.
12:03:45.417 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
12:03:45.421 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
12:03:45.425 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
12:03:45.429 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Curioustly, I removed the channel Motion to have a cleaner log bug I still see it:

Thanks.

I’m just a little worried there are two versions of this device - one using the newer notifications, and one using the older binary sensor commands - as your is.

I think what I will do is to change the database to match what we see in your device. I’ll make a note in the database referring to this so we have all the background if we find that someone has a version of this device that works differently.

Yes, you will. By removing the channel, you stop it being displayed in OH, but the device will still send the command and the binding will still process it - OH will just ignore it.

FYI @sihui

1 Like

Chris usually needs unfiltered logs.

Ok so to make it works I suppose I have to wait for a new database and update ?

My device is just a couple of month old so It may be the latest and greatest for now.

Unless you help with that it could be a long wait. This is a community maintained database.

I’ve already done the database update - in this instance it was better for me to do it as it also required stuff to be deleted.

1 Like

So waiting for the export, snapshot build, and then install the binding using the script. Correct?

Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community

Yes, I’ve already done the export, but need to update on github and do the build. This will be later tonight so it will be available tomorrow.

1 Like

Ok Thank,

My installation is on Synology, I suppose I have to do a manual update? Can you point me where I can go to have instruction and which files do I have to download/update to update and verify it is now working? This is unclear for me.

Thanks!

Robin

I know the README for the manual update script lists how to do it manually. I do not have the forum link handy right now.

1 Like

I have updated manually the zwave binding by 2.5.5.202005041107 and confirm that it works with the HomeSeer motion detector HS-MS100+.

Here is my test rule:

rule "Test Motion detector on"
when
	Item zwave_device_129fb235_node24_alarm_motion changed from OFF to ON
then
	logInfo('test', "It detects!")
end
rule "Test Motion detector off"
when
	Item zwave_device_129fb235_node24_alarm_motion changed from ON to OFF
then
	logInfo('test', "It sleeps!")
end
rule "test sleep"
when
	Item zwave_device_129fb235_node24_alarm_motion changed
then
	logInfo('Test Motion detector.rules', "Detects change!")
	zwave_device_129fb235_node22_switch_dimmer.sendCommand(50)
	
end

And the log:

openhab> list -s | grep -i zwave
248 │ Active   │  80 │ 2.5.5.202005041107     │ org.openhab.binding.zwave
openhab> log:tail
21:27:13.187 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_129fb235_serial_sof changed from 2183 to 2184
21:27:13.201 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_129fb235_serial_sof changed from 2184 to 2185
21:27:15.657 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_serial_zstick_129fb235_serial_sof changed from 2185 to 2186
21:27:15.668 [INFO ] [smarthome.event.ItemStateChangedEvent] - zwave_device_129fb235_node24_alarm_motion changed from OFF to ON
21:27:15.668 [INFO ] [g.eclipse.smarthome.model.script.test] - It detects!
21:27:15.668 [INFO ] [del.script.Test Motion detector.rules] - Detects change!

Thanks for all. Learned a lot:)

Robin

1 Like