HA Core 2024.10.0 breaks system

[gretske47]

The problem

I upgraded to the HA 2024.10.0 core. After the upgrade, I get the following message when I go to the Systems tab - "Error while loading page system." HA then restarts every 5-10 minutes. I restored 2024.8.3 and the problems go away. I did not try 2024.9.x.

What version of Home Assistant Core has the issue?

System Information version | core-2024.8.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.46-haos arch | x86_64 timezone | America/New_York config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4970 Installed Version | 2.0.0 Stage | running Available Repositories | 1507 Downloaded Repositories | 69

AccuWeather

error | failed to load: unknown -- | --

Home Assistant Cloud

logged_in | true -- | -- subscription_expiration | February 25, 2025 at 7:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | false remote_server | us-east-1-0.ui.nabu.casa certificate_status | ready instance_id | 7a3e0f5ae463429aa722fb3f0f37021a can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.09.1 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 468.7 GB disk_used | 20.5 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), Simple Scheduler (2.5), Home Assistant Google Drive Backup (0.112.1), Samba share (12.3.2), ESPHome (2024.8.3), eWeLink Smart Home (1.4.3), Whisper (2.1.2), Piper (1.5.2), Mosquitto broker (6.4.1), ESPHome (beta) (2024.8.3), InfluxDB (5.0.0), Samba Backup (5.2.0), UniFi Network Application (3.2.0), Studio Code Server (5.15.0), openWakeWord (1.10.0), Node-RED (18.0.5), Grafana (10.0.0), Advanced SSH & Web Terminal (18.0.0), Assist Microphone (1.2.0), Zigbee2MQTT (1.40.0-1)

Universal Devices ISY/IoX

host_reachable | ok -- | -- device_connected | true last_heartbeat | October 3, 2024 at 9:23 PM websocket_status | connected

Dashboards

dashboards | 14 -- | -- resources | 44 views | 76 mode | storage

Recorder

oldest_recorder_run | August 31, 2024 at 10:09 AM -- | -- current_recorder_run | October 3, 2024 at 8:46 PM estimated_db_size | 384.06 MiB database_engine | sqlite database_version | 3.45.3

Sonoff

version | 3.7.3 (e240aaf) -- | -- cloud_online | 0 / 1 local_online | 0 / 0

What was the last working version of Home Assistant Core?

2024.8.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

I am not sure if an integration is causing the issue

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?

I wiped out the system to reload a clean HAOS. My bad!

Additional information

I have had HAOS on this Dell Wyse 5070 for about 1.5 years with no difficulties.

[gretske47]

This problem started after the system was powered on and off for 5 days, due to Hurricane Helene.

[Painkillernz]

I also have reboot issues after 2024.10.0 update. Seems to reboot every 30 min.

[dsduarte]

I'm glad to find this post... Today I changed my zigbee coordinaton, updated a lot of add-ons and updated to 2024.10... I loaded a backup from yestarday and I didn't want to try step by step to know what is breaking my system... When my setup has this issue, HA stays up for a few minutes befor restart again! I have HAOS running on a x86 PC as a VM on Proxmox.... The VM stays up all along... only HA Core resets!

[emanuelecochi]

I also have the same problem since I updated hassio to 2024.10.0 it restarts every 15 minutes

[pdivers]

my upgrade broke WeatherFlow, google_home, and rpi_gpio custom integrations. I'm attaching their log files.

WeatherFlow.txt google_home.txt rpi_gpio.txt

[NRutt2005]

Good evening all,

After experiencing the same issues describe here, I came across a solution that seems to have been the fix (for now at least).

Alexa Media Player version 4.13.3 seems to be the issue. Below a link to the GitHub for the Alexa Media Player issue post. The workaround to make HA stable again is to disable the Alexa Media Player if you're on 4.13.3 and this might help.

https://github.com/alandtse/alexa_media_player/issues/2579

[wolfmaster8]

Good evening all,

After experiencing the same issues describe here, I came across a solution that seems to have been the fix (for now at least).

Alexa Media Player version 4.13.3 seems to be the issue. Below a link to the GitHub for the Alexa Media Player issue post. The workaround to make HA stable again is to disable the Alexa Media Player if you're on 4.13.3 and this might help.

alandtse/alexa_media_player#2579

I can confirm this. After disabling Alexa Media Player, HA works just fine! No more reboots every 5 minutes.

[sierralx]

Alexia integration is the problem, downgrade to version 4.13.2 and HA works fine again.

[dhermanns]

I downgraded to Core 2024.9.0 and Alexa Media Player Integration continues to work fine. Since core 2024.10.0 seems to break the whole system - any fast fixes on this?

[viper539]

Same here. HAOS on Hardware. BTW: Memory usage is rising from 60% to 70% after the upgrade. Swapping is down from 100% to 15%.

Hint from Alexa-Media-Player-Github the best course of action might be to roll back to v4.13.2 by selecting '🔁 Redownload' and choosing version v4.13.2 in HACS.

This helped me.

[WladyTee]

I also have the same problem since I updated hassio to 2024.10.0 it restarts every 15 minutes

Ciao Emanuele, I've been experiencing several issues about self-restarting with 2024.08, 2024.09 and 2024.10 and I discovered a lot of watchdog intervention: HA was restarting, no proper shutdown was detected, DB was fixed and then a very slow execution was processed. I also lost the connection from my mobile phones, Companion App was affected with multiple "Disconnections" at launch (both via WiFi and 4G).

After 2 months of multiple tests, I found out that some parameters and flags in CONFIGURATION.YAML affected and crashed my HD installation (x86 NUC).

In a very special way:

• some Zigbee settings blocked my Conbee II usb dongle (detected but no operation).
• some settings on BLUETOOTH_LE tracker were slowing down the processing.
• some HTTP: settings as "login_attempts_threshold" and "ip_ban_enabled" caused to slow down processing and kill remote connection from Companion App.

Currently I experience multiple DNS issues in the log: [resolver] failed to query external DNS server" client-addr="udp:172.30.33.1:54282"

Since I spent long time in the self restarting issues, I just suggest you to check and "#" hash some settings in CONFIGURATION.YAML, then maybe you can temporarily disable some ADD-ON components.

I hope it helps you to make a proper investigation and qualification, my system with 2024.07 was perfectly stable and I got troubles with latest updates until yesterday when I disabled most of the personal customization and features. Cheers!

[gretske47]

OK, based on recommendations here, I disabled Alexa. But 2024.10.0 still did not allow access to the System page. It didn't seem to restart, but I did not run it very long since I couldn't access the system. There is something in 10.0 that is causing the problem. I guess I'll wait for 10.1.

[BrianMcBrayer]

Agreed. My whole system is borked after installing 2024.10.0. It was fine before but ZHA thinks it's working but cannot control my devices, and a whole host of other issues have cropped up. I can't even restore from a backup.

[Humolus]

Nuc brigged after update, cant even turn it on, so there goes 400$ hardware. FFS remove this update ASAP, hacked?

[Painkillernz]

I had to remove SSD and flash fresh HA image then update from downloaded back up post 2024.10.0. Back up restore did not work inside as kept rebooting.

On Sat, 5 Oct 2024, 3:28 am Brian McBrayer, @.***> wrote:

Agreed. My whole system is borked after installing 2024.10.0. It was fine before but ZHA thinks it's working but cannot control my devices, and a whole host of other issues have cropped up. I can't even restore from a backup.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127513#issuecomment-2393846145, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALFEG5JFDHZG4V6J4QRZXFTZZ2QZLAVCNFSM6AAAAABPK43WYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTHA2DMMJUGU . You are receiving this because you commented.Message ID: @.***>

[joostlek]

Since Alexia Media Player v4.13.3 has been pulled, I am going to close this issue as there are no new users running into this problem. Since these issues become a mix of all kinds of issues: if you experience other issues with 2024.10.0 that are not related to Alexa Media Player, please open a new issue with all info you can gather like debug logs and stuff. Thanks!

[gretske47]

Joost -

The original issue was not addressed and is apparently unrelated to the Alex Media Player issue. I am still having a problem with 2024.10.0. Even without AMP, I cannot access the System page. In order to re-submit the issue, I would have to load 10.0 and gather all the info again. I don’t think this should have been closed because the original issue was not addressed.

COL (Ret) Gene Retske @.*** Tel: 803 732 3866

On Oct 5, 2024, at 06:04, Joost Lekkerkerker @.***> wrote:

Since Alexia Media Player v4.13.3 has been pulled, I am going to close this issue as there are no new users running into this problem. Since these issues become a mix of all kinds of issues: if you experience other issues with 2024.10.0 that are not related to Alexa Media Player, please open a new issue with all info you can gather like debug logs and stuff. Thanks!

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127513#issuecomment-2395004449, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZRIWVHSKZNZHPIX2FLZZ62UHAVCNFSM6AAAAABPK43WYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAYDINBUHE. You are receiving this because you authored the thread.

[joostlek]

In the original issue I don't find a lot of information that could help us with debugging. But since the issue is now a collection of noise for Alexa Media Player, I would suggest creating a more specific issue than "2024.10 breaks", this way we can have a better scoped discussion and help you better.

[gretske47]

Joost -

Let me think about this. To do this, I will have to load 10.0, collect all the relevant info and re-submit. That is a good bit of work. I may just live with 6 until 10.1 or later comes out.

-gene

On Oct 5, 2024, at 07:03, Joost Lekkerkerker @.***> wrote:

In the original issue I don't find a lot of information that could help us with debugging. But since the issue is now a collection of noise for Alexa Media Player, I would suggest creating a more specific issue than "2024.10 breaks", this way we can have a better scoped discussion and help you better.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127513#issuecomment-2395019938, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZWUDTJ7I26GYIONKUDZZ7BQTAVCNFSM6AAAAABPK43WYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAYTSOJTHA. You are receiving this because you authored the thread.

[joostlek]

10.1 is already out, but I haven't seen your issue come up during the beta or with others (or I missed it due to the Alexa Media Player noise). So at this point it can be anything and there is no real way to find out what causes this. (Note: since we don't know the issue, chances are high that 10.1 doesn't solve your issue)

[gretske47]

You are right, 10.1 did not fix it. Since I cannot access the System page, I am lost. Whenever I try to access it, I get an error, saying, "Error while loading page system.” I don’t know how to fix this. Any ideas?

I am using an August version which works fine.

Can you direct me to any information on how to proceed?

-gene

On Oct 5, 2024, at 07:13, Joost Lekkerkerker @.***> wrote:

10.1 is already out, but I haven't seen your issue come up during the beta or with others (or I missed it due to the Alexa Media Player noise). So at this point it can be anything and there is no real way to find out what causes this. (Note: since we don't know the issue, chances are high that 10.1 doesn't solve your issue)

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127513#issuecomment-2395022141, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZRAOTI3WODDMAQ6HCDZZ7CU3AVCNFSM6AAAAABPK43WYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZDEMJUGE. You are receiving this because you authored the thread.

[joostlek]

Can you please open a new issue with what you see? Also try to include logs from the file system if possible. Because the system sounds like its working, but something goes wrong

[gretske47]

I’ll try, but without access to System page, I have to use the CLI which is not easy for a non-engineer like me.

On Oct 5, 2024, at 07:33, Joost Lekkerkerker @.***> wrote:

Can you please open a new issue with what you see? Also try to include logs from the file system if possible. Because the system sounds like its working, but something goes wrong

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127513#issuecomment-2395026779, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZR4CXNDQ53YXFYMRYTZZ7FATAVCNFSM6AAAAABPK43WYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZDMNZXHE. You are receiving this because you authored the thread.

[joostlek]

Yes, so open an issue and we can help you there :)

[gretske47]

Submitted.

On Oct 5, 2024, at 07:45, Joost Lekkerkerker @.***> wrote:

Yes, so open an issue and we can help you there :)

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127513#issuecomment-2395029373, or unsubscribe https://github.com/notifications/unsubscribe-auth/A47ZEZWF56XRQPJROO547VLZZ7GM5AVCNFSM6AAAAABPK43WYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGAZDSMZXGM. You are receiving this because you authored the thread.