I am trying to use this sensor on openHAB 2. I am eventually able to get sensor readings from it, but the motion detection does not seem to work. I noticed and have played with several parameters including the report type, associate groups, wakeup, and timeouts, but to no avail. What kind of configuration is required of this device to make it work well?
The device is plugged in via USB, not on battery, and was set up plugged in.
OK, I set up zwave debugging and can see that something is happening upon motion. It’s not clear if it’s an alert or the binary switch is being updated. Are people using the alert channel or the switch channel for this? And how do you get the state of that channel in a rule? The state attribute doesn’t seem to exist on the switch channel at least.
This is using the NOTIFICATION class so you can’t decode it the same as an alarm. The relevant parts are the 07 08. 07 means it’s a HOME_SECURITY notification, and the 00 after means it’s reset, and the 08 after means it’s a motion event.
I will take a look over this in the coming day or two - I have exactly the same issue with the Fibaro FGMS. It should be possible to adjust the settings to use older command classes but I’d prefer to make it work with a more default configuration.
I would like to share my experience with MS6 ZW100 version1.7 under OH2:
all sensors are working fine
setting the motion sensor reset time to 30s works fine (same settings from mhilbush, but working on Batteries)
when I change the reset time to 60s, 120s or to 240s, the reset does not happen. OH2 keep showing Triggered at all times.
Furthermore, the MS6 sends cyclic reports corresponding to the reset time in param 3, each time with sensor_binary_report = 255. Only when param is set to 30s, the `` is setback.
I assume this is something that has to do with byte ordering on the MS6.