Something’s changed in an update of Hass. I updated to the latest version recently and had to remove all my instances of the blueprint Motion Activated light brightness and add them again, because of the error message Error in describing trigger: Cannot read properties of undefined (reading ‘includes’). I have searched the forum and found threads in different places that describes the same problem for other automations and blueprints. Does anybody know what has changed that can have caused this? I am using the exact same blueprint at another location, and there I get the message Unknown trigger, 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 has happened between those versions, but what?
Did you mean to post this in developement?
Well, I thought it was a development issue since something obviously must be changed within the inner workings, but please move me if that’s wrong.
Development is about asking questions on how to develop things for HA.
Ah, sorry! Ok, I’l move it to general.
Post your trigger, likely something changed with your device causing the issue.
That would surprise me, since it happened with six different automations on the same system, all at the same time, and they all have their own triggers. The trigger is a template:
{{ ('on' in states('input_boolean.bevegelsesstyrt_lys_pa_badet')) and ('on' in states('binary_sensor.alle_bevegelsessensorer_pa_badet')) }}
The state for the template called binary_sensor.alle_bevegelsessensorer_pa_badet is a sensor group, in this case with two physical motion sensors, and in the other cases one each, plus one virtual sensor that is really a boolean switch. The boolean in the template is a switch that stops the triggering completely, for when we are away. I have of course checked, and none of them are off, while noen of the virtual motion sensors are on.
FYI, if this is just displayed in the UI, the ui is just having trouble displaying the data. Clear your cache and refresh the page.
I just opened the automation in a browser on a computer that has never been connected to this instance of Hass earlier, and I get the same thing. The silly thing is that I may have deleted and recreated them all, I thought I saved one for checking, but no. So the traces now show that they are working. Still I’d like to know what’s changed, so I can avoid the problem when I upgrade my second location.
it’s because you’re using device triggers. There may be a bug, but this will continue to crop up for people using them. The bug is only in the frontend, so the backend is going to work normal.
Right. I just saw something about a device trigger being a problem for a similar Zigbee thread. But it didn’t work as normal, the lights did not turn on until I deleted and recreated the automation. The missus was not amused… 
So you mean that I should use entity triggers instead? The templates themselves are entities, as far as I know, not devices. Is it the Z-Wave motion sensors that I need to change on? As far as I can see the motion sensing is an entity. So where are the devices in the triggering? I’m honestly confused.
I have no idea, I’m making assumptions here based on what i’ve read. But this is a frontend problem and the only way to really diagnose it is for you to share screenshots of the error for every automation affected while also posting the automation yaml.
The automation is extremely short, since it’s based on a blueprint. Here’s one of them:
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 a screenshot of the error message for the same automation, which now works since I have recreated it:
Can you post that please
Of course! Thank you for takinge the time to look at this! Here it is:
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
Everything looks fine, you should probably craete an issue on homeassitant/frontend on github with this data.
Thanks, I will try! I thought this had to be something in the inner workings since the automations didn’t work at all until I recreated them, but can it still be the frontend?
it likely still is frontend, unless you can show the backend log with an accompanied error
Damn, I wish I hadn’t recreated those automations… I looked at the log from today, and I couldn’t find anything regarding that there. Maybe this is one of those ghosts that can’t be traced, since I see that the error has been reported at least since 2024. 
Issue created, I hope it is in a format they will accept. At least I tried. 