I have three mono price shockwave sensors attempting to be run on the AZ Wave JS instead of legacy. They did work under legacy for many years, though they were sometimes temperamental. I moved over to Z-Wave JS, yes, attempting to get a C8 pro potentially. My c8 I flipped to Z-Wave JS, and I was able to get most devices working again after 24 hours. So far, the only problems I have are with the shock sensors. They don't seem to respond completely; they detect intrusion but do not detect any motion/shock. I wanted to see if anyone has gotten one of these devices to work underneath Z-Wave JS, or should I look at something else to replace them from Zooz. Please let me know either way. Thank you for your help.
Try running this endpoint for one then manually wake it up.
Force a re-interview, endpoint ## below is the decimal node number.
/hub/zwave2/reinterview?node=##
Then you can also turn on debug logging and see what happens when you activate the device. Post anything that is logged.
Also possible that excluding and pairing it again while on Zwave JS would get it working.
I appreciate your help.
Events, I get nothing
Debug Logs
Zwave
I do see stuff happening, but the device appears not to be functioning.
I'm using DHL, a third-party service everyone uses for this type of device.
DHL
I have been trying different drivers, but nothing has worked. 
Any recommendations?
Sounds like Jeff will drop back in to check the response from the endpoint he gave you...
When I ran the URL Wake interview, it just said done, and I provided the Debug logs. I'm sorry may I don't understand.
1 Like
Need a link to that user driver you are using.
It appears the device is sending an Intrusion alarm to the hub, and the driver is not doing anything with it. I wonder if the driver is expecting a sensor binary report and ZWJS is suppressing it or something in favor of the Notification report?
The Zwave logs would be much more useful in text format (can paste in a code block or upload to pastebin.com)
Just to confirm I ran your log screenshots through AI and this is one of the items it came back with for me. I mean I could sit there and decode it all manually but AI works great for this stuff.
2. "Intrusion" Event Confirmation
The log confirms that the device is successfully sending specific security alerts:
- Notification Type 7: This is "Home Security."
- Event 2: This corresponds to "Intrusion / Motion Detection."
- Sequence: You can see the transition from
Sensor status: 0 -> 2(Idle to Intrusion) and back again. This confirms the hardware is working and the Z-Wave mesh is delivering the specific alarm packets.
@bertabcd1234 do you know if there is a system driver for a shock or contact sensor that would use this report? I believe a generic motion sensor driver might work as well if @jsarcone does not mind it showing up as motion.
The Zooz ZSE43 driver does (though you'd have to ignore the device-specific configuration parameters) as shock, and Generic Z-Wave Contact Sensor should as "tamper." A few others should catch it too (like Generic Z-Wave DT Contact Sensor, though the driver as a whole is probably too modern for an older device like I assume this one as, at least if it's not Z-Wave Plus).
That being said, if there's a change in what reports are making it to the driver between Legacy and ZWJS, debug logs (to show what is) plus the new logging endpoint in 2.5.0 might be helpful for Bryan to figure this out -- since the goal is for things not to change.
Motion did not show up at all. Just a blank entry as per the screenshot above. I did flip it back to legacy because I was running out of memory. I was around one Meg of memory so I did flip it back temporarily. But I'll be happy to do more testing. The tamper did register when I opened up the cover but none of the motion sensing shows up at all.
If you are back on ZIP you should grab some debug logs there to see if the reporting is coming in the same (it wont look the same but the message might be the same). Please note which driver works as expected in ZIP and that same driver should work on Zwave JS as well, especially if the report is coming over the same. If the event being reported is different then you have found a bug in Zwave JS.
There are drivers suggested above from @bertabcd1234, probably better than a motion sensor driver, I would NOT use the built in ZSE43 driver, there is potential to set the settings on your device incorrectly. You could try MY ZSE43 custom driver which will hide the settings when an unknown (to the driver) device is being used. Or Try Generic Z-Wave Contact Sensor as suggested.
I just checked my ZSE43 driver, and it DOES NOT pick up the 0x07 / 0x02 event, it is looking for 0x03 which is normally tamper but the ZSE43 uses it to report the shock sensor. That might explain why you got a tamper event. I do not think any of the XS devices have an actual sensor to detect when the cover is removed.
I have my suspicions but I will know for certain with some debug/trace logs while on ZIP.
2 Likes
Thanks! I will look at this as soon as I can. I have some work and personal items going on. Thank you all very much for your help. Thank you!
