SDM02 SP

The Tuya WiFi version can only be integrated into the Tuya Cloud using Tuya's encrypted MQTT communication. It cannot be directly integrated with any third-party cloud platforms, ecosystems, or gateways. Third-party clouds or edge gateways need to be integrated via Tuya cloud APIs. For details, please refer to Tuya's developer documentation.

Note:

1. Tuya's strategy for adjusting the cloud data reporting frequency is not fully disclosed. Based on the latest updates as of April 2026, provided the daily data reporting traffic limit is not exceeded, the fastest expected reporting interval will be between 5 to 15 minutes.

2. Tuya's Smart Life App is user-friendly and straightforward, making it ideal for entry-level smart home users who prefer simplicity and basic energy consumption monitoring.

For standard operation, the Tuya Zigbee version must be integrated with a Tuya gateway, which then connects to the Tuya Cloud via Tuya's encrypted MQTT communication.

Note:

1. Tuya's strategy for adjusting the cloud data reporting frequency is not fully disclosed. Based on the latest updates as of April 2026, provided the daily data reporting traffic limit is not exceeded, the fastest expected reporting interval will be between 5 to 15 minutes.

2. There are unofficial methods available on the market to integrate Tuya Zigbee products with third-party gateways or hubs - such as Home Assistant integration via Zigbee2MQTT. However, please be aware of the following potential issues when using these unofficial integration methods:

• ⚠️Network Congestion: Tuya's proprietary Zigbee data transmission strategy does not bundle data packets. Consequently, high-frequency reporting of the extensive electrical data types from several energy meters, which generate significantly more data than typical smart home Zigbee devices, can easily cause Zigbee network congestion.

• ⚠️Security Risks: Integrating with third-party Zigbee gateways using the default global Trust Centre Link Key “ZigbeeAlliance09” poses potential information security risks. Therefore, using non-Tuya gateways in commercial projects is highly discouraged. For third-party gateway integration, the Standard Zigbee 3.0 version with Install Code is strongly recommended.

The Standard Zigbee 3.0 version can seamlessly connects to third-party gateways. Thanks to the standardized application-layer integration of Zigbee 3.0, it is highly convenient and widely applicable for both residential and commercial building projects.

Currently supported smart home ecosystems include:

• Home Assistant: Integration via Zigbee2MQTT (SPM01, SPM02, SDM01, and SDM02)

• SmartThings: Integration via the SmartThings Hub driver (officially approved).

• Homey: Integration via the Bituo Technik App

You can find information about the commonly used Zigbee Cluster Library on this page.

The Open Wi-Fi version of SDM01 provides the following open APIs (refer to the Device API document), enabling users to implement local automation and connect to custom cloud platforms.

1. Zero-Configuration Discovery Mechanism (LAN Addressing)

   • mDNS / DNS-SD: Supports automatic discovery of the energy meter by EV chargers and PV inverters on the Local Area Network (LAN) without the need for IP scanning.

2. BLE Near-Field Communication Mode (Offline/Maintenance)

   • BLE GATT (Time-limited activation): Requires PIN code + PAKE algorithm authentication for local high-privilege configuration and network resets. Wakes up on demand and closes upon timeout.

   • BLE Broadcast (Always-on 24/7): Unidirectional broadcast of AES-encrypted real-time power data, allowing nearby low-power devices to listen with zero latency and without requiring a connection.

3. LAN Standard Mode (Ultra-low Latency Device Communication) Plaintext or lightweight encryption for local networks.

   • Modbus TCP: Used for local linkage with EV chargers and PV inverters.

   • Local MQTT: Used for local integration with open-source smart home ecosystems.

   • WebSocket (WS) / Raw UDP: Ultra-high frequency real-time power streaming subscription (enables DLB completion within 1-2 seconds).

   • HTTP / CoAP: Suitable for low-frequency parameter configuration and status queries.

4. Cloud Device Access Layer (Device-to-Cloud / Southbound API)

   • MQTTS (MQTT over TLS 1.2/1.3): Core main communication link.

   • HTTPS (OTA dedicated): Exclusively used for downloading large Over-The-Air (OTA) firmware upgrade packages.