-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI template binary has wrong state in core #133967
Comments
Hey there @PhracturedBlue, @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) template documentation |
Can you show the full picture by also executing this query in the dev tools and by showing all entities with this label and its state? |
Facing the exact same issue. Preview shows correct state, pasting the template in devtools shows correct state, but the actual state is wrong - 'None' in my case. Could the usage of
Running 2025.1.0b6 right now. I believe this was working on 2024.12.x. |
yeah, in my case it certainly has to do with the label, more specifically, changing/adding it. My template got out of sync doing so, and required a restart (so not a reload of templates) before all was registered correctly again |
The problem
created in UI:
an showing it is 'Aan' (on) which is true, as there is an update entity being 'on'
however:
is displayed in the dev tools states, and as a consequence the conditions based on this dont evaluate correctly, nor does to show the right state-color/icon in the frontend cards
What version of Home Assistant Core has the issue?
2025.1.0b1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
template
Link to integration documentation on our website
https://www.home-assistant.io/integrations/template
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
filing this explicitly as a backend issue, because the UI Frontend config is correct, and the backend isnt
The text was updated successfully, but these errors were encountered: