OH3 - HS-MS100+ - HomeSeer Z-Wave Plus Motion Sensor

Setup, Configuration and Use Migration
,
1

openHAB 3.2.0 - Release Build
Platform = Raspberry Pi 3 Model B Rev 1.2
Release = Raspbian GNU/Linux 11 (bullseye)
Kernel = Linux 5.15.30-v7+
Memory = Free: 0.24GB (25%), Used: 0.70GB (75%), Total: 0.95GB
Swap = Free: 2.29GB (100%), Used: 0.00GB (0%), Total: 2.29GB
Root = Free: 9.26GB (67%), Used: 4.43GB (33%), Total: 14.32GB

I have several HomeSeer HS-MS100+ motion sensors that were working on 2.5 but are no longer working on OpenHAB 3.2. They did configure and the Items are able to be setup, or re-setup. But when they are triggered nothing seems to happen.

These are the older models from several years ago. I think HomeSeer has released a new version in the last couple of years.

  • zwave_class_basic = BASIC_TYPE_ROUTING_SLAVE
  • zwave_class_generic = GENERIC_TYPE_SENSOR_NOTIFICATION
  • zwave_frequent = false
  • zwave_lastwakeup = 2022-04-16T18:51:41Z
  • modelId = HS-MS100+
  • zwave_listening = false
  • zwave_plus_devicetype = NODE_TYPE_ZWAVEPLUS_NODE
  • zwave_version = 1.1
  • manufacturerId = 000C
  • manufacturerRef = 0201:0009
  • dbReference = 802
  • zwave_deviceid = 9
  • zwave_nodeid = 22
  • defaultAssociations = 1
  • vendor = HomeSeer Technologies
  • zwave_routing = true
  • zwave_plus_roletype = ROLE_TYPE_SLAVE_SLEEPING_REPORTING
  • zwave_beaming = true
  • zwave_secure = false
  • zwave_class_specific = SPECIFIC_TYPE_NOTIFICATION_SENSOR
  • zwave_devicetype = 513
  • zwave_manufacturer = 12

Debug log when Motion is triggered shows the following, But I don’t know what it means.

2022-04-16 15:27:33.971 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 6: Application Command Request (ALIVE:DONE)
2022-04-16 15:27:33.973 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 6: resetResendCount initComplete=true isDead=false
2022-04-16 15:27:33.977 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 6: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2022-04-16 15:27:33.979 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 6: SECURITY not supported
2022-04-16 15:27:33.982 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 6: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT
2022-04-16 15:27:33.985 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 6: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2022-04-16 15:27:33.988 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 6: Alarm Type = BURGLAR (0)
2022-04-16 15:27:33.991 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2022-04-16 15:27:33.994 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2022-04-16 15:27:33.997 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 6: Commands processed 1.
2022-04-16 15:27:34.000 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 6: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12181ec.
2

It looks to me that the device DB was modified in May 2020 so the rather than the motion being detected from the ALARM CC it was moved to the Sensor Binary. From the short Debug log, the device is sending the motion to the Alarm CC.

Maybe there is a way to use Association group 2 (that should/could be setup to get a basic set on Motion). The DB could be changed back to the Alarm CC (or maybe in addition), but the person that made the change could be affected. I’m just not sure. Need to ask @chris

Bob

edit: also what is the value of parameter 14? If zero, try one

3

Changing Parameter 14 to 1 doesn’t seem to help. It was zero.

4

Worth a shot. I do not have the device, so was just speculating based on the DB entry.

Also a long shot, but are both tamper and motion linked to an item (and show no motion/change?) Also is parameter 12 set at 8 (for maximum sensitivity)?

Bob

edit: Also press the button in the back once.