If I have multiple to: states in a trigger, do I have to make a separate entry for each one?

This doesn’t seem to work.

You need a separate trigger. The dropdown won’t normally let you put in a list like that - did you type it?

Yeah, I typed it in.

According to this thread, it should work. I’m trying it in YAML list mode now.

1 Like

You’re right, you have to do it in yaml.

1 Like

So it seems this still doesn’t work. Anyone know what’s wrong with this YAML?

alias: Litter Robot Fix
description: ""
trigger:
  - platform: state
    entity_id:
      - vacuum.downstairs_office_litter_box
    id: downstairs
    to:
      - Error
      - Unavailable
      - Unknown
    for:
      hours: 0
      minutes: 3
      seconds: 0

try with all lowercase.

1 Like

omg you’re right. It shows caps in the integration, but I see in Dev Tools that its in lowercase.

Are you sure error is an actual state? I don’t believe I’ve ever seen that listed anywhere in any integration.

To be clear, it’s not gonna break your automation if id doesn’t exist. Just wanted to point it out in case you expect the automation to trigger on an inexistent state.

I’m 100% positive that the state earlier today was ‘error’. For some reason, when I reset my wifi, the LR never reconnects. Apparently $700 isn’t enough to spend to get a good wifi module…

LR = Ubiquiti LR?

Don’t get me started on that!

No sorry, Litter Robot. :rofl:

1 Like

For reasons I still can’t figure out, this isn’t triggering. What is wrong with me???

alias: Litter Robot Fix
description: ""
trigger:
  - platform: state
    entity_id:
      - vacuum.downstairs_office_litter_box
    id: downstairs
    to:
      - error
      - unavailable
      - unknown
    for:
      hours: 0
      minutes: 3
      seconds: 0
  - platform: state
    entity_id:
      - vacuum.upstairs_office_litter_box
    id: upstairs
    to:
      - error
      - unavailable
      - unknown
    for:
      hours: 0
      minutes: 3
      seconds: 0

Anyone got any idea what I’m doing wrong?