-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
Comments
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
pushed a commit
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:Traceback (if applicable):
Additional info:
The text was updated successfully, but these errors were encountered: