# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: 52.5416
longitude: 13.3904
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 0
# metric for Metric, imperial for Imperial
unit_system: metric
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: Europe/Berlin
# Customization file
customize: !include customize.yaml
# Show links to resources in log and frontend
introduction:
# Enables the frontend
frontend:
# Enables configuration UI
config:
http:
# Secrets are defined in the file secrets.yaml
# api_password: !secret http_password
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# base_url: example.duckdns.org:8123
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
# Optional, allows Home Assistant developers to focus on popular components.
# include_used_components: true
# Discover some devices automatically
discovery:
# Allows you to issue voice commands from the frontend in enabled browsers
conversation:
# Enables support for tracking state changes over time
history:
# View all events in a logbook
logbook:
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# Weather prediction
sensor:
- platform: yr
# Text to speech
tts:
- platform: google
# Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
^^^ This. recorder: is required in the configuration if you also call logbook: or history:. Unlike some other components, recorder is not automatically loaded as a dependency.
thanks guys, I added recorder: to the file, but unfortunately, the problem persists (also after rebooting).
this is what I get when I “Check Config” in the HA backend:
Configuration invalid.CHECK CONFIG
INFO:homeassistant.util.package:Attempting install of colorlog==3.0.1
ERROR:homeassistant.util.package:Unable to install package colorlog==3.0.1: Exception:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/srv/homeassistant/lib/python3.5/site-packages/pip/commands/install.py", line 360, in run
prefix=options.prefix_path,
File "/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_set.py", line 784, in install
**kwargs
File "/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_install.py", line 851, in install
self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
File "/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_install.py", line 1064, in move_wheel_files
isolated=self.isolated,
File "/srv/homeassistant/lib/python3.5/site-packages/pip/wheel.py", line 345, in move_wheel_files
clobber(source, lib_dir, True)
File "/srv/homeassistant/lib/python3.5/site-packages/pip/wheel.py", line 316, in clobber
ensure_dir(destdir)
File "/srv/homeassistant/lib/python3.5/site-packages/pip/utils/__init__.py", line 83, in ensure_dir
os.makedirs(path)
File "/usr/lib/python3.5/os.py", line 241, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/srv/homeassistant/lib/python3.5/site-packages/colorlog-3.0.1.dist-info'
Aborting script, could not install dependency colorlog==3.0.1
And there is your issue. It failed to install a dependency. I’m not too familiar with installs that aren’t in a Docker container as that’s what I run, but you can try installing the dependency yourself that it lists in the error and see if it launches HA with your automations file then.
EDIT: I just noticed a permissions issue is called out in the error log. Unfortunately I will be of little help there as well but double check the user running HA has proper permissions to run python and access the automation file.
From a security standpoint, just changing permissions on a folder for python packages in a production environment can be a bad thing… but 770 isn’t as bad as 777. glad it’s working for you now