Cannot load history anywhere in HA - "loading state history..."

I’m on 0.8.2.
I just discovered that my HA cannot load any history…
I tried deleted the DB to have it recreated but same issue…
logbook works fine.

Any help would be appreciated…



You potentially didn’t wait long enough before clicking on something else. It is bloody slow to load for me. Just wait a minute or so.

I’m having the same issue on 0.80.2. I’m on a 16 core xeon server, so I don’t think it’s a matter of not waiting long enough…

I agree. It’s something else IMO.

I got the same problem, only started with 0.80.2

Yep same here.

Nothing odd in the log:

nick@nuccy:~$ grep -i history ~homeassistant/.homeassistant/home-assistant.log
2018-10-18 18:07:55 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
2018-10-18 18:07:55 INFO (MainThread) [homeassistant.setup] Setting up history
2018-10-18 18:07:55 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2018-10-18 18:07:56 INFO (MainThread) [homeassistant.loader] Loaded history_graph from homeassistant.components.history_graph
2018-10-18 18:07:56 INFO (MainThread) [homeassistant.setup] Setting up history_graph
2018-10-18 18:07:56 INFO (MainThread) [homeassistant.setup] Setup of domain history_graph took 0.1 seconds.

Same also for me. HA running on a 4 core CPU (not Rpi) with mysql backend. Since 80.2.

Dito - no graphs with 0.80.2, but Recorder works. Who opens a ticket?

Ah, it‘s already filed (issue 17563).

1 Like

Same issue for me running 0.80.2.

It’s very slow. I even got a ‘this web page is not responsive’ prompt… but then:


No errors in log. on an Intel Nuc.

I shall leave it on the history page while I eat dinner.

1 Like

Same version, same problem here

Same here on 0.80.2 on fast hardware (i5, lots of RAM, SSD storage…).

Same here ! , Using Pi3

Same problem. RPi3b+ 0.80.2

Same issue for me. Pi 3 + HA 0.80.2

Same here, HA 0.80.2 on a Synology DS916+ with MariaDB

Yup, came here looking for a thread like this-- same here since 0.80.2

This is fixed in 0.80.3 it now loads like it should.

1 Like