How come I have to run these commands to start the Home Assistant?

[homeAssist3050 (homeAssist)]

I guess because the HA runs in a VM if the PI reboots I have to run these commands again to start the HA?

[email protected]:~ $ sudo -u homeassistant -H -s
[email protected]:/home/pi $ cd /srv/homeassistant
[email protected]:/srv/homeassistant $ source bin/activate
(homeassistant) [email protected]:/srv/homeassistant $ hass

Would I just make a linux script and do like a cron job so this is always running? I woke up this morning and the HA wasn’t running from last night, so I had to manually run it via SSH.

Is there a better way to handle this?

[jocnnor (Jim O'Connor)]

Just create a service to run it, then do “systemctl enable” which means “start this service on boot”.

Autostart using systemd

Newer Linux distributions are trending towards using systemd for managing daemons. Typically, systems based on Fedora, ArchLinux, or Debian (8 or later) use systemd. This includes Ubuntu releases including and after 15.04, CentOS, and Red Hat. If you are unsure if your system is using systemd, you may check with the following command: ps -p 1 -o comm= If the preceding command returns the string systemd, continue with the instructions below. A service file is needed to control Home Assistant …

If they do exist, skip to the end where you just ‘enable’ the service

sudo systemctl enable [email protected]_USER

[homeAssist3050 (homeAssist)]

Thanks, Turns out I had the core HA version installed. I installed the HA OS version and now everything works automated.