Firmware ZDO proxying

[puddly]

Thank you for writing and open sourcing this library! ZBOSS has long been on the radar and your implementation is very clear.

I've skimmed through the source code and noticed that ZBOSS seems to intercept and proxy all ZDO requests, similar to Z-Stack before. Does ZBOSS also successfully send any request to endpoint 0 and intercept the response? Or does it not allow the requests to be sent directly to endpoint 0 in the first place?

Also, do you happen to have a link to the serial protocol documentation? I'm unable to find any of the commands within the ZBOSS source code, nor in Nordic's documentation.

[DamKast]

Does ZBOSS also successfully send any request to endpoint 0 and intercept the response? Or does it not allow the requests to be sent directly to endpoint 0 in the first place?

ZBOSS does actually send ZDO requests when using the APSDE data request command (I can see ZDO packets with the sniffer), but the response is intercepted and is not returned to zigpy. This is why we have to overwrite the Zdo class in order to redefine the request methods to use the specific ZBOSS commands.

Also, do you happen to have a link to the serial protocol documentation? I'm unable to find any of the commands within the ZBOSS source code, nor in Nordic's documentation.

I asked directly DSR and they sent me this documentation.

[Hedda]

do you happen to have a link to the serial protocol documentation?

Originally posted by @eexarevsky in zigpy/zigpy#394 (comment)

See there https://cloud.dsr-corporation.com/index.php/s/BAn4LtRWbJjFiAm

Yes, ZBOSS supposes that application does not send ZDO commands as just APS data. Use ZDO API instead.

There are full sources for the host side of ZBOSS NCP there https://developer.nordicsemi.com/Zigbee/ncp_sdk_for_host/ncp_host_v2.2.1.zip

And, remind, Wireshark can parse ZBOSS NCP. But I am in doubt Nordic uses that feature.