Alarm arming countdown

[markdrussell]

Hi All. Following a recent HA software upgrade, my Alarmo/Ring keypad setup stopped working. I’ve got it up and running again, but the countdown peep/lights no longer happen when the alarm is arming/disarming. I suspect it is something to do with the changes made in the commit below, but not entirely sure. Very grateful for any assistance!

d9cebab

[alexShinobii]

Hey! Not sure if this is related, but my problem was that I didn’t have the latest commit in my blueprint (not sure why). Manually updating the YAML (or re-importing the blueprint) fixed it for me. Good luck!

[alexShinobii]

Sorry, actually was referring to this commit:
8d9970f

[markdrussell]

Thanks for the suggestion Alex. I just tried re-importing the latest commit and the problem above still remains unfortunately.

Any thoughts @jsnallen @ImSorryButWho - thanks!

[jefft4]

The commit you referenced appears to have changed the z-wave property key target for 'alarm triggered', which isn't the state that you're having a problem with.
My system also had no arming countdown ("exit delay"), logs showed that the automation was hitting 135-0-18-7 rather than 135-0-18-timeout and failing. Same for the entry delay 135-0-17-timeout. My guess is that the V1 keypad was the -7 keys and the v2 is -timeout. Are you using a V1 or a V2 keypad?

The issue for me, was the bleuprint code was old. HA hadn't pulled the updated code that's currently online (https://github.com/ImSorryButWho/HomeAssistantNotes/blob/main/keypad_blueprint.yaml). I removed the automations and the blueprint, then reinstalled it. Works now :-)

I'd look at the code in your automation to make sure: 'take control' then view the yaml. Check the alarm_arming and alarm_pending condition blocks, see what property_key they're using and whether it matches what your z-wave controller says.

[nsleigh]

Same problem for me - i.e. countdown peep/lights no longer happen when the alarm is arming/disarming. I have a 2nd generation keypad. With a bit of testing it seems to be related the timeout / formatted_delay change, removing that resolved the issue.

I am back on this version which works perfectly:
Commit 5baf421
ImSorryButWho authored on Jul 7, 2023

[mcondren]

I just started having the same issue after my latest zwaveJS update. The ring keypad had new configurations that had to be loaded and re-interviewed via zwaveJS and now there are a lot more notification/indicator settings in wave JS. I'm wondering if this broke the blueprint somehow. It still arms and disarms but I get no exit or entry delays countdowns anymore.

[donoghdb]

So I have fixed the issue on my automation. You need to take control of the automation, got to Option 8 & 9 of the "Then Do". Open the "Actions:" and Z-Wave: Set a value (advanced). Scroll to Property Key and there will be "7". Replace this with "1".
For example below, test it in your Developer Tools

action: zwave_js.set_value

data:
command_class: "135"
endpoint: "0"
property: "18"
value: 30
property_key: "1"
device_id:
- ID-HERE

[nsleigh]

So I have fixed the issue on my automation. You need to take control of the automation, got to Option 8 & 9 of the "Then Do". Open the "Actions:" and Z-Wave: Set a value (advanced). Scroll to Property Key and there will be "7". Replace this with "1". For example below, test it in your Developer Tools

action: zwave_js.set_value
data:
command_class: "135"
endpoint: "0"
property: "18"
value: 30
property_key: "1"
device_id:

• ID-HERE

This worked for me but so did importing the latest template that has "timeout" instead of the number.

What is really odd is that the old value has been working fine until recently and the last time I tried the latest blueprint that didn't work!