Not related to this HA 2022.7, but it is a common UI issue.
Within a few last months we observed changes in Menu, moving a “Restart” button, etc.
I propose a feature which someone may find very useful - scrollbars in Dev tool → Template.
Please have a look.
I have a E1810 that is not working. I can’t get it to pair now and seems to can’t finish a reconfigure.
Please open a new github issues and provide py-spy How to install Py spy on a HA OS instance, please instruct - #44 by Mariusthvdb, MySQL slow query logs, and callgrind.out files from Profiler - Home Assistant
I have broken templates and can’t map an ‘unknown’ attribute to 0 in 2022.7 like I could in 2022.6.
The original template appears appears to be mapping unknown states to 0 with the map('int') filter. I am trying to get a count of batters that are low, unknown or unavailable.
{{ expand('group.aqara_batteries', 'group.shelly_batteries') | map(attribute='state') | map('int') | select('le', 0) | list | length }}
I have tried map(attribute='state', default=0) but that fails because the state exists but is unknown.
I have tried piping it to int(default=0) but that changes it from an array that exists to a scalar.
I have tried map('int(default=0)') but that is an invalid filter.
I have tried replace('unknown', '0') but that treats the input array as a string.
Don’t know if I found a bug or was exploiting an undocumented feature. Either case, I haven’t found a solution.
Wes.
{{ expand('group.aqara_batteries', 'group.shelly_batteries') | map(attribute='state') | map('int', 0) | select('le', 0) | list | length }}
Supply the int filter with an explicit default value (see how in the example I posted). Without it, when it encounters the unknown value it will no longer automatically supply a default but generate an error.
1 Like
Thanks. Didn’t think of that syntax.
Wes.
My Stunning performance is severely frustrated lately by daily
Anyone else seeing this more than before? No clue what it could be yet…
What’s more , it’s only happening on my system using Nabu Casa Cloud… my duckdns systems never see this.
On mobile_app that is.
A whole day trying to fix my ha after updating to 2022.7.3 !
Very frustrated! The fan of my argon one case not working anymore. Lot’s of errors…
Also had a look at all entities… It’s a complete mess! When you select ‘all entities’, a lot ‘old’ entities appear. I found out when I wanted to rename a few, and got errors… Deleted them in de files found in the .storage folder, but they keep coming back.
Performance? Probably because there’s a performance increase because of python 3.10.
I still have a slow startup time…and. Errors everywhere… Even the new 'music assistant ’ is giving errors.
So frustrated…
Yup, I agree, ive been spending two evenings in a row to get everything working again. Primarily BLE integrations are a mess now. I knew Miflora was going to be a issue, but Switchbot wasn’t on the list. I simply can’t get it to work, it just doensn’t. Got a Pi4 running with docker, added dbus and everything but just doesn’t. Finally managed to get things working by using switchbot-mqtt.
What auth method are you using? If you auth using trusted_networks, the mobile app will do this everytime you go on a public network. You must do the auth using username/password when setting up the app or it will do this.
yeah, aware of those restrictions. thats why I always use username/password. But, most surprisingly, this happens all the time when on my home network…
127.0.0.1 indicating it is from an integration inside HA maybe? why not simply use the phones IP address
Every time I’ve had those errors it has been fixed by logging out, then back in again on my wall tablet which runs the HA app.
yeah, well that can’t be can it, because that specific device gets banned, so we need to delete the ip-bans.yaml, and restart before being able to re-log in.nThat’s why it’s such an annoying bug.
Before, I used the trick to toggle my VPN and thus change ip-address, but somehow that doesnt work anymore. Seems the App is clever enough to realize it’s still the same device 
\\homeassistant\config.storage\core.entity_registry was corrupted twice as a result of an upgrade from 2022.6.7 to 2022.7.x (I think I tried .2 and .3, but can’t remember for sure). Replacing a version from a backup from 2022.6.7 fixed one issue, but I could not figure out from the logs what else might have gone wrong as this only fixed the issue temporarily. I’ve been holding off updates since then reason.
I’m planning to upgrade again to 2022.7.3 today or tonight my partner is not at home, so it’s a good moment for a maintenance window . I will post here how the update went.
If i switch to 4G or vice versa I am in with a different token on a different ip address and i have a script that deletes the ip_bans file and restarts HA so it’s pretty painless…
After upgrading from 2022.6 i am getting below in configuration check and not able to restart. Any one know how i can resolve this ?
Validate your configuration if you recently made some changes to it and want to make sure that it is all valid.
Configuration invalid!
‘<’ not supported between instances of ‘BinarySensorEntityDescription’ and ‘BinarySensorEntityDescription’
well, first off, Id be interested in that script.
I d hardly call that painless at all really, more of hacking yourself out of an issue that shouldn’t be there in the first place.
Which is ok-ish if you handle homeassistant all day like we do. The family though doesnt feel it that way.
They simply notice they’re being logged out all the time.
Might not be tied to this release altogether, but it certainly started with it now.
Hi all,
This was a great update, kudos for all the developers and people that helped to get this update come to life.
One of the new features of this update is the History filter and although no one can argue about it’s usefulness, some people like me say that it really would be nice and useful to have the option to see everything history has to offer like before the update.
If you are one of the people that misses the capability of seeing all the available history info please vote here View All Option And even if you are not one of this people and can’t live without the filter, please also vote because you will still have the filter capability and the option of seeing all if you want.
Regards,
Luis Sismeiro
2 Likes
Well, ALL history … i’m not sure why would be usefull to see hundreds, if not thousands of entities at the same time.
But, what WOULD be useful is use of wildecards. So, if i would enter in entity field, say, “sensor.garage%” i’d get all sensor starting with that. And with wildcards we’d also get those “all” possibility (just by entering %).
Ok, now we have option to select device. But that’s not always as usefull as my suggestion, since same pattern can be on quite many different devices, so adding them all would again result in “mini chaos”.
4 Likes