Thanks!
If the actual Automation from Settings > Automation & Scenes > (my automation) > Run works fine, does Automation Trace help?
The actual yaml is pretty straightforward and I confirmed my Lutron entity names haven’t changed
- alias: Bedroom Pico Off
trigger:
- platform: event
event_type: lutron_event
event_data:
id: bedroom_pico_off
action: single
action:
- service: light.turn_off
data:
entity_id: light.bedroom_lamp
This will just run the ‘action’ part of your Automation, so doesn’t test the actual Triggers or Conditions (for automations that have them).
Thanks @sparkydave – so yes, I think somehow with that automation yaml, I am not getting the Trigger.
I checked Developer Tools > States > event.bedroom_pico_off does exist (as before the upgrade), but I think the same automation yaml is no longer triggering…
Yes it does (or may).
I keep getting a notification about a Core update (2024.5.4). When I try and update, however, it doesn’t actually seem to update. I get the notification again shortly after.
EDIT: I should also mention I can’t find anything in the logs at all about an attempted update.
I have HA installed on a docker on an iHost. Prior to the update to the katest version, my HA would show correct status of all lights. Since the update, the states always revert to the previous state. Is there anything I can attach here to get you the information you need?
look in your supervisor logs, not HA logs.
FYI
Installed 2024.5.4 but having issues with mqtt mosquitto broker. I didn’t have time to look, so rollback ongoing. Seems connect / disconnect directly for all client.
You’ll have to clarify what you mean. The broker is not tied to the HA version.
Thanks! Below is the error I appear to be receiving.
2024-05-17 09:49:52.710 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/yellow-homeassistant:2024.5.4: 404 Client Error for http+docker://localhost/v1.44/images/ghcr.io/home-assistant/yellow-homeassistant:2024.5.4/json: Not Found ("No such image: ghcr.io/home-assistant/yellow-homeassistant:2024.5.4")
2024-05-17 09:49:52.711 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
are you out of disk space?
No. I have HA installed on a 64GB nvme ssd, and it’s reporting that I’ve used only 7.4% of the space.
is there any info above that error? It’s a 404 error meaning it can’t find the image
Here’s the log from the last time I tried. I included some of the lines before the actual error.
2024-05-17 12:00:56.564 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.5.4
2024-05-17 12:00:56.565 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/yellow-homeassistant:2024.5.3 to ghcr.io/home-assistant/yellow-homeassistant:2024.5.4
2024-05-17 12:00:56.565 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/yellow-homeassistant with tag 2024.5.4.
2024-05-17 12:01:06.918 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
2024-05-17 12:01:06.925 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
2024-05-17 12:01:06.933 INFO (MainThread) [supervisor.api.middleware.security] /backups/efb43943/info access from cebe7a76_hassio_google_drive_backup
2024-05-17 12:01:06.944 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
2024-05-17 12:01:06.951 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
2024-05-17 12:01:13.885 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/yellow-homeassistant:2024.5.4: 404 Client Error for http+docker://localhost/v1.44/images/ghcr.io/home-assistant/yellow-homeassistant:2024.5.4/json: Not Found ("No such image: ghcr.io/home-assistant/yellow-homeassistant:2024.5.4")
2024-05-17 12:01:13.886 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
What’s your mosquitto version? Did you upgrade it? There is a 2.x version you shouldn’t upgrade to. The specific version that’s problematic is mentioned somewhere on the forum.
I’m using the add-on of mosquitto, it’s version 6.4
It’s mosquitto 2.0.18
Btw, the rollback to 2024.5.3 solved the issue and having mosquito 2.0.18 (nothing change at that level of course) but I will need to upgrade
Correct , it’s in add-on module but I saw this
Same problem with EMQX broker. I think the cause is this PR #117267 that was merged in .4. Going back to .3 and everything’s ok with MQTT connection. Are you using WS connection to the broker or simple TCP?
I wrote to the dev of that PR here.
Read the post I referred you to.
I am running into some issues if I update from 2024.5.0 to anything higher. I always get a rollback to 2024.5.0.
Supervisor log shows:
2024-05-18 08:14:04.581 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.5.4
2024-05-18 08:14:04.582 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2024.5.0 to ghcr.io/home-assistant/qemux86-64-homeassistant:2024.5.4
2024-05-18 08:14:04.582 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2024.5.4.
2024-05-18 08:18:23.089 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping homeassistant application
2024-05-18 08:20:32.933 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning homeassistant application
2024-05-18 08:20:33.183 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2024-05-18 08:20:33.530 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2024.5.4
2024-05-18 08:20:33.531 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2024-05-18 08:23:33.914 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2024-05-18 08:23:33.914 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2024-05-18 08:23:33.915 INFO (MainThread) [supervisor.resolution.module] Create new issue update_rollback - core / None
2024-05-18 08:23:33.918 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
2024-05-18 08:23:33.918 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.5.0
2024-05-18 08:23:33.918 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2024.5.4 to ghcr.io/home-assistant/qemux86-64-homeassistant:2024.5.0
2024-05-18 08:23:33.919 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2024.5.0.
2024-05-18 08:23:34.594 INFO (SyncWorker_5) [supervisor.docker.manager] Stopping homeassistant application
2024-05-18 08:23:37.924 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning homeassistant application
2024-05-18 08:23:38.094 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2024-05-18 08:23:38.480 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2024.5.0
2024-05-18 08:23:38.480 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2024-05-18 08:26:38.870 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2024-05-18 08:28:54.005 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2024-05-18 08:28:54.270 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
Rollback log shows the following:
2024-05-18 08:20:43.058 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration frigate 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
2024-05-18 08:20:43.061 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration solaredge_modbus_multi 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
2024-05-18 08:20:43.063 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration govee 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
2024-05-18 08:20:43.064 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration browser_mod 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
2024-05-18 08:20:43.067 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration places 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
2024-05-18 08:20:43.068 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration powercalc 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
2024-05-18 08:20:43.070 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration broadlink 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
2024-05-18 08:20:43.072 WARNING (SyncWorker_6) [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
2024-05-18 08:20:43.073 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration webrtc 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
2024-05-18 08:20:43.075 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration frank_energie 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
2024-05-18 08:20:43.077 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration degree_days 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
2024-05-18 08:20:43.079 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration deepstack_object 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
2024-05-18 08:20:43.080 ERROR (SyncWorker_6) [homeassistant.loader] The custom integration 'deepstack_object' does not have a version key in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2024-05-18 08:20:43.081 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration ble_monitor 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
2024-05-18 08:20:43.082 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration delete 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
2024-05-18 08:20:43.083 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration audiconnect 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
2024-05-18 08:20:53.672 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2024-05-18 08:21:43.236 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('recorder', None): 1309.301520854}
2024-05-18 08:22:43.311 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('recorder', None): 1309.301520854}
2024-05-18 8:20:29 17 [Warning] Aborted connection 17 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got an error reading communication packets)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service mariadb-post: stopping
[08:38:09] INFO: Deleting service information from Home Assistant
s6-rc: info: service mariadb-post successfully stopped
s6-rc: info: service mariadb-core: stopping
2024-05-18 8:38:09 0 [Note] mysqld (initiated by: unknown): Normal shutdown
2024-05-18 8:38:29 0 [Warning] mysqld: Thread 25 (user : 'homeassistant') did not exit
2024-05-18 8:38:29 0 [Warning] mysqld: Thread 24 (user : 'homeassistant') did not exit
2024-05-18 8:38:29 0 [Warning] mysqld: Thread 22 (user : 'homeassistant') did not exit
2024-05-18 8:38:29 0 [Warning] mysqld: Thread 20 (user : 'homeassistant') did not exit
2024-05-18 8:38:29 0 [Warning] mysqld: Thread 19 (user : 'homeassistant') did not exit
2024-05-18 8:38:29 0 [Warning] mysqld: Thread 18 (user : 'homeassistant') did not exit
I checked all permissions on the MariaDB, but all is correct. Can anyone pinpoint me to solving this issue?