#HAOS on RPI3B 1GB

1 messages · Page 1 of 1 (latest)

thick dome
#

Hey,
came up recently to HAOS when I was searching for suitable "framework" for building smart home, particularly controlling VRT via ZigBee and logging some sensors all around home atm.
I installed HAOS on 32 Gig mSDc (SanDisk HighEndurance A1, U3, V30) inserted it in my Raspberry Pi3B with 1Gig RAM and things get reeeealy bad.
It boots up almost 20 minutes and the system is almost unusable.
Every change I do in the web management to either configuration yamls, or settings or whatever else, causes restart (of supervisor? whole OS? - where to find this?) and the whole system becomes unresponsible for tens of minutes.
Either the webpage loads (but says that has no data received), or timeouts, or even refuses connection and so on...
After it loads up, there's no indices about crash or anything, no notification, no nothing.

Neither there's much about this in the logs, at least as far as I was able to found.
There are only some common issues with websockets, but nothing more, even no info 'bout restarting or whatever it is doing.

Is such behavior normal on this rather light HW, or is it something particularly screwed up on my installation?
The RPI3 should be "oficially" supported, so it should be powerfull enough to run it I guess?

short idol
#

1GB RAM may be the problem. I guess it spends most of the time paging. the minimum recommended seems to be 2GB, and if you want to install anything but a very few, very basic add-ons, get 4GB RAM.

#

I run mine on a pi 4 with 4gb ram and ssd (cheap chinese usb3 to sata cable).

thick dome
short idol
#

you could go out and look for second hand pi's with more ram. or other supported sbc's, nuc style pc's etc.

#

haos is pretty lightweight already. of course if all you need is to log data and communicate via zigbee you could probably write it up on some esp32 platform using arduino ide or similar

thick dome
#

and as that will need to be wired through separate ESP like embedded, I can code it on that one directly 🙂

short idol
#

esp32-h2 and esp32-c6 should both work fine as zigbee endpoints that can send data from your sensors as long as you can fit the sensor data into a defined zigbee endpoint profile. you could then maybe run something like zigbee2mqtt on your pi instead of a full homeassistant and send the logged data to a mosquitto instance running somewhere else. that could then log the data to influxdb. all of this could of course also run as add-ons in haos, but not with 1GB RAM I think. running just zigbee2mqtt should be fine.

thick dome
#

anyways, after some tweaking yesterday, I was able to get it to a state, where it runs quite stable, even with MQTT broker and MQTT.IO
it seems that biggest issues were caused by VS Code server, which seems quite understandable, now that I remember how resource expensive VSC is on my main PC 😆

#

boots in 2 minutes now and there were no random restarts since

short idol
#

yes, keep your integrations and add-ons to a minimum.