Hi,
Here’s my experience, which lead to my “silly comment”. YMMV!
I used the original RaZberry for many years running on a RPi3 then RPi4.
The RPi3 worked fine, but on a RPi4, the Bluetooth radio shares the default console device, so remapping is required to use both a RaZberry and Bluetooth.
The next issue is updating firmware - the RaZberry could only be updated using the OS image from the manufacturer. This meant shutting down openHAB or HASS, creating a seperate image on a uSD card, booting, and then registration to get a login after flashing, and each time you checked for the next firmware update, your login had been deleted due to inactivity. Firmware updates were required back then to fix several mesh issues I had encountered.
The next issue is the form-factor. The RaZberry assumes installation onto “bare” pin headers on a RPi ONLY. If you use a RPi case, it likely fouls the PCB. In my case, a passive metal heat-block case needed me to manufacture a custom DIL pin header stand-off to raise the RaZberry above the case - which also was acting as a ground-plane and reducing the RF range.
Upgrading from a RaZberry to a USB device meant it could be removed and updated on ANY separate PC or Mac (slight shame as I prefer Linux). A standard case worked fine. Bluetooth just worked. If an upgrade is needed from a RPi to something else - the same radio works on any standard USB port…
…or so it should, if Aeotec hadn’t messed up the S5 USB interface .
If things have changed with the latest RaZberry - great. Certainly, an external antenna helps a lot.