Skip to content
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

Closed
wjb82 opened this issue Oct 3, 2024 · 34 comments
Closed

Problems after upgrade #127395

wjb82 opened this issue Oct 3, 2024 · 34 comments

Comments

@wjb82
Copy link

wjb82 commented Oct 3, 2024

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

version core-2024.10.0
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 Europe/Rome
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.1
Stage running
Available Repositories 1427
Downloaded Repositories 29
Home Assistant Cloud
logged_in false
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 30.8 GB
disk_used 9.2 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization oracle
board ova
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.15.0), File editor (5.8.0), eWeLink Smart Home (1.4.3), Home Assistant Google Drive Backup (0.112.1), Samba share (12.3.2)
Dashboards
dashboards 3
resources 15
views 15
mode storage
Recorder
oldest_recorder_run 24 settembre 2024 alle ore 10:50
current_recorder_run 3 ottobre 2024 alle ore 09:24
estimated_db_size 462.15 MiB
database_engine sqlite
database_version 3.45.3

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@NotFU1
Copy link

NotFU1 commented Oct 3, 2024

Same here, had to power off and quickly setup safe mode and then restore 2024.9.3

@mazzy89
Copy link
Contributor

mazzy89 commented Oct 3, 2024

Same here.

@CannyGent
Copy link

CannyGent commented Oct 3, 2024

Same here - my HA OS 13.1 console shows an Out of memory error and kills a python3 process
Screenshot 2024-10-03 085552

UPDATE: have successfully reverted to 2024.9.3 by issuing this command:
ha core update --version 2024.9.3

UPDATE: spoke too soon... 2024.9.3 now giving me the same out of memory error. This is on a proxmox VM with 8GB RAM.

@margatemarcel
Copy link

Same here. Constant reboots.

@florianmulatz
Copy link

Same for me - one difference. It does not directly reboot - it simply crashes and never comes back. I have to do ha core restart then it's back for about 5min or so and crashes again

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.

@florianmulatz
Copy link

UPDATE: spoke too soon... 2024.9.3 now giving me the same out of memory error. This is on a proxmox VM with 8GB RAM.

that's bad ... I also tried that - currently rebooting my system :O

@thitcher
Copy link

thitcher commented Oct 3, 2024

Same here. It crashes constantly and then need several minutes before it comes up again. Running HAOS on Proxmox VM.

@timredd99
Copy link

Same here, constant reboot about every 15min with 2024.10.0

@florianmulatz
Copy link

seen this during start of homeassistant - don't know if it's relevant in this case:

2024-10-03 10:11:13.915 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 453, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 168, in async_update_listeners
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 533, in _handle_coordinator_update
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state
    self.__async_calculate_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 293, in state
    if (is_on := self.is_on) is None:
                 ^^^^^^^^^^
  File "/config/custom_components/moonraker/binary_sensor.py", line 133, in is_on
    return self.is_on_fn(self)
           ^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/moonraker/binary_sensor.py", line 98, in update_available_fn
    sensor.coordinator.data["machine_update"]["version_info"][component][
KeyError: 'remote_version'

@cloudbr34k84
Copy link

cloudbr34k84 commented Oct 3, 2024

ok same here as well
Running HAOS on NUC, was all fine before 2024.10. I was on the beta channel on discord and brought this up as well as i sytarted gettinh issues as soon as i updated to one of the betas. I was told to run profiler, but i cant as the system disconnects as soon as i use the menu. My nuc increases in temp and noise, and even does this on Safe Mode. i raised a issue as well
#127379

@florianmulatz
Copy link

jep - unfortunately also downgrade to 2024.9.3 did not help - still crashing

@Der-WU
Copy link

Der-WU commented Oct 3, 2024

Do u use Alexa Media Player ?
I think it is related to the Alexa Media Player.
After I Update ha, I got an Update for Alexa Media Player. I Update amp and the restarts begin. After Downgrade amp the latest ha Runs Fine for me.

@CannyGent
Copy link

Do u use Alexa Media Player ? I think it is related to the Alexa Media Player. After I Update ha, I got an Update for Alexa Media Player. I Update amp and the restarts begin. After Downgrade amp the latest ha Runs Fine for me.

Yes - I do! And I also installed that update just prior to the core upgrade... will revert that now and see what happens.

@thomasmiddendorp
Copy link

Do u use Alexa Media Player ? I think it is related to the Alexa Media Player. After I Update ha, I got an Update for Alexa Media Player. I Update amp and the restarts begin. After Downgrade amp the latest ha Runs Fine for me.

had the same idea, I disabled Alexa for now to see is its works

@florianmulatz
Copy link

yes I do - really? How did you downgrade - via HACS?

@thitcher
Copy link

thitcher commented Oct 3, 2024

Me, too.
Use Amp and reverted back.
Noticed that after I reverted back to last working core, all my better thermostat entities are not avaliable anymore.... 🤔

@florianmulatz
Copy link

Use Amp and reverted back.
Noticed that after I reverted back to last working core, all my better thermostat entities are not avaliable anymore.... 🤔

same for me! AMP disabled - working again. I'll update to 2024.10 again now to check if my thermostats working again ;)

@florianmulatz
Copy link

florianmulatz commented Oct 3, 2024

just for reference -->
alandtse/alexa_media_player#2579

this is the issue created for AlexaMediaPlayer

@CannyGent
Copy link

Ok - AMP downgraded and I am back to 2024.10 core and everything holding steady...

@cloudbr34k84
Copy link

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.

@CancunManny
Copy link

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.

@thitcher
Copy link

thitcher commented Oct 3, 2024

Use Amp and reverted back.
Noticed that after I reverted back to last working core, all my better thermostat entities are not avaliable anymore.... 🤔

same for me! AMP disabled - working again. I'll update to 2024.10 again now to check if my thermostats working again ;)

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:
after several restarts and some patience, all BT entities are back now 🐝

@halli77
Copy link

halli77 commented Oct 3, 2024

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.

@florianmulatz
Copy link

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 ...

@halli77
Copy link

halli77 commented Oct 3, 2024

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 :-)

@Meigl89
Copy link

Meigl89 commented Oct 3, 2024

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.

@lloydbayley
Copy link

Had to downgrade the Alexa too. Thank goodness I found this thread! Well-done everyone! :)

@hanley-development
Copy link

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!

@dnwalker68
Copy link

Alexa has also struck me. It constantly reboots...

@tebiwi
Copy link

tebiwi commented Oct 4, 2024

Just downgrading AMP to 13.2. brought everything back to normal. All Automations are working again, also the voice-enabled.

@click2saurabh
Copy link

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 😄

@lloydbayley
Copy link

@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! :)

@wjb82 wjb82 closed this as completed Oct 4, 2024
@wjb82
Copy link
Author

wjb82 commented Oct 4, 2024

The problem is the Alexa Media Player update , if i disable the reboots are stopped, thanks to all

@lbarreiro
Copy link

lbarreiro commented Oct 4, 2024

Thanks to all, disabling the AMP did the trick.
Still didn't downgraded the AMP
I'm in a Raspberry Pi and did notice that the processor was working at 6% and now is at 2%, any one with the same?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests