From 93df84bb5ae0fd68b28faa610c57ee7877e68150 Mon Sep 17 00:00:00 2001 From: Jerry Workman Date: Mon, 26 Feb 2018 21:19:33 -0500 Subject: [PATCH] Add note to ensure database instance starts before Home Assistant --- source/_components/recorder.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/_components/recorder.markdown b/source/_components/recorder.markdown index 039d94ceb2d..f8eebfe4e38 100644 --- a/source/_components/recorder.markdown +++ b/source/_components/recorder.markdown @@ -156,6 +156,15 @@ If the `recorder` component is activated then some components support `restore_s | PostgreSQL | `postgresql://scott:tiger@SERVER_IP/DB_NAME` | | MS SQL Server | `mssql+pymssql://user:pass@SERVER_IP/DB_NAME?charset=utf8` | ++

++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 file /etc/systemd/system/home-assistant@homeassistant.service as root (e.g. sudo nano /etc/systemd/system/home-assistant@homeassistant.service) and add the service - for PostgreSQL: ++``` ++[Unit] ++Description=Home Assistant ++After=network.target postgresql.service ++``` ++

+ ## {% linkable_title Installation notes %} Not all Python bindings for the chosen database engine can be installed directly. This section contains additional details which should help you to get it working.