Need Help - Error calling Config validator

Configuration
1

I keep getting an error when i boot into HA

It says

"Failed to restart Home Assistant

The system cannot restart because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:24:22:42"

I dont know what this is, I tried re loading the YAML’s in the developer tools, if i do them individually they all pass, but if i try to reload all Yamls it fails.

Here are some of the error log entries

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:317
integration: Home Assistant WebSocket API ([documentation](https://www.home-assistant.io/integrations/websocket_api), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+websocket_api%22))
First occurred: 12:59:35 PM (10 occurrences)
Last logged: 2:24:22 PM

* [140100774678496] Error during service call to homeassistant.reload_all: Cannot quick reload all YAML configurations because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:12:2c:d4
* [140100884853632] Error during service call to homeassistant.reload_all: Cannot quick reload all YAML configurations because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:12:2c:d4
* [140100884853632] Error during service call to homeassistant.restart: The system cannot restart because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:12:2c:d4
* [140100884853632] Error during service call to homeassistant.restart: The system cannot restart because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:24:22:42

Logger: homeassistant.helpers.check_config
Source: helpers/check_config.py:217
First occurred: 12:59:05 PM (21 occurrences)
Last logged: 2:24:22 PM

Unexpected error validating config
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/check_config.py", line 217, in async_check_ha_config_file
    await config_validator.async_validate_config(hass, config)
  File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 328, in async_validate_config
    await _try_async_validate_config_item(hass, p_config)
  File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 306, in _try_async_validate_config_item
    return await _async_validate_config_item(hass, config, False, True)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 220, in _async_validate_config_item
    automation_config[CONF_TRIGGERS] = await async_validate_trigger_config(
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, validated_config[CONF_TRIGGERS]
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/trigger.py", line 462, in async_validate_trigger_config
    conf = await platform.async_validate_trigger_config(hass, conf)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/device_automation/trigger.py", line 61, in async_validate_trigger_config
    return await async_validate_device_automation_config(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, config, TRIGGER_SCHEMA, DeviceAutomationType.TRIGGER
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/device_automation/helpers.py", line 119, in async_validate_device_automation_config
    await getattr(platform, DYNAMIC_VALIDATOR[automation_type])(hass, config),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/device_trigger.py", line 51, in async_validate_trigger_config
    _, triggers = _get_device_trigger_data(hass, config[CONF_DEVICE_ID])
                  ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/device_trigger.py", line 34, in _get_device_trigger_data
    zha_device = async_get_zha_device_proxy(hass, device_id).device
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/helpers.py", line 1115, in async_get_zha_device_proxy
    return zha_gateway_proxy.device_proxies[ieee]
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
KeyError: d4:48:67:ff:fe:12:2c:d4

Logger: homeassistant.components.http.ban
Source: components/http/ban.py:136
integration: HTTP (documentation, issues)
First occurred: 12:22:06 PM (1 occurrence)
Last logged: 12:22:06 PM

Login attempt or request with invalid authentication from 10.0.0.62 (10.0.0.62). Requested URL: '/api/websocket'. (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36)

Logger: homeassistant.components.homeassistant
Source: components/homeassistant/__init__.py:218
integration: Home Assistant Core Integration (documentation, issues)
First occurred: 1:21:04 PM (9 occurrences)
Last logged: 2:24:22 PM

The system cannot restart because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:12:2c:d4
The system cannot restart because the configuration is not valid: Unexpected error calling config validator: d4:48:67:ff:fe:24:22:42
2

I would look at everything you edited since the last time you restarted.
configuration.yaml, automations, scripts, templates. anything. You syntax errored something. (most likely)

3

I didn’t edit anything. The power went out and the HA server restarted. That’s all

4

Well the error says otherwise.
The power dump could have corrupted something as well.
If you have a PI using an SD card the disk writes are so slow that pull the plug power outs regularly corrupt things and you may have to restore a backup.
The biggest chance is that you have a syntax error from a change weeks ago and this is the first it was restarted since then.

5

So I have already tried a back up a couple of times, the most recent was from a week ago when everything was working fine.

Which was the syntax error?

If I post the entire log could you pinpoint the problem for me?

6

That’s not something I’m interested in doing.

1 Like
7

This is all that is in my main configuration.yaml
This seems like there should be more than this?

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
8

Ok, Some progress, maybe

I deleted everything in the automations.yaml as that seemed to be one of the key problems.

As soon as i did that, all errors went to 0. Everything booted normally, I was able to restart.

I tried adding back the automations 1 by 1. Errors start back up immediately. so i deleted them all again and tried to add Automations back in manually

The first one i tried gets this error

##

New automation setup failed

Your new automation has saved, but waiting for it to setup has timed out. This could be due to errors parsing your configuration.yaml, please check the configuration in developer tools. Your automation will not be visible until this is corrected, and automations are reloaded. Changes to area, category, or labels were not saved and must be reapplied.

Went to developer tools and checked each individual yaml, all good
Tried the check all configuration, i get the same error back

Configuration errors

Unexpected error calling config validator: d4:48:67:ff:fe:24:22:42

Please help me out here

9

Your install is probably corrupted from the power outage.