Someone please help this noob!

I can’t get the weather to work right wont take the multiple senor and doesnt like the groups either. been strugglng to to figure it out. please help.

[quote=“matthoover14, post:1, topic:37797, full:true”]
I can’t get the weather to work right wont take the multiple senor and doesnt like the groups either. been strugglng to to figure it out. please help.

indent preformatted text by 4 spaces
#  Name of the location where Home Assistant is running
  name: Boone Grove
#  Location required to calculate the time the sun rises and sets
  latitude: 41.3538
  longitude: -87.1340
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 715
  # metric for Metric, imperial for Imperial
  unit_system: imperial
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Chicago
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
   frontend:

# Enables configuration UI
config:

  mqtt:
   broker: 
   port: 
   client_id: home-assistant-1
   username:
   password: 

binary_sensor:
  - platform: iss
camera:
  - platform: generic
    name: ISS
    still_image_url: https://maps.googleapis.com/maps/api/staticmap?center={{ states.binary_sensor.iss.attributes.lat }},{{ states.binary_sensor.iss.attributes.long }}&zoom=5&size=500x500&maptype=roadmap&markers=color:blue%7Clabel:P%7C{{ states.binary_sensor.iss.attributes.lat }},{{ states.binary_sensor.iss.attributes.long }}
    limit_refetch_to_url_change: true

device_tracker:
  - platform: owntracks
#mqtt:
#  broker: 
#  port: 
#    waypoints: True
#    waypoint_whitelist:
#      - owntracks/phone
zwave:
  usb_path: /dev/ttyACM0

http:
  # Secrets are defined in the file secrets.yaml
  api_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

# Text to speech
tts:
  - platform: google

# Cloud
#cloud:

group: !include groups.yaml
sensor:
  - platform: wunderground
    api_key: 7c862c00f78cd8ed
    monitored_conditions:
      - temp_high_record_c
      - temp_high_1d_c
      - temp_c
      - temp_low_1d_c
      - temp_low_record_c
      - precip_1d
      - precip_1d_mm
      - wind_kph
      - wind_1d_kph
      - alerts

group:
 # weather_overview:
  name: Weather overview
  entities:
      - sensor.pws_weather_1d_metric
      - sensor.pws_temp_high_record_c
      - sensor.pws_temp_high_1d_c
      - sensor.pws_temp_c
      - sensor.pws_temp_low_1d_c
      - sensor.pws_temp_low_record_c
      - sensor.pws_precip_1d
      - sensor.pws_precip_1d_mm
      - sensor.pws_wind_kph
      - sensor.pws_wind_1d_kph
      - sensor.pws_alerts

  monitored_conditions:
      - weather_1d_imperial
      - weather_1n_imperial
      - weather_2d_imperial
      - weather_2n_imperial
      - weather_3d_imperial
      - weather_3n_imperial
      - weather_4d_imperial
      - weather_4n_imperial
 # daily_forecast:
  name: Daily Forecast
  entities:
      - sensor.pws_weather_1d_imperial
      - sensor.pws_weather_1n_imperial
      - sensor.pws_weather_2d_imperial
      - sensor.pws_weather_2n_imperial
      - sensor.pws_weather_3d_imperial
      - sensor.pws_weather_3n_imperial
      - sensor.pws_weather_4d_imperial
      - sensor.pws_weather_4n_imperial

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

Before anyone’s going to give you a hand, you’re going to need to fix your formatting. Use the < / > button to post code. Or start and end the block with three ticks (the key to the right of 1).

Also, a sample from the home_assistant.log error would be helpful.

1 Like

I found the space or indent of the camera: is a little strange. It is quite hard to see. If you could put it with </> would be great.

ok i found how to fix the view i will get the error codes

the camera is one of the few thigs that is working lol

ok this is the error codes i get from home assitant
Testing configuration at /config

2018-01-03 20:48:36 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key “name”. Check lines 110 and 134.
2018-01-03 20:48:36 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key “entities”. Check lines 111 and 135.
2018-01-03 20:48:36 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/configuration.yaml contains duplicate key “group”. Check lines 92 and 108.
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.config] Invalid config for [introduction]: not a valid value for dictionary value @ data[‘introduction’]. Got OrderedDict([(‘frontend’, None)]). (See /config/configuration.yaml, line 19). Please check the docs at https://home-assistant.io/components/introduction/
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Setup failed for introduction: Invalid config.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up http
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up recorder
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up history
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up zwave
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.config] Invalid config for [group]: Entity ID daily forecast is an invalid entity id for dictionary value @ data[‘group’][‘name’][‘entities’]. Got None
Entity ID weather_1d_imperial is an invalid entity id for dictionary value @ data[‘group’][‘monitored_conditions’][‘entities’]. Got None. (See /config/configuration.yaml, line 110). Please check the docs at https://home-assistant.io/components/group/
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Setup failed for group: Invalid config.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up updater
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up sensor
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up sun
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up map
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up discovery
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain zwave took 0.3 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.3 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.2 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.1 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.1 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up zone
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain discovery took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up config
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of automation. Setup failed for dependencies: group
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Setup failed for automation: Could not setup all dependencies.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up conversation
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of script. Setup failed for dependencies: group
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Setup failed for script: Could not setup all dependencies.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up tts
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up camera
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up api
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up system_log
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of device_tracker. Setup failed for dependencies: group
2018-01-03 20:48:38 ERROR (MainThread) [homeassistant.setup] Setup failed for device_tracker: Could not setup all dependencies.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up frontend
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds.
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setting up logbook
2018-01-03 20:48:38 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.0 seconds.
Failed config
introduction:
frontend: None

General Errors:
- Setup failed for introduction: Invalid config.
- Setup failed for group: Invalid config.
- Unable to setup dependencies of automation. Setup failed for dependencies: group
- Setup failed for automation: Could not setup all dependencies.
- Unable to setup dependencies of script. Setup failed for dependencies: group
- Setup failed for script: Could not setup all dependencies.
- Unable to setup dependencies of device_tracker. Setup failed for dependencies: group
- Setup failed for device_tracker: Could not setup all dependencies.

group:
entities: [source /config/configuration.yaml:136]
- sensor.pws_weather_1d_imperial
- sensor.pws_weather_1n_imperial
- sensor.pws_weather_2d_imperial
- sensor.pws_weather_2n_imperial
- sensor.pws_weather_3d_imperial
- sensor.pws_weather_3n_imperial
- sensor.pws_weather_4d_imperial
- sensor.pws_weather_4n_imperial
monitored_conditions: [source /config/configuration.yaml:125]
- weather_1d_imperial
- weather_1n_imperial
- weather_2d_imperial
- weather_2n_imperial
- weather_3d_imperial
- weather_3n_imperial
- weather_4d_imperial
- weather_4n_imperial
name: Daily Forecast

Successful config (partial)
introduction:
group:

from your configuration.yaml I see double group: one pointed to group: !include groups.yaml
and another one group:

weather_overview:

name: Weather overview

put this inside groups.yaml./ take group: out from configuration.yaml and leave the group: !include groups.yaml in configuration.yaml

  name: Weather overview
  entities:
      - sensor.pws_weather_1d_metric
      - sensor.pws_temp_high_record_c
      - sensor.pws_temp_high_1d_c
      - sensor.pws_temp_c
      - sensor.pws_temp_low_1d_c
      - sensor.pws_temp_low_record_c
      - sensor.pws_precip_1d
      - sensor.pws_precip_1d_mm
      - sensor.pws_wind_kph
      - sensor.pws_wind_1d_kph
      - sensor.pws_alerts

  monitored_conditions:
      - weather_1d_imperial
      - weather_1n_imperial
      - weather_2d_imperial
      - weather_2n_imperial
      - weather_3d_imperial
      - weather_3n_imperial
      - weather_4d_imperial
      - weather_4n_imperial
 # daily_forecast:
  name: Daily Forecast
  entities:
      - sensor.pws_weather_1d_imperial
      - sensor.pws_weather_1n_imperial
      - sensor.pws_weather_2d_imperial
      - sensor.pws_weather_2n_imperial
      - sensor.pws_weather_3d_imperial
      - sensor.pws_weather_3n_imperial
      - sensor.pws_weather_4d_imperial
      - sensor.pws_weather_4n_imperial
1 Like

ok i did that and now a buch of other stuuf that was working before isn’t? still no weather?

#cloud:

group: !include groups.yaml

automation: !include automations.yaml
script: !include scripts.yaml
1 Like

from your sensor platform I see only from wuunderground.

sensor:
  - platform: wunderground
    api_key: 7c862c00f78cd8ed
    monitored_conditions:
      - temp_high_record_c
      - temp_high_1d_c
      - temp_c
      - temp_low_1d_c
      - temp_low_record_c
      - precip_1d
      - precip_1d_mm
      - wind_kph
      - wind_1d_kph
      - alerts

From group platform. I see group.weather_overview, group.monitored_conditions and group.daily forcast. But the sensor inside these group, where are they come from?
And the group: monitored_conditions you have to put name: and entities: inside the group
monitored_conditions:
- weather_1d_imperial
- weather_1n_imperial
- weather_2d_imperial
- weather_2n_imperial
- weather_3d_imperial
- weather_3n_imperial
- weather_4d_imperial
- weather_4n_imperial

i just followed the coding example on the home assistant components page for weather/ weather underground. this is what my config.yaml looks like now but it is bricking out of home asst.

error codes has follows;

2018-01-03 21:57:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/groups.yaml contains duplicate key “name”. Check lines 3 and 27.
2018-01-03 21:57:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] YAML file /config/groups.yaml contains duplicate key “entities”. Check lines 4 and 28.
2018-01-03 21:57:46 ERROR (SyncWorker_0) [homeassistant.util.yaml] while parsing a block mapping
in “/config/automations.yaml”, line 1, column 3
expected , but found ‘-’
in “/config/automations.yaml”, line 6, column 3
2018-01-03 21:57:46 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/automations.yaml”, line 1, column 3
expected , but found ‘-’
in “/config/automations.yaml”, line 6, column 3

#  Name of the location where Home Assistant is running
  name: Boone Grove
#  Location required to calculate the time the sun rises and sets
  latitude: 41.3538
  longitude: -87.1340
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 715
  # metric for Metric, imperial for Imperial
  unit_system: imperial
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Chicago
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

mqtt:
  broker: 
  client_id: home-assistant-1
  username: 
  password:

binary_sensor:
  - platform: iss
    camera:
  - platform: generic
    name: ISS
    still_image_url: https://maps.googleapis.com/maps/api/staticmap?center={{ states.binary_sensor.iss.attributes.lat }},{{ states.binary_sensor.iss.attributes.long }}&zoom=5&size=500x500&maptype=roadmap&markers=color:blue%7Clabel:P%7C{{ states.binary_sensor.iss.attributes.lat }},{{ states.binary_sensor.iss.attributes.long }}
    limit_refetch_to_url_change: true

device_tracker:
  - platform: owntracks
#mqtt:
#  broker: 1
#  port: 1
#    waypoints: True
#    waypoint_whitelist:
#      - owntracks//phone
zwave:
  usb_path: /dev/ttyACM0

http:
  # Secrets are defined in the file secrets.yaml
  api_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

# Text to speech
tts:
- platform: google

# Cloud
#cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
sensor:
  - platform: wunderground
    api_key: 7c862c00f78cd8ed
    monitored_conditions:
      - temp_high_record_c
      - temp_high_1d_c
      - temp_c
      - temp_low_1d_c
      - temp_low_record_c
      - precip_1d
      - precip_1d_mm
      - wind_kph
      - wind_1d_kph
      - alerts
      - weather_1d_imperial
      - weather_1n_imperial
      - weather_2d_imperial
      - weather_2n_imperial
      - weather_3d_imperial
      - weather_3n_imperial
      - weather_4d_imperial
      - weather_4n_imperial

So whatever from wuunderground you have to put it in wuundergroup platform first. Then when you get the entities_id for each one you can make it in a group platform

1 Like

i am way over my head thank you. i have to go back over config from last post it’s not even letting me open h.a. now

it cannot load ha because of wrong configuration. your ha is still ok. take out the wuunderground from group first. Then try restart your ha. it will surely come back.

so take it out of group.yaml?

take these out from groups.yaml

  name: Weather overview
  entities:
      - sensor.pws_weather_1d_metric
      - sensor.pws_temp_high_record_c
      - sensor.pws_temp_high_1d_c
      - sensor.pws_temp_c
      - sensor.pws_temp_low_1d_c
      - sensor.pws_temp_low_record_c
      - sensor.pws_precip_1d
      - sensor.pws_precip_1d_mm
      - sensor.pws_wind_kph
      - sensor.pws_wind_1d_kph
      - sensor.pws_alerts

  monitored_conditions:
      - weather_1d_imperial
      - weather_1n_imperial
      - weather_2d_imperial
      - weather_2n_imperial
      - weather_3d_imperial
      - weather_3n_imperial
      - weather_4d_imperial
      - weather_4n_imperial
 # daily_forecast:
  name: Daily Forecast
  entities:
      - sensor.pws_weather_1d_imperial
      - sensor.pws_weather_1n_imperial
      - sensor.pws_weather_2d_imperial
      - sensor.pws_weather_2n_imperial
      - sensor.pws_weather_3d_imperial
      - sensor.pws_weather_3n_imperial
      - sensor.pws_weather_4d_imperial
      - sensor.pws_weather_4n_imperial
1 Like

ok did that but error codes has follows;

2018-01-03 22:29:41 ERROR (SyncWorker_0) [homeassistant.util.yaml] while parsing a block mapping
in “/config/automations.yaml”, line 1, column 3
expected , but found ‘-’
in “/config/automations.yaml”, line 6, column 3
2018-01-03 22:29:41 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while parsing a block mapping
in “/config/automations.yaml”, line 1, column 3
expected , but found ‘-’
in “/config/automations.yaml”, line 6, column 3

#  Name of the location where Home Assistant is running
  name: Boone Grove
#  Location required to calculate the time the sun rises and sets
  latitude: 41.3538
  longitude: -87.1340
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 715
  # metric for Metric, imperial for Imperial
  unit_system: imperial
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Chicago
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

mqtt:
  broker: 
  port: 
  client_id: home-assistant-1
  username: 
  password: 

binary_sensor:
  - platform: iss
    camera:
  - platform: generic
    name: ISS
    still_image_url: https://maps.googleapis.com/maps/api/staticmap?center={{ states.binary_sensor.iss.attributes.lat }},{{ states.binary_sensor.iss.attributes.long }}&zoom=5&size=500x500&maptype=roadmap&markers=color:blue%7Clabel:P%7C{{ states.binary_sensor.iss.attributes.lat }},{{ states.binary_sensor.iss.attributes.long }}
    limit_refetch_to_url_change: true

device_tracker:
  - platform: owntracks
#mqtt:
#  broker: 
#  port: 
#    waypoints: True
#    waypoint_whitelist:
#      - owntracks//phone
zwave:
  usb_path: /dev/ttyACM0

http:
  # Secrets are defined in the file secrets.yaml
  api_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

# Text to speech
tts:
- platform: google

# Cloud
#cloud:

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

the groups.yaml file is ok now. but problem with your automations.yaml file. So check that file.

copy your automation from automations.yaml file in www.yamllint.com
You will see what wrong with your automation

Normally, the problem come from space and indent.

yaaaaaaa it worked

1 Like