IKEA BADRING water leakage - incomplete pairing - UNINITIALIZED

Add-ons Bindings
1

Setup:
Zigbee coordinator: SiLabs Ember based NCP (BitronVideo)
ZigBee device: IKEA BADRING water sensor

Issue:
I’m having problem with BADRING water sensor. The pairing is not completed (status UNINITIALIZED), either no channels, or channels are (partially?) created, and in the log I can see exception:

2024-12-21 22:06:42.182 [ERROR] [ng.zigbee.handler.ZigBeeThingHandler] - null: Exception creating channels
java.lang.NullPointerException: Cannot invoke "Object.hashCode()" because "key" is null                                                                                                                                  at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) ~[?:?]                                                                                                                                 at com.zsmartsystems.zigbee.ZigBeeNetworkManager.getNode(ZigBeeNetworkManager.java:1647) ~[bundleFile:?]
        at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.getNode(ZigBeeCoordinatorHandler.java:1003) ~[bundleFile:?]                                                                                       at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.createZigBeeChannelConverter(ZigBeeThingHandler.java:551) ~[bundleFile:?]                                                                               at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.initializeDevice(ZigBeeThingHandler.java:532) ~[bundleFile:?]
        at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.doNodeInitialisation(ZigBeeThingHandler.java:394) [bundleFile:?]                                                                                        at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$1.call(ZigBeeThingHandler.java:244) [bundleFile:?]                                                                                                      at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$1.call(ZigBeeThingHandler.java:1) [bundleFile:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]                                                                                                                                                at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]                                                                                          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]                                                                                                                         at java.lang.Thread.run(Thread.java:840) [?:?]

Interestingly other IKEA bulbs or PARASOLL window sensor works.
What are the next steps so someone can help? Or is anyone this one working?

2

I had the same issue with some IKEA devices, and thought I was doing something wrong. In all cases, letting things rest for up to an hour (obviously some kind of cycle or refresh of the Zigbee protocol taking place?) solved it for me.

I assume that’s not the case for you?

3

@Cplant , no it isn’t. I gave it even few days, nothing, still UNINITIALIZED.

I noticed that the channels have empty configuration

  - id: SOMEID_batterylevel
    channelTypeUID: system:battery-level
    label: Battery Level
    configuration: {}

so I tried to “fix” that by looking to other IKEA (PARASOLL)

  - id: SOMEID_batterylevel
    channelTypeUID: system:battery-level
    label: Battery Level
    configuration:
      zigbee_reporting_polling: 7200

but it seems it did not help, again the same exception in the log as noted above.

4

Interestingly after few hours playing with other stuff and restart of OH it is now ONLINE and Water Alarm channel works.
During last few weeks I did almost everything (including restarting OH, rebooting RPi) to no avail.

Today I did only one extra thing and it is the above configuration field population. May be this helped and could help someone else too. I’ll monitor it, but at this moment I do not find it “reliable”