I can't get the Hubitat to pick up this device. This is a Z-Wave Plus device. Any tricks to get this device to pair would be greatly appreciated.
What have you tried? The manual is not very clear but says you should press the "program switch" once (and observe its behavior to see if it's already included), put Hubitat in discovery mode, then press it again. It's especially unclear about this, but if it's like the Zooz, the "program switch" is the small hole on the back you can poke with a small paperclip or similar.
If you're moving it from another hub or the LED suggests its already included (or even just for fun), you might also try a general exclusion or resetting it first. Once again, the Monoprice manual fails, but the Zooz says pressing the button 10 times within 10 seconds will do a reset, so that might help too.
Good luck!
I bet if you change the z wave radio to secure join to all it will pair, I had the exact issue as yours with 2 monoprice 4 in 1, I ended pairing them secure, then changed the radio back to locks and garage doors.
I will tag @mike.maxwell for input.
Good luck.
We're not familiar with the Monoprice device, Zooz is not affiliated with Monoprice in any way. They order the sensor from the same factory and look similar but both hardware and software is very different so we wouldn't be able to assist here much. Sorry!
I can't get this Monoprice 4in1 sensor (15902) to pair either. Did discover there is a reset on the bottom that requires a really small pin to depress. After reset it will blink 5 times indicating it is ready to pair but then nothing. Even trying to exclude it after reset doesn't work. Also tried the All secure Z-wave option suggested.
any other suggestions?
Try to pair it while a foot or two from the hub.
Thanks - that did the trick. Did a exclusion and then reset and it finally found it. Several times it would find the sensor but hang on initializing. Very picky sensors!
I know this is an aged thread, like to get any comments about this. Thanks,
I just got 15902 no problem pairing it; but can not get any status update after pairing. From the event logs, it shows only the Resync All, but no response from the sensor; tried reset the sensor, and exclusion Z-wave multiple times, It was the same, no response; may be bad sensor device ?
It took a while but mine as able was able to sync. It’s just that I don’t have any motion detection. The temp and humidity works. I’m just using the default Zooz 4 in 1 device. Not sure if there are any other drivers that might work better? Or any one getting the motion detection to work?
I tried it quite a few times to pair it, and no success, reset sensor, exclude zwave device, restart hubitat. I tried it with my Raspberry Pi Home Assistant gateway. To my surprise, it paired in non secure mode the 1st time, got all 4 sensors info, so no problem with the sensor. The HA zwave debug log shows details message exchange between the controller and the sensor, which is very helpful to see if there were no-response, error response, etc. Is there any zwave debug info that I can turn on to help diagnostic this ?
I got one of those as well. It takes A LOT of patience to pair. I ended-up pairing, then unpairing, then pairing again, then doing both at the same time... It would unpair very quickly. It would also find it relatively quickly, but it seemed to just hand at Initializing... Very annoying! Now to see how well it works...
No luck here either. It seems like everything related to hubitat has to be difficult.
I'm running into this myself. I can get it to pair, and it automatically defaults to the Zooz 4-in-1 driver, but the motion reports "active" and never changes.
So, it is actually working with the Zooz 4-1 driver... the issue was that the motion re-trigger option has different values depending on your firmware. One of the settings is 15 MINUTES or 15 SECONDS depending upon the firmware version. My firmware was 5.1, which interpreted that setting as Minutes. Once I changed it to 1 minute and pushed the button to resync it started reporting active/inactive more reliably.
1 Like
This thing is reliable once properly configured. . . It loves falling asleep or hanging up on mixed messaging, or something; at least until it is happily configured in the network. The sensor itself reports by flashing after the press: once upon initializing, and again after a few seconds to indicate it is done - or giving up. I found best practice to press the pinhole button every 10-15 seconds; or after flashing the second round, until properly synced/included/configured with the hub. In a few instances, mine was flashing 5 times even after it was purportedly configured in the hub; the sensor didn't believe itself to be properly configured and was not reporting sensor data. I had to exclude, reset, and try inclusion again until during inclusion - which has to be like one foot from the device - both the hub was done/ready to name device, and the device reported back with just the single flash. It was still dropping sensor reports or not reporting motion or illuminance reliably, losing packets in the network, falling asleep, idk. I did the same thing (~press every 15 seconds) during ZWave repair sequence and now it is working brilliantly.
I got a couple 15902 to pair properly (firmware 5.1, secured connection). I can change settings and get them sync'd (syncStatus = synced).
My issue is that it reports temp/humidity/luminance every 3 minutes no matter which trigger settings combination I use, even with temp change trigger set to 9F, light change trigger to 50% and humidity change trigger to 50%.
This drains the batteries in no times... What can I do to change this 3 minutes automatic report?
