HS-MS100+ not sensing motion

Hi all,

I picked up one of these cool little "eyeball" motion sensors from Homeseer.... a HS-MS100+ Z-Wave sensor.

Using my Z-stick and Indigo 7.3.1, I was able to connect to it and see it as 005 - Motion Sensor in the list of device.s

However, try as I might, the thing will not detect motion. I can move it around, move around it, etc. The log doesn't show any activity and the device state never goes from "off" to "on."

I tried removing the device and re-adding it to no avail

Has anyone used this little guy successfully?

P.S. How do I tell Indigo to put my Z-wave stick into exclusion mode so I can remove the device?

Thanks. I was able to "exclude" it, but when I re-added it, the address associated with it increased by one from the last time I added it.

Speaking of, it's still not activating when I move it or move around it. Here's the log showing my activation:

Code: Select all

May 26, 2019 at 7:50:33 AM
   Z-Wave                          started controller inclusion mode with encryption
   Z-Wave                          controller included module: 006 - Notification Sensor
   Z-Wave                          querying module for encryption support
   Z-Wave                          starting encryption key exchange with module
   Z-Wave                          completed encryption key exchange with module
   Z-Wave                          stopped controller inclusion mode
   Z-Wave                          Syncing - started for "006 - Notification Sensor"
   Z-Wave                          Syncing - retrieved module neighbors list: 3
   Z-Wave                          Syncing - assigning return route to "006 - Notification Sensor"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: HomeSeer - 000C, Motion Sensor (HS-MS100+) - 02010009
   Z-Wave                          Syncing - retrieved protocol version 4.61, app version 1.01
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
   Z-Wave                          Syncing - retrieved command classes: 80v1 84v2 85v1 86v1 55v1 98v1 59v1 5Av1 5Ev1 9Fv1 20v1 30v1 6Cv1 70v1 71v1 72v1 73v1 7Av1
   Z-Wave                          Syncing - retrieved encrypt commands: 80 30 84 85 86 6C 70 71 72 73 59 5A 7A
   Z-Wave                          Syncing - retrieved capabilities: routing, battery, beaming, security, waking
   Z-Wave                          Syncing - retrieved wake interval of 0 minutes
   Z-Wave                          Syncing - device "006 - Notification Sensor" wake interval changed to 60 minutes
   Z-Wave                          Syncing - retrieved group 1 associations: []
   Z-Wave                          Syncing - retrieved group 2 associations: []
   Z-Wave                          Syncing - added group 1 association to interface
   Z-Wave                          Syncing - retrieved battery level of 100%
   Z-Wave                          Syncing - created device "006 - Motion Sensor"
   Z-Wave                          Syncing - complete

The notes for 7.3 indicate this device is supported, so I'm wondering if I just have a non-working/bad device?

[matt (support)]

That one should work with Indigo. I suspect something funny is occurring with how it works when encryption is enabled. Try excluding it from Indigo then re-include it without encryption to see if it then works.

If it doesn't then turn on Indigo's Z-Wave debug logging checkbox (via the Interfaces->Z-Wave->Configure... menu item) and trip the motion sensor a few times then copy/paste the Event Log results into a reply for me.

Thanks Matt.

I put my Z-Wave stick in exclusion mode and tapped the button on the motion sensor three times, and got the message that the module was excluded.

I then put the Z-Wave stick in inclusion mode (NOT encryption) and taped the button once on the motion sensor. It was associated.

I then added a new device (007 - Notification Sensor) and pressed Sync, and go this:

Code: Select all

May 26, 2019 at 6:56:25 PM
   Z-Wave                          Syncing - started for "007 - Notification Sensor"
   Z-Wave                          Syncing - retrieved module neighbors list: 3
   Z-Wave                          Syncing - assigning return route to "007 - Notification Sensor"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: HomeSeer - 000C, Motion Sensor (HS-MS100+) - 02010009
   Z-Wave                          Syncing - retrieved protocol version 4.61, app version 1.01
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
   Z-Wave                          Syncing - retrieved command classes: 80v1 84v2 85v1 86v1 55v1 59v1 5Av1 5Ev1 20v1 30v1 6Cv1 70v1 71v1 72v1 73v1 7Av1
   Z-Wave                          Syncing - retrieved encrypt commands: - none -
   Z-Wave                          Syncing - retrieved capabilities: routing, battery, beaming, waking
   Z-Wave                          Syncing - retrieved wake interval of 0 minutes
   Z-Wave                          Syncing - device "007 - Notification Sensor" wake interval changed to 60 minutes
   Z-Wave                          Syncing - retrieved group 1 associations: []
   Z-Wave                          Syncing - retrieved group 2 associations: []
   Z-Wave                          Syncing - added group 1 association to interface
   Z-Wave                          Syncing - retrieved battery level of 100%
   Z-Wave                          Syncing - created device "007 - Motion Sensor"
   Z-Wave                          Syncing - complete
   Z-Wave                          received "007 - Motion Sensor" status update battery level 100%
   Z-Wave                          received "007 - Motion Sensor" status update is on


Now the sensor's state is stuck on "on" in the devices list. Moving it around or moving around it does nothing.

This sure seems like a bad sensor, but I'll await your feedback.

[matt (support)]

Sounds like it might be a lemon, but did you try it with debug logging enabled (see my post above) to make sure it isn't sending a command Indigo just isn't routing to the device correctly?

Sorry Matt, I missed that one completely.

I just turned on Z-Wave debugging as you indicated. Here's the output:

Code: Select all

  Z-Wave Debug                    stopping node healing thread
   Z-Wave Debug                    stopping node status polling thread
   Z-Wave Debug                    stopped zwave packet parser thread
   Z-Wave                          connection reset requested
   Z-Wave Debug                    starting serial connection loop
   Z-Wave Debug                    starting zwave packet parser thread
   Z-Wave Debug                    SENT getVersion: 01 03 00 15 E9
   Z-Wave Debug                    RCVD getVersion: 01 10 01 15 5A 2D 57 61 76 65 20 33 2E 39 35 00 01 99
   Z-Wave Debug                    . .  getVersion: Z-Wave 3.95 static controller
   Z-Wave Debug                    SENT getHomeID: 01 03 00 20 DC
   Z-Wave Debug                    RCVD getHomeID: 01 08 01 20 E0 3B 8A 4A 01 CC
   Z-Wave Debug                    . .  getHomeID: E03B8A4A, nodeID: 001
   Z-Wave Debug                    SENT getInterfaceFeatures: 01 03 00 05 F9
   Z-Wave Debug                    RCVD getInterfaceFeatures: 01 04 01 05 18 E7
   Z-Wave Debug                    . .  getInterfaceFeatures: 18
   Z-Wave Debug                    SENT getInterfaceApiCapabilities: 01 03 00 07 FB
   Z-Wave Debug                    RCVD getInterfaceApiCapabilities: 01 2B 01 07 01 00 00 86 01 01 00 5A FE 81 FF 88 4F 1F 00 00 FB 9F 7D A0 67 00 00 80 00 80 86 00 00 00 E8 73 00 00 0E 00 00 60 00 00 FA
   Z-Wave Debug                    . .  getInterfaceApiCapabilities: supportedFuncIDs: 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 1C 20 21 22 23 24 27 29 2A 2B 2C 2D 41 42 44 45 46 47 48 49 4A 4B 4C 4D 50 51 53 54 55 56 57 5E 60 61 62 63 66 67 80 90 92 93 98 B4 B6 B7 B8 B9 BA BD BE BF D2 D3 D4 EE EF
   Z-Wave Debug                    . .  getInterfaceApiCapabilities: serialApi 1.00, manufactureId 0086, productType 0101, productId 005A
   Z-Wave                          connected to Z-Stick Plus (ZW090) interface on /dev/cu.usbmodem3A21 (firmware 1.00)
   Z-Wave Debug                    SENT forceSUC: 01 05 00 54 01 01 AE
   Z-Wave Debug                    RCVD forceSUC: 01 04 01 54 01 AF
   Z-Wave Debug                    SENT getInitialNodeData: 01 03 00 02 FE
   Z-Wave Debug                    RCVD getInitialNodeData: 01 25 01 02 05 08 1D 4D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00 81
   Z-Wave Debug                    . .  getInitialNodeData: is static update controller
   Z-Wave Debug                    . .  getInitialNodeData: [1, 3, 4, 7]
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 01 BB
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 93 16 01 02 02 01 33
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 001, class name: Static Computer Controller
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Static Controller : Static Controller : Static Computer Controller (02 : 02 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: beaming
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 03 B9
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 D3 9C 01 04 07 01 FA
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 003, class name: Notification Sensor
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: routing, beaming
   Z-Wave Debug                    overriding node 003 type from zwOnOffSensorType to zwRelayType
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 04 BE
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 004, class name: Notification Sensor
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: routing, beaming
   Z-Wave                          found module included in controller with no matching device (missing or disabled): 004 - Notification Sensor
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 07 BD
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 007, class name: Notification Sensor
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: routing, beaming
   Z-Wave Debug                    starting node healing thread
   Z-Wave Debug                    starting node status polling thread


Again, moving the sensor or moving in front of it doesn't have any effect. The output stays static, and there is no visual indication in the lower left hand corner of the main Indigo window that any communication is happening.

I'll contact HomeSeer tomorrow.

Following up...

I called SmartHome this morning (I actually bought it from them, not HomeSeer) and they told me to call HomeSeer. I just did that and the nice tech indicated that since he didn't really know Indigo, he could only do some basic troubleshooting steps, which ended up with the same result: I can "pair" the HS-MS100+ to my Z-Wave stick, but after that it doesn't respond.

Just to clarify, someone has actually tested this device with Indigo 7.3, right?

[matt (support)]

I checked my notes and we added the definition for this one based on the technical details from a user's submission (from Indigo) and from its manual. Based on the manual by default it should send the Basic Set command when motion is detected (and then the clear command 10 minutes after motion is last detected). If you aren't seeing any commands logged (with debug logging enabled) around the time motion is tripped or 10 minutes after motion was last tripped, then I think the module isn't working correctly. If Indigo is showing the state is stuck on, then put it in a desk drawer for an hour or so and see if it ever sends out the clear message.

If it were sending a command different than what Indigo was expecting (meaning Indigo's device definition needs tweaking) then it would be possible Indigo wouldn't update the device state or show the command in the log, but that is only true if debug logging isn't enabled. If debug logging is enabled then you should be seeing some type of command coming from the module when motion is tripped (and then 10 minutes later when it clears).

Following up here, Matt.

I had a chat with the guys at HomeSeer explaining the issue I'm having with the HS-MS100+ and even sent him a link to this thread. his response:

The MS100 uses the Sensor Binary and Notification command classes.

I'm not a Z-Wave expert, and I don't know if this has any bearing on why it's not working.

[matt (support)]

Indigo's definition for the HS-MS100+ should catch both of those commands. If you aren't seeing any commands coming from it with debug logging enabled then I believe it isn't working.

Thanks for confirming, Matt. I've started a replacement process with SmartHome and expect to have another one here soon. I'll post on this thread when I have the replacement.

I just received my replacement HS-MS100+ from SmartHome and unfortunately, the problem persists. No motion detected, and the device stays in an on state in Indigo 7.3.1.

Really would like to see this cool little motion sensor work though. Jay/Matt, any other suggestions? I would be happy to ship it to you if you guys think it would help.

[matt (support)]

Well bummer. I'm not sure what is going on with this one. Can you try the following steps (I know you've done most of these before, but let's start clean and run a full suite of tests):

1) Exclude the module from the Z-Stick.
2) Clear the Event Log window in Indigo.
3) Enable Indigo's Z-Wave Debug logging checkbox (via Interfaces->Z-Wave->Configure... menu item).
3) Re-include the module withOUT encryption enabled.
4) Re-sync the module.
5) Copy/paste the Event Log results into a forum reply.
6) Put the module into a desk drawer or closet where it is impossible to trip for 30+ minutes.
7) Clear the Event Log window.
8) Open the drawer and wave at the motion sensor.
9) Copy/paste the Event Log window results into another reply for me.
10) Wait 15 minutes.
11) If any additional commands come from the module copy/paste those from the log as well.

Matt,

I followed your instructions. Thank you for that. It turns out that with some patience, the device IS working.

Code: Select all

Jun 12, 2019 at 9:00:49 AM
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 07 08 00 72
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
   Z-Wave Debug                    . .  requestAlarmSensorStatus: defnStatusByte 255
   Z-Wave                          received "010 - Motion Sensor" status update is on

Jun 12, 2019 at 9:09:39 AM
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 10 00 04 00 0B 0A 71 05 00 00 00 FF 07 00 01 08 6F
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
   Z-Wave Debug                    . .  requestAlarmSensorStatus: defnStatusByte 0
   Z-Wave                          received "010 - Motion Sensor" status update is off


But it took almost 10 minutes for the device to go back from the ON state to the OFF state!

That seems like an extraordinary time for a motion sensor to go from the ON to OFF state right after being triggered and then placed into a dark drawer with no movement.

So I did some Googling and found this:

https://cache-m2.smarthome.com/manuals/ ... -guide.pdf

Page 2 shows an advanced configuration that allows the setting of, among other things, the timeout in seconds.

I don't see a way in Indigo to set this up however. Is that possible?

Thanks. I'm an Insteon guy so Z-Wave is very new to me. I discovered this setting under the Interfaces menu and have successfully changed the setting! Awesome stuff. Thank you.

Sorry for the false alarm guys. It looks like this puppy is indeed working well after all!