core: Stopped because of unknown reason "null" at

The problem

Since version 2023.8.x I have an automation that has the following error when it executes with triggers. If I execute it manually then everything works.

Stopped because of unknown reason “null” at 5 août 2023 à 07:05:50 (runtime: 0.19 seconds)_

alias: Désactivation mode nuit
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.mouvement_bureau
      - binary_sensor.mouvement_cuisine
      - binary_sensor.mouvement_salon
    from: "off"
    to: "on"
condition: []
action:
  - service: scene.turn_on
    data: {}
    target:
      entity_id: scene.mode_jour
mode: single

What version of Home Assistant Core has the issue?

2023.8.x

What was the last working version of Home Assistant Core?

2023.7.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Automation

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 18 (10 by maintainers)

Most upvoted comments

Can you create a separate issue?

So the service to turn off the automation has an argument called “stop actions” which, as the name implies, stops all actions. When you turn off an automation via the UI you always stop the actions (which kinda seems logical to me, because for example you have an automation with a long timer or something similar and if it didn’t automatically stop that action when you turn it off you could end up with running this automation 10 times unless you manually call a service to stop everything, you get the point).

So the quick fix for you for now is turning the automation off via the automation itself and then passing false as argument like so

action:
  - service: scene.turn_on
    data: {}
    target:
      entity_id: scene.test
  - service: automation.turn_off
    data:
      stop_actions: false
    target:
      entity_id: automation.97828

I am still going to try to figure out how we can improve this error message

Ah that worked. I can reproduce this on my production environment, I’ll try to do the same on my dev environment and then I will check where it goes wrong