How to expose Alarm_Types for my Yale lock?

Third party integrations
1

Hi all,

I have my lock paired in Vera (for quite a long time now) and I can lock and unlock through HA just fine, and it does report the battery level and the state etc, I’m just not quite able to get at these alarm reports (see page 4: https://www.cd-jackson.com/zwave_device_uploads/321/Yale-Z-Wave-Developers-Guide.pdf).

I’m basically following this thread which suggests the need to set up a template in HA to show the status in the HA front end - Show which code unlocked your Schlage lock (mostly solved)

My issue (I think?) is I’m not really clear on where to find the correct name for “sensor.front_door_alarm_type” for example. Should that sensor already exist in HA? Do I need to change the “front_door” part to match my lock entity? I just can’t seem to work it out :smiley:

Here’s what I have so far:

image
image781×90 1.56 KB

image

I’ve tried with and without the entity id. I’ve tried changing the names to sensor.touchscreen_deadbolt_24_alarm_type. I’m just not quite clear on the syntax…

2

The thread you linked already has your answer. The alarm_type sensor is exposed by the HA Z-Wave integration (OpenZWave) which requires a Z-Wave USB stick as a controller. If you are using Vera as your Z-Wave controller you won’t have it.

3

Hmm, interesting. I wonder why Vera doesn’t see/expose the same details? That’s actually really annoying…

I do have a Zwave stick but it’d be a bit of a drama switching everything over just to get this working :frowning:

4

Maybe the Vera software itself can do this, I have no clue, but the HA Vera integration is very simple when it comes to lock devices: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/vera/lock.py

5

Reading the Yale doc (https://www.cd-jackson.com/zwave_device_uploads/321/Yale-Z-Wave-Developers-Guide.pdf) it mentions:

COMMAND_CLASS_ASSOCIATION

The lock supports 1 association group with 5 devices. Alarm Reports are sent out

unsolicited to devices included in the association group.

I wonder if I need to utilise that somehow?

6

Vera is hiding these levels of details from you. You’re not going to get anything else out of it.

7

Looking at the Vera API docs (I think that’s what they are?), it looks like it might be possible to get the alarm values via the ZWaveDevice1 “service” (see AlarmTypes variable). But this is probably something that does not currently exist that HA could use.

8

Yep makes sense.

The Vera stuff is actually, finally, getting some solid support as another company have bought them out and they actually appear to know what they’re doing (unlike the previous owners). They’re in the process of rewriting a lot of the code, so I’ve just hit up one of the devs to see if they’re able to expose these details as part of their rewrite. Fingers crossed!

9

Very interested to know this as well as I just bought a VeraPlus to replace my Wink Hub. While not critical to have these alarm_types I’d like the ability to use “unlocked by keypad” in automations.

10

Hey, voice your support here (the dev said if there’s enough interest they’ll look at adding it):

https://community.getvera.com/t/expose-alarm-command-classes-for-locks/208202/4

1 Like
11

Done. Hope the devs can get it working soon!