zlacker

>>pictur+(OP)
Can someone explain the Home Assistant anecdote regarding JS and curl | sudo sh? Does the author mean Home Assistant isn't secure? Or that there's some issue with the front end of it? Or something else?

Because imo... that is the answer. We have seen so many stupid closed ecosystems of home automation stuff come and go, I dunno why you'd mess with anything else at this point. In fact I just got another email reminder that Google is turning off the old Works with Nest stack. Remember Nest? Yeah...

>>jmuguy+Ey
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).

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

>>move-o+fB
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.

>>neuros+XG2
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.