Configuration validation does not work with Raspberry Pi All-In-One Installation

pi@RPI-Hass:~ $ hass --script check_config
-bash: hass: command not found

hey @cvanandel,

that’s because that installation is using virtual envs. You need to change to the Virtual Env before execute ir. Something like this:

Change to hass user:
sudo su -s /bin/bash hass

Change to virtual enviroment
source /srv/hass/hass_venv/bin/activate

once there you can execute hass:
hass --script check_config

give it a try …

2 Likes

@davedan
Thanks for the reply davedan, I will give it a try I am still a noob at this

@davedan
That worked like a charm, thanks a bunch

Hi davedan

I’m having the same problem and your instructions to cvanandel don’t work either…

pi@hassbian:~ $ hass --script check_config
Config does not exist: /home/pi/.homeassistant/configuration.yaml
pi@hassbian:~ $ sudo su -s /bin/bash hass
No passwd entry for user ‘hass’
pi@hassbian:~ $ source /srv/hass/hass_venv/bin/activate
-bash: /srv/hass/hass_venv/bin/activate: No such file or directory
pi@hassbian:~ $ hass --script check_config
Config does not exist: /home/pi/.homeassistant/configuration.yaml

You can use
hass --script check_config -c /path_to_configuration.yaml
replace /path_to_configuration.yaml to wherever your homeassistemt configuration is.

my configuration file is under
network/HASSBIAN/homeassistant/configuration

how would I type that into putty?

A normal hasbian install would create the configuration files in /home/homeassistant/.homeassistant so the command would be
hass --script check_config -c /home/homeassistant/.homeassistant

Note the DOT in front of the second homeassistant. In Linux creating a folder with a leading dot makes that folder hidden.