![]() I actually prefer this because it brings me freedom and control, versus being subject to whatever decision-of-the-week the Home Assistant people get into their heads.Īnd it's not just Home Assistant stuff. ![]() ![]() HACS installs just fine in the Home Assistant container, and you can just run containers for everything else, which is what I do on my Intel-based NAS. Which- is impressive, because I have a lot of devices and integrations. In less then 20 seconds after me clicking "Reboot", it is back and FULLY loaded. Rollbacks are effortless (Although- I have not yet had to do one.).Īnd- the 20 second reboot times, aren't an exaggeration. Best decision ever.īackups are done automatically through my existing tools. I decided to just run it on my existing infrastructure. Since- I have a LOT of infrastructure at my house, including many servers, 40 gigabit networking, and multiple terabytes of NVMe. ![]() Updating would frequently take between 10-30 minutes, and it was common for the update to be rolled back. Reliability was great- however, updates caused a ton of issues. ![]() I used to run it on a dedicated pi-4 by itself. Tbh- the reason I originally switched to running it in docker. (After the upgrade, I moved the SSD back to the 3B+ where it works alongside MariaDB and Mosquitto containers and all average about 2% CPU usage.) I understand that performance will depend on how much stuff is configured and I guess my installation is on the light side. 20s would be great but I'll settle for 10 minutes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |