85.1 changes trigger behavior?

Configuration
1

I’ve had the below automation for quite some time and it’s worked well to catch lights left on and shut them off. But with the move from 84.6 to 85.1 it is no longer triggering. Nothing has been changed; no errors in the logs; it just doesn’t trigger.

I’ve looked at the release notes and can’t see anything related.

Anyone have any ideas?

   trigger:
      - platform: state
        entity_id:
           - switch.basement_stairs_switch
           - switch.garage_switch
           - switch.mudroom_light_switch
           - switch.upstairs_hallway_switch
        to: 'on'
        for:
           minutes: 45
2

Check the entlity_ids of your switches in the dev tools states menu. They may have changed.

Do you have any conditions for this automation?

3

No conditions, stripped it down to debug. Entity ID’s all check out in template editor and show proper state and last_changed times

It’s really really odd…

4

Your list of switch ids are indented one space too many. Not sure if that will make a difference.

5

Thanks, I took a look at that and the VS Code yaml linter doesn’t complain; it is a consistent with everything else at that level.

But I removed a space on all of them and restarted and… same issue…

It seems any trigger with a list of entities and a “for” configured is not working correctly… I tested this and its consistent. Without the for it seems to trigger correctly.

6

That’s odd. I’m on 0.85.1 and my automations with for: in the triggers are working:

- id: hallway_lights_auto_off
  alias: 'Hallway Lights Auto Off'
  trigger:
    platform: state
    entity_id: binary_sensor.pir_hall
    to: 'off'
    for:
      minutes: 1
  condition:
    - condition: state
      entity_id: light.lifx_hallway
      state: 'on'
  action:
    - service: light.turn_off
      entity_id: light.lifx_hallway

I don’t have any with multiple triggers though.

7

I have multiple entities in triggers and hey appear to be working in 85.1

I do use a comma separated list though:

  - alias: stair lights off if no movement
    initial_state: true
    trigger:
      platform: state
      entity_id: binary_sensor.motion_sensor_158d0001d5c926, binary_sensor.motion_sensor_158d0001a24dde, binary_sensor.motion_sensor_158d000163e2c1
      to: 'off'
      for: 
        seconds: 2
    action:
      - service: light.turn_off
        data: 
          entity_id: light.stairs
          transition: 30
8

Rolled back to 84.6 and it all works without any changes…

9

sounds like it’s time to file bug report.

10

I’m having a similar issue with 0.85.1. I haven’t narrowed it down to what, but some of my automations no longer work, some very basic ones, with no error in the log.

11

Are your automations enabled?

12

Yup, double checked it and also manually fired to make sure it runs clean

13

I’ve now back to back tested this on 84.6 and 85.1 and definitely an issue on 85.1; but fine under 84.6

14

Is it only automations with a list of triggers?

15

Correct, single works.

16

Bump; still seeing this on 86.3.

17

You need to submit an issue.

(Sorry, not you @finity - I replied to the wrong message and can’t edit it).