Simple Blueprint : Zigbee2MQTT Frient Keypad for Alarm control panel (ex: Alarmo)

Blueprints Exchange
, , ,
23

Hi, I’ve setup my Frient keypad with HA using this blueprint. It works fine (syncing between Alarmo and the Keypad) and also the Exit_delay works with blinks and beeps. However, the Entry_delay does not work correctly, only the LED is blinking, no sound.

Anyone has experienced the same issues and is there a way to solve this?

Update: I fixed this! It was an advanced setting in Alarmo, where the option ‘Use entry delay’ was not enabled!

24

Hi everyone. First of all thanks for this blueprint.
I’ve a question related to the usage of the PIN code.
Is it possible that when we arm alarmo from the keyboard that no PIN was requested ?
For disarm i understand but for arm, should be better i belive to have this functionnality.

1 Like
25

Just type ‘;’ after your last keyboard code in the automation. Worked for me.

26

Hi guys, have been using this blueprint for a couple of days now and almost everything working fine so far. Thanks for the work!

Furthermore, we received some rfid tags this morning and I just can’t get them to work. It’s a ISO 14443A 13,56 MHz M1 Chip Model (this one for more info: https://www.amazon.es/dp/B01DAAO1KG?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1) but I just don’t get any code when listening to events after putting the tag close to the center of the keypad (and pushing lock or unlock). Any clues what might be going on?

Sorry if this is obvious but I’m quite new to this and it’s is driving me mad so far…
Thanks!

27

Hi, i use frient keyped over zigbee2mqtt.
I treid to save the blueprint but i get this error:
Message malformed: extra keys not allowed @ data[‘triggers’
i only set MQTT State Topic of your Zigbee2MQTT Keypad so far and the control panal options.
Any ideas how to solve this?
Regards

28

Could you add the following to your code? It looks like it was missed. This is necessary because when Alarmo switches to Home mode, the Frient keypad doesn’t receive the update and keeps beeping.

- trigger: state
  entity_id: !input control_panel
  to: armed_home
  id: panel_armed_home
2 Likes
29

Confirming Cengolotti’s message: this needs to be added indeed. I was just navigating to this page to do the same suggestion…

Hassdevil, you need to add an automation based on the blueprint, not trying to edit the blueprint itself via the blueprint menu.

Joseuah, it is important to not include spaces between the semicolons ( ; ) and to include a + before the code. For example

1234;+E5G51CXA;+P3G21PAX

Also be sure that the code itself only contains alphanumeric characters, no double dots in between ( : )
@Author the blueprint can maybe be changed to filter out (ignore) spaces

1 Like
32

A tip, it’s better to use !input control_panel instead of the entity directly, so you can select the entity directly from the blueprint dropdown.

    sequence:
    - choose:
      - conditions:
        - condition: template
          value_template: '{{trigger.payload_json.action == "arm_all_zones" }}'
        sequence:
          - action: alarm_control_panel.alarm_arm_away
            target:
              entity_id: !input control_panel
            data:
              code: '{{trigger.payload_json.action_code}}'
33

Thank you, I was trying to get the features working using ZHA with limited success. Because of this Blueprint I installed a second Zigbee router (Zigbee2MQTT) and everything works as intended, plus I got to learn the MQTT basics.
Keep up the good work :slight_smile:

34

Thanks for reporting this I was getting crazy about the home mode actions not been triggered.

1 Like
35

Hi @BeGood,

I was looking as others to make the keypad work to be able to arm, arm home, arm away, without entering a pin code. I tried working on your blueprint but I failed to achieve it.

I have seen that other user get to make it work with the same Frient keypad, only requiring the PIN to disarm. frient-keypad/keypad.yaml at main · ginkel/frient-keypad · GitHub

May you considered this as an improvement or feature to implement in your blueprint?

Thanks for your help.

36

Got it. Line 286 in the yaml:
delete the "trigger.payload_json.action_code in pin_list and " so you only have “‘{{trigger.payload_json.action
== “arm_all_zones” }}’” as value template.

This will avoid checking for the pin for the arm all zones. You can do the same for the other arming modes

EDIT:
There is a fork of the blueprint with that feature:

37

The blueprint works nicely with my Frient Keypad but I get this error in the log, any suggestion on how to fix it? Loggare: homeassistant.components.automation.frient_keypad_with_alarm_control_panel_ex_alarmo
Källa: helpers/script.py:2064
integration: Automatisering (dokumentation, ärenden)
Inträffade först: 12:01:42 (6 förekomster)
Senast loggade: 12:06:43

Frient Keypad with Alarm Control Panel (ex: Alarmo): Choose at step 1: choice 8: Error in ‘choose[0]’ evaluation: In ‘template’ condition: TypeError: ‘in ’ requires string as left operand, not NoneType

38

It works very good but I have one issue:

In Alarmo, if I set the ‘Armed Home’ to have an exit delay of 2 seconds (just for visual confirmation) then it gets armed BUT the Frient keypad keeps bleeping as though it did not get the confirmation. I tested this a bunch of times for all other modes and the others work well. But for Armed Home, the keypad keeps beeping.
Alarmo explicitly has an option to give a custom exit/entry delay, so it ‘should’ be supported. I wonder if this happens for others too?

39

Literally a few posts above yours, buddy. Simple Blueprint : Zigbee2MQTT Frient Keypad for Alarm control panel (ex: Alarmo) - #28 by Cengolotti

1 Like
40

I should have read it properly, thanks!
I used this fork and confirm its fixed (as well as other improvements): GitHub - rado0x54/frient_keypad_alarmo: Blueprint for HomeAssistant for Frient keypad with Alarmo

1 Like