Automation state change trigger stopped firing

Configuration
1

I’m at a bit of a loss, my ‘washer complete’ notification automation recently stopped working when the washer state changes to ‘Finished’… I can check the ‘Traces’ and the little blue UI banner shows “triggered”, but the trace generated shows that none of the blocks were executed. This was working, but seems to have broken with a recent update. Am I missing something to get this to trigger properly? I can see the entity state changes in history, but none of the available states show up as options when creating the automation trigger… it’s like it won’t acknowledge the other states exist.

alias: Clothes Washer Cycle Complete Notification
triggers:
  - trigger: state
    entity_id:
      - sensor.az306932n_laundry_machine_state
    not_from:
      - Unknown
      - Unavailable
    to:
      - Finished
2

In the three dot menu on the top right of the trace, download it and paste it here please.

1 Like
3

You *might want to supply the entire automation. Taking your statement at face value, the trigger may have worked and nothing ran because of a problem elsewhere.
It makes it much easier for us to offer constructive answers if you follow Community Guidelines #9. 11, & 14 by supplying a properly formatted configuration for the automation that you have attempted. Please share the YAML and any errors so we can see what you’ve done.

2 Likes
4

Paste the full automation and its trace so we can help you debug it.

Only thing that I can see, based on what you have provided, is that your states are capitalised. AFAIK, states should always be in lowercase:

alias: Clothes Washer Cycle Complete Notification
triggers:
  - trigger: state
    entity_id:
      - sensor.az306932n_laundry_machine_state
    not_from:
      - unknown
      - unavailable
    to:
      - finished
1 Like
5

Sorry guys, I didn’t even know there was a way to download the trace details. Looking at that actually solved my problem because it shows details that are not in the UI trace information.

Turns out, I apparently have a problem in my variables section… Not entirely sure why yet, as I copied the setup from another working automation, so I need to debug a little.

I will post more details on the automation itself and the issue I found with the trace when I’m at my PC next.

1 Like
6

Turns out I was trying to use variables at the top level of an automation, and that’s apparently not supported. I moved it under the actions section and it’s working again. Apparently it stopped working right around the time of an update because I had made that variable addition… I’d forgotten I added that… so makes sense that something broke.

Here’s the updated YAML that’s now working (it’s at least firing the initial notification, I think I still need to make some other tweaks with how the script part is working).

alias: Clothes Washer Cycle Complete Notification
triggers:
  - trigger: state
    entity_id:
      - sensor.az306932n_laundry_machine_state
    not_from:
      - Unknown
      - Unavailable
    to:
      - Finished
actions:
  - variables:
      clothes_moved: "{{ 'MOVED_' ~ context.id }}"
  - action: input_boolean.turn_on
    target:
      entity_id: input_boolean.wet_laundry_in_washer
    data: {}
  - action: notify.all_general
    data:
      message: Clothes washer has finished a cycle.  Please move wet clothes to dryer.
      title: Clothes Washer Cycle Complete
      data:
        actions:
          - action: "{{ clothes_moved }}"
            title: CLOTHES MOVED
        tag: washing_machine
        group: laundry
        notification_icon: mdi:washing-machine-alert
  - action: script.laundry_monitor_script
    data:
      clothes_moved: "{{ clothes_moved }}"
1 Like