Deprecating Core and Supervised installation methods, and 32-bit systems

Allwiner A20(ARMv7), there is no 64 bit

1 Like

I’m currently still running Debian Bookworm. If I upgrade to Trixie, will my Home Assistant Supervised still work? I know it won’t be supported, but I’m just curious if it will work?

I haven’t upgraded to Trixie yet but according to THIS statement HA Supervised will still work.

1 Like

Home assistant says there are two supported installation methods. I am currently on Supervised and love it. So if ā€œContainerizedā€ is a supported platform is there a page that lists all the containers and instructions to install them.

For example Z-Wave, Music Assistant to list a few.

It would be nice if the team put together a page pointing to at least the top 10 containers that people generally run with instructions on integrating them. That is called a supported installation IMHO.

As it stands ā€œContainerā€ seems not really supported. If I want to move to supported Container it seems the supported part is, well figure it out yourself.

I’m saying this in good faith that the Container part is weak at best and yes I realize ā€œAdd onsā€ are not supported on the feature matrix but that seems not helpfully when certain very popular add-ons such as Z-Wave are not DIRECTLY documented.

There would be no point in doing this because then they would just need to keep the instructions up to date. Meanwhile every project you mentioned has instructions on their README on how to install.

Ok great well how about a direct link in the Container install documentation to the top add on pages so users don’t have to go searching and possibly ending up on the wrong page. God knows searching these days doesn’t always provide great results.

That would be highly useful. Maybe there is a community page for this but I didn’t find one.

Just a little help here would be fantastic.

That doesn’t exist even in the community guides because no one wants to own it. It would be quite a bit of regular work and updating. Another reason it’s not in the documentation either.

2 Likes

I can’t see how hard it would be to list the top level projects.

Whisper
Piper
Z-WaveJS
Samba Share
Esphome
Music Assistant
Mosquito server
Matter server

I’m sure they are probably all github pages and as likely to change as the Home Assistant github page.

Here is the issue a search for ā€œWhisper docker imageā€ turns up about 3 or 4 different sites. A short time by the HA team listing the recommended site would be very helpful. Probably take about 30 minutes of work to add the correct links. For at least those. Possibly a few more but under 10 at least.

It would minimize forum traffic and be very helpful to the users.

1 Like

No, many are separate docs sites, for example Installation - Music Assistant

but really it shouldn’t be that difficult to search and find that, it is the first result when you search music assistant docker install instructions

And THAT is the exact problem.

Everyone wants things to be there for them while everyone also wants SOMEBODY ELSE to prep it, vet it, package it, support it etc.

Theres simply is NOT enough manpower to do these things. Even something that seems as simple as ā€˜well how hard can it be to just make a list?’

(see also, well, how hard can it be to just ask the teachers to… Same problem different soapbox)

Do you know how much it takes to even maintain ā€˜just a simple list?’

Support takes planning, checking, periodic review etc. To just list this it would take a significant part of someones time at least one day a month else it gets stale… And THEN people would scream it’s not up to date…

Addons are already packaging something (a docker container) and making them available in HA. Removing that need does not mean oh hey let’s keep doing the support work we’re trying to shed because we don’t have enough time to do it as it is.

Remember - every single ask takes cycles and if you want a better HA going forward you need tk shed some of the dead weight or be cursed to carry it forever.

11 Likes

Yep. We are 1 community guide or documentation pr away from that list being public. But people would rather be the project manager for home assistant instead of managing the product… if you catch my drift.

6 Likes

Then create a list and a pull request with the changes to the docs and offer to maintain in actively,

If it’s not accepted, create a community guide and maintain it actively.

This is open source and a large community.
Not everything has to (and can) be done by a few core developers.

Otherwise, looking at the HA addon repo and the community addon repo might give every user a good idea about popular addons.
That should be enough to find the repos / docker images for the services that were created for HAOS because it can’t run default docker containers.

Why does this post sound a little bit harsh?
Because your posts did as well and are very demanding.

Like mentioned above, this is a community and an open source project.
Everyone is welcome to contribute if something is missing (in his opinion).

Edit: Forgot to add the links:

A little bit Thy? :wink:

No sir. A LOT bit. I’ve lived through the nightmare of perpetual support and well I just need a. Or why don’t they…

You don’t want to be stuck there. Trust me.

1 Like

Great I’ll try figure out a pull request to add those links to Container info paragraph
so users can find them readily.

Thanks

2 Likes

If you where just looking for some kind of list of the known most used add-ons then look at opt-in Home Assistant analytics as that is the only statistics that has been collected → Add-ons | Home Assistant Analytics

PS: Yes I know that is a ā€œopt-inā€ collection only but if how else should you answer a question about ā€œtop projectsā€ when refering to addons?

1 Like

Exactly, but I’d reverse the sequence: Prove that you are able and willing to maintain this by making it a community guide and if successful, get it integrated.

2 Likes

Oh, brother! Here we go full-circle back to the accuracy of the opt-in analytics argument from the beginning of this thread!!! :roll_eyes:

Yes, that was a fun discussion. People who are not willing to share what they are using who are disgruntled that they are not counted in as users. Who are also making assumptions about how many non sharers use deprecated systems in the absense of any data.

6 Likes

Any opposition to that depreciation, regardless of the arguments used, was completely crushed by the many fanboys in this thread from the very beginning. It is pointless to even attempt to explain a different point of view without immediately being ridiculed.

So its done. Message friom supervisor: Unsupported system - Operating System