Invalid config
See original GitHub issueSince updating Home Assistant to 2021.4, I have received the following Invalid config notification. I believe this relates to the bom-weather-card and am hoping that you will be able to provide some help in fixing. I cannot decipher the code. It does mention Script in the notification, and the code it provides in the Log suggests line 14 of my configuration.yaml file which is my scripts.yaml. I have gone through Scripts and there is no script pertaining to the BOM-Weather-Card…
Logger: homeassistant.config Source: config.py:437 First occurred: 10:41:38 (1 occurrences) Last logged: 10:41:38
Invalid config for [script]: expected a dictionary. Got OrderedDict([(‘homeassistant’, OrderedDict([(‘name’, ‘Home’), (‘latitude’, -xx.xxxxxx), (‘longitude’, xxx.xxxxx), (‘elevation’, 24), (‘unit_system’, ‘metric’), (‘time_zone’, ‘Australia/Sydney’), (‘internal_url’, ‘http://homeassistant.local:8123’), (‘packages’, OrderedDict([(‘weather’, OrderedDict([(‘sensor’, [OrderedDict([(‘platform’, ‘template’), (‘sensors’, OrderedDict([(‘bom_current_text’, OrderedDict([(‘value_template’, "{% set val = states(‘sensor.zetland_short_text_0’).split(‘.’)[0] %} … (See /config/configuration.yaml, line 14).
And my config yaml for reference.
homeassistant: !include homeassistant.yaml
logger:
default: info
default_config:
mobile_app:
discovery:
frontend: !include frontend.yaml
tts: !include tts.yaml
cloud: !include cloud.yaml
group: !include groups.yaml
script: !include scripts.yaml
automation: !include automations.yaml
scene: !include scenes.yaml
device_tracker: !include device_tracker.yaml
input_select: !include input_select.yaml
sensor: !include sensor.yaml
binary_sensor: !include binary_sensor.yaml
zone: !include zones.yaml
proximity: !include proximity.yaml
light: !include light.yaml
switch: !include switch.yaml
climate: !include climate.yaml
spotify: !include spotify.yaml
#spotcast: !include spotcast.yaml
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top GitHub Comments
Yes I did… I’ll check it tomorrow but pretty sure as the card works it’s going to be something else in one of your scripts.
so I think the error is unrelated to the card config. Is the card showing ok in lovelace? I think the error is spurious as it seems to not like one of your scripts. If not, can you send me by email… weather.yaml lovelace config for card uour location lat/long so I can setup my config for your area. email: david@wilfam.net