core HA сonfiguration check doesn't correspond to HA error check in log

The problem

In some typical cases, such as when HA configuration has syntactic error or automation with no data parameter, standard configuration check tool doesn't show any error, while HA log shows it and stops the integrations with such errors. This is inconsistent behavour of the system. The expected behaviour is to shows all config check errors in HA config check tool (configurations - server controls - check configuration).

What is version of Home Assistant Core has the issue?

core-2021.5.1

What was the last working version of Home Assistant Core?

none

What type of installation are you running?

Home Assistant Container

Integration causing the issue

System tool

Link to integration documentation on our website

https://www.home-assistant.io/getting-started/configuration/

Example YAML snippet

automation:
  - alias: check
    trigger:
      platform: sun
    action:
      service: system_log.write
      data:
        message: "sunset"

Anything in the logs that might be useful for us?

2021-05-31 20:07:38 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: required key not provided @ data['event']. Got None. (See ?, line ?).

Additional information

No response

May 31 '21 17:05 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Sep 10 '21 09:09 github-actions[bot]

It is still the serious headache, because HA doesn't provide correct compilation information for some cases nevertheless it can.

Sep 10 '21 09:09 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Dec 12 '21 20:12 github-actions[bot]

Still is the case. I'm surprised that such a core problem has not been solved yet.

Dec 13 '21 04:12 Spirituss

Any update on this very annoying issue?

Jan 19 '22 10:01 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Apr 28 '22 11:04 github-actions[bot]

Nothing was changed. Still very illogical behaviour.

Apr 28 '22 15:04 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Aug 03 '22 16:08 github-actions[bot]

@Spirituss it seems that #77258 addresses this issue, should we link this issue to the PR?

Nov 10 '22 18:11 AmadeusW

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Apr 15 '23 20:04 issue-triage-workflows[bot]

The problem is still relevant

Apr 17 '23 07:04 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Jul 16 '23 09:07 issue-triage-workflows[bot]

Bump

Jul 16 '23 20:07 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Oct 14 '23 22:10 issue-triage-workflows[bot]

@Spirituss it seems that #77258 addresses this issue, should we link this issue to the PR? @AmadeusW I suppose this pr could solve the problem. So please link it.

Oct 15 '23 11:10 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Jan 13 '24 12:01 issue-triage-workflows[bot]

@AmadeusW The problem still exists.

Jan 13 '24 13:01 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Apr 12 '24 15:04 issue-triage-workflows[bot]

bump

Apr 12 '24 19:04 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Jul 15 '24 08:07 issue-triage-workflows[bot]

bump

Jul 15 '24 11:07 Spirituss

@AmadeusW @ Here is another case of such a problem:

The error from the log:

2024-10-07 21:25:42.732 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'cover_pack_open_window' could not be validated and has been disabled: required key not provided @ data['trigger'][0]['platform']. Got None

But the yaml config check return no errors.

Oct 08 '24 10:10 Spirituss

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Jan 23 '25 17:01 issue-triage-workflows[bot]

Still has not been solved. I'm sad.

Jan 23 '25 17:01 Spirituss

I'm not a regular dev on this project. I was only curious how config validation works, and I stumbled upon your issue report. Each component is responsible for its own configuration validation. This is for both the YAML check config, as well as startup configurations. They seem to usually be two different things. Although I don't have a full grasp of it yet, it seems that YAML configuration is being phased out somewhat. What I really wanted to say to you is that the original issue reported on this for the "automation" component may very well be resolved, and the nature of your issue report is too generic for anyone to work on. You might have more luck opening a report for each component that gives you this issue, then the team assigned to that component can look into it.

Mar 25 '25 22:03 fosterchuck

Oh hi there 👋

Going through our backlogs noticed this one. When this issue was reported, it would have been valid. Nowadays, this is no longer the case.

Configuration checking only looks for issues that may cause start-up issues. Issues with automations, for example, are provided by the automation integration itself at runtime. A single non-working integration doesn't stop the rest of Home Assistant and the automation to work.

This behavior has been refined over the past 2 years and is currently pretty much final.

This is also described in our UI nowadays:

I'm going to close this issue for that reason.

../Frenck

Apr 15 '25 20:04 frenck