2023.10: New looks and more tile card features!

mdino · October 10, 2023, 4:57am

Hi everyone,
I am using HA core on a Raspberry Pi running on Debian 11. After the upgrade from 2023.8.1 to 2023.10.1 I got this error message

ImportError: libssl.so.3: cannot open shared object file: No such file or directory

It looks like libssl.so.3 is only available in Debian 12 (bookworm) that has recently been released. Likely this version of libssl-dev could be installed on Debian 11 but only with a lot of effort (see HELP: Suddenly ImportError libssl.so.3: cannot open shared object file).
So it looks that the OS has to be upgraded in order to use the latest HA version. In the release notes it is not mentioned that there are dependencies.

I usually do frequent updates of HA, but it is not the first time in the past months that there are dependencies that can’t be fulfilled “out of the box” with an actual OS like Debian 11. I remember having an issue with a required ffmpeg version that wasn’t available from the repo and thus had to be manually compiled.
I think that Debian is one of the common distributions and would appreciate if more effort would be spent to maintain compatibility with actual distros.

francisp · October 10, 2023, 5:18am

Debian 12 was released on June 10th 2023. In the supervised architectural notes it is clearly stated:

github.com

home-assistant/architecture/blob/b85484512dd8f27338c6ae2ff28e9a7cf78abb2f/adr/0014-home-assistant-supervised.md

# 0014. Installation method: Home Assistant Supervised

Date: 2020-06-03

## Status

Accepted

## Context

Define a supported installation method as per [ADR-0012](https://github.com/home-assistant/architecture/blob/master/adr/0012-define-supported-installation-method.md).

## Decision

This installation method provides the full Home Assistant experience on a regular operating system. This means, all components from the Home Assistant method are used, except for the Home Assistant Operating System. This system will run the Home Assistant Supervisor. The Supervisor is not just an application, it is a full appliance that manages the whole system. It will clean up, repair or reset settings to default if they no longer match expected values.

By not using the Home Assistant Operating System, the user is responsible for making sure that all required components are installed and maintained. Required components and their versions will change over time. Home Assistant Supervised is provided as-is as a foundation for community supported do-it-yourself solutions. We only accept bug reports for issues that have been reproduced on a freshly installed, fully updated Debian with no additional packages.

This method is considered advanced and should only be used if one is an expert in managing a Linux operating system, Docker and networking.

This file has been truncated. show original

Debian Linux Debian 12 aka Bookworm (no derivatives)
and
Only the above-listed version of Debian Linux is supported for running this installation method. When a new major version of Debian is released, the previous major version is dropped, with a deprecation time of 4 months.
So the 4 months has passed, and Debian 11 is not supported anymore.

parautenbach · October 10, 2023, 5:24am

It should be in the main release notes, just like Python deprecations are, since Debian is the officially supported OS. Not everyone runs Supervised and needs to be concerned with its changes. This affects Core too. Perhaps this was an unintentional oversight.

PS: I’m already on Debian 12, so I’m not affected.

EDIT: Debian is in fact not a hard dependency for HA Core. I would still recommend it though.

jspanitz · October 10, 2023, 10:59am

I always laugh at people who laugh at people who wipe their ip addresses.

speculativefiction · October 10, 2023, 12:24pm

I’m having the same issue. Were you able to find a resolution?

bradich · October 10, 2023, 12:58pm

Nope. No idea what to do here.

coolhand · October 10, 2023, 4:10pm

I wanted to see if anyone else has been having any problems with the Synology integration since the 2023.10 release on October 4? I upgraded to 2023.10 on October 5, and then to 2023.10.1 on October 6. Ever since I upgraded to 2023.10, my Synology become ‘unknown’ at least once a day with no obvious reason. I haven’t had much time to troubleshoot, but I was hoping someone may have some idea what may be happening?

KennethLavrsen · October 10, 2023, 7:50pm

You are a bit unfair and unreasonable in my view. Yes we all create a backup when we upgrade HA itself or any addon. You have to actually unselect it. So most should be able to revert to a previous version some weeks back.

But each backup takes a significant space and it is fair to assume that we all only keep backups for a reasonable time. The last Mosquitto version that is verified to be stable is 2.0.11 and Home Assistant upgrade to an assumed unstable version back in March. You cannot expect that we all keep backups of everything for this long. We are in October. This is 7 months ago.

I think it is a fair request that the addon gets reverted back to a stable version until a fixed version is available. I am not speaking for myself as I have Mosquitto on a Debian 12 box. I just get upset when people gets treated unfair

Duke_box · October 10, 2023, 9:33pm

Harsh and unreasonable comment.
It is the devs fault that they forced an upgrade to an unsupported version of MQTT.

vvv850 · October 10, 2023, 10:17pm

Well said. I usually keep old updates off host but only because I forget about them.

The space is an issue on one hand and on the other, the speed needed to backup a 3GB restore point is also a problem. On a NUC i5 Gen11, 32GB RAM and 4 cores allocated, it takes 20 mins. It seems to be limited by using a single thread for this process.

tom_l · October 11, 2023, 1:04am

Sorry you feel that way. But I did explain what the very first section of the documentation (after installation) says you should be doing.

It is not unreasonable to keep the last backup of all your installed add-ons if you copy them elsewhere.

Also nine times out of ten an issue will show up right away, so you usually don’t even have to keep the backup that long.

Would it be nice if we had a versioning system that allowed downgrading of add-ons?

Yes. Yes it would. But we don’t. So please follow the advice in the documentation.

Tinkerer · October 11, 2023, 6:58am

No, it doesn’t

The only thing that affects Core is the Python deprecation, you can run it on any OS that you can get Python 3.11 (shortly 3.12) and all the required packages running.

parautenbach · October 11, 2023, 11:18am

Thanks for the correction. I reread the docs and see the Debian requirement is specific to HA Supervised. I somehow always understood it was true for HA Core too. That said, to get dependencies built and installed, it’s probably advised and easiest to use Debian. Since it is supported for HA Supervised, your likelihood to get things running will probably be best on Debian.

kenny · October 11, 2023, 1:10pm

Same issue +1, and I also went to Tile Card - Home Assistant but found nothing about this.

N5A · October 11, 2023, 10:22pm

Unfortunately The newest update does not have the fix for MyQ, while MyQ got a updated python, the issue for MyQ is related to a user-agent string. the Python update didn’t fix mine. We’ll have to see if the next update gets it. a full reboot did not correct it. Maybe I need to remove/add the integration again?

b0park · October 11, 2023, 11:33pm

Oh man I was excited for this update but it blew up my entire HA install. HASS never started, Supervisor wouldn’t start and all my integrations were toast. I’ll wait for some revisions. I highly suggest you take the time to do a full backup and maybe even a snapshot if you’ve got it in a VM so you can rollback easily.

jerrm · October 12, 2023, 12:53am

There is no currently working MyQ version at the moment. Chamberlain changed things again yesterday.

Other platforms that have historically worked even when HA was broken are also reported broken this time.

We’ll have to wait and see how this round of whack-a-mole goes.

Or do what I did and get a local solution.

nickrout · October 12, 2023, 2:31am

That hasn’t been anyone else’s experience. Logs? Logs?

CaptTom · October 12, 2023, 12:19pm

Seems a few people have this problem with every release, but usually only a few.

Obviously, it’s good advice to be prepared to restore if necessary. And be prepared to review (and post) logs. But I’m wondering if there’s another step we should all be doing.

I might start doing a full cold reboot before each update. HA runs 24/7 and I am often tinkering with it. Something could creep in which interferes with the next restart, whether I update or not. It would be helpful to know whether it’s the update, or something else, which caused the problem. Just a thought.

boheme61 · October 12, 2023, 12:37pm

I haven’t thought about it exactly like you, but i always check my core/supervisor logs before hitting install, so sometimes it has “inspired” me to reboot first, and if i still see “Error’s” (my default loglevel ), and it’s related to i.e 3rd-part (or other things, which i have not experienced problems from) i hit Install, and hope they are gone next time i check

EDIT: But your wording " Something could creep in " got my thinking/paranoid