Eckart
(Severing)
February 11, 2022, 12:51pm
1
Hello,
I have moved my HA installation with backup/restore from an RPi4 to an OdroidN2+ and updated to the current HA version 2022.2.5.
Now everything works - only the tab “History” remains empty: it shows a loading symbol forever.
After researching in the forum, I have already deleted the file home-assistant_v2.db twice. No success: It is created again, but History remains empty. Another attempt: In configuration.yaml “recorder:…” switched to an external MariaDB10. It is filled, with phpMyAdmin I see the data, but the History tab remains empty. Another strange thing is that I can see the history of the individual entities.
What can I do there?
Thankful for any help: Eckart
tom_l
February 11, 2022, 12:55pm
2
A few others seem to be experiencing the same issue. It may be unrelated to your recent move:
opened 10:33PM - 17 Jan 22 UTC
integration: history
### The problem
If I click on the `history` entry (`http://homeassistant:8123… /history`) the screen loads forever:
![image](https://user-images.githubusercontent.com/66269310/149839168-d42a29b4-2082-4331-840f-e0a324360d2f.png)
If I open a page for an entity, e.g. `http://homeassistant:8123/history?entity_id=sensor.nilan_eg_hauswirtschaftsraum_energy_power` everything is OK.
If I delete the entity, it spins again forever...
I deleted the mariaDB integration and installed it again so that the states table is empty again. After a couple of hours there are 60.764 entries in it. Still no success loading the history integration...
### What version of Home Assistant Core has the issue?
2021.12.9
### What was the last working version of Home Assistant Core?
? (did work before, but not sure when)
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
history
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/history/
### Example YAML snippet
```yaml
history:
recorder:
db_url: !secret recorder_url
purge_keep_days: 21
auto_purge: true
exclude:
domains:
- updater
- device_tracker
- zwave
- zigbee
- script
- group
- scan_store
- zone
entity_globs:
- sensor.weather_*
- binary_sensor.*_status
- sensor.*_last_restart
- sensor.*_last_boot
- sensor.*_uptime
- binary_sensor.lampe*
- binary_sensor.nas*
- binary_sensor.pc*
- binary_sensor.*_firmware_update
- sensor.alexa*
- sensor.*battery
- switch.alexa_*
- sensor.rollo*
- binary_sensor.motion*
- sensor.motion*temperature
- sensor.motion_*illuminance*
- sensor.galaxy_tab_a7*
- sensor.nuki_hausture_rss*
- sensor.openwb_cp1_spannung_phase*
entities:
- sun.sun
- sensor.last_boot
- sensor.date
event_types:
- call_service
include:
entities:
- binary_sensor.motion_carport
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
Is there a way to debug this?
Or - as a workaround - is it possible to start the history tab without auto-loading all entities?
Usually I what to see 1-3 at the same time, but that would be a feature request because right now you can see all or just one...
Eckart
(Severing)
February 11, 2022, 2:27pm
3
You are right. I join that threat. Eckart
1 Like