Browse the most common questions and expert answers about Manufacturing on the Tuya IoT Platform.
When performing an OTA upgrade on an MCU, the time interval for sending the upgrade package is not directly related to the defined size of a single package. The key factor is the speed of the MCU's response: after the module sends a package, if the MCU can immediately respond to the current data package, the next package will be sent immediately. Therefore, the actual upgrade time depends on the MCU's response speed, rather than simply the package size. To estimate the upgrade time, it is recommended to follow these steps: 1. Use a bare module to simulate the MCU and test the interaction during the OTA upgrade process. 2. Add log output during the upgrade process to observe the details of sending and receiving. 3. Note that the MCU needs to respond within 5 seconds after receiving a package to ensure the smooth sending of the next data package. 4. Test the performance under different hardware environments and network conditions using a debugging assistant, as these factors may affect the overall speed.
In low-power device scenarios, the MQTT+HTTP protocol can be used to determine whether a device is online or offline. The specific operation method is to judge through the BizCode of the message queue: when the BizCode is online, the device is in an online state; when the BizCode is offline, the device is in an offline state. Configure the message queue to receive device status messages. Devices that are permanently online are usually not considered offline and can be checked by re-networking. Low-power devices need to be temporarily online to receive status messages, and battery-powered devices usually need to be powered under specific conditions to listen for messages.
Device logs show instructions originating from the "cloud," which may come from cloud systems or backend automated tasks. Possible scenarios include: 1. Automated scenarios: such as scheduled tasks automatically triggered. 2. Smart scenarios: user-configured smart scenarios triggered in the cloud. 3. Remote control: instructions directly issued through cloud interfaces or management backend. The specific methods to check the trigger reasons for these instructions are as follows: 1. Device Log Analysis: Check the time and source records of the triggered instructions in conjunction with device logs. 2. Troubleshoot Automation and Smart Scenarios: View the settings of automated scenarios and smart scenarios associated with the device to see if they correspond to the trigger conditions within the time period. 3. Check Cloud Configuration Changes: Verify whether there have been any changes to automated tasks or other cloud configurations recently. 4. API Interface Troubleshooting: Instructions triggered by calling cloud API interfaces will also show as originating from the cloud, and further analysis of interface logs and call records can be conducted. Note: "Source details" being empty may be due to technical limitations or data synchronization issues leading to unrecorded information. In this case, a comprehensive analysis using the above methods is needed to find the specific source of the instructions.
In the SaaS project of the cloud development platform, devices cannot be directly added to the project for monitoring through the OEM App. OEM App and Smart Space belong to different systems, and devices under the OEM App cannot be displayed within the SaaS system. Devices within the SaaS project need to be added through the Smart Space App, and the ownership of external application devices belongs to the owner of the external application. The cloud project owner only has permission to view the device status. For detailed content of the solution, please refer to this document:Link Devices.
The general steps to resolve the issue of deleting a project are as follows: 1. Confirm that the project has no dependencies, such as other functions or modules being used. 2. Access the project management interface and check if there is an option to delete the project. 3. Check user permissions to ensure you have administrator rights to delete the project. 4. Clear the project cache, then try to delete the project again. 5. If the project still cannot be deleted, it is recommended to check for any system limitations or errors. If there are any, contact technical support for assistance in resolving the issue.
If you receive a "No Permission" error message, it is usually because the subscription has expired. You need to clear all data center information, save, and then reselect the required data center to help re-enable the data center for continued use. The specific steps are as follows: 1. Clear the data center information and save. 2. Reselect the required data center. 3. Apply for an extension of the trial period, and it is recommended to wait 2 hours after the application is approved before attempting to call the interface. 4. If the error still occurs after waiting for more than 2 hours, you can provide feedback on the issue again.
If you are referring to the MCU version number in the 0x01 command, then the same PID number and DP points will not affect the use and debugging of DP function points. However, if serial communication cannot be performed normally due to the inconsistency of the actual model of the MCU, it is recommended to contact the manufacturer of the MCU for troubleshooting and resolution.
Currently, both the Bluetooth and Zigbee modules will return a confirmation message to the MCU after receiving the DP point reported by the MCU, indicating whether the reporting was successful. The Wi-Fi module can use the synchronous reporting command: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-17-%E7%8A%B6%E6%80%81%E4%B8%8A%E6%8A%A5%EF%BC%88%E5%90%8C%E6%AD%A5%EF%BC%89(0x022).
For tutorials on MCU SDK code logic, please refer to the Serial Protocol Center: https://developer.tuya.com/en/docs/mcu-standard-protocol, specifically the documentation on MCU SDK porting in the corresponding protocol directory.
MCU emulation is used to simulate an MCU, enabling communication with a real module. It is typically used to test the interaction flow between modules. Module emulation is used to simulate a module, enabling communication with an external MCU. It is typically used to debug whether the MCU code can interact correctly with module instructions.
When using the debug assistant to connect to the WBR3 module, a remote service failure popup appears and the start debugging button turns gray. Solution: 1. The error at the start of the debug assistant does not affect normal debugging, and users can ignore this error. 2. Check the wiring, especially whether the wiring of the serial version and the module tx is correct. 3. Confirm the delivery method selected when ordering the module on the platform: - If "empty delivery" is selected, the module does not have firmware and needs to be flashed with firmware to be used normally. 4. If you have any other issues or questions, you can always contact ticket support for further assistance.
MCU docking development, the module will actively send commands when powered on. The MCU needs to reply before continuing interaction. If the MCU does not receive data, check whether the hardware and wiring are normal.
Currently not supported.
To be transmitted.
Hello, the "Scenes" in the mode settings are the factory preset configurations of the product. If these preset scenes cannot meet your personalized needs, you can feed back the specific issues to the seller to facilitate subsequent product optimization. Thank you for your support and understanding.
Tuya cloud servers can be deployed in multiple data centers to meet the business needs of customers. The Asia-Pacific nodes include Tokyo, Japan, but whether they meet the specific needs of customers needs further discussion. Tuya ensures the security of data and the speed of service.
If you need to use the MCU SDK development method, please select the custom solution when creating a product, instead of the zero-code solution. The zero-code solution does not support the MCU SDK access method.
When using the API to obtain user information, if only partial user information can be obtained, you can troubleshoot and resolve the issue by following these steps: 1. Confirm the API call for user information and ensure the parameters are set correctly, such as the correct start_time/end_time. 2. If the device ID does not appear on the platform, you need to switch data centers, such as switching to the EU data center. 3. When calling APIs from different data centers, you need to change the domain address. Refer to the documentation for specific domains:https://developer.tuya.com/en/docs/iot/api-request?id=Ka4a8uuo1j4t4#title-1-Endpoints. 4. If more precise geographic location information (latitude and longitude) is needed, you need to remove the device through the mobile app and re-add it. 5. If the API call takes too long or is unsuccessful, check your code for errors. 6. When errors occur in calling APIs from other regions, ensure you are using the data center paired with the device. 7. For devices that have been removed, you need to re-add the device and test again.
To send scheduled data directly to the MCU without needing a gateway, you need to add a custom function point to the current product. The specific steps are as follows: 1. Customize a function point for scheduled data. 2. Use this custom function point to pass scheduled data transparently to the MCU for execution. 3. Further development is needed to adapt the panel, as the current public version panel does not support this feature. A custom panel needs to be developed to achieve the function of sending directly to the MCU. The current weekly scheduling function point can only be scheduled through the cloud, requiring the device to be connected to the gateway. However, through the development of custom function points, it is possible to send scheduled data directly without a gateway.
The DP toggle switch is quite special. The module receives the ASCII code corresponding to the base64 encrypted string from the cloud, so when the device receives this DP data, it needs to perform base64 decryption first. Protocol parsing of the toggle switch: The first byte:bit0 corresponds to on or off, bit1-bit7 corresponds to which channel (bit1-bit7 needs to be converted to decimal); The second and third bytes correspond to time, in seconds. For example: After decrypting BQAF, it is 05 00 05, the first byte 05--0000 0101 channel 2 on, the second and third bytes are time 5s. After decrypting BQAFBwAC, it is 05 00 05 07 00 02, two sets of toggle settings, the first set channel 2 on for 5s; The second set 07 00 02, 07--0000 0111, channel 3 on for 2s. Note: Channels generally start from 0, so channel 2 actually corresponds to switch three.
The old version of the debugging assistant will report this error, closing the error does not affect normal use. We recommend using the debugging assistant in the production solution tool, which is constantly updated. Refer to the documentation for downloading the production solution tool:https://developer.tuya.com/en/docs/iot/SCJJ-01?id=Kcpv15oujgz00.
Using UTF8 encoding, the app panel sends in hexadecimal, and the MCU parses it upon receipt.
Solution: 1. Copy to generate a new PID; 2. In the new PID, select "03 Hardware Development", and click "Replace Hardware" in the right sidebar; 3. In hardware selection, choose a replaceable module; Note: Module selection can be based on the requirement to use a module with an onboard antenna or a module with an external IPEX antenna (external antenna needs to be purchased from the antenna manufacturer); 4. Finally, generate new production materials. You can operate through the following link:https://platform.tuya.com/purchase/mop/list. If there are still issues following the above operations,you can contact support personnel through a ticket for further assistance.
Currently, Huawei HarmonyOS NEXT (pure HarmonyOS) app and device panel are undergoing iterations of related supporting capabilities, so unsupported device panels will be loaded onto the basic panel, which is a normal phenomenon. Currently, it is in the stage of public version device panel coverage, and only some public version mini program panels support the HarmonyOS app. Users need to patiently wait for the comprehensive support update of the device panel.
Using two's complement form. For example: -19 Take 8-bit binary as an example, calculate the two's complement of -19, steps are as follows: Step 1: Determine the 8-bit original code of +19 Decimal to binary conversion of 19: 16 + 2 + 1 = 19 → Binary is10011 8-bit original code needs to fill in high-order 0, so the original code of +19 is:00010011(The sign bit is 0, indicating a positive number, the last 7 bits are value bits) Step 2: Find the 8-bit original code of -19 The original code of a negative number = sign bit (1) + value bits of the positive number, so the original code of -19 is:10010011(The sign bit is 1, indicating a negative number, the last 7 bits are the same as the value bits of +19) Step 3: Find the 8-bit inverse code of -19 The inverse code of a negative number = sign bit unchanged + value bits inverted (0→1, 1→0) -19's original code value bits are0010011(last 7 bits), after inversion is1101100so the inverse code of -19 is:11101100(The sign bit remains 1, the value bits become the inversion result) Step 4: Find the 8-bit two's complement of -19 The two's complement of a negative number = inverse code + 1 -19's inverse code is11101100, after adding 1:11101100 + 1 = 11101101 Final Result The 8-bit two's complement of -19 is:11101101 If other bit lengths (such as 16-bit, 32-bit) two's complement are needed, just extend the high-order value bits after the sign bit (fill 0), and then calculate according to the above steps. For example, the 16-bit two's complement is:11111111 11101101.
I suggest you first check the phone's cache and try replacing the phone to rule out slow screen loading due to cache or hardware issues. If the problem persists, it is recommended to upload the APP log to confirm whether there is a compatibility issue with the phone system. After the log is uploaded, device data analysis found that the device error reported pseudo data, please check the data on the MCU side again. For data that does not need to be synchronized, you can choose not to transmit it after the device is powered on to improve response speed.
When configuring the module for the first time, if the signal search time extends from about 10 seconds to over 30 seconds, possible solutions are as follows: 1. Check if the module has correctly entered the network configuration standby state; 2. Open the APP for device search after the module enters the network configuration standby state; 3. Confirm the test video, which should show the device reset process and entering the network configuration standby state; 4. Compare multiple test results to confirm whether each device search takes 30 seconds; 5. If the search time is longer only during the initial configuration, try unbinding the device and configuring it again; 6. Provide the test video to the technical support team for further analysis, including videos of the device entering the network configuration standby state and the APP search process. If the issue is not resolved after the above steps, please submit a ticket for further support.
The failure of the Bluetooth module's reporting is usually related to the module's network status. Ensure the module is in a connected state; otherwise, it cannot process reporting commands normally. When the module is disconnected, the MCU reporting will fail, so it must be ensured that the module is connected to the network before reporting.
To enable the module to enter network configuration mode, first confirm whether the module has already entered the network configuration state. If the module is not in the network configuration state, you can send a reset command via the MCU to let the module re-enter the network configuration state. If the module has been powered on for a while but cannot find the network configuration information (code 03), it is recommended to print the module log to check the issue. You can directly connect the pin to print instead of using a command to open debug. If the current firmware version is outdated (such as 2.1.6), it is recommended to use the APP for network configuration once, and then upgrade the module's firmware version to the latest version 3.1.69.
Specifically, it can be customized according to the configuration of the platform, and it can be configured to enter the distribution network state or the non-distribution network state when it is powered on for the first time. Sensing products are generally in a non-distributed state, depending on the platform configuration.
Yes, otherwise you cannot call the openAPI. You can purchase a free trial version and renew your subscription after it expires: https://support.tuya.com/en/help/_detail/Kc3n6kr7kllhc.
The programming tool consists of software and hardware tools. Hardware tools can be purchased from the sample store, and software tools can be downloaded from PMS. Refer to the following document: https://developer.tuya.com/en/docs/iot/SCJJ-01?id=Kcpv15oujgz00.
Please see the attached code: 📎 PHP_Demo_Test.zip.
Please refer to the attached code 📎 PHP_Demo_Test.zip.
After creating a product on the platform and adding features, click Next. On the Device Interaction page, you can select a device panel for your product. We provide four types of panels: For details, see What kinds of panels are available for products created on the Tuya Developer Platform?
The data displayed on developer platform is 24 hours ago, please query every other day.
Tuya Cloud Development Platform is an open IoT cloud platform that provides various cloud services including OpenAPI for application developers, equipment manufacturers, and solution providers. IoT SaaS applications can be quickly developed for "Powered by Tuya" devices. Click to see how to quickly develop on the cloud development platform to realize the control of smart devices. If you want to link devices, Tuya Smart, Smart Life or OEM App to your cloud project, you need to choose Smart Home PaaS when you create the project. If you choose Custom Development, it is not possible to make quick associations. 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. You need do account verification. If you are reminded that you cannot add devices across regions/data centers when adding devices, you need to add the corresponding data centers in your cloud development project:.
This is because your personal information is incorrect. If you receive a message indicating that your identity verification on the Cloud Development Platform fails due to a wrong mobile phone number, name, or ID number, Verify in your mobile phone business hall app or at the business hall whether the current mobile phone number is the one you registered by using your ID card number. At present, the IoT platform only supports the use of my ID card to open identity verification，and a person can only authenticate an account. Note: IoT accounts are only available for mainland China. For accounts outside of mainland China, please click: How do overseas and China Hong Kong, Macao and Taiwan region developers conduct organization verification?
Not supported.
Indicates the instruction issued through the open API.
If you are adding a new standard function point, you need to remove the device, clear the app cache, and reconfigure the network. If it still doesn't display, you need to confirm whether the added function point is related to other function points. For example, in lighting products, the white light and color light function points need to be added together with the work mode function point to be displayed. If you cannot determine, it is recommended to add all function points for testing. If you are adding a custom function point, you need to confirm whether the current panel supports custom function points. Some panels that support custom function points will display them on the settings page. You can check if they are displayed on the settings page. If not, it means the panel does not currently support custom functions.
Currently, the open platform does not support IPV6 IP addresses.
Debug assistant error, need to download again.
The refresh_token remains valid until it is updated.
Hello, we are sorry, we are currently unable to provide the UI design files for the all-in-one panel. If you have any requirements regarding interface design, you cancommunicate in detail with Tuya's business personnel to assist in handling your needs.
The service's IP will change dynamically, it is not recommended to reference it.
No charge.
Hello, we currently do not provide source code files for public panels. If you need to develop a panel, you can refer tocustom panelsfor development.
Support, please refer to the documentation:Production Resource Pool.
When the module reports the network status as 6, open the APP to scan the code for binding. Note: The QR code needs to be generated by yourself, you cannot directly use the QR code on the module. There are two ways to obtain the QR code: 1. Debugging stage: You can set the "Qr" field in the product information command to 1. When the module's network status changes to 6, the module will issue the hexadecimal data of the URL through the 0x72 93 command. The developer needs to convert it into a string and then use a QR code conversion tool to convert it into a QR code. Example: a: Set Qr to 1, and after setting, please power the module on again. Note: If there is no "Qr setting" after opening the debugging assistant and selecting the Cat.1 protocol, you need to download the latest version of the debugging assistant. Please refer to this document:https://developer.tuya.com/en/docs/iot/SCJJ-01?id=Kcpv15oujgz00Download the production solution, and then get the latest version of the debugging assistant in the production solution: b: After the module reports the network status as 6, the module issues the URL data: c: Convert hexadecimal to string d: Use an online tool (e.g., Grass QR Code) to convert the URL into a QR code: 2. Production stage: Please change the Qr field to 0, refer to this document:https://developer.tuya.com/en/docs/iot/code?id=Kc0nc66niv9loInstall the required software (Bartender software must be activated, otherwise it cannot be used normally), use the upper computer to print the QR code, where the input parameter type can choose authorized SN or authorized IMEI. After locking the parameters, use a scanner to scan the laser engraving on the surface of the module.
Refer to the gateway MCU general protocol.
The pop-up appears because your device is a strongly bound device, and it must be removed from the app by the previously bound account before it can be added by another account. You can click to submit an unbinding request on the app, and the product owner will receive an unbinding work order on the developer platform and choose whether to unbind for you.
At the moment of connecting to the gateway, the gateway defaults to the device being online, and then starts performing heartbeat checks. If the heartbeat cannot be detected, it will display as offline. The interval time from showing online on the homepage to showing offline on the homepage is related to the number of devices under the gateway and is not fixed. The more devices there are, the longer the time may be. Clicking on the device panel will directly trigger a query for the device's heartbeat, and if it cannot be detected, a popup will immediately prompt that it is offline.
Pay attention to the DP unit in the conditions. If the DP unit is not seconds, it may cause the automation scenario to fail to execute correctly. Because the app's default save rule is to save in seconds, it is recommended that the device's DP unit is also set to seconds.
You can try using the lowest baud rate of 9600 first. Some MCU models have severe frequency deviation, and the higher the baud rate, the greater the error.
Hello, this is because individual developers or accounts that have not yet passed corporate certification are not supported to use this panel. You need to complete corporate certification first, then you can choose. Shortcut link: Become a corporate user now Operation process:.
Definition of Tuya Cloud devices: All IoT devices connected to Tuya Cloud are called IoT devices of the Tuya solution. Generally, there are the following two situations: 1. Hardware manufacturers, through the purchase of Tuya's Wi-Fi module, on the Tuya developer platform Product function definition, generate finished products by yourself, this kind of IoT device can be called a Tuya solution; 2. Buyers, through Tuya channels, purchase finished products of equipment produced in cooperation with Tuya, this kind of IoT device is also called Tuya solution.
An mcu_sdk package contains the MCU code automatically generated based on the product functions defined on the Tuya developer platform. The communications and protocol parsing frameworks are already available and can be added directly to an existing MCU project to develop an MCU program quickly.
It is recommended to use the SmartLife or Tuya apps for scan code linkage. Self-owned App (OEM App/ App SDK) accounts do not support scan code linkage. Please refer to the following link for linkage. https://developer.tuya.com/en/docs/iot/link-devices?id=Ka471nu1sfmkl#title-2-%E6%93%8D%E4%BD%9C%E6%AD%A5%E9%AA%A4.
Compared to a private cloud, Tuya Cloud possesses the following advantages: 1. With Tuya Cloud, you do not need to worry about technical platform issues, such as server, database, technical team, and service expansion issues. Tuya Cloud is updated each week, allowing you to use new functions with ease. 2. Tuya Cloud helps you save costs hundreds of times over because you do not need to purchase servers or hire technical personnel or ask a third party to maintain the cloud. In addition, a private cloud cannot provide auto scaling, global services, or security protection. If your company does not have strong technical capabilities, the data on your private cloud makes no sense. It cannot go private and is easily lost. Tuya Cloud allows you to obtain your data anytime. 3. The success of Alibaba Cloud and Amazon Web Services (AWS) has proven that public clouds are the trend of the times. 4. If you want to use a private cloud, Tuya provides a hybrid deployment solution, which not only ensures that servers can be deployed in your IDC but also supports rapid iteration of the Tuya developer platform.
Tuya Cloud provides the simple mode (implicit authorization) for cloud-based interworking through OAuth 2.0. Developers can apply for cloud APIs on the Tuya developer platform, call Tuya open APIs based on Tuya's open API specifications, obtain their user and device data, and control devices with permission. In simple mode, developers need to create an OEM App or product on the platform before they can obtain user or device data with their developer account.
A no-code development has the following characteristics: 1. You can select the panel and firmware based on the Tuya and SmartLife App. 2. You can configure hardware items as required. 3. You can directly purchase modules with firmware and design peripheral circuits by yourself without the intervention of project managers, which is more convenient and time-saving. 4. It can cover related categories such as electrical engineering, lighting and sensing.
This event indicates that the device has been disassociated from the originally linked gateway and re-associated with another gateway.
The issuance action is based on the action function of Tuyalink's device, which is an independent function configuration from the attribute function. Therefore, the issuance action interface will not affect the device attribute values.
Please ensure that differential upgrade is selected when creating the firmware upgrade task. If it is not selected, please delete the upgrade task and create a new one. Simply returning to the steps and selecting differential upgrade on the original upgrade task will not take effect.
Most no-code development solution firmware does not have a serial port, and cannot be connected to an external MCU. Some product solutions support serial port connection to meet scenario requirements, depending on the solution. You can create a custom product, please refer to the link: https://developer.tuya.com/en/docs/iot/mcu-access-guide?id=K9hrbv1ub5owo.
You need to delete the associated cloud project of the SaaS project first before you can delete the SaaS project. If the cloud project is not deleted, the SaaS project currently cannot be deleted.
Find the corresponding cloud project in project management, click "...", and then click "delete".
As one of the most frequently-used solutions to connect to the Tuya IoT Console, the MCU connection solution is mainly used to enable products with MCU to be smart. Tuya provides hardware modules, apps, and cloud services. You only need to focus on product function research and development and develop the smart products efficiently and quickly with Tuya MCU SDK, public version app, and panel. Please click to view manuals.
Click the "Close" button in the top right corner.
If the frequency of MCU firmware reporting does not exceed the reporting frequency limit, it shall be calculated based on the actual reporting of MCU firmware; If the MCU reporting frequency exceeds the reporting frequency limit, the SDK will limit the reporting frequency according to the configuration here.
Query reporting refers to the cloud or app proactively sensing the device status, sending commands to the device, and after receiving the corresponding command, the device initiates a report; or when dp is issued, it is found that dp has not changed. (i.e., reporting the same value once).
Log in to the Cloud Services - My Subscriptions page to view it, as shown in the image below:.
App schema is the unique identifier of the App application, which is used to associate the uniqueness of the application. Register users using the cloud API, and query users will need this identifier. There are two ways to obtain it: 1. Inquire in the OEM App or App SDK details, the channel identifier is the schema 2. If the App is associated with a cloud project, it can be seen in the associated options.
Subscribe to API products Log in to the Tuya Developer Platform. Click Cloud—API Management—API Products. On the All Products page, click an API product. On the page of API product detail, click Subscribe. On the displayed page, select service and payment method, and click Buy now. Authorize project to call APIs After you subscribe to an API project, you need to authorize projects to call this API. On the page of API product detail, click the Projecttab &rt;New Authorization. In the New Authorization dialog, select a project for authorization. Click OK to complete authorization. (Optional) Click Cancel Authorization to void the authorization of a project to call this API. For more details please see: https://developer.tuya.com/en/docs/iot/applying-for-api-group-permissions?id=Ka6vf012u6q76.
URI parameters are annotated with @Path GET request with parameters, use @Query annotation POST request with parameters, annotated with @Body For the return type, refer to the API documentation for the result field type in the returned data. （Refer to this document for development steps: https://developer.tuya.com/en/docs/iot/device-control-best-practice-java?id=Kat2uf0cwn9k9）.
If the token has expired, the effect is the same. If it hasn't expired, using refresh_token will update the token value and extend its validity period, whereas requesting the current token will not extend its duration.
Save the downloaded JSON file again and re-import it into the debugging assistant.
You need to clear all data centers, click save, and then re-select the required data center.
The replication of the public version panel is actually achieved by copying the product. For the product copying method, please click here to view. After completing the product copying operation, the new product and the original product will share the same public version panel.
Find the corresponding cloud project in cloud development and click Edit: Modify the data center in the popup window that opens.
Embedded development and debugging typically include the following stages: 1. Define the product to be developed. 2. Obtain development components and the corresponding SDK. 3. Debug the program, which includes steps such as compiling, flashing, authorization, running, and debugging. The debugging methods vary significantly between different systems. For example, in a Linux environment, you can use GDB to set breakpoints and trace the execution process; in an RTOS, you can track issues by reviewing logs.
Function nesting can be up to 9 levels deep.
Before selecting the source of the device, please make sure that you have selected the correct region.
The data of string type is sent to the MCU in ASCII code form. After receiving the data, the MCU needs to convert the ASCII code into a string and parse the string to obtain the corresponding command. When the MCU reports data to the module, the operation is reversed.
The module performs an adaptive baud every time it is powered on, that is, it sends a heartbeat at a baud of 9600, then sends a heartbeat at a baud of 115200, and alternates sending until it receives a reply from the MCU. It then fixes a baud rate, and the next time it is powered on, it will perform adaptive baud again. If you are using a common serial port display tool, fixing a baud to detect the data sent by the serial port, then the tool will only display the data decoded at that baud. The data at the other baud will be displayed as garbled, which appears as "the module keeps repeating sending heartbeat, and there will be an extra byte." The extra byte is the garbled display of the serial port display tool at the other baud. Note: The Zigbee module will perform an adaptive baud the first time it is powered on after leaving the factory, but as soon as it receives a reply from the MCU, it will fix a baud, and it will not perform an adaptive baud again when powered on again.
Low power mesh devices must be used with a gateway, non low power devices support direct mobile phone connection and gateway.
Specific device is required to support low power networks, such as Zigbee.
The delay in cloud-to-cloud integration is in milliseconds, which is almost negligible.
1.Once hardware connection, Tuya module is connected to the MCU via serial port. 2. In terms of software functions, the MCU is responsible for parsing the data sent by the module, and controlling the corresponding peripherals, such as relays, motors, etc. through the commands sent by the module.
When you use the MCU universal integration method, Tuya provides a module that has burned the general firmware. The program in the general firmware is only used for the module to communicate with the customer.
Product function is realized by MCU, MCU and module are integrated through the serial port to achieve data interaction and networking.
All communication data between our cloud platform and the device is encrypted using AES. On the basis of AES, it also supports TLS communication encryption. The device uses one machine and one code for security. You can also get more information about our safety certification from the following URL: https://www.tuya.com/en/rule.
Description documents can be provided based on the license pattern. There is no format requirement for redirect_url. If it is a normal http callback address, it will be called back to the server you specified. If it is not normal, it can be called back to the browser to meet localized parsing needs.
No, you need to go to the PMS system (https://pms.tuya.com/ -- Production Management -- Work Order Management -- Production Certificate Confirmation to confirm.
Simple mode and license mode.
In license mode (explicit authorization), a developer uses a cloud API key on the Tuya Cloud platform and then calls a Tuya open API based on Tuya's open API specifications to obtain authorized resource data. Tuya Cloud provides the license mode for cloud aggregation scenarios where there are no OEM apps on the Tuya platform.
Factory reset refers to restoring everything to the factory state. For the central control, it means returning to the system version state, thus displaying the installed APK versions in the installed system, which may be different.
The current time zone online time can be obtained through serial port protocol instructions.
Obtained through the serial protocol command word 20.
Tuya Smart Cloud issues commands to IoT devices mainly through the MQTT protocol for communication.
import hashlib message = bytes(client_id+t+nonce+stringtoSign).encode('utf-8') secret = bytes(secret).encode('utf-8') signature = hmac.new(secret, message, hashlib.sha256).hexdigest().upper().
To add an entry, you need to add it in the platform product's multilingual settings. On the device panel page, download the multilingual file of the current tab, edit the file to add the entry, and then re-import it.
Tuya Smart Wi-Fi module, Bluetooth module, and Zigbee module serial ports are 3.3V TTL level. The TTL level standard output L: 0.8V ; H: 2.4V. Input L: 1.2V ; H: 2.0V TTL devices must output a low level of less than 0.8V, and a high level of more than 2.4V. For inputs, below 1.2V is considered as 0, and above 2.0V is considered as 1. If your MCU operating voltage is 5V, when interfacing with the Tuya module, refer to MCU Interface Hardware Design to add a level shifting circuit.
No, the Wi-Fi+BLE module is primarily based on Wi-Fi. If you only want Bluetooth functionality, it is recommended to directly choose a Bluetooth module, which is also cheaper.
The country code needs to correspond with the respective data center. You can pre-fetch the country code corresponding to the data center by GET {{url}}/v1.0/all-countries, and then select the corresponding url.
To check whether the app location permission is enabled for the device, enable the app location permission and remove the device. After the device is reconfigured, refresh the weather data.
The cloud sends the signing certificate when the robot vacuum is being paired. The file is stored in the local memory. Before the robot vacuum is paired, the data is encrypted with a unique AuthKey.
Dear user, it may be that you have turned on the Cloud Authorization IP Allowlist function. After enabling this function, you can set up a list of IPs that can legally access Tuya's data centers through the IP whitelist function. Requests from source IPs that are not in this list will be rejected. If you don't need to close it.
Not supported.
It can be used at the same time, but it does not support recording.
The outermost asset structure can establish up to 1000 assets, and the total number of all asset nodes does not exceed 10,000.
At present, a project can only configure one data center configuration, and multiple data center addresses cannot be configured.
Because the panel is parsed and displayed according to standard function points, if you have selected fewer standard function points or modified the default values of the standard function points, it will cause the panel to fail to parse and report errors. It is recommended that you reselect all standard function points, clear the app cache and re-add the device to try.
The error is within 1~3 seconds and is related to the network environment.
Because the product does not have statistics configured, you are required to provide your pid and the type of statistics to be activated by submitting a work order.
DIY panels are currently not supported, only modifications to the text of the panels are supported. You can modify it through the following two methods: Method one: In the IoT platform's App--Panel Center--My Panel, find the product panel you need to modify, click View, go to the Multi-Language Management of Product Configuration, and modify it in the tab of Device Panel. Method two: In the IoT platform's App--Product Language, select the product you need to modify at the top of the page, and modify it in the Device Panel tab.
Please confirm if there is an account associated with the device network on the platform. Operation document link: https://developer.tuya.com/en/docs/iot/link-devices?id=Ka471nu1sfmkl.
Distinguish between network distribution not exceeding 15 minutes and exceeding 15 minutes; Network distribution not exceeding 15 minutes: Remove the network distribution, wait for 10 seconds, power on again, and scan the production test signal to enter the production test. Network distribution exceeding 15 minutes: Need to re-burn the authorization.
There are three reasons: 1. The linked App account is not the device's networking account. 2. You chose manual linking, and devices are not automatically linked. 3. The device name contains words like "Telecom Xiaoyi Edition," indicating that the device is customized by the operator, and the data is not in Tuya. You cannot obtain device data and need to consult the device seller.
At present, you can apply for the IoT Core trial version free of charge for up to 6 months. After the expiration, you can continue to apply for an extension. After the API calls exceed the monthly free quota, access will be restricted. Wait for the next month to refresh the quota or purchase a more advanced IoT Core version . Some industry services and PaaS services have separate billing prices, which require additional charges. You can view the following documents: https://developer.tuya.com/en/docs/iot/membership-service?id=K9m8k45jwvg9j IoT Core：https://www.tuya.com/vas/commodity/IOT_CORE_V2.
7200s.
You must ensure that the network of the Tuya plugin for Homebridge installed on your computer and the Wi-Fi to which your mobile device connects is in the same LAN.
For more information, see https://github.com/tuya/tuya-homebridge/wiki/Supported-Tuya-Device-Types?_source=6a1b8046224626e798190c06532c8be2.
For more information about data center selection, see https://developer.tuya.com/en/docs/iot/oem-app-data-center-distributed?id=Kafi0ku9l07qb.
If the project industry of the device is Smart Home, make sure that Smart Home is selected as the method of cloud development. If Custom is selected as the development method, the device cannot obtain the video stream.
We have dedicated servers outside China to help reduce the network delay. If your server is located outside China, but your device is in China, the network delay is inevitably high. If you want to test your device, we recommend that you use a server in China. Alternatively, you can register an account outside China and pair a device for the test. The network delay is normal. Chinese region: https://openapi.tuyacn.com American region: https://openapi.tuyaus.com European region: https://openapi.tuyaeu.com.
Enum values are sent from 00.
Get the instruction set supported by the device through the interface GET /v1.0/devices/{device_id}/functions or GET /v1.0/functions/{category}.
Real-time reporting does not need to be timestamped; Logging-based reporting can be timestamped and can be cached in the module if no network connection.
We choose moji weather App and return both PM2.5 and PM2.5C information, while the PM2.5 value is almost the same as the AQI.
If the network is interrupted, the device will automatically connect after the network is restored, and the process is at the second level. In addition, Tuya cloud has the ability to dynamically expand according to the network load.
Currently MCU docking products request weather data and the temperature defaults to Celsius.
The interface currently has a time limit, you can query the total number without adding a time range. The default current page is 100, and paging parameter query (page_no, page_size) can be added. Get user list: https://developer.tuya.com/en/docs/cloud/76f3e0885f?id=Kawfji9n0sdmq.
Most customers are taking the uid parameter value and will use the uid returned by the token. This value is actually of no practical significance to the user and needs to be ignored. The real value should be obtained by obtaining the user list under the application and then checking the corresponding User's uid. See the documentation chapter for details: “Get the user list”https://developer.tuya.com/en/docs/iot/open-api/api-reference/smart-home-family-management/user-management?id=K95ztzvgwnshy.
First check whether the reported MCU information protocol interface is correctly docked, the default genera firmware does not contain PID, and no PID can not complete network configuration; If display Newdevice, that is caused by MCU did not correctly report the PID.
Tuya allows developers to operate device resources based on the app, product, or authorization. 1. App-based device operation: An app developer on Tuya Cloud can operate devices that are bound to users of the app. 2. Product-based device operation: A developer can operate devices that belong to the developer's Tuya Cloud products. 3. Authorized device operation: A third-party developer can operate a user's device resources after being authorized by the user.
There is no corresponding API interface for the time being, and the APP and the client cloud need to be adapted.
You can refer to this document, access address: https://developer.tuya.com/en/docs/iot/api-request?id=Ka4a8uuo1j4t4#title-1-%E6%8E%A5%E5%85%A5 %E5%9C%B0%E5%9D%80.
For details, visit https://developer.tuya.com/en/docs/iot/tuya-smart-cloud-platform-overview?id=K914joiyhhf7r.
Token-related interface (v1.0/token&v1.0/token/{refresh_token}): sign = HMAC-SHA256(client_id + t, secret).toUpperCase() Business interface (non-token interface): sign = HMAC-SHA256(client_id + access_token + t, secret).toUpperCase().
Two hours, after expiration, you need to exchange fresh_token for a new token.
The encoding format of Tuya SDK is UTF-8, please change the encoding format of the compiler or viewer.
No, the MCU only needs to respond and does not need to send too much data.
Yes, the response time of the passive reporting module may be slightly slower.
Calling is supported. The label is obsolete because it guides developers to use the upgraded interface. Generally, the interface seen in the document will not be changed, only the upgrade is performed. The interface before the upgrade also supports calling.
Modules with general firmware like firmware key can be used interchangeably, and no PID in the general connection solution module, the PID is initialized by MCU.
Tuya's cloud simulation assistant has been optimized and integrated most communications protocols.
If you select the MCU solution, Tuya provides the MCU SDK. You can develop the MCU yourself.
Find the function in the function definition, and click "Edit", and then set the multiple as required (the data will be transmitted with the exponential conversion of 10). For example, if you report 26.5, please set the multiple to 1, then convert 265 to hexadecimal to report. The panel will automatically convert 265 to 26.5 according to the multiple. If you follow the above settings but the decimals cannot be displayed, please confirm whether the panel supports the decimal display.
The cloud server's response time is shorter than 40 ms (0.04s) in China, which is on the same level as Baidu shorter than 80 ms (0.08s) in Asia shorter than 90 ms (0.09s) in Europe and the USA In Middle East and Africa, the network response time is also short.
No, considering security, each different type of access requires a different key.
We do not recommend MCU actively report data to the module at regular intervals, and we recommend that only data changes requiring actively report and no need regular reporting.
You can visit: https://developer.tuya.com/en/docs/cloud/customer-feedback?id=Kb68j30fcldlb.
It can be distinguished according to the country code through the interface of GET {{url}}/v1.0/all-countries. cn is China, eu is Europe, us is Americas, and in is India.
The tokens in different data centers are independent and cannot be mixed. For example, the token obtained from China cannot be used as the token in the request header of the Americas.
You can restrict the number of MCU retransmissions to 3.
Yes, if you move to another area, it is recommended that you reconfigure the network connection. Our service covers the whole world, you can enjoy faster speed by choosing the right area. There are many applications for domain names, many of which are already packaged, and there are many applications for cloud-to-cloud connection. If you have mobile device requirements, you can submit a new work order to describe your requirements, and then we judge whether there are other solutions that can suit you. In addition, if there is defined logic when configuring the network, for example, when the network is configured, the code is hard-coded to match the China region, then it cannot be changed.
In order to prevent malicious tampering of the API call process, calling any API needs to carry a signature. Tuya Cloud according to the request parameters, signature verification, illegal signature request will be rejected.
Sum all bytes in the frame and calculate the remainder of the byte sum to 256.
Area ID interface of the set-top box. Get area column table: GET /v1.0/infrareds/{infrared_id}/provinces/{province_id}/cities/{city_id }/areas.
Hello, you only need to create a cloud development project, and then click the Overview tab to find your Access ID/Client ID and Access Secret/Client Secret.
After a user is added to the project, the user can be authorized with the corresponding asset management authority. You can change the password of a created user and delete the user. For more details please see: https://developer.tuya.com/en/docs/iot/manage-user-account?id=Kag2ytz6c4gf1.
We can provide you with device log API to get device logs. Reference documents: https://developer.tuya.com/en/docs/cloud/device-management?id=K9g6rfntdz78a.
Please log in to the Tuya developer platform IoT.tuya.com, click Cloud on the left navigation bar, and select Usage to view the usage status of your account. You can also follow the API Statistics and Messages Statistics to view the usage of the two resources separately.
When you call an API operation of Tuya Cloud, you must provide a signature to verify your identity. This topic describes how to generate a signature in a call. Signature algorithm Tuya Smart uses HMAC-SHA256 to create a message digest. Different signature algorithms are used in the following types of API operations: token management operations and service management operations. Signature algorithm for token management operations Scope of application: operations that are used to get or refresh tokens. Signature algorithm: sign = HMAC-SHA256(client_id + t, secret).toUpperCase() Procedure to sign a request: client_idand the 13-digit standard timestamp of the specified request to create a string. secret. Encode the hash digest value into a new string. Capitalize all letters of the new string. Signature algorithm for service management operations Scope of application: operations that are used to manage services rather than tokens. Signature algorithm: sign = HMAC-SHA256(client_id + access_token + t, secret).toUpperCase() Procedure to sign a request: client_idaccess_token, and the 13-digit standard timestamp of the specified request to create a string. secret. Encode the hash digest value into a new string. Capitalize all letters of the new string. For more details please see：https://developer.tuya.com/en/docs/iot/sign-requests?id=Kae3co5j4000h.
The Cloud Development allows you to manage the devices and assign the device permissions by asset IDs. Click to see how to manage assets.
If you use the same dev_id, code, and value to access the HTTP restfull API, then the MQTT issuance of control commands needs to be checked in addition to the access_token (validity), data encryption method, sign signature rules, whether payload JSON body Field is missing, whether dev_id is a real device.
Start net pairing is required when a configured module is removed from the App and needs to be paired again. Restore factory settings can be used for products that can be paired only after you manually enable their network pairing function, which has been disabled after a manual reset of the products.
When you encounter a problem, you can submit a work order. Tuya will have a corresponding person in charge to answer and provide support for you, but it will be slower in time. Or you can pay a certain consultation fee, build a project group, and Tuya provides one-on-one support.
The error is a known issue in the open source community of puslar, and does not affect the message push. Ignore it for the time being.
When the module does not get a response from the MCU, it will reissue proactively ( 5s each time, which is enough to write Flash for MCU). If he same package of data had been sent more than three times in total, then the upgrade is judged to have failed.
You can refer to the document address: https://developer.tuya.com/en/docs/iot/standarddescription?id=K9i5ql6waswzq, click the corresponding product catalog to view the category name; Cloud docking can be obtained by obtaining the device instruction set API, and the return parameters will also inform the category of the specific product Document address: https://developer.tuya.com/en/docs/cloud/device-control?id=K95zu01ksols7.
If refresh_token is stored, it can be refreshed based on refresh_token. If refresh_token expires or fails to be refreshed, it needs to be re-authorized according to the authorization code authorization process (enter username & password, re-authenticate and authorize).
The internal beta version of the API can be used normally, in the same way as other interfaces.
You can refer to the following link: https://developer.tuya.com/en/docs/iot/quick-start1?id=K95ztz9u9t89n.
The device ID and UUID are generally the same, only some products of the category will be different, and the specific category will be reflected in use. The outside generally uses the device ID as an identification code.
At present, it does not affect that the current policy of app changing password will not cancel authorization.
The debugged data by using debugging assistant is the same as the data communicated by MCU, and MCU could refer to debugging assistant command.
Simulators cannot simulate hardware-coded cameras. Use a real camera for commissioning.
This is mostly a case where the module is not receiving data from the MCU debugging assistant, and you need to check if the module's RX is receiving data and if the serial port is normal.
MCU_SDK needs flash 4Kbyte, and RAM slightly differs from the different functions, for which usually tens of bytes is enough. If the OTA function is needed, RAM needs to be more than 256 bytes.
Data transmission is also transparent transmission, means that no matter how the services are transmitted, the module is only responsible for transmitting the services to the destination node and ensuring the transmission quality, without processing the transmitted services.
You can visit https://developer.tuya.com/en/docs/iot/tuya-smart-cloud-platform-overview?id=K914joiyhhf7r.
Micro controller Unit, the device has its own control board, the function of the product is defined by the control board, and the networking module is connected to the control board to realize the networking function.
The base protocol has nothing to do with the product, but is a shared protocol of the module, including module initialization commands and some extended function commands, such as heartbeat packet, network status releasing, and function point status query and other commands.
API is the acronym for Application Programming Interface, which is a software intermediary that allows two applications to talk to each other.
This command can be sent to the module when the device needs to be rewired.
This problem occurs. The most likely reason is that the password field is entered in plain text when registering, and the api requires MD5 encrypted cipher text. When you solve it, you need to register the user again. The password will be replaced.
Compared with ordinary services, cloud servers have higher advantages in stability, security, and reliability, and can be quickly expanded and flexibly configured. Tuya servers are cloud servers.
The project category created at present cannot be modified. You can create another project.
Tuya is oriented to 6 major industries（Include Smart Compus,Smart Agriculture,Smart Industry,Smart Real Estate,Smart Energy,Smart Elderly Care）, relying on data-driven operations to empower Tuya's cooperative companies to create new smart business models, reduce costs and increase efficiency, and optimize user experience. You can communicate your specific needs with our online customer service staff, and we will arrange staff to contact you as soon as possible. https://www.tuya.com/solution/list.
Tuya pushes the real-time device status in MQ messages. You can subscribe to this feature. For details, see https://developer.tuya.com/en/docs/iot/message-service?id=K95zu0nzdw9cd.
All devices added by the user in the App can be controlled.
IPTV currently does not support foreign channels.
Pls find the website below:https://developer.tuya.com/en/docs/iot/open-api/product-pricing/membership-service?id=K9m8k45jwvg9j.
Clientid is accessid, you can apply after logging in on our platform. Link: https://developer.tuya.com/en/docs/iot/quick-start1?id=K95ztz9u9t89n.
Proactive reporting: When an MCU receives a command from a module and executes an action, it needs to report the new DP status to the module. Proactive status reporting uses a synchronous processing protocol. When the module receives the proactively reported information, it sends the ACK message to the MCU. Passive reporting: When the MCU proactively detects a DP change or restarts, it reports the changed DP status to the module. Passive status reporting uses an asynchronous processing protocol. The module reports the data to the gateway and waits for the gateway's response. If the gateway does not return a response within the specified time or returns "fail", the module sends the NACK message to the MCU, and the MCU must retransmit the data. In passive reporting mode, the module's response content is determined by whether the gateway has received data. The response time is long. In proactive reporting mode, the module considers the gateway to be connected and returns data to the MCU directly. The response time is short.
The functions of some equipment have been customized by equipment manufacturers, which are somewhat different from the standard instruction set. Tuya staff is required to do background processing. Please contact online customer service or your account manager for assistance.
Set the highest priority for serial port interrupt, exclusive interrupt when sending and receiving data.
PID is transmitted in the form of the string ASCII code hexadecimal.
The module will keep sending the product query command.
SDK package on MCU hardware resource requirements: Flash 4K byte, RAM and DP point data length related to one hundred bytes (OTA function should be greater than 260 byte). The number of function nesting levels is 9. If users do not have enough resources, they can dock the protocol on their own and the functions in the SDK package can still be used as a reference.
There is no limit to the number of linked accounts.
The two channel distributions may have overlapping parts. In this condition, there will be interference with each other. The module will automatically select the optimal channel according to the environment.
Yes.
Wi-Fi and NB API interfaces are the same to obtain power information. Whether the APIs of cloud-cloud interconnection are consistent has nothing to do with the communication protocol, because the server will try to control the unification of the external interface.
Because the data channel takes MQTT transmission, it mainly controls the transmission of related command data, and it is recommended that it does not exceed 1K.
Password rules for SDK verification: Password rules SDK does not do password verification. Tuya is done by the upper layer, and it is recommended that the customer's password rules: 6-20 digits, must have letters and numbers. The cloud has also verified that the client will make the password sha value, and the cloud will go back to match, similar to 123456, A11111, and other simple passwords, to avoid the occurrence of overly simple passwords.
Tuya support provides customers to use the Puslar test environment and the official environment under one developer account. After adding the device to the test channel, the news of the device will be pushed to the test environment, and the official environment will no longer receive the news of the device.
The open message platform does not allow access by default. If you need access, please submit a ticket to open.
The panel updates the upgrade progress according to the response frame of the upgrade package returned by MCU % value is updated.
Several microseconds.
MCU general connection is to query the mac address of the module.
The first heartbeat packet is to identify the first time the MCU starts or send after MCU is reset, and used to reinitialize the parameters of each DP point, while the subsequent heartbeat packets are mainly used to shake hands and determine if the device is offline.
Module supports upgrading MCU protocol , every frame has cumulative validation, customers can put the whole firmware check code into bin file together to do more secure validation.
Tuya module's current serial port processing mechanism is based on serial port full duplex, and both sending&receiving can be supported simultaneously.
After power on, the device needs to be initialized with the module to get the mac address.
The data length, data content, or checksum may be incorrect. Combined reporting requires that all data is correct. If any data is incorrect, the whole packet will be lost.
It will be sent again in 15s after the correct reply.
Module processing mode and MCU and module cooperation mode.
The protocols are classified into basic and functional protocols. Basic protocols are independent of products. They are common protocols of modules and include module initialization commands and some extended functional commands. Functional protocols are DP data transmission and receiving commands that the platform automatically generates based on the definition of each product DP.
Check the serial port sending configuration.
Check the module logs to locate the failure cause.
Currently only supports 2.4GHz band, WBR3D supports 5G band.
It is determined according to the GPIO name, for example, GPIO1 data is 0x01.
The value of PM2.5 is currently only available in mainland China.
Please check whether the module is under the low-power-consumption status. The low-power state module UART only supports downlink, the module will not respond to any commands sent by the MCU. However, the module can be awakened by pulling down the low-power control pin.
No, upgrade failure are reported by the baseline.
After a DP is modified and migrated to another program, you need to re-pair the device to control it.
SDK function nesting level is 8 layers, to check whether MCU function nesting processing capability can meet the requirement.
CODE takes up about 4KB and RAM varies slightly according to the function, usually tens of bytes are enough. If OTA function is needed, RAM needs about 256 bytes. For users with limited MCU resources, consider not using SDK to connect with Tuya protocol which can save some space.
The ipc SDK needs to be accessed based on the home SDK access, because the device distribution network is implemented in the homeSDK. For more details please see: https://developer.tuya.com/en/docs/iot/ipc-sdk-manual?id=Kadz3e3pfgnwi.
Refer to the document:https://developer.tuya.com/en/docs/cloud/video-cloud-storage?id=Kaiuydzbyo2g1.
This is normal, because display in circle is the color obtained by HSV synthesis, the color disc represents only one element of the color.
If the registration is successful, you can log in the corresponding App. Please note that the password is encrypted by md5 when registering through cloud-cloud docking.
Preparation Ensure that JDK7 or later is used. Sign up for a developer account on the Tuya Cloud Platform and confirm the AccessID, AccessKey, and Endpoint (call address) values. Source code installation Go to the Github CodeHub to download the source code package. Decompress the source package to the proper position of your project. Reference the corresponding module code. For more information, see the example. Reference JAR package installation Contact relevant personnel to obtain the JAR package. Add the JAR package to the proper position of your code. Instructions The SDK provides two methods to implement API requests. If you need to implement some APIs yourself, select either of the methods. You can also contact Tuya. Tuya personnel will update the SDK version in time. For more information, visit https://developer.tuya.com/en/docs/iot/device-control-best-practice-java?id=Kat2uf0cwn9k9.
Currently, mainly the C language is used, and the assembly language is seldom used. Tuya has no plan for using rust.
Use the Tuya module debugging assistant to simulate the MCU and check whether the communication between the MCU and module is normal. If so, the pairing failure is not caused by the module. For more information about how to use the module debugging assistant, visit https://developer.tuya.com/en/docs/iot/module-debugging-assistant-instruction?id=K9hs0cj3lf0au.
Data of the fault type is bitmap data, which can be one byte, two bytes, or four bytes in length. When a fault occurs, the corresponding bit is set to 1. When multiple bytes are contained, data of fault type is displayed in big-endian mode.
When data communication is performed between the MCU and the module, the maximum length of a single data packet that is limited bythe module and the maximum length of a data packet that can be received by the MCU are used.
The toolchain indicates compilation tools, function libraries of the original factory, and related configurations used during compilation and running.
The MCU SDK is generated based on the selected product solution. If you select a general integration solution, the MCU SDK for general integration is generated. If you select the HomeKit solution, the MCU SDK for HomeKit integration is generated.
No, non-code modules cannot be used for products that use the MCU general integration solution.
Tuya's MCU SDK is the processing code developed using C language based on Tuya's serial protocol. Any compiler that can identify C language can be used.
Self-processing by module means that the pairing indicator and button are connected to a GPIO of the module. The GPIO pin drives the LED to display the module status.
Common computing devices, such as Raspberry Pi, are general hardware platforms on which different types of hardware can be extended to support various functions. They feature abundant resources and powerful capabilities but also high costs. They apply tothe learning scenarios. Tuya hardware devices are professional hardware platforms oriented to specific application scenarios and enable optimized solution design to meet business requirements. They feature dedicated capabilities, limited resources, and low costs. They apply to business scenarios.
Not necessarily, this depends on the strong and weak binding relationship of the device. 1. Strong binding: the user must first unbind the device from the App before the next person can operate the network; the advantage is safety, the disadvantage is the operation is troublesome, currently some devices of IPC and door locks choose to use strong binding, some ease of operation can be sacrificed for safety. 2. Medium binding: The level is slightly weaker than the strong binding. After the local reset, the previous bound user will not be removed, and the next user can also configure the network, but will send a push and message center to the previous user to notify the previous user; Between strong and weak binding , only one more notification than weak binding. 3. Weak binging: It is the weakest binding level which has the largest percentage. The device can be reset and bound by another user at will, without the consent of previous user, and no notification to previous user.
Restore factory settings clears a module's network pairing information and restarts the module. After a restart, the module exits from the network pairing state. To make the module re-enter the network pairing state, the start network pairing command is required. Start network pairing resets a module and enables the module to enter the network pairing state. For example, it enables a configured module that is disconnected from the network to re-enter the network pairing state.
0x00: the first heartbeat return value after MCU restart, sent only once, used by the module to determine whether the MCU is restarting or not; 0x01: except for the first return value of 0 after MCU restart, all others return this value.
The latest general firmware heartbeat packet mechanism is sent once every 15s, and the timing is not affected by the sending command.
When the module restarts and the module network status changes.
Using special network configuration solution, can not use MCU exit the network; Entering into network configuration if other mobile phones connected before exiting the original network, or use the original App to remove the device before exit the network.
The settings of the DP point supports negative numbers. It only need to report according to the complement. The data format is usually 4 bytes. Such as displaying -19, the reported data is FFFF FFED.
Dear user, it may be that you have turned on the Cloud Authorization IP Allowlist function. After enabling this function, you can set up a list of IPs that can legally access Tuya's data centers through the IP whitelist function. Requests from source IPs that are not in this list will be rejected. If you don't need to close it.
We have a special host computer for testing IR remote control, the IR remote control is connected to the computer through the serial board. One is the host and the other is slave. Click the host computer to test it.
No panel is provided for device access. If you choose smart product development, you can select the corresponding panel. For more information, see the following figure.
Dear user, we are sorry for your inconvenience. Tap Restore Factory Defaults on Echo Show to unbind the Amazon Alexa App account from it. You can then bind another Amazon Alexa App account to Echo Show.
Power-on network configuration without timeout and anti-misdelete: Automatically enters network configuration state upon power-on, the network configuration indicator keeps flashing and remains in the network configuration state. If it was previously connected and accidentally long-pressed to reset, it cannot automatically reconnect; Power-on network configuration with 3-minute timeout and anti-misdelete: Automatically enters network configuration state upon power-on, the indicator flashes, and if no network configuration is done within 3 minutes, it automatically exits the network configuration state. If it was previously connected and accidentally long-pressed to reset, and no network configuration is done within 3 minutes, it automatically reconnects; Long-press network configuration with 3-minute timeout and anti-misdelete: Requires long-pressing the button to enter the network configuration state upon power-on, the indicator flashes, and if no network configuration is done within 3 minutes, it automatically exits the network configuration state. If it was previously connected and accidentally long-pressed to reset, and no network configuration is done within 3 minutes, it automatically reconnects.
The displayed time is linked to the time zone at the bottom of the page. The default is the same as local time.
System on Chip, referred to as SoC, is also a system on a chip. In a narrow sense, it is the chip integration at the core of the information system, which integrates the key components of the system on a chip. In a broad sense, SoC is a tiny system. If the central processing unit (CPU) is the brain, then SoC is the system including the brain, heart, eyes and hands. Academic circles at home and abroad generally tend to define SoC as the integration of microprocessor, analog IP core, digital IP core and memory (or off-chip storage control interface) on a single chip, which is usually customized by customers or for specific purposes standard products.
If the product is connected to a mobile phone, it is recommended to remove it from the phone before shipping. If the product has completed the production test, it doesn't matter if it blinks when powered on or not removed; however, it is advised to inform the customer to manually reset it after receiving it.
AUTHKEY is the authorized value of the device, which is a service code registered on Tuya Cloud and available to use Tuya Cloud service.
Hello, the water heater is usually tested before leaving the factory, so a small amount of water will be left in the pipe and cannot be completely emptied, which is a normal phenomenon.
No, controlling a single device will not affect the group's panel.
The new panel already supports the display of the complete temperature, you can update the panel on the product.
The preview crash is generally caused when the product is created, and the selected function points are incomplete, which causes the UI panel to fail to load. You can add function points and then test.
This reason is you use a custom panel. Because of this type of pid, there may be more new dp and processing logic. If it is directly replaced with the public version, the control ability of the public version panel may not match this pid.
Yes, but the APP can't be connected for more than 15 minutes.
The functions of no-code development products are preset function points and preset optional function points. At the same time, the No-Code Development products only support standard function points, and the function points that you customize will not take effect (for details on custom function points, please refer to the second section of the custom development scheme). For a detailed introduction to standard function points, please refer to"Standard Function". If you want to modify the no-code development access plan of the product you have created, you can delete or add function points in the "Function Definition". If your product chooses a custom access plan, you can change it according to your needs.
When the panel is refreshed, the App will pull data from Tuya Cloud and update the display status of each device on the panel.
Check whether the device is offline first. If the device is offline, re-pair the device with the network and try again. Test the control function near the Zigbee gateway. If the hardware cannot be controlled, check whether the gateway's firmware version is too low. If so, update the gateway.
The Wi-Fi HomeKit general solution indicates the MCU integration solution with simultaneous connections to Tuya IoT Platform and HomeKit. The device MCU connects to the Wi-Fi module through a serial port. Tuya provides network modules, apps, and IoT-enabled cloud services, which can be integrated with HomeKit. Compared with other communication module solutions, the Wi-Fi HomeKit module connects to the cloud through the router without needing a gateway. Data operations are convenient, the transmission speed is fast, and the user experience is good. The following figure shows the communication schematic diagram of the Wi-Fi HomeKit general module integration solution. For more information, visit https://developer.tuya.com/en/docs/iot/homekit?id=Ka39uh7izqd5n.
For details, visit https://docs.tuya.com/en/iot/device-development/access-mode-soc/soc-guide/soc-dev.
Please confirm whether all the required dp are checked in the current product. If the panel is omitted, an error will be reported.
Tap Me in the bottom right corner and then the settings icon in the top right corner and tap Clear Cache. Restart the app and scan the QR code to perform a virtual panel test again.
This generally refers to the device control interface after the App is configured with the network device.
Usually, the recharge threshold is set by the factory and cannot be changed. You can consult the seller or refer to the instruction manual for accurate information.
Dear user, we are sorry for your inconvenience. A router may have a reset button or hole. If a router has a reset button, power on the router and press and hold the RESET button for 5s to 8s until the system status indicator blinks quickly three times. If a router has a reset hole, use a sharp object, such as a clip or pen tip to press and hold it. Note: To reset some wireless routers, press and hold the RESET button for more than 3s until the indicator is on. For some wireless routers, the RESET button is also used as the QSS button.
Serial method (BL0942/HLW8032): 3% Pulse collection method (BL0937/HLW8012): 5%.
Yes, the new version has the same pin position and functionality unless there have been modifications to the firmware configuration.
Product status: Under development. It can be modified, but the module needs to be reprogrammed to take effect after the configuration is changed. Product status: development completed. Cannot be modified, you need to return to the state of development before you can modify it.
The heartbeat function does not need to be written separately, the SDK is integrated internally.
We build white-label Tuya apps, IoT dashboards, and custom integrations for your business.
🚀 Schedule a Call