I have a Yale YRL256 leverset that sends an event if too many wrong codes were entered in the lock as seen here:
Is there any way for me to set up an alert either with the rues machine or events engine?
Don't know about the latter, but you can do this in Rule Machine using the "tamper" trigger type. If your device sends tamper: detected for things other than this particular real-world event, you'll have to do some digging that is a bit awkward but not impossible, assuming the description text (like towards the right of your screenshot) has something that can consistently identify the event. If not, triggering on "tamper detected" should be enough. Then, in your actions, just send a notification.
Alternatively, and a bit easier (not that this particular rule is that difficult): use the Notifications app, choose tamper sensor as the type, and then configure the rest of the app accordingly. You get some extra options here with less work than RM, but, of course, either works.
1 Like
I tried what you said. The problem is when i set a rule up for tamper, my lock isnt one of my device choices. It only shows motion detectors, devices that actually have a tamper switch. Someone in group elsewhere said this coyld be done in the events manager but didnt tell me how. Im hoping someone here may know. Im surprised this isnt a default notification. I would think if someone's trying different codes at a lock to get it, one would want to be alerted
May need to look at custom triggers to find it.
1 Like
What driver are you using? I have a Yale lock and am using the generic zigbee lock driver. That tamper attribute does not appear to be exposed by the generic driver.
I have the zwave version. Im using the generic zwave driver
Hmmm don't see it there either... Possible the lock sends the event but the driver doesn't support the attribute. In which case I think you'd need a custom driver.
I figured seeing as it does sent a tamper alert, there was someway to use that as a trigger
There should be, even if you need to use a "Custom Attribute" trigger like @thebearmay suggested (I was operating under the assumption that the driver fully implemented this capability, but it's possible they just added it as a plain. attribute; either way, it's definitely usable since your history shows you're getting an event).
1 Like
