Zigbee samples fail to pair with Hubitat

[Tiit]

Hi,

Users of our product have reported issues with multiple versions of Hubitat hubs when pairing Zigbee. I'm investigating this issue and have reached a point where I could use your help on how to proceed. I have captured Wireshark logs of the pairing process with multiple version of Hubitat hubs and they all see to fail in the same way in the TCLK Update process. So thinking something is majorly wrong with my code I tried clean Zigbee Light Switch samples from SDK versions 2.5.0, 2.7.0 and 2.9.2 and they all fail in the same way. So now I have reached a point where a clean sample build (just adding the CONFIG_ZIGBEE_CHANNEL_SELECTION_MODE_MULTI thing to prj.conf) fails with a commercially available hub and I'm not sure where to go from here. 

I can share Wireshark captures if those would help. Or can you suggest something I should try to further investigate this. All the samples and my product work well with most other Zigbee controllers with no issues. So far the problem seems to specifically relate to Hubitat somehow. But I have tried other Zigbee devices with Hubitat and they seems to work fine. I have also tried contacting Hubitat developers but with little luck so far.

Tiit

[Tiit]

Hi Marte,

I did try that but it seems that Hubitat sends the key unsolicited and this setting probably just disables the requesting of the key. The unsolicited key still seems to trigger the leave response unfortunately.

Tiit

[Marte Myrvold]

Hi Tiit,

I have been trying to investigate whether there are any other workarounds or solutions, but unfortunately, I have not found anything. 

I recommend contacting Hubitat support (https://support.hubitat.com/).

Best regards,
Marte

[Tiit]

Hi Marte,

I did talk with Hubitat support as well and while they are aware of the issue they did not see a way to fix this without causing problems for their other users with devices working in non-standard ways. 

I also contacted ZBOSS developers and they suggested I could join the organization as the lowest tier member for access to the specific source files I would need to fix this. But that still comes with a yearly subscription cost that would not make sense for the few users we have with this issue. 

So unfortunately it seems that we will just have to accept the limitations of the current version and advise users to upgrade to newer Hubitat versions that do work. I think the core issue comes from the way developers try to make their devices work in standard breaking ways. With Zigbee it seems that any certification is pretty rare and with years of development certain things have evolved on their own to become non-compliant and now that is breaking backwards compatibility. 

While unfortunate this is something I can live with for now. Thank you for all the help and let's hope Matter has fewer issues like this in the future.

Tiit