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
home/not_home instead of Home/Away and Binary sensor only returning on/off #5683
Comments
Yes I do use custom cards elsewhere, but not on that view.. that view was actually done as a test to show the issue without custom cards I was surprised of the card-tool error too, but there is no custom-card, the one I posted it's literally the whole view file |
@thomasloven do you think that the card-tool might be miss-behaving somehow here? |
A panel view doesn't have an |
Can you check the logs of the backend for the |
Nothing related in the home-assistant.log |
Oh I think I got what you mean for backend.
|
Seeing the same in regular cards: https://community.home-assistant.io/t/0-109-new-integrations-page-and-weather-card-frontend-lost-weight/191097/238?u=mariusthvdb all devices show like this, on regular core cards, no custom cards involved:
|
Custom cards need updating: https://developers.home-assistant.io/blog/2020/04/23/frontend-translations Other than that I'm not able to reproduce this... |
could this be related:
since you speak of translations, it is the only thing I the logs I can see. rather a lot of it I must admit |
I saw that too now:
To provide the whole config bit, in the configuration.yaml I got this:
The dashboard file is:
And the view file:
|
yes, and I now see that all binary_sensors show lower on/off also. as OP . Must admit this is a HA instance in English, have another one in Dutch which seems so show alright. a 3d instance hasn't got device_trackers, and only 1 binary_sensor.updater which also shows correctly, in English. My production system is in trouble... 109.1 |
I have tried: All of them have the same issue to me. |
Can you guys post a list of your loaded integrations? Either from |
|
What is |
That is the problem, can you try disabling it? |
Sure |
Actually now from HACS it is named "var" instead of "variable". |
in my case it is https://github.com/rogro82/hass-variables, ill disable it for testing right now. |
That's it, using the latest version (which change variable.py into var/init.py) did it! Damn! |
@Mariusthvdb try to rename that variable folder inside custom_components to var and restart HA... probably it will fix yours too! |
why would you say that is the cause of the issue? apparently we use different integrations, could they both be the cause for the identical issue? |
If that works, I would open an issue to that project to change the name maybe |
I think it's the "variable" name causing HA to try to use that instead of an internal component. |
this is the only CC I have which is not in a dedicated folder, but directly in custom/components.. |
But the git repo you ponted to have it in a folder and the py file is init.py as new standard (from quite some time now, so that might be it |
yes, I had the init and the other files there, (it has been a long standing CC) and now moved those to /custom_components/var now I checked it again... ;-) why would this now all of a sudden cause havoc? @bramkragten , it has been functioning perfectly for almost 3 years, on each and every Ha version, and this error was never there. btw: solved! |
I have the feeling something has changed in the translation which uses something like either a variable.py file or something that caused HA to get confused. |
my CC variable stopped working now I have it in its dedicated folder.... |
Are you using the latest update? |
think this can be closed here, Ill sort my Variable stuff in the repo, while giving it another restart right now. Would like to understand though why this was the cause, and if we can use the /variable folder or not, cause if I use /var, the integration wont work/initialize... |
@SeLLeRoNe And, my device_trackers, and binary_sensors all show correctly now. so 1+1 = 3 ;-0 thanks Andrea and Bram! |
Before it was variable.py correct? |
hmm we are supposed to guard for that and still support single file custom components. Testing it now. |
Fix here home-assistant/core#35032 |
got to say, you're a magician. very impressed thx! |
Checklist
The problem
Since the update to 0.109.0 (up until 0.109.2) all my UI card that have to deal with binary sensor or "person" are returning "miss-translated" values.
All the "Home" fields are now showing as "home"
All the "Away" fields are now showing as "not_home"
The Door/Window binary sensor is showing on/off instead of open/closed
The Leak binary sensor is showing on/off insteadf of wet/dry (not sure if it was "wet")
And so on
Expected behavior
States in the UI should be show in a more "human friendly" way (as they were previous 0.109.0)
Steps to reproduce
Environment
State of relevant entities
Test View used:
Version 0.108.9
Version 0.109.2:
Problem-relevant configuration
Javascript errors shown in your browser console/inspector
Additional information
The text was updated successfully, but these errors were encountered: