Unable to edit configuration

Configuration
1

Hi. Total newbie here.
I have a Hassio running on a Raspberry, ethernet connected.

I’ve successfully enabled SMB, and I CAN edit configuration.yaml

I’ve tried to add Netatmo thermostat and sensor as told in the help, and even started from scratch following the “random sensor” in the installation guide.

Each and every time I edit the .yaml file and I restart the raspberry, no frontend is started.
I have to revert back to a previous sconfiguration.yaml where I changed only the coordinates to make myip:8123 available again.

What I am doing wrong?

2

The easiest way I’ve found to choke Home Assistant is with a yaml formatting error.

Have you tried checking your changes in a yaml validator like yamllint.com?

1 Like
3

Sorry, I didn’t specify that I checked the config with the built-in tool without problems :confused:

4

What does the log say?

1 Like
5

After using Yamlint -I didn’t know it-, correcting some spaces/tabs, here the resulting log

2017-11-06 20:49:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] while parsing a block mapping
  in "/config/configuration.yaml", line 1, column 1
expected <block end>, but found '<block mapping start>'
  in "/config/configuration.yaml", line 84, column 3
2017-11-06 20:49:46 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while parsing a block mapping
  in "/config/configuration.yaml", line 1, column 1
expected <block end>, but found '<block mapping start>'
  in "/config/configuration.yaml", line 84, column 3

The first error is the worst, seen I didn’t touch the start of the configuration.yaml (row 1 column 1 isnt’t the real start of the file?)
Now I have to understand what a and are and how to change one for another :smiley:

6 
  homeassistant:
      # Name of the location where Home Assistant is running
      name: Home
      # Location required to calculate the time the sun rises and sets
      latitude: 43.xxxx
      longitude: 11.xxxx
      # Impacts weather/sunrise data (altitude above sea level in meters)
      elevation: 35
      # 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/Rome
      # 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

    group: !include groups.yaml
    automation: include automations.yaml
    script: !include scripts.yaml


    sensor:
      - platform: random
      
    netatmo:
      api_key: xxxxxx
      secret_key: xxxxxxx
      username: [email protected]
      password: xxxxxxx

    sensor:
        platform: netatmo
        station: Tardis
        modules:
      Esterno:
       - temperature
       - battery_vp
       - humidity
       - pressure	
      Interno:
        - temperature
        - battery_vp
        - humidity
        - co2
      Interno2:
         - temperature
         - battery_vp   
         - humidity		
         - co2
       Pluviometro:
          - sum_rain_1   
    		
     climate:
      - platform: netatmo

This is the whole code. I can’t understand yet.

7

Is this the formatting, or do you have 2 spaces in front of every line?
If so, delete them.

8

Your indent on line 84 (Esterno:) was incorrect. Hass is extremely tempermental about formatting, especially indents and spacing. Indentations must always be 2 spaces, no more, no less. You should also only use uppercase letters in friendly names, as hass will convert them to lowercase anyway.

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 43.xxxx
  longitude: 11.xxxx
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 35
  # 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/Rome
  # 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

group: !include groups.yaml
automation: include automations.yaml
script: !include scripts.yaml


sensor:
  - platform: random

netatmo:
  api_key: xxxxxx
  secret_key: xxxxxxx
  username: [email protected]
  password: xxxxxxx

sensor:
  platform: netatmo
  station: Tardis
  modules:
    esterno:
      - temperature
      - battery_vp
      - humidity
      - pressure	
    interno:
      - temperature
      - battery_vp
      - humidity
      - co2
    interno2:
      - temperature
      - battery_vp   
      - humidity		
      - co2
    pluviometro:
      - sum_rain_1   

climate:
  - platform: netatmo
2 Likes
9

thank you all, I have come to the same conclusion while Bahnburner was writing.
Now I am retrieving (and, don’t know why, displaying) all the data from all the sensors.
Another day, another problem :wink:

Again, thank you all :slight_smile:

1 Like