I used the installer script from GitHub - home-assistant/supervised-installer: Installer for a generic Linux system it creates a hassio network (172.30.32.0/23) for 5 containers - audio, cli, dns, observer and supervisor and it places multicast and homeasistant on the host network. I have a macvlan (10.23.23.0/24). I tried moving just the homeassitant container to the macvlan network, and it does not work. I’m sure there’s an easier way. Any ideas?
A supervised install is intended to be standalone. As in you run the installer on a vm or machine already running vanilla Debian and then let it manage the machine for you. Any additional containers added, setting changes, etc should be done via supervisor.
Trying to deploy supervisor into an existing docker setup alongside other containers which arent addons isn’t supported. You certainly can’t move the containers between networks, that definitely won’t work.
If you want to run home assistant in an existing docker setup alongside other containers you already have running you should use the container install method.
This eliminates the use of supervised Home Assistant, correct?
The container install method doesn’t include supervisor, correct. But supervisor’s job is to manage your system and in particular your docker deployment. Seems like you don’t want that since you already have a working docker deployment.
dont you lose out on addons though with the store? and perhaps external access?
Yes, but add-ons are just Docker containers with special sauce that lets you add and configure them from the HA UI. You’re able to install them as standalone containers/packages.
Remote access isn’t enabled by default in HA and also isn’t dependent on the Supervisor, so no, you wouldn’t lose the ability to set up remote access.
interesting, maybe I will go this route, that’s what I get for doing it how I did it last time…a few years ago. If that is really the only thing missing, but I feel like the last time I tried (several years ago) this I couldnt setup zigbee stuff or add google assistant, etc.
None of that is/was dependent on the Supervisor
1 Like
I will try out core and see If I can get everything going. Definitely going to have to figure out how to add a file editor for modifying yaml. Is there a good place to get started on adding the add ons manually?
It’s not “core” that you want.
“core” is not a docker install. It’s installed directly on the host OS.
there are 4 general types of installs: HA Core, HA Container, HA Supervised & HA OS.
the first two don’t implement a supervisor. The last three are dockerized installs.
so if you want docker but no supervisor you need to use the HA Container install method.
apologies, i meant ha container
No problem. I was just trying to head off any possible confusion later.
I mount my containers on an nfs share, so I’ll just use notepad from outside of docker to modify my yaml files. I think the big thing will be setting up zigbee and linking it to docker, etc. Hopefully there’s so good howto’s I can find in the forums. Thanks for the guidance!
I use WinSCP to access my config files and I use Notepad++ to edit them.
That’s pretty straight forward actually.
you just provide your zigbee controller as a device to your container.
I created persistent device paths as udev rules and then use those as devices in my docker run command.
I can post mine here if it helps.
so I do provide my usb zigbee controller to docker in the past, that shouldnt be a problem, but I wont be able to install zigbee2mqtt or anything like that in docker without the addon store, so i’m going to guess i’ll just spin up another container for that and then figure out how to make them communicate?
Yes, I assumed you were going to use ZHA for zigbee and that is already built-in to HA.
But if you are using zigbee2mqtt then you will just create a zigbee2mqtt docker container with the zigbee stick as a device to that container.
zigbee2mqtt uses mqtt as the interface between the zigbee2mqtt instance and HA.
So both need to be connected to your mqtt broker and mqtt discovery needs to be enabled.
If you don’t already have a broker you can also create one of those in docker as well.
1 Like
I mean Z2M is probably the easiest one. It was built for easy usage with any home automation platform and then an HA addon was added later. Just follow this. For the broker use this
2 Likes
I did use zha orginally, I had just read that z2m had a little better support, but I dont recall having issues wtih any of my devices in zha, perhaps i’ll switch back
Actually I would say that ZHA is easier.
It’s already built-in to HA. It doesn’t require a separate docker container for it to run and it doesn’t need mqtt so there is one less point of failure.
I’ve literally been using ZHA since pretty much the time I started using HA over 5 years ago and I only remember one time a LONG time ago that I had any issues with it and it was for a very short time. TBH, I don’t even remember what the problem was anymore.
Just to clarify I was thinking more “easiest addon to run standalone without supervisor”. Since its got a thorough docker guide and just a simple homeassistant config option to enable. I wasn’t comparing it to the other zigbee options, you’re right, zha is probably easier.
1 Like