Hass.IO Suddenly Worked Again.
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: xxxxx
longitude: xxxx
# 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: Asia/Singapore
# 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: xxx.duckdns.org:8123
{
"defaults": [
"8.8.8.8",
"8.8.4.4"
],
"forwards": [8123],
"hosts": [
{
"host": "xxx.duckdns.org",
"ip": "192.168.1.103"
}
]
}
# 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
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: http://192.168.1.3:3218
xiaomi_aqara:
discovery_retry: 5
gateways:
- key: xxxxxx
ifttt:
key: xxxxxxx
your http: section is completely broken. your YAML should not have JSON in it like that.
So I removed the lines you mentioned above and it worked for one instance and refused to load again after the following restart.
Any idea what could be the possible reasoning? I’ll send the current configuration.yaml below.
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: 1.2855
longitude: 103.8565
# 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: Asia/Singapore
# 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: myip.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
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: http:/myip:3218
xiaomi_aqara:
discovery_retry: 5
gateways:
- key: xxxx
ifttt:
key: xxxxx
[/quote]
> Blockquote
Well, what do the logs say?
You aren’t going to be able to troubleshoot anything if you don’t look at the logs.
If the logs mentioned refers to home-assistang.log then here are the logs below:
2018-01-15 14:56:12 ERROR (SyncWorker_0) [homeassistant.util.yaml] mapping values are not allowed here
in “/config/groups.yaml”, line 9, column 14
2018-01-15 14:56:12 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: mapping values are not allowed here
in “/config/groups.yaml”, line 9, column 14
So fix your groups yaml… That’s obviously the problem at this point.
Sorry for sounding stupid. I’m really new at this.
2018-01-19 08:31:40 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=12 from 2018-01-15 09:11:42.377447)
2018-01-19 08:31:52 WARNING (MainThread) [homeassistant.setup] Setup of sensor is taking over 10 seconds.
2018-01-19 08:32:01 WARNING (MainThread) [homeassistant.components.sensor.yr] Retrying in 15 minutes: Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:True [Try again]
2018-01-19 08:32:03 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
Here’s a recent log from my Hass.Io. It’s back to being unable to open the GUI. Hope you could assist. Thanks.
If you don’t share your complete configuration (minus the usernames/passwords/API keys), we can’t really help you.
You have a problem in your configuration. It won’t load because your configuration is broken.
I have the same issue, after a reboot I get the erro connection refused. I’m new and even do not now how to access the file. should I take the SD card out and use a special program to acces that?
Hey Arkest. Firstly don’t panic. Hassio has really strict rules for the configurations.yaml file. More than likely, something in there has gone wrong.
Do you have access to the configurations.yaml file? You can access this through configurator (hassio.local:3218) or samba share on your laptop.
Once you’ve obtained the configurations.yaml file, post the content here (excluding passwords/usernames/API keys).
thanks for your response, hope I can get it back to work, I got the file from the SD card:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: 51.9934
longitude: 4.216
# 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/Amsterdam
# Customization file
customize: !include customize.yaml
# Show links to resources in log and frontend
introduction:
# Enables the frontend
frontend:
# Enables configuration UI
config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
base_url: https://arkest.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
# 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:
# add logging for mysensor
logger:
default: info
logs:
homeassistant.components.mysensors: debug
mysensors: debug
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# adding the mysensors
mysensors:
gateways:
- device: '/dev/ttyUSB0'
- device: '/dev/ttyACM0'
persistence_file: '/config/mysensors.json'
# baud_rate: 38400
# persistence: true
# retain: true
version: '2.0'
# Sensors
sensor:
# Weather prediction
- platform: yr
# Text to speech
tts:
- platform: google
# Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: http://hassio.local:3218
You have duplicatemysensors
You also have bad spacing on one of those.
The log file will literally tell you where it’s messed up and why
thanks for your support, it’s solved, indeed some mistakes in the config file. your support was just what I needed to point the direction. (and that it was that easy to acces the files via hassio.local:3218)
What do I do if I get ERR_CONNECTION_REFUSED and I cannot get acces via port 3218? My putty says connection refused as well. I can ping and get answer, so the Pi3 is running. I’ve installed Hassio and I’m at 0.87
Any suggestions?