Help: config check throws error - no idea where to look

Configuration
1

Hi,

can someone help me point to where I could try to look for the issue? I have no idea which config file or entry is causing this error in the config files(s). Is it in the config.yaml, automations.yaml, etc? Or somewhere else completely?

Logger: homeassistant.components.websocket_api.http.connection
Source: components/hassio/__init__.py:705
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 7:59:39 PM (1 occurrences)
Last logged: 7:59:39 PM

[1640054664] The system cannot restart because the configuration is not valid: Unexpected error calling config validator: 'NoneType' object is not iterable
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 202, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1738, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1775, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 705, in async_handle_core_service
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Unexpected error calling config validator: 'NoneType' object is not iterable

Happy to share more info once I know what to share.

Thanks in advance.

2

Yeah, error messages are not always helpful.

If you are using yaml to edit your files, uncomment sections until you find the cause.
What did you change/add recently?

1 Like
3

I am having the same error (different service and files). I was attempting to get text to speech (tts) over Sonos working. I tried to go back and manually delete everything I had added, but still get the error when I “Check Configuration”.

In the screenshot from @skipper22hassio, can he modify core.py? If so where are those files located?

Thank you!

BensBar

4

I figured it out. I had a single “-” at the end of the automations file. So I am going back to my assumption that we do not touch the .py files. :grinning:

5

Hi, thanks for the “uncomment” hint. Seems so obvious.
I started with “not including” other files in the configuration.yaml and the error disappeared when I uncommented script: !include scripts.yaml. Turns out that I startet the script.yaml with script:, wich is one script: to many and indeed not iterable.

6

Thanks a million for this. I had same problem and was really stressed before I realized I also had a “-” at the end of the automations.yaml file.