Error loading automation (500) in Web GUI

Configuration
6

OK. I found what the issue was. I have a manual alarm with an automation that disarms it when I return home. I used the code from this site: Disarming a manual alarm control panel in automation with a code

Here’s what I have in my automations.yaml file for this:

- id: disarm_when_brian_returns_home
  alias: "Disarm when Brian returns home"
  trigger:
    - platform: state
      entity_id: device_tracker.brians_iphone_12_pro
      from: not_home
      to: home
  action:
    service: alarm_control_panel.alarm_disarm
    entity_id: alarm_control_panel.house_alarm
    data:
#      code: !secret alarm_code
      entity_id: alarm_control_panel.house_alarm

The problem is the line that I’ve commented out. I believe that this is a result of the 2021.4 upgrade where secrets are not allowed in other yaml files.

At this moment, we are unsure if this is a breaking change or not, so we list it, just to be sure.

We are now explicitly only supporting secrets inside your Home Assistant Core and Lovelace configuration files (and anything included from there). Secrets are no longer supported in other loaded YAML files.

This change should not affect regular users of Home Assistant, however, we have been made aware that some custom integrations may cause problems. If you are a user of Dwains theme, the HomeKit Infused theme or lovelace_gen, please make sure to update those or check with the upstream project.

2 Likes