And yet you have not posted for 7 years … Geez
I also have only orangepis and I will continue to operate them likely long after 2025.12.0. If you encounter a challenge feel free to make a public help post and at-mention me I would be happy to take a look. I don’t plan to stop using supervised and in my case I operate home assistant on three separate OPi hardware: Zero 2W, Zero 3W (this is best), and the OPi 5 plus 32GB (good for motionEye recording).
Without supervised, there is no path forward on orange pis for HA.
What this topic has shown me is that most supervised users don’t understand their installation either.
Perhaps tone down on the insults. Have you built software even remotely as complex as HA?
Much respect to the community for all the hard work on this project being used (for Free) by millions… As a Unix admin for 20 years now, I run several HA systems on Debian 12, Supervised. I apologize if I’ve misunderstood…
Am I correct to say, my Supervised systems will No Longer receive Update notifications (Front end - Core - Supervisor) after 2025.12 install?
Same here. Running one OPi3 on Armbian HA distro and other on OPiZ3 Debian desktop. Second one is really cool, it’s consuming only 1.7W energy. Hard to understand the reasons for giving up the HA supervised. Personally would agree to a reasonable usage fee instead of using/buying hardware with X times the power consumption.
yes, you are wrong to say that. Your system will receive update notifications for everything besides supervisor (as long as supervisor continues to function, which I believe was said there is no reason it would not continue to function)
Y’all need to calm down, it’s a free open source project, if you’re using an unsupported method, you’re on your own, simple as that. Some if you are wayyy too entitled for a project that people volunteer for. Also RTFM or blog post in this case, it’s perfectly clear IMHO.
Half of you whining are probably the same people that try to tell your IT department to switch to Linux and libre office for a corporate environment, and brag to everyone how you use some specialty configured Linux distro and made a custom kernel becausereasons
Get with the game or get out. It’s super easy to run a VM or a container, if for whatever reason that doesn’t work for you, fork HA and develop your own software.
Thanks to everyone who helps make HA what it is today, my house wouldn’t be the same.
Until today, we have been using a supported method. A method with advantages no other method can offer.
And when I started it was clear that you really shouldn’t choose that method. You’re complaining because you took an unnecessarily complicated way of using HA and you’re having to deal with it. Migrate and move on, software evolves gramps, it’s a free project so stop complaining.
In many cases this is not true, many people talk about how they installed separate software outside of HA in their supervised installation, which was stated in the HA documentation to make the installation be considered unsupported already. Many users were already running unsupported and did not realize it.
I can of course only speak for myself, but my installation at least consider itself to be both healthy and supported:
“Friskt” = “Healthy”
“Stöds” = “Supported”
Just because it says supported does not mean it always is.
If you install other software on the OS, then it is unsupported, even though the checks do not the other software.
That’s your opinion. My opinion is that I left HAOS because it wasn’t working for me (see my previous post in this thread) and chose a better path that was less complicated, worked better and offered far more options. One of four supported installation methods.
Then what’s with other posts in this thread advising to edit raspi config for loading additional hardware drivers? By this line of think merely suggesting anybody touch that file you’re now in “unsupported” camp. To be clear I don’t believe that. I think someone should be able to load additional drivers for USB dongles or whatever they are adding on to home assistant.
I’m not really trying to argue but this line of thinking isn’t productive. If you’re not harming home assistant it’s fine.
That being said I agree that calling out the devs as being bad is a bad thing to say. In general, a healthy project needs regular positive reinforcement.
You can. It’s free open source software.
Unsupported doesn’t mean you can’t do whatever you want. It means if you find a problem then the maintainers are not going to spend effort fixing it
In my experience, if you spend the effort to file a quality bug report, then it is on radar and at times fixed. Even better if one can submit patches.
“support”, even your definition of it, is arbitrary. You can still file bug reports and forum posts for help. It is an open source community and the community can continue to support whatever they want. Just like I mentioned to others they’re welcome to at-mention me in supervised-specific forum help posts.
What technically isn’t supported is if you try to install via an unsupported method and ask for help because there’s a bug in the install method itself. Unless someone in the community patches it, because core devs will not be patching it.
I have already forked the supervised project and intend to maintain it for myself; others are welcome to install from it and file bug reports there.
If you are running “unsupported” and you file a legitimate bug report that affects everyone I highly doubt the report will be rejected on the grounds that one isn’t operating HA the way devs want.
… this thread also shows that the community has changed significantly since this project launched: there is a tone of entitlement / aggression, which is a surprising contrast to the earlier years.
Good luck to the maintainers and admins. You continue to ship great stuff for your mission
thank you.
HA OS didn’t work on my mainboard, so the next best solution for me was to install the supervised Version, with the support of a really great youtube Tutorial.
What needs clarification to me is the following: As I am running now an unsupported installation method, does this mean I will stop receiving updates for my Home Assistant Setup? Or does this only matter in case of an installation from scratch?
That’s not clear for me, as of “don’t use this installation method in the future, because we don’t support it anymore” vs. “you used a now unsupported installation method, no more updates for you in the future”.
Seriously? I think half of this thread posts are about this.
And the subject was also touched a lot in the previous discussion thread,which is linked in the bottom of the first post here.
