3 ms·

The author is referring to the officially recommended way to install home-assistant on a Linux box, which is just curl-ing and running an install script as root

The author is referring to the officially recommended way to install home-assistant on a Linux box, which is just curl-ing and running an install script as root. I totally get how that's off-putting, but the real recommended way to run home assistant is to install Home Assistant OS on dedicated hardware. Which also can be off-putting. Either way, it's my favourite software that I regularly interact with (unless you count Linux).

bluSCALE4 3y ago
This. This is what she meant. But the problem is, if you really like home automation and don't want to spend an arm and a leg buying just one spec, you'll have problems and will have to use multiple hubs.
move-on-by 3y ago
I just run it in a docker container along with zwave-js, which is also in a docker container.
- neurostimulant 3y ago
  My only issue with running HA with docker is when I restart the machine, the docker container starts before my ZigBee dongle shows up in /dev/, which means all ZigBee devices are not accessible until I restarted the container. I ended up patching the docker unit file to add 2 minutes delay, but the patch will be reverted next time docker updated. I wonder if there is a better way to fix this.
  - hiatus 3y ago
    Depending on your setup, you might be able to use docker-compose with depends on and a health check to start your containers in an order and to await the device availability.
radlad 3y ago
I don't think that's really fair - the recommended way to run Home Assistant is to run HA OS (on a VM or dedicated machine, like a Raspberry Pi), or to run it in a Docker container. The "Supervised" installation (i.e. installing Home Assistant on top of an existing Linux install) is doable, but not preferred. https://www.home-assistant.io/installation/ https://www.home-assistant.io/installation/
- katbyte 3y ago
  Iirc they explicitly say don’t / recommend against it. I mean I still did but it definitely isn’t the way most people will install it at all
  - raman325 3y ago
    We tried, but the community wanted to keep the installation method, so we kept it around.
    - katbyte 3y ago
      personally i did it because i like my servers to be debian & i wanted it to match all the other VMs i have running so thanks for keeping it around :)
phito 3y ago
Meanwhile on Windows, everyone gives admin rights to random installers without batting an eye.

bluSCALE4 3y ago

This. This is what she meant. But the problem is, if you really like home automation and don't want to spend an arm and a leg buying just one spec, you'll have problems and will have to use multiple hubs.

move-on-by 3y ago

I just run it in a docker container along with zwave-js, which is also in a docker container.

neurostimulant 3y ago
My only issue with running HA with docker is when I restart the machine, the docker container starts before my ZigBee dongle shows up in /dev/, which means all ZigBee devices are not accessible until I restarted the container. I ended up patching the docker unit file to add 2 minutes delay, but the patch will be reverted next time docker updated. I wonder if there is a better way to fix this.
- hiatus 3y ago
  Depending on your setup, you might be able to use docker-compose with depends on and a health check to start your containers in an order and to await the device availability.

radlad 3y ago

I don't think that's really fair - the recommended way to run Home Assistant is to run HA OS (on a VM or dedicated machine, like a Raspberry Pi), or to run it in a Docker container. The "Supervised" installation (i.e. installing Home Assistant on top of an existing Linux install) is doable, but not preferred. https://www.home-assistant.io/installation/ https://www.home-assistant.io/installation/

katbyte 3y ago
Iirc they explicitly say don’t / recommend against it. I mean I still did but it definitely isn’t the way most people will install it at all
- raman325 3y ago
  We tried, but the community wanted to keep the installation method, so we kept it around.
  - katbyte 3y ago
    personally i did it because i like my servers to be debian & i wanted it to match all the other VMs i have running so thanks for keeping it around :)

phito 3y ago

Meanwhile on Windows, everyone gives admin rights to random installers without batting an eye.