How do I reset tamper cover on garage door sensor?

[Madcodger]

Another noob to zwave question... I installed an ecolink garage door (tilt) sensor, and took the cover off after install. Now, after putting the cover back on, it continues to show "tampering cover removed". How do I turn it off? Can't see to find answer in tiny manual.

[Frobozz]

Replace 62 with your device Reference ID. (found on the advanced tab)

&hs.SetDeviceValueByRef(62, 0, True)

[MStan]

Replace 62 with your device Reference ID. (found on the advanced tab)

&hs.SetDeviceValueByRef(62, 0, True)

Where do you enter this?

[ewkearns]

Create an event similar to this. My device reference is 1086, change that to the correct number of your device reference (as noted above).

[Android]

For anyone that comes across this trying to reset a device's tamper status, the "ref" is not actually the ref parameter found by hovering over your device, but actually the feature value.

[ewkearns]

For anyone that comes across this trying to reset a device's tamper status, the "ref" is not actually the ref parameter found by hovering over your device, but actually the feature value.

How does one even see, "the ref parameter found by hovering over your device"? I don't have a clue what that is!

[Kevb]

How does one even see, "the ref parameter found by hovering over your device"? I don't have a clue what that is!

If I hold the cursor over a device on the Devices page, the bottom left of the screen shows IPaddress ref=xxx and other info.

[ewkearns]

If I hold the cursor over a device on the Devices page, the bottom left of the screen shows IPaddress ref=xxx and other info.

OK, I see that and get (for instance) http://192.168.xxx.xxx:xx/devices.html?ref=1602&subpage=devprop&tab=settings, but 1602 IS the reference number to use in the "immediate script command."

[Jebus]

How do I reset tamper cover on garage door sensor?

It has been my experience that just replacing the tamper cover on a z-wave device resets the tamper cover status.
The device knew the cover was removed by a tiny switch, it should know when it's replaced.
Try removing and replacing the cover again while device is awake.

[joegr]

It has been my experience that just replacing the tamper cover on a z-wave device resets the tamper cover status.
The device knew the cover was removed by a tiny switch, it should know when it's replaced.
Try removing and replacing the cover again while device is awake.

It hasn't worked that way for me. The tamper seems to stick. I guess that makes sense. If you don't have an event to catch the tamper when it happens, you wouldn't want the person that tampered it to be able to hide their activity just by putting the cover back on.

[Jebus]

A valid configured device that had it's tamper cover replaced, after removing it, will send a status value of 0 and HS then sets a status of No Event. Every device w/tamper, that I have, sets this on the Home Security HS device status.

[joegr]

Specifically, DWZWAVE2.5-ECO hasn't cleared tamper for me. I'm running HS3 with the 3.0.10.0 Z-wave plugin.

I do get this in the log about once every day.

Mar-01 9:27:40 AM

Z-Wave

Zstick+: Z-Wave Wake-Up 'No More Info' Notification sent to Node 26(1st Mail Box Ecolink Notification Sensor).

Mar-01 9:27:40 AM

Z-Wave

Zstick+: Wake-Up Notification Processing for Node 26 (1st Mail Box Ecolink Notification Sensor)

Mar-01 9:27:40 AM

Z-Wave

Zstick+: Z-Wave Wake-Up Notification Received for Node 26

This may indicate some configuration problem? It is otherwise operating correctly.

[Jebus]

What does it say in the logs when you remove and replace the cover?

[joegr]

It's been over a year since I messed with it, so I don't recall what was logged when the cover was removed. I'm pretty sure that nothing was logged when it was replaced. I did remove and replace it a time or two after that (to see if that would clear the tamper). I don't recall anything being logged then.

[ewkearns]

This is a known issue for some devices (maybe not all) that has been posted in this forum. Once they start reporting incorrectly, my experience is that there is no help other than an immediate script resetting the value.