Here is my error, Your configuration contains extra keys that the platform does not support.
Please remove [payload_off].
binary_sensor:
- platform: mqtt
device_class: motion
state_topic: "smartthings/Kitchen Motion Sensor/motion/state"
name: 'Kitchen Motion Sensor'
payload_on: "active"
payload_off: "inactive"
Any ideas on how I can fix this?
Hello,
I am having similar issues with a custom component in the new version of Home assistant.
i tired to seek help through the post by @balloob above but as its a custom component i can’t get help from home assistant and the author @daemondazz of the component is not replying.
any help would be much appreciated.
Home Assistant release with the issue:
0.88.1 onward
Last working Home Assistant release (if known):
0.87
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/custom_components/display/fully_kiosk
Link to component: GitHub - daemondazz/homeassistant-displays: Custom display platform and components for Home Assistant
Description of problem:
As of 0.88.1 a warning is shown:
Your configuration contains extra keys that the platform does not support (but were silently accepted before 0.88). Please find and remove the following.This will become a breaking change.
- [name], [host], [password]. (See /config/configuration.yaml, line 70).
- [name], [host], [password]. (See /config/configuration.yaml, line 74).
- [name], [host], [password]. (See /config/configuration.yaml, line 78).
- [name], [host], [password]. (See /config/configuration.yaml, line 82).
Problem-relevant configuration.yaml entries:
#tablet battery
display:
- platform: fully_kiosk
name: Dining Tablet
host: '192.168.0.179'
password: !secret http_password
- platform: fully_kiosk
name: Lobby Tablet
host: '192.168.0.168'
password: !secret http_password
- platform: fully_kiosk
name: TV Tablet
host: '192.168.0.185'
password: !secret http_password
- platform: fully_kiosk
name: 'Nexus 10 Tablet'
host: '192.168.0.183'
password: !secret http_password
Any help people are able to give as to what needs changing would be much appreciated.
I’m sorry for being the bearer of bad news. I’ve used this analogy before. Going to balloob for a custom component is like talking with apple about why the google maps app doesn’t work. It seems as if the developer abandoned this component. So you’ll need to fix it, get the dev to fix it, or get someone else to make a new repo with the fixes. Good luck.
Hi @petro,
I totally get your point about going to balloob and only did this as it was suggested above to report it.
I’m not very experienced in coding but am more then willing to try an fix it myself, just no idea how to.
that why I’m posting here, I’m hoping someone with more experience and knowledge may be able to help guide me in the right direction. It has been suggested elsewhere that the ‘name’ ‘host’ and ‘password’ may not be in the ‘fully_kiosk’ configuration schema but have no idea what this is or how to add them.
I think you should create a new thread listing the component and issue. Burying it in this thread won’t get much visibility.
Exactly same issue here with icon and device. Has anyone solved it?
For me it was the Xiaomi Dafang camera with alternate firmware… (https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks)
Updating firmware fixed it for me.
ok preparing for the big upgrade, I’ve found a few keys… icon and unit_of_measurement in my case.
still im puzzled what to do, since in this particular case, the keys do work… the statistics sensor https://www.home-assistant.io/components/sensor.statistics/
the icon and unit_of_measurement aren’t listed, but my config
- platform: statistics
entity_id: sensor.gas_actueel_verbruik
name: Gas uur gemiddelde
icon: mdi:fire
max_age:
minutes: 60
unit_of_measurement: '/m3'
show correctly. 
would this be a config error, or a bug to be issued and adapted in the doc’s…
Icon is not a valid field. Take a look at the page you linked. Do you see “icon” listed? It’s not even a valid option for the base sensor class. It should be configured in the customize section.
thanks, both fields aren’t valid apparently. moved them to the customize.
have three more though in my report, that are not found in the sensor platforms anywhere I can find manually… Would there be an nifty script command to find the icon and unit_of_measurement fields in the config files?
this isn’t much help without further locating the issue:
[Info] Installed homeassistant==0.90.2, check config now
[Error] Wrong config found!
Testing configuration at /tmp/config
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon].
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon].
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon].
WARNING:homeassistant.components.http:Configuring api_password via the http component has been deprecated. Use the legacy api password auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password
WARNING:homeassistant.components.http:Configuring trusted_networks via the http component has been deprecated. Use the trusted networks auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#trusted-networks
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon], [unit_of_measurement].
Failed config
General Errors:
- Platform not found: binary_sensor.hue
- Platform not found: sensor.hue
- Platform not found: sensor.hue
- Platform not found: device_tracker.hue
Which 3, you’ve got a ton of warnings there
sorry, I meant the top 3 icon warnings. The others are self-explanatory…Would need and love some extra help from HA to locate these
the bottom warning about the [icon] and [unit_of_measurement] was the erroneous statistics sensor which I now repaired and reran the conf checker on successfully:
[Info] Installed homeassistant==0.90.2, check config now
[Error] Wrong config found!
Testing configuration at /tmp/config
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon].
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon].
WARNING:homeassistant.helpers.config_validation:Your configuration contains extra keys that the platform does not support.
Please remove [icon].
WARNING:homeassistant.components.http:Configuring api_password via the http component has been deprecated. Use the legacy api password auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password
WARNING:homeassistant.components.http:Configuring trusted_networks via the http component has been deprecated. Use the trusted networks auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#trusted-networks
Failed config
General Errors:
- Platform not found: device_tracker.hue
- Platform not found: binary_sensor.hue
- Platform not found: sensor.hue
- Platform not found: sensor.hue
Successful config (partial)
Use notepad++ to search your config directory for all ‘icon:’ fields.
cool, forget about that. Use BBEdit here 
think I might have found the culprits, in the light group. Which is silly of course, since both lights and groups have the icon: as a valid field.
https://www.home-assistant.io/components/light.group/ doesn’t offer it as an option however. Think that might be a bug? Doesn’t work in the front-end either, so that figures.
light:
- platform: group
icon: mdi:silverware
name: EetTafel
entities:
- light.dining_table_lamp_1
- light.dining_table_lamp_2
- light.dining_table_lamp_3
It’s not a bug. They revamped the system so that unused fields are completely ignored. All icon handling is done through customize. Just look in the docs for that, Icon is not listed as an option, only name and entities.
sure, appreciate that, but since the light group is what it is, a group, it is rather counter intuitive to not allow for the icon: to be a valid option. filed an issue to see what gives:
https://github.com/home-assistant/home-assistant/issues/22530
at least got all those ut of the way before adjusting the bigger issue of the Custom component Hue…
[Info] Installed homeassistant==0.90.2, check config now
[Error] Wrong config found!
Testing configuration at /tmp/config
Failed config
General Errors:
- Platform not found: binary_sensor.hue
- Platform not found: sensor.hue
- Platform not found: sensor.hue
- Platform not found: device_tracker.hue
Successful config (partial)
but that’s not for this thread, so Ill take that elsewhere , thanks for the assistance!
And that’s where I disagree… a light group is a light. That’s why it’s in the light domain, not the group domain.
Also similar problem here, someone has a solution for me? (HA 0.92.1 on a Pi)
The solution is provided in the Config Warning.
" Your configuration contains extra keys that the platform does not support. … Please find and remove the following. …
Remove username and all of exclude because these keys (options) are no longer supported in version 0.88+.