RaZberry 7 Z-Wave shield is UP and RUNNING with OH3.3 ZWave Binding (and connects to Z-Wave Device Devolo thermostat successfully)

…and the box new Devolo 014G0160 Room Thermostat could be integrated just as easily with RaZberry 7 Pro ZWave 700 shield. Sensortemperature, Setpointheating, Setpointcooling and BatteryLevel… all there… :+1:

FYI: Tested 2022-02-16 with:

  • openHAB 3.3.0-SNAPSHOT - Build #2733
  • Raspberry 3 Model B+
  • RaZberry 7 PRO shield (z-wave.me ) FW: 7.16.01.02 (2021-12-08)
  • Devolo (Danfoss) Radiator Control MT02650 / zwave_version: 1.0
  • Devolo (Danfoss) Room Thermostat 014G0160 / zwave_version: 1.0
  • Fibaro FGWP102 Metered Wall Plug Switch / zwave_version: 3.2

This is not correct. Z-Wave.Me RaZberry 7 has Static and Bridge mode. The simplest way to switch it to the Static mode (supported by the OH3) is to use it once in Z-Way (Z-Way will switch it to the Static mode). We can provide a simple bash command to do it without Z-Way if needed.

And of course, we suggest the new firmware from February (7.17) since it fixes many issues in the SiLabs SDK itself.

Sounds brilliant but Z-Wave.Me is sadly no longer something I will buy until current situation is resolved.

Sad to hear that. We (as the Z-Wave.Me team members) were never supporting the current regime, were battling against election falsifications, repressions, and militarism. And now we are a prisoner of both sanctions (by US, EU, and you personally) and our own government restricting our work in EU and US. You should do the opposite - support people you like to help them do a better world around you.

Anyway, Z-Wave.Me will continue to provide the best tools in the Z-Wave world and make homes peaceful, eco-friendly, and safe places for living.

1 Like

Replying about the backup & restore: yes, with Z-Way you can restore a 3rd or a 5th gen board on the 7th gen. We provide a smooth experience to our customers migrating to the new version.

1 Like

Hi PoltoS

I just migrated from a Razberry V2 to Razberry 7 Pro using export/import in Z-Way.
All devices where online in Openhab but performance was bad. After updating Firmware from 7.28 to 7.38 and activating the Long Range license, the controller goes even offline in Openhab after some time after reboot. (Z-Way Server still states that long range is not supportet/activated even if there is a tick under “Controller info”)

In general is there anything needed to do after controller upgrade on Z-Way / Openhab side?
In logfile I see entries like this while using new controller:

2024-09-11 23:10:46.992 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Exception during ZWave thread. 
java.lang.IllegalStateException: Queue full
	at java.util.AbstractQueue.add(AbstractQueue.java:98) ~[?:?]
	at java.util.concurrent.ArrayBlockingQueue.add(ArrayBlockingQueue.java:329) ~[?:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.processReceiveMessage(ZWaveTransactionManager.java:447) ~[bundleFile:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveController.incomingPacket(ZWaveController.java:1091) ~[bundleFile:?]
	at org.openhab.binding.zwave.handler.ZWaveControllerHandler.incomingMessage(ZWaveControllerHandler.java:464) ~[bundleFile:?]
	at org.openhab.binding.zwave.handler.ZWaveSerialHandler$ZWaveReceiveThread.run(ZWaveSerialHandler.java:427) [bundleFile:?]

I also see this for my Shelly Wave devices, but I see it also on the old controller and seems to be an issue with the Shelly Wave devices

2024-09-11 19:18:41.323 [WARN ] [.core.thing.binding.BaseThingHandler] - Attempt to apply invalid configuration 'Configuration[{key=config_75_2; type=BigDecimal; value=600}, {key=config_76_1; type=BigDecimal; value=1}, {key=binding_cmdrepollperiod; type=BigDecimal; value=2000.0}, {key=config_74_2; type=BigDecimal; value=0}, {key=config_85_1; type=BigDecimal; value=30}, {key=config_72_2; type=BigDecimal; value=95}, {key=config_73_1; type=BigDecimal; value=0}, {key=config_40_1; type=BigDecimal; value=50}, {key=config_71_1; type=BigDecimal; value=1}, {key=config_91_2; type=BigDecimal; value=12000}, {key=group_5; type=ListN; value=[]}, {key=config_80_1; type=BigDecimal; value=10}, {key=group_4; type=ListN; value=[]}, {key=group_7; type=ListN; value=[]}, {key=group_6; type=ListN; value=[]}, {key=group_1; type=ArrayList; value=[controller, controller]}, {key=group_3; type=ListN; value=[]}, {key=group_2; type=ListN; value=[]}, {key=config_1_1; type=BigDecimal; value=0}, {key=action_reinit; type=Boolean; value=false}, {key=config_3_1; type=BigDecimal; value=0}, {key=config_78_1; type=BigDecimal; value=3}, {key=config_5_1; type=BigDecimal; value=0}, {key=node_id; type=BigDecimal; value=63}]' on thing 'zwave:device:50600ad9:node63' blocked. This is most likely a bug: {group_1=Only 1 elements are allowed but 2 are provided.}

Reverting to old controller, everthing seems fine.
I will try to enable debug log while using new controller to hopefully get more information.

Update:
Yesterday I updated to Openhab 4.2.1 from 4.1.3 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. I hope it stays like this.

Update 2
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.