[Feedback] Home Assistant

[mfelipec]

Description

Good afternoon. I really liked the project, but for me I still can't implement it in my home. One of the reasons is the basic Home Assistant as an installation option. My suggestion is to change this version of Home Assistant to the more complete version, with Home Assistant Supervisor, or Hass.io. In this way, it facilitates its use, including for installing addons, themes and other things necessary for greater control of residential devices. hassio docker hassio

Thanks for your attention and keep up the great work.

Additional Information

No response

[Dvalin21]

I second this!!!

[ggantn]

+1

[ETWang1991]

Transfer to APP request processing

[kerta1n]

There is a problem with this. Having supervisor run means that you will unnecessarily have two management portals. Home Assistant Supervisor is near complete deprecation, and if you like the style of the Supervisor, you're much better off using their buildroot OS (which does indeed support the same architectures that casaOS does). You run the risk of security vulnerabilities with two programs accessing the Docker socket, which also means that your system can be exploited with both Go and Python malware. Also, Supervisor (both by running the script AND on the devs' buildroot OS) does not allow you to run a popular container application called Portainer, as using Portainer with Supervisor is just as risky as running HA Supervisor and casaOS.

[Dvalin21]

Another alternative is have CasaOS come with the ability of creating a VM as well as dockers like proxmox so that things like HAOS can be installed yet controlled through CasaOS.

[interkelstar]

@mfelipec in fact why cannot you implement it in your own home though? which HAOS capabilities do you need that CasaOS cannot provide you? Essentially HAOS add-ons are just other docker images and installing docker containers is exactly the point of Casa OS. Most of the App-containers are already available on CasaOS App store, you don't need add-on to edit files since /config folder is mapped on the host system (so you just edit configs in CasaOS ui) and any other home automation addon (like esphome, mqtt, zigbeee) can be installed as docker containers in Casa OS using docker compose. HACS is also installable into container, they have instruction for that. You can even add sidepanel to home assistant UI cia simple section in configuration.yml if you want to.

[anlx-sw]

Feedback/user story from new CasaOS user: Today I learned about CasaOS and saw that homeassistant is one of the often mentioned use cases.

As i wanted to give homeassistant a try for some time and i need some additional docker addons i thought it would be a good idea to do so with CasaOS.. So i set up a linux server and installed CasaOS and the homeassistant app.

There is a specific use case for my intercom which is best done via homeassistant which was the driver to start with homeassistant. https://github.com/pergolafabio/Hikvision-Addons/blob/main/frigate/twowayaudio.with.frigate.md

I tried to follow the guidline and add the additional repositories. As there was no option to add repositories I started to troubleshoot and found out that there is no native way to add homeassistant-addons to the CasaOS homeassistant installation.

So I installed a haos-vm to be able to install the addons - although I would really like to use the more modern and faster CasaOS.. For a first time homeassistant and CasaOS user it is just to complex to install some additional docker containers and integrate them correctly with the homeassistant container without any feature built in (or any official guideline on how to do so) from CasaOS. So hopefully I soon find another usecase to try out CasaOS.

Later I found this github issue and thought it might be a good idea to contribute my feedback.

[interkelstar]

@anlx-sw it's very easy to install any custom docker container in CasaOS, you just click "+" button and from docker-sompose or socker run command install it. Any homeassistant addon is essentially just a docker container. Communication is done via ports, either for MQTT or any other app, so in order to integrate them, just conenct container to host network.

From what I see nothing can stop you from using frigate extestion, internally it uses docker container/addon as described here https://github.com/blakeblackshear/frigate-hass-addons/blob/main/frigate/config.yaml

So just adding custom docker app with image, version and ports from this config should work for you (MQTT is also a separate container and integrations are done via HACS as I see).

Also if you'd like to have homeassistant sidepanel entry, just add it to your configuration.yaml

[anlx-sw]

@interkelstar thanks for your answer.

the issue is not that it can't be done. If i have the time i can write my own docker compose files and docker images, set up communication and config and so on - i can work something out (even without CasaOS). The + button for a docker file would be lacking some basic options like to use a tempfs - so it will be CLI/Docker Compose scripts anyways for more complex scenarios.

MQTT i only found in the additional repositories for casaos - i saw no mqtt server in the base repositories. so again I would really have to know what i want to do and how to achieve this.

I don't want to critizise - i know it's open source and if i need something i can (if time and skill permits) contribute myself. I just wanted to point out the homeassistant user experience is much easier if I would be able to use addons - because i just could click the button and add the addon instead of a several hours trial and error until everything works out.

I don't look for a solution for my current problem. I just wanted to point out why the current situation is not good for less expirienced homeassistant users, and a native way to add homeassistant addon repositirories would be beneficial.

[marcboivin]

It might be a cardinal sin, but what about HAOS in a container? Same "security issue" and Christopher Nolan would probably want royalties, but you'd get the full HAOS experience add-on store integration, the whole 9 yards.

[bugmike25]

Transfer to APP request processing

@ETWang1991 was there any progress on this?