Device Pairing

Last Updated on : 2024-03-04 08:53:04

This topic describes information about device pairing that applies when you develop IP camera (IPC) apps. For more information about pairing other types of devices, see Device Pairing.

Pairing modes

IPCs can be paired over Wi-Fi in multiple modes. The Wi-Fi Easy Connect (EZ) and access point (AP) modes for IPCs are the same as those for other types of devices. The following pairing modes are available:

  • Wi-Fi EZ, also known as the SmartConfig mode

  • AP mode, also known as the hotspot mode

  • QR code mode

    QR code mode is relatively simple. We recommend that you use the QR code mode. If the device can not scan the QR code, try the Wi-Fi EZ mode.

  • Pairing in combination with cloud development

    The device activation implementation and code vary depending on the SDKs used for developing pairing functionality.

    A tailored version of the pairing SDK is used to implement pairing functionality. For more information, see the GitHub repository tuya-android-activator-sdk.

Binding patterns

Smart devices support three levels of binding patterns: strong, medium, and weak. A device can be activated in a home of a specific account based on the specified binding pattern. The verification method for unbinding the device varies based on different binding patterns.

  • Strong binding:

    To change the account that is associated with a device, remove the device from the app with the currently associated account and pair the device with the app by using the preferred account.

    IPCs support audio and video transmission and require privacy protection. To achieve this purpose, by default, the strong binding pattern is used and cannot be changed. If you want to switch to another binding pattern, carefully estimate and minimize the potential negative impact, and submit a ticket to request technical support.

  • Medium binding:

    A device can be bound to a preferred account. You do not need to remove the device from the app with the currently associated account. In this case, the home administrator or default administrator of this account receives a push notification of the binding operation.

  • Weak binding:

    A device can be bound to a preferred account. You do not need to remove the device from the app with the currently associated account.