Core 2024.6.x Alarm Panel Fix

M3Power95 · June 10, 2024, 5:20pm

Hello everyone. Not sure if this belongs here, but I couldn’t think of a better place to put it. It seems that with the HAOS Core 6.x update, it has broken the alarm panel functions for “arm home” and “arm away” functions in the lovelace card whereby it now requires a code to be input. I have tested this with both my RingMQTT and Aarlo integration and both are broken now due to this issue. Request fixing Core 6.x to fix the alarm panel entity discovery to set code_arm_required to false by default like I believe it was before.

nickrout · June 10, 2024, 8:07pm

There is no core 6.x. please correct your post.

Also not a feature request. Moving…

And aarlo and ringmqtt seem to be custom integrations. If they are, ask there.

M3Power95 · June 10, 2024, 8:32pm

Sorry, by Core 6.x I meant to say any of the Core updates so far within the “6” major revision (“2024.6.x”). This issue only occurred when I updated to HA Core 6.0, and 6.1 did the same thing. All else being equal, I moved back to Core 2024.5.5 and it resolved the issue, leading me to think it was an issue with the HA Core update.

nickrout · June 10, 2024, 8:39pm

If you mean 2024.6, damn well say it.

tom_l · June 11, 2024, 2:20am

github.com/home-assistant/core

Manual alarm now requires code to disarm

opened 03:15PM - 08 Jun 24 UTC

closed 05:11PM - 10 Jun 24 UTC

cweakland

integration: manual

### The problem On v2024.6.1 you can not disable the code for disarming. I se…e this is a feature of the MQTT alarm, but not for the manual alarm, can code_disarm_required be added to this integration? I understand that I can add the code into an automation to disarm, and this partially achieves my goal. However, if you use the UI you must enter a disarm code. ### What version of Home Assistant Core has the issue? 2024.6.1 ### What was the last working version of Home Assistant Core? 2024.5 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Manual Alarm ### Link to integration documentation on our website https://www.home-assistant.io/integrations/manual/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml configuration.yaml: alarm_control_panel: - platform: manual name: house trigger_time: 600 disarm_after_trigger: false delay_time: 0 arming_time: 0 code_arm_required: false code: !secret alarm_code ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

M3Power95 · June 11, 2024, 2:30am

Thanks for this workaround! Is there a function I can add in that yaml for code_disarm_required? Or does removing “code: !secret alarm_code” in the yaml code work for disarming and arming without a code in the UI? If I’m using HA I don’t want to have to use the code at all like I can with 2024.5.x versions of core.

Thanks

tom_l · June 11, 2024, 2:50am

Share your current alarm config.

M3Power95 · June 11, 2024, 3:09am

No special config in my config.yaml file. Just using the basic alarm panel provided by the lovelace frontend:

square: false
type: grid
columns: 1
cards:
  - states:
      - arm_home
      - arm_away
    type: alarm-panel
    entity: alarm_control_panel.newcastle_alarm
    name: Ring System
  - states:
      - arm_home
      - arm_away
    type: alarm-panel
    entity: alarm_control_panel.aarlo_location_home
    name: Arlo System

This is what is currently working in Core 2024.5.5 (I’ve reverted back since Core 2024.6.x broke these). These are working through the Ring MQTT and Arlo integrations.

tom_l · June 11, 2024, 4:08am

That’s your card config not your alarm config.

I see you are using the RingMQTT add-on which uses discovery. So there will be no yaml config you can change.

However, according to this there is a new version of the add-on that fixes it. You just need to update.

github.com/tsightler/ring-mqtt

HA 2024.6 - Can't change Ring mode - requires code

opened 11:58AM - 06 Jun 24 UTC

closed 05:34PM - 08 Jun 24 UTC

Scope666

Home Assistant

### Describe the Bug Can't change Ring Mode (Disarmed, Home or Away) for camera…s ### Steps to Reproduce Try to change mode without owning a Ring Alarm system. ### Expected Behavior Works successfully without throwing error. ### Log Output ```shell 2024-06-06 07:47:42.309 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [23151872931536] Arming requires a code but none was given for alarm_control_panel.branchburg_mode This was working fine in 2024.5 and before. ``` ### Screenshots ![Screenshot_1](https://github.com/tsightler/ring-mqtt/assets/31927547/577159bc-96a0-4ca7-9cd9-8e0a450dd269) ### Config File ```shell { "mqtt_url": "mqtt://192.168.1.200:1883", "mqtt_options": "", "livestream_user": "", "livestream_pass": "", "disarm_code": "", "enable_cameras": true, "enable_modes": true, "enable_panic": false, "hass_topic": "homeassistant/status", "ring_topic": "ring", "location_ids": [ "" ] } ``` ### Install Type Docker - Unraid ### Version v5.6.4 ### Operating System Unraid ### Architecture x86_64 ### Machine Details 12th Gen Intel® Core™ i7-12700 @ 2079 MHz

M3Power95 · June 11, 2024, 12:14pm

Thank you. I did see the Ring MQTT update that fixes this issue. However I still have the issue on the Arlo side, and that integration hasn’t been changed yet so I don’t want to have one system working and one not working. I guess the best thing to do is just wait for the Arlo update before updating to the 2024.6.x core?

pergola.fabio · June 16, 2024, 8:30pm

Seeing the same thing, using an mqtt alarm, and now it displays a huge keypad, how to disable it?

nickrout · June 16, 2024, 8:35pm

Speak to the developer of that integration.

M3Power95 · June 25, 2024, 3:29am

Both Ring and Arlo have been fixed. Ring MQTT integration fixed it directly, and now you can go into the Arlo integration config and disable the alarm requirement via the UI. It worked for me and I’m now on the latest version of HA Core and back to the way things were!

Arcane1980 · August 29, 2024, 1:28pm

I only just added Arlo to my system today, so I don’t know if it has ever worked in past revisions, but my card has the same issue I think.

This is how the card is coded. It looks lovely and clicking on the buttonm appear to function, but they don’t make the change or retain their state on exit.

states:
  - arm_home
  - arm_away
  - arm_night
type: alarm-panel
entity: alarm_control_panel.aarlo_arlo_base_station
name: Camera Arming