5 ms·
Its not prohibited here. What technical decisions are questionable?
by dfc 1y ago
Its not prohibited here. What technical decisions are questionable?
- billfor 1y agoYes it's prohibited I posted a few corrections (one positive , one negative) to his technical review, and it got downvoted, as will this probably....
- jolmg 1y agoI wouldn't consider downvotes to mean something is prohibited. I did in the past because that's what I limited myself to downvoting, but people just downvote what they don't like for whatever reason. All you can do is to not let it get to you.
- Bjartr 1y ago"prohihited" implies an official rule enforced by the community organizers. Downvotes are an expression of opinion by community members.
- traverseda 1y agoHome assistant supervisor is not very friendly. It's designed so that it must be kept up to date, and handles it's own auto-update features. It also won't run nicely in a docker container with some significant hacks. This means that the only deployment option if you want a complete home assistant install is to use their "Home Assistant OS" or specific debian versions. Generally it feels like they're making deploying it as hard as possible, doing stuff like checking if supervisor is running in a docker container and just not working if it is. This is presumably born out of frustrations with users deploying it incorrectly, but there really is no reason a supervisor based HA install can't run in a docker container. I've got a some private hacks doing just that, that I'm hesitant to post publicly in case they find some way to break it. No idea what the obsession is with keeping a full home assistant install from running in a container, but it's very strange. Trying to add more friction so they can sell more of their dedicated hardware? Their hardware is nice and stands on it's own, the only reason I don't use it is because I want to run on an old touch screen chromebook for very low power usage.
- jillyboel3 1y agoI've been running home assistant in docker for years. Just the `homeassistant/home-assistant` image. Don't need anything more. Best I can tell is that the supervisor is for people who just wanted a managed home assistant in a box setup at which point it's fair for the software to take over the system.
- traverseda 1y agoSupervisor is more or less required for some pretty critical add-ons.
- XorNot 1y agoSuch as? Only one that comes to mind is ESPHome, and I run that separately just fine.
- traverseda 1y agoNodeRED is a complete PITA to set up outside of supervisor. It requires extensions on both ends, and it passes the auth in a weird way.
- jillyboel3 1y agoI'm running NodeRED and ESPHome in their own docker containers, integrated with home assistant, just fine. Never used supervisor. It's been a few years since I set them up so I don't remember the details but that also means it wasn't anything notable. They've been stable since.
- traverseda 1y agoDo you have it embedded in the Home Assistant UI, and using HA user credentials?
- dzikimarian 1y ago
- watusername 1y agoAs one example, they (core contributors and founder) were, and still are, very heavy-handed regarding how you are allowed to install their software: https://news.ycombinator.com/item?id=27505277 https://news.ycombinator.com/item?id=27505277
- DaSHacka 1y agoWow, how pathetically obnoxious. I was going to purchase a Home Assistant Yellow for my homelab, glad to know I need to minimize my interaction with the project before I pulled the trigger. Will be sure to inform others using the project about this too, they deserve to know its a risk to rely on a project with such hostile core contributors. Truly "Open Source" in name only (OSINO?)