Okay, odd question – after you create a new automation via the UI (locking the front door at 8pm) the automation is on the filesystem in the automation.yaml file but nowhere to be found on the UI. Am I missing something or just looking in the wrong place ( Settings > Automation & Scenes ).
It should be on the list in Settings - Automations and Scenes - Automations.
Have you checked the whole list in case it got an unexpected name?
If it’s not in the automations list (as @templeton_nash described), maybe you managed to create an invalid automation. Did you create the automation by hand or with a blueprint? I had this problem when I started working with my own blueprints. May check the log regarding this.
There is only 3 automations there… that were imported in. Nothing else around.
The automation was created from an empty automation.
I re-did the automation, saved as “lockDoor” and it still does not show up (I did a full restart to be sure):
Produced yaml (I did not modify the yaml):
- id: '1665921345592'
alias: LockDoor
description: ''
trigger:
- platform: time
at: '20:00:00'
condition:
- condition: state
entity_id: lock.front_door
state: unlocked
action:
- service: lock.lock
data: {}
target:
entity_id: lock.front_door
mode: single
Home Assistant Operating System Version: 9.2
Home Assistant 2022.10.4
Started with just a blank automation, pretty simple trigger, condition and action. See post above.
When you press the e-key to open up the entity filter and type in LockDoor
, is there also no entry for your automation?
Did you look at your logs? Best is to clear the list in the frontend and then restart your instance from another tab and see if any warnings/errors show up
Does not show up in the entity list.
Nothing in the logs about automation, config error, or door …
I did a restart …
2022-10-16 10:01:00.052 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hass_agent_mediaplayer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.054 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration yahoofinance which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.055 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hass_agent_notifier which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.057 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.058 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.060 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration blitzortung which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.061 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration toyota_na which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:00.063 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration weatheralerts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-10-16 10:01:22.359 WARNING (MainThread) [homeassistant.components.mqtt] The 'broker' option near /config/configuration.yaml:46 is deprecated, please remove it from your configuration
2022-10-16 10:01:22.369 WARNING (MainThread) [homeassistant.components.mqtt] The 'discovery' option near /config/configuration.yaml:46 is deprecated, please remove it from your configuration
2022-10-16 10:01:22.371 WARNING (MainThread) [homeassistant.components.mqtt] The 'password' option near /config/configuration.yaml:46 is deprecated, please remove it from your configuration
2022-10-16 10:01:22.373 WARNING (MainThread) [homeassistant.components.mqtt] The 'port' option near /config/configuration.yaml:46 is deprecated, please remove it from your configuration
2022-10-16 10:01:22.374 WARNING (MainThread) [homeassistant.components.mqtt] The 'username' option near /config/configuration.yaml:46 is deprecated, please remove it from your configuration
2022-10-16 10:01:22.450 ERROR (MainThread) [homeassistant.core] Connection to SABnzbd API failed: SABnzbd API request timed out
2022-10-16 10:01:22.454 WARNING (MainThread) [homeassistant.config_entries] Config entry '0d31a8171ce3' for sabnzbd integration not ready yet: None; Retrying in background
2022-10-16 10:01:22.560 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform scrape is taking over 10 seconds.
2022-10-16 10:01:22.564 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform weatheralerts is taking over 10 seconds.
2022-10-16 10:01:30.420 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_wan_status already exists - ignoring binary_sensor.freebsd_router_wan_status
2022-10-16 10:01:30.430 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_bytes_received already exists - ignoring sensor.freebsd_router_b_received
2022-10-16 10:01:30.432 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_bytes_sent already exists - ignoring sensor.freebsd_router_b_sent
2022-10-16 10:01:30.434 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_packets_received already exists - ignoring sensor.freebsd_router_packets_received
2022-10-16 10:01:30.435 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_packets_sent already exists - ignoring sensor.freebsd_router_packets_sent
2022-10-16 10:01:30.436 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_ip already exists - ignoring sensor.freebsd_router_external_ip
2022-10-16 10:01:30.439 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_wan_status already exists - ignoring sensor.freebsd_router_wan_status
2022-10-16 10:01:30.441 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_KiB/sec_received already exists - ignoring sensor.freebsd_router_kib_s_received
2022-10-16 10:01:30.443 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_KiB/sec_sent already exists - ignoring sensor.freebsd_router_kib_s_sent
2022-10-16 10:01:30.445 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_packets/sec_received already exists - ignoring sensor.freebsd_router_packets_s_received
2022-10-16 10:01:30.447 ERROR (MainThread) [homeassistant.components.sensor] Platform upnp does not generate unique IDs. ID uuid:6185ad41-954e-6796-9a51-d612f4bf675_packets/sec_sent already exists - ignoring sensor.freebsd_router_packets_s_sent
It should show up in the list…
Try and check if the automation is in automation.yaml several times? If yes, delete them all, and create a new. Or, just delete all lines in automations.yaml. You only have very few automations, might be quick to create agin. You mention they 3 automations were imported? Maybe creating some error
I deleted the automations.yaml file content, deleted the include for the HACS repo that was importing the weather alerts … however they are still showing in the UI and obviously it won’t let you delete them.
They only show up in the store, so how do I delete them?
$ find . -type f -exec grep -il "weather alert" {} /dev/null \;
./.storage/hacs.repositories
./.storage/core.entity_registry
./.storage/core.restore_state
./custom_components/hacs/utils/default.repositories
Does not make much sense. You should not have any automations in the gui. I do not have any good suggestions. If you have just started, maybe a clean start is best. Something must be wrong
After all of that multiple tries of trying to delete the entities from the database (external mysql) the upgrade to 2022.10.5. After the update, the 3 entries are no longer there.
The manually created automation does show up now.