Warning about keys that are not supported for Fully Kiosk Custom Component

I have raised this elsewhere but have been suggested to give it its own thread…


I am having similar issues with a custom component in the new version of Home assistant.
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):

Operating environment (Hass.io/Docker/Windows/etc.)::slight_smile:


Link to component: https://github.com/daemondazz/homeassistant-displays

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
  - platform: fully_kiosk
    name: Dining Tablet
    host: ''
    password: !secret http_password
  - platform: fully_kiosk
    name: Lobby Tablet
    host: ''
    password: !secret http_password
  - platform: fully_kiosk
    name: TV Tablet
    host: ''
    password: !secret http_password
  - platform: fully_kiosk
    name: 'Nexus 10 Tablet'
    host: ''
    password: !secret http_password

Fully Kiosk definitely uses the ‘name’ ‘host’ and ‘password’.
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.

Any help people are able to give as to what needs changing would be much appreciated

Many thanks

it’s a custom component. The structure for custom_components has changed in 0.88 so you need to review the folder structure.
New structure is
[config]/custom_components/[component_name]/component.py where component is a valid HA component name, like binary_sensor | device_tracker etc

I personally use https://github.com/thomasloven/lovelace-fullykiosk for Kiosk

Hi @lolouk44,

Thanks for your comment. I’m aware of the folder issues but this is a different issue to that.
I have noticed some other components for fully kiosk but like your above link they are all related to using the lovelace interface.
I’m currently using HADashboard on my fully kiosk tablets and want to stick with that for the moment as it seems to work very well.
I should have also mentioned the fully kiosk custom component is working perfectly it is just the constant warnings a per my original post that is the problem.

Hi all,

I have also a similar issue:

Error loading custom_components.fully_kiosk.display. Make sure all dependencies are installed

Traceback (most recent call last): File “/usr/local/lib/python3.7/site-packages/homeassistant/loader.py”, line 166, in _load_file module = importlib.import_module(path) File “/usr/local/lib/python3.7/importlib/init.py”, line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File “<frozen importlib._bootstrap>”, line 1006, in _gcd_import File “<frozen importlib._bootstrap>”, line 983, in _find_and_load File “<frozen importlib._bootstrap>”, line 967, in _find_and_load_unlocked File “<frozen importlib._bootstrap>”, line 677, in _load_unlocked File “<frozen importlib._bootstrap_external>”, line 728, in exec_module File “<frozen importlib._bootstrap>”, line 219, in _call_with_frames_removed File “/config/custom_components/fully_kiosk/display.py”, line 17, in <module> from . import ( ImportError: cannot import name ‘DisplayDevice’ from ‘custom_components.fully_kiosk’ (unknown location)

Seems it is NOT only a folder structure issue (I moved the component as it needed to be), but more something to change in the code.

I’ve opened a simple PR to fix this warning, hopefully @daemondazz will review it soon!

Many thanks to all that have assisted with this.
@daemondazz has now corrected the issue with the unsupported key and also the issue with the file/folder structure. this seems to have corrected both issues.
If anyone else comes across this tread with the same issues you can find the new custom component files on @daemondazz github here: https://github.com/daemondazz/homeassistant-displays

I had this working before, now after updating to 0.90 and installing the latest files i get this error when i try to call turn_off or turn_on.

2019-03-30 12:05:44 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/app/homeassistant/core.py”, line 1138, in async_call
self._execute_service(handler, service_call))
File “/usr/src/app/homeassistant/core.py”, line 1160, in _execute_service
await handler.func(service_call)
File “/config/custom_components/display/init.py”, line 82, in async_handle_display_service
for display in target_displays:
TypeError: ‘coroutine’ object is not iterable

Any ideas?

I’ve got the same. I’ve looked into it a bit, but don’t know what the cause is yet.

I opened a ticket here: https://github.com/daemondazz/homeassistant-displays/issues/10

Yes, i have same issue but everything else seems to work correctly

The coroutine error has been corrected. Please see the github page for latest code.

I made the updates from your github page for the latest code and now I am getting this error

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].

I assumed this was fixed here - > https://github.com/daemondazz/homeassistant-displays/pull/8

Any ideas on why I am getting this now? (I am on ver 0.91.3)