Why not using `homeassistant` container rather than `hassio`?

[sebi5361]

Why not using homeassistant rather than hassio? For me it worked straight out of the box by installing the container homeassistant/raspberrypi3-homeassistant:stable using portainer. I believe it wouldn't require a separate installation as for hassio in the IOT stack. Furthermore it doesn't depend on the two additional containers (supervisor + other). Additionally hassio allows to install extensions such as mosquitto using its web interface, which makes it weird as mosquitto might get duplicated when already installed in another container.

[Slyke]

I was the one who added HASSIO instead of Home Assistant (originally) in a PR here. I was following this: https://www.home-assistant.io/faq/ha-vs-hassio/

I have previously tried to get add-ons working on home assistant inside docker, but was unable. I believe the installation process has been fixed/upgraded since I submitted the PR a few weeks back.

[gcgarner]

Due to popular request i changed over the "proper" hassio install. I have no idea why the creators felt the need to make such a complicated 3 container system with a supervisor service. Seems needlessly over complicated to me.

I can have a look at pulling a straight homeassistant/xxx-homeassistant:stable in the future.

Hassio was a later addition to the project, the focus is on docker containers as services

[Slyke]

Totally agree there with you on the unnecessary complexity. Hoping that the Mozilla Things thing fixes it (along with the other QoL stuff that plagues Home Assistant, like only being able to make config changes in yaml files).

[gcgarner]

I can only assume that they had a very specific need to go with the service route. Otherwise they would have just used a docker-compose example and tagged the images like everyone else does. Pulling the image straight may work for most things but there may be a few gotchas somewhere

Their docker hub page is blank and has no instructions.

[sebi5361]

I believe hassio has to do with their ad hoc OS called HassOS. Homeassistant better fits on a normal linux OS. I had no trouble installing the corresponding docker container. I even made sure to share the container directory /ssl with the external directory /home/pi/IOTstack/volumes/letsencrypt/config/etc/letsencrypt to allow https access.

[leighhunter59]

I just attempted to install Home Assistant via ./menu.sh and received the following errors:

Err:1 http://muug.ca/mirror/raspbian/raspbian buster/main armhf libonig5 armhf 6.9.1-1 Connection failed [IP: 208.81.1.244 80] Get:2 http://muug.ca/mirror/raspbian/raspbian buster/main armhf libjq1 armhf 1.5+dfsg-2+b1 [119 kB] Fetched 106 kB in 1min 19s (1,349 B/s) E: Failed to fetch http://muug.ca/mirror/raspbian/raspbian/pool/main/libo/libonig/libonig5_6.9.1-1_armhf.deb Connection failed [IP: 208.81.1.244 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? [Error] Please install jq first

I looked at muug.ca/mirror/raspbian and did not see a raspbian subfolder. I have previously installed docker containers on different SD card however I was interested in leveraging your hard work (thank you) and use IOTstack if possible. I'm new to docker and home assistant and just creating a development sandbox on RPi 3 B for now. Please advise. Thank you in advance.

[gcgarner]

Hi @leighhunter59

I think it could just be that the mirror was down or just rebuilding because i can see it now. Can you try again and see it the installation goes through and let me know if the error goes away or changes?

[leighhunter59]

working now! bad timing, story of my life :-). Thank you. Merry Christmas

[JuanGrados]

Hi @gcgarner first of all thanks a lot for the project!

I was using before the stack that included the homeassistant container and it was working fine. Now that I updated the IoTstack project to also add Zigbee2MQTT I realised about this change to Hassio. Unfortunately I do not manage to get HA working, it is not clear to me from the instructions how to get it running.

I have just ran the Hassio script form the menu and I see the two "special" containers but I do not understand where is home assistant :S Could you add a more detailed instructions in the wiki or point me to some other resources?

Also I had before my HA exposed to the internet through DuckDNS and letsencrypt, is the new DNS container for that now?

I am confused :S

Thank you!!

[gcgarner]

Hi Juan

The team that designed the Hass.io container for some reason (which i have not looked into) created a service to manage Hassio. It installs the two special container you mentioned, the supervisor and dns. I can only assume that they have a very specific need to guarantee the operation as intended.

what is supposed to happen is I call their installer and it installs their two special container. The supervisor then downloads and installs home assistant.

Something important, your docker-compose.yml file will no longer have an entry for home-assistant, it is all managed via the special service and not part of the stack.

you can run docker ps to see which containers are running or just portainer. If your old home-assistant is running then the new one wont be able to start because the port 8123 will be in use.

You have some options

if you want to stay on your old setup and go back what you already have working: you can stop and disable the service and remove it with these instructions https://github.com/gcgarner/IOTstack/wiki/Home-Assistant#removal Then you can use the custom container function i added https://github.com/gcgarner/IOTstack/wiki/Custom to create a custom.txt file in the service folder with the name of your old container, i think its "hassio" , use the menu to build the stack again and the custom entry will be added to your docker-compose.yml file. You will be back to the old container

if you want to migrate to the new "official" hassio: make sure that your old hassio is not running check with docker ps or in portainer. stop it and run docker logs hassio_supervisor and see if it has any info in it. the supervisor should be responsible for downloading the new container you can run docker images -a to see if you have an image called something like homeassistant_raspberrypi that should be the new container and it should start automatically. If you get this far, let me know and I'll be able to help you further

On Thu, 9 Jan 2020 at 23:27, JuanGrados notifications@github.com wrote:

Hi @gcgarner https://github.com/gcgarner first of all thanks a lot for the project!

I was using before the stack that included the homeassistant container and it was working fine. Now that I updated the IoTstack project to also add Zigbee2MQTT I realised about this change to Hassio. Unfortunately I do not manage to get HA working, it is not clear to me from the instructions how to get it running.

I have just ran the Hassio script form the menu and I see the two "special" containers but I do not understand where is home assistant :S Could you add a more detailed instructions in the wiki or point me to some other resources?

Thank you!!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gcgarner/IOTstack/issues/86?email_source=notifications&email_token=ALECSYJLWIWPTGBWALPQJO3Q46JCJA5CNFSM4JPKLZDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIR27YY#issuecomment-572764131, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALECSYMAWHM7WPCMK6NAK7TQ46JCJANCNFSM4JPKLZDA .

[JuanGrados]

Hi @gcgarner thanks for the explanation.

FI had stopped the other HA container before the new installation but for some reason the supervisor didn't start the Hassio installation until I rebooted the raspberry. Now it is running, but it is not working the same... anyhow that's another topic.

Thanks for the help! Best