I’m currently running Hass.io on a pi3b+ functioning as just a quiet little box humming away and not bothering anyone. It’s consistently at <20% cpu usage (typically 8%), memory is about 1/2 used of the 1G on board.
I have found the vast majority of response issues and less than perfect reliability was solved by moving from the telecom company supplied cheap wifi/router/modem to a bit more robust dual band router (read: don’t buy the cheapest out there). The issues have been network, not cpu.
I personally don’t see what an upgrade would buy me. I think I’m gunna pass on this one.
You can boot about any is except HassOs from ssd . Just not HassOs you can boot Rasbian Buster ( or Jessie on a pi 3) from ssd and then run HASS Io in a docker. All from ssd. I run Jessie from ssd on a pi 3B+ now , not even a ssd in the slot.!!
I’m looking forward to getting hass.io on a more powerfull raspberry like the 4gb version, I really like this little beast doing so much of my stuff.
As soon as it’s available, I’m going to convert the current 3b+ used for hass.io to a PBX instead
I’m not picking on you, ptmy, I just grabbed the first comment I saw.
There seems to be a bit of mixing up of terms in this thread (along with pretty much every other thread) about what HassIO, HassOS, and Home-Assistant actually are.
HassIO is ONLY the docker stack (specifically the supervisor container) for running Home Assistant. This gives you all the add-ons, etc.
HassIO runs on pretty much any system you can install docker on, including nearly every linux system including Ubuntu and Rasbian. If you install HassIO on Rasbian and boot Rasbian from a SSD, then you can run all of HassIO from a boot SSD.
However HassIO is not an operating system. You can’t flash HassIO to a SD card, and it wont run at all without an operating system under it.
HassOS is an entire (minimal) operating system and this is what you can flash to an SD card or disk. HassOS comes pre-built with Docker and HassIO installed.
It’s not any better that on the blog post even the dev seems to have mixed them up by talking about bringing HassIO support to the Pi4. If the Pi4 can run docker, I don’t see why they would need to do anything at all to run HassIO. They are likely talking about building support for running HassOS on it.
I can’t help you with the problem you’re experiencing (seems like a Raspbian driver issue) but just want to say that you can cut down that long-winded URL to just this: https://www.amazon.co.uk/Aeotec-Z-Stick-Z-Wave-create-gateway/dp/B00YETCNOE
The rest of that URL isn’t needed (except for Amazon’s own analytics).
PXE and USB Boot
Support for these additional bootmodes will be added in the future via optional bootloader updates. The current schedule is to release PXE boot first, then USB boot.
I got my definition based on description here: https://www.home-assistant.io/hassio/installation/. The title says “Installing HassIO.” You download the image that contains both the OS and docker image, which they’re calling HASSIO based on the title, then you burn the image to an SD card, and you’re done. Based on description here: https://github.com/home-assistant/hassos, I’m under the impression that HASSOS is just the OS without the docker image.
In summary, my interpretation based on the above is: HASSIO = HASSOS + HA docker imager, HASSIO = just the OS part of it.
I see how that conclusion was reasoned, and it makes sense. But is incorrect. HassIO is the Dockerized HA specifically including the HA Supervisor container. HassIO doesn’t require HassOS in any way; I run it in Ubuntu myself.
HassOS isnt distributed without Docker and HA preinstalled on it, so they’re inseparable as far as I know.
Straightening out that documentation on github to better clarify what’s what has been on my todo list for a while, so it’s not anyone’s fault for reading the unclear documentation and drawing assumptions from it.
HA is a fantastic product. But as with most fast-moving open source projects, there’s a ton of information on the internet. Many tutorials, documentations, and suggested solutions to problems are completely outdated and at times misleading. This is why I believe at least the official documentations have to be updated religiously to reflect current state of the product. Thank you for your efforts with this; I really appreciate it.