Open patmolloy opened 3 years ago
Please see issue 194 of this repo which explains why this repo is dormant.
Then please see issue 106 of the active repo. That seems to have some solutions for this problem. I don't use hass.io myself so I can't speak to their efficacy but the suggestion by di-ai-wai towards the end about installing network-manager and apparmor makes sense.
When I checked my own RPi those were already installed. I have no memory of installing those packages by hand so the most logical explanation I can think of lies in how I started. Of the three Raspbian images on offer (which I will call "full", "intermediate", and "light"), I chose intermediate. My guess is that the "light" version lacks these two packages. If that rings a bell with how you built your own system we might finally have figured out why "hass.io not installing" keeps resurfacing as an issue.
@patmolloy further to my earlier comment, this just turned up on the Discord channel for IOTstack. It might be useful. For the record, apparmor-profiles are also installed on my RPi. The reference to the "lite" version seems to confirm my hypothesis as to the underlying cause.
@patmolloy - also posted this on Discord earlier today. I'm walking back from my comments about full vs intermediate vs lite image starting points. I don't think that's as important as I first thought.
Just a heads-up on the topic of Hass.io. The general consensus of Discord and Googling seems to be that a successful installation of Hass.io requires these dependencies before Docker is installed via IOTstack menu:
$ sudo apt install apparmor apparmor-profiles
$ sudo apt install network-manager
I can confirm that that sequence works. If those dependencies are satisfied before Docker is installed, Hass.io installs from the IOTstack menu without any problems.
However, getting to that point involved all manner of hair loss including (apparently) hung systems and much starting over with freshly-imaged SD cards. If anyone heard cursing coming from Down Under, it was probably me.
I eventually figured out what was going on. It seems that network-manager
randomly re-generates the MAC address for the WiFi interface. Three reboots in a row and ifconfig wlan0
returns these MACs:
92:12:11:2c:54:47
1a:ac:9b:85:69:a9
c6:80:4a:a8:b9:f2
Whether this is troublesome or not will depend on your environment. In my case, I have a combination of DHCP static assignments plus a local DNS (upstream of PiHole) gluing everything together. My setup assumes MAC address invariance so the network-manager
behaviour was downright confusing - until the penny finally dropped.
If you're going down the Hass.io path, I'd recommend an Ethernet cable and avoiding the WiFi interface until you are satisfied everything is working.
Had (and still have) issues with the installation of hass.io from IOTstack. After installing network-manager as Paraphraser mentioned above, my DHCP server from my Fritz.box get confused by the raspi WIFI/MAC-Adress hopping. Currently I try to install everthing with eth0 connected. But I'm not shure, what happens, if I disconnect it.
I see this .. culminating with the error [Error] No NetworkManager support on host.
Any ideas how to remedy?
TIA