There is a tamper event in Hubitat logged, but nothing in node-red. So I'm not sure if Maker API isn't sending the event at all, or if the node-red nodes are trashing it (but I was coming off the "event" node, so I don't think so...).
That's weird. FWIW, I not using the event node. I'm using the lock device node with "All" attributes selected.
I turned on Maker API debugging - it is not in there, so I'm pretty sure Maker API isn't sending the event at all. 
@bravenel or @mike.maxwell - Any idea why when I input the wrong code enough to get a tamper event on the lock, and an event shows up in the device logs, that Maker API is not sending an event for this? I would think if the device is generating an event then Maker API should be sending it?
This is with the in-box Generic Zigbee Lock driver.
Note below - no Maker API debug log at all for the tamper event @ 8:07:38...
Device Log:
Maker API debug log:
-
You see the lock event in Maker API at 8:06:35 -
Tamper event @ 8:07:38 is missing altogether -
Next lock event in Maker API is the manual unlock at 8:07:42
1 Like
Huh - I just tried my sequence again, and it doesn't work. I'll be danged - I was sure "sure" it worked because I remember playing around to get the switch node right.
Maybe it works if you use websocket instead of webhook. 
I'm not willing to test that right now, though.
I just wanted it to work with the built in HE notification app .
Is this possible?
I entered wrong codes a couple of times in my 916 ZWave where it blinks red color when entered wrong
Nothing shows up in my event log
The attribute is not showing up as a supported attribute for the device. Maker API subscribes to all of the supported attributes of a device. And, "tamper" is not an attribute in the driver, although it is an event.
Unfortunately, "tamper" "detected" is used for several different conditions, not just the one you are interested in. Only the description text discriminates which of those it is, and Maker API (and other apps) don't look at description text. I suspect we'd have to do some schema work to surface this attribute and its possible conditions.
Z-Wave lock driver does not send an event for this. I'm not sure, but the lock may not be reporting it.
This is the reason nothing has been done with this; there is not consistency across the various locks.
I was pretty sure that was why. Thanks for confirming. This isn't a huge issue for me, so don't do any extra work on my account.
Again, you will not see anything in the event log on the device page. It will show up in the hub live logs however if you have debug logging enabled for the device. My Kwikset Z-Wave locks do show up in the live logs.
I do have debug enabled. I will check again later
Thank you
