bkbartk
(Bkbartk)
June 10, 2024, 9:56am
1
Hello,
I have an alarm without code. and since v 2024.6.1 the service does not allow me to enable it without code.
I use this service
service: alarm_control_panel.alarm_arm_away
target:
entity_id: alarm_control_panel.home_alarm
data: {}
and the following error shows up
Failed to call service alarm_control_panel.alarm_arm_away. Arming requires a code but none was given for alarm_control_panel.home_alarm
just adding a random code seems to work
data:
code: "0"
but I still need to check disarm and then check all my automations, but I think using no code should be allowed again, because I cannot imagine I’m the only one suffering here.
IoTPlay
(Jéan)
June 10, 2024, 6:59pm
2
Same problem - interface stopped working as result of that - and in the config file - the following line does not work:
code_arm_required: false
bkbartk
(Bkbartk)
June 10, 2024, 7:12pm
3
I actually got it working,
I have a bit of a weird config but
alarm_control_panel:
- platform: manual
name: Home Alarm
# code: "1234"
arming_time: 1
delay_time: 1
trigger_time: 1
disarmed:
trigger_time: 1
armed_home:
arming_time: 1
delay_time: 1
code_arm_required: false
- platform: template
panels:
safe_alarm_panel:
value_template: "{{ states('alarm_control_panel.home_alarm') }}"
arm_away:
# - condition: state
# entity_id: group.users
# state: not_home
- service: alarm_control_panel.alarm_arm_away
target:
entity_id: alarm_control_panel.home_alarm
data:
code: "0"
arm_home:
service: alarm_control_panel.alarm_arm_home
target:
entity_id: alarm_control_panel.home_alarm
data:
code: "0"
disarm:
# - condition: state
# entity_id: group.users
# state: home
- service: alarm_control_panel.alarm_disarm
target:
entity_id: alarm_control_panel.home_alarm
code_format: no_code
code_arm_required: false
code_arm_required: false
and
data:
code: "0"
are both needed,
Also in the automations you need to add the last part on every arm event.
disarm you still can do without code.
anyone know if this has been fixed in 2024.6.3?
No, unfortunately not fixed in 2024.6.3.
oh dear. Thats a pity. Hope someone is aware and fixing…