88.0 complains about keys that are not supported , while they are?

efurban · February 21, 2019, 2:16pm

same issue here. “your configuration contains extra keys that the platform does not support”
and the line indicated was for pushover.

name: pushover_travis

anyone else seeing this warning message?

balloob · February 21, 2019, 4:26pm

Every time there is warning about a key that is missing but it is supposed to work, it is actually an existing bug that is surfacing. Report them and the can be fixed. When reporting, don’t just dump your logs in an issue and let us figure it out, because we won’t. Report on a per platform basis which keys are getting flagged.

Here is an example issue https://github.com/home-assistant/home-assistant/issues/21263

pergola.fabio · February 21, 2019, 4:39pm

Thx… I also opened an issue, but it’s closed now

Does it means they already did action?

Here , see below, or do I need to report again?

Dixey · February 21, 2019, 4:41pm

Dark sky key update_interval: for sensor works, for platform, HA complains.

petro · February 21, 2019, 5:08pm

Write it up as an issue on github, that’s what @balloob is refering to when he says ‘report it’.

123 · February 21, 2019, 5:36pm

Version 0.88 contains a Breaking Change concerning update_interval. It has been replaced by scan_interval. I mentioned it in a post here and, for the convenience of others, listed some of the affected components. DarkSky is one of them (the DarkSky Sensor’s documentation shows an entry for the scan_interval option but not for update_interval).

joopy · February 21, 2019, 7:14pm

I have the same: - platform: samsungtv when using mac:

edit:
fixed https://github.com/home-assistant/home-assistant/issues/21263

remo.78 · February 22, 2019, 5:43am

I updated Home Assistant to version 88.0
I have the following WARNING:
2019-02-22 05:22:04 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
Please remove [name]. (See /home/homeassistant/.homeassistant/configuration.yaml, line 161).

Line 161 - string “remote:”

Operating environment (Hass.io/Docker/Windows/etc.):
Home Assistant (Raspbian) Built using Python 3, Polymer

Component/platform:

remote:

platform: itach
name: Living room
host: 192.168.0.11
devices:
- name: TV
  connaddr: 3
  commands:
  - name: “ON”
    data: “0000 006D…”
  - name: “OFF”
    data: “0000 006D…”
- name: TV sound
  connaddr: 3
  commands:
  - name: “Up”
    data: “0000 006D…”
  - name: “Down”
    data: “0000 006D …”

aidbish · February 22, 2019, 6:18am

see this post further up. 88.0 complains about keys that are not supported , while they are?

pergola.fabio · February 22, 2019, 6:52am

88.1 is out, it already fixed 2 of my issues I started this thread with, but I reported also to github

remo.78 · February 22, 2019, 6:55am

I had a lot of errors in the string. For example platform: template

" initial: No Message"
I deleted these lines and the problem disappeared.

remo.78 · February 22, 2019, 7:41am

Problem solved

pergola.fabio · February 22, 2019, 7:44am

specialists on github

badabing · February 23, 2019, 1:53pm

I’m on 0.88.1 and am getting this warning

2019-02-23 08:41:50 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
Please remove [device].

I see no references in my config to [device] and have no idea where is this coming from.
Any suggestions on how to narrow it down?

No obvious issues with HA are observed.
Thanks

BB

jossie67 · February 23, 2019, 2:25pm

I’m still have the same issue’s

2019-02-23 15:22:08 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
Please remove [icon].  (See /config/config/binary_sensor.yaml, line 4).

This in line 1 till 11

#- platform: ring
- platform: ring
# Mobiel
# Jos Thuis
- platform: mqtt
  name: "Jos Thuis"
  icon: mdi:face
  state_topic: "location/josthuis"
  payload_on: "On"
  payload_off: "Off"
  device_class: occupancy

aidbish · February 23, 2019, 2:32pm

icon is not a valid option for mqtt binary sensor. you need to remove it

petro · February 23, 2019, 4:11pm

have you searched your config files for the word device using something like notepadd++?

badabing · February 23, 2019, 6:30pm

Thanks @petro,

have you searched your config files for the word device using something like notepadd++?

Yes I have, sorry if I wasn’t clear, this only showed up after upgrading to 0.88.x
Thanks
BB

JAS-MRS · February 24, 2019, 12:14am

I had the same warning and found it was caused by Dafang Hacks mqtt-autodiscovery.sh - it’s now been updated.
https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks/issues/952

badabing · February 24, 2019, 1:56pm

Thank you,
That was indeed my issue as well.

Have a good day.
BB