2022.7: A stunning performance

[cerebrate (Alistair Young)]

It’s not explicitly mentioned in the release notes, but just in case –

Anyone here know if the merged PR

Add mariadb-connector-c to Dockerfile by bdraco · Pull Request #247 · home-assistant/docker (github.com)

has made it into 2022.7.5?

[hassbrad]

Completely agree. History was my quick glance at everything I wanted to see using a carefully curated list in my config file. I’m not even sure what the history component does anymore if I also have to pick everything on the page itself? Then also clutter it up with all the items I’ve picked at the top?

I’ve started building history graphs to show on different dashboards to replace this, but then I also have to build a way to show different time frames to get the same functionality that the history page had.

[makai]

I don’t think so, latest release is from 17 days ago and this PR has been merged 5 days ago

[CaptTom (Tom)]

@hassbrad

I’ve started building history graphs to show on different dashboards to replace this, but then I also have to build a way to show different time frames to get the same functionality that the history page had.

This would be a nice FR for history_graph cards; the ability to select date/time ranges.

[VDRainer]

@hassbrad

I’ve started building history graphs to show on different dashboards to replace this, but then I also have to build a way to show different time frames to get the same functionality that the history page had.

Maybe take a look at my workaround.
I’m happy with it.

New History in 2022.7 - Multiple dynamic History URLs by groups

For a long time i used the History only for a few entities included in the history config. The new history panel is nice, but: - the selections are gone after restarts - the selections are gone after ‘Show more’ in a more-info dialog - i want to have multiple sets with selections You can bookmark the history in your browser, but then you have to edit them because they include timestamps. So here is my (hopefully only temporarily) Workaround. Create groups with the entities you want in the…

BTW: If anyone is able to template the start timestamp to the urls in the frontend

&start_date=2022-07-13T22:00:00.000Z

it will also be possible to open the sets with different time frames.

[hassbrad]

Agreed, please go here and vote if you would like to see this as well.

Add date/time ranges to History Graph Card

Add the ability to select a date/time range for the History Graph Card similar to the History Panel. Either by adding the functionality to the UI of the card itself or by adding template functionality to the hours_to_show field (or something similar). Since the 2022.7 update, the History Panel functionality has changed in such a way that I can not use it as an overall quick glance of all information about my system. It’s now a very manual process with many steps to show what you want, not a p…

Also, this is a somewhat workable solution for now.

Dynamically select the number of hours or sensors to show on a history graph or mini graph card

Hey everyone, Here’s a way to dynamically select the number of hours a history graph shows. This project relies 100% on the config-template-card, so all credits go to the developer. First, we create an input_select entity. input_select: hours_to_show: name: Hours to show options: - 24 - 12 - 4 - 2 - 48 - 72 initial: 24 Then the code for creating our card is the following: type: vertical-stack cards: - type: entities entities: …

[Viking]

After updating to 7.x I’m experiencing over and over again that starting HA partly fails in the sense that some integrations do not load and several custom dashboards fail to load. This only happens when there’s a section in the configuration.yaml file that has lines with incorrect indentations. Still, the Check configuration command always produce a Configuration Valid! output. It seems as if this check is no longer capable of catching incorrect indentations? I belive it used to be able to do that in earlier versions.
Info: I run 2022.7.5 in a docker container.

[nickrout]

You can see the state of the code in any release on github. Open any piece of code, click the dropdown that says “dev”, then “tags”, then the version you want to look at.

[teskanoo]

Thanks @stevemann, I’ll be giving that a go this weekend.

I’ve only once had to do a restore, and that was after trying out a new zigbee integration (which unfortunately clobbered all of my DeConz entity assignments)

In regards to updating HassOS, I was not aware that I would be able to get back to a pre-upgrade state with a restore of a full snapshot, I guess I was thinking that the full snapshot only contained “my configuration”, not HomeAssistant itself

Cheers

[teskanoo]

I got burned by that way back when…

Never realised that filenames needed to be unique in split config regardless of path

[Ildar_Gabdullin]

@teskanoo

Never realised that filenames needed to be unique in split config regardless of path

Created an issue:

Using packages: if some file has a same filename - it is ignored w/o any errors in Log. Please show an error in Log

[Fruitsmart]

Since this update, Alexa no longer runs for me.

api/alexa

[anatolyk (Anatoly)]

Got the same error. Did you find any solution ?

[aeozyalcin (Anil Ozyalcin)]

Hey all,

I just ran into a showstopper issue on my setup after updating from 7.4 to 7.5. What’s weird is, I didn’t run into this issue until I updated to 7.5. HTTPS/SSL has completely broken on my setup now, and I get the following error every time I try to connect to the HTTPS port on my HA server. The browser gives me an ERR_SSL_PROTOCOL_ERROR, and HA logs show:

Logger: aiohttp.server
Source: /usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py:405
First occurred: 5:19:48 PM (305 occurrences)
Last logged: 5:33:52 PM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 334, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 551, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message="Bad status line 'Invalid method encountered'"

Like I said, up until and including 7.4, I didn’t have this issue. It started when I updated to 7.5. Now reverting to any of my 7.x backups exhibit the same issue, and the only way out is to go back to my 6.7 backup…

My setup uses duckdns with let’s encrypt SSL cert. This has worked perfectly until today

[nickrout]

@aeozyalcin

7.4 to 7.5

do you mean 2022.7.4 and 2022.7.5. If so, say so please.

[aeozyalcin (Anil Ozyalcin)]

yes correct.

[afxefx (Jerry Sullivan)]

I had to upgrade from buster to bullseye to resolve this issue. Libavcodec-dev on buster doesn’t have the necessary files to properly build ha-av. This guide should help: Upgrading to Raspberry Pi OS Bullseye - Pi My Life Up

[aeozyalcin (Anil Ozyalcin)]

For other that run into this issue, how I ended up fixing the issue was by removing the browser_mod custom component. It appears that was causing the issue… Somehow…

[dbrunt (Daniel)]

@tom_l

Hamburger is three horizontal lines. Meatball is three vertical dots. It was in one of the recent release party videos.

Has anyone informed McDonalds or The Old Spaghetti Factory??

[tbut7633 (Tom Bworth)]

I saw your issues with REST sensors and matched with my long long loading time for my REST sensors gave me the idea to remove them. The result was I was no longer having memory leaks. Although the memory is higher overall, it is sustainable (60% of Rasp Pi 4 4GB) rather than leaking out and then crashing every 12-24hrs.