Zigbee devices offline after migration to openhabian 1.7

domofl · December 16, 2021, 5:12pm

Dear all,

I wanted to update to openhabian 1.7, not sure what version i was running before, but the while updating openhab to the latest state it said something that support for that openhabian version was not happening anymore (>2 years). So I updates openhab to 3.1.1, everything was still running fine.

After that I made a backup of the config.

Then I downloaded the image of 1.7 and flashed that to the SD card. After the initial boot/install i restored the backup I made earlier. That is working fine (zwave, sitemaps, rules, etc), except for zigbee. The controller is working fine (it seems), but all the devices are “OFFLINE” and also not responding.

Any suggestions?

Thank you,

Ramon

rlkoshak · December 16, 2021, 5:13pm

What do you see in openhab.log?

The Coordiantor Thing shows as online in MainUI?

domofl · December 16, 2021, 5:43pm

Thank you for replying.

Yes the coordinator shows as online. So that seems to be working.

I do see this in the logs:

2021-12-15 18:08:02.874 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - BC33ACFFFE2CCB90: Starting ZigBee device discovery
2021-12-15 18:08:02.886 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 84FD27FFFED10001: Starting ZigBee device discovery
2021-12-15 18:08:02.887 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 804B50FFFEC23602: Starting ZigBee device discovery
2021-12-15 18:08:02.888 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 84FD27FFFE479709: Starting ZigBee device discovery
2021-12-15 18:08:02.889 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 84FD27FFFE51EDAF: Starting ZigBee device discovery

and

2021-12-15 18:08:03.055 [ERROR] [e.ember.internal.ash.AshFrameHandler] - AshReceiveParserThread Exception:
java.lang.IllegalStateException: Queue full
        at java.util.AbstractQueue.add(AbstractQueue.java:98) ~[?:?]
        at java.util.concurrent.ArrayBlockingQueue.add(ArrayBlockingQueue.java:326) ~[?:?]
        at com.zsmartsystems.zigbee.dongle.ember.internal.ash.AshFrameHandler.handleIncomingFrame(AshFrameHandler.java:239) ~[bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.ember.internal.ash.AshFrameHandler.access$700(AshFrameHandler.java:59) ~[bundleFile:?]
        at com.zsmartsystems.zigbee.dongle.ember.internal.ash.AshFrameHandler$AshReceiveParserThread.run(AshFrameHandler.java:314) [bundleFile:?]

and

2021-12-15 18:08:46.506 [ERROR] [verter.ZigBeeConverterBatteryPercent] - 84FD27FFFED10001: Error 0xffff setting server binding
2021-12-15 18:08:55.928 [ERROR] [verter.ZigBeeConverterBatteryPercent] - BC33ACFFFE5E7FE9: Error 0xffff setting server binding
2021-12-15 18:09:09.555 [ERROR] [verter.ZigBeeConverterBatteryPercent] - BC33ACFFFE2CCB90: Error 0xffff setting server binding
2021-12-15 18:09:14.269 [ERROR] [verter.ZigBeeConverterBatteryPercent] - 84FD27FFFE479709: Error 0xffff setting server binding
2021-12-15 18:09:14.340 [ERROR] [verter.ZigBeeConverterBatteryPercent] - 804B50FFFEC23602: Error 0xffff setting server binding
2021-12-15 18:09:23.762 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 84FD27FFFED10001: Channel zigbee:device:01381834:84fd27fffed10001:84FD27FFFED10001_1_batteryalarm failed to initial>
2021-12-15 18:09:33.191 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - BC33ACFFFE2CCB90: Channel zigbee:device:01381834:bc33acfffe2ccb90:BC33ACFFFE2CCB90_1_batteryalarm failed to initial>
2021-12-15 18:09:47.867 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - BC33ACFFFE5E7FE9: Channel zigbee:device:01381834:bc33acfffe5e7fe9:BC33ACFFFE5E7FE9_1_batteryalarm failed to initial>
2021-12-15 18:09:52.061 [WARN ] [ng.zigbee.handler.ZigBeeThingHandler] - EC1BBDFFFEEDD17D: No supported clusters found
2021-12-15 18:09:57.286 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - BC33ACFFFE5E8D1F: Starting ZigBee device discovery
2021-12-15 18:10:01.904 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - EC1BBDFFFEEDD17D: Starting ZigBee device discovery
2021-12-15 18:10:06.751 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 84FD27FFFE6F763C: Starting ZigBee device discovery
2021-12-15 18:10:16.146 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 000D6FFFFEA4E410: Starting ZigBee device discovery
2021-12-15 18:10:34.970 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 84FD27FFFE479709: Channel zigbee:device:01381834:84fd27fffe479709:84FD27FFFE479709_1_batteryalarm failed to initial>
2021-12-15 18:10:40.805 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 804B50FFFEC23602: Channel zigbee:device:01381834:804b50fffec23602:804B50FFFEC23602_1_batteryalarm failed to initial>
2021-12-15 18:10:44.394 [ERROR] [verter.ZigBeeConverterBatteryPercent] - 84FD27FFFE6F763C: Error 0xffff setting server binding

Best regards,

Ramon

rlkoshak · December 16, 2021, 5:48pm

OK, you’ll have to generate and post some debug logs from the binding (see the binding docs for details on how to do that).

If I were to blindly try something, I’d delete a Thing and then rediscover it to see if that gets that Thing working. If so you know what to do for the rest.

domofl · December 18, 2021, 10:10pm

I put debug log level in the binding, but the first thing it generates is the ash thread exception. So in the end I just left all the things in, just scanned again for new devices and put each device in pairing mode. Although there was no indication of a new device it did start working again as intended.

Thank you for the suggestion