on a bare as possible ‘test’ HA instance, my Logbook won’t load at all while the History pane is very swift.
of course, logbook: is enabled, and I can see the Logbook in the left side menu, which upon clicking leads to:
This is on beta 2021.4.0b2 now, but was there in several releases back also. 2 other instances do load the logbook fine, and I dont know what to look for comparing the instances.
Please help me out here, what should I check. thanks!
Maybe its an issue caused by corrupted database files. If you are ok with deleting these datafiles, you can delete the files home-assistant_v2.db and home-assistant.log in the config folder and reboot the server. But please understand that deleting this file will lead to losing of the history of the devices.
Thanks, but I’ve done that multiple times already .
Tried on 2021.4.0b2, logbook loads fine, so it is not related to the beta version.
Yes, that’s what I said in my opening post. Must be a instance specific issue, but how to find it…
So I’ve added:
logbook:
include:
domains:
- switch
- person
to narrow down the logbook to 15 (14 switches, 1 person) entities… nothing showing but the swirling icon. migrated to MariaDB, still nothing. And rebooted the Host (opposed to a more restart between config changes)
I now notice this:
ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1824518880] Received invalid command: trace/contexts
shows each time I try to show the Logbook.guess Ill file an issue now…
problem solved.
Error was appearing since the beta, (though the issue was from before that) and Bram has a fix for that in the making, component not loaded.
In my case, I had no automations or scripts, so these components we not loaded. Adding 1 single automation immediately fixed this. According to Ludeeus only loading the components already suffices
thanks for any feedback