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.