![]() ![]() (You’re doing automatic backups, right? If not, that should be your next priority, just after checking the database size.) See also Smaller backups are faster to create, download and restore and they won’t fill up your backup storage location. more wear) on flash-based storage (such as SD cards), meaning they will degrade faster and they will fail sooner than you might expect.Īdditionally, the database is included by default in Home Assistant backups ( formerly called snapshots). Excessive I/O also causes more stress (i.e. This will mostly cause excessive I/O, making some parts of the system stall while waiting for reads and writes. The larger the database, the slower Home Assistant will run, because SQLite will have to read/write more data (and more metadata, such as indexes). Bookmark this page, go have fun, and come back later!Īfter using Home Assistant for several weeks, and after adding many integrations and devices, the recorder database will grow. Wait for a couple of weeks, get yourself more familiar with the project, enjoy your new home automation system, then come back to this guide. Why should you care about the database size? Well, there are several reasons…īut first, there is one reason why you should not care: if you are new to Home Assistant, don’t worry about the database size at the beginning. ![]() If your setup is different, this guide can still be useful, but you have to adapt to your environment. I’m running Home Assistant on a Raspberry Pi with the default SQLite database. How to figure out which entities are using too much space.Please be aware your Home Assistant version can be slightly different, and thus you need to adapt yourself the instructions from this guide. Since then, changes have happened, but this guide hasn’t been updated (yet). Note: This guide was written for an earlier version of Home Assistant (around 2021).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |