Multiple topics about logbook not working, halting the whole system or taking forever to load.
My personal experience is halting the whole system (NUC with HAOS and NAS with MariaDB).
Before HA I came from Hubitat, which has a realtime and history based logbook that works really well and is very fast. I like to propose a similar logbook for HA. I’m willing to send my old Hubitat hub to whoever wants to pick up on development as an example, since I don’t use the thing anymore. I would love to add my two cents to development but I don’t thinks that would be wise. I do want to help in any other way though.
No issues here (using MySQL) with 2 year history…
Filtering 1 year on a single object shows within half a second
(ha runs on a vmware, mysql on debian11)
In that case i’d expect some sort of message in the “repairs” section. But I still don’t get what that is for. It has been empty since it was introduced.
That sounds more like a bug that should be fixed, many users myself included do not suffer from this behavior you described.
by default not everything is included in the logbook, did you make sure to read the docs to configure it properly for your use case?
repair messages need to be built by the integration and are shown based on known errors like misconfiguration. Have you filed an issue on github for the first sentence in this feature request? Have you checked open issues on github to see if its being looked at?
