recorder integration is responsible for storing details in a database, which then are handled by the
Home Assistant uses SQLAlchemy, which is an Object Relational Mapper (ORM). This means that you can use any SQL backend for the recorder that is supported by SQLAlchemy, like MySQL, MariaDB, PostgreSQL, or MS SQL Server.
The default database engine is SQLite which doesn’t require any configuration. The database is stored in your Home Assistant configuration directory (
.homeassistant or ‘/config/’ in HassIO) and called
To change the defaults for the
recorder integration in your installation, add the following to your
# Example configuration.yaml entry recorder:
Enables the recorder integration. Only allowed once.
The URL that points to your database.
Specify the number of history days to keep in recorder database after a purge.
How often (in days) the purge task runs. If a scheduled purge is missed (e.g., if Home Assistant was not running), the schedule will resume soon after Home Assistant restarts. You can use the service call
purgewhen required without impacting the purge schedule. If this is set to
0(zero), automatic purging is disabled.
Configure which integrations should be excluded from recordings.
Configure which integrations should be included in recordings. If set, all other entities will not be recorded.
Defining domains and entities to
exclude (aka. blacklist) is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually, these are entities/domains that do not change (like
weblink) or rarely change (like
# Example configuration.yaml entry with exclude recorder: purge_keep_days: 5 db_url: sqlite:////home/user/.homeassistant/test exclude: domains: - automation - weblink - updater entities: - sun.sun # Don't record sun data - sensor.last_boot # Comes from 'systemmonitor' sensor platform - sensor.date
define domains and entities to record by using the
include configuration (aka. whitelist) is convenient if you have a lot of entities in your system and your
exclude lists possibly get very large, so it might be better just to define the entities or domains to record.
# Example configuration.yaml entry with include recorder: include: domains: - sensor - switch - media_player
You can also use the
include list to define the domains/entities to record, and exclude some of those within the
exclude list. This makes sense if you, for instance, include the
sensor domain, but want to exclude some specific sensors. Instead of adding every sensor entity to the
entities list just include the
sensor domain and exclude the sensor entities you are not interested in.
# Example configuration.yaml entry with include and exclude recorder: include: domains: - sensor - switch - media_player exclude: entities: - sensor.last_boot - sensor.date
If you only want to hide events from your history, take a look at the
history integration. The same goes for the logbook. But if you have privacy concerns about certain events or want them in neither the history or logbook, you should use the
include options of the
recorder integration. That way they aren’t even in your database, you can reduce storage and keep the database small by excluding certain often-logged events (like
Call the service
recorder.purge to start a purge task which deletes events and states older than x days, according to
keep_days service data.
|Service data attribute||Optional||Description|
||yes||The number of history days to keep in recorder database (defaults to the integration
||yes||Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses.|
|MS SQL Server||
Some installations of MariaDB/MySQL may require an ALTERNATE_PORT (3rd-party hosting providers or parallel installations) to be added to the SERVER_IP, e.g.,
Unix Socket connections always bring performance advantages over TCP, if the database is on the same host as the
recorder instance (i.e.
If you want to use Unix Sockets for PostgreSQL you need to modify the
pg_hba.conf. See PostgreSQL
If you are using the default
FULL recovery model for MS SQL Server you will need to manually backup your log file to prevent your transaction log from growing too large. It is recommended you change the recovery model to
SIMPLE unless you are worried about data loss between backups.
If you are running a database server instance on the same server as Home Assistant then you must ensure that this service starts before Home Assistant. For a Linux instance running Systemd (Raspberry Pi, Debian, Ubuntu and others) then you should edit the service file.
sudo nano /etc/systemd/system/[email protected]
and add the service for the database, for example, PostgreSQL:
[Unit] Description=Home Assistant After=network.target postgresql.service
Save the file then reload
sudo systemctl daemon-reload
Not all Python bindings for the chosen database engine can be installed directly. This section contains additional details that should help you to get it working.
If you are in a virtual environment, don’t forget to activate it before installing the
mysqlclient Python package described below.
[email protected]:~ $ sudo -u homeassistant -H -s [email protected]:~$ source /srv/homeassistant/bin/activate (homeassistant) [email protected]:~$ pip3 install mysqlclient
For MariaDB you may have to install a few dependencies. If you’re using MariaDB version 10.2,
libmariadbclient-dev was renamed to
libmariadb-dev. If you’re using MariaDB 10.3, the package
libmariadb-dev-compat must also be installed. Please install the correct packages based on your MariaDB version.
On the Python side we use the
sudo apt-get install libmariadbclient-dev libssl-dev pip3 install mysqlclient
For MySQL you may have to install a few dependencies. You can choose between
sudo apt-get install default-libmysqlclient-dev libssl-dev pip3 install mysqlclient
After installing the dependencies, it is required to create the database manually. During the startup, Home Assistant will look for the database specified in the
db_url. If the database doesn’t exist, it will not automatically create it for you.
Once Home Assistant finds the database, with the right level of permissions, all the required tables will then be automatically created and the data will be populated accordingly.
For PostgreSQL you may have to install a few dependencies:
sudo apt-get install postgresql-server-dev-X.Y pip3 install psycopg2
For using Unix Sockets, add the following line to your
local DB_NAME USER_NAME peer
DB_NAME is the name of your database and
USER_NAME is the name of the user running the Home Assistant instance (see securing your installation).
Reload the PostgreSQL configuration after that:
$ sudo -i -u postgres psql -c "SELECT pg_reload_conf();" pg_reload_conf ---------------- t (1 row)
A service restart will work as well.
For MS SQL Server you may have to install a few dependencies:
sudo apt-get install freetds-dev pip3 install pymssql
If you are in a virtual environment, don’t forget to activate it before installing the pymssql package.
sudo -u homeassistant -H -s source /srv/homeassistant/bin/activate pip3 install pymssql