Comment on I love Home Assistant, but...
hedgehog@ttrpg.network 10 months ago
Have you considered not using the Home Assistant OS? You don’t need to run it to use Home Assistant. You can instead set your host up with some other OS, like Debian, and then run Home Assistant in a docker container (or containers, plural) and run any other containers you want.
I’m not doing this myself so can’t speak to its limitations, but from what I’ve heard, if you’re familiar with Docker then it’s pretty straightforward.
A lot of apps use hard coded paths, so using a subdomain per app makes it much easier to use them all. Traefik has middleware, including stripPrefix, which allow you to strip a path prefix before forwarding the path to the app, though - have you tried that approach?
Strip prefix won’t work if the frontend expects to find paths at absolute locations. You would need to patch the html, css and js on the fly, which is somewhere between ugly and (almost) impossible.
I would also suggest to simply use custom (sub) domains. Especially in your intranet you can have whatever domains you want.
Strip prefix won’t work if the frontend expects to find paths at absolute locations. You would need to patch the html, css and js on the fly, which is somewhere between ugly and (almost) impossible.
This is what I’ve seen would be the only “feasible” way of getting HA to work behind a subpath, in my opinion this only works for very small application though (not something as complex as Home Assistant).
I’m (currently) on Raspberry Pi OS (as I need something that “just works”). Home Assistant is running in Docker like everything else.
A lot of apps use hard coded paths, so using a subdomain per app makes it much easier to use them all. Traefik has middleware, including stripPrefix, which allow you to strip a path prefix before forwarding the path to the app, though - have you tried that approach?
I should’ve mentioned this, but I’m using Nginx (I really enjoy the simplicity of just having to add a section to a file whenever I want to add something). Before running HAOS I was running RPIOS again and used Traefik, it worked (but felt like a lot more work to setup than just a plain Nginx setup).
This was going to be my suggestion. Just run home assistant as a Docker container, problem solved!
Still no subpaths, changing default authentication providers, and there can still be workarounds that feel hackish (I’ve used HA is a container before) the difference is that you’ll do less in Home Assistant, so you avoid them as much as possible.
MaggiWuerze@feddit.de 10 months ago
You can’t use add-ons when running HA as a docker container, which basically lobotomizes it.
Maximilious@kbin.social 10 months ago
Yes you can. It requires those docker containers to be installed and plugged into it on a stand alone system. This is exactly what HAOS is doing behind the scenes for is users and why many stick with it.
infeeeee@lemm.ee 10 months ago
Addons are just other containers, you can run them next to ha
peter@feddit.uk 10 months ago
You don’t get the direct integration then though, as far as I’m aware there’s no way to manually setup an addon
infeeeee@lemm.ee 10 months ago
What direct integration? You get a button on the UI, vs you do everything the way you want.
HAOS is intended for people who want everything to just work, without much fiddling. If you need something more, you need a docker based install. You can do everything there and even more, but you have to set it up manually.
vzq@lemmy.blahaj.zone 10 months ago
Add ons are just shitty packaging of other software. Just run the other software directly.
aksdb@lemmy.world 10 months ago
What kind of addons? I have HACS and it works fine.
JustEnoughDucks@feddit.nl 10 months ago
No backup solutions besides manual backing up and then setting up baremetal backing up
no configuration editor
HACS works, but no custom addons
manual configuration of esphome/nodered/mosquitto (I prefer this though)
I prefer docker because it is comfortable for me and I run all my services on one server, but it is indeed a bit less easy.
aksdb@lemmy.world 10 months ago
When I host multiple services, I need to back them up as well. I simply mount all data volumes of all containers into a unified location that gets backed up by kopia every hour.
Since the volume is directly on disk, I also didn’t have any problems editing configuration files.
The things I see listed as addons on the website are dedicated services anyway, that have images of their own you can easily spin up as containers.
I think if someone is advanced enough to want to run HASS on their own together with other stuff, they prefer to have more control anyway.
hai@lemmy.ml 10 months ago
Reading all of these replying I’m starting to think that maybe my problem was assuming that because add-ons are Docker container they should be treated as such.
hai@lemmy.ml 10 months ago
Yes and no. If you want a really simple setup HAOS add-ons are amazing, but as soon as you want to run something someone else hasn’t created a container for you’re stuck doing extra work than just writing a
Dockerfileordocker-compose. Plus, you can’t setup networks between them and (as mentioned in the original post) sharing drives can be hackish as well.The (grim) reason had I tried HAOS was because of the promise of something really simple that my family could figure out if something ever happened to me.
Celestus@lemm.ee 10 months ago
Home Assistant OS add-ons are usually just repackaged and pre-configured Docker containers. The only thing the add-ons system really gives you is convenience
sabreW4K3@lemmy.tf 10 months ago
There’s alternative installation methods.