Nabu casa doesn’t own home assistant, it’s owned by a non profit controlled by a group of open source projects. It can’t be sold without the open home foundation agreeing to sell it.
7 Likes
Was just getting back to installing Frigate and I noticed this (emphasis is mine):
Frigate is a Docker container that can be run on any Docker host including as a HassOS Addon. Note that a Home Assistant Addon is not the same thing as the integration. The integration is required to integrate Frigate into Home Assistant.
Does this mean any add-on can be manually run as a docker container, separately of HAOS?
I must be missing something because this seems like The Way.
No that’s not what that means. That means frigate is available elsewhere as a docker container separate from HAOS. The addon is a special case docker container to make it easier to run in HAOS.
The takeaway is… There’s a docker container out there somewhere for X - run that if not in haos and don’t have addons.
1 Like
The one thing I’ve learned from this topic is that the majority* of Supervised users don’t read posts or summaries before they reply.
Not as many Core users has complained either.
*Analytics may not be accurate.
6 Likes
Obviously!
You do not need the addon to run frigate.
2 Likes
This! I confess I haven’t ever thought of opting into analytics that way, but it’s just like politics: If you don’t vote, don’t grouse. Voting is the price you pay to have the right to complain!
6 Likes
A rather oblique comparison and the same as comparing apples with oranges.
What does the disclosure of personal data to a software manufacturer have to do with the choice of a political system and the resulting consequences?
Especially when the software manufacturer’s motto is full-bodied announced as “Open source […] that puts local control and privacy first”?
This thread has certainly taken a strange turn where well-intentioned criticism has given way to attacks, accusations and opinion mongering based on personal preferences.
1 Like
Afraid I have to agree with a couple of the most recent posts by a.o. @Tamsy and @rbaker91
we’ve come here, mostly surprised, and hoped for a conversation yet we’re greeted with a very adversary response.
We’re all aware that supervised is a conscious choice to make, and quite a few of its users are knowingly running it in a way that implies that they are not entitled to ‘support’. It’s the response and the fact that information on how to use it has disappeared that comes across as - dare I say it - almost aggressive.
and the crux of the matter? That it’s avoidable. If the code itself remains, just continue as is and make clear which support is provided and which isn’t. Nobody will object…
2 Likes
It’s absolutely apples and oranges. I think the analogy holds though - you give anonymized input to influence further decision making.
And nobody forces you to disclose anything. But even though it was not the deciding factor in this case, it would be foolish to think that no decisions are made based on usage numbers (e.g. handling of integrations that report 0 users)
I see no attacks, but on the other hand a lot of entitlement from users towards a free software, where a lot of development is still done by volunteers.
That’s just not true. People (in general) don’t read. It would just be a source of confusion, if it remains on the official website. This thread has shown that a lot of people already were not aware that they were running unsupported scenarios. If it’s community supported it needs to move to community sites, like custom integrations do it as well.
5 Likes
Im running Supervised on debian on vmware windows 11, because is Stable and i hardend the system my way. Tried 3 times the HA os and after few days the system corrupted and i had to reinstall all from scratch, the backups didnt work as it should two years ago. I hope you will support supervised in the future…
Will we lose support only for the supervised system or the Home Assistant Core and addons updates also??
Sad to see this…
I feel exactly the same. Been running supervised on Deb 12. I have Frigate running in Docker as well on the same box. I need both of these, so I am feeling forced to run 2 separate PC’s. Tried Proxmox, after days I have given up trying to get HA and frigate to co-exist… I hope the “powers to be” reconsider supporting Supervised. I am also another person who opted out of analytics…
Folks need to inventory what they are getting out of the project and put at least that much back into it. When they don’t, it withers.
Think of it like a community park. When people do things like take home their trash instead of fill up a can, the park costs less to operate. Everything adds up.
Unlike a community park, there is no “city budget” to pay for HA development.
3 Likes
If you already have Docker, why not the HA Container version?
Maybe because container does not have addon updates? And complicates things further?
For Proxmox I use:
- HAOS in a seperate VM for HA and all the addons I want to use easily
- Second VM for Docker. Here I run all all containers unrelated to HA (like Scrypted NVR, which is an alternative to Frigate)
- Other services or setups that are not available for docker or I don’t want to run in docker for whatever reason are LXC containers.
Used it this way since I started with HA and never regretted.
You just have to add enough RAM to the machine, so it’s not a problem to apply enough fixed memory to two large VMs, as you loose the benefit of the shared resources compared to sticking only with one of the 3 virtualization types in one large Host OS.
I upgraded to 32GB when I moved to HA. HA and Docker VM get each 10GB of ram, the rest can be shared by the Proxmox Host and the LXC containers.
3 Likes
But if someone is already running Frigate in a Docker container, they’re already happy to maintain this (Frigate is available as an add-on for HAOS, yet that’s not what they’re running, so it didn’t look like update functionality was too important).
2 Likes
I completely agree with you.It seems as Homeassistant wants to become a paid home automation solution in the future.
1 Like
It seems to me that this move is exactly the other way around. With four options to support, their resources were being drained. They are withdrawing support for two lower utilized options with higher support costs so that they do not have to charge. I am hoping this will result in more development of the core product.
9 Likes