I have been doing a lot of research into Home Assistant and how it works and am now in the stages of converting across my SmartThings ecosystem.
I have an existing Docker setup using Docker Compose to automate deployment with other services such as Deconz, Mosquitto, etc and at present, I am running the standard Home Assistant image.
Through further research, I have determined that I would probably need to be running HASS.IO as opposed to standard Home Assistant as I wish to integrate Node-RED and various other addons.
I understand that HASS.IO is essentially Dockerised Home Assistant with ancillary helper containers that allow for modular extension of Home Assistant.
Is there therefore a way to retrofit Home Assistant with the additional HASS.IO modules via Docker Compose?
I know that there is an install script that essentially deploys HASS.IO to docker but I cannot understand why I would need this if using Composeā¦?
Take a look at the script and what it does. You ācouldā replicate what it does without the need for a script. But in answer to your question, you could not use compose AND the script at the same time. You can use compose for all your other containers, and the script to install and set the service to run for HASSIO, or try to replicate what it does on your own using compose.
The script merely downloads the images, creates a service, and configures the containers with some bind mounts.
It doesnāt make any sense to do that. You just use the hassio to maintain home assistant and addins and can then still use docker-compose for other things outside home assistant. What is the attraction of using compose with hassio? You can just install Home Assistant in docker if you want (but no add-ons that way)
I currently run home assistant in a venv on a NUC and I am migrating to a NAS VM utilizing docker. I have tried both home assistant and Hassio and like Hassioās ability to manage add ons. The option to install Hassio via docker compose seems like it would simplify the install and I think it help on managing a traefik reverse proxy.
Using docker compose to run home assistant is certainly an option, but having hassio manage add-ons sure is nice.
My options are either, keep hassio and figure out how to reverse proxy it, while all my other containers accomplish this thru docker compose. Or just give up on Hassio and use documented methods to reverse proxy Home Assistant via Traefik using docker compose.
well itās pretty much childs play to install hassio as a generic linux install in docker and there are people using traefik as a reverse proxy.
I run Hassio in docker on my NUC but use Caddy as the reverse proxy and I let home assistant look after the homeassistant and addons updates but use docker compose for other containers.
You can do that, but the point of docker-compose (from what I gather) is having a central file that manages it all. So the attraction would be using docker-compose for its intended purpose of using it to manage all your docker containers (including hassio in this instance).
I am using it. But if Iām wrong in my assumption based on my own observations of its use feel free to enlighten me on why it ādoesnāt make sense to do thatā.
When you said āfrom what I gatherā that indicated you donāt use it (docker-compose)
So docker compose sets up or easily enables you to setup networks and config folders and ports inside and outside the container etcā¦ So what is the point of doing that when Hass.io itself manages all of that and does it without you needing to worry about doing that yourself. Hass.io will also update itself and so will your add-onsā¦ so exactly what do you consider is to be gained by adding in an extra level of complexity where it isnāt needed?
I canāt see that docker-compose adds anything to hass.ioā¦ It would make sense if you were using it to deploy other containers that require you to āmanuallyā set up and configure them.
The beauty of docker and docker-compose is you can use it however you want to. So I can use hass.io and all itās add-ons and let hass.io manage that and then use docker-compose to manage other containersā¦
Because someone may be using it in a different way to you, and it may be easier for them to write a single command that updates and restarts all of their docker containers without faffing about with hassio menus, whilst maintaining the āconvenienceā factor of hassio addons for their containers that are solely homeassistant oriented.
I canāt see how adding a few lines to a docker compose file and then integrating hassio in to your other routines for updates and maintenance is an extra level of complexity. In fact I would say it is the opposite. I can update all my other containers with one command, but have to go in to hassio and open a menu and press a button to do my hassio ones. Rubbish.
You canāt, but thatās your use case. Everyone has different needs and requirements.
Except if you tell us we canāt
Why bother to use hassio? Itās completely pointless. You can just use the native apps for all your devices. Why add an extra level of complexity?
