I can install and run it on a PI3B, but I would probably not be able to add that big a setup to it.
The issue here is that a PI3B is really limited on resources, so with each update that grow the requirement for resources to just run the HA core, less and less is available for the user’s own setup.
If your setup is too big, then it bootloops.
I would not call a PI3B a recommended way of running HA, when there is a note for that specific model saying that it is only ok to get started.
I think I’ve found a solution. As mentioned earlier, I’ve had issues with my RPI 3B, which kept restarting constantly. I found out that, somehow, it was my USB ZigBee device causing trouble when I installed HAOS 12.4 and up.
This issue now seems to be resolved for me; I have HAOS 13.2 installed.
As mentioned, I discovered that it had something to do with my USB, nothing to do with RAM usage, etc. I found out that a Raspberry Pi supports a function that enables the use of an alternative USB driver.
All I had to do was add a new line to the config.txt file containing:
dtoverlay=dwc2
The config.txt file can be found on the hassos-boot partition.
This forces your Raspberry Pi to use an alternative USB driver right from boot. Since then, I haven’t had any issues, and everything is running just as stably as before.
I hope this can help others besides me; I’ve struggled with this for a long time!
