![]() # Capture and log data to the HA database Keep a small rolling set of data (e.g.Purge on a regular bases (the default is daily at 04:12am).You can explicitly include or explicitly exclude what is recorded, or use a combination of both. I have no experience with this, only mention it here for the sake of completeness. There are guys who extract data from the in-memory HA database to an online BigQuery database. Or you can put it in memory (which is volatile and you will loose the contents of the database when you reboot), and then on regular intervals extract only the reduced data set that you really want to a persistent database. move it to a USB drive if you’re still on SD. It is possible to change the default location of the HA database. This may very well reduce the need to tinker with the database setup. In release 2022.4 database optimizations were implemented to improve performance and to reduce the amount of data written to and stored in the database. Reducing the hassio_audio container logging can be done by using a bit of a dirty workaround to change the Pulse Audio log level inside the container from “debug” to e.g. It seems log filtering for some HA components like hassio_audio is not yet implemented. “warning”: # Change hassio_supervisor log level Some HA components do not support the HA Logger settings and must be configured by passing parameters from the command line using the HA CLI.ĭo the following from the command prompt or SSH to change the log level for hassio_supervisor to e.g. Set the default level that will apply to all components (supporting this feature), and override it where needed for specific cases where you want to see more detailed information: logger: In configuration.yaml, appart from other filtering settings, it is possible to set the logging level of HA components and integrations. Home Assistant 1) Logsįirst step and perhaps the easiest is to make sure HA outputs the minimum of logging to the downstream systems. Now with all that out of the way, it’s time to roll up the sleeves and get our hands dirty (and systems clean)… A. New functionality may render your change useless, and you may want to undo it to reduce load on the system (e.g.In future you may want to undo some changes, to expand logging again to help troubleshooting that new problem.If something does not work (anymore), then you know what you changed, and when.Īll those sudden errors may or may not even be caused by your change, but you can only make the link if you have this information available.Write up everything you change, and also the time it was (effectively) implemented. don’t disable Samba logs if anybody else can access your RPi and you want to monitor (failed) connections. Apply changes incrementally, and test in between. ![]() Make a backup of every (system) file before you make changes.When implementing changes to the system, whatever we do we want to maintain stability and be able to revert back to a working state should things go south. ![]() (You may want to upvote these changes, to show their importance to the user community) Unfortunately there is no joy, so I submitted a feature request for hassio_supervisor to filter out its own debug statements. There are tickets to correct this behavior for hassio_supervisor and hassio_audio. So it is not possible to run a daily report to “show me all errors that occurred on my system today”, because most if not all of those errors are no errors at all.
0 Comments
Leave a Reply. |