core
core copied to clipboard
Automations not visible anymore after upgrade to 2024.2.0
The problem
Since the 2024.2.0 update, I cannot see any configured automation in the app or on the website. I do not see anything in the log to have any clue where this issue comes from. The automations are still in the automations.yaml file.
I cannot test whether the automations work, as I also have a ZHA start issue. Will test whether the automations are working when the ZHA issue is resolved.
What version of Home Assistant Core has the issue?
2024.2.0
What was the last working version of Home Assistant Core?
2024.1.6
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Automation
Link to integration documentation on our website
https://www.home-assistant.io/docs/automation/
Diagnostics information
No response
Example YAML snippet
- id: '1707080029282'
alias: '[Gang boven] Wasmachine bezig'
description: ''
trigger:
- type: power
platform: device
device_id: 46f35dd1b6f1bb786ceb2f651daa9dfe
entity_id: 518e6a295fc6c16481ff8bbf4a4a04ba
domain: sensor
above: 100
condition: []
action:
- service: input_boolean.turn_on
target:
entity_id:
- input_boolean.wasmachine_bezig
data: {}
mode: single
Anything in the logs that might be useful for us?
No response
Additional information
No response
Do you see something special in the logs? What if you try to add a new integration, do you see anything strange?
It adds the automation to the yaml, but still not visible in the app/website.
I get the following error:
2024-02-08 11:04:40.518 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/config/automation.py", line 26, in hook await hass.services.async_call(DOMAIN, SERVICE_RELOAD) File "/usr/src/homeassistant/homeassistant/core.py", line 2224, in async_call raise ServiceNotFound(domain, service) from None homeassistant.exceptions.ServiceNotFound: Service automation.reload not found.
Have now confirmed that this is caused when ZHA couldn't load due to OTA providers not reachable. There is an unwanted link between viewing of configured automations and the readiness of ZHA.
See https://github.com/home-assistant/core/issues/109931