Automation- Trace- Error in describing trigger:

stevemann · February 15, 2026, 4:28pm

Searching the forum, I see this issue going back a few years, but this is new for me. Trace doesn’t work, but the automation does.

Error in describing trigger: Cannot read properties of undefined (reading ‘includes’)

Any ideas if this can be fixed?
Note, I do not use the Automation UI or Blueprints

- id: 'driveway_person_presence'
  alias: Driveway person Presence
  description: Turns on driveway light when persons are detected in the driveway.
  trigger:
    - id: person_entered_zone
      platform: state
      entity_id: binary_sensor.driveway_zone_person_occupancy
      from: "off"
      to: "on"
  condition:
    - condition: sun
      after: sunset
      before: sunrise
  action:
    - service: light.turn_on
      target:
        entity_id: light.driveway_light_light
  mode: single

123 · February 15, 2026, 6:04pm

It’s a bug that will be fixed in the next release.

github.com/home-assistant/frontend

Error in describing trigger: Cannot read properties of undefined (reading ‘includes’)

opened 06:23PM - 11 Feb 26 UTC

closed 07:51PM - 11 Feb 26 UTC

Mastiffen

### Checklist - [x] I have updated to the latest available Home Assistant versi…on. - [x] I have cleared the cache of my browser. - [x] I have tried a different browser to see if it is related to my browser. - [x] I have tried reproducing the issue in [safe mode](https://www.home-assistant.io/blog/2023/11/01/release-202311/#restarting-into-safe-mode) to rule out problems with unsupported custom resources. ### Describe the issue you are experiencing It was suggested that I opened this as an issue here, by an admin on the board. I have searched the board and it seems to have raised it's head in other users' automations at least a year or two back. Today all my motion sensing automations based on the motion activated light brightness stopped working. I see the same error in them all. I had to delete them all and recreated them to get them working again. This is the automation that runs on the blueprint: ```yaml alias: Bevegelsesaktivert lys på soverom i andre oppe description: "" use_blueprint: path: Aleks130699/motion_light_brightness.yaml input: motion_entity: binary_sensor.templatebevegelsessensor_pa_soverom_i_andre_oppe on_night_time: "23:00:00" off_night_time: "07:00:00" day_brightness: 100 night_brightness: 20 light_target: entity_id: light.dimmer_for_taklys_pa_soverom_i_andre ``` Here's the blueprint: ```yaml blueprint: name: Motion-activated Light-brightness description: Turn the light on to brightness when motion is detected, depending on the selected time period, different brightness and turn-on time. domain: automation input: motion_entity: name: Motion Sensor selector: entity: domain: - binary_sensor device_class: - motion multiple: false light_target: name: Light selector: target: entity: - domain: - light on_night_time: name: (Required) On Time Night description: The time when the night mode starts. selector: time: {} off_night_time: name: (Required) Off Time Night description: The time when the night mode ends. selector: time: {} day_brightness: name: Day brightness description: Brightness, in daytime mode default: 1 selector: number: min: 1.0 max: 100.0 step: 1.0 mode: slider night_brightness: name: Night brightness description: Brightness, in night mode mode default: 1 selector: number: min: 1.0 max: 100.0 step: 1.0 mode: slider no_motion_wait_day: name: Wait time day description: Time to leave the light on after detecting the last movement for daytime mode. default: 120 selector: number: min: 0.0 max: 3600.0 unit_of_measurement: seconds mode: slider step: 1.0 no_motion_wait_night: name: Wait time night description: Time to leave the light on after detecting the last movement in night mode default: 120 selector: number: min: 0.0 max: 3600.0 unit_of_measurement: seconds mode: slider step: 1.0 source_url: https://gist.github.com/Aleks130699/5021baf8f4f1d63800d0f42842ba62b5 mode: restart max_exceeded: silent trigger: platform: state entity_id: !input motion_entity from: 'off' to: 'on' action: - choose: - conditions: - condition: time after: !input on_night_time before: !input off_night_time sequence: - alias: Turn on the light service: light.turn_on data: brightness_pct: !input night_brightness target: !input light_target - alias: Wait until there is no motion from device wait_for_trigger: platform: state entity_id: !input motion_entity from: 'on' to: 'off' - alias: Wait the number of seconds that has been set delay: !input no_motion_wait_night - alias: Turn off the light service: light.turn_off target: !input light_target default: - alias: Turn on the light service: light.turn_on data: brightness_pct: !input day_brightness target: !input light_target - alias: Wait until there is no motion from device wait_for_trigger: platform: state entity_id: !input motion_entity from: 'on' to: 'off' - alias: Wait the number of seconds that has been set delay: !input no_motion_wait_day - alias: Turn off the light service: light.turn_off target: !input light_target ``` The trigger is a template sensor, that allows the automation to be deactivated wit a boolean in other automations (activating and deactivating the automations themselfes has to many possible errors): `{{ ('on' in states('input_boolean.bevegelsesstyrt_lys_pa_badet')) and ('on' in states('binary_sensor.alle_bevegelsessensorer_pa_badet')) }}` The `binary_sensor.alle_bevegelsessensorer_pa_badet` is a sensor group with two physical Z-Wave motion sensors and one virtual sensor, a boolean that can be swithed by other automations to keep the light on in the controlled room. Here's a screenshot of the trace, unfortunately after I recreated the automation, so it worked again, but the error message is there: <img width="1729" height="953" alt="Image" src="https://github.com/user-attachments/assets/3433337f-d0e8-4c4c-bb5e-c20193671a32" /> So deleting and recreating the automations seems to fix that they are not workin, but I don't know for how long. I am using the exact same blueprint at another location, and there I get the message `Unknown trigger` in trace, but the automation works as they should. At that location I have version 2025.11.3, while the version in my house with the problem is 2026.2.1. So something seemed to have happened between those versions. ### Describe the behavior you expected It should just keep on working. ### Steps to reproduce the issue 1. The steps are in the description. 2. 3. ... ### What version of Home Assistant Core has the issue? 2026.2.1 ### What was the last working version of Home Assistant Core? 2025.11.3 ### In which browser are you experiencing the issue? _No response_ ### Which operating system are you using to run this browser? WIndows 10 Pro ### State of relevant entities ```txt ``` ### Problem-relevant frontend configuration ```yaml ``` ### JavaScript errors shown in your browser console/inspector ```txt ``` ### Additional information _No response_

If you want to eliminate the error message now, simply update your automation’s syntax.

trigger → triggers
condition → conditions
action → actions

platform → trigger
service → action

- id: 'driveway_person_presence'
  alias: Driveway person Presence
  description: Turns on driveway light when persons are detected in the driveway.
  triggers:
    - id: person_entered_zone
      trigger: state
      entity_id: binary_sensor.driveway_zone_person_occupancy
      from: "off"
      to: "on"
  conditions:
    - condition: sun
      after: sunset
      before: sunrise
  actions:
    - action: light.turn_on
      target:
        entity_id: light.driveway_light_light
  mode: single

123 · February 16, 2026, 12:43pm

Did you try updating the automation’s syntax or will you wait for the next release?

stevemann · February 16, 2026, 7:41pm

Thanks.

All of my automations are manually generated. If the Automations syntax has changed, no one highlighted it.

123 · February 16, 2026, 10:39pm

You’re welcome!

Please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which indicates to others that this topic has been solved. This helps other users find answers to similar questions.

For future reference, the syntax modification was described in the following release notes:

FWIW, I also use a text editor to create/modify my automations. Even though the old syntax was not deprecated, I updated all of my automations to the new syntax this past summer.

Rather than do a global search & replace, I took the opportunity to review each one (add some refinements where possible). It was a wee bit of a chore but I spread the work out over a few sessions and ultimately ended up with neater, future-proof automations.

stevemann · February 16, 2026, 10:51pm

I have 228 old-school automations… I think that back in 2024 I was just skimming for “Breaking changes”, but since then I have been reading the releases more closely.

For some reason I don’t always see the solution icon every time I open a thread I started.

mmiller7 · February 20, 2026, 12:23am

It really feels like if this kind of stuff is going to break the system it ought to be in breaking changes…like you, I carefully review those but if stuff isn’t being deprecated and works, why would I think I need to change it?