Thanks. It looks to me like this is not a major issue. It looks like the bind is working ok, but the system is not properly correlating the response, so we are seeing this error. I will take a look at this, but I do see a positive response from the device.
(ignore the attribute report that was received here - it’s not relevant to the bind transaction)
This resulted in the following error after the 10 second timeout -:
2018-12-18 19:40:23.819 [ERROR] [converter.ZigBeeConverterSwitchOnoff] - 282C02BFFFE022B8: Error 0xffff setting server binding
Clearly this bind was successfully acknowledged by the device, but the library didn’t correlate the response.
I think this can therefore be ignored for now.