Zigbee binding stopped working since 2.5 M4

Tags: #<Tag:0x00007fc2086fa0c8> #<Tag:0x00007fc2086f9fb0> #<Tag:0x00007fc2086f9d80>

Hi,

I’m using OSMC Vero with CC2531 zigbee coordinator. Up until 2.5 M3 everything worked without problems. When I first upgraded to M4, zigbee devices either stopped working or took like 30s to respond to command. I was getting these errors in log

2019-10-28 18:55:31.810 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [205:com.zsmartsystems.zigbee.dongle.cc2531:1.2.3]
at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [205:com.zsmartsystems.zigbee.dongle.cc2531:1.2.3]
at java.lang.Thread.run(Thread.java:748) [?:?]

I’ve reverted back to M3 and all was good, but yesterday I (accidentally) upgraded to 2.5 M5 and it’s still completely broken - the devices (mainly Tradfri bulbs) no longer respond to any commands. So far I’ve tried:

  • Rebooting
  • Reconnecting CC2531 stick
  • Reset Controller in CC2531 thing parameters
  • Removing and pairing all bulbs again
  • Disabling/enabling coordinator and individual bulbs
  • Toggling “Initialize device in bulb setup” (for some reason this button is displayed multiple times)

Weird thing is that pairing works flawlessly, bulbs are immediately put into inbox, all channels and properties are recognized correctly, it even seems to show online status right, but commands don’t do anything. I’ve Increased logging level as per zigbee binding page, here’s the output when I try to change brightness of one bulb:

log.txt (28.2 KB)

Does anyone have any idea what’s going on? Did anything important changed in M4?

Lots changed, but not in the TI driver where your error seems to be. The driver has had nearly no changes for a year or more.

I think lots of other people are using the TI driver, although I don’t personally use it so can’t really comment too much unfortunately.

Can I get some help with this? I updated to 2.5 release version but the issue still persist. All the battery operated zigbee devices like door and temperature sensors work without problem, but every single tradfri lightbulb ignores commands. Here’s console log, Im also attaching more verbose log: openhab-log-verbose.txt (249.0 KB) .

Is there anything I could do to debug it? I don’t want to be stuck on M3 foverever

2019-12-16 21:25:55.672 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 14B457FFFE2AE968: Starting ZigBee device discovery
2019-12-16 21:25:55.686 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - D0CF5EFFFEFA85B3: Starting ZigBee device discovery
2019-12-16 21:25:55.706 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00044DB501: Starting ZigBee device discovery
2019-12-16 21:25:55.738 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D0004114303: Starting ZigBee device discovery
2019-12-16 21:26:07.299 [WARN ] [org.eclipse.jetty.io.ManagedSelector] - java.nio.channels.ClosedSelectorException
2019-12-16 21:26:07.305 [WARN ] [l.protocol.RemoteControllerWebSocket] - WebSocketClient failure: java.lang.InterruptedException
2019-12-16 21:26:07.711 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D00044DB501: Error 0xffff setting server binding
2019-12-16 21:26:07.714 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D0002A19D3C: Starting ZigBee device discovery
2019-12-16 21:26:07.714 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D00044DB501: Channel zigbee:device:8ca79041:00158d00044db501:00158D00044DB501_1_pressure failed to initialise device
2019-12-16 21:26:07.718 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D0003217E1B: Starting ZigBee device discovery
2019-12-16 21:26:07.739 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - D0CF5EFFFEF8D40D: Starting ZigBee device discovery
2019-12-16 21:26:07.749 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00044DB460: Starting ZigBee device discovery
2019-12-16 21:26:19.667 [ERROR] [converter.ZigBeeConverterSwitchLevel] - D0CF5EFFFEFA85B3: Error opening device level controls
2019-12-16 21:26:19.668 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - D0CF5EFFFEFA85B3: Channel zigbee:device:8ca79041:d0cf5efffefa85b3:D0CF5EFFFEFA85B3_1_dimmer failed to initialise device
2019-12-16 21:26:19.720 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 14B457FFFEC3571C: Starting ZigBee device discovery
2019-12-16 21:26:19.733 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - D0CF5EFFFEFA7C4D: Starting ZigBee device discovery
2019-12-16 21:26:19.755 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00044B02C8: Starting ZigBee device discovery
2019-12-16 21:27:01.975 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D0004465E75: Error 0xffff setting server binding
2019-12-16 21:27:01.977 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0004465E75: Channel zigbee:device:8ca79041:00158d0004465e75:00158D0004465E75_1_pressure failed to initialise device
2019-12-16 21:27:55.816 [WARN ] [.converter.ZigBeeConverterColorColor] - 00158D0002A19D3C: Cannot determine whether device supports RGB color. Assuming it supports HUE/SAT
2019-12-16 21:28:23.021 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D0004114303: Error 0xffff setting server binding
2019-12-16 21:28:23.023 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0004114303: Channel zigbee:device:8ca79041:00158d0004114303:00158D0004114303_1_pressure failed to initialise device
2019-12-16 21:28:31.734 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D00044DB460: Error 0xffff setting server binding
2019-12-16 21:28:31.736 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D00044DB460: Channel zigbee:device:8ca79041:00158d00044db460:00158D00044DB460_1_pressure failed to initialise device
2019-12-16 21:28:50.084 [INFO ] [marthome.model.script.bedroom.rgbled] - Lights turned on by door
2019-12-16 21:29:03.576 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:25:55.672 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 14B457FFFE2AE968: Starting ZigBee device discovery
2019-12-16 21:25:55.686 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - D0CF5EFFFEFA85B3: Starting ZigBee device discovery
2019-12-16 21:25:55.706 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00044DB501: Starting ZigBee device discovery
2019-12-16 21:25:55.738 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D0004114303: Starting ZigBee device discovery
2019-12-16 21:26:07.299 [WARN ] [org.eclipse.jetty.io.ManagedSelector] - java.nio.channels.ClosedSelectorException
2019-12-16 21:26:07.305 [WARN ] [l.protocol.RemoteControllerWebSocket] - WebSocketClient failure: java.lang.InterruptedException
2019-12-16 21:26:07.711 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D00044DB501: Error 0xffff setting server binding
2019-12-16 21:26:07.714 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D0002A19D3C: Starting ZigBee device discovery
2019-12-16 21:26:07.714 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D00044DB501: Channel zigbee:device:8ca79041:00158d00044db501:00158D00044DB501_1_pressure failed to initialise device
2019-12-16 21:26:07.718 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D0003217E1B: Starting ZigBee device discovery
2019-12-16 21:26:07.739 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - D0CF5EFFFEF8D40D: Starting ZigBee device discovery
2019-12-16 21:26:07.749 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00044DB460: Starting ZigBee device discovery
2019-12-16 21:26:19.667 [ERROR] [converter.ZigBeeConverterSwitchLevel] - D0CF5EFFFEFA85B3: Error opening device level controls
2019-12-16 21:26:19.668 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - D0CF5EFFFEFA85B3: Channel zigbee:device:8ca79041:d0cf5efffefa85b3:D0CF5EFFFEFA85B3_1_dimmer failed to initialise device
2019-12-16 21:26:19.720 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 14B457FFFEC3571C: Starting ZigBee device discovery
2019-12-16 21:26:19.733 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - D0CF5EFFFEFA7C4D: Starting ZigBee device discovery
2019-12-16 21:26:19.755 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 00158D00044B02C8: Starting ZigBee device discovery
2019-12-16 21:27:01.975 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D0004465E75: Error 0xffff setting server binding
2019-12-16 21:27:01.977 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0004465E75: Channel zigbee:device:8ca79041:00158d0004465e75:00158D0004465E75_1_pressure failed to initialise device
2019-12-16 21:27:55.816 [WARN ] [.converter.ZigBeeConverterColorColor] - 00158D0002A19D3C: Cannot determine whether device supports RGB color. Assuming it supports HUE/SAT
2019-12-16 21:28:23.021 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D0004114303: Error 0xffff setting server binding
2019-12-16 21:28:23.023 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D0004114303: Channel zigbee:device:8ca79041:00158d0004114303:00158D0004114303_1_pressure failed to initialise device
2019-12-16 21:28:31.734 [ERROR] [r.ZigBeeConverterAtmosphericPressure] - 00158D00044DB460: Error 0xffff setting server binding
2019-12-16 21:28:31.736 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - 00158D00044DB460: Channel zigbee:device:8ca79041:00158d00044db460:00158D00044DB460_1_pressure failed to initialise device
2019-12-16 21:28:50.084 [INFO ] [marthome.model.script.bedroom.rgbled] - Lights turned on by door
2019-12-16 21:29:03.576 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]

2019-12-16 21:29:23.185 [INFO ] [g.eclipse.smarthome.model.script.UPS] - UPS Status: OL: online=true, on battery=false, charge=false, discharge=false
2019-12-16 21:29:26.099 [ERROR] [converter.ZigBeeConverterSwitchLevel] - D0CF5EFFFEFA7C4D: Error opening device level controls
2019-12-16 21:29:26.102 [INFO ] [ng.zigbee.handler.ZigBeeThingHandler] - D0CF5EFFFEFA7C4D: Channel zigbee:device:8ca79041:d0cf5efffefa7c4d:D0CF5EFFFEFA7C4D_1_dimmer failed to initialise device
2019-12-16 21:29:28.277 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Stineni proti slunci': Could not cast NULL to java.lang.Number; line 64, column 20, length 46
2019-12-16 21:29:28.277 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Stineni proti slunci': Could not cast NULL to java.lang.Number; line 64, column 20, length 46
2019-12-16 21:29:28.277 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Stineni proti slunci': Could not cast NULL to java.lang.Number; line 64, column 20, length 46
2019-12-16 21:29:31.706 [ERROR] [converter.ZigBeeConverterSwitchLevel] - 00158D00024F7537: Error 0xffff setting client binding
2019-12-16 21:29:34.615 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Stineni proti slunci': Could not cast NULL to java.lang.Number; line 64, column 20, length 46
2019-12-16 21:29:37.563 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:29:43.708 [ERROR] [converter.ZigBeeConverterSwitchLevel] - 00158D00024F7537: Error 0xffff setting client binding
2019-12-16 21:30:34.657 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Stineni proti slunci': Could not cast NULL to java.lang.Number; line 64, column 20, length 46
2019-12-16 21:30:40.761 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:31:07.658 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:31:16.031 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:31:27.738 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:31:33.871 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:31:34.614 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Stineni proti slunci': Could not cast NULL to java.lang.Number; line 64, column 20, length 46
2019-12-16 21:31:41.058 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
2019-12-16 21:32:03.515 [ERROR] [531.network.packet.ZToolPacketStream] - Packet parsing failed due to exception.
com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolParseException: Packet checksum failed
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketStream.parsePacket(ZToolPacketStream.java:141) [bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.cc2531.network.packet.ZToolPacketParser.run(ZToolPacketParser.java:107) [bundleFile:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]

Ok, here’s a weird thing. If I remove all the bulb-things, reset them (by turning them off and on 6 times) , and turn them off by wall switch (so they have no power), and then disable and enable the CC2531 controller, all the bulbs start appearing in inbox like if they were powered on. How can they be detected by controller, when they are powered off?

Ok last update, I have removed all zigbee things, uninstalled binding, restarted openhab and cleared cache, then reinstalled binding again and added only 2 bulbs. That got rid of all the other things in inbox. Now it sort of works, but each command takes about 10 seconds to complete…

Hi,
I can confirm all of your problems.
I have the same problems with the cc2531 stick with the Z-Stack firmware from Koenk and 1x Ikea Trädfri light and 5x Müller Tint lights
I tested 2 sticks and 2 Openhab installations on Raspi 3 +4. Unfortunately without success. It only worked again after the downgrade to version 2.40 stable.
Unfortunately only one day, then the stick was no longer recognized.
After several days of trying to find a solution, I switched to the conbee II stick from dresden elektronik. This works with the hue binding without any problems.

What are the debug logs showing?

Ok so after reinstalling binding all the errors in log i posted earlier disappeared. This is log i captured after I sent bunch of commands to change brightness of bulbs. First command completed almost immediately, subseqnet took longer and longer, then one bulb stopped responding completely.
openhab2.log (178.3 KB)

So I’ve tried switching to zigbee2mqtt binding instead, that was massive fail, it didn’t work at all. So I flashed cc2531 back but noticed one thing - what is the correct firmware for zigbee binding to work? Documentation states

The file name is CC2531ZNP-Pro-Secure_Standard.hex and its sha256 is 3cc5dc571ef0f49e3f42c6c2ca076d6f8fef33a945c71e6f951b839ba0599d3c

But after flashing that, zigbee does not work at all - stick is detected but never discovers anything. I’ve actulally flashed file ‘CC2531ZNP-Pro-Secure_LinkKeyJoin.hex’ with hash befa48cd4fda1b5602ef1932f907ff1f4b81f4ae8349c7a5034d7bf58a3e271b, which works with issues I mentioned (first command executes immediately, any subsequent take multiple seconds to complete)

I can confirm the slow execution of commands with CC2531 after I upgraded from 2.5 M2 to 2.5 stable. Some commands do not seem to be executed at all.

I cleared the cache, did a lot of restarts but things even got worse. I see a lot of “Packet checksum failed” errors. Today my battery operated can not update their linked items any more.

I got so frustrated that I ordered a Telegesis dongle today, but now I realize I’m not the only one…

I tried to produce a Debug log, see attachment. All problems described in my post above initially appeared after update from 2.5 M2 to 2.5 stable.

The log includes several commands (color, dimmer) to the tradfri bulbs and I pressed the buttons on the xiami battery devices to force them to send update for their channels.
Openhab.log (240.4 KB)

Xiaomi Aqara Temperature / Humidity / Pressure Sensors:
00158d00032170c3 (button pressed several times, but no update received, distance to coordinator is 3 meters)
00158d0004146cd9 (does not seem to appear in the log at all)

Ikea Tradfri Bulbs:
14b457fffe4d3b1c (commands not executed)
14b457fffe4e0900 (commands executed with delay)
14b457fffe4ebec4 (commands not executed)

Log settings:
log:set debug com.zsmartsystems.zigbee
log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee.dongle.cc2531

@chris: Hope this helps!

I don’t really see any major issue in the logs unfortunately. I really need to get the binding updated to the latest zigbee libraries since the current library is now a few months old (or more I think). I didn’t want to do that right before the OH2.5 release since people have been using it for the past few months and there haven’t been any major issues so I wanted to leave well alone.

However, to debug I really need to be up to date as trying to debug something that is many versions old is very difficult. Over Christmas I will look to migrate the binding to this new version - there’s already a PR mostly ready to go with this.

I hope that you will find something, because like this, openhab/zigbee is completely unusable with CC2531.

I downgraded to 2.5M2 today and luckily zigbee binding works as expected again.

But many people are using it though over the past few months and there has been no change at all for about 1 year (maybe more) in the CC2531 driver.

I have to confirm the issues:

My setup is almost identical to Martin’s:

  • Controller CC2531 (used perfectly with 2.4)
  • Ikea Tradfri Bulb
  • Few Xiaomi Aqara devices: Motion detector, door sensor and Temperature

After upgrading to 2.5 all devices were marked as “offline - gone”. Rediscovering didn’t help.

So I’ve reset the Ikea bulb: immediately discovered and online.
The Xiaomi devices are instead never discovered completely and always marked as offline.

In addition I also confirm the difficulty in sending commands to the Ikea bulb: the first is usually immediate. Subsequent commands to the bulb (after few secs) are either delayed or completely ignored. The same applies to updates from the bulb.

I agree that in this state the Zigbee binding id not usable. My critical stuff is running on Z-Wave so I can afford to stay with these few devices not working properly and not downgrading to 2.4.

Maybe in this way I can help/support Chris in fixing and improving this.
It’s amazing how much effort and passion you put in this.

Let me know if you need some specific logs from specific procedures. And if you need I would also be happy to donate an Ikea bulb and a Aqara Sensor.

I’m of course open to any help you may provide. I don’t routinely use the CC2531, but it’s strange that it’s changed when the code has not changed for a very long time. This does make me suspect there could be other issues at play.

Most of my supported users use the Silabs Ember chips so this system for sure gets a lot more testing. The CC2531 doesn’t provide some of the feedback that is provided by the Silabs interface, and the CC2531 is no longer supported by Texas, so I definitely would not recommend it for future users.

Hi,
I also can confirm all the issues reported here.
My configuration is almost the same with cc2531 dongle and several bulbs from Ikea, Mueller tint and Osram.
Up to OH2.4 everything worked fine. I updated directly from 2.4 to 2.5. No Milestone in between.

What to do? Go back to 2.5M2 or wait for a solution?

Going back to M2 will not help long term The developer is convinced that the Zigbee binding is not the issue because it has not changed significantly. It is likely an interaction with the binding, the serial binding, or some other dependency.

Please read the binding documentation - it describes how to get log files.

1 Like

@chris, same issue here after 2.5 upgrade, using Nortek HUSBZB-1 USB. The zwave devices and controller work fine, only an issue with zigbee after upgrade. I tried using the log commands documented here:

I am too new to attach log file here. I’ve uploaded it to my drive, link below:

I used the zigbee log viewer by Chris and noticed some delivery errors, am not too familiar with troubleshooting this.