#Automation turning off switch, then turning it back on 1 second later

1 messages · Page 1 of 1 (latest)

frigid beacon
#

Have an automation to turn off a zwave light switch at midnight. For the most part it works fine, but last night I'm finding that it turned off, then turned it back on immediately one second later [see attached image]. Only change is that I updated the home assistant docker container yesterday.
What the heck happened, and how can I assist on getting this fixed?

mortal quarry
#

you'll need to share the YAML

rustic quartzBOT
#

To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.

frigid beacon
#

The specific automation config is:

- id: '1728224315258'
  alias: Outside mini cans off at midnight
  description: Turn the outside mini can lights off at midnight
  triggers:
  - trigger: time
    at:
      entity_id: sensor.sun_next_midnight
      offset: -00:05:00
  conditions: []
  actions:
  - type: turn_off
    device_id: 0feb0a1d50c8906b1363ac7bffc29869
    entity_id: 0349b09bf4e9fd358a11e3cce7942c9f
    domain: switch
  mode: single
mortal quarry
#

there's no "turn on" in there at all

#

I suggest looking at the automation traces for those runs

frigid beacon
#

Right! 😕

#

How can I look at automation traces?

frigid beacon
#

I believe that says about the same 😕

mortal quarry
#

The only thing that I can think of is that it's either something about the device itself, or that switch is actually a template switch that has some additional actions in it

#

you can run that action yourself and see what happens

peak karma
frigid beacon
#

Clicking on it brings me to the same automation.
This is weird now, last night, it was successful