-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems after upgrade #127395
Comments
Same here, had to power off and quickly setup safe mode and then restore 2024.9.3 |
Same here. |
Same here. Constant reboots. |
Same for me - one difference. It does not directly reboot - it simply crashes and never comes back. I have to do I can not see any "out of memory" messages for my system (generic x86 machine). There are also no log messages displayed to suggest anything. |
that's bad ... I also tried that - currently rebooting my system :O |
Same here. It crashes constantly and then need several minutes before it comes up again. Running HAOS on Proxmox VM. |
Same here, constant reboot about every 15min with 2024.10.0 |
seen this during start of homeassistant - don't know if it's relevant in this case:
|
ok same here as well |
jep - unfortunately also downgrade to 2024.9.3 did not help - still crashing |
Do u use Alexa Media Player ? |
Yes - I do! And I also installed that update just prior to the core upgrade... will revert that now and see what happens. |
had the same idea, I disabled Alexa for now to see is its works |
yes I do - really? How did you downgrade - via HACS? |
Me, too. |
same for me! AMP disabled - working again. I'll update to 2024.10 again now to check if my thermostats working again ;) |
just for reference --> this is the issue created for AlexaMediaPlayer |
Ok - AMP downgraded and I am back to 2024.10 core and everything holding steady... |
On another issue a user said there seems to be an issue with python3 -m homeassistant ..." process was on 100% CPU and at the same time HA was not responsive. |
I was in the same boat as all of you. The Alexa Media Player update and the Core update came out around the same time. I too at first assumed the issue was with the core update, but turns out it was with Alexa update. I am not as skilled as many of you guys. Some were able to "roll back" via Hacs, but I couldn't do much before my system went offline. I was able to "roll back" by restoring a backup I made on Sept 30th. If you are not that good with systems like myself your best solution is to do backups often. I had to "restore" 3 times before I was able to pinpoint the issue was with the AMP update not the Core. It takes me about 8 minutes to restore from a backup, which is much less than me trying to figure out how to roll back the AMP upgrade I just did, especially when HA keeps losing connection. |
Any changes with your BT entities? Mine are not avaliable anymore... So at worst case I have to reconfigure all my thermostats, would avoid that, if possible EDIT: |
Same here :-( System is constantly rebooting. Worked fine for about 15 hours after update to 2024.10. Frontend does not load, SMB-share is reachable. |
seen the above? About AlexaMediaPlayer? Maybe same for you ... |
Yea, that did the trick. I connected to the config share, deleted the folder alexa_media in custom_components, and after reboot ha worked as ever. Thanks for the hint :-) |
I disabled the alexa media player and that seems to do the trick. Before restart every 6 minutes, now its running for 10 min. If that solves it, I'll downgrade to a previous version and check again with running alexa. @Users who asked for downgrade: Go to HACS, select alexa media player, 3 dots and "download again" (dont know the translation exactly) and select previous version should do the trick. |
Had to downgrade the Alexa too. Thank goodness I found this thread! Well-done everyone! :) |
I think I have said this a million times now.... thank the smart home system gods this community exists. Been pulling my hair out trying to disable everything before a crash. changed the google search for the last 24 hours and bam! |
Alexa has also struck me. It constantly reboots... |
Just downgrading AMP to 13.2. brought everything back to normal. All Automations are working again, also the voice-enabled. |
Disabling AMP did the trick for me. Spent few hours trying to get to log and capture the issue. Wasn’t allowing me enough time to investigate also. Kept losing connection. I was blaming SLZB06-M latest firmware update until now 😄 |
@click2saurabh Just something to help out (hopefully). I, too, had the same problem. Eventually, once I found the problem, I logged into the terminal and renamed the alexa_media directory to allow things to start properly. Then just before I did the downgrade, I renamed the directory back. Look, it's not the most elegant of ways but it bloody works! :) |
The problem is the Alexa Media Player update , if i disable the reboots are stopped, thanks to all |
Thanks to all, disabling the AMP did the trick. |
The problem
The HA reboot every 15 min and it lost the Connect devices by the app, and i must reisntall the app on tablet/smartphone at every reset of the HA
What version of Home Assistant Core has the issue?
core-2024.10.0
What was the last working version of Home Assistant Core?
core-2024.09
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: