Issue Arming Alarm since most recent update with envisalink

Configuration
21

for me its not fixed. Still error “Arming requires a code but none was given for alarm_control_panel.cellar_alarm”

but I have disabled code in configuration. Why its even needed when arming?

1 Like
22

Show your config yaml (without your code obviously)

Mines is working perfectly fine on 2024.6.2 now.

23

add the following to your yaml file under the alarm section.
code_arm_required: false

2 Likes
24

It works! Thank you!

25

Where exactly do I add this line? I’m using a different alarm integration, so that’s probably the issue but I want to see if this works. If I add it in the script that calls the entity to arm the alarm, it errors with “Extra keys are not allowed…”
If I put it under configuration where my alarm integration is set up, it errors for a bad configuration.

26

code_arm_required: false in the envisalink configuration causes the module to not load due to bad configuration.

This doesn’t work for me. I feel like I have a project coming up to replace my alarm system, since this integration isn’t seeing any effort.

27

Quickly fixed with @iprowell’s explanation above eg; code_arm_required: false

Many thanks!

28

…aaaand how do you do that, since it breaks the configuration? No, nope nevermind, I yanked mine out and replaced it with a modern solution already. I just find it frustrating that there’s this sort of half information going around here that only seems to work for a select few.

29

I switched to the (AWESOME) new integration to resolve the code_arm_required issue with Envisalink. The migration was so seamless; didn’t need to redo any entities or automations. Highly recommended:

30

Hi,
The issues that have been reported by @NathanCu, @esk1 and others, look to be closed and merged to the releases, but the problem still exists on my end.

Problem is that I still have code_arm_required: true in the attributes of envisalink alarm_control_panel entity, and this attribute cannot be changed.

So the current behavior in 2024.9.latest is that one still require to input the alarm code for the arm to work. Either manually in the GUI alarm keypad or in a script, like:

- action: alarm_control_panel.alarm_arm_home
    metadata: {}
    data:
      code: !secret alarm_code
    target:
      entity_id: alarm_control_panel.my_alarm

Has anybody achieved the following expected behavior with the official integration?

  • ARM HOME and ARM AWAY do not require code input in the UI or in a script
  • Code is required always when disarming the alarm, from UI or script. (so there is no code: defined under envisalink: in configuration.yaml

?