Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rfxtrx config validatin breaking the components #1756

Closed
turbokongen opened this issue Apr 9, 2016 · 1 comment · Fixed by #1758
Closed

Rfxtrx config validatin breaking the components #1756

turbokongen opened this issue Apr 9, 2016 · 1 comment · Fixed by #1758

Comments

@turbokongen
Copy link
Contributor

Home Assistant release (hass --version):
0.18.dev0

Python release (python3 --version):
3.5.1

Component/platform:
rfxtrx

Description of problem:
The config validation has broken the rfxtrx component at switch, light, and sensor level.
It reports back:
16-04-09 09:52:27 homeassistant.bootstrap: Invalid config for [rfxtrx]: extra keys not allowed @ data['zwave']
In this case it reports zwave as extra key, but at each restart it pics a random component in the config.
Expected:

Problem-relevant configuration.yaml entries and steps to reproduce:

homeassistant:
  # Name of the location where Home Assistant is running
  name: 'Drømmehuset'
  # Location required to calculate the time the sun rises and sets
  latitude: xxx
  longitude: xxx
  # C for Celcius, F for Fahrenheit
  temperature_unit: C
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: Europe/Oslo

##########################################################
# Personligfisering
##########################################################
  customize: !include customize.yaml

# Discover some devices automatically
# discovery:

# Pushbullet notification service
notify:
  platform: pushbullet
  api_key: xxx
  name: 'pushmelding'

# Zwave settings
zwave:
  usb_path: /dev/ttyACM0
  config_path: /usr/local/share/python-openzwave/config
  polling_interval: 60000
  debug: 0

# RFXtrx433E settings
rfxtrx:
  device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Z69C6G-if00-port0

# Enables support for tracking state changes over time.
history:
  placeholder: true

# Track the sun
sun:

# Enables the frontend
frontend:

# View all events in a logbook
logbook:

# Show links to resources in log and frontend
#introduction:

# Allows you to issue voice commands from the frontend
#conversation:

# Checks for available updates
# updater:

# Verisure Hub
verisure:
 username: xxx
 password: xxx
 code_digits: 6

http:
 development: 1
 api_password: xxx

########################################################
# Overvåkere
########################################################
device_tracker:
  - platform: ddwrt
    host: 10.0.0.138
    username: xxx
    password: xxx
  - platform: ddwrt
    host: 10.0.0.88
    username: xxx
    password: xxx

########################################################
# Grupper
########################################################
group: !include group.yaml

#########################################################
# Sensorer
#########################################################
sensor: !include sensor.yaml

#########################################################
# Brytere
#########################################################
switch: !include switches.yaml
#########################################################
# Lysbrytere
#########################################################
light: !include light.yaml
#########################################################
# Thermostats
#########################################################
thermostat: !include thermostat.yaml

#########################################################
# Automation
#########################################################
automation: !include automation.yaml

####################################
# Automation scripts
####################################
script: !include script.yaml

media_player:
  - platform: cast
#  platform: samsungtv
#  host: 10.0.0.13
#  port: 7676

input_select: !include input_select.yaml

Traceback (if applicable):

16-04-09 09:52:10 homeassistant.bootstrap: Invalid config for [rfxtrx]: extra keys not allowed @ data['zwave']
16-04-09 09:52:10 homeassistant.bootstrap: Unable to prepare setup for platform switch.rfxtrx because dependency rfxtrx could not be initialized
16-04-09 09:52:11 homeassistant.bootstrap: Invalid config for [rfxtrx]: extra keys not allowed @ data['zwave']
16-04-09 09:52:11 homeassistant.bootstrap: Unable to prepare setup for platform sensor.rfxtrx because dependency rfxtrx could not be initialized
16-04-09 09:52:00 homeassistant.bootstrap: Invalid config for [rfxtrx]: extra keys not allowed @ data['zwave']
16-04-09 09:52:00 homeassistant.bootstrap: Unable to prepare setup for platform light.rfxtrx because dependency rfxtrx could not be initialized

Additional info:

@Danielhiversen
Copy link
Member

I'm sorry for that. I will not be able to fix it before Monday 😢

turbokongen added a commit to turbokongen/home-assistant that referenced this issue Apr 9, 2016
balloob added a commit that referenced this issue Apr 9, 2016
* We need to allow extra keys on top level componenet config

fixes #1756

* Add comment about location of hass (fixes #1723)

* Fix for MQTT config validation on the protocol field. (#1765)

* Update frontend with weblink fix

* Fix for light service validation. (#1770)

Incorrect validation tested if passed value was a list instead of
a member of the list.

* Accept group without entities in configuration. (#1768)

* Accept group without entities in configuration.

People seem to use these as placeholders for future expansion of their
home automation dreams, and we used to accept them.  We still have to
specify at least one of 'name', 'view' or 'icon' so that the group is
parsed as a dictionary.

* Also accept empty entities: key in a group.

* Additional fix for empty entities value in a group config.

* Version bump to 0.17.1
@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants