Any HW recommendation?

[mstormi (Markus Storm)]

@jimtng

@matt1

My take on it is that you should have a hardware backup as well as software backups. So I own two odroid n2+ as two full sets of hardware.

+1 LOVE THIS idea!

[…]

So that’s one benefit of using a cheaper SBC like a pi. Having two copies of the hardware isn’t too expensive.

This has always been one of the key ideas behind openHABian, now it’s also in the docs.

Ultimately however, it’s all about maximum service availability (i.e. your home working at all times).
That’s not the result of getting the best server hardware or by “cleverly” selecting SSD over SD/ZRAM.
Service availability is only ever the result of comprehensive system design and congenial operations that fit the hardware choice, see 2nd link in my previous post and and also the rationale behind explained here I already referred to earlier.

@jimtng

Running Raspberries off the internal SD card only may result in system instabilities as these memory cards can degrade quickly under openHAB’s use conditions (infamous ‘wearout’). When you choose to deploy openHABian, it’ll use the ZRAM feature to mitigate.

That might need to be rephrased a bit.

Probably, but people take away from reading that what they want to take anyway.
Either way, that’s the genuine docs, i.e. not part of openHABian docs. These also apply to e.g. generic Raspi OS on RPi 5. I know it’s not easy to understand the subtle differences and implications but if you read it like that it’s not an argument against (plain SD) Raspis but a strong argument in favor of openHABian in fact (as it provides ZRAM and SD mirroring).
Plus, that writing hasn’t been updated in a long time so yes time for an adequate update there, too.

@jimtng

Perhaps it’s also worth mentioning that javascript is slow to load (but not to execute) on an rpi, and such issue doesn’t exist on an amd64 architecture. It would probably save people’s time if they had the choice of using a server instead.

EDIT: There’s an update on that already.