No longer able to arm alarm through HomeKit

[Depechie]

The problem

I have a Verisue alarm that is available as an alarm panel in Home Assistant through the Verisure integration. Thanks to the HomeKit bridge in Home Assistant I can use it in HomeKit to arm and disarm. But since Home Assistant 2024.6 the arm function does no longer work stating that I did not provide a code to arm it. Although the code is passed along in the YAML configuration of HomeKit in Home Assistant.

I think the change made to the alarm panel to being able to provide a default code is the culprit here... https://www.home-assistant.io/blog/2024/06/05/release-20246/#other-noteworthy-changes

What version of Home Assistant Core has the issue?

core-2024.6.2

What was the last working version of Home Assistant Core?

core-2024.5.x

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Verisure HomeKit

Link to integration documentation on our website

https://www.home-assistant.io/integrations/verisure/ https://www.home-assistant.io/integrations/homekit/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Error log: homeassistant.exceptions.ServiceValidationError: Arming requires a code but none was given for alarm_control_panel.verisure

Additional information

No response

[oakedcorn]

I added "code_arm_required: false" - this seems to have solved it.

alarm_control_panel:

• platform: template panels: alarm: code_format: no_code code_arm_required: false value_template: ...

[home-assistant[bot]]

verisure documentation verisure source

[Depechie]

I added "code_arm_required: false" - this seems to have solved it.

alarm_control_panel:

• platform: template panels: alarm: code_format: no_code code_arm_required: false value_template: ...

@oakedcorn not able to test this yet ( will do later when I'm at home ) But I do not get it why this would fix it, because the Verisure alarm can only be armed with a code. So setting that property is contradicting that and feels weird. Or maybe the naming is wrong and the property would mean that you actually need to fill in a code through the UI...? Anyhow, I will test it out later and report back.

Update @oakedcorn I can't seem to make it work with your extra YAML suggestions, my alarm still does not get armed

[oakedcorn]

@Depechie, I received the exact same error as you "Arming requires a code", but I'm not using the Verisure plugin. Instead I have an alarm_control_panel template that maps a HA alarm entity to the ultrasync integration. So this is different from your setup. Nonetheless, I think the issue is that somewhere (probably the HA alarm entity) a default of "require code on arm" has recently changed from false to true.

[oakedcorn]

This ticket seems to be related: https://github.com/home-assistant/core/issues/118882

[SpectrumTech]

Wow, HA works one way for how long? And then someone comes along and decides the default action should be the exact opposite of how it was working without considering how that might affect things. If you need to make something work for you, why don’t you create the edge case for yourself? At least create a work around instead of forcing everyone to enter a code to arm the alarm. And who the heck does that anyway? I get disarming the alarm maybe. If crooks are breaking in your house to arm your alarm for you… that’s kinda weird.

[Depechie]

Hey @gjohansson-ST was HomeKit also in the picture with your #118961 fix? Because the weird thing is, that all other items in the issues list speak of not needing a code. But my setup has a code! It is configured in he HomeKit config:

  alarm_control_panel.verisure_alarm:
    code: !secret verisure_alarm

[home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homekit` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homekit` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

homekit documentation homekit source _{^{(message by IssueLinks)}}

[Depechie]

Hey @frenck I know you also had some history with the Verisure integration. Do you have a similar setup with HomeKit? Or any insights on how to get this working again? Kinda bummer that since 2024.6 I can no longer operate my alarm.