Zigbee2MQTT - Sync Keypad and Alarm Control Panel States

Blueprints Exchange
,
147

Hello everyone,
I’m trying to code this wonderful work from bluprint to nodered to implement my alarm with keypad.
I’m using ALARMO and Develco KEYZB-110
Would anyone know how to help me?

148

After updating Home Assistant to 2025.1 and Z2M to 2.0, the blueprint no longer worked correctly for me. I have found a fix that resolves this. I would post this above - but only if others also have the problem with the current Home Assistant Version 2025.1 and Zigbee2MQTT 2.0. How does it look for you? Is the blueprint still working?

149

after moving to z2m 2.0, it stopped working. Reason is probably that the actions have changed in z2m to HA

150

I just updated the blueprint in the first post to fix the problem. Would be happy for some feedback, if it works :slight_smile:

151

Hi @AndrejDelany

I’ve just updated to HA 2025.1.2 and z2m 2.0

In z2m, in the ‘status’ tab of the keyboard I still have the ‘actions’ :

image

Can you tell me (or anyone else) if this is the case for you too ?

152

For my Linkind Keypad it’s different.

{
    "ac_status": false,
    "battery": 8,
    "battery_defect": false,
    "battery_low": true,
    "last_seen": "2025-01-07T00:21:35+01:00",
    "linkquality": 69,
    "occupancy": false,
    "restore_reports": true,
    "smoke": false,
    "supervision_reports": true,
    "tamper": false,
    "test": false,
    "trouble": false,
    "voltage": 2500
}
1 Like
153

ok thanks for the information :wink:

154

Using the Frient Keypad. Do anyone get feedback to the keypad, such as LED indicators when arming/disarming, and countdown noise?

155

Hi everyone,

I’m using the blueprint with my Zigbee keypad. The integration works, but I noticed that the blueprint has an open “Pincode” text field where the valid PIN must be entered (example: 1234).

This makes the PIN value:

  • Visible in the Home Assistant UI
  • Stored in plaintext in the automation/blueprint config
  • Potentially included in backups or screenshots

Since I already use Alarmo for my alarm system (which has its own secure PIN handling), I’d prefer not to store the code again in the blueprint.

:point_right: My questions:

  1. Is there a way to hide or mask this field in the UI (like password mode)?
  2. Can I reference a secret (!secret) or a masked input_text helper instead of typing the raw PIN?
  3. Or should I completely bypass the blueprint and just forward keypad events (with the raw pin_code from MQTT) directly to Alarmo for validation?

I’m mainly looking for best practices on handling PINs securely here, so they aren’t exposed in plain text.

Thanks for any suggestions!