Hardware:
Raspberry Pi 5
RaZberry Pro 7 Z-Wave Controller
Software:
OpenHAB 4.1.2
OS: Openhabian
Background:
Previously used RaZberry Pro 7 with a Raspberry Pi 4 on OpenHAB 3.x without issues.
I recently upgraded to a Raspberry Pi 5 and installed OpenHAB 4.1.2. However, my RaZberry Pro 7 Z-Wave controller is showing as offline with the status:
BRIDGE_OFFLINE
Controller is offline
Has anyone successfully used RaZberry Pro 7 with Raspberry Pi 5 and OpenHAB 4.1.2?
Are there additional configurations required for Raspberry Pi 5?
Is there a known issue with RaZberry Pro 7 and OpenHAB 4.1.2 on Raspberry Pi 5?
Any help or suggestions would be greatly appreciated!
Unfortunately I have never used the Razberry devices on Rpi 3, 4, or 5. I just hoped the linked thread might help. I use a Zooz USB dongle on my Rpi5. Maybe someone else will be able to help. Sorry
Just migrated from Razberry v2 (500 series) to Pro 7 on Raspberry 4 and OH 4.1.3 yesterday evening. Basically everything is working. Iām not sure about performance and reliability yet, but this can take some time until routing etc. is recalculated. Did an export/import using Z-Way Server.
Update
Because performance was still bad and bad reliability for battery devices, I upgraded Razberry 7 firmware from 7.28 to 7.38 and also applied the long range license. Firmware Upgrade was successfull, long range still state hardware not supportet even if license is applied.
However, since FW Upgrade the controller goes offline too after some time, I guess after 1-2 hours after reboot. Canāt see anything apart of Queue full. (Debug was not enabled at this time)
I wrote this earlier, but I think it is still accurate.
The 800 chip āLong Rangeā capability is misleading. Long Range Zsticks have dual frequency ranges. One set of frequencies are for āclassicā Zwave and have the same range as 700 chip (and 500 chip) controllers. Long Range uses a separate set of frequencies with a spread spectrum technology that allows for higher power. I found this on the Silabs website and the summary below is extracted from my understanding. To achieve the higher power Long Range capability, the device must be included with the following requirements (these could change over time?):
1) Long Range nodes have 12 bit addresses (vs classic 8 bit) starting at 256. This would require a major refactoring on the binding.
2) Long Range inclusion requires Smart Start. This is not currently coded into the OH Zwave binding.
3) Long Range inclusion requires S2 security. The OH Zwave binding currently only supports S0 security.
4) Long Range is currently only permitted in North America.
5) Long Range nodes only ātalkā to the controller (no mesh) so the binding needs to relay messages to other nodes (No Association Group messages).
6) Without all the Long Range requirements nodes will automatically be included in classic mode.
Yes, I remember this part in the docs. If it is only permitted in North America it is obvious why even z-way-server says it is not supported. The main goal of Razberry 7 Pro was to get more devices in direct range of controller with the external antenna.
However, long range or not, the Razberry 7 is not working correctly. I will try to get debug logs.
Yesterday I updated to Openhab 4.2.1 successfully and today morning I switched to the Razberry 7 pro again. For some reason it looks much better now, after 1-2 hours the network seem to be fast and reliable.
Update
Razberry 7 still working great on OH 4.2.1 and RPi4. Everything seems to be fine now. Nearly all devices now in direct range to controller.
FTR - Any binding can be set to debug from the UI setting page (on the right) and the ZW developer created a debug viewer for screening (green good, yellow-caution, red-not so good) here Z-Wave Log Viewer (opensmarthouse.org). (in case problems arise)
I again got problems. Sometimes Z-Wave commands are lost or delayed (Message timeout, send failed, Thing State offline etc.). I decided to go back to Razberry V2 because I nearly never had such issues with this board.
