Tamper alarms not being received

[johnvoipguy (John Watkins)]

I’m not seeing any tamper (cover removed), from my AEOTEC, or ecoLink. I can see the alarmReports in the device Types, but I never see them come in.

is there something I’m missing?

[kevintierney]

In ST, device types currently don’t have the ability to generate an alert directly. You’ll need a smart app to monitor the device and create an alert or text

Here are some threads where this type of issue is discussed

Capability urgentAlert

To answer your question, just read this thread. The biggest problem, as I see it right now, is that ST isn’t helping or guiding in any way. As far as I can tell, we’re just amusing ourselves debating about all of this. It’s shame, really, because I can’t seriously recommend ST to anyone because of the large shortcomings right now and what appears to be complete apathy on the part of ST to fix them. I mean - really - this isn’t a trivial thing here. If a person buys a $200 door lock that alerts when someone is breaking in, they EXPECT the controller to pass that alert along to them. This is a door lock that ST claims as certified and even sells on their own website!

Capability Tamper Alert

Great recommended new Capability, thanks! The problem with ST’s current architecture is there is no way to have parent-child or any sort of grouping of Capabilities with inherited or polymorphically compatible properties / characteristics. Tamper is likely a good example case of an Urgent Alert, per @garyd9’s Topic: But ST only lets you be one or the other, not both. I’m guessing that even if the code of the Platform would make this easy enough to squeeze in (i.e., some form of inheritance, grouping, polymorphism), the overall impact makes that a long-term feature request at best. In the meantime, if we want a single SmartApp to catch all important alerts, it should allow input of Devices with capability.urgentAlert, and a separate input of those with capability.tamper (two Device pr…

Device types: how can a device alert/alarm/notify of critical problems?

(There’s actually a proposed solution in the latter half of this post - the first half is just describing a problem, and then trying to emphasize how serious it is.) If it’s not obvious from my recent postings, I’m playing around with device type code. One issue I see over and over is that a device might experience a serious problem that a human being REALLY needs to be informed about, but there doesn’t seem to be any way for a device type to send a notification or alarm. For example, let’s say you get this new wiz-bang auto-magic does everything ESP enabled door lock. This thing can detect if a burglar is even THINKING about breaking into your house! So, you add it as a new z-wave device, see that ST can lock/unlock it, and you go off to work. Then, while you’re at work, a burglar j…

[johnvoipguy (John Watkins)]

Thanks @kevintierney. I’ll review the previous postings. however, when I’m looking at logging for the device I’m not even seeing a Zwave event (shouldn’t I?). regardless of an actual push, or txt, or something…

[kevintierney]

Yeah, it should at least be showing in the log, if the device supports it and the device handler has the code to log that event. Are your devices using device specific device types, or generic ones?

[johnvoipguy (John Watkins)]

My test devices are the generic zwave motion/contact, at the moment. I wander if I need to add the catch-all to the parser, I didn’t see when I look earlier?

[johnvoipguy (John Watkins)]

I got my not seeing events in the device handler figured out…

I added alarmv1, alarmv2 to the device handler and I get a change in value in my tile, and I see the events under activity feed.

I still haven’t been able to figure out how to subscribe to these events. i’ve tried the following subscribe settings, but I don’t see any events in my Smart App. I do see motion events, so I know that’s working…

    subscribe(motion,"motion", onMotion)
    subscribe(motion,"alarmReport", onMotion)
    subscribe(motion,"AlarmReport", onMotion)
    subscribe(motion,"alarmV2", onMotion)
    subscribe(motion,"alarmv2", onMotion)
    subscribe(motion,"sensor", onMotion)
    subscribe(motion,"alarm", onMotion)
    subscribe(motion,"notification", onMotion)

[kevintierney]

What does your alarm create event look like? The subscription should look similar

[johnvoipguy (John Watkins)]

def zwaveEvent(physicalgraph.zwave.commands.alarmv2.AlarmReport cmd)
{
def map = [:]
map.name = "tamper"
map.value = cmd.alarmLevel == 255 ? “tampered” : "secured"
if (map.value == “tampered”) {
map.value = "tampered"
map.descriptionText = "$device.displayName has been tampered with"
map.isStateChange = "true"
map.display = "true"
log.debug “tampered: $map”
}
else {
map.value = "secured"
map.descriptionText = "$device.displayName is secured"
map.isStateChange = "true"
map.display = "true"
log.debug “secure: $map”

   	}
createEvent(map)

[kevintierney]

Try

subscribe(motion,“tamper”, onMotion)

[johnvoipguy (John Watkins)]

You are the man @kevintierney! thanks for the help!

I got the Smart Things hub about 2 weeks ago, So I’m still learning the correlation between all the functions…

[kevintierney]

Glad I could help. I still have much to learn and it’s much trial and error. In this case you had to subscribe based on the event name