OH3.1 M4 : HS-DS100+ Zwave secure inclusion - no device alerts; insecure inclusion - device unknown but get alerts (debug)

rbergen · May 9, 2021, 12:18am

Hello,

I have a HS-DS100+ Window/Door sensor that has different issues depending if it is secure included or insecure included - either way, it doesn’t work.

I’m running OH3.1 M4 with the Zwave 3.1M4 binding

ZWave controller: Aeotec Gen zstick gen 5

Zwave Debug is enabled

log:list | grep ~                                                                                                                                                                                                           openhab> log:list | grep -i wave
org.openhab.binding.zwave                          │ DEBUG

Secure inclusion:
When I perform a soft-secure inclusion, the device is recognized properly as a HomeSeer HS-DS100+, however when I perform any trigger operations (tamper, door open/closed, etc), there are no updates in the logs.
Security inclusion shows it is successful, but there are no logs showing up on any trigger, even with debug enabled

(Had to upload / attach logs due to character post limit)
zwave.txt (66.3 KB)

No further logs are received, no matter what

Non-secure inclusion
When I take out the Aeotec zstick from the raspberry pi and perform an inclusion next to the device by pushing the button on the USB stick, it gets included insecurely. In OH3, I perform an inclusion and select Scan, and the device that I included through hardware shows up in the list, but the vendor is Unknown.

Error messages I receive are:

2021-05-09 01:40:10.290 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery could not resolve to a thingType! Manufacturer data not known.
2021-05-09 01:40:18.925 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: MANUFACTURER not set
2021-05-09 01:40:18.928 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Controller status changed to ONLINE.
2021-05-09 01:40:18.930 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Controller is ONLINE. Starting device initialisation.
2021-05-09 01:40:18.954 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating node properties.
2021-05-09 01:40:18.961 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating node properties. MAN=2147483647

Full logs:

2021-05-09 01:55:54.762 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Application Command Request (ALIVE:SECURITY_REPORT)
2021-05-09 01:55:54.764 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2021-05-09 01:55:54.766 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: SECURITY NOT required on COMMAND_CLASS_ALARM
2021-05-09 01:55:54.767 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2021-05-09 01:55:54.769 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=23, status=255, plen=0
2021-05-09 01:55:54.771 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = ACCESS_CONTROL (0)
2021-05-09 01:55:54.773 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2021-05-09 01:55:54.774 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2021-05-09 01:55:54.775 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.
2021-05-09 01:55:54.776 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@c65d23.
2021-05-09 01:55:54.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Application Command Request (ALIVE:SECURITY_REPORT)
2021-05-09 01:55:54.784 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2021-05-09 01:55:54.785 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
2021-05-09 01:55:54.786 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Received COMMAND_CLASS_SENSOR_BINARY V0 SENSOR_BINARY_REPORT
2021-05-09 01:55:54.787 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Sensor Binary report, type=Unknown, value=0
2021-05-09 01:55:54.788 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2021-05-09 01:55:54.789 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2021-05-09 01:55:54.790 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.
2021-05-09 01:55:54.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@14aec1a.
2021-05-09 01:58:49.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling...
2021-05-09 01:58:49.580 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete
2021-05-09 02:01:05.419 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Application Command Request (ALIVE:SECURITY_REPORT)
2021-05-09 02:01:05.420 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2021-05-09 02:01:05.421 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: SECURITY NOT required on COMMAND_CLASS_BATTERY
2021-05-09 02:01:05.423 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Received COMMAND_CLASS_BATTERY V0 BATTERY_REPORT
2021-05-09 02:01:05.424 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 11: Battery report value = 100
2021-05-09 02:01:05.425 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2021-05-09 02:01:05.427 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BATTERY, value=100
2021-05-09 02:01:05.428 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.
2021-05-09 02:01:05.430 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1dc2bc5.
2021-05-09 02:01:05.875 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Application Command Request (ALIVE:SECURITY_REPORT)
2021-05-09 02:01:05.877 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2021-05-09 02:01:05.878 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: SECURITY NOT required on COMMAND_CLASS_ALARM
2021-05-09 02:01:05.880 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Received COMMAND_CLASS_ALARM V0 NOTIFICATION_REPORT
2021-05-09 02:01:05.881 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2021-05-09 02:01:05.882 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = BURGLAR (0)
2021-05-09 02:01:05.884 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2021-05-09 02:01:05.885 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2021-05-09 02:01:05.887 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.
2021-05-09 02:01:05.888 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@f19e60.
2021-05-09 02:01:06.311 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Application Command Request (ALIVE:SECURITY_REPORT)
2021-05-09 02:01:06.312 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2021-05-09 02:01:06.314 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
2021-05-09 02:01:06.316 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Received COMMAND_CLASS_SENSOR_BINARY V0 SENSOR_BINARY_REPORT
2021-05-09 02:01:06.318 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Sensor Binary report, type=Unknown, value=0
2021-05-09 02:01:06.320 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2021-05-09 02:01:06.322 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2021-05-09 02:01:06.323 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.
2021-05-09 02:01:06.324 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@caf358.
2021-05-09 02:01:06.717 [DEBUG] [serialmessage.RemoveNodeMessageClass] - NODE 11: Removing slave.
2021-05-09 02:01:06.718 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveInclusionEvent
2021-05-09 02:01:06.723 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Node Init transaction completed with response null
2021-05-09 02:01:06.724 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Skipping initialization thread, process stopped by controller
2021-05-09 02:01:06.777 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveInclusionEvent

When I perform any trigger options (battery report, tamper, door open/closed, etc) I can see them in the debug logs, such as:

2021-05-09 02:01:05.427 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BATTERY, value=100
2021-05-09 02:01:05.428 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.

At this point, I’m not sure what is easier to fix:
Option 1) Secure inclusion: Why the events are not being seen at all in the logs
Option 2) Insecure inclusion: Do I just need to add it to the zwave database? But why would it have a different manufacturer code on secure / insecure inclusion?
In the logs, it said:
Updating node properties. MAN=2147483647
Is that the manufacturer code that needs to be updated or added in the DB? Can this manufacturer code just be linked to the other one in the DB without having to reenter everything?
I’ve never added something to the DB before, so I want to make sure I’m doing it correctly.

Option 3) ???

Thanks!

rbergen · May 9, 2021, 2:49am

I managed to get the secure inclusion to work properly.

One thing that I noticed is when I tried to Heal the device, it would say it had not yet finished initializing, despite hitting the button once (many times) and triple click (many times) and each time I could see in the debugs that it was communicating.

I changed the following settings, not sure which, if any, or if all of them helped:
Enable basic SET commands: 1 (was 0)
Association Groups 1: Controller (was not explicitly set)
Association Groups 2: Controller (was not explicitly set)
Wakeup Node: 1 (was 0, 1 is my controller)

Even so, the heal command would still say it was not initialized.

Can not start heal as initialisation is not complete (VERSION).

Just as a guess, I held the button down for 5 seconds (this is not documented in the manual anywhere! This was just a guess). There were A LOT of logs generated in debug when I did this.

Ran another heal, and this time it said it was not full initialized, but had a different message in the brackets beside (Set association)

Can not start heal as initialisation is not complete (SET_ASSOCIATION).

I figured I was on the right track, so I held down the button for a second time for 5 seconds, and this time, afterwards the heal worked successfully. I then tried creating some alerts, and they all started to come through.

Bruce_Osborne · May 9, 2021, 6:16am

Please update the community supported database with these wake up information. We have found that at times the vendor manual is incorrect or incomplete.

For zwave plus devices the controller should only be set on the for group. That is its purpose within the standard.

system · June 19, 2021, 10:17pm

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.