2022.7: A stunning performance

[Marsman]

@koying but the release note clearly mentions this:

Lastly, @pvizeli has been working hard to ship Home Assistant on Python 3.10! Which also brings quite a performance improvement. If you run the Home Assistant Operating System or use our container installation method, you will automatically get this; there is no need to do anything

So my understanding is that I will loose Bluetooth because I am running Home Assistant OS which will automatically start using Python 3.10 and thus break Bluetooth integrations.

[Mariusthvdb (Marius)]

just to plug the search bar feature request in History a bit, I’ve added the fr to only search in included entities…

Increase the width of the search bar on new history browser

if I could add to this selector in the search bar: make it show only the available entities, like history-explorer-card does. Usecase: many people have filters installed on History/recorder, and the current search box still shows all excluded entities. In a config of over 3500 entities, with say 200 included, this makes for a pretty bad user experience…

[Mariusthvdb (Marius)]

thanks Tom, a great thought indeed.

however, this is my veto setting:

veto_files:
  - ._*
  - .DS_Store
  - Thumbs.db
  - .Trashes

so noting to cause .svg files to be hidden. And I remember in the process it suddenly stopped working, so I did see them before. Let me find that spot in history…

[koying (Chris B)]

Indeed. I talk about the core installation method, so not HAOS

[Mariusthvdb (Marius)]

yes the BT demise is a pity indeed and a nasty side effect of the Python 3.1X speed.
Reason for me to keep 1 instance on 2022.6 and publish those trackers over Mqtt.
Ive not found a reliable and Off-the-Shelf solution to replace it yet.

[keithr59]

An issue has been raised which you may wish to subscribe to.

https://github.com/home-assistant/core/issues/74564

[dthomeassistant]

Even after replacing the .js file it is not working. Anything else I can try?

[Cadster]

@dthomeassistant Clear your cache, see here.

[evlo]

in settings > about.
yes.
No, I’m not sure it is updated, i did just run the two commands.

sudo docker pull homeassistant/home-assistant
sudo docker restart homeassistant

[maxshcherbina (Max)]

Don’t know if this has been suggested to you yet, but with these history changes you can save the state of your history panel as a URL. Opening that URL will always open up in that state.

Just as a stop gap solution.

[HurstOlds]

I have the same problem. Applied update and my entire system is borked. My mobile app on my phone won’t even authenticate/log in. I got my phone’s IP banned, lol. It’s so bad, and broke so many integrations, that I’m going to have to try to figure out how to roll back. I’ve never performed a roll back, is it complicated?

[CentralCommand (Mike)]

Please submit a feature request if you haven’t yet.

In the meantime, I think you can make your own dashboard with auto-entities. Something like this maybe?

type: custom:auto-entities
card:
  type: history-graph
  hours_to_show: 12
filter:
  include:
    <Move history.include filters here>
  exclude:
    <Move history.exclude filters here>

The syntax for include and exclude is different in auto entities so you’ll need some adjustment to your filters. But all options history supports are supported by this card. Then drop the card in a new dashboard in single-card panel mode and you’ve got your history dashboard back.

The only thing I’m not sure about is whether the history graph card works like the history panel and automatically excludes entities you listed which were excluded from recorder. If not then that would be a bummer since you’d have to move recorders filters over too and duplicate them.

But maybe a better workaround then listing 156 entities in the meantime?

[HA_fanatic]

I did check the dock and I tested it out as well as best as I could also looked at int and float as well that’s why I made the educated guess that when bool is used as a filter the value inside the parenthesis is maybe the default value but I don’t see it explicitly written out so hence why I came here to asked. I did do my due diligence.

[allenporter]

Hi, that is not correct unless you’ve disabled “my home assistant”? See discussion in Nest - Home Assistant – but i assume there you mean that you replace with your real hostname.

Just want to clarify that this advice is not correct in general, and most everyone should be using https://my.home-assistant.io/redirect/oauth as their redirect url.

[yonny24]

Just updated mine - No issues! Thanks guys!

Updated the Alexxit new release just before, made a backup (proxmox lxc container).
Got various custom components also - so far smooth sailing

[gazzaman2k (Gareth Williams)]

press yes and youll see itll ask for the update file location on your pc… clicking yes wont do anything to your zwave device this is not an auto update you need to manually find the files online to flash over zwave.

the zwave updater works great, i updated my 6 aeotec multisensor 6’s to latest 1.15 version as i have never updated them since i had them over 5 years ago. i used homeseer update files for them not the .exe that come in the downloads file extension type .hec

[Mariusthvdb (Marius)]

@GrizzlyAK

At a minimum, the drop-down list should at least be cognizant of whether the entity it is displaying to the user actually has any history to show if selected.

agreed. please also add to this FR, Increase the width of the search bar on new history browser - #4 by Mariusthvdb
which explicitly takes about the searchbar

[yonny24]

2022.7 is using a bit more memory than the previous version though. Well if its faster I can’t complain

[Edwin_D]

I don’t see memory use going up, but I do see processor use going down…

[koying (Chris B)]

@HA_fanatic

I did do my due diligence.

Really?

Templating