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

[Spirituss]

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

[github-actions]

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.

[Spirituss]

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

[github-actions]

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.

[Spirituss]

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

[Spirituss]

Any update on this very annoying issue?

[github-actions]

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.

[Spirituss]

Nothing was changed. Still very illogical behaviour.

[github-actions]

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.

[AmadeusW]

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

[issue-triage-workflows]

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.

[Spirituss]

The problem is still relevant

[issue-triage-workflows]

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.

[Spirituss]

Bump

[issue-triage-workflows]

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.

[Spirituss]

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

[issue-triage-workflows]

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.

[Spirituss]

@AmadeusW The problem still exists.

[issue-triage-workflows]

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.

[Spirituss]

bump

[issue-triage-workflows]

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.

[Spirituss]

bump

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