Browse the most common questions and expert answers about Consumer After-sales Issues on the Tuya IoT Platform.
Screen rotation is a DP point capability. You can use the schema of DeviceBean to obtain the type information of the device control data point. Then confirm the DP point corresponding to the screen rotation of your current device, and then call publishDps to issue DP point data. https://developer.tuya.com/en/docs/app-development/devicemanage?id=Ka6ki8r2rfiuu.
When browsing videos on the WEB, due to local network issues, P2P links cannot be established, and cloud forwarding preview will be performed, with a ten-minute limit. There is no distinction between H.264 or H.265 encoding. If there is always a situation of cloud forwarding preview terminal, please check whether the user's network is smooth.
To trigger the message event for cloud storage video, the following steps need to be taken: 1. Ensure the SDK application is integrated with the appropriate Tuya SDK library. 2. Use the IPC SDK to receive the device's motion events. 3. Save the video to custom cloud storage. 4. Develop your own logic to implement the event trigger mechanism for receiving cloud storage video messages and display them on the device. 5. If the account has enabled the event storage service, confirm whether the cloud storage function is enabled on the device. 6. Use the getMotionDetectionInfo interface to query cloud storage recordings; query the video based on the alarm picture's corresponding time. 7. It may be necessary to associate the query time with the video segments in the storage card. 8. If the video query is unsuccessful, check the relevant logs to ensure the Camera object is correctly initialized, and use the CameraCloudStorageActivity provided in the sample project for querying. 9. If the video link is not successfully obtained, check the logs related to the SDK interface to ensure the relevant methods and logic are correctly configured and called.
Please confirm whether the device has already been bound to the international version of the Tuya App. If so, please unbind the device from the international version of the App and then use the domestic version of the Tuya App to test scanning. Cross-region operations are not supported, so if the device is already bound to the international version of the App, scanning on the domestic version of the App is not supported.
The default language of the Tuya App is determined by the language settings of the phone system. If the phone system language is set to English, the App will display in English by default. If you need to switch languages, you can do so in the App's multilingual settings.
Based on the situation provided by the user, it is recommended to take the following steps to resolve the issue: 1. Ensure that the router and device can automatically reconnect to the cloud after power cycling. You can verify if the module works properly by testing the bare module separately and simulating tests using a debugging assistant. 2. If the Wi-Fi module returns to normal after power cycling, it may be a power instability issue. It is recommended to check the power stability. 3. Capture the local logs of the module for analysis. You can capture the network configuration logs by sending commands via the serial port, ensuring the operation is performed at the correct rate. 4. If the issue recurs and the logs indicate normal network reconnection, it is recommended to record a test video to illustrate the problem and continuously monitor the module logs to help diagnose the source of the issue more thoroughly.
To resolve the issue of information transmission being blocked during the integration of Tuya devices and cloud applications, and to understand the access situation of IoT core services, please follow these steps: 1. Check the current status of the IoT Core service to ensure the service has not expired or been restricted. 2. Log in to the Tuya Developer Platform and check whether the service subscription status is valid. 3. If the service period has expired, apply for an extension of the trial period or re-subscribe to the service. You can request an extension through the application function provided by the platform. 4. Check the network settings and firewall configuration to ensure that the ports and protocols for message transmission are allowed through. 5. Confirm that the device and cloud application are configured correctly and support the relevant functions of the IoT Core service. 6. When encountering problems, ensure detailed logging for further diagnosis, and consult a professional technical team for assistance if needed.
For mobile phone manufacturers without official push support in China, such as Samsung, Meizu, Lenovo, Nubia, etc., Tuya supports using the MQTT push solution. This solution can only receive pushes when the App is running in the foreground. If the App is closed or in the background, push messages cannot be received. In addition, the Tuya public version App also follows this push logic, meaning that if the App is killed or not opened, it cannot receive pushes, such as doorbell and anti-hijacking alerts. Regarding third-party push support, Tuya does not support the integration of third-party push services such as Getui. Users can choose to integrate the push services of the corresponding mobile phone manufacturers and set the product's alarm content on the Tuya platform to achieve push notifications. For more information on push integration, you can refer to the Tuya Developer Platform and related documentation support for assistance.
The hotspot name for the public version app hotspot network configuration must comply with the specifications of our customized hotspot requirements. This specification has been effective for many years and must be followed for network configuration.
Hello, Due to some modules not having a field for printing the material code (P/N), the material code (P/N) for these modules will not be printed on the module but will be printed on the delivery note. Note: When placing an order, if the production delivery information edit page prompts "Material code (P/N) will be printed on the delivery note," it indicates that this module does not have a field to print the material code (P/N).
Confirm whether your trial renewal has successfully taken effect. Since the renewal may take some time to process, it is recommended to wait or try testing again the next day. If the IoT Core trial period has been extended and approved, but you still encounter the error "No permission, your cloud development plan subscription has expired," you can take the following steps to resolve it: 1. Confirm that the free quota for API calls this month has not been exhausted, which can be resolved by automatically refreshing the quota next month. 2. Ensure that the IoT Core trial period or related subscription has been correctly activated and recognized in the system. If there are issues with system settings or subscriptions, this error may occur. 3. If the status is confirmed to be normal, there may be some delay time for the extension application to take effect after approval, it is recommended to try again later or try again tomorrow. 4. If the problem persists, consider purchasing a more advanced version of IoT Core to continue using the service.
Hello, the IoT Core connection service experience version has a limit on free resources per month. If the status of the cloud development basic resource experience version shows "paused", it means that the free quota for this month has been used up. You need to wait for the quota to refresh next month to continue using it. You can refer to this knowledge: https://support.tuya.com/en/help/_detail/K8sdy1milue6z, to check usage and remaining quota.
For Device Connection Service whose accounts are registered after October 15, 2021, Tuya offers a free trial of one month, starting from the date when developers apply for the free trial. For details, visit: https://developer.tuya.com/en/docs/iot/open-api/quick-start/membership-service?id=K9m8k45jwvg9j.
There is only one Mesh device that can be directly connected to the mobile phone, and the network configuration and control of other devices rely on forwarding. A family in the app can be configured with a maximum of 1000 devices.(Prior to version 6.9.0, there were 200).
EU users inApp v6.5.0 and above versionscan export data through the following path:App Settings Privacy Policy Management Device Data Export.
The reaction of scanning the device interaction code with a mobile phone may be related to the type of device. For virtual device testing, scanning the QR code is only used to add the device, and the step to enter the Wi-Fi account and password will not pop up. However, when adding a real device, the app will automatically prompt for the Wi-Fi name and password information. For plugplay type devices, on the page to enter Wi-Fi and password, you can click the skip button in the upper right corner to skip the Wi-Fi information input and directly proceed with device networking. Therefore, not all devices require entering Wi-Fi account and password after scanning the interaction code.
Tuya's cloud service has global coverage, and Tuya Wi-Fi products can be used worldwide, except for the North and South Poles. The products support sales in other countries. When using Tuya Wi-Fi products, different country channel codes should be configured during module burning (products with module firmware version greater than 3.x.x do not need to select channel codes). The specific configuration method and guidance documents for selecting channel codes are as follows: The role of country codesHow to choose Wi-Fi channel codes?What is Wi-Fi country code adaptation?
No, according to EU law,from September 12, 2025,it is required thatIoT products and serviceswithin the EU must support user access and export of device data.
Network modules are classified into LAN modules and WAN modules based on the network coverage. LAN modules: The network coverage is within a few meters. LAN modules are generally intended for indoor short-range network applications. WAN modules: The network coverage is within a few kilometers. WAN modules are generally intended for outdoor long-range network applications.
Currently, local area networks (LANs) support access protocols such as Wi-Fi, Bluetooth Mesh, Bluetooth Single Point, Matter over Thread, and Zigbee.
Contact the product manager for connection lines to obtain such specifications.
In environments without Wi-Fi, it is recommended to use a single Bluetooth module. However, it should be noted that a single Bluetooth module cannot be controlled remotely without a gateway, and only supports short-range control. This is a characteristic of Bluetooth modules. Therefore, if remote control functionality is required, please ensure there is an appropriate gateway device in the environment.
In the case where the module already has a network connection record, when using the anti-mistouch mode, the module will automatically reconnect after a 3-minute timeout. If it does not reconnect, it may be because the anti-mistouch mode was not selected correctly.
The garbled TX data sent by the module may be due to incorrect baud rate settings or connection issues. Ensure that the baud rate used meets the module's requirements, with common baud rates for Tuya modules being 9600 and 115200. Please confirm whether the module's baud rate adaptive function is enabled to facilitate correct debugging and ensure connection stability.
For the modules that have been potted, a push upgrade will be carried out. Unused modules need to be upgraded independently. Future modules and orders will incorporate anti-backflow technology during application to enhance performance and stability.
You can contact the product manager to obtain selection content related to onboard antennas.
For the circuit evaluation issues related to sleep mode, it is recommended that you first provide the schematic of the level conversion for us to conduct evaluation analysis. Regarding the differences between the US version, European version, and Chinese version of the module, please refer to the module specification to compare and identify specific differences. Additionally, during the sleep circuit design process, attention should be paid to the issue of not connecting pull-up resistors, and a solution should be reserved.
If you need to change the module's pin position, you can change it to another supported position, ensuring that the new position does not affect the normal operation of other functions.
When using the getLatestMessageImage method in the IThingCameraMessage interface, an error "Remote api run unknown failed" occurs. It is recommended to take the following steps to resolve it: 1. Check the correctness of the device ID parameter. Ensure the device ID is passed correctly. 2. Confirm that the device ID parameter is in the format of a list collection and set the parameters correctly. For example: {"devIds":"[\"ebe2a245f7ae78bd69icad\"]"}. 3. Convert the device ID to JSON format and try again. 4. If the error message indicates "Camera connection does not exist," confirm the parameter format is: ["ebc0602da8a4a11e1bth1q"], ensuring there are no extra nested square brackets. 5. If the issue persists, please confirm the connection status of the device and try again.
Some modules exhibit abnormal behavior when powered on. Anti-backflow is enabled when powered on, but it defaults to off after repowering. After clearing the data area, control is normal. It is recommended to check the status of register 8007 to ensure whether the enable state is saved.
The main difference between T1-M and T1-2S lies in the antenna type, where T1-M uses a ceramic antenna suitable for compact structures, while T1-2S-NL uses an onboard antenna suitable for loose structures. Generally, there is no significant difference in performance, but in cramped spaces or environments with a lot of surrounding metal, it is recommended to use an external antenna. Regarding wireless performance, the Wi-Fi transmission power and reception sensitivity of the T1-M module in different modes can be referenced in the specification sheet, with typical transmission power being 17 dBm and reception sensitivity being -88 dBm. When choosing a new model, you can select the appropriate module based on the compactness of the structure. From the shipment volume perspective, the T1-U module has a much larger shipment volume than the T1-M, so it is recommended to use T1-U.
If you cannot find the T1-M-IPEX module on the platform, it may be because the appliance category does not support T series modules. Currently, the platform has no plans to open T1 and T3 modules, as the stability of WBR3 is better. We recommend you consider using other model modules.
If Ethernet interface support is needed, it is generally achieved through SPI or serial port to Ethernet interface conversion. You can refer to similar recommended circuits. The T3-U series module SPI to Ethernet already has reference circuits and solutions, and you can consult the corresponding product manager.
If the device keeps restarting while the module voltage is stable, you can check and handle it from the following aspects: 1. Check if there are other reasons causing the device to restart, such as when the device is interfacing with the MCU, confirm whether a reset command is being sent. Additionally, you can check if the battery voltage is dropping. 2. The module may restart when the network connection times out. It is recommended to check the network status or set a longer network residency time to reduce the restart phenomenon. The minimum restart time that can be set is 180 seconds. 3. Check the interaction of serial port data. In most UART hardware designs, TX and RX are at a high level when idle, which may prevent complete power-off. It is recommended to disable the serial port when the module is powered off, allowing TX and RX to be in an open-drain high-impedance or low-level state. 4. Check whether the serial port data complies with the protocol, reduce the frequency of data reporting, and use a 3.3V DC power supply to test the module. 5. Compare the data interaction process with the debugging assistant to confirm whether the MCU correctly responds after the module sends data. Incorrect interaction data may cause problems.
For newly added custom DP points on mesh devices, re-networking is required for immediate effect.
Hello, CN: a1.tuyacn.com a2.tuyacn.com a3.tuyacn.com m1.tuyacn.com m2.tuyacn.com EU: a1.tuyaeu.com a2.tuyaeu.com a3.tuyaeu.com m1.tuyaeu.com m2.tuyaeu.com US: a1.tuyaus.com a2.tuyaus.com a3.tuyaus.com m1.tuyaus.com m2.tuyaus.com Port: 80 443 1883 8883 8886 You can whitelist the above domains and ports on the firewall.
It is recommended to distinguish by order batch, the first 9 digits of the SN of the Tuya module are the same, all belonging to the same order.
Suspended.
The module does not perform direct contact discharge or air discharge; it uses the coupling plate method for indirect discharge ±4KV.
BT3L module does not have the automatic strong connection feature. If this feature is needed, it is recommended to develop an app to work with the device end. Additionally, consider using a gateway to control device connections.
EN pin can be left unconnected, and the power can be controlled directly. When EN is connected to the MCU, the EN pin needs to be pulled high before powering on to ensure the module can start normally.
You need to determine whether the packaging of the existing motherboard is consistent with the packaging of the WBR3 module. You can refer to the WBR3 module specification to check the compatibility of the packaging. If the packaging is consistent, it can be directly embedded. If it is inconsistent, it may be necessary to design a new baseboard to adapt to the WBR3 module.
Tuya: tuyaSmart SmartLife: smartlife.
After the trial period of IoT Core expires, you can no longer use relevant APIs. You can refer to the operations at the following link for service renewal. After your service renewal application is approved, you can continue to use IoT Core. https://support.tuya.com/en/help/_detail/Kc3n6kr7kllhc.
You can reconfigure the device to synchronize the time zone: https://support.tuya.com/en/help/_detail/K9hutfy2zi0y9.
Tuya developer platform features the following requirements（If the upper limit is exceeded, it cannot guarantee the user experience.） Tuya & SmartLife Apps Item Description Upper limit Number of schedules Maximum number of schedules that can be created for a device Local timer: 30, cloud timer: 200 Number of home devices Maximum number of devices that can be added for a home 200 (Version 6.9.0 and later: 1000) Number of tap-to-runs Maximum number of scenes that can be created for a home 200 (Version 6.9.0 and later: 200) Number of automations Maximum number of automations that can be created for a home 200 Number of tap-to-run actions Maximum number of actions that can be created in a scene 200 Number of automation actions Maximum number of actions that can be created in an automation scene 200 Number of automation conditions Maximum number of conditions that can be created in an automation scene 10 Number of simultaneous logins Maximum number of mobile devices supported by a single account for simultaneous login 200 Number of homes Maximum number of homes that an account can create 20 Number of home members Maximum number of members that can be added to a home 20 Number of rooms Maximum number of rooms that can be created for a home 20 Number of room devices Maximum number of devices that can be added for a room 50 Number of devices in device group Maximum number of devices that can be added to a device group 100 Number of home device groups Maximum number of device groups that can be created for a home 20 Number of users in device group sharing Maximum number of users that a single device group can be shared with 20 Number of users in device sharing Maximum number of users that a single device can be shared with 20 Number of joined homes Maximum number of homes that an account can join in 20 Other: Item Description Upper limit Number of products Maximum number of products that can be created on Tuya Developer Platform 500 MQTT message length Maximum length of an M.
No.
No.
There are no restrictions on the use of Tuya cloud, which can be used by both individual developers and enterprise developers. Note: Due to relevant laws and regulations, individual users in mainland China need to do identity verification before they can use the cloud development platform normally, users outside mainland China do not have this restriction. If you are a foreign user, but you are prompted to do identity verification when using the cloud development platform, it may be caused by the wrong country code you selected when registering. Please click to view the solution. The billing method of cloud development projects is shown in the figure below: For more details please see: https://developer.tuya.com/en/docs/iot/membership-service?id=K9m8k45jwvg9j.
I. Differences between BLE mesh and Wi-Fi technology Networking capability and network scale Mesh devices have the ability to network and can adapt to the needs of large-scale control. They can reach up to thousands of control scenarios, while the experience of using Wi-Fi with a router connected to more than a dozen devices is poor, and mobile phones and computers cannot access the internet normally. Control methods BLE mesh can be controlled by a mobile phone's Bluetooth without a router, while Wi-Fi devices must go through a router to control Wi-Fi smart devices. Power consumption BLE mesh devices have lower power consumption, normally around 6.5mA, and can reach uA-level current during sleep mode. Module price The price of Bluetooth ICs is much lower than that of Wi-Fi ICs, making the cost of modules lower. II. Differences between BLE mesh and Zigbee technology Essential differences: BLE mesh technology is a short-range communication technology derived from the development of smartphones. Based on BLE technology, the control between mobile phones and smart devices can be more convenient. At the same time, with the help of APP and cloud computing technology, it can achieve distance sensing, touchless triggering, and location navigation functions that Zigbee technology cannot achieve. Meanwhile, BLE mesh technology can also achieve the networking control and sensor information collection functions supported by Zigbee. Zigbee technology is a product of the industrial automation era, and electronic and electrical device networks designed and constructed based on Zigbee technology. It was initially used for industrial control and later introduced into the smart home industry. Communication path methods BLE mesh uses a broadcast method for control, and all nodes in the network will forward the data, ensuring that there are multiple paths for the data to reach the target node. At the same time, the limitations of forwarding times and other network layer restrictions wi.
Hello, in order to improve security, we will upgrade the network configuration mode of Wi-Fi devices. [Upgrade range] Tuya and SmartLife (above v3.23.0), Tuya OEM App (Template：v3.23.5 or above); [Upgrade content] After the upgrade, the "Auto Discovery" function will not support the use of EZ mode to add ordinary Wi-Fi devices; but you can still configure the network through "Manually add"; In addition, other Wi-Fi devices can still be configured through "auto-discovery", including dual-mode devices (Bluetooth LE-Wi-Fi devices), lightning devices, and Wi-Fi devices that support HomeKit. If you have any questions, you can give feedback via "Tuya Developer Platform-Technical Support" (https://service.console.tuya.com). You can also call the dedicated service hotline: 400-881-8611 in mainland China, 844-672-5646 in other areas. We will serve you wholeheartedly, thank you for your support to Tuya!
Media stream processing equipment anomaly, such as P2P connection disconnection during stream pulling, needs to be reported to embedded developers for resolution.
Hello, not supported.
Module selection platform: https://solution.tuya.com/hardware.
Stamp Hole Encapsulation.
After the device has been offline for 30 minutes, Tuya Cloud sends a notification to remind the user that the device is offline, and there will also be a message record in the message center.
cat.1, cat.m, and NB-IoT protocol modules support QR code network configuration; Wi-Fi protocol modules support specific firmware versions and above, for details consult Tuya staff; Except for shared firmware, BLE protocol modules all support QR code network configuration.
Yes.
Message subscription fees are included in the IoT Core service and are not charged extra.
No.
In such cases, it is usually a Bluetooth door lock. When the Bluetooth door lock is not using a Bluetooth gateway, if you operate the door lock to unlock and the app goes to the background, the device cannot report the unlock status to the app via Bluetooth, and the app cannot know the unlock status of the device. Consequently, the cloud cannot know either, so it will not send an unlock notification. Once the door lock is connected to the Bluetooth gateway, the unlock status can be sent to the cloud through the gateway. When the cloud knows the device is unlocked, it will send an unlock notification to the app.
The low-power offline mechanism for cloud judgment is: set offline time * 3, which means if the heartbeat is set to 8 hours, and the cloud does not receive mq messages for three consecutive 8-hour periods (24 hours), it is considered offline. Offline reminder sending time: offline time + 30 minutes.
Support firmware version 2.6 and above for Mesh universal docking to develop devices with distributed linkage capabilities. Note that in universal docking, only the op operator supports DP data. Usually, a C4 command is sent, for example: 55 AA 00 C4 00 0B C1 58 00 07 A5 05 01 04 00 01 01, C1 58: dst_addr, 0xA5 sub-command: linkage report, DP data: 05 01 04 00 01 01. Return: 00, indicating the command was sent successfully.
Because Bluetooth mesh has a large amount of data communication during the communication process, and there is other data within the network, the data provided to the app will not be displayed in the cloud logs. If you need it to be displayed in the cloud logs, you can try customizing the app implementation.
Can adjust OPERATE_RET tuya_ipc_trigger_alarm_without_event(TUYA_ALARM_T *alarm); to solve Assignment of input parameter alarm: alarm_info.type = NOTIFICATION_NAME_MOTION; // Assign according to actual type alarm_info.is_notify = md_enable; alarm_info.trigger_time = tal_time_get_posix(); // Timestamp alarm_info.upload_time = 0; alarm_info.valid = 1; alarm_info.force = 1; alarm_info.resource_type = RESOURCE_PIC; alarm_info.pic_buf = (CHAR_T *)snap_buffer; alarm_info.pic_size = snap_size; alarm_info.extra_data = NULL; alarm_info.context = NULL; alarm_info.context_cnt = 0; alarm_info.media = NULL; alarm_info.media_cnt = 0;.
No, whether the module enables the low power consumption mode for maintaining a long connection, without this field, the low power consumption mode is turned off by default. For some products, in the absence of network control, the module needs to keep the average power consumption below 15mA while maintaining a connection with the router. This capability can be enabled through this field. If the product has no power consumption requirements, this field does not need to be considered. 0: Turn off low power consumption mode 1: Turn on module low power consumption mode.
The 0x0A command is required to start the network configuration.
Direct communication between two nodes is not currently supported, but it can be achieved through a group. Add the two devices to the same group on the app, then the devices obtain the group address and send data to the group address. Other devices in the same group will receive the data.
No, soldering is not required on the back of the module, and it is not recommended to route signal lines.
Tuya All-in-one App is supported globally, covering major countries and cities except for Antarctica and the Arctic. The countries and regions not supported are: Iran, North Korea, Syria, Sudan, South Sudan, Crimea, and Cuba.
Hello, you can get the latest update of our app through the update instructions in the developer-document center: https://developer.tuya.com/en/docs/iot/tuya-smart-app-smart-life-app-advantages?id=K989rqa49rluq.
Our modules undergo high and low temperature reliability testing. Under normal power conditions, there should be no issues. For specific power requirements, please refer to the module specifications.
Before binding the NB module, please make sure that the NB module is equipped with the minimum system circuit. The power supply is stable, the antenna compliance signal strength is good, and the NB dedicated IoT SIM card has been inserted. The NB module is not activated before it is used for the first time after leaving the factory. At this time, the binding using the Tuya App will fail, and the activation must be completed after the first network connection. Module activation steps: The module is powered, and the MCU interacts with the module. The module will send a 01 command word to the MCU to query the product PID. MCU responds to the product information query command sent by the module. The module receives the product information and uploads it to the cloud to activate the module. Network status 03 (connected to the telecommunications platform, the device is not bound) At this time, you can use the Tuya App to scan the module shortcode label to bind the device.
The Zigbee water valve does not support group creation.
Because CarPlay only supports cloud-based operations, you need to configure a Bluetooth gateway and add this device to the Bluetooth gateway for the established linkage to work on CarPlay.
If the number of devices is small, you can subscribe to the IoT Core Free Edition:https://developer.tuya.com/en/docs/iot/membership-service?id=K9m8k45jwvg9j If you need to control devices via API, you need to subscribe to the IoT Core service If no secondary development is needed, you can control it with the Tuya App.
Currently, the modules connected to the Tuya Developer Platform mainly include Wi-Fi, Bluetooth, Zigbee, and NB.
Before binding the NB module, please make sure that the NB module is equipped with the minimum system circuit. The power supply is stable, the antenna compliance signal strength is good, and the NB dedicated IoT SIM card has been inserted. The NB module is not activated before it is used for the first time after leaving the factory. At this time, the binding using the Tuya App will fail, and the activation must be completed after the first network connection. Module activation steps: The module is powered, and the MCU interacts with the module. The module will send a 01 command word to the MCU to query the product PID. MCU responds to the product information query command sent by the module. The module receives the product information and uploads it to the cloud to activate the module. Network status 03 (connected to the telecommunications platform, the device is not bound) At this time, Tuya App can be used to scan the module shortcode tag to bind the device. After the App is bound, the device must interact with Tuya Cloud once before it can synchronize the bound messages. You can interact with Tuya Cloud by actively reporting a piece of data or MCU sending a reset command to the module. The successfully synchronized module will send out a bound network status notification. The NB module has strong binding. Once bound by a user, the device must be removed through the App to bind other users. The local reset command on the device cannot be unbound. The module short code label is the unique identification code of Tuya NB module, and the non-module comes with a production label, which is generally affixed to the outer packaging of the whole machine, which is convenient for terminal customers to bind and use. This label must use the Tuya label printing tool to generate the label, the tool can be obtained from the Tuya's staff. In the development stage, you can manually enter the module IMEI binding.
The international version of the Tuya and SmartLife App for Android, starting from version 5.1.0, has added a pop-up for 2.4G & 5G network detection. For applications in the European and American regions, if the currently connected network is the 5G band, the following pop-up will appear, displaying a list of SSID information for 2.4G and mixed frequency networks.
If you are referring to Tuya's Tuya App and SmartLife App, adding new languages is not supported. For an OEM App purchased on the Tuya platform, you can add the required languages according to your needs by following these steps: 1. Find your app on the Tuya platform and click on "Set Functions" 2. Locate "Change the App's Language" and click Edit. 3. After selecting the required languages, click OK. 4. It will take effect after building the app.
Before binding the NB module, please make sure that the NB module is equipped with the minimum system circuit. The power supply is stable, the antenna compliance signal strength is good, and the NB dedicated IoT SIM card has been inserted. The NB module is not activated before it is used for the first time after leaving the factory. At this time, the binding using the Tuya App will fail, and the activation must be completed after the first network connection. Module activation steps: The module is powered, and the MCU and the module perform serial data interaction. The module will send a 01 command word to the MCU to query the product PID. MCU reply to the product information query command sent by the module. The module will upload the product information to the cloud for module activation. The module returns to the network status 03 (connected to the telecommunications platform, the device is not bound) At this time, you can use the Tuya App to scan the module shortcode label to bind the device.
Yes, this App is now compatible with HarmonyOS NEXT.
You can download SmartLife (click to download the QR code) by scanning the QR code below. You can also search for the SmartLife App in the App Store or Google Play to download and install it.
International version: 19 Domestic version: 1233006116.
In the device list page of Tuya /SmartLife App, click on the central Add Device button or click the upper right + button, you can enter the Add Device page. Detailed graphic instructions can be found in the operation manual, click to enter.
The Tuya all-in-one App currently supports only 1; The Tuya Commercial Lighting App supports multiple; When integrating the smart life SDK to develop an App, a household can have multiple Bluetooth mesh, but it is recommended to create only one mesh.
MCU OTA is not supported. Old firmware not supported, universal docking firmware key: keyen8gu, version v0.2 or above. New firmware supports: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcu_ota_doc?id=Kej5qev56yvxa.
No.
The SmartLife App supports the use of the tablet. On the Android tablet, you can adjust the horizontal screen and vertical screen by yourself (adjust the path App-My-Settings-Tablet Mode); on the Apple iPad, the horizontal screen mode is used.
Except the control panel page, the font size on other app pages will not change with the system font size. Typically, the font size on the control panel page changes with the system font size, depending on the panel implementation.
Tuya App and SmartLife App are both official Tuya App. The only difference between the two is that the Tuya App uses the Tuya logo and elements, while the SmartLife App removes all Tuya logo and elements. The data of the two apps are independent of each other, and data such as Tap-to-Run and Automation in the app cannot be transferred. If you need to transfer the device, you need to remove the device from one app and add it again in another app.
Tuya App/SmartLife App supports： Simplified Chinese, Traditional Chinese, English, German, French,Russian , Italian, Portuguese, Spanish, Japanese, Korean, Russian,Portuguese (Brazil), Spanish (Latin America) and Arabic. The languages supported by the OEM App depend on depend on whether the account has completed organization vertification. For the account vertification process, please refer to: https://developer.tuya.com/en/docs/iot/enterprise-certification?id=K914k3u3cgq58 Languages supported by default: Simplified Chinese, Traditional Chinese, English, German, French, Russian. To support other languages, you need to upgrade your account. Supported languages after vertification is completed: Chinese, Traditional Chinese, English, Spanish, French, Arabic, Japanese, German, Italian, Greek, Bulgarian, Czech, Korean, Russian, Dutch, Turkish, Hebrew, Polish, Hungarian, Vietnamese, Kazakh, Norwegian, Danish, Finnish, Svenska, Portuguese, Indonesian, Thai, Romanian, Hindi, Burmese, Ukrainian, Slovak, Malay, Bengalese, Urdu, Uzbek, Uygur, Macedonian, Filipino, Croatian, Serb, Slovenia, Lithuanian, Mongol, Estonian, Latin, Azerbaijani, Xhosa, Nepali, Bosnian, Kinyarwanda, Belarusian, Persian, Hausa, Lao, Swahili, Latvian, Kashmiri, Traditional Chinese(Hong Kong Special Administrative Region,China), Javanese, Telugu, Marathi, Tamil, Portuguese(Brazil), Gujarati, English(United Kingdom), Spanish(Latin America), Armenian. You can manage various languages in your OEM App through the Tuya developer platform. For details, please visit: https://developer.tuya.com/en/docs/iot/app-development/app-multilingual/app-internationalization?id=Ka1flcgy1j3a8.
Tuya Bluetooth module BTU-IPEX, Wi-Fi module WR4-IPEX support external antennas with an I-PEX connector.
Currently Tuya has MCU universal docking NB modules: NM1/NM1-CT/NM1-GL/NX1 module.
open your App and flow those steps:【Me】~【Settings】~【Account and Security】~【Link Now】.
Whether to include firmware depends on the module type and product development method. If there is an empty delivery option on the module procurement page, use the Tuya production solution for burning. If there is only a custom delivery option, the Tuya factory will burn it for you and ship it, so you don't need to worry about the firmware issue.
I. Presentation Form Set up automation/one-click execution, as shown below, product features appear with terms like dp_switch, dp_mode, etc. II. Solution Steps: 1. Log in to the development platform https://iot.tuya.com 2. Product Development — Product Configuration — Scene Linkage Setting Enter the relevant page, check the Scene Linkage Setting, and configure whether it is normal. In the following situation, you need to go to Product Multilanguage to set. 3. Product Development — Product Configuration — Product Multilanguage Modify the display copy of related product features 4. If Multilingual support is available for multiple countries, you can choose to export for modification and then import. 5. For more detailed guidance documents: Click here 6. After the operation is completed, if the panel display is not updated, please clear the app cache, click here for app cache clearing, and then test and verify.
In an ordinary all-in-one app, a household can have up to 200 devices connected to the network.
Without gateway: number of mobile phones=number of non low power nodes in mesh network With gateway: unlimited.
Bluetooth mesh is a new protocol introduced by Bluetooth. The previous protocol only supports a single device to communicate with a single device, while the mesh protocol supports multiple devices to communicate with each other, and data transmission between multiple devices is broadcast. Bluetooth 4.0 phones can directly control Bluetooth mesh devices.
Wi-Fi does not have large-scale networking capabilities, Zigbee and Bluetooth mesh have networking capabilities.
A regular all-in-one app can connect up to 200 devices per household.
0XE8 is to query the version number for OTA upgrade.
Yes.
A family supports binding up to 200 devices by default, and can activate the Settings of Smart Control(new) on the app to increase data restrictions on home devices. Each gateway supports 128 (64 in the old version), and each family supports multiple gateways.
Because the Tuya App only allows in app painting and does not enable system picture in picture, when the App is opened, picture in picture can be displayed normally. Once the App interface is exited, picture in picture will disappear together.
The UI service package for IP cameras does not require additional fees, and the service package is included in the Smart Life App SDK.
The Tuya all-in-one app does not support adding after-sales contact information. If you encounter any problems while using the all-in-one app, you can provide feedback through the help center in the app, and technical support will be responsible for resolving and responding.
Not currently supported.
In China, only mobile cards support direct connection, while overseas generally supports direct connection.
The use of NM1-GL module in foreign countries depends on the local operator's SIM card.
Not supported.
Tuya modules all have this feature.
The commonly used modules are: BT3L, BT7L/BT7L-IPEX, BTU, BP3L, BPU. You can create Bluetooth mesh protocol products and view the list of supported modules on the hardware development page.
Hello, during the interaction between the app and the cloud, MQTT may experience disconnections due to network fluctuations, the app being moved to the background, etc. You simply need to keep the app in the foreground, and it will automatically reconnect. The F004 error in question is caused by the app actively disconnecting the MQTT connection.
No, generally need optocoupler drive.
When transmitting DP data, it is recommended that dp_len should not exceed 40 bytes.
The concept of antenna bandwidth: Bandwidth: Bandwidth is a measure of the amount of spectral space occupied by a communication or data signal. For antennas, it refers to the frequency range within which the antenna's electrical parameters remain within allowable limits as the operating frequency changes. This corresponding frequency range is called the bandwidth. It is usually expressed as the difference between the frequencies at which the signal amplitude nominally decreases by 3dB relative to the amplitude at the center frequency, also known as the 3dB bandwidth. These frequency points represent the half-power points of the amplitude versus frequency function. Additionally, there is the necessary bandwidth, which refers to the minimum spectral space typically required for the effective transmission and reception of communication or data signals.
An issued command can pass through 8 nodes at most. For example, based on distance, there are 8 devices a, b, c, d, e, f, g, h. The broadcast message transmission path is: gateway-a-b-c-d-e-f-g-h. The message can only reach h, and cannot be forwarded further.
After the number of heartbeats increases, there are many uncertainties regarding the RF environment of a large-scale network. Customization can be done if there are special requirements.
Tuya currently offers a variety of types of modules to select, and the baud part is optional. You can consult a technician for the specific model: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Bluetooth LE V7.5 with the upgraded MCU function has been tested but has not been released officially. Sigmesh Bluetooth does not support MCU upgrades.
After turning off the broadcast and timer at the same time, MCU control SDA=0, then the module will go into deep sleep, module current is about 3uA. After waking up, the module will restart and run again. Note: The output of SCL pin is not controllable at this time (MCU input should use weak pull-down to indicate not connected).
Without power off, MCU can enable low power and turn off the system clock and modify the broadcast interval by sending command to the module.
Refer to the specific description in the Low Power Protocol section of the Bluetooth mesh Universal Serial Port Protocol.
It is Bluetooth LE for WBR combo module.
Tuya currently has a dual-band module solution.
The general low power mode cannot be changed. Please contact the PM to customize the firmware if you need.
If you are using a Wi-Fi module, the module can go into a low power state when it is powered off. The power-off operation is implemented by the MCU. If the MCU is not powered off, the module will not go into a low power state.
Wi-Fi low power module does not have an external INT.. After the module processes one frame of data, the power of the Wi-Fi module is disconnected to achieve low power consumption.
Now the latest Wi-Fi low power device panel cancelled the offline reminder, because the Wi-Fi low power itself achieved by disconnecting the module power. When offline, it is impossible to verify if MCU is actively power off or device out of power or some other exceptions.
Two batteries are connected in series with only 3V, and the voltage will be lower during use. The module needs a voltage of 3 to 3.6V for stable operation. All circuits need a boost circuit.
The Tuya Cloud simulation assistant simulates data sending and receiving of a Wi-Fi module. It is connected to developers' MCUs through a USB-to-TTL tool to verify whether data sending and receiving of the MCUs comply with Tuya's communication protocol and module workflow.
At present, the firmware of the module is divided into: low power firmware and general firmware.
The Wi-Fi and Zigbee protocols that are commonly connected to the MCU can select modules with low power firmware. The Bluetooth LE protocol can send low power related commands. For the TuyaOS solution, you can design low power logic by yourself.
You can specify the low field in command 01 to enable the low power mode.
Whether low power consumption is related to firmware and not strongly related to modules.
No, low power general integration does not have a self-processing protocol.
Since the module is not a purely resistive component, the value of the DC impedance is also related to the performance of the testing instrument. Generally, the DC impedance is in the MΩ range.
To ensure the proper functioning of the module, the 10uF and 0.1uF (marked as "104") capacitors on the power pins are crucial, primarily for filtering and stabilizing the power supply. The 10uF and 0.1uF capacitors work together to provide a stable and clean power supply for the chip. The 10uF capacitor is responsible for low-frequency filtering and energy storage, while the 0.1uF capacitor handles high-frequency filtering, effectively dealing with electrical noise and interference, thereby ensuring the normal operation of the module.
After the app binding is complete, the device needs to interact with the cloud once to synchronize the binding message. This can be done by actively reporting a piece of data.
For packaging information, please contact your business manager.
The trial version of the IoT Core connection service supports 50 connected devices and 10 controlled devices. For details, please refer to the service introduction page:https://www.tuya.com/vas/commodity/IOT_CORE_V2.
At present, the modules we provide only support networking functions. The external circuits and functions of the product need to be developed by you. You can refer to the following document: https://developer.tuya.com/en/docs/iot/configure-in-platform/create-product/create-product?id=K914jp1ijtsfe.
This is normal. This is because recording a video starts with an I-frame. If no I-frame is detected at the beginning time of the recording, the recording starts at the next I-frame. So, the length will be shorter. Normally, the interval between two frames is 2 seconds. It is recommended that you have no less than 2 seconds for the IPC SDK-based recording to improve the success rate of video recording.
No-code development mesh devices are by default standard SIG Mesh devices, whereas mesh devices with the MCU SDK solution default as transparent transmission devices without a configured mesh category. Only devices with the same mesh category can join the same group.
Reduce the resistance value of the discharge resistor or the capacitance value of the power supply.
The first generation IPEX antenna is used. Please refer to the datasheet of the module for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Directions for troubleshooting chip damage: Whether the baseplate circuit is reasonable, whether a voltage regulation and filtering circuit is designed, and whether there have been instances of voltage or current exceeding the module's voltage peak during actual use: Test the voltage peak data of each pin for both good and defective modules from the same order (pay special attention to whether there is overvoltage at the moment of power-on; if so, consider designing a delay circuit). Whether ESD protection measures are in place during the manufacturing process, ensuring necessary electrostatic protection, enhancing the awareness of electrostatic protection among testers, and standardizing testing techniques: It is recommended to combine the positions where defects frequently occur on-site, and optimize the related processes accordingly.
This occurs because the logic embedded in the doorbell device is to report a doorbell call once it detects someone lingering. To solve this issue, the reporting logic on the doorbell device needs to be modified.
For local app debugging, turn on the debug mode and check if there is a log printing of -[__NSCFType CGColor]: unrecognized selector sent to instance. If there is, it indicates a conflict between the UIView extension method and the React library, please rename the extension method borderColor.
When multiple identical products have been added under an account, a number is automatically appended to the product name to distinguish between different devices.
The Tuya All-in-One App is a free app that is immediately usable, offering convenient control, rich scenarios, powerful functions, and global applicability. It is designed to control multiple brands and various types of smart devices via a mobile application. Based on Android and iOS systems, it enables remote control of household appliances. The pioneering Pegasus connection technology supports automatic detection of new devices and one-click network configuration. It supports a rich combination of one-click execution and automated smart scenarios, enabling interaction and intercommunication between products. Cross-platform third-party voice control, such as Amazon Echo and Google Home, frees users' hands. Practical life-oriented permission management and device sharing make device usage more secure. One app works globally, seamlessly integrating with local life, allowing users to easily control smart devices, monitor the status of home devices in real-time, and enjoy a smart lifestyle.
Our watch app is not an independent app, but an extension. The mobile app cannot synchronize data without opening it, so the app needs to be running in the foreground to synchronize data to the watch for display.
Infrared devices/radio frequency devices do not support sharing, and the learning code of the shared device cannot be obtained, which will cause permission issues. Therefore, after sharing, the App cannot send commands to the device normally, and even if the command is sent, the device will not respond.
Bluetooth devices need to be added under the gateway to the cloud to be online, and if not mounted under the gateway, logs can only show reporting and not issuing.
If the message "No permissions. Your subscription to cloud development plan has expired" is displayed, it indicates that the trial period of your cloud development plan has expired. You can apply for a trial period extension based on the following figures.We will approve your application within one to two workdays. We recommend that you pay attention to your service status.
After the device is successfully networked, the cloud will store the relevant information of the device, including (name, picture). After changing the product picture, when adding the device again, it will first retrieve the picture of the device cached in the cloud. Only by removing the device and clearing the data, will the cached data of the device in the cloud be cleared, and the latest uploaded product picture will be displayed when re-networking.
The universal Bluetooth mesh module supports misoperation prevention function. The reconnection time is 30 minutes, which cannot be changed.
Hangzhou Tuya Information Technology Co., Ltd.
Some 4G products do not support, specific support needs to be confirmed by submitting a ticket with the PID.
Module Package Library: https://images.tuyacn.com/app/order/Module_LIBRARY_AD.rar Update link: https://pan.baidu.com/s/10xJBTxyDQjweUI6C6LhrNQ#list/path=%2F Note: The above link is not the official package library of Tuya, and is provided for reference only.
The working voltage range of most Wi-Fi modules is 3V ～ 3.6V. Bluetooth modules working voltage is 1.9V～3.6V. Zigbee modules working voltage is 2.4V～3.8V. NB modules working voltage is 2.1V～3.63V. You need to refer to the module's specification sheet: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
No. It is more convenient to use a 3.3 V MCU because you will need to convert the serial interface level if the MCU does not use 3.3 V power. Modules can be directly connected to 5V level, see the document for details: https://developer.tuya.com/en/docs/iot/mcu-access-hardware-design?id=Kaiuyozkmbgv0.
After the expiration of the free trial period for cloud development, the relevant open capabilities will no longer be available. For example: the API cannot be called successfully, and the device message cannot be successfully received. If you need to continue to use the cloud development platform, please upgrade the Flagship Edition of the cloud development platform. Click to view benefits and fees IoT Core service purchase link.
See the attached figure for the circular and square pad areas. The pads can be left unconnected and do not require soldering when the product is used.
The Tuya public version App uses Tuya's self-developed private protocol and does not support the GB28181 protocol.
No, you need to print the network configuration code by yourself. For details, please refer to: https://developer.tuya.com/cn/docs/iot/code?id=Kc0nc66niv9lo.
I. Manifestation Operate the shortcut key, as shown in the figure below, the word dp_switch appears. II. Solution steps: 1. Log in to the IoT platform https://iot.tuya.com 2. In Product Development - Product Configuration - Quick Toggle, click Settings to enter the relevant page. 3. Check the opened shortcut function points, whether multi-language is configured, and the related names 4. Enter the Multilingual management page and modify the relevant copy content 5. If it supports multiple countries' languages, you can choose to export and modify, then import. 6. More detailed guidance documents: click here 7. After the operation is completed, if the panel display has not been updated, please clear the app cache, click here for the app to clear the cache, and then test and verify. 8. If all of the above attempts are still not feasible, you can ask for help by submitting a work ticket.
1, How is the offline status determined? The device's online or offline status in the App depends on the server's judgment of the device state. According to our server's judgment logic, if no data or ping packets from the device are received during two consecutive detection cycles, the server will consider the device to be offline. A single detection cycle is 60*1.25 seconds, meaning that after the device is powered off for 60*1.25*2 seconds, the server will consider the device to be offline. There is a time difference of about 140 seconds, during which the device will still be shown as online in the App, but control will not be effective. 2, Is it possible to shorten this offline determination time? We have considered shortening the time difference by two methods. The first is to consider the device offline if no data is received from the device during one detection cycle. The second is to shorten the detection cycle from 60 seconds. However, based on Tuya's 6 years of practical experience, shortening the offline detection cycle will generate a large number of offline events, which cannot truly indicate whether the device is offline. It will also bring a significant amount of traffic costs and message storage costs. We do not recommend shortening the offline time determination from the perspective of user-friendliness and cost. The current time difference of 2-3 minutes to display offline is the most suitable solution we have found through long-term practice.
Email: ^[a-zA-Z0-9_+&*-]+(?:\.[a-zA-Z0-9_+&*-]+)*@(?:[a-zA-Z0-9-]+\.)+[a-zA-Z]{1,20}$ Mobile: [0-9]{1,} For international use Google's libphonenumber jar utility class.
Generation IPEX Antenna Base.
Excessive ripple indicates poor power supply quality, affecting the normal operation of the module. Ripple over 100mV can cause control delays, abnormal heating of the module, or even damage to the module.
When an NB-IoT module runs a reset command, it will unbind from the user and clear all data that has not been sent, clear the activation information, restore the local heartbeat interval to eight hours, and request activation again from the cloud. For specific agreement content, please refer to the agreement document: https://developer.tuya.com/en/docs/iot/universal-serial-port-access-protocol?id=K9bt65q7ucbnr#title-3-Query%20product%20information.
Currently, new versions are all launched at the same time.
Change the phone system language to English.
For Tuya App, it supports multiple gateways connected, indeed adding a gateway cannot increase the total number of nodes, but it helps to enhance the network stability (the gateway can be used as a repeater).
Currently none, the modules of the Tuya are mostly powered by 3.3V.
You need to confirm first if the device is in network configuration status. When the NB module reports the network status as Status 3: Connected to the telecom platform, device not bound, that's when the APP can successfully bind by scanning the QR code.
Whichever home the device is bound to, and whichever account that home belongs to, the device belongs to that account.
App account blocked and automatically unblocked after 3 hours.
If the user also enables automatic upgrades on the App, then the firmware will be upgraded within the set time period without the user noticing. If the user does not enable automatic upgrades on the App, then a forced upgrade mode will be implemented. A forced upgrade means that upgrade alerts are actively pushed to App users. The users have no choice and must upgrade;.
Error code 23, the number of sessions has reached the limit.
If it is caused by the lack of service order binding, you can find the relevant person in charge to bind the service order.
Please check whether you have enabled high contrast fonts in your phone's system settings. Our icons are actually text, if the phone system has high contrast fonts turned on, the system will configure it to be black and white, and it will not be able to display gray/green normally.
Please refer to the document for solution: https://support.tuya.com/zh/help/_detail/Kcc6992xdsize.
No, they do not need to be connected to GND.
Several reporting statuses of the device: 1.Active reporting - After the device status changes, it actively reports DP data. 2.Query reporting - The cloud or app wants to actively perceive the device status, sends instructions to the device, and the device initiates a report after receiving the corresponding instructions. 3.Synchronous reporting - The device actively synchronizes the status with the cloud (possibly due to the device being powered on again). Only active reporting by the device will trigger linkage. If it is a query or synchronous report, it will not trigger linkage.
Different scenarios require different treatments for sub-devices. Currently, the default TTL (Time to Live) for sub-devices in the public version online is 8. With designed hardware signals and no obstruction or interference in the module RF, the maximum coverage distance per hop can reach 200 meters in open outdoor areas, and over 50 meters per hop in complex indoor network environments such as offices. Therefore, in practical projects, the corresponding node layout should be selected based on the hardware design of the finished device, network scale, and coverage distance. If the default 8 hops cannot provide sufficient coverage in special application scenarios, custom firmware modification of network parameters may be needed to better adapt to the specific functionality required.
Open the app. Tap on "Me" in the navigation menu. Click on the settings icon in the top-right corner. Select "About" from the settings menu. Choose "Upload Log" from the options. Follow the prompts to upload the log file. Please refer to the attached image for reference.
This is because central control devices do not have a transfer function. When the family owner transfers and the original binder leaves the family, the binding status will be cleared, and the device will enter the network configuration state.
No, these appliances generally cause low-frequency interference, which is very different from the signal frequency band in which the module works.
Yes, but there may be slight differences for different products and protocols. First, some non-development solution products can support product configuration to choose whether to support anti-misdelete mechanism. Customized solution protocols can support different anti-misdelete mechanisms through instructions. For details, please refer to the protocol documentation. Second, because the anti-misdelete mechanism has a high power consumption risk, some low-power product firmware does not support it. Finally, different protocols and firmware may have different situations. If you have any questions, please contact us by submitting a work order.
"If both PIDs are non-development solutions and the firmware configurations are different, they cannot be mixed. If the firmware configurations are the same, they can be mixed. If both PIDs are custom solutions, you need to determine whether the firmware keys are the same, because different firmware keys will affect the firmware upgrade later. The firmware key can be viewed in the hardware debugging of the third step of product creation.".
Tuya modules generally output digital signals, such as PWM or IIC signals.
The Wi-Fi with the SmartLife prefix is a hotspot released by the device during the network configuration process. You can check it in the corresponding Wi-Fi list on your phone.
Please refer to the module specification for specific parameters:https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
No. Without a gateway, you can use Bluetooth mesh only for local control.
Yes. The EN pin can be pulled down to shut down and reset the module. For more information, visit https://www.tuyaos.com/viewtopic.php?t=191.
This error may occur due to network issues. The host cannot access the production system of Tuya if the network encounters an error. Make sure your computer is connected to the Internet and the service is not blocked.
A trial account is a guest account. After a guest account logs out, it is deleted. Then, the devices under the account are automatically removed and, of course, disconnected.
The power consumption varies with modules. For more information, visit https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The parameters vary with modules. For more information, visit https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The MCU determines and requests for module firmware upgrade and MCU firmware upgrade when it is powered on. We recommend that you configure the silent upgrade during OTA configuration.
Yes, the module will resend the data twice if it does not receive a response from the MCU within 1s.
Different modules have different voltage ranges, please check the module specification: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The storage temperature range of different modules is different, please refer to the module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Open App, click—Me—Settings-Clear cache, clear App cache. Go back to the App homepage, pull down the device list to refresh the following, and then re-enter the device control panel.
Generally, when power is on, 3.3V is caused by a surge voltage. You can use an oscilloscope for further verification. The solution is generally to replace a more stable power supply scheme, increase a 3.3V filter capacitor or increase an LDO to step down.
Bluetooth does not support self-processing mode, but it can only be used in the cooperative processing mode.
Bluetooth has the following advantages: 1. Low power, suitable for devices powered by batteries 2. Cost-effective, applicable to low-cost devices 3. Simultaneous transmission of data and voice signals 4. Low delay.
You need to upgrade App to version 3.13.0 or above.
This would happen if the parameter value in the DP point out of the fetch range.
Bluetooth control steps: 1. Turn on the Bluetooth of the mobile phone, and the device uses Bluetooth to configure the network; 2. The router used for the network configuration is powered off (the phone hotspot is turned off), and the wifi of mobile phone is turned off, and the 4G+Bluetooth is on, and then you need to wait about 3-5mins; 3. You can control it at this time. The control at this time is the Bluetooth control, and you can also control it by turning off 4G.
Bluetooth mesh as an underlying communication technology, itself does not have functionality; Devices using Bluetooth Mesh vary in functionality, but typically have the following general functions: • Control by voice • As a smart scenario condition or perform tasks • Form device group to perform batch operation • sharing through family.
Related to the chip, generally 3dBm or so.
Check if the module firmware version is 0.6 or above on the panel, and the mesh panel needs to match the mesh general firmware version 0.6 or above.
As long as the signal output by the power statistics chip can be connected to the IO port of the module.
The battery will be replaced as the battery voltage decreases.
The battery voltage will be lower with the use of voltage, please note that below the minimum working voltage of the module may cause the module can not work properly.
A mesh network can connect up to more than 3000 nodes using the Jizhi Light Control App. In order to stabilize the control, it is recommended to add a gateway.
The device is not connected with the remote control, but controlled by the broadcast signal.
Tuya private mesh network is based on the broadcast channel. When the device is in a normal state, it will always monitor the data packets in the broadcast channel. When it receives the data packet, it will judge whether it is sent to itself. If it is, execute it. If not, it will judge whether the packet needs to be forwarded. , if it needs to be forwarded, send this packet to the air again to achieve the function of data relay.
Except for the Wi-Fi module achieve low power through MCU power-off, the low power of other types of modules is long-term power supply of the module.
Recommended to use IO port to drive the triode, and provide the appropriate driving voltage for MOS through the on&off of the triode.
Tuya NB module supports OTA upgrade, using Tuya self-developed and chip factory developed differential upgrade solution, and the upgrade time varies according to the different firmware packages. The upgrade process will consume part of flow and a lot of power consumption, so it is generally not recommended to upgrade, so please evaluate before upgrading.
Yes, all Tuya modules satisfy the ISO9001 standards.
At present, the modules we provide only support networking functions. The external circuits and functions of the product need to be developed by you. You can refer to the following document: https://developer.tuya.com/en/docs/iot/configure-in-platform/create-product/create-product?id=K914jp1ijtsfe.
Tuya module supports 14 channels.
You can enter the documentation center: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber to learn more about it.
No, the rated operating temperature of the module is within 105℃, and abnormal operation will occur after exceeding.
At present, in addition to the on-board antenna of the module, there are three types of external antennas: the ipex antenna, the monopole antenna, and the spring antenna.
Yes, the length corresponds to the resonance point. It is recommended to match the antenna length recommended by Tuya, or let a professional RF manufacturer match.
The maximum is 3.6V.
The Tuya module output pwm minimum Ton is about 5ns, when the pwm frequency is 20K, and the minimum brightness is 1%, then select the CW mode, and slide all the way Ton to the minimum value on the heating and cooling bar, which is close to 5ns.
The maximum gain of the on-board antenna of the Tuya module is 2.2dBi.
Tuya provides cloud services all over the world. Therefore, products that use Tuya modules can be used globally except in Antarctica and Arctic.
The maximum IO drive current of Tuya module is 12mA.
It is recommended that you connect the pull-up resistor to VCC. Currently most of the Tuya modules have built in pull-ups. If you are unsure, you can refer to the specifications.
Advantages: Low cost, convenient assembly Disadvantages: low efficiency, easy to be interfered by motherboard signal.
There are there ways to embed Tuya module: 1. In-line/side-insertion welding type: the module is inserted vertically into the circuit board 2. patch welding type: the module is attached to the circuit board 3. pin type: fixed directly by the pins.
You can use a barcode scanner to scan the module's QR code. Then, its MAC address appears in the master computer.
Tuya supports some firmware BUG fixes and upgrades, but firmware configuration adjustments cannot.
Tuya modules are divided into standard version and high temperature version. The working temperature of the standard version is from -20 ℃ to 85 ℃, and the high temperature version can reach to 105 ℃. Please check the module data sheet for more details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The wireless signal frequency that Tuya module works is 2.4G frequency band.
The device cannot be registered to the cloud platform and cannot be connected to the server.
The external soft antenna of Tuya module is characterized by: the product shell is metal.
The characteristic of the external spiral antenna of the Tuya module is that it has the better directivity.
The module of Tuya can be connected with an external antenna.
In any case, including under the high temperature and the low temperature environment, during the network configuration process of the EZ or AP, and in the configured network control. No matter what the state of the whole lamp control, the module VCC must be stable between 3V to 3.6V.
In order to reduce the average power consumption of the module, when the module does not send and receive signals and process other tasks, the module will enter the sleep state, and then the firmware will start a few ms to check whether there are commands or tasks, if not, continue to sleep. This mechanism causes the current of the module vcc to keep beating, which cannot stabilize the firmware value.
Strong anti-interference ability, troublesome assembly and higher cost;.
Tuya currently does not have a wireless solution for local long-distance communication.
Yes, Tuya mainly promotes Bluetooth mesh (Sigmesh).
Wi-fi，blutooth，zigbee，NB module.
No, although metal conductors can radiate part of the energy, they cannot effectively radiate electromagnetic waves (energy radiation, low efficiency). The length, thickness, and external packaging materials of the monopole antenna will affect the performance of the antenna. The best effect needs to use the antenna sent by Tuya (according to the whole machine debugging).
Yes. Similar to the effect of the external dielectric material on the antenna resonance, it will also affect the antenna resonance frequency. It is recommended to match the antenna specifications recommended by Tuya.
The monopole antenna is recommended to use Teflon packaging material, because the simple metal core is easy to bend and break during installation due to its small diameter. Too much curvature will affect the antenna performance when the product is shipped. Teflon outer packaging material can enhance the flexibility of the antenna.
At present, Tuya ipex antenna has two specifications: 60mm and 130mm. You can contact the Tuya's supplier UB or match it yourself.
After the App pulls the devices connected to the Internet into a group, it will fix a group address. When the App operates the group, it will directly send the group package, and the devices in the same group can respond.
The device virtual ID is subject to change. Depending on the communication type of the device and the chip used, the logic of the device virtual ID change is different: when the same App account is bound, some devices will change the device virtual ID after resetting/restoring to factory settings. And some devices will not change the device virtual ID even after resetting/restoring to factory settings. But if the device is bound to another App account, the original device virtual ID of this device will change in most cases.
No, the RST pin of the module is a hardware reset pin and cannot clear the Wi-Fi configuration information.
Wi-Fi, Bluetooth, and Zigbee modules can all support LAN communication.
It can be routed, but I2C signal line is not recommended.
1.Communication protocol: long connection or short connection. 2.Temperature requirement: 105 for Lighting. Most of the products use normal temperature modules, but for products such as bulbs, the temperature inside the bulb may reach over 100℃, It has to use a high-temperature version of the module. 3. Power consumption: maximum for Wi-Fi. 4. Embedding method: patch, pin, and side insertion. 5. Chip platform: the main performance 6. GPIO requirements: basic requirement, otherwise using MCU solution if the quantity is too much. 7. Antenna type: onboard antenna, external antenna, IPEX interface 8. Size requirements.
In the case of no obvious obstacle blocking the route, the distance between the equipment and the route is 3 meters, and the minimum standard is 60. If it is lower than 60, it is a defective product.
It is supposed to check whether power supply to the module is stable. Unstable power supply can easily cause voltage dips. If it is MCU solution, pls check if the module receives the reset command.
If the network environment is better, the network connecting time is generally 4-10S.
The package of our module is compatible with in-line and SMD, but some modules are with headers before leaving the factory, and some are not. Customers can use soldering methods according to the actual conditions.
It is generally done with suspend processing, which is used for hardware reset.
When the module communicates with the MCU, the reset pin can be disconnected. You can also reserve an I/O pin for proactive reset if the program crashes.
Keep this point high when the module has no output, to avoid false triggering by interference signals.
If the temperature of the module exceeds the normal operating temperature, problems such as offline and malfunction may occur.
Hello, the module does not have over-temperature protection.
It is recommended that you should not place the module on the main control board where the high-frequency signal generated by the power board will cause signal interference to the module.
The warranty period of Tuya module is one year.
No, the modules work stably, and some modules support the sleep mode.
Avoid metal parts at least 15mm away, and the antenna shall be hollowed out of the frame or near the antenna.
The output voltage of the module control relay is 3.3V.
You can reduce the filter capacitor of the module and add a bleeder resistor.
A module's performance is determined by the chip.
The module has virtual soldering. If it is abnormal in batch, please check whether the actual furnace temperature of wave soldering reaches 220℃-240℃.
The module generates PWM signals to control products.
The function of the π-type circuit is to match the antenna impedance. If it is not matched, it will cause poor radio frequency performance.
PCB line belongs to metal, metal will have interference for the antenna signal, so when designing the circuit, it is recommended that the antenna is hollowed out to avoid interference to the signal.
Different modules have different parameters, please check the module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Generally, it is necessary to test the voltage ripple, load capacity and dynamic response of the power supply.The voltage ripple should generally be less than 100mv, the load capacity should meet the maximum peak current of the module, and the dynamic response should be less than 10%*Vout.
The module will restart repeatedly, network pairing fails, or the network pairing indicator is abnormal.
For Wi-Fi, choose 500mA or more, Zigbee, and Bluetooth 150mA or more.
Pin for digital-to-analog conversion, whose function is collecting analog signals and converting them into digital signals.
The output current of the module control relay is within 1mA.
The ADC pin is a voltage acquisition pin and cannot be used for normal IO port function; But needs to be hanging if not used.
A single antenna field type is difficult to be rounded, insertion loss is high, efficiency is relatively low, and easy to be interfered by the motherboard.
Onboard antennas are cost-effective, do not install an antenna independently, and easy to assemble.
The capacitor connected next to the crystal oscillator is called the load capacitor. The capacitor and the internal circuit together form a certain frequency of oscillation to ensure that the oscillation frequency of the crystal oscillator is more stable.
Tuya module can be controlled both through LAN and WAN, as long as the device is not offline.
No.
Yes.
Yes.
Yes.
After the gateway device is powered off, the App can be displayed offline for about three minutes.
Yes, it supports, and it is necessary to produce according to the furnace temperature curve provided by our company.
We can determine the firmware information in the module through the log printed by the module. The printing method of the module log is as follows: Lead out the LOG_TX pin of the module and connect it to the RX of the serial port. Supply power to the module and GND, the baud rate is generally 115200.
The first step is to check whether there is a short circuit between VCC-GND; The second step is to supply power to the device and check the current situation; The third step is to connect the log and serial port, check the log; Finally check the communication DP point and panel.
Commonly used monopole antennas, microstrip antennas, PCB onboard antennas, ceramic antennas, etc.
The normal process is the network status first sents 02, and then 03 to 04. If MCU does not respond to module 01 command in time, the module will not send other command words, so when MCU does not respond to 01 command in time which causes the module missed sending the network status 02 and directly send network status 03 and 04.
Responsible for sending and receiving electromagnetic wave signals from the air.
The firmware contains the boot file. And if your own firmware does not contain this file, you need to burn the boot file first.
The simple judgment is to test the continuity between VCC and GND. Under the normal circumstances, the impedance is bigger. If the impedance between VCC and GND is only a few hundred ohms or less, the module is basically damaged.
Tuya controls the quality through production process control, antenna signal calibration, strict production testing, and 100% factory inspection.
Before using the device in DRX mode, make sure: Use IoT SIM card that supports DRX type; When creating products on the IOT platform, select DRX as the power consumption type; The power consumption mode carried by the MCU in the response product information is DRX mode; After the module wakes up, it needs to call the sleep lock command to prevent entering lightsleep.
The antenna length of Tuya product configuration has been matched. This length has the best RF performance, so it is not recommended to cut it.
The length of the conductor is a specific ratio or integer multiple of the signal wavelength.
Circuit board size, cost, radiation range and directivity.
A well-designed antenna can increase the working range of wireless products.
Yes, if conditions permit, the larger gain means more signal enhancement.
Return loss, bandwidth, radiation efficiency, radiation pattern, gain.
No, the antenna needs to be purchased by yourself.
If the clearance area is sufficient, there will be no difference in general performance; If there are many surrounding metal environments or the space around the board is cramped, you can consider using an external FPC antenna to ensure performance.
Increase sending and receiving signal strength.
Before selecting the module you need, you need to create a product and then select the module. If you cannot select the module you need in the recommended list, it means that the product is not compatible with this module. It is recommended to use other models. If there is no module is shown in the recommended list, you can submit a ticket to report the problem, and our technicians will guide you to choose a suitable module.
The remaining days of the free trial period will be added to the membership period. For example, you get a 3-month free trial period on August 1, 2020, and then activate a 1-year official membership on September 1, 2020. The remaining 2-month free trial period is added to the 1-year membership, so the overdue date of membership is October 31, 2021.
The equipment suitable for NB-IoT communication includes three meters, alarms, and locators and sensors that require high power consumption.
If the two products are both connected with MCU, and the firmware is common firmware, the module can be common. You need to report the different PIDs in the terminal. In the case of No-Code Access, the same scheme and firmware configuration is required.
Yes.
The simple metal core is easy to bend and break during installation due to its small diameter. Too large bending will affect the antenna performance. Therefore, the use of Teflon external packaging materials can enhance the flexibility of the antenna.
Yes, it has an impact. Similar to the effect of the external dielectric material on the antenna resonance, it will also affect the antenna resonance frequency.
Tuya Bluetooth is a mesh topology, and data can be transferred directly between devices and devices. Groups can be created in the device details interface. As long as you control one device in the group, the devices in the group will change at the same time.
Yes, you can use the modules purchased in no-code solutions without development. You only need to design hardware.
After the App is bound, the device have to interact with Tuya Cloud at least once before synchronizing the binding message.
The control packets are mainly single packet, group packet and mesh broadcast packet.
The Bluetooth mesh protocol is a many-to-many (M2M) communication protocol based on Bluetooth. Devices that support the Bluetooth mesh protocol also support Bluetooth 4.0 and 5.0 and can communicate with other devices that support Bluetooth 4.0, such as mobile phones and computers.
Bluetooth Low Energy (Bluetooth LE, colloquially Bluetooth LE, formerly marketed as Bluetooth Smart) is a wireless personal area network technology designed and marketed by the Bluetooth Special Interest Group (Bluetooth SIG) aimed at novel applications in the healthcare, fitness, beacons, security, and home entertainment industries. It is independent of classic Bluetooth[clarification needed] and has no compatibility, but BR/EDR and LE can coexist. The original specification was developed by Nokia in 2006 under the name Wibree, which was integrated into Bluetooth 4.0 in December 2009 as Bluetooth Low Energy.
Bluetooth 5.0 is a Bluetooth technical standard proposed by the Bluetooth Special Interest Group in 2016. Bluetooth 5.0 improves the speed of devices with a low power consumption. Bluetooth 5.0 combined with Wi-Fi assists in positioning indoor locations, increases the transmission speed, and extends the effective working distance.
Tuya provides a series of cost-effective proprietary network modules. These network modules support multiple communication protocols, specifications, working temperatures, and welding methods. They also apply to different product types and development solutions. You can choose them to support your product scenarios. Tuya currently has modules: Wi-Fi module, Bluetooth Mesh module, NB module, Zigbee module, etc. These modules all realize the connection function, but the connection method is different. For more details about the Module Datasheet, please see：https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Module encapsulation is also known as Integrated circuit (IC) packaging. IC packaging indicates that the semiconductor IC chip is encapsulated in a supporting case. The case stores, fixes, seals, and protects the chip, enhances the electrical performance, and connects the chip to external circuits. Connectors on the chip are connected to pins on the case through a conductor. These pins then connect to other components through the conductor on the PCB. Packaging is important to the CPU and other large-scale integration (LSI) circuits.
A smart scene predefined in your App associates multiple smart devices to allow you to start or stop these devices simultaneously with one instruction. For example, you can create a smart scene named "Go out" to turn off your lamps, lock the door, and lower the temperature of the thermostat. To create a smart scene, open the App, tap Scene, and tap the plus sign (+) in the upper right corner. On the displayed create Smart page, specify conditions, actions, and the scene name, and click Save.
The wireless transparent transmission module, as its name implies, can transparently transmit data. During the transparent data transmission process, the sender and the receiver do not need to process the data, so the data from the sender is the same in length and content as that reaching at the receiver. The wireless transparent transmission module is equivalent to a data cable or serial cable.
Antenna gain tells us the power transmitted by an antenna in a specific direction as compared to an isotropic antenna. This specification describes how strong a signal an antenna can send out or receive in a specified direction.
First of all, stay away from transformers, inductors and other components. At the same time, there shouldn't be any metal under the module. For details, please consult the Tuya staff.
It may be that the module is authorized first, the flash is changed halfway or the chip is not re-authorized.
Analysis: the video record time is just for reference, the real time is based on the video content. i.e. the phone recorded 5mins, but the video streaming stuck or delay because of network issue like 5seconds, the real time is 4mins55seconds, instead of the record time 5mins. Instruction: check if the stream stuck at some time.
Hello, you need to clear the App cache, end the App running process, then open the App, click the device to regain the UI.
PSM-type terminals sleep deeply during non-business periods and do not receive downlink data. Only when the terminal actively sends uplink data (MO Data) can receive the downlink data buffered by the IoT platform. Please confirm whether it belongs to the following conditions: App panel operation issued instructions, but the module did not send issued data. This is because the NB module is in PSM low power consumption mode, and peripherals such as radio frequency reception are turned off, and data cannot be received. The module must actively report data once and interact with Tuya Cloud once, the heartbeat cycle arrives to send a heartbeat or a local event triggers the wake-up module to send data, and the issued instruction that was stuck in the last operation will be issued. For multiple DP operations, multiple data will be issued, and only the latest operation will be issued for the same DP. When the heartbeat interval set by the module expires, the module will automatically interact with the platform once to maintain the heartbeat. At this time, the cached data is delivered. If the device is offline, all issued commands cached by the platform will be cleared.
It depends on your own chip platform, whether Tuya has a supported embedded SDK. In the same way, if you want to use Tuya's modules on other platforms, it also depends on whether the platforms supports the embedded SDK.
The best position of the pull-down resistor is between the copper skin of the network where the IO port is located and the GND.
The antenna gain differs from the modules. Please refer to the module specification for details, https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The low power mode of Wi-Fi is achieved by powering off the module, so that the module cannot always maintain a heartbeat connection with the MCU, and there is no heartbeat packet.
Wi-Fi low-power sensor devices, APP shows that they are permanently online, and there is no concept of offline.
The parameters of different modules are different, please refer to the module specification page for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The parameters of different modules are different, please refer to the module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
DRX: indicates discontinuous reception. However, to hardware products, it is continuous reception. Data can be received at anytime. The DRX mode has the highest power consumption. The standby power consumption is about 1 mA. eDRX: indicates that the network is connected for a while and disconnected for a while. When the network is connected, data can be received. When the network is disconnected, data cannot be received. The network interruption time is configurable, ranging from 10s to several hours. In eDRX mode, the standby power consumption is about 0.2 mA when the network interruption interval is 5 minutes. PSM mode: The network is disconnected at several days intervals. When the network is connected, data can be received. When the network is disconnected, data cannot be received. In PSM mode, the standby power consumption is microampere-level, and a battery can be used for five years.
Because it is a low-power product, it is smaller than Wi-Fi products in terms of response speed and transmission bandwidth.
The main advantages of NB-IoT communication products are: long distance, large connection volume, and low power consumption.
PSM (Power Saving Mode): The terminal is in deep sleep status and does not accept downlink data. Only when the terminal actively sends uplink data will it accept the downlink data buffered by the IoT platform. DRX (Discontinus Reception): The terminal detects whether there is downlink service once every DRX cycle. Please note that the DRX cycle is determined by the operator and depends on the APN service eDRX (Extended DRX) handled by the SIM. During each eDRX cycle, only one end of the time window monitors the paging channel according to the DRX cycle, and the rest of the time is in sleep mode.
Example: "Single status data unit" MCU report example: DP point 109 bool type variable, the value is 1 55 aa 00 08 00 0c 00 00 00 00 00 00 00 6d 01 00 01 01 d1.
If the network status of the module changes, it will actively send to the MCU to notify the current network status: Search for NB network-0x01; Search for NB network-0x02; Connected to the telecom platform, the device is not bound to:-0x03; Device Has been bound and connected to Tuya Cloud: -0x04.
Example: DP point 109 bool type variable, the value is 1. DP point 102 string variable, "201804121507" (specific transmission corresponding to ASCII value) 55 aa 00 08 00 1c 00 00 00 00 00 00 00 6d 01 00 01 01 66 03 00 0c 32 30 31 38 30 34 31 32 31 35 30 37 a7.
Query product information, that is, product id: corresponding to the Tuya developer platform PID (product identification), which is generated by the Tuya Cloud developer platform and used to record product-related information in the cloud. The MCU responds to the module pid, and the module will register this product information to the cloud.
Example: DP point 109 bool type variable, the value is 1, 55 aa 00 05 00 05 6d 01 00 01 01 79.
MCU sets the NB module sleep lock: 55 aa 00 b2 00 01 01 00.
MCU sets the heartbeat interval time of the module: 55 aa 00 b3 00 04 00 00 0e 10 da (set the heartbeat interval to 1 hour).
MCU obtains whether the query module has been bound by the user: 55 aa 00 bb 00 00 0a,.
MCU queries module NB network strength: 55 aa 00 0b 00 00 0a.
Yes, the MCU obtains the local time: 55 aa 00 06 00 00 05. Get the local time.
MCU sends: 55 aa 00 03 00 00 02; module returns: 55 aa 00 03 00 00 02, indicating that the reset is successful.
Example: The module issues a control command: (The system switch corresponds to DP No. 3, uses a bool variable, and the startup value is 1) 55 aa 00 09 0005 03 01 00 01 01 13.
05 command word is reported in real time; 08 command word is reported in record type.
Two reasons: 1. Bound: The device has been bound by another person, and the device needs to be unbound so that it can be bound by other accounts. Unbinding requires the APP or the cloud. 2. Not activated: The device has not been activated and needs to be powered on to allow the NB device to connect to the network. Please refer to this link for details.
Yes, but you need to use a DRX SIM card, and select the DRX mode when creating the product on the platform (*not online). The platform will determine which mechanism the product uses based on the reported pid. The NB module that uses the DRX card will not enter the PSM state, and all the data sent can be received. NB modules using PSM cards are not supported, and are determined by the NB hardware characteristics.
The NB module supports the combined reporting. Please view the docking protocol for the format. And the data reported for one frame does not exceed 255 bytes.
It is recommended that when you report more than 2dp data each time, you should use combined reporting, which can save reporting time and power.
After the sleep lock function is turned on, the module turns off the function of entering the PSM. In the state of idel. The module does not enter the low-power state, and can respond to the instructions sent by the MCU in real time; SIM card in DRX mode: Since the two modes use the same firmware, no distinction is made, so to ensure the stable performance of the module. The sleep lock can be opened after the MCU and the module complete the basic interaction; SIM card in PSM mode: If the module wakes up, a large amount of data is reported every time, and the data packet interval is long. In order to prevent the module from entering the PSM low power consumption state before the data is sent, the sleep lock can be opened after the module wakes up, and the sleep lock can be closed after the data is sent (selected according to actual needs).
This heartbeat is the interaction heartbeat cycle between the module and the platform. The default heartbeat interval of the module is 8 hours, the shortest is 2 minutes, and the longest is 1 week.
The time from before sleep to the next wake-up is the heartbeat interval.
Yes, setting it to 0 is equivalent to configuring the heartbeat cycle to 1 week.
A heartbeat of the module will make it consume the traffic about 96Byte to be interactied with the cloud. If you want to avoid the traffic loss caused by frequent heartbeat reporting, you can set the heartbeat interval to 1 week.
NB-IoT modules have a heartbeat interface. Vendors can customize the heartbeat interval, for example, 2 or 4 hours. The heartbeat interval depends on MCU indicators, such as the connection and power-supply time and power consumption. A door lock uses the heartbeat interface to periodically communicate with the cloud to synchronize the door lock status (online/offline).
When PSM type modules report data, they must exist PSM mode. The module can be woken up by lowering PSM_EINT above than 5ms (depending on the measured time). At this time, the 05 command word-real time data report or 08 command word-logged data report (recommended) can be used. DRX type modules can respond to MCU's reporting command in real time; 05 and 08 command word usage details can be found in the general protocol.
If you want to change the product PID or modify some DP points, you need to reset the NB module. The MCU sends a reset command to the module to reactivate the module, and the module can only take effect if the device is not bound to be reactivated.
The number of single network access nodes for the NB module is 50,000 per community.
Tuya NB modules are divided into PSM and DRX type. The two types correspond to two different cloud logics. Please confirm product business type before applying for the module. PSM type module will enter into PSM mode to reduce power consumption, normally used in battery-powered devices, fixed report notification type and can't respond to sending command in real time; DRX type module will not enter low power and respond to sending&receiving data in real time, normally used for power-insensitive devices with real-time control type.
Support offline code remote control, POP.
Confirm whether the MCU has received the command that the module's network configuration status is connected to the cloud when sending the reset command. When the module is not connected to the cloud, the reset command is received and the module is reset. However, the module is not connected to the external network, the reset information cannot be transferred to the background, and the device on the App cannot be automatically removed. If someone else reconfigures the device, the device will be automatically removed if it has not been removed before.
It means general-purpose input/output ports.
Without such permission, device removal must be initiated by the App or the device itself.
Yes. A module's serial port is used for firmware burning. If the module is surface mounted onto the PCB, the module can interwork with the MCU over a serial port.
Bluetooth mesh is suitable for commercial lighting, low-power consumption electrical engineering, and sensors because it has long transmission distance and low power consumption.
Yes.
Number of groups per family: currently no limit; Number of sub-devices in each group: no limit; How many groups can be added to each sub-device at the same time: 8.
Yes, it can be supported.
Nodes on a Bluetooth mesh network are connected in mesh topology.
App operation sends data, but the module does not send data. This is because the NB is in PSM low power consumption mode, and peripherals such as radio frequency reception are turned off, and data cannot be received. The module must actively report data once and interact with Tuya Cloud once, and the issued instruction that was stuck in the last operation will be issued. Multiple dp point operations will send multiple data, and only the latest operation will be sent to the same dp point. If you choose a DRX type product. You can send data every time you click the module.
The idle mechanism is enabled if the NB-IoT device is in PSM mode. Meanwhile, Tuya's general firmware has a command for changing the T3324 time. A large T3324 value can cause the device to frequently experience paging cycles. This will lead to a rise in power consumption followed by a fall. When the T3324 time elapses, the device enters the deep sleep PSM state. Operators may have set the T3324 time when you buy a SIM card for your NB-IoT device. Different APNs have different values and are used for different purposes. For more information, see the following figures. The following figure shows the APNs of China Telecom SIM cards and the corresponding T3324 time. The following figure shows the APNs of China Mobile SIM cards and the corresponding T3324 time.
Enter the homepage of the App and tap「Me」. Tap the「Settings」 icon in the top right corner and tap 「About」 to view the current version number of the App.
Currently, we support a network of 3,200 nodes in theory. If a gateway is required, each gateway supports 64 to 200 nodes (depending on the gateway model). You can increase the number of gateways to support more nodes. There is no limit to the number of nodes if you only use Bluetooth without a gateway.
The general short-range wireless communication technologies are as follows: UWB, NFC, Wi-Fi, Bluetooth, and Zigbee.
Single strand copper wire.
Please check the module datasheet: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Please check the specific values in the module specification: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The parameters of different modules are different, please refer to the module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The parameters of different modules are different, please check the module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The parameters of different modules are different, please refer to the pin definitions in the module specification: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The packaging of different modules will be different, please refer to the module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Different modules use different chips. For details, please refer to the module specification: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
he dimensions of different modules are different, please refer to the specific module specification for details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
Due to the openness of wireless signals, different wireless devices may interfere with each other. Therefore, countries have specific requirements and restrictions for Wi-Fi devices regarding the frequency spectrum, radio frequency (RF) power, security, and more. The Wi-Fi devices shall comply with the requirements of the country or region where they will be sold. Different countries have different requirements for Wi-Fi channels. For example, the Wi-Fi channels numbered 1-13 are supported by China and Europe (European routers can be used directly in China), while North America supports channels numbered 1-11 and Japan 1-14. When you apply for a module license, a country code is written into the flash. After the device is started, the country code will be read, and the original API is called to set the channels and related parameters. (Note: If you choose the wrong country code, the device may not be able to match the network successfully).
Network modules are a series of Tuya-developed modules with ultrahigh cost-effectiveness. They support multiple communication protocols, dimensions, operating temperatures, and soldering modes. Network modules are widely applicable to the communication or voice scenarios of various IoT-enabled devices and provide flexible development solutions.
This is because the update is not for the MCU or firmware, but the JSON configuration file of the firmware.
Wi-Fi, Bluetooth, Zigbee, UWB, Wi-SUN, Matter, Sub-GHz, LoRa, Thread, Amazon Sidewalk, NB-IoT, LTE (4G), GNSS, third-party 4G modules.
Lighting, electrical devices, sensors, home appliances, and more.
NB-IoT modules are classified into the PSM and DRX types. The two types correspond to different cloud logic and authorization but have the same firmware version. PSM NB-IoT modules will enter the PSM mode to reduce power consumption and are usually used for devices powered by batteries. PSM NB-IoT modules report notifications at a scheduled time and cannot respond to received commands in real time. DRX NB-IoT modules will not enter the low-power mode. Such modules respond to uplink and downlink data in real time. They are usually used for devices that are insensitive to power consumption.
IoT SIM cards are bound to devices. One IoT SIM card can be bound to only one device. However, one device can be bound to multiple SIM cards.
An NB-IoT module supports the direct connection and non-direct connection solutions.
(1) The SIM card is not inserted or is incorrectly inserted. (2) The SIM card authorization fails. (Check whether the IMEI is normal using the module debugging assistant.) (3) A China Telecom or China Mobile SIM card is used, but direct connection, that is, the tuya connection method, is selected. Change the connection method to ISP.
Yes. When the heartbeat period is 8 hours, the RTC can be set to 5 minutes to report record type data. This is applicable for fire alert detection.
The NM1-CT module whose firmware version is later than 2.0.6 supports local timing. The NM1 module whose firmware version is later than 3.1.8 support local timing. The NM1-GL module whose firmware version is later than 1.1.0 support local timing.
The MCU SDK determines the pairing status of an MCU based on the return value of mcu_get_nbiot_work_state().
When the sleep lock is enabled in DRX mode, data can be reported and sent in real time. When the sleep lock is enabled in PSM mode, data sent by the App has a delay. Only when the MCU reports data, the data sent by the App is sent to the module.
An IMEI is used to identify a device, and an IMSI is used to identify a mobile subscriber and the operator with whom the subscriber holds an account.
The NB-IoT protocol is special. When the NB-IoT module sends a command to the MCU, the MCU needs to first reply to the module with a 55 aa 00 09 00 00 08 message and then report the DP status.
The NB-IoT module needs to connect to a GNSS module because the NB-IoT base station supports rather low LBS accuracy.
The host does not process the data frames sent by the module. (The protocol data frames of the module debugging assistant are incomplete.).
The power domain of the serial ports on the NM1 module is 1.8V. To connect to an MCU with 3.3V output, use a level translator, triode, or MOSFET for voltage level translation.
You must perform an incremental OTA update for an NB-IoT module. Otherwise, the update fails.
Enter the IMEI on the module or scan the QR code.
(1) The power supply of the module is abnormal. (2) The SIM card is reversely inserted. (3) The corresponding service is not activated for the SIM card. (4) The firmware mode is consistent with the service activated for the SIM card. (5) The region is not covered by the NB-IoT network, which is the least possible cause. (6) The SIM card has been bound to a device before and cannot be bound to other devices. Contact the operator. PS_REG_DENIED is displayed in the logs if this is the cause. (7) The PSM mode is selected during product creation, and therefore, this mode is also used for the authorized module firmware. In this case, the use of the App is affected even if the PID is changed in the MCU, and you need to purchase a module in DRX mode.
After the NB-IoT device receives an unbinding command or a reset command, it connects to OneNET through the LwM2M protocol, clears record type data, resets the ICCID, and resets the heartbeat interval and the interval for record type wakeup to 8 hours.
Tuya NB-IoT modules support the 3GPP Release 14. Therefore, it will support positioning as long as operators' base stations support positioning. However, operators' base stations do not support positioning for the time being.
If the peripheral circuit is not affected and required test points are led, the assembled modules can be directly flashed on boards.
For more information, refer to local timing DPs of lighting products that use the Bluetooth mesh general integration solution.
Currently, Tuya uses Telink or PHY+ Bluetooth mesh solutions.
Yes. In offline state, the 0xE0 command is used to report data. A module can store 63 data records. The BK3432 module can store only 23 data records.
The software is based on Bluetooth 4.2, which complies with the mesh 1.0.1 standard. The module TLSR825x supports Bluetooth 5.0 or earlier.
The Cloud Development Plans (except the trial edition) generate a bill based on the actual usage volume every month. If the bill amount is within the specified member amount, no extra amount must be paid. If not, the excess part needs to be paid before you can continue to enable cloud development.
Querying the module SN based on the device ID is not supported.
It depends. Currently, most gateways support 128 nodes. For more information, see the manual of the gateway.
Command 08.
20.
It takes about 3 seconds for the module to connect to the cloud service using the power-off EZ mode to connect the firmware in a general integration solution after it is powered on.
When the module is in PSM mode: If the sleep lock is not enabled, the device will go into the sleep state and enter the low-power mode after data is transmitted. If the MCU needs to send data again, you must use the PSM button to wake up the module and send data again. If the sleep lock is disabled, the device will not go into the sleep state. If the MCU has data to be sent, the MCU will enable the sleep lock and enter the low-power mode after all data is sent.
When a device is powered on for the first time and connected to Tuya IoT Cloud, you must activate the device and download the schema before you can bind the device.
Operators require one-to-one binding of SIM cards and devices for property protection and security reasons. One SIM card can be bound to only one device IMEI. Check whether your SIM card is overdue and ensure that the SIM card has not been used for any other device.
Check whether the heartbeat interval is set to 0s. The default heartbeat interval of NB-IoT general-purpose firmware is 8 hours. See the following table for more other heartbeat intervals. Heartbeat interval Effect Remarks 8 h (default) 8 hours is required for the device to switch from PSM to Active. 0s 604800s (7 days) is required for the device to switch from PSM to Active. This is where misoperations often occur. 1–120s 120s is required for the device to switch from PSM to Active. 120–604800s The specified number of seconds is required for the device to wake up. More than 604800s 604800s (7 days) is required for the device to switch from PSM to Active. Note: If the heartbeat interval is set to 0s, it takes 7 days for the device to become Active, and no heartbeat messages will be reported within this time frame.
Yes. To do this, you can use DRX-compatible devices. Make sure that: You use a DRX-compatible IoT SIM card. You select DRX as the power consumption type when creating the product on Tuya IoT Platform. The power consumption type in the product information returned from the MCU is DRX.
Analysis: After unbinding is completed in the app, the cloud fails to send the unbinding information to the module due to network issues, causing inconsistent binding states between the local module and the cloud. Solution: If the network status of an NB-IoT device is Bound when it is actually removed, you can initiate an interaction with Tuya IoT Cloud to synchronize unbinding information by using one of the following methods: Try to report data to the platform. The data reporting will fail and the network status changes from Bound to Unbound (recommended). Have the MCU send a reset command to reset the NB-IoT module.
After an NB-IoT module is woken up, it enters the Idle state and enables the Active-Timer when it does not send data. If the Active-Timer times out, the terminal enters the PSM mode.
The NB-IoT module starts discovering networks after it is powered on. A used NB-IoT module will enter the sleep mode if it detects that the signal is weak within one minute or it fails to connect to the base station for two minutes. When used for the first time, an NB-IoT module will enter the sleep mode if it fails to connect to the base station for six minutes.
The reason may be that the cloud and the app fail to implement data synchronization due to network issues. A locally reset NB-IoT module will send an unbinding request to the cloud. The cloud synchronizes the information of unbinding to the app.
The cloud considers a device offline if it does not receive a heartbeat message or other data from the device within three heartbeat cycles. The offline status is synchronized to the app.
Check whether thecameraobject is created. Check the error message that is returned in thecameraInitFailed:callback. Ifnilis returned for thecameraobject, check whetherp2pTypeis1. Ifp2pTypeis1, importTuyaSmartCameraT. This module is no longer maintained. We recommend that you contact the manufacturer to update the IP camera (IPC) firmware. Check whether a peer-to-peer (P2P) connection is created.startPreivewmust be called after the callbackcameraDidConnected:is executed.
When you use the IPC SDK to develop or control the talk feature, call enableMute. During the video recording, you are required not to turn on or off sound or use the talk feature.
This error may occur because the hard decision decoding of some mobile phone models does not support the resolution of H.265 code streams. We recommend that you upgrade the App IPC SDK to 3.34.6 or above. Decoding compatibility is supported by new versions. If hard decision decoding is not supported, soft decision decoding will be performed.
Check whether the error message Terminated due to signal 13 is returned. Add the following code block to main.m: int main(int argc, char * argv[]) { @autoreleasepool { struct sigaction sa; sa.sa_handler = SIG_IGN; sigemptyset(&sa.sa_mask); sa.sa_flags = 0; if (sigaction(SIGPIPE, &sa, NULL) 0) { perror("cannot ignore SIGPIPE"); return-1; } returnUIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); } }.
The buttons and indicator lights are both active low by default. When the button is pressed, IO is low. The indicator light is on when the IO port is low level. Just refer to the schematic diagram provided by Tuya.
Tuya Bluetooth mesh serial protocol architecture is as follows. Note: After receiving the module, make sure the module works properly before encoding. In the MCU simulation mode, the debugging assistant simulates the MCU to automatically respond to the module with the correct protocol data. After you pair the module with the mobile phone, you can test DP data reporting and sending. You can get familiar with the protocol interaction process while verifying the module, which will enhance development debugging efficiency in subsequent stages. The connection between the simulated MCU and the Tuya module is as follows: Procedure This section describes the steps of operating the assistant and pairing the module. For more information, see Module Debugging Assistant. Based on the schematic diagram of the minimum system, you build the peripheral circuit of the module and jump the wire directly in case of simple testing. Open the debugging assistant in the development documents, and import the debugging file. Select the Bluetooth mesh general protocol and MCU simulation mode. Connect the module serial port to the computer through a USB-to-TTL adapter, and select the corresponding serial port, and baud in the assistant. After you open the serial port and click Start, and the module will automatically proceed with initial protocol interaction with the host. Note: The Bluetooth mesh module will constantly send heartbeat packets after power on. When receiving the correct response, it will proceed with the initial protocol interaction. If the module does not send data after power on, check if the peripheral circuit of the module is correct. Click Reset in the Distribution Network Function area and the module enters network pairing mode. The module will disconnect Bluetooth, remove Bluetooth binding, clear cache, and then reboot.
The parameters in the timeRange method (point of time: timestamp, length: the number of seconds) show time data.
On-board antennas and external antennas cannot be used at the same time. The attached figure takes the CBU-IPEX module as an example, where the CBU-IPEX on-board antenna is suspended and must be connected to an external antenna for use.
You can view the details to purchase and activate: https://www.tuya.com/vas/commodity/IOT_CORE_V2.
It takes one or two business days to review an IoT Core renewal application.
In the parameters of the request, the interval between startTime and endTime must be greater than one hour.
If the hardware is notified to enable the privacy protection mode, it disables P2P preview, local storage, and cloud storage. The functions are still available. The logic on the client is to disable the UI. You can implement the privacy protection mode by disabling the streams UIs.
Tuya's security module is a type of security solution that integrates both software and hardware to defend against high-intensity attacks on the software and hardware. It encrypts chips to protect the code from replication and reverse engineering development. It provides a root of trust for monitoring system recovery and security updates.
NB-IoT devices do not connect to Tuya's MQTT server, but communicate with the operator, who then communicates through Tuya's external NB gateway service. These devices have the following characteristics: NB-IoT devices have a heartbeat cycle setting, which can be configured at the product level or actively reported by the device. If not configured, the default is 8 hours. The ACK, heartbeat, reporting, and request of NB-IoT devices will refresh the online status of the device after being processed by the NB gateway service. The online logic of NB-IoT devices is that if the cloud does not receive any requests to refresh the online status of the device from the NB gateway service within three times the heartbeat cycle, the device is considered offline. For example, if the heartbeat cycle is set to 8 hours, the device will be set to offline if no message is received within 24 hours. The offline logic of NB-IoT devices.
The Tuya smart camera project docking solution is provided by our company with an App SDK. The docking manufacturer will embed the SDK into the camera firmware to realize the product access to Tuya platform. Tuya SDK is divided into two parts, one part is the public functions such as login and registration, message push, network distribution and other functions. For this part of the SDK, please refer to: https://developer.tuya.com/en/docs/iot/app-development/sdk-development/deprecated-topics/app-sdk-creation-instruction?id=K989rt8rm8lc6 The camera depends on the public part of Tuya, so if you need to integrate the camera in the APP, please connect the Tuya public sdk first, the camera related SDK reference: iOS: https://developer.tuya.com/en/docs/app-development/ipccamera?id=Ka5vexydbwua5 Android: https://developer.tuya.com/en/docs/app-development/overview?id=Ka6km92o4do96.
For legacy versions, when p2pType is 1, the app might crash after the destory method is called. This problem has been fixed in SDK v3.1.1 and later versions. Before destory is called, stop the preview or callback operation and call disConnect to stop a P2P connection.
This problem is caused by the conflict with the version of FFmpeg multimedia framework library. You package the existing video playback library into a dynamic library to fix the problem.
The simulator does not support the hardware decoding mechanism of certain IPCs. To fix this problem, use a real device for debugging instead.
Before you redirect to the page, call the getHomeDetail API.
Call the setCloudMute() function during initialization.
Currently, an IPC supports only the H.264 and H.265 video encoding methods.
Multi-view preview is dedicated to real devices, and virtual devices are filtered out. Even if an account has multiple virtual devices, only one preview view is displayed on the multi-view preview page.
When your mobile phone is disconnected or encounters a power failure, sessionChange is called back. For more information, visit https://developer.tuya.com/en/docs/app-development/livestream?id=Ka6nuvynnjk7h#title-7-Link%20code.
The TuyaSmartP2pChannel class is contained in the TuyaSmartP2pChannelKit SDK.
"The camera opens the device details interface and prompts "the device is not compatible". If the TuyaSmartCameraType instance object is a TuyaSmartCameraTutkImp object, our device control business package does not support it, and you need to develop the device interface yourself.".
When the IPC device logs out of the App, it must call: [ThingSmartCameraFactory userDidLogOut];.
We recommend that you contact the manufacturer to check whether the timestamps of audio frames match the timestamps of video frames.
Before playback is started, the API request must be made to return the SD card-stored video clips generated on the current date. Make sure that request parameters are correct.playTimemust bestartTimeor later, and be earlier thanendTime.
Service purchase link：https://www.tuya.com/vas/commodity/IOT_CORE_V2 Product Pricing Description：https://developer.tuya.com/en/docs/iot/membership-service?id=K9m8k45jwvg9j#BasicConnection.
We build white-label Tuya apps, IoT dashboards, and custom integrations for your business.
🚀 Schedule a Call