home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.03k stars 28.27k forks source link

Automations stop working, needs to be recreated to work again #108999

Closed 0verEngineer closed 1 week ago

0verEngineer commented 3 months ago

The problem

I have a few automations and they are driving me crazy, sometimes one or two automations stop working and a restart of the docker container did not fix it, the only fix is deleting the automation and recreating it from the exact same yaml, it works again instantly.

Edit: I can toggle the light in homeassistant and zigbee2mqtt while the automation does not work and the motion sensor does also show the motions in zigbee2mqtt and homeassistant

This is the automation where i have this problem currently:

description: ""
condition:
  - condition: state
    entity_id: input_boolean.enable_all_motion_activated_lights
    state: "on"
use_blueprint:
  path: homeassistant/motion_light.yaml
  input:
    motion_entity: binary_sensor.motion_sensor_02_office_occupancy
    light_target:
      entity_id: light.lightswitch1_office_lightswitch1_office
    no_motion_wait: 300

What version of Home Assistant Core has the issue?

core-2024.1.5

What was the last working version of Home Assistant Core?

non existent

What type of installation are you running?

Home Assistant Container

Integration causing the issue

MQTT

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

codyc1515 commented 3 months ago

What happens when you run it manually?

issue-triage-workflows[bot] commented 2 weeks ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.