[SOLVED] Null pointer exception after switching zigbee device

Hi all,

testing a new zigbee two channel relay, I noticed a null pointer exception (see log file attached) which appears every time after I switched the device. This is not a real problem for me as the relay works. However, I guess this should be fixed somewhere?

Device: Xiaomi two way relays LLKZMK11LM
Openhab: 2.5.0 M1

Annotations:

  • The linked items are configured as autoupdate = false and I manually send a refresh command. Maybe this is relevant when reading the log file.
  • I also use some other switches, they do not show this problem.

2019-06-15 16:14:11.441 [ERROR] [tworkManager$AFMessageListenerFilter] - Error AF message listener notify.
java.lang.NullPointerException: null
at com.zsmartsystems.zigbee.serialization.DefaultDeserializer.readZigBeeType(DefaultDeserializer.java:72) ~[201:com.zsmartsystems.zigbee:1.1.6]
at com.zsmartsystems.zigbee.zcl.field.AttributeReport.deserialize(AttributeReport.java:100) ~[201:com.zsmartsystems.zigbee:1.1.6]
at com.zsmartsystems.zigbee.zcl.ZclFieldDeserializer.deserialize(ZclFieldDeserializer.java:73) ~[201:com.zsmartsystems.zigbee:1.1.6]
at com.zsmartsystems.zigbee.zcl.clusters.general.ReportAttributesCommand.deserialize(ReportAttributesCommand.java:88) ~[201:com.zsmartsystems.zigbee:1.1.6]
at com.zsmartsystems.zigbee.ZigBeeNetworkManager.receiveZclCommand(ZigBeeNetworkManager.java:808) ~[201:com.zsmartsystems.zigbee:1.1.6]
at com.zsmartsystems.zigbee.ZigBeeNetworkManager.receiveCommand(ZigBeeNetworkManager.java:731) ~[201:com.zsmartsystems.zigbee:1.1.6]
at com.zsmartsystems.zigbee.dongle.cc2531.ZigBeeDongleTiCc2531.notify(ZigBeeDongleTiCc2531.java:316) ~[202:com.zsmartsystems.zigbee.dongle.cc2531:1.1.6]
at com.zsmartsystems.zigbee.dongle.cc2531.network.ZigBeeNetworkManager$AFMessageListenerFilter.receivedAsynchronousCommand(ZigBeeNetworkManager.java:1288) [202:com.zsmartsystems.zigbee.dongle.cc2531:1.1.6]
at com.zsmartsystems.zigbee.dongle.cc2531.network.impl.CommandInterfaceImpl.notifyAsynchronousCommand(CommandInterfaceImpl.java:382) [202:com.zsmartsystems.zigbee.dongle.cc2531:1.1.6]
at com.zsmartsystems.zigbee.dongle.cc2531.network.impl.CommandInterfaceImpl.handlePacket(CommandInterfaceImpl.java:160) [202:com.zsmartsystems.zigbee.dongle.cc2531:1.1.6]
at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:116) [202:com.zsmartsystems.zigbee.dongle.cc2531:1.1.6]
at java.lang.Thread.run(Thread.java:748) [?:?]

Here is the complete log file including one null pointer exception after switching ON and one null pointer exception after switching OFF: zigbee_log.txt (99.2 KB)

Kind regards!

Please use a more recent binding, and if the problem persists provide an updated log. My guess at the moment is that the issue is already fixed.

Thank you. I’ll consider this as fixed until I’m able to try a new version (currently I have version 1.1.6).

I’ll have to wait for a new milestone build as the version 1.1.7 to 1.1.10 installed with the “manual install script” fail to load on my 2.5.0 M1 installation with severe errors like:

2019-06-15 17:55:30.620 [ERROR] [org.openhab.binding.zigbee ] - FrameworkEvent ERROR - org.openhab.binding.zigbee

[…]

2019-06-15 17:55:30.632 [ERROR] [org.openhab.binding.zigbee ] - bundle org.openhab.binding.zigbee:2.5.0.201906151001 (327)BundleComponentActivator : Unexpected failure enabling component holder org.openhab.binding.zigbee.internal.converter.warningdevice.DynamicWarningCommandDescriptionProvider