[RELEASE] Vision Shock Sensor (ZS 5101)

dth_security
dth_sensors
dth_watersensor

(Kevin) #1

This is a device handler for the Vision Shock Sensor (Model: ZS 5101).

The Vision Shock Sensor detects vibration and it also has terminals inside that allow you to attach an external sensor.


Features

  • Choose between Motion or Acceleration for the primary Capability which is shown in the main tile.

  • The primary capability will switch to active on vibration and switch back to inactive 10 seconds after vibration stops.

  • Choose between Tamper, Water, Motion or Contact for the secondary Capability which is shown as the secondary status of the main tile.

  • The secondary capability will switch to its active state (detected/wet/active/open) when the device is opened or the attached external sensor changes from closed to open.

  • The device doesn’t send a clear event for the secondary capability so once it becomes active you need to manually tap the refresh tile to reset it.


Screenshots

      


Sump Pump Monitoring

I can think of a lot of ways to use this device, but I think its the perfect device for monitoring a sump pump because you can use the vibration to detect when the sump pump turns on and you can attach an external sensor and use it as a water sensor.

I’ve attached the vibration sensor to the PVC pipe with a cable tie and I have a cheap dump contact sensor connected to the terminals. The magnet is attached to the float of my backup pump and the contact is positioned next to it so that the circuit is closed.

If my primary sump pump fails, the water will reach the backup pump’s float causing the external sensor to change to open and the device handler to report water wet.

Dangling the wires and allowing the water to close the circuit won’t cause the device to send a notification to SmartThings. If you want to use the external contact to detect high water, you need to use either an external sensor or rig something to pull the wires apart because the device only sends a notification when the circuit changes from closed to open.



[Request] - Device Handler for Z-wave + Monoprice Shock Sensor
Vision Shock Sensor ZS 5101
Vision Shock Vibration Sensor notifications to iPhone
Aqara vibration sensors available
Contact sensor for sump pit?
Pretty tilt/vibration sensor
(Winston Byrd) #2

I have not been able to get this to work. After I update the device handler, in does show additional useful tiles but the only recent activity that shows is tamper door, battery level and ‘acceleration inactive’


(Kevin) #3

Can you post the device’s raw description which is shown in the IDE? That will allow me to see if it’s the same model and firmware that I have.


(Winston Byrd) #4

zw:Ss type:0701 mfr:0109 prod:2003 model:0307 ver:16.06 zwv:4.24 lib:03 cc:5E,22,85,59,80,5A,7A,72,71,73,98,86,84 role:06 ff:8C07 ui:8C07


(Kevin) #5

I’ll have to do some research on that device because it doesn’t match mine.

If you post the make and model I’ll look into it tonight.


(Winston Byrd) #6

It is sold by Monoprice as, "Z-Wave Plus® Shock Detector, NO LOGO"
It has a little weight mounted on a spring and it should be detecting vibration of the spring.

https://www.monoprice.com/product?p_id=15269


(Kevin) #7

Another user had the Monoprice device and it was working for them, but it was unreliable. I’ve made a change that might fix the problem, but I haven’t finished testing it so I’ll PM you the code.


#8

I just bought the monoprice shock sensor (#15269) have the same issue piekingandknowit where it doesn’t function after adding to the app/hub. It remains in “inactive” and the only event entries are the 3 created when it was added. I have the same device raw description as piekingandknowit as well.

I’m happy to help with research or provide info to help move this along. Thanks for your work for the community!


(Kevin) #9

I have a new version that fixes that problem for the Monoprice device, but I’m still testing to make sure it doesn’t break the vision device. I’ll send you the new version and will most likely publish it later tonight.


(Kevin) #10

I just released the new version that should work with the Monoprice device.


#11

Thanks for your work for the community.

I tried various include/exclude/profiles/etc over the weekend and think I have a defective unit… It’s not registering any motion/vibration whether I use your handler or any basic (i.e. door sensor) one. The logs show no activity other than device inclusion and the check-in every 12 hours.

I’m going to contact monoprice for a replacement or return.


(Kevin) #12

You might want to try excluding it, factory resetting it, removing my DTH (just to rule it out) and including it to see if the default DTH it gets assigned shows any activity in live logging.


(Craig Shaffer) #13

I have a MonoPrice 15269 sensor and it doesn’t work via this handler.

Here is the descriptor:
zw:Ss type:0701 mfr:0109 prod:2003 model:0307 ver:16.06 zwv:4.24 lib:03 cc:5E,22,85,59,80,5A,7A,72,71,73,98,86,84 role:06 ff:8C07 ui:8C07

Here is the log:
bc3bfdce-fa28-4792-a5bc-e44d41e5237a 8:31:42 PM: warn Unable to extract encapsulated cmd from SecurityMessageEncapsulation(commandByte: [40, 202, 100, 80, 81, 150, 222, 132, 0, 163, 55, 72, 227, 233, 240, 255, 114, 19, 1, 5], commandClassIdentifier: 144, commandIdentifier: 245, reserved13: 1, secondFrame: false, sequenceCounter: 2, sequenced: true)
bc3bfdce-fa28-4792-a5bc-e44d41e5237a 8:31:09 PM: warn Unable to extract encapsulated cmd from SecurityMessageEncapsulation(commandByte: [42, 48, 21, 38, 236, 100, 139, 121, 0, 53, 162, 136, 40, 123, 47, 249, 214, 1, 19, 1], commandClassIdentifier: 208, commandIdentifier: 90, reserved13: 1, secondFrame: true, sequenceCounter: 10, sequenced: false)


(chris) #14

Same here, I got the 15269 from monoprice yesterday and added krlaframbosie’s device handler but the sensor just says inactive. sorry for the ignorance but do we just copy the entire “raw” as it is and publish it or do we need to edit some lines?

i have 2 new 15269’s i received two days ago and they both do same thing. just says inactive in the smartthings app. They both showed “open” when i used the default zwave smarthtings handler.

I appreciate Kevin for taking time to help us.


(Kevin) #15

I just sent you both a PM with another version to try…


#16

Please add me to the test group when you get a chance. Thanks.


(Craig Shaffer) #17

I tested your new version but no love. I can trigger an immediate message by opening and closing the cover. When I do that I get this message:

I did it twice:

bc3bfdce-fa28-4792-a5bc-e44d41e5237a 10:16:26 PM: warn Unable to extract encapsulated cmd from SecurityMessageEncapsulation(commandByte: [47, 135, 173, 102, 40, 153, 146, 235, 0, 36, 22, 0, 86, 219, 194, 230, 116, 19, 1, 5], commandClassIdentifier: 84, commandIdentifier: 229, reserved13: 3, secondFrame: true, sequenceCounter: 9, sequenced: true)
bc3bfdce-fa28-4792-a5bc-e44d41e5237a 10:16:00 PM: warn Unable to extract encapsulated cmd from SecurityMessageEncapsulation(commandByte: [96, 151, 120, 170, 45, 114, 78, 233, 0, 225, 250, 193, 192, 230, 253, 190, 207, 0, 4, 0], commandClassIdentifier: 148, commandIdentifier: 191, reserved13: 2, secondFrame: false, sequenceCounter: 11, sequenced: true)

Then I waited about 10 minutes and I tapped it a few times but the status never updated or changed. No new messages were logged either so I think maybe these modules could be faulty. I could send this unit to you for testing / programming / debug if you are interested. Other-wise I’m just going to send it back to Monoprice because it doesn’t work for me.


(Kevin) #18

I didn’t expect it to work, but I figured it was worth a shot.

I just noticed that the fingerprint you posted has a lowercase “s” and “98” in the cc list, but it doesn’t have any commands listed in the “sec” list.

If the secure inclusion wasn’t successful that might explain why the “sec” list isn’t in the fingerprint and why you’re seeing those errors.

Try removing the device, and my DTH, then unplug and taking the batteries out of the hub for a few minutes, and then plug the hub back in and add the device.

See if it works with the default DTH which will most likely be a contact sensor. If it works install my DTH, switch the device to it, and see if it still works or starts logging those errors again.

I don’t mind continuing to troubleshoot this, and I can think of a couple more things to try, but just so you know, this device has an official Monoprice DTH.

Unfortunately Monoprice partnered with rboy so if you want the Official Monoprice DTH you’re going to have to purchase it from him.


(Craig Shaffer) #19

Hi,

I don’t mind continuing to troubleshoot. I’ll test it out tonight when I get home. I didn’t know there was an official DTH but there’s no harm in continuing development.

There will probably be lots of people like me who buy the sensor and expect it just to work like so many other z-wave devices. I don’t actually mind paying to help offset all the work that goes into writing these drivers but I think we are pretty close to a working solution and I found your driver first so others might as well.


(Craig Shaffer) #20

Here’s what I’ve got after a delete of the DTH and the device followed by a reboot of the hub. Then I did a re-add via my phone with the default settings.

1.) I loads as a Z-wave plus door/window sensor
2.) It always shows "OPEN"
3.) The raw descriptor still has the ss:
zw:Ss type:0701 mfr:0109 prod:2003 model:0307 ver:16.06 zwv:4.24 lib:03 cc:5E,22,85,59,80,5A,7A,72,71,73,98,86,84 role:06 ff:8C07 ui:8C07
4.) I still don’t get anything in the log when I tap the sensor (despite getting a red light)
5.) When I open and close the sensor I get the following:
88652e41-1cdb-4a35-af29-d1f573b47314 6:20:16 PM: debug Parsed 'zw device: 11, command: 9881, payload: 54 1B D5 B9 2E 00 56 21 1F 1F 18 00 2A 81 11 24 E5 5B 0B D1 00 04 00 ’ to [[descriptionText:SecurityMessageEncapsulation(commandByte: [185, 46, 0, 86, 33, 31, 31, 24, 0, 42, 129, 17, 36, 229, 91, 11, 209, 0, 4, 0], commandClassIdentifier: 27, commandIdentifier: 213, reserved13: 1, secondFrame: false, sequenceCounter: 4, sequenced: true), isStateChange:false, displayed:false, linkText:Z-Wave Plus Door/Window Sensor]]
88652e41-1cdb-4a35-af29-d1f573b47314 6:20:16 PM: warn Unable to extract encapsulated cmd from SecurityMessageEncapsulation(commandByte: [185, 46, 0, 86, 33, 31, 31, 24, 0, 42, 129, 17, 36, 229, 91, 11, 209, 0, 4, 0], commandClassIdentifier: 27, commandIdentifier: 213, reserved13: 1, secondFrame: false, sequenceCounter: 4, sequenced: true)
88652e41-1cdb-4a35-af29-d1f573b47314 6:20:16 PM: debug encapsulated: null