search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.75k stars 29.53k forks source link

HA ัonfiguration check doesn't correspond to HA error check in log #51302

Open Spirituss opened 3 years ago

Spirituss commented 3 years ago

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[bot] commented 2 years ago

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 commented 2 years ago

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

github-actions[bot] commented 2 years ago

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 commented 2 years ago

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

Spirituss commented 2 years ago

Any update on this very annoying issue?

github-actions[bot] commented 2 years ago

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 commented 2 years ago

Nothing was changed. Still very illogical behaviour.

github-actions[bot] commented 2 years ago

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 commented 1 year ago

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

issue-triage-workflows[bot] commented 1 year ago

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 commented 1 year ago

The problem is still relevant

issue-triage-workflows[bot] commented 1 year ago

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 commented 1 year ago

Bump

issue-triage-workflows[bot] commented 10 months ago

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 commented 10 months ago

@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[bot] commented 7 months ago

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 commented 7 months ago

@AmadeusW The problem still exists.

issue-triage-workflows[bot] commented 4 months ago

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 commented 4 months ago

bump

issue-triage-workflows[bot] commented 1 month ago

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 commented 1 month ago

bump