Hi all, first time posting, long time lurker.
During up coming holidays, I plan to move from Raspberry Pi 3 B (2016 model) to a brand new Raspberry Pi 4 (2019 4GB model). My pi3 setup consisted of Hassbian, NGINX, Deconz, pi-hole, etc, and a few of my own C programs.
Reason for not directly using HassIO image file on Pi 4 is because I had tried HassIO about 4-6 months ago and found SSH terminal too limited, it’s not a true Linux CLI. No GCC, I can’t run normal Linux commands and I’ve no access to underlying OS.
Because support for Hassbian has been dropped, also I have my own GCC compiled programs I’d like to run and I’m comfortable in Linux CLI. I have decided to start afresh with Raspbian image for Pi4 and install HassIO via Docker.
The Docker compose install method looks very tidy.
My questions are:
- Is this install method recommended? This method seems like no brainer approach for people comfortable with Linux CLI, but I see most people seems to stick with standard HassIO image on Pi.
- Any pitfalls with this method? Everything in HassIO will work with this method, correct? Stuff like update home assistant via UI, add-ons, snapshots.
- How will USB accessary work for Deconz add-on? I found this tutorial for standard HASSIO, how does abstracting another layer with Raspbian + Docker affect USB ID’s?
- How about Bluetooth trackers?
- What about System Monitor?
- I have 2 subnet, one for home, one for IoT devices. Pi 3 uses wired for home and general access, wireless for IoT subnet. Will both network be passed into the Docker instance?
Hope to do as much as possible within HassIO using addons and rely on snapshot feature. So any hardware/SD failure I’ll only need re-do initial docker setup, all home automation related will be restored via snapshot feature.
Finally, whole Docker concept is new to me. Can anyone recommend a crash cource on Docker, enough to understand what’s going on behind the scenes with HassIO and Supervisor?
Many thanks in advance.