Open Zocker1999NET opened 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.
Just ran into this myself. It's silently just ignored.
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.
Still valid i think
The problem
When using
!input
with a non-existent input for setting a variable in a blueprint (see example in YAML below), Home-Assistant does outright just skip reading the file any further without issuing any warnings.I even tried to set the log level from WARNING to INFO where no log appeared either.
This makes
Steps to reproduce:
What version of Home Assistant Core has the issue?
2023.3.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Blueprints
Link to integration documentation on our website
https://www.home-assistant.io/docs/blueprint/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response