Updating Home Assistant Core - Stuck on Loading Data

Installation Home Assistant OS
1

image
image603×626 10.7 KB

Hey guys,

The past two times I have tried to upgrade home assistant core for the update for September and now I just tried October and both times Home assistant upgrades successfully. However, when I go to browse and login, it is just stuck at the loading data screen. I am able to even see everything popping up in the bottom left saying it has started successfully and my alerts and everything are working as expected but I cannot browse Home assistant.

I have tried dumping my browser cache, I have tried browsing via internal IP address and homeassistant.local but it is the same issue. I have tried via mobile and via pc. The only resolution I have is to revert to backup, but I don’t want to not be able to upgrade in the foreseeable future. Is anybody else running into this? I am running HASSOS in vmware on a windows pc. I have also tried rebooting the VM itself, as well as completely rebooting (and complete shutdown then power up) the windows pc as well but nothing fixes it.

1 Like
2

Hi,

I ran into the same problem after updating to 2024.10.3.
My HA is running on a RasPi 5
I also tried rebooting and all the other recommended steps. Nothing worked.
Home Assistant itself seems to run fine. My automations and connections to Apple Homekit are working. Only the front end ist stuck.

3

Sucks that you are going through the same thing as me, but also happy I am not the only one haha! Everything I was searching for online was from typically years ago and it was typically just a browser cache issue which this is not (have tried multiple browsers, incognito, multiple devices, etc). Even home assistant themselves recommend just dumping your cache when this happens to resolve which I have done multiple times.

By any chance do you have HACS installed or any other custom add ons? I was thinking of disabling those before upgrading the next time I try. I just don’t know when I will have a chance to do it again, because with mine being vmware I have to recreate the VM each time and then restore from HA backup which isn’t too bad but takes a little longer.

I was really hoping that it was a fluke with the September update like I said, but then ran into the same exact thing with the October one.

4

Do you guys see any information in home-assistant.log. Wondering if you might have the same problem as I have and if you have found a resolution yet.

5

Same problem also…

6

Thanks for your response @DBM that unfortunately isn’t my issue as I don’t have SolarEdge. I do think it has to do with a HAC integration though. I did give it another shot tonight and I tried disabling HACS along with all of the integrations as well that I have but that still didn’t work unfortunately so I have to work through another restore.

I think I may remove my HACS installs to see if it then works, but the problem is I won’t necessarily know which one causes the issue but it would still be a good test.
For the rest of you do you happen to use Music Assistant, Firemote Card, Team Tracker, or Team Tracker Card?

If we have a common HACS integration, maybe that will point to the issue.

7

did you try to do a safe mode restart to if that changes the behavior?

I do not have those integrations btw

8

Hello,

I’m not sure this can help but I ran into the same problem after updating to 2024.10.3.
My HA is running on debian (Supervised).

I get this in my home-assistant.log :

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/connection.py”, line 227, in async_handle
handler(self.hass, self, msg)
File “/usr/src/homeassistant/homeassistant/components/recorder/basic_websocket_api.py”, line 31, in ws_info
if instance := get_instance(hass):
^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/recorder.py”, line 76, in get_instance
return hass.data[DATA_INSTANCE]
~~~~~~~~~^^^^^^^^^^^^^^^
KeyError: ‘recorder_instance’

I just rollback my last recorder configuration :

recorder:
  db_url: !secret mysql_connect
  db_max_retries: 20
  purge_keep_days: 30
  exclude:
    entities:
      - sensor.time
      - sensor.date_time
#      - device_tracker # This exclusion was rolled back
9

I am still getting this error on Home Assistant Yellow running 2024.11.1 - does anyone know of a fix?

10

I unfortunately haven’t had a chance to test again and it will probably be another week or two. Do you have any HACS integrations that I had listed previously by any chance? For my next attempt I am going to try and look at more of the CLI logs which I haven’t yet done. Also it was mentioned to try to start home assistant in safe mode which I am assuming you can try to do via the CLI as well so I may give that a try.

I will definitely post any updates on my next attempt.

11

I have tried in safe mode and I can access using my external domain still - but not on the local ip.

Looking back through your post @salok08228, I also use the Team tracker add-on and cards but that doesn’t seem to have any effect when in safe mode and also trying to access via the local ip.

12

Same issue here. Seems to happen when an update is available.
Secondly is Tuya in need of reautentication when loading hangs.

13

Hey guys,

Finally got around to trying to figure this out over the past couple of days and made a copy of my VM so I could more thoroughly test. @madjx you were correct!! When you posted last, I didn’t think I had done anything with recorder (and I haven’t in years) and so I embarrassingly glazed over your response because I didn’t think it was applicable to me. Truth be told I very rarely make direct changes to my configuration.yaml file anymore (used to do that in my early days with HA).

Anyways I ended up checking my configuration.yaml file to be sure and sure enough recorder was in there :expressionless: . After I commented out the recorder lines in my configuration.yaml and then rebooted the VM it came right up. Hopefully that helps others and if it isn’t recorder specifically maybe there is some other legacy stuff in your configuration.yaml file causing issues.

cheers @madjx thanks again and thanks to everyone helping point me in the right direction!!