Dear forum:
I've been buying a bunch of HomeSeer HS-MS100+ motion sensors, but HE recognizes them as Zooz ZSE18; that's the closest I can get. I see the specs/interface for the HomeSeer on GitHub, but I can't find a HE driver. Anyone have one? (Some day I'd like to learn how to write a driver.)
I don’t have any HomeSeer devices, but does the Zooz driver that go selected work? If so, is there anything that you are looking for that it doesn’t support?
That looks perfectly identical to the ZSE18, does the Zooz ZSE18 driver not work for it?
If not keep it on the ZSE18 driver, turn on info and debug logging then trigger motion a couple of time. It should produce some logs with all the events coming in. Post a screenshot of the logs.
If needed I could make a combo ZSE18 / MS100 driver.
I've given up on the HS-MS100+. It is too difficult to pair. If you succeed with the ZSE18 driver, all is well. Sometimes it wants to register as Ring. Yes, it is desirable to get a custom driver for it.
Right. The frustration arose from the little beasties refusing to pair at all.
I would be pleased to send you the data to help create a device driver, but I have none of the little beasties left.
Hey guys, I managed to pair four of the HS-MS100+'s with no issues to my hubitat (in powered, z-wave repeater mode). The hub had no issues finding them, although it didn't know which driver to use by default.
Though I'm happy to confirm the ZSE18 driver works absolutely perfect! (Though I only have used the motion detection and motion timeout features)
I am trying to include the HS-MS100+. I added several times as ZSE18 but no motion is logged. Both the MS100+ and the ZSE18 are indicated to have S2 security but the Hubitat inclusion does not bring up the option to select without security and may be including with security. I'm guessing, then that attempts to set parameters does not work? Parameter 14 to enable/disable Basic Set Command is 0=disable 1=enable with default 0 so this may be the problem. Anyway, here are the log results you asked for.
2025-04-15 08:34:26.055 PM
error
groovy.lang.MissingMethodException: No signature of method: DefaultDevice.secureCmd() is applicable for argument types: (hubitat.zwave.commands.configurationv1.ConfigurationGet) values: [ConfigurationGet(parameterNumber:14)]
I switched to your driver. Got better sync (able to specify main power) and state variables now listing but still no motion detection in log. Lost the commands sections that had in the prior driver to get parameter settings so I don't see how to set any parameters. Tried removing, excluding and re-including... no change. No longer have "Info" button to get that log entry. Only log entry that might be useful:
2025-04-16 11:53:51.004 AM
Turn on trace logging on my driver, wait long enough for the device to time out and then trigger motion on it. There should be SOMETHING that gets logged?
Please give a screenshot of logs, not text. Thanks.
Thanks! for working on this... Here's the result after turning trace on. Pressed the button on device 3 times to get it to communicate and got the one log entry "sensor value 255" which is what I think should see with motion. Get no entries afterwards of motion (through 10:51AM)... also LED on device never flashes as it used to do w/ motion when connected to homeseer hub. dev:3462025-04-17 10:13:48.918 AM
debug
Office Motion: Unhandled zwaveEvent: SensorBinaryReport(sensorValue:255, sensorType:12) (ep 0) dev:3462025-04-17 10:13:48.915 AM
trace
Office Motion: parse: zw device: 0E, command: 3003, payload: FF 0C , isMulticast: false --PARSED-- SensorBinaryReport(sensorValue:255, sensorType:12) dev:3462025-04-17 10:11:00.016 AM
debug
Office Motion: getConfigureCmds... dev:3462025-04-17 10:10:58.968 AM
info
Office Motion: Logging Level is: Trace (4) for 2 Hours dev:3462025-04-17 10:10:58.945 AM
debug
Office Motion: updated...
Ok thanks, I will try and look at it more later today. The issue is that it is sending SensorBinary reports which is a depreciated zwave command class. Most motion sensors use Notifcation reports typically, so the drivers are not picking up the SensorBinary reports.
You could try the driver: Generic Z-Wave Motion Sensor
If anything will support the old SensorBinary it would be that one.
Should have included... this came up couple times... issue? dev:3442025-04-17 11:02:50.457 AM
error
java.lang.ClassCastException: null (method setLevel)
That's a different device ID, so different device. If you click on the red "Error" text it will open up the device page. Should be a dimmer or something with a level or position. Motion sensors wont have anything with setLevel.