During the network configuration, the Tuya gateway reads 6 attributes under the basic cluster of the device to identify it. After the sub-device responds with data, the sub-device panel will pop up on the App.
Zigbee 3.0 requires obtaining the Trust Center (TC) link key during the network entry process. If the TC link key fails to be obtained, the device will leave the network.
In summary, the issue of the device going offline immediately after successful network configuration may be due to the failure to obtain the TC link key. The possible causes for this issue could be:
- The gateway reads the attributes under the basic cluster and registers them to the cloud. Right after the sub-device interface pops up on the App, the user exits the network configuration interface. At this point, because the network configuration mode is exited, the device fails to obtain the TC link key.
- During mass device network configuration, a large number of concurrent entries can cause the gateway to be busy, resulting in the device's TC link key request not being responded to.
- Interference and other factors may cause the sub-device's request key, the gateway's transport, and the subsequent verify and confirm as well as their APS ACK not to be responded to, leading to a failure in the TC link key exchange.
It is recommended to take the following measures to avoid this:
Use the gateway's local button (short press) to initiate extended network configuration. In extended network configuration mode, the gateway will register with the cloud after the device TC link key interaction, thus solving the problem of the device going offline due to not obtaining the TC link key.
Do not exit the interface immediately when the sub-device panel appears during App network configuration. Waiting on the interface for 30s allows the gateway to remain in network configuration mode, facilitating the sub-device's acquisition of the TC link key.