For about two years i use OH.
Now 2.4 but it is for me more experimental installation as stable project. It is a little bit dirty with different “tests”)))
Now i want to install on a new raspi a new clean one and setup only things i need.
My setup consist of:
google assistant integration
zigbee2mqtt dongle and soft for it
zwave dongle and binding for it
mysql as persistance
Arduino with rf as rf signals receiver
broadlink with binding for sending rf and ir signals
fritzbox fr64 binding
And some other
So in this case i have a few questions:
Which version is now stable 2.4 or 2.5 good enought?
Is Raspi 4 (4Gb) supported now enought to have less problems or better old one 3+?
Is SSD have no problems on 4 (or 3+). I have heard about boot problems on 4 with SSD.
Is it a software (firmware) problem of booting from SSD, dont u know?
I ask because if i get pi4 now, will i be able to upgrade it to ssd when “ssd boot” update will be ready or it will be hardware modified?
It means that i can install same inage of OH on it?
For a Pi 4 you likely need to connect your Z-Wave & ZigBee USB sticks through a hub to the Pi. Its USB ports have hardware standards issues discovered after release.
I would generally recommend 2.5M4 with plans to move to the 2.5 release at the end of this year. There have been major architectural changes between 2.5M1 & the latest 2.5M4. You should do a fresh install but may be able to import a configuration backup/
I’m running sort of the same stack (zwave, zigbee, Chromecast etc) on my raspi4 with Openhab 2.5m2 and it works really well, no issues since I migrated from my raspi2 for over a month now. Don’t know anything about ssd boot but that’s interesting so gonna Google that;)
The API docs are working in M4.
I think the location changed after M1. It is under User Interface instead of binding. It might be easiest to uninstall the api docs before upgrading and then install again.
As is already mentioned, i have got pi4 and i have setup arduino and zigbee over usb without any hubs and without problems. Maybe because i have revision 1.1.
Maybe i will got this problems later, so how must this issues looks like - that device is not recognised or anything else?