command do not follow the Zigate protocol

[pipiche38]

@puddly, currently the zigpy-zigate rely only on receiving 0x8000 status response to handle the next command.
This is wrong as the current NXP Zigbee stack rely on the protection of aPDU and nPDU.

In such and depending on the nature of the command ( ZDO, ZCL ), with Ack or w/o Ack, you must wait that the command is out of the Zigate or even receive by the targeted device.

@Badz has implemented a version which works perfectly on our environment (with the new radio API)
https://github.com/zigbeefordomoticz/zigpy-zigate/blob/7d29c71411998584bb0da0a42e07f5f5ea119cab/zigpy_zigate/api.py#L298

If not doing that you will get some strange behaviour when sending command on a more intensive way.