Browse the most common questions and expert answers about Device Development on the Tuya IoT Platform.
The cost of BQB certification mainly consists of three parts: the Bluetooth Alliance annual membership fee, the product certification DID certificate fee, and testing fees. The annual fee and DID certificate fee information is available from the Bluetooth Alliance website: https://www.bluetooth.com/fee-schedule/ I. Bluetooth Alliance Annual Membership Fee This fee depends on your chosen membership level and certification type. Based on the Bluetooth Alliance's 2026 fee schedule (generally adjusted annually): Adopter Members: Free application and registration, no membership fee required. Contributing Adopter Members: Small Contributing Adopter Member Companies (Annual revenue less than $100 million): Annual fee $3,500. Large Contributing Adopter Member Companies (Annual revenue exceeding $100 million): Annual fee $16,500. Associate Members: Small Associate Member Companies (Annual Revenue less than US$100 million): Annual Fee US$11,250. Large Associate Member Companies (Annual Revenue exceeding US$100 million): Annual Fee US$52,500. II. Product Qualification Fees: Adopter Members: DID Qualification Fee US$12,000. Contributing Adopter Members: DID Qualification Fee US$12,000. (The first qualification fee each year is discounted by 33%, resulting in a DID Qualification Fee of US$8,000.) Associate Members: DID Qualification Fee US$6,000. (A 50% discount is offered on all qualification fees.) III. Testing and Service Fees These fees vary depending on product complexity and the chosen service provider. Testing fees: Approximately RMB 10,000-14,000 for a single-mode (BLE) system and RMB 20,000-28,000 for a dual-mode (BLE+BR/EDR) system. If the module or finished product solution already has a BQB certificate, OEM customers can list it based on the existing BQB certificate and be exempt from testing fees.
To achieve a gradient effect three times during device network configuration and then transition to a fixed value at other times, the PWM function can be utilized in the application layer logic without the need for process or timer polling. The specific steps are as follows: 1. When the device starts network configuration, set the PWM parameters to achieve a three-time gradient effect. 2. After the network configuration ends, adjust the PWM parameters to maintain the device at a fixed output value. If the PWM function cannot meet the requirements, other software design solutions can be considered. Utilizing the PWM function can avoid the use of additional processes and timers, thereby saving system resources.
To report negative temperatures, please ensure the following: 1. Use the two's complement form to report negative temperatures. For example, if the actual temperature is -19, it should be reported as its two's complement, i.e., 0xFFFFFFFFED. 2. To avoid misinterpretation or display errors, confirm that the two's complement value is displayed correctly. Reporting 0xFFFFFFED should display as -19. 3. If the data displayed by the device does not match expectations, check the device logs to confirm whether the data was actually reported as expected. If it is found that the report was unsuccessful, check the correctness of the data reported by the MCU. 4. Check whether the platform function point configuration is correct. If the function points on the platform have been modified, reconfigure the network before performing the test. 5. If the issue is still not resolved after the above steps, please contact the relevant technical support for further assistance.
The WBR3 module does not have a direct command to close the network configuration. The following methods can be used to close the network configuration: 1. Configure the working mode to timeout network configuration. If the module does not successfully configure the network within a certain time (default 3 minutes, customizable), it will automatically return to low power state. 2. Try to directly power off the module and restart the device to exit the current network configuration mode. Reference document link: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-wifi-time?id=Kd2fzooztuuqt.
One of the reasons for the "GATEWAY_DELETE" offline log is that the device is reconfigured after being reset. Device reset may lead to the device being deleted and offline, thus generating this offline log. It is recommended to check the device's operation history or configuration records to confirm the specific reset action, in order to further investigate possible misoperation or anomalies.
The SDK downloaded from the Tuya platform is usually in source code form. Users can import it into the Arduino IDE, modify it, and combine it with Arduino software for hardware development. Choose an appropriate base program to modify, such as the ble_led program. When encountering abnormal program interaction issues, first capture the data from the module and the microcontroller to ensure they are interacting normally and the connections are correct. If data interaction is unsuccessful, compare the original successful interaction code with the modified code to check the modifications. For simulation debugging, you can refer to the provided support attachments for program simulation and debugging to solve the issue of the device not being searchable. For different models of microcontrollers, such as STM32, appropriate program resources should be used, and further debugging should be done by referring to the attachments provided by Tuya.
Please check the hardware connection and confirm that the RX, TX, VCC, and GND of the 4G module are connected correctly, and that the SIM card and antenna are installed. Ensure that the module can interact normally with the debugging assistant so that the network status can be correctly delivered to the debugging assistant. If the interface definition is completed and the corresponding json file is downloaded, please adapt it on the MCU side to ensure that the module can communicate with the MCU and implement product logic. Download the latest SDK to ensure all necessary functions are available for normal use.
If the Cat module L511 using a 3.8V, 2A power supply cannot be used after connecting the module's TX to the USB-to-serial RX, please confirm the following points: 1. First, confirm that the voltage of the main serial port is 1.8V. 2. If you need to connect to a 3.3V MCU, level conversion is required to match the voltage. 3. After completing the level conversion, you should be able to communicate normally with the MCU. 4. To ensure normal communication, it is recommended to capture the data from the module's TX to check if any data is being sent.
Determine if the Tuya Bluetooth module can be properly networked: Check whether the module is broadcasting signals normally to ensure the device can broadcast signals properly during networking. This can be verified by checking its broadcast cycle or detecting whether the device is in a broadcast state. Confirm whether the device's firmware burning and authorization information are valid, as these steps are crucial for the device's normal activation. Check if there are any interference factors in the module environment, such as the module antenna being blocked or being close to high-frequency devices, which may lead to networking failure. When using the SmartLife App for networking, pay attention to the networking status updates, MTU, timestamp, and connection parameters to ensure they are normal. Solution for the phone unable to bind again after unbinding: Confirm whether the device is in the "unbound" state, as only in this state can the app be used for networking and binding. If the device can be searched but networking and binding fail, try changing the phone or turning off the phone's Bluetooth, then clear the app cache and try networking again. If the problem persists, it is recommended to upload the app logs and provide the networking account and app name for further analysis and problem-solving.
ZS3L module can be directly used to replace TYZS3 module without changing the package, achieving PIN to PIN replacement.
In a scenario with two cameras, users can implement the camera video switching function in the app through the following steps: 1. Create a custom feature point in the app so that it can display the "lens switch ipc_camera_view" feature point on the device panel. 2. When the user clicks the lens switch feature point in the app, the device reports the video stream information of the corresponding lens. 3. After implementing the camera switch feature point, consider issuing commands via SPI or UART serial port to switch camera video. 4. When switching cameras, the device needs to resend the 0x63 command to obtain the video attributes of the second camera. 5. Set the platform to dual-camera picture-in-picture mode, then reconfigure the network to achieve back-and-forth switching between the main and secondary cameras without obtaining the lock-end camera count.
Here are the steps to the solution: 1. Ensure the device has been activated with network configuration while online, so the device can recognize the local time zone. 2. In offline mode, obtain the accurate date and time from the hardware RTC and convert it to UTC time (seconds). 3. Use the `tuya_ipc_set_service_time()` interface to set the UTC time obtained from the RTC into the SDK. 4. While setting the time, attempt to execute `uni_set_time_zone("+08:00")` to set the time zone. If the SDK version does not support this interface, try calling the function through external definition. 5. Check whether the creation of the recording storage path uses the SDK internal time, ensuring the time passed to the SDK is accurate UTC time. 6. If the above methods cannot solve the problem, it may be necessary for the customer to activate the device first to ensure the device knows the local time zone and can correctly set the time zone offset. 7. If the device must support recording while completely offline, ensure the device accurately maintains time through hardware or other means, and set the SDK time by accurately reading the RTC clock.
If your camera intermittently shows an "offline" status, you can try the following steps: 1. Ensure the camera is within the effective range of the router to avoid signal interference. You can try adjusting the camera's position to improve signal strength. 2. Check the firmware update status of the camera device to ensure it is running the latest version. Firmware updates can resolve known issues and improve connectivity. 3. Restart the router to refresh network settings, ensure the router firmware is the latest version, and try changing the Wi-Fi channel to reduce congestion. 4. Check if there are other electronic devices in the area that may affect the Wi-Fi signal. 5. Perform a factory reset on the camera and then reconfigure it to clear any temporary faults or incorrect settings. 6. If the problem persists, check the device log to confirm if each time it goes online is accompanied by a device restart. If the power is normal, it may be a fault with the device itself, and it is recommended to return the device to the factory for further analysis.
You can purchase the "Tablet Adaptation" value-added service:https://www.tuya.com/vas/commodity/OEM_APP_ADVANCED.
Dear user, we are sorry for your inconvenience. Network configurations change if you replace the router or use a new network. To use a device that has been connected to a different network, first remove that device, reconnect it to the new network. You need to reconnect all the Wi-Fi devices and gateways (including Zigbee and Bluetooth gateways). But those devices which under the gateways (including Zigbee and Bluetooth gateways) are not required for reconnection. You can also use Auto Scan mode to add multiple devices at once. If your device fails to connect to the smart device after replacing the router or modem, it may be that your router is 2.4GHz and 5GHz mixed, or your router is not compatible with our device. Note: Even you change back the SSID and Wi-Fi password to the same as the original one, you still need to select the network and Wi-Fi password again when readd your devices. If you not, there may be a problem of not being able to connect to the Internet. This is because the Wi-Fi password you set in the router will be encrypted by the router into a string of longer and more complex passwords to prevent others from cracking and stealing. After you reset the router or replace the router, even if you set the same password, it will be encrypted by the router into a new password. If you do not re-select the network and enter the password when configuring the network, the router will still receive the previous encrypted password, so the connection will time out.
After logging into the App using third-party accounts such as WeChat or QQ, you may receive a prompt saying "Already registered" when binding your phone number or email for the following reasons: If you have previously registered an account with that phone number/email, logging in through third-party accounts like WeChat or QQ will create a new independent account instead of associating with the original account, thus it cannot be bound to that phone number/email. Similarly, after logging in through a third-party account, it is not possible to inherit the device information under the original phone number/email account.
No, it is not possible. The same account only supports registration for one country/region within the App, and cannot be registered for other countries/regions.
You can use the relevant API of the Tuya platform to set up cloud timing functions. The specific steps are as follows: 1. Confirm that the device has gateway or Wi-Fi capabilities, as cloud timing is applicable to such devices by issuing commands from the cloud. 2. Use the API provided by Tuya for development: - Use the addTimer API to add a new timing task for the device. You can set the start and end times of the timing task and define the repeat rule for the interval days. - Use the updateTimer API to update existing timing tasks. - Use the removeTimer API to delete timing tasks. - Use the syncTimerTask API to obtain the timing list of a specific category under the device. 3. Set different timing tasks for different scenarios, such as timed cleaning or timed reminders. You can specify different "categories" during configuration to ensure that timing commands are set separately for different application scenarios. 4. During panel development, implementation needs to be carried out according to the specific timing interface. Please refer to the interface documentation provided by the Tuya developer platform. Additionally, if you need to add a new timing DP, please communicate and coordinate with the UI panel development team. During panel development, after setting the DP points, these automated tasks will be issued from the cloud to the device at the set time point to execute the corresponding functions.
Calls to obtain or refresh tokens count towards the monthly total of API calls. Therefore, it is important to manage the number of calls when using the API.
The music rhythm function in the colorful light strip includes two modes: local music rhythm and app music rhythm. 1. App Music Rhythm: Implemented through the SmartLife App, the app collects environmental volume through the phone's microphone. The SmartLife App needs to remain open to function properly; if the phone screen is turned off or switched to another app, the function will be disabled. 2. Local Music Rhythm: The light strip collects environmental volume through the microphone on the light strip controller, allowing music rhythm without opening the SmartLife App.
Confirm that the issue is caused by a network connection problem. When resolving similar issues, first check the device's network status and settings. At the same time, collecting application logs and the integrated podfile.lock file can help developers better identify and resolve the issue. If you encounter this type of error again, it is recommended to further analyze through these steps.
To ensure the Wi-Fi module achieves low power mode while maintaining connectivity, the following measures can be taken: 1. Use the Wi-Fi T3 series module. This module supports keep-alive low power consumption, with power consumption of about 150 microamps in long connection state. 2. Configure in the existing SDK: - Add wake-up pin and low power configuration fields. For detailed information, refer to the protocol:https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-lowpower?id=Ke9jrvpzvxe03. - Select configuration in the 0x01 low power field. - Configuration code example: ```c #ifdef LONG_CONN_LOWPOWER sprintf((char *)str,",\"low\":%d",LONG_CONN_LOWPOWER); length = set_wifi_uart_buffer(length, str, my_strlen(str)); // ===== 【New】Low power and wake-up pin configuration ===== // 1. Set low power mode to AP keep-alive (long keep-alive) sprintf((char *)str, ",\"sm\":2"); length = set_wifi_uart_buffer(length, str, my_strlen(str)); // 2. Configure the pin (wk) and polarity (wkp) for MCU to wake up the module // Use pin 14, falling edge effective (wkp=0) sprintf((char *)str, ",\"wk\":14,\"wkp\":0"); length = set_wifi_uart_buffer(length, str, my_strlen(str)); // 3. 【Optional】Configure the pin (mwk) and hold time (mwkpt) for the module to wake up the MCU // Use pin 12, high level hold for 50ms (default value) // sprintf((char *)str, ",\"mwk\":12,\"mwkpt\":50"); // length = set_wifi_uart_buffer(length, str, my_strlen(str)); #endif ``` 3. Check pin configuration: - If the module wakes up the MCU, choose the appropriate pin for connection, ensuring the IO port is connected to the external pin of the MCU to achieve wake-up. 4. Capture TX and RX data between the MCU and the module, ensuring heartbeat data is replied within 500ms, otherwise the baud rate may not be locked. 5. If the device cannot connect to the network: - Confirm whether the wake-up pin connection on the module side is correct. - Wake up the module after powering on and reply to the command. You c.
The display of device signal strength units depends on the data value reported by the device: - When the reported data is less than or equal to 0, the unit displayed is dBm. - When the reported data is greater than 0, the unit displayed is percentage. To modify the display unit, you need to change the reported data: - For no-development products, it is currently not possible to modify the reported data. - For MCU development products, you can obtain and modify it through serial port commands, see the standard protocol document:https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-22-%E8%8E%B7%E5%8F%96%E5%BD%93%E5%89%8D%20Wi-Fi%20%E4%BF%A1%E5%8F%B7%E5%BC%BA%E5%BA%A6%EF%BC%88%E5%8F%AF%E9%80%89%EF%BC%89(0x24).
Encountering an error in locating the first I-frame is usually due to the inability to find a suitable I-frame. Specific steps to resolve this issue may include: 1. Check whether the firmware version of the IPC camera is compatible with Tuya's SDK 6.x and ensure all related hardware configurations are correct. 2. Confirm whether the I-frame setting parameters meet the requirements, and check the configuration files and setting parameters of the camera during initialization. 3. Try restarting the device to see if the error persists. 4. Refer to the relevant Tuya platform documentation for more detailed information on I-frame configuration:https://developer.tuya.com/en/docs/iot-device-dev/IPC-Product-Sofrware-Development-Kit?id=Kbfjuvhlyu2wr 5. If the issue persists, it may be necessary to update the firmware or SDK version to find a potential solution. By following these steps, you can further troubleshoot and resolve the I-frame location error issue when using the Tuya SDK with IPC products.
Burning the BTU module does not require a Bluetooth beacon. The specific steps are as follows: 1. Confirm that the serial port is correctly connected to the Telink burner: The module's tx is connected to the serial port's rx The module's rx is connected to the serial port's tx The module's sws is connected to the SWM of the Telink burner 2. If the line is too long, please ensure that the Telink burner, serial port, and module share the GND. 3. Select the corresponding serial COM port number in the software. 4. The EVK burner can be obtained through the following purchase address:https://h5.m.taobao.com/awp/core/detail.htm?ft=t&id=693265513597 5. The burner data cable can be obtained through the following purchase address:https://detail.tmall.com/item.htm?id=35754507608&ali_refid=a3_430583_1006:1102486793:N:FHTWuIqQpWJyG9Wm/uSmbBE1p4+YNbMK:da92d1e1ee84e6ef49fd7fddcf882737&ali_trackid=1_da92d1e1ee84e6ef49fd7fddcf882737&spm=a230r.1.14.1&skuId=73557 6. If the line is too long, please ensure that the Telink burner and serial port share the ground.
After purchasing the wrong model of the empty Wi-Fi module, users need to pay attention to the following points: 1. The Wi-Fi module delivered empty requires users to perform the burning themselves. You can refer to the relevant documents and guides on the Tuya platform for module burning. 2. Products with non-quality issues do not support refunds, so users cannot return them. It is recommended that users confirm the required model and carefully select it before purchasing to avoid problems.
According to the relevant information of the T series modules, the RX1 and TX1 pins correspond to the P10 and P11 pins in the firmware configuration. You can refer to the following link for detailed pin information of the T1-2S module: https://developer.tuya.com/en/docs/iot/T1-2S-module-datasheet?id=Kcl2d5xjy1rly According to the information, adjust the firmware configuration to use the P10 and P11 pins to access the RX1 and TX1 functions.
The reporting interval is recommended to be set to at least 250ms to ensure stability and normal data reception. If frequent data transmission is required, optimization can be achieved by combining the reporting of DP data, that is, including multiple function point data in one reporting command. This can reduce the frequency of reporting while ensuring the timeliness and completeness of the data.
Check whether the firmware version uploaded to the platform is the same as the actual version to be upgraded. The MCU firmware version needs to be refreshed, and if the version number does not change, it will timeout and fail.
It is recommended to reconnect the device to the network and check if the event time is synchronized. The specific steps are as follows: 1. Check the network connection status of the device to ensure it is online. 2. If the device is offline, reconnect it to the network through the device's settings interface or related application. 3. After completing the network connection, wait for the device to synchronize and update its event time. 4. Check the device's time settings and network time service to ensure they are set to the correct time zone and synchronization source. Following the above steps, the event time of the device should be able to synchronize normally.
When encountering the 4G module L511C-Y6E displaying "Searching for network" and not working properly, you can try the following solutions: 1. Please check if the card status is normal. 2. Confirm whether the APN configuration is correct. 3. If the problem is still not resolved, you can obtain the module operation log: and submit it for further analysis.
SmartLife and Tuya App are two separate applications, and their data does not interconnect. Therefore, it is not possible to directly view devices added through the SmartLife app on the Tuya website. The steps to resolve this issue are as follows: 1. To view your devices on the Tuya platform, you first need to associate the app account with the cloud project. 2. Log in to the Tuya platform, then go to the settings of the relevant app account. 3. Associate your app account in the cloud project so that it can be displayed on the platform. 4. Once the association is successful, you can access and view your device information through the platform, including the device's Local Key. To obtain the device's Local Key, you can use the device query function provided by the platform. Follow these steps to query the device ID: - Open the application and enter the device control interface. - Click the "···" in the upper right corner to enter the device details page. - Click "Device Information" and look for "Virtual ID".
To achieve the device's gradual change three times during network configuration, and a fixed value at other times, it is recommended to implement this through application layer logic. You can try using the PWM (Pulse Width Modulation) function to meet the requirements. If the PWM function cannot meet the requirements, it may be necessary to implement this logic through other application layer measures. The method of using the PWM function can be specifically referred to in the following steps: 1. In network configuration mode, set the PWM control module to perform 3 cycles of gradual change, resetting the state after each cycle is completed. 2. In non-network configuration mode, set the PWM control module to directly change to the target fixed value. 3. Ensure that the system design distinguishes between network configuration and non-network configuration states to facilitate logic switching and setting. If the PWM function indeed cannot meet the requirements, it may be necessary to consider using timers or other logical components for state monitoring and processing.
It can be resolved by following these steps: 1. Go to the firmware management page. 2. Create a new firmware version and upload the corresponding bin file. 3. Save the new version.
This is normal. Currently, the SDK has a logic for periodic reporting of signals. The SDK will report device operation information such as signal strength and remaining memory every hour.
Even if the device is offline, the reason why DP values can still be uploaded is usually because the mobile app uploads the data to the cloud through its own network, rather than the device automatically connecting to the internet. To confirm this situation, you can try turning off the mobile network connection.
The Industry App 3.1.0 baseline corresponds to the Smart Home App baseline 6.7.0, and has been adapted to the iOS26 baseline version 6.8.0. The Industry App adaptation for the iOS26 baseline version is expected to be available by the end of March or early April.
The reasons for the occurrence of multiple daily [online] records without [offline] records may be as follows: 1. When the offline time of the device is less than 3 minutes and it reconnects during this period, only the [online] record will be logged, and the [offline] record will not be displayed. 2. If the device's network is consistently unstable, frequently disconnecting and reconnecting, the cloud log will record multiple [online] records. Solution: 1. Check whether the device's network connection is stable. 2. It is recommended to connect the device to a mobile hotspot and observe whether the test device still has similar issues. 3. If the device has no issues in a stable network environment during testing, it indicates that the original network may be unstable and requires further optimization. By following the above steps, you can analyze and locate the cause and optimize the device's network condition, thereby reducing unnecessary multiple [online] records.
Chip malfunction, increased power consumption, and overheating are usually related to the chip's I/O pin configuration and button connections. Solution: 1. Check if there is a situation where the maximum driving capability of the module's I/O pins, 12mA, is exceeded, and ensure that the physical button connections comply with the module design. 2. Compare the normal chip and the abnormal chip, use a multimeter to test the clamping diode voltage value of the button pins and the resistance value of the power supply pins, to confirm whether the chip is electrostatically broken down. 3. The original button signal selection pin is P24, change it to a flying wire connection to the P28 master control pin to solve the abnormal problem. If the hardware is directly connected to the P28 pin and there is still a problem when the button is pressed, it may involve a software bug, and the correct pin needs to be selected for input signal. 4. After the anomaly occurs, re-power and observe whether it recovers, use an oscilloscope to detect the ripple of the 3.3V power supply or power through an external DC power supply. 5. From the PCBlayout analysis, the button circuit may be interfered by the ceramic antenna. Use an oscilloscope to detect the waveform of the button pins, keep the button and its circuit away from the antenna, or connect an external button to eliminate the interference from the antenna. 6. Investigation found that it was the influence of the ceramic antenna, and it returned to normal after removal. If problems persist, further samples can be sent for detailed testing and analysis. Knowledge source can refer to TYWE3S module socket circuit design description.
When attempting a device firmware update, if the prompt "Update Canceled" appears, you can try the following solutions: 1. Ensure the device has sufficient battery power before performing the firmware update to avoid OTA update failure due to low battery. 2. Use the "SmartLife" iOS app to test if the same issue exists. If the "SmartLife" app can update normally, it may be an issue with the OEM app. 3. Update the app version to the latest version of odm 7.1.0, then repackage and test the issue. 4. After disabling the multilingual debug mode, the iOS device will be able to update normally. Disabling the multilingual debug mode may resolve this issue, allowing the update prompt to display correctly.
About T2 Module: The T2 module is no longer recommended for use and is not supported for further purchase. Users are advised to consider using modules recommended by other platforms for development. About T1 Module: The T1 series only has modules, no development boards. Users can directly purchase modules for development. About T1-U Module: You can refer to the module specification for circuit design. Refer to the documentation for authorization burning operation:https://support.tuya.com/en/help/_detail/Kdvkkr15m4f9v.
The solution is carried out in two steps: 1. Check the connection between the serial port and the module to ensure correct connection. Serial port RX connects to module TX, serial port TX connects to module RX, serial port 3.3V connects to module 3.3V, GND connects to module GND 2. If communication is still not possible, reinstall the serial port driver. You can refer to the following links for the operation guide: Where to download the Tuya serial port driver? Common questions and answers for cloud module production testing.
For the issue of successful device programming but failed production testing, you can troubleshoot by following these steps: 1. Check whether the wiring between the module and the serial port board is correct, including the RX, TX, and RST connections between the module and the serial port board. 2. Replace the Token to check if there is a problem with the firmware corresponding to the authorization code. 3. Ensure that there is no antivirus software interfering with the production test in the computer environment. For the issue of "flash unprotect failed" when using the Beken Writer tool, you can try the following steps: 1. Check whether the wiring between the module and the serial port board, such as GND, 3.3V, RST/CEN, is correct. 2. Confirm whether the serial port driver version meets the requirements. 3. For non-Tuya serial ports without an RST pin, manual reset is required; you can try several times, especially pressing the reset button within 3 seconds after clicking erase. 4. Use the new version or the 1.6.3 version of the original factory tool downloaded from the attachment for operation.
To resolve the issue of firmware burning failure, please follow these steps to check and handle: 1. Confirm that the downloader and driver are working properly. 2. Verify whether the burning mode has been correctly entered and check if the wiring between the module and the serial port board is correct. 3. Check if the serial port driver version is correct and complete. 4. Ensure there are no issues with the computer environment, such as confirming that the relevant C++ libraries are installed (e.g., vcredist_x64.zip and vcredist_x86.zip). 5. Ensure the production solution tool is correctly installed. If the tool is installed but problems persist, it is recommended to reinstall and try again. 6. Try lowering the burning baud rate to the minimum value, then gradually increase it to observe which value succeeds. 7. Try using a different serial port or module. 8. Provide additional 3.3V power supply to the module, and it is recommended to use a power supply device with normal current requirements. 9. Use a green board, 2M high-speed serial port board for testing. 10. Try to shorten the length of the adapter cable between the serial port and the module, it is recommended not to exceed 40 cm, and separate the DuPont lines by tearing them apart and keeping a certain distance. 11. If the above steps do not resolve the issue, try setting the baud rate to 921600, which can be successful in some cases.
In module production testing, possible reasons affecting module connectivity include: 1. Ensure communication between the module and MCU is normal, and confirm the SSID and password of the production test route are sent correctly. 2. Confirm that the heartbeat packet and product query packet have been replied to before testing, and the module has completed initialization. 3. The device carrying capacity of the test router is limited, ensure the number of devices undergoing production testing at the same time is not too many. Home routers can support up to 20 devices, enterprise routers can support up to 30. 4. If the device is powered on for less than 5 seconds, initialization may not be complete, affecting connection performance. 5. Occasionally, a device may fail to connect, possibly due to limited router carrying capacity or the device's Wi-Fi module not stably entering network configuration mode. It is recommended to pay attention to router performance and ensure device initialization and stable power supply. Regarding the production test mode process: if(wifi_test_sta==0) this judgment needs to be adjusted, the latest firmware (3.x.x) version has canceled EZ network configuration, and this state is no longer issued. If the n field configuration is not selected, it needs to be changed to if(wifi_test_sta==1). For specific firmware version adjustment instructions, please refer to:https://developer.tuya.com/en/docs/mcu-standard-protocol/version_history?id=Keso963kpkr9o.
When using the iOS SDK (ThingSmartHomeKit, ThingSmartBusinessExtensionKit, ThingSmartCryption), you may encounter issues such as "Cannot find 'ThingSmartSDK' in scope" and "No such module 'ThingSmartHomeKit'". The solutions are as follows: 1. Ensure that the Podfile includes the correct SDK dependencies, such as `pod 'ThingSmartHomeKit'`, and check if the related modules are successfully installed after executing `pod install`. 2. Verify that the Framework Search Paths and Header Search Paths in the Xcode project settings include the SDK installation path, ensuring the paths are set correctly. 3. Check the status of the `ENABLE_BITCODE` option in the project's build settings and adjust it to `NO` if necessary. 4. Ensure that the SDK files (Build and ThingSmartCryption.podspec) are placed at the same level as the project's Podfile. 5. Clean the project and try recompiling. 6. If module or path-related errors still occur, confirm whether the SDK version and Xcode version are compatible. 7. Add `use_frameworks!` and `use_modular_headers!` to the Podfile and re-execute `pod install`. 8. If the issue persists, it may be due to Xcode compile cache or CocoaPods local cache issues. It is recommended to clear these caches and rebuild the project. Following the above steps can solve most problems. If the issue is still not resolved, it is recommended to create a new project for testing to determine if the problem is caused by cache or other settings.
This issue may involve communication problems between the gateway and the device, possibly due to the gateway sending incorrect query commands or abnormal device status reports. It is recommended to take the following steps to troubleshoot and resolve the issue: 1. Contact the engineers responsible for developing the sub-device and the gateway engineers to verify the data reporting and query relationship between the gateway and the sub-device. 2. Check the gateway configuration and firmware version to ensure they are the latest versions and do not have any known vulnerabilities or errors. 3. Review the device logs to identify any abnormal communication or status reports. 4. Power cycle the device and gateway to see if the issue persists. 5. If necessary, reconfigure or rewrite the firmware to ensure normal communication between the device and the gateway.
The difference between the ZigBee modules provided by Tuya with IPEX interface and without IPEX interface lies in the type of antenna interface. Modules with IPEX interface require users to connect an external antenna, while modules without IPEX interface have a built-in antenna. Users need to determine whether an external antenna is needed based on the product's usage environment and communication distance requirements. If the product needs to communicate over a long distance or penetrate many obstacles, it is recommended to use an external antenna to enhance signal coverage and stability. It should be noted that the modules sold do not include antennas, and users need to configure them themselves. According to device classification, low-power devices (such as Zigbee End Device) are suitable for battery power supply, while high-power devices (such as Zigbee Router Device) are suitable for mains power supply. The specific judgment criteria should be determined based on the usage scenario and test results.
If your app is in the listing status, you can click "Return to Development" in step four "Listing Management". If your app is in critical management status, you can directly click the steps above to reselect the market and package.
When there is no response after sending a reset command using the serial port debugging assistant, the following measures can be taken to resolve the issue: 1. Check if the module is in a low power state, which will cause the module to not respond to any commands. 2. Confirm whether the serial connection is correct: the module's tx should be connected to the serial port's rx, and the module's rx should be connected to the serial port's tx. 3. The reply to the module's heartbeat data must be completed within 500ms, otherwise the baud rate for serial interaction cannot be locked. 4. Confirm whether the module has been flashed with the general firmware.
You can find the official documentation and resources at the following locations: GitHub Repository (Source Code & README):https://github.com/tuya/tuyaopen Official Developer Guide:https://tuyaopen.ai/docs/about-tuyaopen.
If the following configurations are updated, you need to rebuild an OEM app. The platform displays the rebuilding entry at the bottom of the page after you modify related configurations. 1. App configuration process Interface configuration: When configurations for the interface are modified, the OEM app needs to be rebuilt for the configurations to take effect. Function configuration: 1. Settings for advanced functions; 2. Custom hotspot (only for apps that use a template earlier than V3.23.0) 2. Launch configuration page iOS certificate Android certificate Android map Data center 3. Optional configuration page Third-party integration: When a third-party login method or third-party push service is activated for the first time, the OEM app needs to be rebuilt. After activation, the enable/disable operations do not require app rebuilding. 4. New languages.
Dear user. Please check in the following ways: Please make sure whether the App that you previously signed up and the one you're logging in are the same; Is the user name entered correctly? For instance, you misremembered the email account or password; Please confirm the registration method at that time. For instance, you logged in with a social account at that time, but enter an email account now; If the above problem does not exist after the investigation, please feedback.
According to the document, call the scan interface when entering the homepage,set ScanType to SINGLE, and all devices with Bluetooth can be scanned. Then, customize a popup to display the scanned devices. https://developer.tuya.com/en/docs/app-development/android-bluetooth-ble?id=Karv7r2ju4c21#title-2-%E5%BC%80%E5%A7%8B%E6%89%AB%E6%8F%8F.
Automation: Find the specified automation in "Smart", and delete "Phone/SMS Reminder" from the execution actions. Alert Notification: Go to App — Me — Settings — App Notification — Phone Call / SMS Message — Alert Notification, and cancel the relevant operations.
One-time Purchase (Pay-as-you-go, no automatic renewal) Basic One-time Pack: valid for 30 days, the top choice for temporary notifications Standard Count Pack: valid for 180 days, meets regular reminder needs Long-term Large-capacity Pack: valid for 365 days, ideal for high-frequency notifications Subscription Packages (Auto-renewal, more convenient) Basic Subscription: valid for 30 days, for short-term high-frequency use Large-capacity Subscription: valid for 365 days, more cost-effective for long-term use Multi-channel Combo Subscription: valid for 270 days, full coverage of SMS + phone channels Purchase Tips: Choose one-time packs for temporary use, subscription packs for long-term use, and combo subscription packs for dual channels! Activation Path: App → "Assistant" → "SMS and Phone Notifications" → Select a package to purchase.
Hello, after purchasing the call notification service, you need to configure it first (configure by Create Scene or setting device alarm notifications) before you can receive notifications.If you still do not receive notifications after configuration, please troubleshoot through the following steps first:Check whether the system has triggered notifications in 【View Alert】 on the call notification service page. If there is no trigger, please confirm whether you have set Do Not Disturb or disabled notifications. The system will not send notifications if it is within the set Do Not Disturb period or notifications are disabled; If it has been triggered, you can check the failure reason. If it is rejected, it is recommended that you check the missed calls in your phone system to see if you missed the call, or set call blocking which caused you to miss the call. If the above still cannot solve your problem, please provide the time when you did not receive the notification and the configured notification content, and submit feedback for further troubleshooting.
Hello, after purchasing the SMS Notifications Service, you need to configure it first (Create Scene for notifications or set Device Alert notifications) before you can receive notifications. If you still do not receive notifications after configuration, please troubleshoot through the following steps first:Check whether the system has triggered notifications in 【View Alert】 on the SMS Notifications Service page. If there is no trigger, please confirm whether you have set Do Not Disturb or disabled notifications. The system will not send notifications if it is within the set Do Not Disturb period or notifications are disabled; If it has been triggered, please check the SMS in your phone system to see if you missed it, or set spam SMS blocking which caused you not to see the SMS. If the above still cannot solve your problem, please provide the time when you did not receive the notification and the configured notification content, and submit feedback for further troubleshooting.
Default number rule: The mobile phone number bound to your App account when using the service for the first time is set as the default notification number. Other receiving numbers: You can add family members' numbers at the same time, and multiple accounts can receive notifications synchronously. You can click the Set Recipient button on the Assistant - SMS Notifications Service page to add the phone numbers you want to receive notifications. Unwanted numbers can be deleted or disabled. (The mobile phone number bound to your App account cannot be deleted or disabled.).
First, please ensure that you have enabled the necessary permissions for the app, such as location permissions and Bluetooth permissions. Secondly, make sure you have correctly filled in the PID in the code, and that the device has been written with authorization information and reported an unbound status.
Follow the app instructions to add the gateway, then operate on the gateway panel to enable the gateway to add lighting and sensor devices, thus achieving control of lighting and monitoring sensor data.
Use initPanelEnvironment, Example: initPanelEnvironment({ useDefaultOffline: false, showBLEToast: false });.
Access may be unavailable due to network issues. The current source address for the integrated SDK dependency: source 'https://github.com/tuya/tuya-pod-specs.git' source 'https://github.com/CocoaPods/Specs.git'.
First, please ensure that you have enabled the necessary permissions for the app, such as location permissions and Bluetooth permissions. Secondly, make sure you have correctly filled in the PID in the code, and that the MCU and module are interacting with data normally. The module must report an unbound status to be discovered by the app.
Hello, you can disable the notification number by following the path below: App-【Assistant】—【SMS and Call Notifications】—【Set Recipient】, find the corresponding number and tap the toggle button next to the number.
You can use the video cloud storage service by following these steps: Complete service purchase: Select and purchase the corresponding cloud storage package in the App. Bind the smart camera device: First add the target smart camera in the App, then bind the device to the activated cloud storage service. Enable motion detection function: Enter the device control panel and turn on the motion detection switch. When the device detects dynamic changes in the monitoring screen, the video data will be automatically encrypted and uploaded to the cloud for storage.
The table below lists the serial port pins and wake-up pins for some Zigbee modules. These may vary depending on the firmware; please refer to the actual firmware for the correct information. Module Model Module TX Module RX Wake-up MCU Wake-up Module ZS3L PA5 PA6 PC1 PA3 ZS13S PA5 PA6 PC1 PA3 ZSU PA5 PA6 PC1 PA3 ZSC PA5 PA6 PA0 PA3 TYZS3 PA0 PA1 PF5 PA2 TYZS5 PA0 PA1 PA4 PA3 ZTU PB1 PB7 PB4 PB5/PD2 ZT3L PB1 PB7 PB4 PB5/PD2 ZT5 PB1 PB7 PB4 PB5/PD2 ZT2S PB1 PB7 PB4 PB5/PD2.
Resetting the device will not remove the app. It will go offline.
For more information, see the definition in the "Query product information" section of the protocol document: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-6-%E6%9F%A5%E8%AF%A2%E4%BA%A7%E5%93%81%E4%BF%A1%E6%81%AF%EF%BC%880x01%EF%BC%89.
Custom implementation requiredThingDeviceDetailExternalProtocol /// Disable the mini program functional page - (BOOL)disableDeviceDetailMiniProgramFuntionalPage; Custom implementation requiredThingDeviceDetailExternalProtocol. /// Custom device detail page - (BOOL)customDeviceDetailPageWithDevice:(ThingSmartDeviceModel *)device group:(ThingSmartGroupModel *)group businessParams:(NSDictionary *)businessParams; Code example: - (BOOL)disableDeviceDetailMiniProgramFuntionalPage{ return YES; } /// Custom device detail page - (BOOL)customDeviceDetailPageWithDevice:(ThingSmartDeviceModel *)device group:(ThingSmartGroupModel *)group businessParams:(NSDictionary *)businessParams{ [self.navigationController pushViewController:[testViewController new] animated:YES]; return YES; }.
The device cannot temporarily obtain the DP list.
Currently not completed, please stay tuned.
Devices in the Matter protocol support network configuration through scanning codes, but do not support direct custom network configuration through hotspots. Therefore, devices using the Matter protocol can be networked, but the process is completed by scanning a QR code, rather than through custom hotspots.
Hello, You can find "Home" - "Current Page Card Opacity" in the interface configuration - detail configuration, adjust it to 100%, and the color will be consistent.
Indicates the average number of LED beads per total length of the light strip. For example:The device reports the data of the light strip length function point as 500cm, with 100 light beads, indicating that the light strip is 5 meters long, with one LED bead every 5 centimeters, totaling 100.
Device logs on the platform can view upgrade progress logs, without detailed upgrade interaction process, refer to platform logs.
When using the WBR3 module, if the MCU can normally respond to the module's heartbeat packet and the power supply is normal, but the applet cannot trigger the module function, and communication between the MCU and the module is not normal, the following measures can be taken: 1. Confirm whether the sending interval of the heartbeat packet is correct, it is recommended to be once every 15 seconds, not 3 seconds. 2. Check whether the wiring of the serial port is correct to ensure that the module normally receives the heartbeat data sent by the MCU. 3. Use debugging tools to simulate communication and confirm that each function call is normal. 4. View and update the module's firmware version to the latest version (3.1.69). 5. Use the debugging assistant to simulate MCU network configuration, view the device upgrade page of the APP to obtain the module firmware version. 6. Send the heartbeat within 500ms to ensure high priority of serial port interrupts. 7. Use a serial port board to read the module logs (baud rate 115200) to check the normality of communication. 8. Capture the data of MCU tx and module rx to ensure correct hardware connection. 9. Troubleshoot hardware issues, especially components like resistors on TX that may cause signal attenuation.
Sending 00 is because the module initially sends heartbeat packets at different baud rates.
Before the framework initialization, call tuya_ble_set_startup_attr(TUYA_BLE_ABILITY_T attr) and set it to network configuration mode only. After successful network configuration, call the tuya_ble_set_serv_switch interface and set it to false to turn off the Bluetooth service.
Curtain motor common faults include failure to start, unsmooth operation, excessive noise, etc. You can try the following solutions: 1. Check if the power connection is normal to ensure stable power supply to the motor. 2. Clean the pollutants around the motor to ensure unobstructed operation. 3. If the noise is too loud, check if there are worn or loose parts inside the motor, and contact maintenance personnel if necessary. 4. If the motor fails to start, it may be a control panel or remote control failure, please check the battery or converter connection. If the above methods cannot solve the problem, please contact professional after-sales personnel for repair.
When the curtain device does not respond when clicking open/close on the app or Tuya screen, you can try the following solutions: 1. Check the network connection. Ensure the Wi-Fi network used by the device is smooth, with both upload and download speeds not lower than 2 MB/s or 16 Mbps. You can try using a network speed test app for testing. 2. Move the phone closer to the device, keep the app open and stationary for 3 minutes, and confirm whether the device is still online. 3. Check the device logs to see if there are commands issued but lacking data reporting. 4. If the device data is not reported normally, you need to feedback the issue to the product manufacturer or seller for further hardware or software inspection. The Tuya platform does not directly manufacture or sell products but provides platform support.
The power consumption of a magnetic latching relay is very low because it only consumes energy when changing the contact state. Switching from normally open to normally closed or from normally closed to normally open only requires a short current pulse, and no energy is consumed in the holding state. This feature makes magnetic latching relays very suitable for energy-saving applications, such as single-wire switches or battery-powered devices.
In the scenario of Bluetooth Mesh light group control, the group panel does not support displaying all functions of a single device, including the countdown function. To achieve the countdown function in the group, please follow these steps: 1. Check whether all required function points have been correctly added to the panel. 2. If newly added function points are not displayed, you can try removing the device, clearing the app cache, and reconfiguring the network. 3. Confirm the relevance of the function points. Currently, the group panel does not support the countdown function, and there is no other way to achieve this function. This is because single light control uses local timing, while group control uses cloud timing, which requires gateway support to be implemented.
To access S3 resources using @aws-sdk/client-s3, please follow thetutorialto configure the domain names related to the request, and then follow the relevant AWS tutorials to integrate on your own.
Wireless certification fixed frequency prototypes generally cannot directly use existing mass production modules. This is because most wireless products do not have parameters that can be clearly and comprehensively displayed on test instruments during normal operation. The wireless parameters of the product need to be set to work stably within specific channels and modulation to better demonstrate the various transmission parameters of the wireless module for RF testing, which means setting a fixed frequency. Samples can be purchased from sample stores or produced according to the guidance documents. However, for example, cellular modules can generally use production modules, but a test SIM card must be used to connect to the instrument for testing.
There is no fixed limit on the number of DP data points reported by the module, but there is an excess limit on message reporting. Users can refer to the relevant documentation to understand the billing and regional calculation rules for message reporting. Detailed information can be viewed at the following link:https://support.tuya.com/en/help/_detail/Keu1n45gp8qa3.
Just authorize another enterprise, no charge, reference document:Cross-enterprise authorization.
Please check the document:https://developer.tuya.com/en/miniapp/log/changelog.
If the device cannot be unbound through conventional methods, it may be because the device is set to strong binding mode. If the device is strongly bound, it must be removed from the App using the original account before it can be bound to a new account. For devices with special requirements, it is recommended to contact relevant customer service or technical personnel for further processing. In some cases, it may be necessary to submit a ticket request on the developer platform to achieve unbinding or removal operations. Ensure that the device is not unable to unbind due to hardware failure. If necessary, check the device hardware and try unbinding again.
The CB3S module specification mainly covers the application fields of the module, pin definitions, electrical parameters, and Wi-Fi and Bluetooth RF parameters, but does not include detailed content on register operations and Wi-Fi function configuration. Regarding the requirements for register operations and Wi-Fi function configuration: If the product is "zero code development-free direction," such as the "Five-way Scene Switch_Wi-Fi & Bluetooth LE" product, programming is not required, so no information on register-related operations is provided. If you are developing other products and have related needs, you can check theDocumentation Center for relevant information.
To obtain the Gateway SDK development package, users first need to have the appropriate compilation toolchain. The Gateway SDK is provided as a C static link library, so users also need to ensure that the runtime environment is Linux and prepare the host program to initialize and handle the SDK lifecycle. Users can obtain the development package through Tuya Wind IDE, specifically by visiting the link:https://developer.tuya.com/en/docs/iot-device-dev/Gateway-Product-Software-Development-Kit?id=Kbfjuqtma64w4.
To integrate the ATmega8A microcontroller into the Tuya platform and communicate using the Tuya MCU protocol, the following steps can be taken: 1. Create a product that meets your needs. After the product is created, serial port protocol and quick start documents will be provided for reference. Relevant documents can be accessed at the following link: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-quickstart?id=Kcyugb6rz0sp0 2. For reference documents on hardware design, you can check the following link: https://developer.tuya.com/en/docs/iot/WBRxxSerialModuleUART?id=Kamx66vpa4r4w 3. Regarding recommendations for Wi-Fi or Zigbee modules, the choice of module depends on specific technical requirements and usage scenarios. Common modules include TYWE3S, WB3S, WR3E, or ZS3L, and specific choices can be further researched according to needs. 4. For requirements or limitations of using the MCU protocol on a custom PCB, refer to the detailed instructions provided in the quick start document. 5. If device certification is needed, consider the integration scheme of the external MCU with the Tuya module in the device architecture, and communicate with relevant certification bodies to understand specific certification requirements. 6. When connecting ATmega8A (5V) with Tuya module (3.3V), ensure to use an appropriate voltage conversion scheme to protect the device. If there are any other questions or need for assistance, it is recommended to communicate again with the Tuya technical team.
When you encounter the error: java.lang.Unsatisfiedlinkerror while uploading an app, unable to find the implementation of a specific method, you can resolve it by following these steps: 1. Confirm whether the APK you are using is the latest packaged version, ensuring all updates are included. 2. Check whether the build.gradle file has correctly added the security components and the implementation fileTree(include: ['*.aar'], dir: 'libs') dependency. 3. Confirm whether the device's CPU architecture is x86. Currently, the SDK only supports armeabi-v7a and arm64-v8a architectures. 4. If x86 or x86_64 architectures have been added in the app's build, remove these architectures from the build, and then re-upload the application.
Solution is as follows: 1. Check the device logs to confirm whether the scheduled tasks are executed normally. 2. Investigate whether there are other reasons for the device to be turned on: Check if there is control through third-party platforms (such as Alexa). It is recommended that users cancel the association of the device with the Alexa application or stop using voice capabilities to control the device. 3. If both scheduled tasks and third-party platform control are fine, it is recommended to further investigate whether there is a hardware failure in the device.
To resolve the issue of the firmware version being unavailable for selection, please follow these steps: 1. Refresh the page to see if there are available firmware versions to choose from. 2. If there are still no selectable versions after refreshing the page, try clicking to change the version to see if there are other available firmware versions. 3. If you successfully select an available version, you can proceed with order submission. If the issue is still not resolved, it is recommended to contact technical support for further assistance.
When using the Android SDK for device network configuration, if the device has successfully connected but the interface still shows a searching status, you can refer to the following steps for troubleshooting and resolution: 1. Ensure that there is logic to update the UI in the `onFound` and `onConnected` callbacks of the `connectDevice` method. When the callback is triggered, call the relevant methods to refresh the device list or status on the interface. 2. Call the `getHomeDetail` interface and query the `deviceList` based on the returned `HomeBean`. You can find specific usage examples and documentation on the Tuya developer platform. 3. If you have already called the above interface but cannot query the device, please check whether the network configuration was successful and confirm whether the home ID used to query the device list is consistent with the home ID used during network configuration. 4. If the issue is still not resolved, it is recommended to provide the network configuration account, home ID, and network configuration logs to the technical support team for further analysis of the problem.
When using the cloud module burning tool for burning, if you encounter a situation where the authorization code cannot be obtained, it may be due to the following reasons: 1. Network connection issues: Please check if the network connection is normal to ensure the burning tool can access the authorization server. 2. Account permission issues: Ensure that the account applying for the authorization code has the appropriate operational permissions and that the authorization code is applied using the correct account. 3. Product configuration issues: Check whether the product corresponding to the applied authorization code has completed firmware configuration on the platform. Solutions: If it is a network issue, it is recommended to switch to a stable network environment. If it is an account permission issue, you need to operate using the account corresponding to the authorization code. If it is a product configuration issue, you need to complete the product firmware configuration on the platform and apply for a new authorization code.
If there is an issue with Tuya Wi-Fi products where 3-4 devices disconnect when leaving, the possible reason is the router's device access limit. Suggestions: 1. Use a pure Bluetooth module + Bluetooth gateway or Zigbee module + Zigbee gateway to reduce dependence on Wi-Fi. 2. Replace with a higher performance router, or add routers to support more device connections.
SDK identifies after installing new firmware through the gateway and restarting. After installation is complete, the SDK will update the version number to the cloud, and the cloud will push a message to the App to confirm the upgrade is successful. Ensure the gateway restarts and updates normally to accurately convey upgrade information.
To ensure that fingerprint and card information is not lost during device synchronization, it is necessary to report complete DP information each time data is synchronized, including fingerprints, passwords, and cards, even if there are no changes, all must be synchronized. For reporting the initial state, the following steps can ensure that the app interface displays consistently with the device state: 1. Use the DP message report (0x06) command to synchronize the current state of the device to the cloud after the device is powered on or successfully networked, including unlocking methods, unlocking delay, and other initial configurations. 2. After the device is connected to the network, use real-time status reporting (0x05) to actively send the current state of the device to the cloud to ensure the app can receive and update the display. 3. Confirm that the data reported by the device is consistent with the data displayed on the cloud UI panel, check the interaction logs between the device and the cloud to ensure correct data reporting. 4. If there is a discrepancy between the app interface display and the device reported status, it is recommended to submit a new work order to seek further assistance from the panel engineer.
To configure the smart socket to connect to Wi-Fi, follow these steps: 1. Ensure your Wi-Fi network is working properly and the smart socket is powered on. 2. Use the app on your smart device (such as Tuya) to enter the device addition page. 3. Press and hold the setup button on the smart socket until the indicator light starts flashing, indicating the socket is in network configuration mode. 4. In the app, select Wi-Fi configuration or smart configuration, follow the prompts to select your Wi-Fi network, and enter the password. 5. Wait for the device to connect to the Wi-Fi network, which may take a few minutes. 6. Once connected successfully, the socket indicator light will stay on, and you can view and control the socket in the app. Note: Ensure the smart socket and the router are on the same Wi-Fi band (2.4GHz) to ensure compatibility.
Using PWM dimming technology to achieve a flicker-free effect can be optimized in the following ways: 1. Increase the PWM frequency: If using a mobile phone for testing, the PWM frequency can be increased to above 8KHz, which can reduce the flicker effect during shooting. 2. When using a flicker tester, if increasing the PWM frequency is ineffective, a filter circuit needs to be added to the hardware circuit to weaken the ripple effect. Through these measures, the flicker problem during PWM dimming can be effectively reduced, ensuring the stability of light output and visual comfort.
To achieve real-time changes in lighting when adjusting the brightness or color temperature of Wi-Fi protocol devices through an app, you need to ensure the following: 1. Ensure the device supports stepless adjustment of brightness and color temperature, rather than just step value adjustment. 2. Add the adjustment function point to ensure that real-time data can be continuously sent during sliding to achieve real-time changes in device status. 3. The value range for brightness and color temperature is fixed. It is recommended to add or modify function points according to actual needs and then retry. 4. Remote control service command 0x0A can be used for continuous increase and decrease of brightness, which is an important command for achieving stepless adjustment. After completing these steps, the device should support real-time changes during sliding adjustment.
When selecting a module, consider the following factors: 1. Operating Temperature: Ensure the module operates stably within the expected environmental temperature range. 2. Size Specifications: Match the space constraints of the product. 3. Supported Antenna Type: Choose the appropriate antenna to ensure good signal strength. 4. Soldering Method: Confirm that the module's soldering method is compatible with the product's manufacturing process. Based on the above factors, conduct a comprehensive evaluation to select the most suitable module.
When choosing a Tuya Bluetooth Mesh Gateway, consider the following factors: 1. Number of nodes: Select a gateway that supports the number of nodes required to connect your devices. 2. Network robustness: Multiple gateways can enhance network robustness, so consider configuring multiple gateways. 3. Compatibility with other devices: Ensure the gateway is compatible with other existing devices and systems. 4. Usage scenarios: Choose a suitable gateway based on usage scenarios (indoor, outdoor, etc.). 5. Installation and maintenance: Consider the ease of installation and the cost of future maintenance. For specific purchasing questions, it is recommended to contact your business manager.
In the global configuration file `global.config.ts` of the mini program, the correct position to set `disableCache: true` is within the exported configuration object. Ensure that this configuration property is used correctly and included in the actual exported configuration object, for example: ```typescript export const config = { disableCache: true, // other configurations }; ``` The specific position may need to be adjusted according to the actual project structure and configuration content. Make sure `disableCache: true` is placed in the root configuration object and correctly exported so that the configuration can take effect.
Hello, it is just a suggestion to turn on Bluetooth, not a mandatory requirement. You can click × to close the prompt page, which will guide you to connect to the hotspot emitted by the device. Turning on Bluetooth will make it easier to add, as Bluetooth search generally involves fewer steps than other search methods.
The reasons for the smart wall zero-fire switch device being offline may include: 1. Signal issues: The communication distance between the switch and the gateway is too long or there are too many walls in between, leading to unstable or interrupted signals. It is recommended to shorten the distance or increase the number of gateways; 2. Network issues: The router is powered off or disconnected, affecting the device's network connection. The device will come back online once the network is restored; By confirming the above reasons and taking corresponding measures, the frequent offline issue of the smart wall zero-fire switch can be effectively resolved.
Network Diagnosis is a one‑click online tool designed to help troubleshoot connectivity issues. When you encounter problems while using the app, this function performs an in‑depth check of the app’s current network environment.The Diagnostic Log it generates helps our technical team identify and resolve issues quickly. Instructions Tap Start Diagnosis. Once complete, tap Upload Log. Tap Copy Log to Clipboard. After you see the "Log copied to clipboard" message, paste the content into a chat or feedback ticket and send it to us. Once we receive your log, we will troubleshoot and provide a solution as soon as possible.
The app is being adapted for HarmonyOS. Currently, it supports HarmonyOS 5 (HarmonyOS NEXT) and above. Please refer to the display in the Huawei official AppGallery for details. The app is not supported if it cannot be found.
The video image of the smart camera may appear inverted due to the following reasons: Camera installation direction: If the camera is installed upside down, the video image will appear inverted. In this case, you need to adjust the installation direction of the camera so that it faces up. Camera setting problem: Some cameras have a "rotate image" or similar option in the settings to adjust the direction of the image. If this setting is misoperated, it may also cause the image to be inverted. You can access the settings page by clicking the icon in the upper right corner of the device control page, and check whether the relevant options are available for the device on this page. If the above methods cannot solve the problem, it may be the camera itself problem, it is recommended that you contact the device seller or manufacturer for help. Hope this answer helps you!
A reset can be generated in 10ns+, and a duration of several tens of milliseconds, such as 50ms, is generally recommended. An RC filter must be added to the RESET signal.
If the firmware upgrade fails, you can follow the troubleshooting steps below to resolve the issue: Network stability assurance: Firmware upgrades can sometimes fail due to unstable internet connections. We recommend trying to change to a more stable network environment or using a mobile hotspot to attempt the upgrade again. This will provide a more reliable network connection to ensure a smooth firmware upgrade process. Bluetooth device firmware upgrade considerations: For firmware upgrades involving Bluetooth devices, it is important to keep the relevant app in the foreground throughout the upgrade process. Exiting the app during the upgrade can potentially lead to firmware upgrade failures. Therefore, please ensure that you do not exit the app while the firmware upgrade is in progress to ensure a successful completion. If the problem still cannot be resolved using the troubleshooting methods above, we recommend that you contact the seller for further assistance and support. Thank you for your support and understanding.
Hello, device data from different Homes is isolated from each other. After creating a new Home, devices from the original Home will not be automatically synced to the new one. Only devices that others have shared with you individually will be displayed on all Home pages; all other devices are only visible within their respective Home.
Open the App homepage, tap the menu icon (☰) in the upper right corner, and select Manage Rooms to enter the page; On the Manage Rooms page, tap the target room group to access its management interface; Select the Room option, and the page will display a list of all rooms available to be added to this room group; Find the room you want to add, tap the Add button, and you can complete the addition of the room to the room group.
Zigbee low-power firmware has an external INT pin. When the MCU needs to send data to the module, it must first wake up the module via this pin. Currently, the general-purpose Zigbee low-power firmware only supports IO wake-up and does not support serial port wake-up. For details, please refer to: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-zigbee-uart-protocol?id=Kdg17v4544p37#title-1-%E4%BD%8E%E5%8A%9F%E8%80%97%E5%94%A4%E9%86%92.
Function points generally choose the string type, and need to report hexadecimal data. The panel generally supports displaying UTF-8 data, and the encoding of data reported by the MCU needs to be implemented by the developer themselves. Reference example:.
First, check if the device is physically obstructed Check if the camera’s pan-tilt unit is blocked by objects such as dust covers, cables, or storage racks; gently move the pan-tilt to check for jamming or abnormal noises, then remove the obstructions and try to pan/tilt the camera again. Check the device panel and perform pan-tilt calibration Locate the direction control buttons on the device’s panel and try to directly control the camera’s rotation via these buttons; if pan-tilt calibration is supported, follow the instructions in the user manual to complete the calibration and then test the function. Try resetting the device Follow the steps in the user manual to perform a factory reset, then re-bind the device after resetting and check if the camera can pan/tilt normally. Troubleshoot hardware malfunctions If the camera still cannot pan/tilt after performing the above steps, there may be a hardware malfunction. It is recommended to contact after-sales service or the seller to request inspection and repair.
If the schedule tasks and smart scene execution of some devices in the group are abnormal, you can troubleshoot and handle it by following these steps: Check the device online status Verify whether the abnormal devices are online and connected to the network; offline devices cannot receive group execution commands. You can try removing the devices and adding them again to restore the network connection. Check the group configuration Enter the group management page and confirm that the abnormal devices have been correctly added to the target group and the corresponding execution actions have been configured for them. Resync scenes and schedule tasks Delete the schedule/smart scene tasks associated with the abnormal devices, add them again and save the configuration; you can also remove the devices from the group and add them back, then rebind the relevant tasks. Feedback for further troubleshooting If the above operations are all ineffective, please record the model of the abnormal devices, details of the group configuration and specific fault phenomena, and submit the issue through the designated feedback channel.
If your device can only detect and connect to the 2.4G WiFi band but not the 5G WiFi band, the main reason is usually that the WiFi module equipped on the device only supports the single 2.4G band and is incompatible with the 5G WiFi band. We recommend that you first refer to the device's product manual or contact the seller directly to verify the band support of the module.
If a smart task (including Tap-to-Run and Automation scenes) fails to execute normally, troubleshoot and resolve the issue by following the steps below: Check Task Execution Logs Go to the detail page of the Automation or Tap-to-Run scene and query the task execution logs. The logs will clearly indicate whether the task was executed normally and the specific cause of execution failure, allowing you to locate the problem directly according to the prompts. Verify Device Operating Status Check if the device is powered on, turned on and online normally; at the same time, confirm that the device has a stable network connection and no offline issues during the task execution period. Recreate the Smart Task If the device status is normal but the task still fails to execute, delete the abnormal task, then re-add and save the new task configuration. Rebind the Smart Device If the problem persists after recreating the task, first remove the device from the App, and after completing the re-addition, configure the corresponding Timing or Automation tasks again. Check the Connection Method of Bluetooth Devices For Bluetooth-connected devices, only Bluetooth Mesh Devices or devices within the effective Bluetooth communication range support scene control execution. Devices out of range or non-Mesh network devices may fail to respond to task instructions. Notes Automation rules created based on environmental parameters such as temperature and temperature-humidity may experience execution exceptions due to the device's edge trigger mechanism. You can submit the problem through the designated feedback channel, and we will further troubleshoot for you. Edge Trigger Explanation: The device triggers automation only at the moment when the monitored value crosses the set threshold (e.g., the trigger is activated when the temperature rises from 25℃ to 26℃, and no repeated triggers occur if the temperature remains above 26℃). Why doesn't the Leave or Arrive (beta) feature take effect? Why d.
Hello, please troubleshoot in the following ways: First, confirm whether the device is shared with you by others. Shared devices cannot be used as execution actions for Automation or scenes for the time being. If the device is not shared with you by others but the corresponding device or its functions cannot be found, it is because this product does not support adding them to Automation and Tap-to-Run. If the device can be found but some functions are missing in the function category, it means only the displayed functions support scene linkage. The options for devices and their functions in scene linkage (Automation/Tap-to-Run) are set by the product manufacturer. If you want to add support for scene linkage (Automation/Tap-to-Run) for more devices or their functions, you can feed back this problem to the product after-sales team for their subsequent improvement. Thank you for your support and understanding.
Your device may currently be in Bluetooth or local area network (LAN) control mode. Please switch your phone's network to a different WiFi or 4G/5G environment, or turn off Bluetooth on your phone. Then, check in the app to see if the device is online to confirm if it is actually connected to the external network, as only devices connected to the external network can be controlled through cloud-based automation. (Bluetooth devices need to be connected to a gateway to work in automation.).
Tap-to-Run There are 3 main types of Tap-to-Run in the App. You can quickly start the smart devices in your home by setting up Tap-to-Run, saving the trouble of turning them on one by one. Control Devices: Add the smart devices you want to control via Tap-to-Run Example: You can turn on all the required smart devices in your home at the same time through Tap-to-Run, without having to turn them on individually. Select Smart: Add the Automation you want to activate via Tap-to-Run (Pre-configured Automation is required) Example: You can activate the pre-configured Automation through Tap-to-Run, without triggering the trigger condition of the Automation. Delay: Add a delayed task Example: You can set a desired delay for the linkage between two devices by adding a delay in Tap-to-Run. Automation There are 4 main types of Automation in the App. You can fully utilize the smart devices in your home by setting up Automation to enable a smart life. When weather changes: Linkage between the external environment and devices Example: You can set the air conditioner to turn on automatically when the temperature is higher than 29℃; or set the air purifier to turn on automatically when the PM2.5 value exceeds a certain number. When location changes: Linkage between geographic location and devices. You can choose to perform specific actions when arriving at or leaving a certain place Example: You can set the air conditioner and water heater at home to turn on automatically when you are near home; or set all electrical appliances at home to turn off and the motion detection function of the camera to turn on when you leave home. Schedule: Linkage between the timing function and devices Example: Set the curtains to open automatically at 8 a.m. on workdays. When device status changes: Linkage between device status changes and other devices Example: You can set the aromatherapy machine and air purifier at home to turn on automatically when the air conditioner is turned on; or set the ala.
Tuya scheme supports BLE communication scheme. The development method for door locks and accessories is the same, using BLE low-power Bluetooth communication. There is no dedicated development documentation, you can apply for the BK3633_M SDK to obtain the accessory development package and proceed with development. Develop the lock normally, and if you encounter any problems, you can communicate within the group.
Tuya's SMB lighting solution has significant differences from ordinary Tuya Bluetooth in terms of functionality, application scenarios, and technical characteristics. SMB lighting is suitable for commercial and high-end scenarios, featuring a distributed architecture and AI agents; ordinary Tuya Bluetooth is more suitable for home or small-scale scenarios. SMB is not Bluetooth mesh, and developing an SMB solution requires creating a product from the corresponding entry point. Pricing issues need to be consulted with relevant personnel. Tuya Bluetooth modules are suitable for specific small or home scenarios and cannot be directly shared with the SMB lighting solution.
Tuya iOS App control of non-Tuya Matter Thread devices requires an Apple Matter Hub, as Apple has restrictions that necessitate calling their interface to achieve this functionality. This may be related to compatibility with Apple's system. Other brands like Google and Samsung have similar rules. Actual test devices need to be scheduled in advance for confirmation. It is recommended to consult technical support or check the product documentation for more information.
If the door lock log shows that the door opening record was uploaded successfully, but the App does not display it, it may be because the record-type data is not enabled. Request the device ID for further investigation of the issue, and contact Tuya staff to enable the relevant services if necessary.
Tuya Cloud can test the configuration items of the Matter protocol. The information of the Matter protocol must be configured to ensure that the device is compatible with the Matter protocol and operates normally.
To optimize device programs and avoid excessive message reporting, it is recommended to take the following measures: 1. Reduce unnecessary message reporting frequency. 2. Optimize program logic and set effective conditions, such as reporting messages only when the temperature change is greater than 0.5℃. This logic optimization not only helps reduce device power consumption but also improves device stability. Additionally, if the device has already experienced excessive message reporting, you can apply for a free excessive message gift on the message reporting statistics page, which will provide enough time to optimize program logic and perform OTA upgrades.
The Tuya Cloud Test app currently does not support the miniapp panel. The mini program panel needs to be used in the new version of the app, OEM app, and app SDK.
To display string type data in a control, you can take the following steps: 1. Use the function `mcu_dp_string_update()` to report string data. The parameters of this function include the data point ID, the pointer to the string data, and its length. 2. Ensure that the string data is correctly converted to the required format for uploading. It is recommended to convert the string to hexadecimal format for reporting. For example, if the string "abcd1234" is reported, the correct hexadecimal data is: "61 62 63 64 31 32 33 34". 3. After reporting, the control will display the data according to the attribute settings. Ensure that the data is uploaded to the specified component in the correct format, and the display effect depends on the implementation of the control.
Hello, Bluetooth Mesh devices now support the function of local scene linkage after the setup of a local network.
WB3RD's Wi-Fi dual-band module supports frequency ranges including 2.4GHz and 5GHz.
If the DP data reporting is abnormal, it is generally because the reporting does not follow the protocol. You can capture the serial port data and compare it with the protocol. Or use the debugging assistant for debugging first.
In anti-misoperation mode, the device cannot unbind from the APP through commands. In the normal network configuration mode, the device will automatically unbind from the APP.
To ensure the temperature units of the device and the app remain consistent, please follow these steps: 1. Add the DP for temperature scale switching. 2. Include the temperature scale status byte in DP114. This can solve the issue where device operations cannot be reported to the app and ensure the device changes correctly when the app switches temperature units.
If the burning of an empty module shows success, but some modules have not burned the authorization function, it may be because the number of token authorizations has been exhausted. If the production test fails, you need to refer to the document-FAQfor troubleshooting or submit error screenshots throughTechnical Ticketto seek technical support for processing.
THP23-ZB-X gateway supports Zigbee 3.0 standard devices and is available for use abroad without regional restrictions.
The current of the WBR3 module in the lowest power consumption state is 1.5mA. The measured current in low power consumption state is 30mA, so it is unlikely to achieve long battery life. It should be noted that to achieve lower power consumption, power-off or other low power consumption designs can be considered. Low power consumption design has a great impact on battery life, and even when not connected to the network or in active state, battery life still needs to be achieved through power-off circuits or other solutions to achieve battery power saving effects. If you want a low power consumption long-lasting active module, you can consider the T3 series, such as T3-U, T3-3S, etc.
The Wi-Fi bands supported by the device are determined by the module. If you need to support the 5G Wi-Fi band, please choose a module that supports 5G for device design or replacement. Check the device manual or module specification to confirm the supported bands. All routers typically support the 2.4GHz band, but the 5GHz band is only available on devices with modules that support 5G.
When encountering a situation where the screen device is offline and cannot be reset, please first confirm whether the device is connected to the APP or the hotel SaaS system. If the device is an old M1 version without gateway capability, it is recommended to perform the following operations: 1. Try unbinding the device through the APP, and then reset the device. 2. Try changing the Wi-Fi network or use a mobile hotspot for connection. These steps are intended to eliminate issues with network connection and device version to restore the device's online status.
In the map interface, you can switch to the quick map building page by resetting the current map. After resetting, the device will attempt to report empty map data. If the homepage still displays the map instead of the quick map building page, you need to check the interface parameters and the device reporting status. It is recommended to share local device logs during troubleshooting to more accurately pinpoint the issue.
For multi-mode gateways that support both wired and wireless connections, the mobile phone and gateway need to be on the same network when connected via wired. This is because the app is designed to discover and connect devices through the same local area network (LAN) to enable information transmission. For devices that support dual-mode networking, there is no LAN restriction when using BLE networking.
Suggest allocating pins based on actual hardware. If pin changes are needed later, the firmware must be re-burned to ensure the system can correctly execute the updated settings.
The price difference of Zigbee modules is mainly influenced by different chips. Chips determine the performance and cost of the modules, so different chips may lead to differences in module prices.
Report according to the packet protocol, please refer to the document:https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-16-%E7%8A%B6%E6%80%81%E4%B8%8A%E6%8A%A5%EF%BC%88%E5%BC%82%E6%AD%A5%EF%BC%89(0x07).
Some devices can automatically connect to the platform after powering on, but some devices need to be connected by pressing a button to wake up. These devices usually do not use wake words, so button operation may be required before each conversation. However, using wake words for natural device wake-up and connection may be more convenient.
Wi-Fi module model S.TL-DQ-XP-A-WBR1-1 is still available for purchase.
The statistics of the sensors have been added and support for chart display. Please confirm that the relevant functions have been correctly configured and ensure that the sensor data is reported to the cloud normally. You can use the chart component binding function points to display the required sensor data statistics results.
To associate the data of temperature and humidity sensors with lighting fixtures in the App, there is currently no direct configuration entry. You can achieve this by creatingscene linkage: set the sensor as thetrigger device and the lighting fixture as theexecution device.
The main difference between the WBR1 and WBR3 modules lies in the packaging. The WBR1 module can support a 5V serial port due to its packaging. It is recommended to choose between these two modules based on the specific needs of the device and refer to the module specifications and Tuya's module selection platform for more detailed information. Link:https://solution.tuya.com/en/hardwareSelection.
We provide solutions for detecting Wi-Fi signal strength and Bluetooth signal strength, suitable for product production testing. Signal strength data can be obtained by sending instructions through the MCU. For detailed development information, please refer to the relevant serial protocol document for device production testing instructions.
Both BK3633QN33 and BK3633QN49 chips support secondary development through SDK. For developing these two types of chips, users need to apply for a development whitelist. After obtaining the whitelist, users can develop according to the provided SDK. For specific application procedures and required materials, please contact relevant technical support. BK3633QN33 supports MCU SDK solutions, users may also apply for a whitelist.
To resolve the issue of the WBR3 device being unable to connect to the network, you can try the following steps: 1. Increase the priority of the serial port interrupt to ensure timely processing of serial data. 2. Use the single-step debugging function to check the code, especially where data registers are read in interrupts and the main loop, to confirm whether there is a data read conflict. 3. Test the reference code to ensure that the code logic is consistent with the requirements of the device network configuration function. 4. Check the data reading parts in the interrupt handling and the main loop to ensure there are no conflicts caused by concurrent access to the same data register. 5. If the problem persists, consider further debugging the details of serial data reception and processing to ensure correct data transmission and interpretation.
Possible reasons include CBU not receiving data, CBU damage, or hardware grounding issues. It is recommended to check the hardware, confirm that it shares the same power supply and ground with the MCU. You can use the Tuya module debugging assistant to test whether the module is functioning properly.
After the access control machine enters the network configuration mode, it cannot exit the network configuration state by restarting the power. It is recommended to manually exit the pending network configuration state by sending a reset command through the Wi-Fi module. If you do not want the device to enter the network configuration state, avoid triggering the network configuration. For the issue of poor Wi-Fi signal, consider controlling the EN pin of the module or adjusting the position of the router to avoid network configuration problems.
Due to the lack of a standard library in the chip compilation chain, it is impossible to use math.h through compilation. It is recommended to write software functions to achieve related functions. You can consider using a custom implementation method to calculate the square root, ensuring that the code is independent of the standard library to be compatible with the limitations of the chip's compilation chain.
If you encounter issues with obtaining Beijing time during use, you can try the following methods for troubleshooting and resolution: 1. Capture serial port logs to identify possible causes of the issue. Analyzing serial port logs can help pinpoint the problem. 2. Check if the program version is correct, ensuring that you are using the latest version and correct configuration. Through the above steps, you can usually effectively resolve issues related to time acquisition.
The coordinate data calculation for the RVC SDK sweeper's area cleaning box, restricted area box, virtual wall line, and point-to-sweep is based on the machine coordinate system. The specific calculation methods are as follows: Coordinate System Explanation Machine Coordinate System: The coordinate data for area cleaning box, restricted area box, virtual wall line, and point-to-sweep are defined relative to the machine's starting position (origin O). Coordinate Type: Uses INT32 integer values, representing the number of grids relative to origin O. Actual Distance Calculation Actual Distance Formula: The calculation method for the actual position is: Actual Distance = Number of Grids × Grid Resolution For example, if the grid resolution is 5cm, the actual position represented by the coordinate (100, 200) is: (500cm, 1000cm) = (5m, 10m).
When screen artifacts appear accompanied by the printing tuya_ipc_rtp_pack_nal h264 error, it usually indicates an error in the H.264 encoded data packet during video stream processing. This may be caused by the following reasons: NAL unit start code issue: Decoding should only support NAL unit start codes beginning with 0x00,0x00,0x00,0x01, and not other formats like 0x00,0x00,0x01,0x06. If the packet format does not meet the requirements, it may lead to decoding failure, resulting in screen artifacts. Network transmission issue: Unstable network may cause video data packet loss or errors. Check the stability of the network connection and ensure that the packets are not damaged during transmission. Video stream encoding issue: There may be issues with the encoder generating the video stream. Ensure compatible encoding parameters are used and check if the encoding implementation complies with standards. It is recommended to first check whether the video stream format complies with the H.264 encoding standard to ensure the correctness of the packets.
Error Message bt hal send fail.-28689 refers to an error that occurred while sending data during Bluetooth communication. This error is usually caused by the following reasons: Bluetooth adaptation layer issue: Check the Bluetooth adaptation layer code to ensure the interface returns need to be 0, not other abnormal values. Service registration issue: It may be that when adding a service, the handle, attributes, parameters, etc. were not correctly passed to the SDK, resulting in data sending failure, most commonlythe registered conn_handle is inconsistent with the sent conn_handle. Bluetooth environment interference: There may be interference from other Bluetooth devices, causing unstable communication. To better locate the problem, it is recommended to check the relevant code to ensure that the Bluetooth sending operation is properly handled and that the return value is correct for each interface call.
If you choose Open development, the Tuya Developer Platform supports upgrades through the module firmware upgrade function. Developers can create module firmware on the platform, independently select chips, and configure modules for functional expansion and upgrades.
If the WBRU module can enter the distribution network but cannot connect to the router, it may be caused by a firmware issue. Please confirm the firmware version and try testing with different versions of the firmware. At the same time, be sure to check the signal strength, password, and settings of the router to ensure they are correct. Ensure stable power supply to the module. It is recommended to use a debugging assistant for more detailed troubleshooting.
You can purchaseMini Program Market or buy the app premium version.Home/Away Arming,.
There is no direct correlation between the completion of custom panels and the purchase of modules. Whether the project can be completed depends on the customer's acceptance. If the acceptance is OK, the acceptance form can be signed, and the PM can close the project.
Error code 1010 usually indicates that the Token has expired. Please ensure that the correct access_token is included in each request and check its validity. Specific steps to resolve the issue are as follows: 1. Confirm that the correct access_token is included in the request header. 2. Visit the Tuya Developer platform to ensure that the access_token obtained and used is valid. Refer toGet Tokento verify the validity period of the access_token. 3. Check whether the request meets the standard requirements of the Tuya API, refer toAPI Request Specificationsto ensure that the access_token is correctly included in the request header. If all the above steps have been confirmed correct but the issue still exists, please contact technical support for further troubleshooting.
Users need to use a custom-developed OEM app or SDK app to achieve device binding: 1. OEM App: Users should refer to the OAuth 2.0 authorization configuration to generate the H5 authorization link. The device needs to be unbound from the initial application and then rebound to the new custom application. 2. SDK App: Users should refer to the binding method of their own developed application to achieve device binding. Public version apps (such as Tuya App or SmartLife App) do not support users adding devices to cloud projects. If using a custom-developed application, users need to ensure the device is unbound from the original application.
The firmware name used by the door sensor can determine whether low power consumption is supported. T3 firmware generally supports low power consumption, but the specific situation still needs to be verified by the firmware name to see if it is a low power version.
If the socket's overcharge protection is automatically activated causing the device to be unusable, you can disable the overcharge protection feature in the app panel.
Zero-cross detection for metering cannot be directly disabled, but the requirement can be achieved through the following methods: 1. Locate the relevant zero-cross detection component for metering in the code. 2. Review and understand the code implementation of zero-cross detection for metering. 3. Separate the timing component and basic switch functionality from the existing demo to achieve the desired functionality. 4. If certain application layer components are not needed, you can choose to write alternative code to meet project requirements. 5. Implement your own components through code to adapt to specific usage scenarios and requirements.
The Wi-Fi pass-through module interfaces with the MCU main control via a serial port, supporting data from multiple charging guns. The panel interface can be customized through self-development or using the panel applet SDK to distinguish between gun 1 and gun 2.
Tuya provides pure Bluetooth modules, the BT series, which can be applied to charging piles. Create a product through the Tuya developer platform and select the BLE communication method. You can view the product creation steps and find the module specification to get more information.
To solve the issue of Xiao Zhi Butler not being able to precisely control the three-in-one temperature controller, you can follow these steps: 1. Check whether the device name is configured correctly; it should be "temperature controller," and ensure the device location is also set to "living room." 2. According to the switch configuration mentioned in the conversation, ensure "on" corresponds to true and "off" corresponds to false. If it does not match, modify it yourself. 3. Confirm whether the name can be modified; this is crucial. Since the names on the panel are all switches and cannot be modified, it is necessary to split the voice scheme to ensure accurate control. 4. The voice scheme split requires setting the names of the main scheme and the two split schemes (ventila_switch and heater_switch) to be different, so that precise control can be achieved through voice commands. 5. Modify the dp point names within the panel and ensure these names can be customized and are not duplicated. 6. After that, directly use voice commands to set the temperature or wind speed according to the new split scheme, such as: "Set the temperature/speed of to XX.".
Solving this issue involves the following steps: 1. Check the module's power supply and hardware connections, ensuring that pins such as TX, RX, EN, GPIO15 are configured correctly. 2. Monitor abnormal behavior or errors in circuit design during module operation. 3. Use testing tools like oscilloscopes to monitor any anomalies. 4. If abnormal behavior persists or a software bug is suspected, such as an integer overflow issue, try seeking a firmware update to resolve related functionality issues. 5. Provide the device ID and approximate time of failure to the technical support team for further log analysis. 6. Contact the product developer to obtain device logs for analysis, as the firmware is not maintained by Tuya, and specific issues may need to be resolved by the manufacturer. 7. If a satisfactory solution cannot be obtained from the manufacturer, it is recommended to contact the product seller for handling, but note that the product's firmware may not be maintained by Tuya. 8. Before purchasing the product, inquire whether there is a WWT or WWS certification label to ensure product quality and durability. For the current issue, contacting the seller may be the most effective way to handle it due to product quality problems.
To manually flash the Wi-Fi firmware with a specified product ID, you can use the Tuya burning tool or other specified methods. For more detailed steps, please refer to the link:https://developer.tuya.com/en/docs/iot/TYMZ?id=Kc3kd9vbl0ymm. If the firmware configuration is changed, it needs to be re-flashed to make the changes effective. If hardware configuration needs to be changed, you must regenerate the firmware, purchase a production certificate, and flash it to the module or create a new order for the module.
Regarding the firmware version deactivation issue of the WBR3 module, the new version of the firmware is backward compatible, and users can switch to the new version to place orders and use normally. It is recommended to upgrade a single device for testing, and after verifying there are no issues, proceed with bulk purchasing of modules. There are certain differences in firmware versions, which can be referred to in the accompanying product instructions.
To address the issue of slow module response in the design, consider the following solutions: 1. After detecting the mobile app pressing the switch, check whether the MCU immediately reports the DP data. If there is a delay in the MCU processing other tasks and not reporting data in time, it will lead to slow response. 2. Ensure the MCU's processing logic is clear, prioritizing the handling of button response events. 3. Conduct comprehensive performance testing to evaluate the response time of the entire system and optimize any bottlenecks found.
If you encounter insensitivity issues when using the APP to control the device switch, you can try the following solutions: 1. Check the device's online status: Confirm through the log whether the device is online normally and check if there is any data reporting. 2. Optimize the mobile network: Try switching the phone to a different network environment, control the device again, and see if the issue is resolved. 3. Change the device network: If the problem occurs frequently, configure the device to another network and observe whether the issue still exists. 4. Test the physical button switch: Use the device's physical button or remote control to conduct several experiments to see if the issue improves under these circumstances.
The T1-2S-NL module of the T1 series and the CB2Swifi module are pin2pin compatible. For software, it is recommended to conduct actual tests to confirm compatibility, as there may be differences in module firmware. Even if the protocol and pin positions are the same, specific issues still need to be checked in the software. When replacing, for example, replacing CB2S with other modules (such as CBU or T1), it is necessary to consider whether software adjustments are needed based on test results. During the testing process, if specific issues are encountered, you can communicate with the support team at any time for assistance.
The Android APK package downloaded via the QR code does not match the content, mainly due to incorrect application packaging settings. The specific steps to resolve this are as follows: 1. Confirm that the download link corresponding to the QR code points to the correct version of the APK. 2. If the domestic package fails to be packaged, check whether the package contains disallowed components, such as Firebase. 3. After removing the components that do not meet the requirements, repackage the domestic version APK. 4. Ensure that the QR codes for different regions point to the corresponding versions: the domestic QR code corresponds to the domestic package, and the international QR code corresponds to the international package. 5. Ensure the customized application version is correct, and communicate with relevant personnel if necessary to resolve packaging failure issues. 6. You may need to refresh the page and rescan the QR code to download to ensure the downloaded package is correct. 7. If the problem persists, check whether a historical version of the package was used for download, and ensure the QR code points to the latest correct version.
According to the device log inspection results, the device offline issue is due to keepalive_timeout, which is usually caused by network or power supply problems. The solutions are as follows: 1. Change the device's network settings to ensure a stable connection. 2. Replace the device's power supply, as there may be an issue with the current power source. 3. After completing the above replacements, observe to confirm whether the issue is resolved.
Using the PHY6222 chip for a solution with TFT screen display is feasible. PHY6222 supports two SPI interfaces, which can be used to connect the TFT screen and external FLASH memory. Ensure the SPI interface is configured correctly, including clock polarity and phase settings. It is recommended that embedded engineers write simple code for testing to verify the feasibility of sharing the SPI interface.
To resolve the issue of UUID not connecting to the server, please check the following points: 1. Confirm whether the device enters AP mode during the QR code network configuration and check the interface call status. 2. Confirm whether the device has been assigned the correct IP address, then continue debugging the relevant network configuration interface. If the problem is caused by a function being stuck, please resolve the issue with that function and then retry the connection.
Choosing South Korea's Wi-Fi channel code during domestic testing may affect RF power, but pairing can still be done. It is advisable to choose channel codes that comply with domestic standards to avoid unnecessary testing issues. Understanding the default channel ranges of various countries can better configure device testing parameters.
By attaching the SN code to the drive product, rapid device traceability can be achieved. Adding to the App to view the reported version can generate the device ID for pushing. To reduce inventory and meet the needs of different end customers, the SN code can be exported from our platform's order list without scanning each one individually.
Tuya does not directly provide power modules. Tuya provides power design guidelines, but specific designs need to be adjusted according to the specific requirements of the module. During the design process, attention should be paid to circuit diagram modifications, selection of serial communication interfaces, selection of resistor parameters, and how to connect the MCU. If there are any issues, you can refer to relevant guidelines for modifications and optimization.
To control online Tuya devices via FastAPI and obtain the device's online status, please follow these steps: 1. Visit the Tuya developer website to obtain relevant API interface documentation: Send Attributes, Query Single Device Details 2. Ensure the device is networked to Tuya Smart or Smart Life App and synchronized to the cloud project, refer to the specific operation:Add Device to Cloud Project 3. Use Postman and server-side SDK to improve API integration efficiency: Set Up Postman Environment and Call API, Server-side SDK 4. Confirm project API permissions, obtain access token, and correctly construct the signature:Obtain Token, Cloud Authorization Signature Mechanism 5. If a "token invalid" error occurs, ensure the device is bound to the account asset, refer to the documentation:Link Devices 6. For a complete operation tutorial, please refer to:Tuya Cloud Development Integration Document, ensure the device is correctly added and bound in the Tuya App or Smart Life App. If a transfer is needed, you can consult through detailed documents and support links.
App SDK version 6.7.0 already supports Google's 16K adaptation policy requirements for Android 15. If your App SDK version is below 6.7.0, please upgrade the App SDK version.
Hello, please first check your app branch version. If it is below 7.1.0, please update to 7.1.0 or above, and then inform us to help you hide it.
Not supported to enlarge, hardware debugged well.
LAN communication is not supported in low power consumption mode, only supported in standard power consumption mode. Reconfigure the network after switching power consumption modes for testing.
Feeding schedule, cycle timing, random timing, etc., are all function point timings. After setting the timing, the device needs to report the timing data to the panel for the timing task to be displayed. The device needs to execute the timing locally, and after execution, the device needs to report the timing data according to the protocol to modify the current timing status.
The device may fail to send messages when memory consumption is too high. By debugging the return value, the radar processing code can be checked to ensure the device remains stable when unattended. For display logic-related issues, code optimization can be used to resolve them. Apart from memory issues, power cycling can be used as a temporary solution to restore the device's normal functionality.
It is normal for the module to display online after the gateway is powered off. After the gateway is powered off, the app generally shows online within 3 minutes, and after 3 minutes, it will show offline only after the reconnection fails.
Wi-Fi modules usually need to connect to a router to access the network. The module achieves connection by configuring the router's SSID and password.
Currently, the low-power Wi-Fi module mainly promoted by Tuya is the T3 series. The T3-U module can be used as a substitute, and the T3-3S module has some differences in form.
General docking firmware is divided into Zigbee ordinary and 3.0 versions, Zigbee 3.0 can access HUE. Please check whether the firmware is ordinary firmware or Zigbee 3.0 firmware, and ensure that the device is in network configuration mode; also check whether the gateway supports Zigbee 3.0.
Tuya devices do not support control through the Homey gateway because Homey is not an officially supported platform by Tuya. Tuya devices currently support control through MQTT and HTTP protocols.
After network configuration, check the MAC address to print the QR code. The configured network will close the production test channel after a long period of inactivity, and the specific time varies depending on the device configuration.
When using the WBR3 module, the anti-misoperation mode cannot be unbound through commands, so the regular mode must be used to enter the network configuration state. After the first power-on, the module may need to send a reset command to ensure the module correctly enters the network configuration state. The reset command should be sent after the module initialization is complete, otherwise, it may cause the module to fail to enter the network configuration state. Ensure the power supply is stable, as power fluctuations can cause the module to restart and extend the initialization time. If the device has successfully connected to the APP and you want to bind it to another person, after the device successfully connects to the APP, sending a reset command will cause the module to restart and enter the network configuration state, allowing new binding.
If your device is using a SIM card provided by Tuya, but the network cannot connect, please confirm whether the card model is correct. A common cause of network issues is purchasing the wrong card model, possibly selecting a card dedicated to NB-IOT protocol devices, while actually needing a card for 4G devices. Please replace it with a SIM card suitable for 4G devices to ensure normal connectivity.
Flickering may occur when switching images, which is caused by multiple factors. To reduce or solve the flickering issue, you can try the following methods: 1. Compress images: Prioritize compressing resources within the package, ensuring each image is preferably less than 100KB. 2. Choose the appropriate format: Use JPG for photos, PNG for lines/transparent/Logo, and SVG for small icons. 3. Use CDN / Cloud: Place larger images on CDN to reduce package size and network loading time. Ray mini program cloud steps: Create a cdn directory at the project root; configure "publicRoot" in project.tuya.json; using IDE's CDN upload will generate cdnImage.json; use utils/getCdnImgUrl to encapsulate image links. 4. Preload and progressive display: Preload the next image to avoid waiting for network loading when switching. 5. Lazy loading and merging images: Load only visible images on the first screen, and load when scrolling into the visible area to reduce blocking. 6. Use sprite images: For a large number of small images, use CSS sprite to reduce request concurrency. If flickering issues persist, it is recommended to display all images first, then use the hidden attribute to hide images that do not need to be displayed. If preloading is unsuccessful, try using sprite images to ensure effective preloading.
Device network configuration supports b/g/n network modes. It is recommended to configure the router to these modes, no configuration is required on the device side.
The RED DA Cybersecurity (EN18031) report is a controlled release, and you can place an order to obtain the report through the link below. https://www.tuya.com/vas/commodity/RED_CYBERSECURITY Open the link and select the service:Provide module certificate; click to purchase immediately to place a 0 yuan order, the developer account needs to have company information, we need internal remarks to release. Note: The module data in the report cannot be referenced by third-party testing agencies without authorization, otherwise it will lead to infringement. If authorization for module data is needed, you can select the service "Provide module data and authorization letter" in the link. You can also contact your business manager for further communication.
Please refer to the Tuya IoT Platform documentation for detailed guidance on this topic.
To clear device-related data when unbinding the device, appropriate control commands can be sent to the device so that when the device receives the unbinding command, it simultaneously clears the recorded data. The steps are as follows: 1. The device receives the unbinding or reset command. 2. The device initiates lwm2m or onenet connection. 3. Clear recorded data on the device. 4. Reset the device's ICCID information. 5. Reset the heartbeat interval and recorded wake-up interval to default values (e.g., 8 hours). After completing the above steps, the device data will be cleared, ensuring data security after the device is unbound.
During the secondary development of the T1 module SOC, you may encounter errors due to missing header files during compilation. Here are the steps to resolve the issue: 1. Right-click on the project and select config project to disable the OEM macro. 2. If the compilation still reports errors, you may need to block specific header files. 3. The OEM macro is used to generate OEM firmware. If the product development is completed and the OEM firmware is used by multiple customers, there is no need to change the PID or recompile a new version. Reference link: https://www.tuyaos.com/viewtopic.php?p=5945&hilit=oem#p5945 4. Change the PID to key and enable the ENABLE_TY_FIRMWARE_OEM macro, then call tuya_iot_oem_set(TRUE). 5. Use production credentials during manufacturing, without the authorization code list. The product development package may not support OEM, and deleting the example may result in successful compilation. 6. Ensure to clean the project and recompile. 7. If there are still issues, you can try disabling the OEM macro and deleting the related demo. It is recommended to reopen and compile once before blocking for compilation.
In the product multilingual configuration, you can remove the prefix to display the normal status. Please log in to your IoT platform account, then find the product multilingual configuration option in the product development steps, and adjust the display prefix settings to achieve this. Refer to:How to handle the appearance of dp_XXX, dp_identifier, or display garbled characters, English characters, etc., on the panel control interface?Go to configuration.
Currently, the Huawei pure HarmonyOS (HarmonyOS NEXT) system and device panels are still iterating on related supporting capabilities. Therefore, unsupported device panels will load the basic panel, which is normal. HarmonyOS system coverage of the public version device panels is underway. At present, some public version mini-program panels have achieved HarmonyOS system compatibility, and full panel support is being gradually implemented. Please wait patiently. Solutions for other panel solutions are as follows: Customized panels: Contact the project manager to evaluate the adaptation plan. Studio panels: Not supported, currently not planned. It is recommended to switch to a public version panel or develop a custom panel. Custom Development Panel: 1. Panel Mini Program: Requires evaluation by the mini program team. Please provide the following information: List of protocols involved in the mini program (required): e.g., Wi-Fi, Zigbee, Mesh Mini program's PID (required): The developer account to which the mini program belongs (required): List of APIs used by the mini program (required, APIs used in ty or imported from @ray-js/ray): e.g., ty.device.xxx, openZigbeeLocalGroup 2. RN SDK Solution: Incompatible; needs to be replaced with the panel mini program solution.
Dear user, we are sorry for your inconvenience. If you do so: Open the App, click the device icon to enter the device control panel (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be controlled). Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of the corresponding third-party control to view the operation manual of the third-party control. One third-party smart speakeraccount can only be bound to one App account, an error will be reported if the binding is repeated. Note Users logging in via third-party/Quick login need to complete account settings first before binding a smart speaker: Go to Me → Settings → Account and Security, bind a mobile phone number or email address and set an initial password (this login method has no default password; please tap Change Login Password to set it); Use the bound mobile phone number or email address to log in to the App when binding the speaker. If devices fail to sync, this login method may not be supported for the time being; please try registering a new account. The following are the connection methods of several third-party smart speakers supported by the App: Alexa Google Assistant IFTTT Tecen Xiaowei DuerOS Dingdong Thank you for your understanding and support.
To review user feedback and execute unbinding operations on the developer platform, follow these steps: I. If you are using the old version of the user feedback system and the device's PID is under your account, You can receive the user's unbinding request on the user feedback page and handle it by following these steps. If the PID is not under your account, you need to contact the owner of the PID for the unbinding operation. Go to the developer platform and enter the Operation - User Feedback page. Select the data center where the user submitted the unbinding feedback. View the list of user feedback. Find the feedback information from the user requesting unbinding. Click on the feedback information to display an information box on the right side of the screen. Click Device Information - Device UUID. The UUID should be a clickable blue link. Click the UUID to enter the device management page. On the device management page, find the device that the user requested to unbind. Click Details on the right side to open the device details page. At the bottom of the device details page, there is a Unbind device button to unbind the device. Click the button to unbind the device. II. If you are using the new version of the user feedback system and you have the authority to handle user feedback,You can directly unbind the device on the user feedback details page by following these steps: Go to the developer platform and enter the Operation - User Feedback page. Select the data center where the user submitted the unbinding feedback. On the list page, find the device unbinding feedback and click the Details button on the right side to enter the details page. On the top right corner of the details page, click the Unbind Device button to complete the device unbinding. Note:When the device user fails to bind the device, the App will automatically redirect to the binding failure page. According to the page guide, the user must submit an unbinding feedback to obtain the device ID. (I.
It requires actual measurement and pulse signal capture before configuring the firmware.
Support Beacon Remote Control.
The American version pins are different, cannot pin to pin.
Follow the phone, the phone needs to switch to 24-hour format.
Except for the P28 pin, other ADC pins have internal resistance. The P28 pin has no internal resistance, it is recommended to use the P28 pin. The V3.12.25 version SDK has an interface to switch off the internal resistance, and after switching off, other ADC pins have the same range as the P28 pin.
Need to add dp37 and dp38 function points, after adding them, support local timing, but it is recommended to add an RTC chip.
Serial port transparent transmission firmware, the latest version can already confirm the channel range that can work normally based on device positioning.
Check if the firmware configuration is set to wide voltage.
No, there is no corresponding configuration item in the segmented dimming firmware configuration, network configuration is required to select the power-on state.
Adding DP points for motion alarm areas in PID can be achieved. The relevant DP points include the alarm area switch and the alarm area. This function relies on panel development, so it needs to be implemented specifically using the SDK panel.
To report door opening records, you need to implement it yourself. Normally, reporting is done using the tuya_ble_dp_data_send or tuya_ble_dp_data_with_time_send interface. Please ensure that the reported data includes the correct timestamp and hardware ID to successfully update the platform logs.
Door lock firmware key5943jddfsyeu3, only supports Bluetooth auxiliary network configuration, does not support Bluetooth channel communication DP.
Incorrect wake-up pin configuration, refer to the pin selection in the image to wake up the MCU and the module. Choosing other pins will not wake them up.
The old version of the CI firmware would issue this command to the MCU, but the latest T series firmware module will not issue it. In practice, infrared production testing success should be determined by whether the infrared-controlled device is controlled. Refer to the infrared production testing process protocol:https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-wifi-ir?id=Kd2fwyilf0v29.
The module side level is 3.3V, the magic color chip requires a 5V level, a logic level conversion chip needs to be added. Additionally, interference in the routing will lead to adjustments in layout routing.
MCU selects an IO port to control whether the speaker is enabled.
Configured with hardware dual control, the corresponding dual control circuit is required to support the switch, otherwise the switch cannot be controlled unless the hardware dual control is canceled. For temporary testing, a level signal can be given to the dual control detection pin for testing.
The product name, product model, and manufacturer name configuration are too long, exceeding 1024 bytes.
Authorization parameters for production testing cannot use test parameters; formal parameters must be used for production testing. Please ensure the data output of the production test tool is correct. For specific parameters, please refer to the development documentation of the production test SDK.
To ensure the proper functioning of APP rule linkage in panel settings, it is recommended to move the rule logic from the panel side to the device side. The specific steps are as follows: 1. Set up logic on the device side so that when the device receives a command, it can automatically turn off other function points, thereby avoiding logical conflicts caused by device reporting. 2. Control the reporting interval and consider combining multiple function points for reporting to optimize command usage. This combined reporting will count as one command. 3. The device's heartbeat or proactive reporting of product status information will not occupy the user's limit of 3500 commands; only dp data will be counted within this limit.
After the module is powered on, you can use the Tuya serial port debugging assistant to simulate MCU communication to verify the information.
If the click event cannot be triggered or debugging cannot be performed in Tuya MiniApp IDE, you can try the following methods: 1. Check the security settings of the IDE to ensure there are no obstructions. 2. Check the logs of the developer tools to troubleshoot potential issues. 3. Try creating a new project for testing to ensure the issue is not project-specific. 4. Use a real device for debugging, rather than relying solely on virtual devices. 5. Check and adjust the resolution of the monitor, as certain resolutions may affect the performance of the IDE.
The flickering of the light may be due to the load of the light being too small. It is recommended that the load power used should not be less than 3W, and a resistor can be added to the lamp circuit to solve the flickering problem. If the problem persists, consider switching the switch to another model of lamp circuit or directly replacing the lamp. In addition, it is recommended to contact the supplier to obtain a switch capacitor to solve the problem, which may help to some extent in solving the flickering issue.
The device indicator light stops flashing, indicating that the device is disconnected from the router. At this time, it cannot be properly networked. The device needs to re-enter the slow flashing or fast flashing networking mode to be properly networked.
Check the following items to resolve issues with connecting to Wi-Fi: 1. Confirm that the module enters network configuration mode and the parameter of `mcu_set_wifi_mode()` is correct. 2. Ensure the Wi-Fi network is on the 2.4G band, as 5G Wi-Fi is not supported. 3. Verify that the entered Wi-Fi password is correct. 4. Ensure the network status is good to avoid configuration failure due to poor network conditions. 5. If the module keeps restarting, check the supply voltage and current to ensure they meet the requirements. When using the SDK, ensure the MCU correctly responds to the data sent by the module. 1. You can use `Uart_PutChar` to send data. 2. Adjust the priority of the serial port interrupt to ensure normal data transmission and reception. If stuck in the state of receiving data for a long time: 1. Confirm the MCU settings are correct and no key configurations are missed. 2. Download and test the official demo for troubleshooting. Following these steps can effectively troubleshoot and achieve normal connection and operation of the Tuya module. In terms of configuration, ensure the SDK is correctly ported and adapted to the device characteristics.
Due to pairing with the phone, this issue does not exist without pairing. It is recommended not to connect to the app before production testing, and connect to the app after production testing.
Support, but it depends on the product plan.
The network status of the WBR3 module is automatically sent to the MCU, and the MCU can obtain the current device's network status by sending the 0x2B command. The heartbeat packet will be sent to the MCU again after reporting the data. For details, please refer to theprotocol document.
When using the debugging assistant for wiring, if the module does not respond and only displays one line of data, please confirm whether the module wiring is correct. The serial port function of the module is usually fixed, it is recommended to change the wiring to serial port 1 instead of serial port 0 according to the module specification for connection. During firmware upgrade, serial port 0 is used by default, and upgrade data must be issued to the MCU according to the protocol. The MCU is responsible for receiving and storing data to complete the firmware refresh. For detailed information about the upgrade protocol, please refer to the relevant developer documentation.
Use the MCU SDK provided by Tuya to implement Wi-Fi configuration for Tuya modules. 1. Call the `mcu_reset_wifi()` function to reset the Wi-Fi module. 2. Call the `mcu_set_wifi_mode()` function to select a specific configuration mode (SMART or AP). 3. In the `while(1)` loop, call the `mcu_get_wifi_work_state()` function to set the corresponding indicator light state based on the returned Wi-Fi status.
When adding new voice features, there is an issue of voice capability not matching the product DP. This can be resolved by editing the power switch of the split scheme. Ensure that the voice capability in the system matches the DP points used by the product to avoid functional anomalies.
If after using the authorization code, the plugin page does not display the video pet viewing, it is recommended to troubleshoot and handle it as follows: Clear the app cache and try again, usually this can solve the issue of video pet viewing not displaying. Ensure the network connection is normal and the device is properly authorized. Additionally, it is recommended to use the latest version of the app to avoid compatibility issues. If the problem is still not resolved, you can contact technical support for further assistance.
AK801 firmware has been discontinued, and there is no replacement firmware. It is recommended to use MCU general docking development products to solve the problem.
When developing the MCU SDK for Zigbee, the automatically generated protocol.C file may contain undefined mcu_recv_xx_cb functions. These functions are typically used for specific business scenarios. During the compilation process, the undefined functions can be commented out and defined later when needed to develop related functionalities. Adapting serial communication with the module is the primary step, and other functionalities can be developed according to the serial protocol specifications. During development, you can refer to the serial protocol documentation provided by Tuya:https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-zigbee-uart-protocol?id=Kdg17v4544p37. If you have any questions, you can contact the technical support team.
The payment account for the module order should be Hangzhou Tuya Information Technology Co., Ltd. If the account name appears as other information, please verify the contract on the order processing platform and perform the relevant stamping and return operations to ensure the payment information is accurate.
The testing method for Wi-Fi module production testing involves testing according to the module's functionality, and you can refer to the documentWi-Fi Product Production Testingfor detailed operations. Production testing scenarios are typically used for RF and serial port testing related to the module, and can be used to evaluate whether the module is working properly. During production testing, it may be necessary to cooperate with other devices to display the test results.
Production will not proceed without payment, and production planning may change. Therefore, it is recommended to make timely payment after placing an order to ensure the smooth progress of the production process.
To complete the Gobe binding hotspot and module order, set the hotspot support in the firmware properties. Ensure that the device's Wi-Fi AP mode is active, and strictly set the AP name and IP segment according to the configuration file.
One of the factors affecting the success rate of device stress testing is the DP stress test interval time. The baseline time for serial port reception is 300 milliseconds. If multiple DPs are synchronized in a short period, the stress test interval should be set to more than 500 milliseconds. By adjusting the DP stress test interval time, the success rate of device stress testing can be improved. Users are advised to try resetting the stress test interval time according to the above suggestions and conduct tests.
To clear the device panel data and restore it to its initial state (data reset / restore default), you can achieve this by restoring the device to factory settings. After the operation is completed, the panel data reported to the cloud by the device will be synchronously cleared, and the panel data can be restored to its initial state. Additional notes: This operation only clears historical / stored data on the cloud and panel, and will not change the device's hardware configuration or factory settings; To reuse the device, you need to add it again in the app and complete the network configuration.
To burn firmware for an empty delivery module, you need to follow these steps: 1. Download the Tuya platform "Production Solutions" software: - Log in to the Tuya Smart Production Management System. - In the left navigation bar, select "Knowledge Base Management Software Download". - Search for and download "Production Solutions". 2. Firmware download: - In the third step of product development on the Tuya Developer Platform, "Hardware Development", click "Add Custom Firmware" to upload the compiled firmware. - Fill in the firmware parameters according to the interface prompts and confirm. - In the "Generated Firmware" area, select "Upload Production Firmware". 3. Compile firmware: - Please refer to the specific ZT series module burning tutorial and obtain detailed guidance on compiling firmware through the WeChat link. The above steps can help you complete the firmware burning process for the empty module.
When integrating the product, the sleep DP point of the standard function and the sleep DP point of the custom function may use the same identifier, causing conflicts. To avoid this conflict, users can add other characters before and after the sleep DP point identifier in the custom function. The specific steps are as follows: Open the custom function settings page of the product. Find the sleep DP point identifier. Modify the identifier by adding some other characters before and after it. Save the settings and confirm the modification. This can effectively distinguish the identifiers between standard functions and custom functions, avoiding conflicts.
The security baseline of the firmware version may vary due to version updates. You can view the update details of the firmware version on the platform to determine if there are any differences in the security baseline.
To confirm whether the purchased PID can be used and ensure the modules are completely consistent, you can refer to the following steps: 1. Confirm that the PID has been switched to the correct firmware version, for example, switch to version 9.5 and complete the necessary tests. 2. Check whether the selection of different PID modules is the same, ensuring their functions and configurations are consistent. This ensures that the PID and modules you purchased can meet the expected usage standards in terms of functionality and performance.
To ensure you receive password unlock notifications from the device lock, please follow these steps to check and set: Firstturn on the notification switch, please confirm in the App or system settings that thealarm message push switch is turned on. Configure push trigger conditionsIf you need to set push for a specific device, add its uniquedevice identification number (PID)as a trigger condition. Modifying the notification content of this device will not affect other devices. Modify notification contentIf you need to adjust the push text, you mustcreate a new alarm messageto achieve this. Note: If placeholders like{variable}are used in the original message, directly modifying them may causehistorical push records to display abnormally. If you encounter problems during operation or need to confirm the specific location of a step, you can tell me at any time.
Follow these steps to resolve the issue of Tyda Cloud burning authorization tools not opening: 1. Right-click to open the folder location of the production solution software and delete that folder. 2. Restart the tool and try reloading. If it still doesn't open, uninstall the production solution. 3. Turn off the firewall and antivirus software, download and install it again to another drive (such as E drive or F drive) to see if the issue is resolved.
If your push service experiences time discrepancies or untimely push issues, you can try the following solutions: 1. Confirm whether the push settings are correct and check if the push service is enabled. 2. Check the network conditions, especially when crossing countries or regions, as network latency may affect push timing. 3. Increase real-time monitoring of the push service to confirm whether there is push congestion, and provide feedback to customer service to confirm if there is server pressure. 4. Check the push cycle settings: for example, whether an alarm will be reported immediately after 23 hours. 5. Not receiving a push for 24 hours may indicate a service anomaly. You can contact technical support to confirm if there is a bug and get help. These steps can help you better resolve push time discrepancy issues. If you have further technical problems, please contact the corresponding technical support.
Check whether the device has reported excessively by viewing the device reporting status page. Each device is allowed to report 3500 messages per day, and exceeding this will incur charges. The number of messages reported is reset monthly. If the device is offline, check the device side or network reasons. Prohibiting the device from going online can only be achieved by powering off the device; there is no separate function to disable device reporting. Restoring the device order function can be operated through the platform's function, see the platform instructions for specific operations.
When the device does not receive control commands from the cloud at the scheduled time, you can troubleshoot by following these steps: 1. Ensure the device remains connected to the network at the scheduled time, as a network disconnection will prevent the device from receiving control commands. 2. Check network stability, as network errors may cause message reception delays. 3. Check if the device and server are located in different regions, which may lead to message reception delays. 4. Ensure the mobile phone is always connected to the server to receive push messages. 5. Most timing settings are performed on the device rather than cloud-based timing. Therefore, confirm the device ID and the set timing to verify if it is cloud-based timing. 6. For issues using local timing methods: ensure you know the protocol to send to the cloud to request downloading the schedule. Receiving "Protocol 13" indicates the cloud has notified the device of an updated schedule, but the device needs to take additional steps to retrieve the new schedule. 7. It is recommended to send DP data to the MCU when the set time arrives, and then the MCU performs tasks for testing. A timed task can be set for five minutes later for testing.
CBU-P uses the BK7231N P version chip, and the rest of the module is completely consistent with the original module. The external model and certification model are still CBU, and the distinction of CBU-P is mainly used for internal production control. If the product uses the CBU module, just select CBU in the production data.
When creating a Matter module for public version testing, it prompts that the advanced capability "Attribute Configuration" requires a Certification Declaration (CD). You can refer to the following document link to configure and complete the module sampling application:https://developer.tuya.com/en/docs/iot-device-dev/matterconfigu?id=Kd315la5yc2zk.
Yes, when activation detects inconsistency between local data and cloud data, it will trigger GW_RESET_DATA_FACTORY. The SDK will automatically replace the cloud data to the local, and the application needs to perform local data cleaning. If there is data that needs to be cleaned, clean it; if there is no data that needs to be cleaned, no reset processing is required.
To connect Thread matter products with Google Home, you need to use a Google speaker as a gateway. Please ensure the Google speaker is properly set up and connected to your home network. In the Google Home app, use the speaker to scan QR codes and perform network configuration operations to connect and control Thread matter devices.
The new firmware version supports the Wi-Fi Scan function, enabling indoor positioning through Wi-Fi scanning technology. When using it for the first time, there is no need to go outdoors; just ensure that the Wi-Fi signal is strong enough in your environment to assist with positioning.
The new version of the firmware supports the Wi-Fi Scan function by default.
In the case of PID firmware discontinuation, if the certified prototype needs to be reconfigured with the Matter test certificate, it is recommended to use its own PID for testing. The firmware version and certificate should be completed before using the official version. The PID used for test samples should be a general PID, and the specific choice should be based on project requirements.
Generally speaking, Matter gateways need to undergo Thread certification to ensure their connectivity and compatibility. Matter protocol certification involves multiple wireless connection protocol versions, including the Thread Group certification program. This helps ensure the product's competitiveness in the market and provides consumers with confidence that the product can reliably operate in a Thread network.
To burn firmware for the THP23-X-D development board, please ensure that the necessary software tools are ready. You can use suitable burning software to connect the development board and perform firmware writing. Depending on the specific protocol type, additional hardware tools and burning tools may be required. Please refer to the relevant documentation of the development board to ensure all steps are executed correctly to avoid operational anomalies.
The QR code for the cat.1 module needs to be printed by yourself and attached to the product casing. In some cases, the network configuration label code can be created through the Tuya production solution. For more detailed operation steps, please refer to the Tuya Developer Platform.
Cat.1 module can export QR code data in batches through the host computer. It is recommended to check the method of obtaining QR codes during the production phase in the documentation. For detailed procedures, refer to the QR code production process. Note: There is no need to connect the computer serial port one by one to copy data.
The Matter module requires self-programming and ensuring the use of the latest version of the Tuya debugging assistant. After powering on, you can use a regular serial port assistant for debugging to ensure data reception. If the Tuya debugging assistant does not receive data, try updating the assistant version and checking the connection settings. It is best to always use the latest version to avoid compatibility issues.
To exit low power mode, the MCU needs to perform two steps: 1. Pull the wake-up signal to wake up the Bluetooth module. 2. Send the E5 command again to exit low power mode.
After the first network configuration, the device should automatically synchronize the cloud time to the MCU without actively obtaining the real-time. 1. Confirm that the module network status is "connected", then send the command to obtain the time. 2. Use the debugging assistant to simulate the MCU to test the command acquisition after connection, and refer to the relevant protocol attachment to ensure the operation is correct. 3. Provide the device ID for further confirmation. 4. If the issue is not resolved, it is recommended to record a test video for problem analysis. 5. In the debugging assistant, find and use the button to obtain the time for functional testing.
Hello, After the OEM App expires,configured features can still be used, but no modifications, additions, or updates to any features can be made. No renewal: Features are read-only, maintaining the status quo. Basic update renewal only: Only supports App updates and independent domain names. Basic version renewal: Retains core features, lacks advanced features (such as tablet/Siri adaptation, ad slots, etc.). Advanced version renewal: Enjoys full feature permissions.
Some Bluetooth single-point devices cannot connect directly to the IDE and may not appear in the IDE device list; Zigbee, sigMesh, beacon, etc., if connected to a gateway, generally show online; If directly connected to a mobile phone, it may appear offline in the IDE.
Call the removeMember interface to leave the family. First, query the corresponding memberId from queryMemberList and then pass in the parameter to leave the family. https://developer.tuya.com/en/docs/app-development/member-information-management?id=Kaiy91tma26nh#title-1-%E5%88%A0%E9%99%A4%E5%AE%B6%E5%BA%AD%E6%88%90%E5%91%98.
Hello, there are currently two solutions: 1. Still use the current mesh scanning and query interface, convert the mac field parameter from AA:BB:CC to aabbcc format 2. Call the single-point Bluetooth scanning and query interface, just pass SIG_MESH as a parameter during scanning, and you can also scan mesh devices.
Hello, if the App is opened in a disconnected state, it will not be able to retrieve any information. If the network is disconnected during the use of the App, you can call the getHomeLocalCache() interface to obtain cached data, provided that the getHomeDetail() interface has been called at least once. The cached data includes the complete home information HomeBean, such as device information: DeviceBean deviceBean = ThingHomeSdk.getDataInstance().getDeviceBean(devId);.
Call the interfaceremoveDevice to remove the device. After removal, the device will enter the pending network configuration state, and you can reconfigure the network later. https://developer.tuya.com/en/docs/app-development/devicemanage?id=Ka6ki8r2rfiuu#title-9-%E7%A7%BB%E9%99%A4%E8%AE%BE%E5%A4%87.
You can integrate the panel button sound function according to the document to control turning it on and off. https://developer.tuya.com/en/docs/app-development/devicecontrol?id=Ka8qhzk2htjby#title-11-%E8%AE%BE%E5%A4%87%E9%9D%A2%E6%9D%BF%E6%8C%89%E9%94%AE%E9%9F%B3%E6%8E%A7%E5%88%B6.
During batch testing, testing is usually conducted by specifying the router's SSID, and then the device performs the prescribed actions to check hardware and aging. This testing method can effectively ensure the quality and normal operation of the device in a mass production environment.
When the device is activated abroad, it will automatically obtain the local time without being affected by the time difference. If the phone's time zone changes, it is recommended to reconfigure the device network to obtain the time again to confirm whether the correct local time can be obtained. It should be noted that the Bluetooth and Wi-Fi & Bluetooth dual-mode protocols may not be the same protocol, and the correct protocol configuration must be ensured.
WBR3 can be connected using AP mode without Bluetooth. AP mode is a basic network configuration method that requires establishing communication between the phone and the device and correctly entering Wi-Fi information for configuration. For specific configuration procedures, please refer to the relevant operation documents for guidance.
The Tuya Wi-Fi module does not provide the functionality to directly close the network connection through serial port commands. Therefore, this requirement cannot be achieved with existing commands. You can reset the Wi-Fi module to disconnect the network connection; although this method is not through serial port commands, it can meet the need to disconnect the network connection. We apologize for any inconvenience this may cause.
To optimize the connection time of the WBR3 Wi-Fi module, the frequency of command sending can be adjusted. Avoid actively sending commands to obtain the module's MAC address when the module has not successfully connected to the network. Wait until the module successfully connects to the network before performing necessary configurations to reduce the issue of needing to test for a long time before connecting.
The temperature obtained after the device is networked is related to the geographical location (i.e., latitude and longitude) of the phone when the device is networked. If the device's latitude and longitude are not obtained, the geographical location is resolved through the IP address. If the temperature displayed by the device does not match expectations, you can try the following steps: - Ensure that the location permission is enabled on the phone before networking. - Confirm that the IP address assigned by the router is consistent with the area where the device is located. - Turn off the VPN connection and use the local network to retest the networking to ensure the device receives the correct geographical location information. - Use an account from the China region for networking tests. If there is a persistent temperature difference, it may be related to the refresh time of the weather data obtained by the device. The Tuya cloud and external weather data sources have their own refresh cycles, which can lead to differences in real-time weather data obtained at different times. If the device is affected by external networks (such as WiFi using external networks), resulting in different weather data sources, it is recommended to restrict the IP in the network router settings to ensure the device receives weather data from the correct region.
For the layout design of the module, please refer to the following materials: Official website materials:https://developer.tuya.com/en/docs/iot/cbu-module?id=Ka8uv3u1q1xxc Reference design guide on the developer forum https://www.tuyaos.com/viewtopic.php?t=33.
For alternative modules to discontinued ones, it is recommended to check the modules recommended by the platform. Specific alternative choices need to be determined based on the model and PID of the discontinued module. Common Wi-Fi modules include the WBR series, CB series, T1, T3, T5 series, among which the T3 and T5 series support Wi-Fi 6 communication standards. Currently, the dual-band Wi-Fi module series also includes models from the WR11 series.
Zigbee weather data is sent by the gateway to the sub-devices. The weather data is based on the activation area of the gateway. For example, if the area in the app home is set to Beijing when the gateway is activated, the command sent by the sub-device will retrieve the weather for Beijing.
Use the 0xE6 command or the 0xA7 command to verify the password. After the module returns a successful unlock, use the 0xE0 record type to report DP14 unlock record. Refer to the protocol:https://developer.tuya.com/en/docs/iot/ble-door-lock-mcu-development-overview?id=K95l67wf9xopf#title-37-%E5%8A%A8%E6%80%81%E5%AF%86%E7%A0%81%EF%BC%88CMD-0xE6%EF%BC%89.
T3 does not support burning UA firmware, the burning address is0x00011000.
Python 3.8 version needs to be installed, because it points to the system-installed Python, a symbolic link needs to be created. You can use the command, sudo ln -sf /usr/bin/python3.8 /usr/bin/python.
Please pay attention to the level of module RX. If the level entering module RX is too high, it will affect Bluetooth broadcasting.
The online version is the released available version, and the review version is the version that is under approval and has not yet been released.
Because the applet is cached in memory by the system, you can disable caching by setting disableCache: true in global.config.ts.
Firmware does not need to be obtained separately, the burning process downloads module information from the cloud through the cloud module upper computer. The specific steps are as follows: 1. Use the authorization code for burning, note that one authorization code can only be used for burning one module. 2. Read and refer to the relevant documentation for detailed information on the burning process: https://support.tuya.com/en/help/_detail/Kdvkkr15m4f9v 3. If there are changes to the function definitions on the cloud platform, for no-development products, you must clear the APP cache and reconfigure the network after changing the function points, and wait about 15 minutes before it can be used normally.
Hello, different business sides have different requirements: Device side: String type DP length is maximum 255 bytes; except for Espressif modules, raw type DP length is maximum 1024 bytes. Cloud side: String type DP length is maximum 255 bytes; RAW type, the cloud's default open channel can support over 1K. Tuya Developer Platform: DP length is recommended not to exceed 255 bytes. In summary, because the business logic of different product panels may be inconsistent, it is recommended that the length of a single DP data point not exceed 255 bytes. Exceeding 255 bytes may cause unpredictable problems, and feasibility and stability testing should be conducted independently. For the need to report extremely long data, it is recommended to develop your own panel or customize a panel to report data from the same DP point in batches and perform splicing processing on the panel side.
Devicees with segmented dimming enabled allow you to adjust the color temperature, color, and brightness of a light by switching it on and off using a wall switch. Segmented dimming works by pre-setting several different states (white light brightness and color temperature, colored light brightness, chroma, and saturation) and saving them locally on the device. When the device is continuously powered on and off for a set period, the state smoothly switches between these preset states each time power is switched on, thus achieving dimming and color adjustment by switching the power on and off. As shown in the image below, if five states are preset: cool light, warm light, red light, green light, and blue light, the following dimming function can be achieved.
It indicates the remaining time that the remote door opening is valid. The MCU needs to report this in reverse order, and it is recommended to report it once every 1 second. 0 means off. Countdown 0 is the marker for ending remote door opening, so a countdown of 0 needs to be reported after each remote door opening operation.
Hello, if it is an All-in-One panel or studio panel, the source code cannot be provided. If it is a customized panel, you can contact the panel's project manager to discuss.
Cause: For security protection purposes, a PIN verification is required when controlling devices like garage doors via third-party speakers. For example, without this restriction, unauthorized individuals could potentially open the garage door by voice command such as"Google, open the door"outdoors.This security restriction cannot be removed. Solutions: Open the app and go to the settings page of the corresponding device to check if theVoice Settingsfunction is available. Some devices support PIN setup in the companion app of the third-party speaker. For detailed operations, refer to the product manual or contact the seller for confirmation.
Notifications are delivered in two ways: Phone Call notifications: A robot will call and broadcast the alert via voice. You can preview the voice message by navigating to Me → Settings → App Message Notifications → Phone Push. SMS notifications: Template messages are sent automatically based on your configured trigger scenarios. The message format is as follows: [App Name] XX App Alert: The SMS notification for the "Automation Name" you set under "Home Name" has been triggered. Please pay attention. Note:Phone Call notifications are made from virtual numbers, so the displayed number may vary with each call.
If the sensitivity is set too high, changes in light and shadow within the monitored area will also be detected as movement. You can adjust the Alarm Sensitivity Level to resolve this issue. The differences between High, Medium, and Low Alarm Sensitivity Levels are as follows: High: The camera will trigger an alarm upon detecting even slight movements of objects within the monitoring area. Medium: The camera will trigger an alarm only when a clearly visible object moves with moderate amplitude. Low: The camera will trigger an alarm only when a clearly visible object moves with significant amplitude. Note: If your device still sends excessive alarms and takes too many photos even after setting the sensitivity toLow, it indicates there are too many moving objects in the monitored area. You can block device notifications for specific time periods via the blocking function.
Hello! The camera may be moving on its own because you have enabled the Motion Tracking feature. When the camera detects changes in the image of a specific area, it will move to capture the scene. The Motion Tracking function not only tracks moving objects but also detects changes in light and shadow within the area. Therefore, even if there are no people or objects moving in that area, the camera may still detect light and shadow changes and move accordingly. If the Motion Tracking feature is not enabled, please reset the device, remove it from the app, and re-add it to calibrate. If the issue persists, it may be a hardware problem—we recommend contacting the seller for after-sales support.
Troubleshoot quickly by following these steps: Test the device with its physical buttons to check for proper functionality (if malfunctioning → contact after-sales support directly). Ensure the network where the device is located is stable. Replace the WiFi with your mobile hotspot to rule out network-related issues. Reset the device and set up the network connection again. If the issue persists → contact after-sales support to troubleshoot hardware faults.
This issue might be due to the "Show Remote Control" feature being turned off. It is recommended that you enable this feature and try again. Steps to follow:click on the universal remote control icon — settings in the upper right corner — "Show Remote Control" at the bottom.
Please troubleshoot the issue by following the steps below: Verify that the device is connected to the network and the network connection is stable. Check if your app is updated to the latest version. Confirm that the linked scene configured in the app is correct and does not conflict with other linked scenes. If the Automation rule is created based on environmental parameters such as temperature, humidity, weather or wind speed, execution exceptions may occur due to the device’s edge-trigger mechanism. For further troubleshooting, please submit your request via the official feedback channel. Note on Edge-Trigger Mechanism: The device triggers the Automation only at the moment when the monitored value crosses the set threshold. For example, the Automation will be triggered when the temperature rises from 25℃ to 26℃, but will not be triggered repeatedly if the temperature remains above 26℃.
Dear user, we are sorry for your inconvenience. The new Zigbee gateway supports “Automation” of local scenario, that is if all the tasks of an “Automation” and the device are under new Zigbee gateway, the “Automation” can be executived in offline mode. Even if your network is offline, the devices and tasks bound under new Zigbee gateway will still execute the automation that you have set before.
Yes. The prerequisite is that all tasks and devices under the Automation belong to the same Gateway device. Note: If the scene execution relies on cloud-based command transmission, it may fail when the external network is unavailable.
Yes. The prerequisite is that all tasks and devices under the automation belong to the same gateway. Note：If scene execution relies on Cloud Scene command transmission, it may fail when the external network is unavailable.
The system does not support directly stopping or interrupting a scene that is running. Automation: It can be temporarily interrupted by toggling the disable switch. If Automation is disabled while a delay task is in progress, the actions scheduled after the delay will not be triggered. Tap-to-Run: There is no direct stop/interruption function. To cancel a delay task, you may terminate its execution by deleting the task.
The "Arrive/Leave" feature allows you to trigger preset device actions when you arrive at or leave a designated location.Usage Steps: Enable Location Permissionfor the app on your mobile phone. Select "Arrive/Leave" in Automation settings, configure the location conditions, and complete the action setup to trigger the task. Reason for Unavailability: This feature requires Google Services support and isnot available on Android devices in Chinese mainland. Troubleshooting: If the feature fails to work, please refer to the relevant FAQ"Why doesn't the Leave or Arrive (beta) feature take effect?".
Dear user, we are sorry for your inconvenience. If you do so: Please reset the device to factory settings first. Uninstall the App, and then reinstall the App to your phone. Then add the device to the App again. If this problem still occurs, there may be a problem with the device hardware, please contact the after-sales personnel to handle after-sales for you. Thank you for your understanding and support.
Use low power control pins, the silk screen of each chip will be different, please see the instruction document for details.
Hello, Bluetooth Mesh devices support scene control, but they need to be used with our Bluetooth Mesh gateway.
To resolve the issue of authorization failure caused by the "Please re-authorize application account" notification when authorizing an application account in miniapp IDE, please follow these steps: 1. Ensure you are logged into miniapp IDE normally and verify that the application's QR code authorization has expired. 2. Check if the application account and developer tools are in the same region. 3. Manually log out of the current account and then re-authorize. 4. If the problem persists, delete the file "C:\Users\[username]\AppData\Roaming\tuya-ark-ide\extension\data\ark.virtual-devices\storage.json" on your local computer, and then log in again. 5. If the error still occurs, close miniapp IDE, delete the node.modules, dist, and yarn.lock files, and then type `yarn install` in VS Code. After installation, reopen miniapp IDE. 6. If the above methods are ineffective, try uninstalling and reinstalling the latest version of miniapp IDE. 7. Ensure that the region selected in the miniapp IDE matches the region of your app account. If your account is in the European region, please select that region.
Currently, Zigbee devices require a gateway to be controlled. Since the Zigbee protocol and the Wi-Fi protocol are different, and no mobile phone currently supports the Zigbee protocol, a Zigbee gateway is needed to convert the Zigbee protocol to the Wi-Fi protocol before it can be controlled by a mobile phone.
1、Please click on this link: https://developer.tuya.com/en/docs/iot/module-test-tool?id=K9qswhqd5ymnp, find the module or chip model, and download the test instructions. 2、The downloaded file is in Word format, and you can download the test software within the instruction by right-clicking the software archive and selecting "Save to file." 3、If you encounter issues downloading the software from the document, you can submit a ticket for consultation or contact Tuya's certification support colleagues.
Currently, Wi-Fi general integration has six operating modes. You can refer to the 01 command in the protocol at the following link: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-5-%E6%9F%A5%E8%AF%A2%E4%BA%A7%E5%93%81%E4%BF%A1%E6%81%AF%EF%BC%880x01%EF%BC%89. Common Network Configuration (0): The module remains in a state ready for network configuration after being powered on at the factory and continues to do so. Timeout Network Configuration Mode (1): Initially, the module powers on in a low power state. If a reset is triggered, it enters the network configuration state. If the module is not configured within 3 minutes, it will enter low power mode. After a reset, if the module restarts within 10 seconds, it continues in the network configuration state; if it takes longer than 10 seconds, it reverts to the low power state (the default duration of 3 minutes can be configured in the mt field). Anti-Mistouch Network Configuration (2): Initially, the module powers on in a low power network configuration state. If a reset is triggered, it enters the network configuration state. If the module is not configured within 3 minutes, it will enter low power mode. After a reset, if the module restarts within 10 seconds, it continues in the network configuration state; if it takes longer than 10 seconds, it reverts to the low power state. After successful configuration in anti-mistouch mode, a reset will not remove it from the app, and it will automatically reconnect in about 3 minutes (the default duration of 3 minutes can be configured in the mt field). Power-On Network Configuration (3): The module enters the network configuration state upon power-up. In this mode, it scans for specific beacons for end product production tests. Power-On Low Power Network Configuration (4): Upon power-up, the module enters the network configuration state. If it is not configured within 3 minutes, it automatically enters low power network confi.
Hello, please troubleshoot in the following way:If the App prompts "The region of the account you are trying to log in to does not support the service temporarily" during binding/connection, it means the registered region of your account is Chinese mainland, and you need to register an App account for another region. When binding/connection fails, we first confirm if it is caused by network issues, which is very important. Check if there is a prompt like "Can't update setting, check your connection" on the interface. Generally, for issues caused by network problems, a loading circle will appear when returning to the assistant interface, and the device list will be displayed after loading completes. If binding/connection to the Action still fails when the network is confirmed to be normal, first confirm that the account used is consistent with the environment of our official App account, then check whether there are online devices bound to the account and whether the devices are offline. If there are no online devices, binding cannot be completed. You only need to add the devices and keep them online. If there are online devices under the App account but binding/connection to the Action still fails, please confirm whether the speaker function has been enabled for the devices under the account. One account can only be bound/connected to one App account, and an error will be reported if binding is repeated. Note: Users who log in to the App via third-party login methods need to bind/connect a mobile phone number or email address first, and then reset the login password (there is no initial password for third-party login). Then use the mobile phone number or email address to log in to the App account when binding to third-party smart speakers. If the issue still cannot be resolved after eliminating the above problems, please submit feedback through the feedback channel and provide relevant information (App name, App account, name of the Action being bound/connected, dev.
Dear user, we are sorry for your inconvenience. If you do so: Verify that your mobile phone allows the App to push messages. Please confirm to open the message push settings in the App, open the App, click Me-Message Center, click the button in the upper right，enable notifications. Check Notifications Settings, whether Do-Not-Disturb Schedule was on. If your mobile phone and device allow the App to push messages but do not receive any messages, check whether the App message center has new message notifications. Some Android mobile phone systems will compulsorily judge our App push as marketing information, thereby forcibly turning off push and sound/vibration reminders. Due to limitations of some Android systems, some Android phones can only receive up to 24 App push messages. If these push messages are not cleared, the phone will not be able to receive new App push messages. Note: If your device is a smart doorbell or smart camera, and you cannot receive the incoming call. This is caused by the restrictions imposed by the mobile phone on our App. You only need to open the App, and you will receive the incoming call normally. The power saving function of some Android phones will close the background process of the App, which is also the reason why you cannot receive the App push: Please turn off the power saving function in the settings, or add the App to the white list of the power saving function (if there is no white list function, you need to turn off the power saving function). Please lock the background process of the App on the background management page of the Android phone, so that the Android system will not automatically close the background process of the App (Android systems with this function can see the "lock" mark on the background process of the App ). Please allow the App to start automatically in the system settings of the Android phone, otherwise the Android system will periodically shut down the background process of the unused App, which will a.
To troubleshoot the error, perform the following steps: Obtain the deviceBean of the gateway. deviceBean=ThingHomeSdk.getDataInstance().getDeviceBean(deviceId); Read the status (online/offline) of the deviceBean. deviceBean. getIsOnline = true/false You can pair the gateway sub-device only when the gateway is online, that is, deviceBean. getIsOnline = true. Otherwise, an error of deviceBean = null will occur.
The first time the module powered on, it will check for heartbeats every 1 second, and if MCU returns a heartbeat, the module will check for heartbeats every 15 seconds.
For Android 11 devices, you must add the ThingHomeSdk.enableBackgroundConnect() code before Tuya initializes ThingHomeSdk.init(this).
You can get the parent room information through this interface: ThingHomeSdk.getDataInstance().getDeviceRoomBean();.
ThingHomeSdk.getUserInstance().getQRDeviceAppInfo.
It can be obtained by User = ThingHomeSDK.getUserInstance (). GetUser (); StringPhoneCode = user.getPhoneCode ();.
Call the ThingHomeSdk.getMemberInstance().getInvitationList API to obtain the list of invited users.
The account time zone can be obtained through ThingHomeSDK.getUserInstance (). GetUser (). GetTimezoneId ().
Get the MAC,IP Address Universal API: ThingHomeSDK.getRequestInstance () Method: requestWithApiName (Stringapiname, Stringversion, MappostData, finalIRequestCallbackcallback) Entry: apiName: tuya.m.device.get Version: 1.0 postData: (“devId”, devId) Callback: voidSuccess (Object response); void onFailure (String errorCode, String errorMsg) The returned result contains parameters such as IP and MAC address.
ThingHomeSDK.setDebugMode(true).
This error does not affect the use of the SDK and can be ignored.
Please check if the `gid` parameter in the request is "0". If it is "0", it means the home ID was not obtained. In this case, you need to integrate the `ThingSmartBusinessExtensionKitBLEExtra` library. If you don't have it, please integrate it. Also, please note: Before making any API calls, always ensure the user is logged in. Before calling the network configuration service package logicYou must first implement the `getCurrentHome` method in `ThingSmartHomeDataProtocol`. Objective-C Example #import ThingSmartBizCore/ThingSmartBizCore.h #import ThingModuleServices/ThingSmartHomeDataProtocol.h - (void)initCurrentHome { // Register the protocol to be implemented [[ThingSmartBizCore sharedInstance] registerService:@protocol(ThingSmartHomeDataProtocol) withInstance:self]; } // Implement the corresponding protocol method - (ThingSmartHome *)getCurrentHome { ThingSmartHome *home = [ThingSmartHome homeWithHomeId:@"current home id"]; return home; }.
Hello! If you cannot find the device in the Google Home App, please first troubleshoot by following these steps: Confirm if the device supports Google Assistant: Enter the control panel, click the button in the top right corner, and check the third-party control supported by the device (Bluetooth devices must be paired with a Bluetooth gateway to be synced). Verify that the account linked to Google Home is correct. Ensure the device is online in our App: Sync failure may occur if the device is offline. If the issue persists after eliminating the above possibilities, please provide the Device ID and a screen recording of the Google Home connection process through the feedback channel. We will further assist you with troubleshooting.
Call the ThingHomeSdk.getMemberInstance().queryMemberList API to obtain the list of members existing in a home.
The "Multi-Control Association" function allows you to control the same device simultaneously after associating the buttons of multiple switches.Example: You can associate the switch that controls the bedroom light with the switch near the bedhead, allowing you to control the bedroom light simultaneously via both switches. If your switch supports the "Multi-Control Association" function: Click the top right corner to access the "Device Details" page; Locate the "Multi-Control Association" module; Click "Associate", then select the devices that support this function. If you cannot find this option, it means your device does not support the function. For accurate information, we recommend consulting the seller. Note: This function currently only supports standard-function switches. It does not temporarily support Scene Switches, curtain switches, etc.
Wi-Fi door lock protocol 03 or 04 command words will clear the network information and let the module enter the network distribution mode. The difference is: Every time the 03 command word is sent, the module switches the network configuration mode, and smartconfig and AP switch back and forth. 04 Command word, according to different DATA data, you can specify which distribution mode the module enters. Reference documents：https://developer.tuya.com/en/docs/iot/door-lock-mcu-docking?id=K950t0p1l51k2.
The ports and services locally monitored by the Tuya module are as follows: Port Number/Service Description 6668 Used only when LAN service is enabled, can be closed by disabling LAN. 6669 Used only during network configuration, will not open during normal use. 7000 Used only when LAN service is enabled, can be closed by disabling LAN. 7001 Used only during network configuration, will not open during normal use. 53 DNS resolution service, used only during network configuration, will not open during normal use. 67 DHCP service, used only during network configuration, will not open during normal use. BLE GATT Used for Bluetooth network configuration.
Dear user. This is because the EZ mode (Blink Quickly) has high requirements for the compatibility of the router, so many routers that have modified some internal protocols cannot use the EZ mode (Blink Quickly). The AP mode (blink slowly) requires relatively low router compatibility, and most routers are compatible.
Subscription services: Choose "Cancel Subscription." After cancellation, the service will automatically terminate at the end of the current billing cycle, and auto-renewal will be disabled. Non-subscription services: Paid orders generally cannot be canceled or refunded.
SmartLife App SDK Development Documentation: https://developer.tuya.com/en/docs/iot/app-sdk-instruction?id=K9kjstc7t376p App SDK Pricing: First year 33,500, then 13,000/year Among them, the Smart Camera SDK, Smart Travel SDK, Robotic Vacuum SDK, and Smart Lock SDK are vertical category SDKs that depend on the SmartLife App SDK. They are primarily tailored to encapsulate features specific to vertical categories, facilitating rapid development of product functionalities for these categories, and no additional fees are charged. Additionally, Tuya provides a range of ready-to-use UI business packages based on the SmartLife App SDK and others: https://developer.tuya.com/en/docs/iot/app-sdk-instruction?id=K9kjstc7t376p#title-1-UI%20%E4%B8%9A%E5%8A%A1%E5%8C%85. These packages allow complete functionality to be achieved through simple calls, with no additional fees. You can decide whether to use them based on your development needs.
SDK version 6.x has it enabled by default; there is no API to disable it.
If you are using firmware that enables quick connection after power loss, low power consumption is achieved by powering off the Wi-Fi module. Therefore, simply powering on the Wi-Fi module will wake it up. If you are using firmware that allows the module to enter low power mode via pin operation, you need to pull the pin high to wake it up. If you are referring to the module reporting a network status of 5, simply sending a reset command will allow the module to re-enter network configuration mode.
The Ministry of Industry and Information Technology requires that starting from September 1, 2023, all newly launched Apps must complete registration before going live,and the general process of registration is as follows: Purchase an unconfigured DNS top-level domain first Carry out ICP registration for the domain Register the App Configure your App's independent domain on the IoT platform Fill in the registration number of the App Build the App Release the App In this process, we may encounter the following issues: How to configure an independent domain for the App on the IoT platform? Do overseas apps that have been launched need to be filed for record? After purchasing the record resource package, what should I do if the record license is missing when filling in the information in the Internet information service module? Can our OEM App be filed on Alibaba Cloud? Why can't a domain name configured with DNS be used for the record filing of this app? Do I need to purchase Tencent Cloud server or resource package for filing? Do we need to remake the iOS certificate for filing? Can a second-level domain without configured DNS be successfully filed for record?
The no-code development solution does not require an external MCU, saving on product costs. The Tuya platform offers a variety of no-code development solutions for you to choose from; If the functions of the no-code development solution do not meet the actual requirements, you can opt for integration using an MCU.
Customers can be guided to customize PN for material differentiation. PN code is the material code of the module, which can be used for internal module material management and differentiation. If the PN is not filled in when placing an order, the default Tuya basic material code will be used. If the PN is entered, the entered PN will be printed.
Possible causes include version compatibility issues and limitations of the WeChat Mini Program runtime environment. Libraries that do not manipulate the DOM (such as Lodash and Redux) are usually usable; UI libraries based on the React DOM (such as Ant Design) are not usable. Check the specific error message and search for related issues in the community or third-party library repository.
In such cases, it is recommended to use real device debugging/real device preview for development troubleshooting.
Account cancellation will erase all data associated with the account, including but not limited to the following: 1. Products and services will be discontinued for this account, including but not limited to products, mobile apps, WeChat mini programs or smart miniapps, Smart Business SaaS(Smart Hospitality, Smart Protect), and4SaaS projects on the platform. 2. Value-added services and purchase orders will be invalidated for this account. 3. Account services will be discontinued.
Not supported.
Hello! You can view the supported device categories within the App via the specific path: Home Page — + icon in the upper right corner — Device Addition Page. To confirm if your device is compatible with the App, we recommend checking the product manual or consulting the seller. Adding a Device: Follow the product manual to configure the device to thenetwork-ready state. Go to Home Page — tap the + icon in the upper right corner — enter the Device Addition Page. The system will automatically search for nearby network-ready devices. Bluetooth devices and dual-mode devices are usually discoverable and displayed as pending addition; you can add them directly. If the device is not found automatically, select Manual Addition. Wi-Fi devices require manual addition: On the Device Addition Page, select the device category and communication method (check the product packaging or manual for the communication method), then follow the App’s on-screen instructions to complete the addition If you are not sure which category your device belongs to, you do not need to choose an option that matches your device. You only need to select the option with the same protocol as your device (Wi-Fi , Bluetooth, Zigbee). If you are not sure what the communication protocol of your device is, please check the product packaging or product manual for confirmation, or you can ask the salesperson for confirmation.
Solution: This error occurs because an incorrect panel is being used. It's due to the use of a mini-program panel. You need to confirm the type of panel being tested; only the RN SDK debug panel is supported.
If you don't sell value-added services, then this module is unnecessary. If you want it displayed, you can configure it in IPC Workbench - Marketing Campaigns - Service Hall Management, or consult your project manager.
This requires you to add the following: standard DP power supply mode: wireless_powermode, battery level: wireless_electricity, low battery alarm: wireless_lowpower, and the custom 7-day battery statistics function: ipc_panel_battery. Only report boolean-type function points. After adding these, it will be displayed on the home panel. You also need to submit a work order to configure the DP145 battery statistics function point, configuring it to the MAX type.
Call the `getHomeDetail` interface, retrieve `getSharedDeviceList` from `HomeBean`, and then query the list of shared devices.
There are two main reasons why the name doesn't update in sync with the phone's language: 1. The product's multi-language name isn't configured. Therefore, the name doesn't update automatically after switching the app's language. You need to go to the product's multi-language settings, edit the text, and add the language name for the different regions. Operation Guide: Document Address Note: After completing the operation, please remove the device and reconfigure it. 2. The user defined and renamed the device name after successfully configuring it. This will not be updated automatically. If the user needs to restore the default device name, they can remove the device (unbind and clear data) and then configure the device again to display the default name.
Sorry, iOS does not have an available method to determine whether Wi-Fi is 2.4G or 5G.
We're sorry, a HarmonyOS version of the SDK is not currently available.
Ensure that the Smart Life SDK version is 6.7.7 or higher to call it properly.
PackConfig is a class used to configure feature switches. You need to create an AppConfig class yourself and then initialize it by calling PackConfig.addValueDelegate(AppConfig.class). Currently, it does not support custom settings.
Quick Connect (EZ) is a legacy configuration mode. To improve the configuration experience, it has been removed from the current firmware. You can use Bluetooth configuration mode and AP configuration mode. Bluetooth configuration is enabled by default. This means that as soon as the device enters AP configuration mode, Bluetooth configuration is also enabled.
If you enable the automatic addition of discovered nearby devices feature in the app, you'll see a notification on the network configuration results screen indicating the device has been successfully added. If you don't enable this feature, you'll need to click the [Add] button on the network configuration results screen for the device to be successfully added.
Make sure the SDK version is 6.7.7 or higher. If it's lower than 6.7.7, you won't be able to call the API 'com.thingclips.smart:thingsmart:6.7.7'.
The serial port protocol includes commands for obtaining Greenwich time and local time. You can obtain the time zone by subtracting Greenwich time from the local time.
Scheduling is divided into two types: cloud scheduling and function point scheduling. 1. Cloud scheduling is divided into cloud scheduling and device scheduling (local scheduling). Cloud scheduling requires no additional processing on the panel or device side. After the panel sets a scheduled task, it is stored in the cloud. When the scheduled task expires, the cloud directly sends the scheduled task command to the device. The device executes the command, and the cloud scheduling ends. Advantages: The number of scheduled tasks is limited to 200. Disadvantages: Cloud scheduling relies on the cloud and cannot be executed if the device is disconnected from the network. Device scheduling (local scheduling) means that after the panel uses the cloud timing component to set a scheduled task, the scheduled data is updated in the device module. When the scheduled task expires, the module sends the task command to the MCU for execution. Advantages: The module executes scheduled tasks even when the network is disconnected. Disadvantages: The number of scheduled tasks is limited to 30. 2. Function point timing includes cyclic timing, random timing, motorized switching, and weekly schedules. Function point timing sends and reports timing data through function points. Because timing data is complex, function points are generally transparent or character-based. The panel sends timing data to the device through the function point according to the protocol. The device parses the function point data and starts the time locally. When the timer expires, the device reports the scheduled task.
All-in-One Panel: The all-in-one panel works immediately after your simple debugging. If this type of panel does not meet your needs, you can try out the self-developed panel. Note: The all-in-one panel cannot modify device functionality; only the panel's appearance and text can be modified. Self-Developed Panel: If the all-in-one panel cannot meet your needs, you can develop a panel on your own by using the Panel MiniApporRN Panel (Previously SDK-Based Panel, expiring soon)solution. Using the SDK and panel API provided by Tuya to develop custom panels requires some code development experience. Customized Panel: After you submit your customization requirements, Tuya will estimate and give you a quotation. If you have specific requirements for panel style or functionality that cannot be met by other solutions, you can contact your business manager to submit a customization request for a customized panel. After you complete the payment, Tuya will design and develop the panel according to your needs and bind it to your product. Studio Panel: It supports directly dragging and dropping visual functional components, what you see is what you get, and you can DIY a panel with your brand style in 5 minutes. If your product is built for mass production, the all-in-one panel and customized panel are recommended. Note that the studio panel does not support customization made by Tuya.
Check that the homeID parameter passed in when calling the API is correct. If the homeID parameter is incorrect or empty, household data will not be retrieved.
The following are several recommended smaller Wi-Fi modules suitable for space-constrained applications: Other Miniaturized Models in the T3 Series T3-2S, T3-3S, T3-E2, and T3-U-IPEX: These modules belong to the low-power Wi-Fi 6 series, similar to the T3-U, offering similar performance advantages (such as wide voltage supply, low-temperature operation, and low keep-alive power consumption) but in a more compact form factor. T1 Series Miniaturized Options T1-M: A plug-in miniaturized module with a built-in ceramic antenna or an external IPEX interface, designed for compact electrical/lighting products. T1-LC5-HL and T1-2S-NL: High- and normal-temperature versions with optimized board thickness and size, suitable for space-sensitive applications. If power consumption is a concern, the T3 series is preferred; if cost optimization is required, the T1-M or LC9 series can be considered. For specific dimensions and interface definitions, please refer to the datasheet or design guide of each module.
The "no cloud upload" setting only applies to usage scenarios where BLE devices are directly connected to the app. In this specific scenario, the app determines whether data reported by the device to the app should be uploaded to the cloud based on whether the function point (DP) is configured for no cloud upload. This setting does not apply to devices using other protocols.
After clicking the "Photo Mode Settings" and "Auto Lock" function points on the panel, the data is directly cached in the cloud. Therefore, it is necessary to proactively send the 0x15 DP cache command each time the device comes online to actively retrieve it once. Each time the APP UI panel is set, the cache must be obtained before proceeding to the next APP UI setting. Reference protocol: https://developer.tuya.com/en/docs/iot/door-lock-mcu-protocol?id=Kcmktkdx4hovi#title-18-%E8%8E%B7%E5%8F%96%20DP%20%E7%BC%93%E5%AD%98%E5%91%BD%E4%BB%A4%200x15.
The MCU first reports the functional data of DP8 alert, then triggers capture or video by sending the 0x64 command for alert event reporting. Reference protocol:https://developer.tuya.com/en/docs/iot/door-lock-mcu-protocol?id=Kcmktkdx4hovi#title-54-%E8%A7%A6%E5%8F%91%E6%8A%93%E6%8B%8D%E5%91%BD%E4%BB%A4%200x64.
As a smart speaker, its display interaction embodies the specificity of minimalist design, with a primary focus on voice interaction. The basic descriptions of LED statuses are as follows: a steady blue light indicates the device is awake and ready for interaction, a breathing blue light signifies voice recognition during a conversation, and a steady blue light appears again when responding. During network pairing activation, red and blue lights alternate, while a steady red light indicates a disconnected network. A breathing blue light is also used to represent scenarios such as configuring sub-devices and Bluetooth connections, among other lighting effects.
Currently, only the BLE Bluetooth network configuration method is supported. The network configuration process is accompanied by device activation, which requires obtaining geolocation information. Therefore, during network configuration, it is necessary to ensure that both the phone's Bluetooth and location services are enabled, and that the app has been granted the relevant permissions.
Currently, the SDK does not provide a corresponding JSON file for time zones or a direct interface to fetch them. Time zones like "Asia/Shanghai" and "America/New_York" are universally standardized and can be retrieved using standard Android APIs. For example, you can use methods such as TimeZone.getDefault().getID to obtain all available time zones and display them. You can refer to the following link and call the relevant methods yourself to retrieve the time zones: https://developer.android.com/reference/kotlin/java/util/TimeZone#getavailableids.
This is because the camera has an upper limit on the number of devices that can view it simultaneously. If you encounter this prompt, you can ask other devices that are currently viewing the camera to exit first, and then turn it on again. After that, you will be able to view it normally.
Setting disableCache: true in global.config.ts disables memory caching and prevents restoring to the last page.
Use initPanelEnvironment, for example: initPanelEnvironment({ useDefaultOffline: false, showBLEToast: false });.
Simple implementations are possible, using capabilities like canvas.
You can check step by step: Whether the file format is EXCEL/JSON supported by the platform and smaller than 1 MB; Whether Chinese text is written under languages such as English; Whether the Chinese and English keys are misaligned; Whether there are duplicate keys (common in EXCEL).
After creating a curtain on the platform, you can view the available modules on Hardware Development page.
Yes, they do. Only the low-power firmware does not support reconnection.
The SDK has a 30-second disconnection mechanism defined by #define tuya_ble_connect_monitor_timeout_ms 30000. When the device is connected, if the connection status i sUNBONDING_UNAUTH_CONN (unbonded, connected, unauthenticated) or BONDING_UNAUTH_CONN(bonded, connected, unauthenticated), a 30-second monitoring timer will be activated.
On the RN panel, you can use TYSdk.devInfo.deviceOnline to obtain the device's online status, but it doesn't support the specific channel being online. The panel miniapp does support this, and we recommend using the panel miniapp for development. Please refer to the documentation: https://developer.tuya.com/en/miniapp/develop/ray/api/device-info/info/getDeviceOnlineType#getdeviceonlinetype.
You can upload up to 6 images.
It does, as long as the program is built with relay functionality.
Call the noDisturbAddAlarm API to set a do-not-disturb period. This is typically for alarm messages. By adding the device and time zone to the do-not-disturb period, you won't receive alarm messages from that device during that period. https://developer.tuya.com/en/docs/app-development/extension-message-dnd?id=Ke7ygf51ile0h#title-4-Add%20DND%20periods.
Use the requestWithApiName common API to call tuya.m.country.list to obtain the country code list. Switching to a multilingual system will automatically switch to the corresponding multilingual country code list, for example, Chinese, English, German, Spanish, and more. https://developer.tuya.com/en/docs/app-development/commoninterface?id=Ka6o3bst0te1r.
After successful network configuration, obtain the device ID. Then instantiate a DeviceBean. Based on the query schema, the corresponding DP point function in the device is obtained. For example, DP point 1 in the attached file is a switch. The product ID can also be found in the DeviceBean. DeviceBean deviceBean = ThingHomeSdk.getDataInstance().getDeviceBean In the returned example, id 1 represents DP point 1, name is switch, and type represents the Boolean type. When sending, select true or false. "code": "switch_1", "iconname": "icon-power" "id": 1, "mode": "rw", "name": "switch", "property": { "type": "bool" }.
Yes, you can register in the Cloud API and client API according to the attached documentation, but you must log in through the app. Cloud API: https://developer.tuya.com/en/docs/cloud/21707ff1ba?id=Kawfjd7120rb0 App: https://developer.tuya.com/en/docs/app-development/usermanage?id=Ka69qtzy9l8nc.
Set bool name="is_scan_support"false/bool in compat-colors.xml.
Not necessarily all deleted, there are two scenarios 1. If the sub-device protocol type includes Bluetooth, including: Wi-Fi/Bluetooth, BLE (single-point Bluetooth), Bluetooth beacon, Sigmesh, the gateway unbinding will not remove the sub-devices, because the App can still control them through the mobile phone's Bluetooth. 2. For non-Bluetooth protocol, after the gateway unbinding and data clearance, the sub-devices will also be removed.
DFS is the abbreviation for Dynamic Frequency Selection, a wireless network technology used to automatically detect radar signals in the wireless spectrum and switch to other channels to avoid interference when these signals are detected. DFS is mainly applied in the 5GHz wireless band, especially in wireless networks using the 802.11a/n/ac/ax (Wi-Fi 5 and Wi-Fi 6) standards. The main purpose of DFS is to protect important radar services, such as military and weather radars, from interference by other wireless device operations. According to international and regional radio regulations, some channels within the 5GHz band are shared, meaning that Wi-Fi devices and radar systems may use the same frequencies. Therefore, Wi-Fi devices using DFS must have the capability to detect radar systems and automatically adjust their operating channels. In practical applications, when a Wi-Fi access point enables DFS, it listens to channels that may be allocated for Wi-Fi communication to detect if a radar system is in use. If a radar signal is detected, the DFS function will force the device to switch to another channel that will not cause interference, and the channel occupied by the radar will not be used again for a period of time. Currently, 5G Wi-Fi products in the 5.25-5.35GHz and 5.47-5.725GHz bands require DFS testing in CE FCC, SRRC certification tests.
BT series modules and ZT series modules need UART + Tailing Micro Programmer BP series modules and WiFi modules need UART only. If the quantity is large, they can be paired with programming tools for use ZS series modules require UART and J-link, the platform does not provide JLINK and needs to be purchased online by yourself.
Thailand NBTC certification is a type of radio and communication equipment certification issued by the National Broadcasting and Telecommunications Commission (NBTC) of Thailand. NBTC is an independent regulatory authority in Thailand responsible for overseeing and managing the broadcasting and telecommunications industries. The purpose of NBTC certification is to ensure that radio and communication equipment complies with Thailand's technical standards and regulations. This applies to all radio equipment sold and used in the Thai market, including mobile phones, wireless LAN devices, Bluetooth devices, satellite devices, radio-controlled toys, etc. To obtain NBTC certification, manufacturers or importers need to submit technical documentation of the relevant equipment for review and ensure that the equipment has passed the necessary tests. These tests typically involve aspects such as frequency usage, power output, and electromagnetic compatibility of the equipment. Certified equipment will be granted the NBTC mark, indicating that the equipment has been verified and can be safely used within Thailand without causing harmful interference to other radio communication services. For companies wishing to import or sell radio communication equipment in the Thai market, obtaining NBTC certification is a necessary step. Wi-Fi1/Bluetooth/Zigbee products can be certified through CE reports.
1、After the Wi-Fi module has passed the production test 1 and production test 2, it can enter the production test 2 again after power on; 2、If the firmware configuration information of PID on the IOT platform selects to re-enter production test 1 not supported, production test 1 cannot be re-entered; if it selects support, it can re-enter production test 1 through the following operations: – In the production test environment (both production test 1 and production test 2 routers exist), power on three times in a row to enter production test, and the first two times to enter production test time are 5S, the third time to power on will enter production test 1 3、If the device is connected to the app for more than 15 minutes, it will not enter the production test. To enter the production test again, you need to connect the device to the app, keep it online, copy the device ID provided on the App, and we can re-enter the production test after a background operation. – When pairing devices with app, there should be no tuya_mdev_test1 or tuya_mdev_test2 signals.
Mandatory certification for electronic and electrical products in Canada. Similar to FCC, it is divided into verification and Certification. Conventional Wi-Fi/BT/Zigbee wireless products need to be certified according to Certification, and after obtaining the certificate, the IC ID number needs to be marked on the nameplate. IC certification and FCC certification can be applied for simultaneously, and certification can be transferred based on the FCC report, saving time and costs.
It will still execute, but being offline may cause some deviations.
During the initialization process of the distribution network, the module will issue a value of 0x03 command. When the value changes to 0x04, it indicates that the distribution network is successful. If it is a standard SDK for porting, you can actively call mcu_get-wifiw_work_state to obtain the network status. It should be noted that the default value of wifiw_work_state is set to FF. Please refer to the next serial port protocol for details: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title -8-%E6%8A%A5%E5%91%8A%E8%AE%BE%E5%A4%87%E8%81%94%E7%BD%91%E7%8A%B6%E6%80%81%EF%BC%880x03%EF%BC%89.
The protocol between the Zigbee module and the device belongs to the Tuya custom protocol. The current no-code development lighting, channels 1-5 all support the Zigbee3.0 standard protocol. Whether other Tuya Zigbee products are compatible with other brands of Zigbee gateways requires actual testing and verification.
Tuya Wi-Fi no-code development solution supports OTA, and OTA uses sha-256 hash signature algorithm.
The Tuya platform currently has a no-code development solution, which is implemented with the power statistics chip and module IO port collection.
The platform's no-code development solution can be created up to 4 channels. If you need more than 4 channels, you can create a switch for a universal docking solution. It supports up to 25 DP points, that is, up to 25 channels of switches.
For Tuya no-code development solution, Wi-Fi supports up to 8 channels, and Zigbee supports up to 4 channels. If you need more functions, please choose MCU docking custom development.
The no-code development solution on the platform has a total of 6 I/O ports available: GPIO0, GPIO4, GPIO5, GPIO12, GPIO13, and GPIO14.
After you create a product in the Tuya developer platform and select the corresponding hardware (chip, module or PCBA), the system will automatically match the firmware according to your development solution. Due to market changes and development solution upgrades, Tuya will regularly upgrade the firmware. Tuya will deprecate some firmware of old versions based on the original chip iteration. In the Tuya developer platform, higher or other available versions will be provided for selection and use. The constant software upgrade services ensure that the products can be operated properly with different firmware versions. Even if the products are being developed or have been produced, this services can help to ensure the delivery of quality products. Note: We will burn the no-code development firmware you configured on the platform into the sample for you, without you having to burn it yourself. The no-code development firmware does not support self-downloading and burning. For more details please see: https://developer.tuya.com/en/docs/iot/firmware-replacement-instructions?id=K9rsxvicyic7y.
Currently, no-code development sensor devices support Zigbee host production test, including PCBA host production test, gateway + host production test; No-code development electrical products and lighting support beacon production test, with metering sockets, switches, plugs and so on support gateway + host end product production test.
In order to ensure that the color light of the light has no color cast, the firmware has built-in Gamma correction, and the Gamma value can be adjusted through the Gamma parameter of the no-code development solution.
If your product is a no-code development solution, you only need to configure the relevant firmware information in the hardware debugging section. If your product is a custom solution, you can choose Tuya firmware or upload custom firmware.
When using IIC driver, only needs 2 IIC pins to drive.
Thank you very much for your trust and support for the platform. Due to the inability to implement scale production burn-in for small batch module orders, manual burn-in is required. To improve delivery efficiency and service quality, the platform has decided to charge a burn-in fee of 200 yuan for orders of single product modules less than 100 pcs from November 21, 2022. No separate burn-in fee is charged for orders of 100 pcs or more. You can also choose naked delivery when you place an order, and complete the burn-in by yourself after receiving. The burning tool can be purchased on the platform, or you can buy it on your own from a third party, and carry out the burn-in by yourself according to the burn-in guide provided by the platform. Platform operating path: Procurement Production R&D Procurement Product Deliverables Procurement Reference for self-burning: How do I flash a small batch module developed in no-code development mode?
The phenomenon is normal; the Bluetooth mesh mechanism works this way. Bluetooth mesh is a topological structure, where one node finds another node. If the entire mesh can find at least one node, it will show as online. It will only show as offline when not a single node can be found. When one of the lights goes offline and no one interacts with it actively, the offline status of the light is not real-time. Only when someone interacts with it can it be determined whether it is offline or not.
Standby power consumption is about 8mA.
The MOQ for cloud module purchases during the trial production and mass production stages is ≥20.
The demand for custom hotspots can be achieved by purchasing value-added services of "Hotspot Customization". There are two situations when modifying the hotspot name: 1. If you haven't placed an order yet, please specify the custom part when placing your order. The custom part must be no longer than 12 characters, including both Chinese and English. Special characters and emoticons are not supported. The hotspot name will be: SL (fixed) – XXXXX (custom part) – XXXX (last 4 digits of the MAC address, automatically generated by the system, no maintenance required), for example, SL-smartlife-3012. For more information, please refer to the document: https://developer.tuya.com/en/docs/iot/customized-hotspot?id=Kafuzks2ue6ur 2. If you have already placed an order and need to modify the hotspot name, the hotspot owner should contact their account manager.
The network configuration mode is selected based on the m field in the 0x01 command. Refer to the protocol: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-7-(Optional)%20Sync%20new%20feature%20settings%20(0x37%20%26%200x00). During timeout configuration and to prevent accidental configuration, the module is first powered on in the low-power configuration (non-configuration) state. After the MCU sends a reset command, the module enters the configuration state. Within 10 seconds of this configuration state, if you power on the module again or reset it by pulling the EN pin, the module will return to the configuration state. If the module exceeds 10 seconds, it will enter the low-power configuration (non-configuration) state. If you do not reset the module, the timeout period is 3 minutes (configurable using the mt field). The main difference is that the 10-second timeout is not configurable, while the timeout period for configuration is configurable from 3 to 10 minutes.
IPC can only purchase cloud storage services through the app; there's no API for purchasing cloud storage services on the cloud.
On the CF chip platform and the latest OS 3.x firmware, the message "BLE GAP EVENT DISCONNECT (0x213)" indicates that the app actively disconnected the Bluetooth connection. You need to check whether the network pairing time has expired. Upload the app log and investigate the cause of the disconnection on the app side.
Currently, this interface is not available.
Yes, CBU-IPEX and CBU only differ in antennas; their software is interchangeable.
Enter the Tuya PMS register an account, and log in. Click Download Software to download the Tuya Cloud Module Burning Authorization Platform. For more details about the Procedure, please see: https://developer.tuya.com/en/docs/iot/overview-of-download-firmware-and-authorization?id=Ka4zcqfo0eb5u#title-4-Procedure.
Hello, if you buy a module, the firmware (including license) has been burned before leaving the factory, you can activate it directly. If you chose empty delivery, you need to download the license after the module is shipped, and then use Tuya production tools to program the license yourself.
This means that this configuration only affects the delivery form you download when you extract the license of the product, such as when you purchase the license of the product separately and extract the license later; If you choose customized delivery when ordering a module, the Tuya factory will use the production voucher to burn the license for your module by default, and you can use it directly after receiving it.
Can be purchased at: https://www.tuya.com/vas/commodity/DEVICE_MESSAGE_QUOTA_COMMODITY.
Ensure that an Android app is not re-signed after being launched on the Google Play. If the app is re-signed, the original app fingerprint will become invalid and you need to configure the new fingerprint in the Google backend. As shown in the following figure, the app signing certificate is the new signature after the app is launched on the Google Play and re-signed. On the Google Cloud platform, check whether the package name, fingerprint, and API key are the same as those on the Tuya developer platform and check whether an Android app is selected. For the map key created on the Google platform, confirm the app fingerprint and Google Maps' API key in the Tuya backend. Other precautions: (1) Configure map information correctly on the Tuya packaging platform before packaging. (2) Check whether the app launched on the Google Play is re-signed. If it is re-signed, add the new SHA1 fingerprint to the API key on the Google platform. (3) To access Google Maps in China, enable the international network access service. (4) If no map information is displayed in Google Maps, check whether the map is correctly configured.
Configure FCM information according to the documentation, obtain the token, and register the device to Tuya using registerDevice. Set the account country code to a foreign region and access to international networks. Ensure the phone supports Google Play Services.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please confirm whether it is caused by the network. It is recommended that you see if there are prompts like “can't update setting, check your connection” on the Google Action screen. If you cannot connect because of the network, In the return to the assistant interface, there will be a loaded circle, and the device list will be displayed after loading. If it is determined that the action of the network fails to be bound, verify that the account to be bound is the same App and account. Check if there is an online device bound to the account and if the device Appears. Offline situation? If there is no online device, you only need to add a good device and keep it online. If there is a device under the App account and it is online, the Action cannot be bound. Please confirm whether the device under your account has been enabled by Google's speaker function.
Dear user, we are sorry for your inconvenience. If you do so: Enter the settings of your phone, check whether the time zone and time of your phone are correct. Try to switch the network of your mobile phone. For example, if you are using mobile data, you can try to switch to a Wi-Fi network.
Modules that are not available for selection may be out of stock or removed from the shelves due to firmware maintenance. We recommend that you use modules recommended by the platform.
Dear user，sorry for the inconvenience，if you do so： Verify that your mobile phone allows the App to push messages. Please confirm to open the message push settings in the App, open the App, click Me-Settings-App Notification-System Notification-Enable System Notification. Check Notifications Settings, whether Do-Not-Disturb Schedule was on. If your mobile phone and device allow the app to push messages but do not receive any messages, check whether the app message center has new message notifications. The power saving function of some Android phones will close the background process of the App, which is also the reason why you cannot receive the App push: Please turn off the power saving function in the settings, or add the App to the white list of the power saving function (if there is no white list function, you need to turn off the power saving function). Please lock the background process of the App on the background management page of the Android phone, so that the Android system will not automatically close the background process of the App (Android systems with this function can see the "lock" mark on the background process of the App ). Please allow the App to start automatically in the system settings of the Android phone, otherwise the Android system will periodically shut down the background process of the unused App, which will also affect the push of App. If message pushing is enabled for the message center and your mobile phone but you still do not receive any messages, provide us with your device ID and the messages that you are supposed to have received. We will arrange for technical support engineers to troubleshoot this issue. The following is the specific setting process of some common mobile phone brands. Samsung phone XiaoMi phone HUAWEI phone OPPO phone VIVO phone.
Tuya's Wi-Fi/Bluetooth/Zigbee modules are not applicable to IEC 62151. The IEC 62151 standard applies to devices designed and intended to connect directly to telecommunications networks. Wi-Fi/Bluetooth/Zigbee products are indirectly connected to the internet through a gateway or router. As of March 2024, in the industry, if IoT products in the EU need to assess network security, the generally chosen standards are EN 303645 or the CE RED directive's testing standard EN 18031.
China's model approval SRRC certification refers to the radio equipment model approval system implemented by the Radio Type Approval Committee (SRRC) under the State Radio Monitoring Center (SRMC), which is part of China's radio management authority. SRRC certification is a legal requirement for the import and sale of radio transmitting equipment in China. The purpose of SRRC certification is to ensure that radio equipment can effectively use radio spectrum resources without causing harmful interference and complies with China's radio regulations and technical standards. This involves testing the transmission characteristics of radio equipment, including parameters such as frequency, power, and bandwidth. Equipment requiring SRRC certification includes, but is not limited to, mobile phones, wireless local area network devices (such as Wi-Fi routers), Bluetooth devices, radio-controlled toys, and wireless data communication devices. Before equipment can be sold in the Chinese market, manufacturers or importers must submit the technical data of the relevant equipment to SRRC for review and ensure that the equipment has passed the necessary tests. Once SRRC certification is obtained, the product will be granted a model approval certificate and number, and this number, CMIIT ID, usually needs to be marked on the product. Currently, the testing standard for 2.4G Wi-Fi Bluetooth devices is "Notice from the Ministry of Industry and Information Technology [2021] No. 129: Concerning the Strengthening and Regulation of Radio Management in the 2400MHz, 5100MHz, and 5800MHz Bands".
Field explain Device SN SN is the serial number. There is a one-to-one correspondence between the device SN and the device's uuid. It refers to the serial number maintained by the customer system itself, which can be found in the PMS system (https://pms.tuya.com/Production Management-Assembly Test-Customer SN Binding or Production Management-Label Printing-Special Label Printing) Complete the binding relationship with the device uuid. After completing the binding, customers can check the corresponding device information through the management device SN. Module SN SN is the serial number. When the Tuya production tool performs burning authorization, it will generate the uuid of the device and bind an SN code. There is a one-to-one correspondence between the module SN and the uuid of the device. In order to facilitate customers to trace shipped equipment. Module firmware key When the product is in IoT Platform Product Development - Product Details - Hardware Development, if the bound firmware type is module firmware or in the firmware OTA, there is an upgrade record of the product's firmware type being module firmware. Here you can see the corresponding firmware key. Module firmware version When the device is activated, the verSw firmware version reported by the device's main networking module. Devices without a primary networking module are empty. For example, sub-devices, or devices without Wi-Fi modules. MCU firmware key In the firmware OTA, there is an upgrade record of the firmware type of this product as MCU firmware. Here you can see the corresponding firmware key. MCU firmware version If the device contains the mcu module + its version number when it is activated, it is the version number of the mcu module. Otherwise, it is the firmware version number of the main networking module when the device is activated. Last update The user modifies the basic information of the device, such as the last modification time of the device name.
Currently, Wi-Fi/BT/Zigbee modules shipped without shielding and antennas are considered limited modules. Additionally, according to FCC certification requirements, if a limited module obtains an FCC certificate, it needs to be tested with the final product as the HOST. However, during the module development stage, the final product cannot be provided. At the same time, the FCC certificate of the limited module cannot be directly referenced by downstream products. Therefore, the module undergoes fixed frequency testing according to FCC radio frequency requirements to obtain a test report proving the module's technical compliance.
When the power outage is lifted or the network is restored, most cameras have the function of automatically reconnecting to the network. Once the network is restored, the camera will try to reconnect to your Wi-Fi network. This is usually an automatic process, and you do not need to manually intervene. If your camera does not automatically reconnect to the network, you can try the following troubleshooting steps: Power: Make sure the camera is properly connected to the power and the power supply is normal. Network: Check that the home WiFi network is working properly. You canrestart the router or try to connect other devices to verify that the network connection is normal. Restart the camera: Try to disconnect the camera from the power and reconnect it to the power, let it restart. Wait for a while, the camera should try to reconnect to the network. Manually configure the network connection: Find the camera in the original home and unbind it from the App, re-connect the network and add the camera, and check the latest firmware. If you have tried the above steps but the problem still exists, it is recommended to refer to the user manual or contact the manufacturer for further troubleshooting.
1、Distinguish between power-on network distribution and button network distribution (Wi-Fi) for entering the production test state differently: Power-on network distribution: 3-second flashing Button network distribution: 250-millisecond flashing 2、Check if the device has network distribution; if the network distribution exceeds 15 minutes, the production test will be closed and cannot enter the production test state.
Hello, please refer to the following Wi-Fi online: onlineType = typeWiFi = 1 BLE online: onlineType = typeBle = 4.
The main steps are as follows: 1. Product Definition: Define the product's specific functions on the developer platform, focusing on data transmission content and format; 2. Interface Configuration: Select and configure a personalized UI based on the product's characteristics, focusing on style, color, icons, etc.; 3. Hardware Selection: Select a suitable Wi-Fi communication module based on the product's PCB characteristics and requirements; 4. MCU Development: Adapt and develop the MCU control program, focusing on network configuration, data interaction, map transmission, etc.; 5. App Development: Build a manufacturer-specific app, focusing on the logo, welcome page, device page, etc.; 6. Operations Management: Configure the app interface in multiple languages, apply for smart speaker activation, and perform other core operations such as OTA device upgrades.
This is because the number of the temporary password opening record reported by the MCU is not consistent with the number issued. You can pay attention to the number issued. The actual number of the Wi-Fi door lock needs to be reported based on the password number + 900.
CE reports are the general term for the test reports required for CE certification. CE certification includes tests in multiple fields, such as safety LVD reports, electromagnetic compatibility EMC reports, radio frequency RF test reports, energy efficiency ERP reports, environmental protection ROHS reports, and so on. EN 300328 is the test standard for local area network technologies like Wi-Fi, Bluetooth, and Zigbee operating in the 2.4G band (2400-2483.5MHz). Therefore, the EN 300328 report is a type of CE RF report, and the CE RF report is one of the CE reports. EN 301489 series standards are the EMC standards for radio equipment testing.
There are some differences between light source solutions and downlight solutions in the field of smart home lighting: 1. Communication Method: Creating downlights only supports Bluetooth mesh communication, while light sources support Wi-Fi, Bluetooth, Bluetooth mesh, or Zigbee communication options. 2. Network Configuration Method: The light source solution requires power cycling to enter network configuration mode, whereas the downlight solution can use AC detection or power cycling. 3. Remote Control Type: The light source solution typically uses a Beacon universal remote or Wi-Fi remote, while downlights use a Bluetooth Mesh module and require a Bluetooth mesh remote. 4. Application Scenarios: The downlight solution is usually suitable for all-metal shell lamps, such as downlights, outdoor lamps, etc. These lamps require special consideration of antenna RF design, and may even need an external antenna. The light source solution is suitable for a wider range of lighting products, such as ceiling lights, panel lights, etc., and can also be used on downlights. 5. Drive Solution: Although downlight and light source solutions may have similarities in driving, there are differences in the design, value, and application scenarios of each type of lamp.
Hello, Homekit is a smart home platform released by Apple in 2014. Because Apple has requirements for the hardware of products connected to Homekit. If your hardware meets Apple's specifications and you want the product to be connected to Homekit, you can contact your project manager. For more details please see: https://www.tuya.com/vas/commodity/detail?code=WWHK Note: Currently supported are electrical lighting and Wi-Fi products with general firmware, as well as Zigbee gateway sensor products.
In the SDK, the initial value of the Wi-Fi status is initialized to FF, which indicates that the module has not yet obtained and sent the network status. It is recommended to delay or actively send the network status from the module before actively obtaining it. The SDK code is shown in the figure:.
The universal Wi-Fi docking protocol does not have instructions to turn off the module network, but during the opening process, the device may not be discovered by the user immediately after being powered on. There are two ways to prevent the APP from actively discovering the device. 1, if the module does not carry Bluetooth, you can reset the module's network configuration to AP pairing mode, and you need to actively identify the device configured as EZ network (Smartconfig mode) mode; 2, control the module's EN pin through the MCU, controlling whether the module is enabled.
There is a limitation, Wi-Fi has a -60dB signal strength limit.
The serial port of a 5V microcontroller is also 5V, but the serial port of the module is 3.3V. When the serial port voltage of the MCU and Wi Fi module is inconsistent, they cannot be directly connected. Can use level conversion circuit. Tuya official website has a recommended level conversion circuit that can be used.https://developer.tuya.com/en/docs/iot/wbr3-module-mcu-serial-communication-instructions?id=K9pfgdk62ae6g.
Yes. It needs to switch level. Select the corresponding MCU docking hardware design according to the communication protocol.
Apple allows users to transfer apps from the original developer to the target developer and provides a series of transfer step tutorials. You can complete the transfer process independently in the App Store Connect backend. However, if your app includes the following features, you cannot directly transfer it. You will need to seek customer service support before you can proceed with the transfer. Sign In with Apple If your app’s login screen previously included the Sign In with Apple feature, you will need Tuya’s assistance to handle data migration before it can be used normally under the target developer. Direct transfer will result in the loss of accounts registered and logged in with Sign In with Apple under the original developer. The feature entrance is shown in the figure below: Wi-Fi Quick Connect Mode Wi-Fi Quick Connect, also known as Easy-Connect, SmartConfig, or EZ Mode, relies on the target developer account already having Multicast Networking permission. The target developer account needs to obtain this permission before transferring the app. You can independently complete this application step on the Apple website. Critical Alerts For security-related products, when alarm information is pushed, the phone or iPad may be in “Do Not Disturb” mode or silent mode, leading to users missing notifications, which poses a security risk. Having this permission allows notifications to be pushed to users with an alert sound even when the device is in silent or do not disturb mode. This feature relies on the target developer account already having Critical Alerts permission. The target developer account needs to obtain this permission before transferring the app. You can independently complete this application step on the Apple website. In-App Purchases Apps with in-app purchases enabled will require Tuya’s assistance to handle data migration before they can be used normally under the target developer. Direct transfer will result in the inability to make purchases u.
This prompt indicates that the Identifier is already in use. Please click Back to return to the previous step, change the Identifier, the content of the registered Identifier can only be the App ID you created in the previous step with the group prefix. For example, if the App ID you created in the previous step is com.example.app, then the current Group ID Identifier can only be group.com.example.app.
It is not necessary. After selecting on the developer platform, the dependencies in the compressed package are just to let you know what the specific dependencies for the corresponding functions are. If there are any new business package functions added or corresponding functions deleted later, you only need to find the corresponding build.gradle in the development documentation and delete the corresponding dependencies. There is no need to reselect. Business package documentation:https://developer.tuya.com/en/docs/app-development/introduction?id=Ka8qhzjygzfau.
Currently, after the App SDK expires, even if the service is not renewed, the SDK can continue to be used, and new users can be registered beyond the limit of 100 users.
The implementation of the panel timing function requires selecting an adaptation plan based on the actual business scenario. The configuration paths and operational requirements for different types of panels vary, as detailed below: 1. Public Version Panel: For public version panels, developers do not need additional development and can directly enable the timing function through the platform's standardized path. The steps are as follows: Enter theProduct Development module; Select the corresponding product and enter theFunction Definition page; On the Function Definition page, find and click theProduct Advanced Features option; In the advanced features list, enable thePanel Timing Function. After configuration, the panel will automatically support timing capabilities without additional code development or configuration operations. If the "Panel Timing Function" has been enabled through the platform but the timing entry is not displayed correctly on the panel side, you can troubleshoot step by step according to the following scenarios: Scenario 1: Display Abnormality Caused by Cache Possible Cause: The local cache of the App has not been updated in time, resulting in the newly enabled timing function not being synchronized to the front-end interface. Troubleshooting Solution: It is recommended that users clear the local cache of the corresponding App,click here for the operation guide, and reopen the App to check if the timing function is displayed correctly. Scenario 2: Panel Type Does Not Support Cloud Timing Display Possible Cause: The current panel type (such as a freely configured panel or certain specific public version panels) does not support the front-end display of cloud timing functions due to architectural design limitations. Solution: If cloud timing functionality is required, developers can consider customizing the panel or developing or building a Studio panel to achieve it. 2. Studio Panel The Studio panel timing function needs to be implemented by c.
Hello, for the app SDK Android side, calling the following method can successfully obtain the country list: val postData = mutableMapOfString, Any() postData["lang"] = "en_US" ThingHomeSdk.getRequestInstance().requestWithApiNameString?( "tuya.m.country.list", "1.0", postData, String::class.java, object : IThingDataCallbackString? { public override fun onSuccess(result: String?) { } public override fun onError(s: String?, s1: String?) { } }) The returned data is similar to: [{"a":"AD","c":"376","continent":"EU","iso3":"AND","n":"Andorra","p":"andaoer"},{"a":"AE","c":"971","continent":"AS","iso3":"ARE","n":"United Arab Emirates","p":"alabolianheqiuzhangguo"},{"a":"AF","c":"93","continent":"AS","iso3":"AFG","n":"Afghanistan","p":"afuhan"},{"a":"AG","c":"1268","continent":"NA","iso3":"ATG","n":"Antigua and Barbuda","p":"antiguahebabuda"},{"a":"AI","c":"1264","continent":"NA","iso3":"AIA","n":"Anguilla","p":"anguila"},{"a":"AL","c":"355","continent":"EU","iso3":"ALB","n":"Albania","p":"aerbaniya"},{"a":"AM","c":"374","continent":"AS","iso3":"ARM","n":"Armenia","p":"yameiniya"},{"a":"AO","c":"244","continent":"AF","iso3":"AGO","n":"Angola","p":"angela"},{"a":"AR","c":"54","continent":"SA","iso3":"ARG","n":"Argentina","p":"agenting"},{"a":"AS","c":"1684","continent":"OC","iso3":"ASM","n":"American Samoa","p":"meishusamoya"},{"a":"AT","c":"43","continent":"EU","iso3":"AUT","n":"Austria","p":"aodili"},{"a":"AU","c":"61","continent":"OC","iso3":"AUS","n":"Australia","p":"aodaliya"},{"a":"AW","c":"297","continent":"NA","iso3":"ABW","n":"Aruba","p":"aluba"},{"a":"AX","c":"35818","continent":"EU","iso3":"ALA","n":"Aland","p":"aolan"},{"a":"AZ","c":"994","continent":"AS","iso3":"AZE","n":"Azerbaijan","p":"asaibaijiang"},{"a":"BA","c":"387","continent":"EU","iso3":"BIH","n":"Bosnia and Herzegovina","p":"bosiniyaheheisaigeweinei"},{"a":"BB","c":"1246","continent":"NA","iso3":"BRB","n":"Barbados","p":"babaduosi"},{"a":"BD","c":"880","continent":"AS","iso3":"BGD","n":"Bangladesh","p".
This is normal. The air conditioner gateway's logic is designed as follows: 1. Air conditioner Gateway A is equivalent to a Zigbee slave device. It lacks Wi-Fi capabilities and cannot be added directly to the app. It connects to the air conditioner via a wired connection, such as 485 or 232. 2. Air conditioner Gateway A must be added to Zigbee Gateway B to be used. 3. Air conditioner Gateway A creates a virtual ID and panel for each connected air conditioner, allowing it to connect to Gateway B. Each air conditioner can be controlled individually on the app.
Dear user, we are sorry for your inconvenience. Data may be unavailable under the following conditions: You have just purchased the cloud storage service. In this case, it is normal if there is no data. Your device is offline. Offline devices cannot upload data to the cloud or record. The SD card in your device is not in FAT 32 format and cannot store data in the SD card. You are using an SD card to store videos, and you have selected Event recording mode, but you have turned off the camera's motion detection function, so the camera will not record events. Your device is damaged and cannot upload data to the cloud. In this case, contact the device supplier to repair your device.
If there are no errors in the code, check if your device uses Zigbee communication. If it is a Zigbee device, real equipment must be used for testing. Virtual devices cannot navigate to the group page, with Android showing an inability to navigate, and iOS allowing navigation but not displaying devices that can be created or added.
During development, if the configuration hides the capsule in the upper right corner, you can use changeDebugMode to set the debug mode. Make sure to disable this feature when going live. import { changeDebugMode } from '@ray-js/ray'; changeDebugMode({ isEnable: true, success: function () { console.log('success'); }, fail: function (e) { console.log('fail', e); } });.
16 channels, channel spacing 5MHz, numbered CH11-CH26, channel center frequency list: 2405MHz, 2410MHz, 2415MHz, ......, 2475MHz, 2480MHz, etc., with an actual 99% occupied bandwidth of about 3MHz. There is an overlap with Wi-Fi channel distribution, and after overlapping, there will be significant interference with each other. In China, the commonly used Wi-Fi channels are 1, 6, 11, so the preferred Zigbee channels are 11, 15, 20, 25, 26. The module will automatically select the optimal channel based on the environment.
It may be because the product uses a non-standard DP, resulting in a mismatch with the reference voice solution's DP. It is recommended to click the button to go to the developer platform, where you can adjust the DP or add the required voice functions.
Select the product for which you want to enable WWT certification, and choose the corresponding product as the application object.
5MHz.
No, according to the national CCC product catalog, Wi-Fi modules are not within the controlled range. Additionally, mobile communication modules are required to undergo mandatory CCC certification.
Please check the ty_dev_upgrade_pre_check_cb interface in the demo. The interface in the demo by default checks the battery level, and you can disable this part.
Zero-code firmware rarely uses this module.
61.95mm*17.97mm.
When you create a product on the platform and select a module, you can view the corresponding module specification sheet and see a simple circuit reference description. If you need more detailed documents, please contact Tuya personnel or submit a ticket.
Numerical DP, fixed four byte length, positive values are prefixed with 0, negative values are reported with complement, and floating-point data is not supported for reporting. Decimals are displayed by configuring multiples on the platform.
Numerical DP, fixed at 4 bytes, positive values are reported with a zero padding of 4 bytes before them, and negative values are reported with a padding of 4 bytes.
Please refer to the following troubleshooting steps: Did you purchase a single-device plan? If yes, a single-device plan can only be used for one camera. If you purchased a multi-device plan, has the number of bound devices reached the maximum limit? After purchasing cloud storage, it is associated with the family and account used for the purchase. Please confirm whether your camera has been removed from the original home or account. If the above steps fail to resolve your issue, please provide feedback through the feedback channel.
Yes, please refer to the document: https://developer.tuya.com/en/miniapp/develop/miniapp/guide/theme/colors#3-theme-color-variable.
No deletion function available.
Submit a fast ticket according to: https://developer.tuya.com/en/miniapp/develop/ray/api/meature to apply for activation.
Ensure the device is properly connected and check the DP control code.
It may be that the current panel miniapp relies on a version of the basic library or Kit package that is not supported in the App environment currently in use. For more details, please refer to Capability Overview for comparison and troubleshooting. Capability Overview document: https://developer.tuya.com/en/miniapp/common/desc/api.
Confirm whether the API call permissions, parameters, and URL are correct, check the error information returned by the network request, and ensure that the server-side interface is stable and responds correctly.
The panel SDK does not support this feature currently, The Panel MiniApp supports it, refer to the link: https://developer.tuya.com/en/miniapp/develop/ray/api/group/functional/openGroupCreate.
If you only flash the firmware onto the module, then the module will not have authorization information. Please refer to the document: https://developer.tuya.com/en/docs/iot-device-dev/Firmware-download-and-authrotion-zigbee?id=Kam0ymclrhau7 Authorize the module before re-attempting to connect to the network.
Yes, for module selection reference link: https://solution.tuya.com/hardwareSelection.
Not supported, you can refer to the serial protocol, currently only standard commands are supported. https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-zigbee-uart-protocol?id=Kdg17v4544p37#title-26-Send%20standard%20command%20to%20group%20(0x42).
During production testing, it is necessary to ensure that the network status issued by the module is 0x00 (not connected to the network), refer to the protocol: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-zigbee-uart-protocol?id=Kdg17v4544p37#title-9-Sync%20module%E2%80%99s%20network%20status%20(0x02).
Product Model THP10-Z THC100-Z THP12-Z-V5 THP10-Z-X THP23-ZB-X Number of Sub-devices 128 (If all are low-power sub-devices, up to 32. No such application scenario currently, generally recommend using a mix of strong and weak electronic devices) 128 (If all are low-power sub-devices, up to 32. No such application scenario currently, generally recommend using a mix of strong and weak electronic devices) 200 (If all are low-power sub-devices, up to 32. No such application scenario currently. Generally recommend using a mix of strong and weak electronic devices, such as 128 strong power + 64 weak power) 128 (Zigbee max 128, Thread current recommendation max 32, Total max 128) Zigbee: 128 Bluetooth mesh: 200 Thread: current recommendation max 32 [Note: Zigbee + Thread does not exceed 128] Communication Distance between Gateway and Sub-devices Open area distance 250m+ Open area distance 250m+ Wi-Fi open area distance 267m, Zigbee open area distance 355m Open area distance 250m+ Wi-Fi open area distance 265m Zigbee open area distance 250m+.
AY: China Region AZ: United States Region EU: Europe Region.
ThingSmartBLEManager does not have a Bluetooth scan timeout callback. The default scan is 2 minutes, and scanning stops after 2 minutes. If no device is scanned within 2 minutes, developers can provide a scan timeout prompt.
Currently, the platform only supports renewal upon package expiration. If the monthly data is exhausted, there is no recharge option available. It is recommended to wait for the next month for restoration.
Up to 20 regular family members or administrators can be added.
The "ch0st0tr9" in the prompt refers to the audio channel. This issue is usually caused by the buffer not being filled with data in a timely manner. This means that the SDK failed to receive the required audio and video data, resulting in a stream failure.
If the 0x3700 command is not used to enable Bluetooth connection status notification, switching the module to Bluetooth is imperceptible and will not send any command; if the 0x3700 command is used to enable Bluetooth connection status notification, the Bluetooth connection status notification command 0x3504 will be issued after switching to Bluetooth.
DP reporting requires a cloud ACK response. If no response is received, the DP report will be recorded, but the SDK supports recording up to 8 (by default). If it exceeds 8, continuing DP reporting will result in this error. After this error occurs, the SDK will cache the DP state value and subsequently synchronize it to the cloud (non-raw DP). Generally, this issue is caused by network problems or reporting too quickly.
The authKey is filled in incorrectly. Please check the authKey.
The following interface can be used /** * @brief Get device network state * * @param[out] nw_stat Network state, see GW_WIFI_NW_STAT_E * * @return OPRT_OK on success. Others on error, please refer to tuya_error_code.h */ OPERATE_RET get_wf_gw_nw_status(OUTGW_WIFI_NW_STAT_E*nw_stat);.
The network configuration process requires the device and the APP to complete the network configuration. A fixed Wi-Fi can be connected to the phone, and the network configuration device will connect to the fixed Wi-Fi account.
The panel preview QR code generated on the developer platform is valid for 24 hours. After expiration, it cannot be used. If you need to extend the validity period, you can regenerate a new QR code.
A Wi-Fi device can only be bound to one app account, but it can be shared with others to control.
You can use TYSdk.devInfo to get device information. You can find cloud timing and webpage redirection functions in panelConfig-bic.
Also known as EZ mode, the operation is relatively simple, and the indicator light usually flashes quickly. This mode relies on communication between devices, and usually, once an existing device successfully connects to the network, other similar devices can also automatically complete the network connection.
Upload a new version and set it as a beta or go live.
The network may be unstable, please check the network connection.
Ensure Node.js version = 16.y.z, and install the latest Microsoft Visual C++ Redistributable, while disabling antivirus software.
When the device cannot interact normally with the server, this event will be reported when the device actively disconnects. It is recommended to prioritize investigating network reasons.
Access is enabled for PID. After activation, your device can support voice control. Once PID access is enabled, you need to search for skills on a third-party platform and complete skill binding before you can control your device via voice. Skill customization is enabled for OEM App. After activation, you can find your OEM skills on a third-party platform.
It is not recommended to directly replace the module on the original PID, as the firmware of the new and old modules is not compatible (the CB module firmware will affect the upgrade). For products that have already been shipped, the conventional approach is: if you need to replace the module, please copy and create a new PID for operation, and use the new PID uniformly for subsequent shipments. This ensures that firmware upgrades are not affected.
Confirm whether the corresponding dependencies are integrated in the project 1. ipc dependency: implementation 'com.thingclips.smart:thingsmart-ipcsdk' 2. ipc business package dependency: implementation 'com.thingclips.smart:thingsmart-bizbundle-camera_panel' implementation "com.thingclips.smart:thingsmart-bizbundle-camera" 3. Mini Program implementation "com.thingclips.smart:thingsmart-bizbundle-miniapp" implementation 'com.thingclips.smart:thingsmart-bizbundle-p2pkit' implementation 'com.thingclips.smart:thingsmart-bizbundle-ipckit' implementation 'com.thingclips.smart:thingsmart-bizbundle-mediakit'.
The issued integers represent: 1: Excellent 2: Good 3: Fair 4: Light Pollution 5: Moderate Pollution 6: Heavy Pollution 7: Severe Pollution In fact, the cloud is divided based on the PM2.5 value range: 1: -1000000~-1 2: -1~35 3: 35~75 4: 75~115 5: 115~150 6: 150~250 7: 250.
The device can download OTA firmware using the http protocol from data.url in topic: tylink/${deviceId}/ota/issue. For detailed process, refer to -Firmware Upgrade OTA - Tuya Developer Platform - Tuya Developer.
In the SDK'sTUYA_ALARM_TYPE_E, only some message events are listed. If there are any missing, you can check the relevant events in the [Multimedia Message Configuration] on the developer platform, then continue to add definitions toTUYA_ALARM_TYPE_E according to the order on the platform, and then report them. For example, the enumeration value 51 should correspond to the definition of package disappearance, but the SDK only defines up to 50 // high temperature alarm, you can add the definition yourself.
Using other SSL/TLS libraries such as mbedtls, libwolfssl, conflicts with the mbedtls in the SDK.
Yes, the OTA will send the OTA data in ascending order according to the channel number.
Through the status callback ipc_sdk_run_var.net_info.ipc_status_change_cb, specifically through the TUYA_IPC_STATUS_NETCFG_START status, the device needs to be aware of the network configuration. Extension: TUYA_IPC_STATUS_NETCFG_STOP: Used to notify the upper layer that the network configuration information has been obtained and the network configuration task can be closed. TUYA_IPC_STATUS_REGISTER_FAILED: Used to notify the upper layer of activation failure. TUYA_IPC_STATUS_ONLINE: Used to notify the upper layer of MQTT going online. TUYA_IPC_STATUS_ONLINE: Used to notify the upper layer of MQTT going offline.
The latest universal docking currently supports obtaining Wi-Fi information, please refer toProtocol 0x3407 instruction.
Because some high-security devices such as door locks or IPCs are by default strongly bound devices.For example, User A purchases a security camera and binds it to their account for monitoring home security. Without User A's knowledge, User B binds the camera to their own account and can view the camera's real-time footage, which is an unsafe situation. Device Binding Mode.
Ensure that the system environment meets the requirements, such as the Node.js version should be 16.y.z or above, and Microsoft Visual C++ should be the latest version possible. Antivirus software should be turned off during installation to avoid interference.
Sometimes during development, it is found that the display effect on the simulator is different from that on the real device. In such cases, it is advisable to use real device preview for testing as much as possible to ensure that the final effect meets expectations.
If not carrying audio and video, the parameters for this interface tuya_sdk_media_adapter_init(NULL, NULL) can be passed as NULL.
To obtain daylight saving time (DST), you can directly use the uni_local_time_get interface. If the local area observes DST, the time obtained will directly reflect DST. The uni_sum_time_get can also be used to obtain DST. If you have doubts about the time obtained using the uni_local_time_get interface, you can also use uni_sum_time_get to check for consistency.
Can actively call mqc_app_quit to notify the app to go offline.
It may be the router's restriction on the SDK internal ports, or it may be a network anomaly. You can first check if the network is normal, and then check if the router has restricted the TCP ports.
This is a normal phenomenon. The main reason is that the app goes offline according to the heartbeat timeout, which is asynchronous with the device end. Generally, the app will display offline in 3-5 minutes.
First, please confirm the communication protocol: 1. If using a BLE module, when the phone is directly connected to the module, the backend log will only have data reporting logs, and there will be no issuing logs. If you want to display issuing logs, you need to associate the module with the gateway. 2. If using a Wi-Fi+BLE dual-mode module, Local Area Network Scenario (phone and device connected to the same router): The device log will not record data issuing logs; Pure Bluetooth Scenario (Wi-Fi disconnected and phone connected via BLE): The device log will also not display Bluetooth control logs. 3. If using a Mesh protocol module, when not connected to the gateway, there will be neither data issuing logs nor data reporting logs. 4. If using a Zigbee module, when the gateway and phone are connected to the same router, it also constitutes a local area network, and at this time, the device log will not have data issuing logs.
You can refer to the following code implementation, which can solve the problem of two versions being the same: If you want to implement OTA upgrade, please create the firmware key for the corresponding channel on the platform and upload the corresponding firmware, then push the upgrade. On the SDK side, determine the corresponding channel in the upgrade callback interface and receive the firmware.
The module returns the current network status as "configured and connected to the router", and logs printPRODUCT OTA CHANNEL CONFIG. You need to reselect the module in the hardware development section under the platform PID, and then reconfigure the network.
/**Code Reference * @brief: RGB change to HSV * @param {IN USHORT_T r - R value, range 0~1000} * @param {IN USHORT_T g - G value, range 0~1000} * @param {IN USHORT_T b - B value, range 0~1000} * @param {OUT USHORT_T *h - H result, range 0~360} * @param {OUT USHORT_T *s - S result, range 0~1000} * @param {OUT USHORT_T *v - V result, range 0~1000} * @retval: none */ VOID vLightToolRGB2HSV(IN USHORT_T r, IN USHORT_T g, IN USHORT_T b, OUT USHORT_T *h, OUT USHORT_T *s, OUT USHORT_T *v) { FLOAT_T r_norm = r / 1000.0f; FLOAT_T g_norm = g / 1000.0f; FLOAT_T b_norm = b / 1000.0f; FLOAT_T max_val = MAX(r_norm, MAX(g_norm, b_norm)); FLOAT_T min_val = MIN(r_norm, MIN(g_norm, b_norm)); FLOAT_T delta = max_val - min_val; // Calculate V (Value) *v = (USHORT_T)(max_val * 1000.0f); // Calculate S (Saturation) if (max_val == 0) { *s = 0; } else { *s = (USHORT_T)((delta / max_val) * 1000.0f); } // Calculate H (Hue) if (delta == 0) { *h = 0; // No hue } else if (max_val == r_norm) { *h = (USHORT_T)(60.0f * ((g_norm - b_norm) / delta)); } else if (max_val == g_norm) { *h = (USHORT_T)(60.0f * (2 + (b_norm - r_norm) / delta)); } else if (max_val == b_norm) { *h = (USHORT_T)(60.0f * (4 + (r_norm - g_norm) / delta)); } // Ensure H is within 0~360 if (*h 0) { *h += 360; } }.
raw data reporting is limited to 512 bytes. If it exceeds 512 bytes, the panel will not be able to retrieve the latest data. It is recommended not to exceed 512 bytes.
Possible situations are as follows: Network speed issues, leading to untimely progress reporting or difficulty in downloading the upgrade package; Device upgrade conditions are not met, mostly due to business logic restrictions, such as not being connected to a charging pile or battery level being below the set threshold; Version number reporting timeout, device upgrade failure resulting in no new version number being reported or the device taking a long time to connect to the network after reboot;.
When the device starts, it will report MQTT messages intensively. It is recommended to delay 500ms after reporting 8 messages each time to avoid message blockage. If you need to report a large number of data points (DP), it is recommended to use a combined reporting method, which can improve efficiency and avoid cloud restrictions.
Error as shown below: TCP disconnection or exception, leading to reporting failure, prioritize checking network reasons.
There is a problem with the device network, please troubleshoot the network issue, especially the DNS configuration.
The reason is that the device to which the app sends data does not respond in time (the app waits for an ack timeout of 10s), or the app considers the network configuration to have failed. The app will send an unbind command, and the device will reset upon receiving it. Developers should focus on troubleshooting MTU-related settings.
Can work normally, the wireless switch solution uses low-power firmware, so the power consumption is low and the power supply requirements are different.
Adjust the brightness according to the direction set by the "Long Press Brightness/Color Temperature Adjustment Direction" option, Bidirectional loop - After changing to the peak value, stay for the time set by the "Long Press to Adjust Brightness/Color Temperature Cycle Change Peak Stay Time" option, then automatically reverse the brightness change (suitable for only one button for dimming); Bidirectional non-loop - After changing to the peak value, no further changes occur, and brightness changes are triggered again after releasing and pressing (suitable for only one button for dimming); Unidirectional non-loop - After changing to the peak value, no further changes occur, and no changes occur even after releasing and pressing again (suitable for two buttons, one for increasing and one for decreasing).
Scan the code to activate and bind the direct cloud connection capability. This capability requires UUID tagging support. It is recommended to contact the Tuya project manager.
Replace tuya_ipc_start_sdk with tuya_ipc_start_sdk_generic interface, as shown below:.
Bluetooth data parsing failed, please check if the UUID and key are correct.
You can directly delete the local db file and then restart the SDK.
The SDK will return these three UUIDs in the registered GATT services, no need to define them yourself.
According to the direction set by the "Short Press/Double Click to Adjust Brightness/Color Temperature Direction" option, the color temperature changes in a bidirectional loop—after adjusting to the peak value, short press/double click again, the brightness will adjust in the opposite direction to the opposite peak value; unidirectional non-loop—after changing to the peak value in the set direction, short press/double click again, the brightness will no longer change.
Non-adjustable, dependent on the accuracy and stability of the device.
The reason is that mqtt is not online yet, so tuya_ipc_get_service_time_force was called.
Supported, the default SDK will generate tuya_user.db_bak after 120s of network configuration activation.
Versions above 6.2.13 support modification, you can add env.db_backup_interval = xxx in tuya_ipc_app_start.
Product names can be configured in multiple languages under PID, as shown in the figure:.
According to the module specification, taking T3 as an example, Wi-Fi connectivity supports 802.11 b/g/n/ax. Wi-Fi 4 = 802.11n Wi-Fi 6 = 802.11ax Therefore, 802.11 B/G belongs to Wi-Fi 4 and earlier compatibility modes. T3 supports Wi-Fi 6 and is backward compatible.
You can use the 0x022 command, and after the MCU reports, the module will reply whether the report was successful, refer tothe document.
Please refer tothe document,Note: If it is MCU serial port docking, the panel sends Base64 encoded string data, and the module sends hexadecimal data to the MCU. Therefore, after the MCU receives the hex data, it should first convert it to ASCII, and then perform base64 decoding to obtain the data consistent with the protocol.
The 0xF4 field can be used. The MCU actively sends 55 AA 03 F4 00 00 F6, please refer to thedocument? Note: The latest module firmware is supported. If the corresponding data is sent and the module does not return, it proves that the module firmware does not support this field. Please upgrade to the latest firmware.
The 0x3404 command can be used, and the new version of the module firmware should be used, refer tolink.
The firmware version is represented by one byte, in the format xx.xx.xxxx, 0x50 corresponds to 01010000, so the firmware version is 1.1.0.
Please note the chip model: The ADC range of the D version chip is 0V-1.2V The ADC range of the G version chip is 0V-1.0V.
You can check if the panel is issuing the combination of two DPs. Currently, the SDK does not parse the combined data by default, and developers need to parse it themselves.
Connect TX and RX for level conversion.
The charging pile category can choose DP27 online status, and this DP point will be issued every time the panel is entered, once every 3 minutes. If other categories do not have this DP point in the standard function, a custom panel is required.
The network indicator light of the sub-device is independent of the gateway status. The socket's indicator light is off when not connected to the network and on when connected.
Class D amplifier, refer toschematic diagram.
No, you must follow the hardware design reference to solder the power-on circuit, level conversion circuit, etc.
Yes, magnetic beads are needed.
Logs of the L511 series modules need to be captured via USB and viewed using the official log software.
In the product information instruction, setting the "m" field to 1 enables the low power mode. Set the "mht" field; the longer the mht field, the lower the power consumption, with a maximum length of30000s. Power consumption can also be reduced by closing the serial port heartbeat with the 0x25 instruction.
This phenomenon proves that the module is constantly restarting, please check if the power supply circuit is normal.
Please ensure to strictly follow the steps in thedocument to install the environment; Pay special attention to whether the original SDK version is correct; Whether OneLib.a has been replaced; Whether the toolchain version is correct, otherwise it will not run correctly even if it compiles successfully.
Related to the poll cycle, the shorter the poll cycle, the higher the power consumption. Under stable connection conditions, it is generally 300-400ua at 200ms, and generally 20, 30ua at 5s. During network configuration, it can reach ma level. Please provide the firmware key to consult FAE for specifics.
Need to check if the incoming timestamp is in UTC time, i.e., time zone 0, Unix timestamp.
Need to confirm whether the differential upgrade is checked when creating the upgrade, as the 4G module only supports differential upgrades.
Firmware: keyukhs5 is 10ms, Firmware: keyyayjm is 200ms.
After the module sends data with the 04 command, the MCU should first reply with the 04 command, and then respond with the 05 command.
MQTT Keep Alive: MQTT heartbeat interval 3 minutes: Monthly data consumption 3.5 MBytes MQTT Keep Alive: MQTT heartbeat interval 2 minutes: Monthly data consumption 5.3 MBytes MQTT Keep Alive: MQTT heartbeat interval 1 minute: Monthly data consumption 10 MBytes One MQTT heartbeat consumes 258B, One bool type data report + dispatch total consumption 386B, One value type data report + dispatch total consumption 386B, One string type data report + dispatch total consumption approximately 402B; 5 value type data packet report approximately consumes 418B Activated device from boot to cloud connection completion consumes approximately 23B (related to the number of DPs, example with 28 DPs) You can refer to the above data and calculate the average daily data consumption based on the device's reporting behavior.
Ensure the IDE version is up to date and check the relevant code logic to avoid incompatible components or styles.
Please ensure the MCU reports after waking up the module, and the module replies with a successful report. In addition, please ensure the timestamp is correct and should be in the UTC timezone.
Only devices with the fast network configuration feature have this characteristic. Because the network configuration is done through broadcasting without establishing a connection, it will initially show as offline. Once you enter the panel and trigger the connection, it will display as online.
If the improper use of interrupts or hardware resources causes issues, and you are developing firmware with the TuyaOS solution, you need to troubleshoot the application code. If you are using the MCU SDK solution or a no-development solution, please contact the project manager/FAE.
The dongle needs to be set to M1-autoconn mode; then the MCU can send RF test commands.
Currently, the accessories do not support MCU SDK development. You can choose TuyaOS for development.
Currently supports up to 38KHZ, refer to the infrared driver code in the product driver example code for reference.
This print usually occurs due to poor network conditions, where data from the previous intercom accumulates and affects the current intercom. You can try switching to a better network environment.
Currently, the 6.X.X series SDK has integrated all network configuration methods, and by default, a single SDK supports multiple network configuration methods.
Currently, there is no resolution limit for the device-side SDK and app. However, if the cloud storage function is enabled, there is a resolution limit on the cloud side, and it is recommended to use mainstream resolutions.
The audio sent from the device supports two formats: PCM and G711A/U.
After the general SDK calls tuya_ipc_ss_start_event or tuya_ipc_ss_set_write_mode, this error will appear in the log, indicating that the initialization of the storage module's directory has not yet been completed. This phenomenon is mostly related to the implementation of the upper layer SD_STATUS_E tuya_ipc_sd_get_status(VOID). The SDK will internally call tuya_ipc_sd_get_status, and only after returning SD_STATUS_NORMAL can the storage directory initialization be completed. Please pay attention to the return value of this interface.
No, you can't. If you don't report audio data, the SDK will report an error, and the app will also have issues parsing the video. Without audio, you can create some silent frames filled with zeros for the ring buffer.
Manually delete the three files: tuya_user.db_bak, tuya_user.db, tuya_enckey.db, and then rerun the SDK to enter the network configuration state.
Please refer to the Tuya IoT Platform documentation for detailed guidance on this topic.
Version 6.2.6 and above supports RED, for details refer to:Release Version.
Please refer to:.
This error is due to not inserting streams into the ring buffer. You can refer to the following document for development and troubleshooting:Audio and Video Ring Buffer.
If the SDK storage solution is adopted, the video files (.media) are in a private format and can only be played back through the App, and cannot be parsed by third-party players.
gw_active err:-4352 indicates authentication failure, check if the PID, UUID, and AUTHKEY filled in the SDK are correct.
Old firmware BT general firmware, no heartbeat under low power, no heartbeat after obtaining MCU information under non-low power, new firmwarekeyyayjm, heartbeat data will always be sent.
Common P2P connection failure error codes: 3: Connection timeout, it is recommended to try reconnecting once; 23: More than 5 people shared and entered the main interface simultaneously, P2P communication was enabled; 1001: Duplicate uuid entry; More P2P SDK error codes.
The 2.x old version of the Wi-Fi universal firmware can retrievecfg_mode, while the 3.x universal firmware log does not print the module's working mode, it can only be viewed through serial data.
After the Wi-Fi information is configured, the device must have been successfully networked for the configuration to be saved when re-entering the networking page. If the device has not been networked, it will not be saved.
you can refer to the document: https://developer.tuya.com/en/docs/iot/product-troubleshooting-guide?id=K9tp15cht184d.
Yes, you need to use a 2.4G Wi-Fi signal.
Dear user, please troubleshoot in the following ways: This is a new feature of the App. Currently, it continues to cover more devices. You can provide feedback in the Energy saving and Low carbon Mini Program, Settings, My Devices, or contact the seller to provide support for the Tuya's capabilities. Some types of devices are not suitable for this feature, such as battery-operated devices and Bluetooth-connected devices (such devices are not always connected to the Internet, so energy consumption cannot be estimated). Different models of the same type of equipment may not be added to this functional section due to different functional configurations. Thank for your understanding.
Wi-Fi devices synchronize when they wake up, and Zigbee devices synchronize in a timely manner.
Currently, production testing using an app is no longer recommended.
No.
This issue only occurs on ASUS, TCL, and Lenovo models. It is a manufacturer system compatibility issue.
You need to log in to the IDE with your Tuya eveloper Platform account. The IDE does not provide the account registration function. If you have not registered a Tuya Developer Platform account, or the password is wrong, click the corresponding link shown in the following figure to redirect to the Tuya Developer Platform for troubleshooting.
To ensure product quality and user experience, please ensure your product has been thoroughly tested and has a valid report (Tuya Cloud in-depth test with a 100% pass rate or self-test pass report) before clicking "Publish Product." Once a product is successfully published, its features cannot be modified to prevent impacting online users.
Check the onDeviceRemoved callback of IThingHomeStatusListener. https://developer.tuya.com/en/docs/app-development/extension-family-ad?id=Kcy2gyhedoagz#title-22-%E5%AE%B6%E5%BA%AD%E8%AE%BE%E5%A4%87%E6%96%B0%E5%A2%9E%E5%88%A0%E9%99%A4%E7%8A%B6%E6%80%81%E7%9B%91%E5%90%AC.
Yes, similar to the OEM App process, you need to send the relevant push notification information to push@tuya.com. Tuya staff will then handle the configuration. If you wish to follow up on the configuration progress after sending the email, you can submit a work order including the sender’s email address and a screenshot of the sent message. This will help the team check the status of your request. Please include the following information in your email: App Name Android Package Name Specify the type of push channel applied for: e.g., Vivo Push Notification Application.
libthing_security_algorithm.so corresponds to the security component. You need to log in to the developer platform again to build the corresponding SDK and download the latest security component. Replace the old security component configured in the project.
First, you need to add a Boolean function point with the DP code ipc_magnification that supports both sending and reporting. This will make the magnification button appear in the lower left corner of the panel. Then, go to the Big Dipper Platform under Product Configuration → Camera Settings to set the maximum magnification level. Options include 2x, 4x, 8x, and 12x, with 12x being the maximum supported. After configuring, save the settings and reconnect the device to the network for the changes to take effect.
Possible causes include: Four-way handshake failure Incorrect router password Changed router encryption method.
Please refer to the following steps for troubleshooting: Check whether Bluetooth permissions have been enabled. Check whether location permissions have been enabled. Verify if the device has entered pairing mode. Use the system Bluetooth on your mobile phone to check whether the Bluetooth broadcast packets emitted by the device can be scanned. Additionally, please note that this callback is only triggered when unactivated devices are scanned. If the device has already been activated, this callback will not be triggered, and the system will automatically proceed with activation and connection. func didDiscoveryDevice(withDeviceInfo deviceInfo: ThingBLEAdvModel) {} So please check the scanned device information in the log printed on Xcode to see if it is in the activated state.
The module is not supported under the current product category. For example, CB series modules cannot be used in home appliance products. The module has been discontinued, or there is a minimum order quantity requirement, making it unavailable for selection. It is incompatible with the current development solution. For instance, the CBLC5 module does not have a serial port and therefore does not support universal integration development. Therefore, it is recommended to select modules that are available on the platform.
No, the module does not have the ability to automatically recover from network issues. That is, after the MCU sends a reset command, it will not automatically reconnect to the gateway after three minutes.
The unprotected and keepalive solutions for Wi-Fi door locks implement different logic for temporary passwords. In both cases, the local MCU verifies the password based on the validity period. With the unprotected solution, you can retrieve the full password information using a command. With the keepalive solution, the password is retrieved once each time the device comes online. When the device is online, the set password is directly sent and verified by the MCU. Expired passwords that were not retrieved can be viewed in the app's history.
You need to check the module's firmware and upgrade it to version 3.x or later.
Characteristics of Tuya's dual-direct-connect solution: 1. Support for platform-agnostic dual systems and one-tap pairing: Dual-direct-connect-enabled devices can be quickly added to Tuya App and a third-party platform, and can link with devices in the Tuya and third-party platform ecosystems. A Tuya App can implement all product functions, while other apps can implement only standard functions. 2. Voice control: Devices can be controlled using a Tuya App or by using voice control through Apple Siri, Amazon Alexa, or Google Nest. 3. Remote control: Users can perform remote control or status sync for devices from Tuya IoT PaaS without the need for a home hub. Some third-party platforms do not support remote device control.
Yes. HomeKit products use hardware protocols to access Tuya IoT PaaS. Other voice platforms, such as Amazon Alexa, Google Assistant, and Samsung SmartThings use cloud accounts to access Tuya IoT PaaS. You can control products using HomeKit and these voice platforms at the same time. In general, Tuya users use HomeKit products in the following scenarios: HomeKit products are connected to the Home App, Tuya App, or an OEM App. Users can use HomePod or Siri to control a HomeKit product connected to the Home App with voice commands or use a third-party smart speaker, such as Amazon Alexa, Google Assistant, or Samsung SmartThings, to control the HomeKit product that has enabled the voice platform-based control function through a Tuya App.
Enabling this feature on the platform will eliminate this prompt.
Currently, its primary function is to assist with positioning.
On the CF chip platform, with the latest OS 3.x firmware, the "BLE GAP EVENT DISCONNECT (Ox208)" message indicates a poor signal. You can try replacing the antenna and retesting the network pairing.
Smart configuration mode is no longer available.
Status Description Note Developing For a smart product in the developing status, you can modify its data point (DP), app panel, cloud configuration, and module information anytime. Also, you can scan the QR code with Tuya App, and experience the product control with your mobile phone. For a smart product in this status, you must check its crucial product document and information, including product name, product ID (PID), selected module, firmware key, DP, app panel, and hardware information. In trial production For a smart product in this status, you can purchase trial production module, and proceed with optional mass production. If the functions are inconsistent or need to be modified during test, you can return to the previous developing status. 1.If your account does not have the permission to purchase, the purchase module button will not appear. 2.The "in trial production" status can be rolled back to the "developing" status. In mass production In this status, development of the smart product has been completed. You can choose some value-added services. For example, device log storage, or applying for Powered by Tuya label. 1.The "in mass production" status cannot be rolled back to the "in trial production" status, in order that functional modification does not affect the released products. 2.You can only modify module information and module member information in the developing status and in trial production status, rather than in mass production status.
Tuya provides different solutions based on the customer type: If you are an electronic lock supplier with embedded development capabilities, Tuya provides you with Wi-Fi, Zigbee, NB-IoT, and Bluetooth LE communication modules, smart lock apps (Tuya, SmartLife, or OEM apps), Tuya IoT services, SaaS solutions, and application systems. If you are a traditional lock supplier without embedded development capabilities, Tuya can recommend professional and mature solution resources to meet your IoT access requirements and help you implement intelligence in one stop. If you want to enter the smart lock market quickly, Tuya has cooperated with over 100 factories and can provide first-class, one-stop smart lock solutions with professional ODM or OEM smart locks. If you have such requirements, contact Tuya personnel.
If you want to purchase Tuya modules for development, you need to log in and register on Tuya Developer Platform: https://iot.tuya.com/to create the products you need to develop. You can purchase testing modules online in the third step 'hardware debugging' page. Click "Buy Module-Submit Order" to complete the payment online. If you meet other problems during development, you can submit problems on the page. Tuya has a professional technical support team to respond to your problems efficiently.
Network Configuration: The remote control does not require network configuration via the app, but the controlled device (light) needs to be configured first before pairing with the remote control. Pairing: Before the first pairing, the controlled device must complete network configuration in the Tuya App. The controlled device will automatically enter pairing mode once powered on/off. If no pairing occurs within 60 seconds, the pairing will end. During this 60-second window, long-press the group (1/2/3/4) button for more than 5 seconds until the light blinks twice, indicating successful pairing and allowing control of the light. If the light does not blink after long-pressing for 10 seconds, please long-press the pairing button again to pair. Each controlled device light can be repeatedly added to different groups, with a maximum of 5 remote controls controlling each light. When a sixth remote control is paired, it will overwrite the information of the first remote control. If multiple lighting devices are in pairing mode, the remote control will pair with multiple devices simultaneously. Once the remote control and light are paired, a remote control device will automatically be generated in the Tuya app. Unpairing: Long-press the combination of group (1/2/3/4) and brightness- button for more than 5 seconds to unpair the light. When the unpairing signal is successfully sent, the indicator light on the remote control will flash rapidly 3 times for notification. Note: If you want to use this remote control in another home, you must delete the remote control device in the Tuya app; otherwise, it cannot be paired with devices in other homes.
Please confirm whether the Pulsar Client environment is consistent with the device environment, and whether the OEM app and App SDK of the device's network configuration have been linked to the cloud project. If you use Tuya or SmartLife App to configure the network, please confirm whether you have scanned the code and authorized to the cloud project. If you have confirmed that you can submit a work order, provide the device ID and clientid, and the Tuya technicians will help you verify and deal with it.
Dear users, Thank you very much for your suggestions, we will feedback them to the relevant departments for evaluation. Of course, because the flashing time of the product is determined by the manufacturer, you can also send your very good suggestion to them, so that they also realize that the product or product's control page still has huge room for improvement. Thanks again for your suggestions, we will make our best efforts to provide users with a better experience! Thank you for your understanding and support, and I wish you a happy life!
Requirements: The product must use Tuya technical solutions, have connected to Tuya Cloud, and have the Alexa voice-based control function enabled. Products must belong to Electrical （curtains excluded）, Lighting, Diffusers, IPCs( video doorbells excluded) , Robot Vacuum, Fans, Air Purifiers, Humidifiers, Dehumidifiers, Thermostats, Heaters, Door locks, Air conditioners. For other categories, you can consult Tuya staff. Alexa skills in certified regions are live and support App-to-App Account Linking. The page for which WWA certification logo marking is applied must exist, that is, the page has an Amazon Standard Identification Number (ASIN). Precautions: On the product sales page on Amazon, consumers must be clearly notified of the app name and Alexa skill name, for example, SmartLife or Tuya used by the product and how to connect an app or Alexa skill to the device. Before successful application, your product sales page cannot use the official WWA certification logo or words, which Amazon will check. The sample that you send to Tuya must be the same as the product sold on the page on Amazon for which WWA certification logo marking is applied. Information filled in the application form must be real, valid, and the same as that described on the product sales page on Amazon. Your product and store must be properly operated on Amazon, meet laws and regulations in the product sales area, never have been blocked by Amazon, and not have a low assessment score or a large number of complaints. If the labeling is unsuccessful or other consequences are caused by not meeting the application conditions or not following the precautions, you must bear it yourself. Tuya will not refund and will not bear any related responsibilities. If you need to certify products such as air purifiers, IPCs with batteries, etc., that require replacement of consumables, you need to provide the Amazon online sales link for the consumables in advance.
The Tuya developer platform supports plug-and-play Wi-Fi switches with a maximum of four gangs. If the MCU solution is used, the number of gangs is determined by hardware resources and number of set DPs. Currently, voice speakers can control switches of up to six gangs.
The Amazon Alexa Access service allows your products to access Amazon Alexa instead of specific Alexa hardware, such as Echo Show. To enable the Amazon Alexa Access service, log in to the Tuya developer platform and click Value-added Service. Locate the Amazon Alexa Access service and click Subscribe. Click Click to view the functions and language list supported by the speaker to view supported functions and languages.
Platform Central Hub requirements iOS App Android App Device Type Wi-Fi Thread Tuya Wi-Fi products do not require a hub Thread products require a Tuya Matter gateway App version 4.7.0 and above iOS system V16.1 and above App version 4.7.0 and above Android system V6.0 and above Lights, sockets, switches, sensors, gateways support support iOS App 4.8.0 and above support Android 4.7.0 and above SmartLife Wi-Fi products do not require a hub Thread products require a Tuya Matter gateway App version 4.7.0 and above iOS system V16.1 and above App version 4.7.0 and above Android system V6.0 and above Lights, sockets, switches, sensors, gateways support only support Thread protocol, iOS does not support Apple Home Apple TV/HomePod system version 16.1 and above / Lights, sockets, switches, sensors, home appliances, gateways support support Google Home Google Nest speakers not supported 2.58.24.1-dogfood and above Lights, sockets, switches, sensors, home appliances, gateways support support Amazon Alexa Echo speakers not supported update to the latest version only support Wi-Fi protocol lights, sockets, switches lights, sockets, switches support.
The infrared gateway uses the "Wi-Fi + infrared" method to enable infrared appliances to achieve network control even if they are disconnected. It can easily integrate all appliances in the home, and can provide remote control, timing tasks, third-party AI voice control, and other functions. You can operate the functions you need through SmartLife or OEM Apps.
RN App is an App for panel SDK development and debugging, which needs to be downloaded separately. Download address: https://smartapp.tuya.com/typaneldev.
You can select the door lock category on the developer platform, select a custom solution to create a product, and then obtain and match the SDK development kit information on the product's hardware development page. In addition, you can refer to the link below for more instructions: 1. Overview of the door lock solution https://docs.tuya.com/en/iot/smart-product-solution/product-solution-lock/doorlock- solution-overview/doorlock-solutions?id=K9g743hx88g9l 2. Wi-Fi door lock MCU docking protocol https://docs.tuya.com/en/iot/smart-product-solution/product-solution-lock/ product-solution-lock-wifi/door-lock-mcu-docking?id=K950t0p1l51k2 3. Bluetooth door lock SDK docking guide https://docs.tuya.com/en/iot/smart-product-solution/ product-solution-lock/product-solution-lock-Bluetooth LE/123?id=K965xj2hde4od 4. Zigbee door lock MCU docking protocol https://docs.tuya.com/en/iot/smart-product-solution/ product-solution-lock/product-solution-lock-zigbee/zigbee-door-lock-universal-docking-agreement?id=K9bjcnh616mg5.
The following takes the Alexa App and SmartLife App as examples. 1. Pairing logic for dual-direct-connect solutions You can configure the device pairing reminder to fading, blinking, power-on, or power-off. a: The fading mode lasts for 6s and then the indicator is steady on. b: The blinking mode lasts for 3 minutes and then the indicator is steady on. The pairing window opens for 10 minutes. The pairing broadcast is closed after the pairing window expires. If Alexa or SmartLife is successfully paired, the other App can continue to pair. After the pairing window expires, the pairing broadcast is closed, and pairing is no longer supported. The pairing broadcast is closed after both Apps are successfully paired. 2. Logic for pairing reset When an App is removed, only the connection of that App (Alexa or SmartLife) is disconnected. If the device is locally reset (turned on and off for N times), the pairing is reset for both Apps. Recovery upon misoperation of resetting: Power on and off the device within 5s to 10 minutes after resetting. Both Apps are paired to the original network. After 10 minutes, the connection with the original network is recovered. 3. Pairing logic for Alexa App Paring: The pairing window is available for the Alexa speaker to search for and add devices. When a device is successfully added, the device blinks once as a reminder. If Alexa App has been paired with and used to control SmartLife previously, the indicator blinks once at the original status after successful pairing. If the pairing fails, the indicator status data is the default data configured on the platform, and the indicator blinks in the specified color. Cancel pairing: remove the device from Alexa App a. If the device is also paired with the SmartLife App, the device gives no reminder. The Alexa speaker can be paired with the device within the pairing window of 10 minutes. b. If the device is not paired with the SmartLife App, the device displays a pairing reminder (fading for 6s). T.
Zigbee's SMB solution is used by clients with smart home lighting OEM App.
Confirm that the lock is connected to the network. Check whether the App used is Tuya or an OEM App. Check whether the scene linkage configured in the App is correct. Check whether the condition is "The door is opened" or "Fingerprint/Code/Card". If the preceding settings are correct, trigger the lock based on the triggering conditions set in the scene. After a new unlocking record is displayed in the App, check the specific triggering condition in the record. If the triggering condition value is correct, contact the Tuya project manager or submit a service ticket to change the trigger mode of the corresponding DP to level triggering.
It depends on the controlled products. For example, the separate control of individual sockets of a power strip is available in the Tuya or SmartLife App, and it is not a custom skill. The separate control of a camera and a lamp is a custom Skill.
The code-free UI creation templates and some app panel templates for Tuya or SmartLife do not support cloud timing. To use this feature, use an app panel template for Tuya or SmartLife that supports cloud timing or customize a panel.
When you develop an OEM App using the SmartLife App SDK, you can perform the following steps to implement the auto-pairing of Bluetooth devices as the all-in-one App does: 1. When the app is started, or when the homepage is pulled down for refreshing, the App initiates a two-minute Bluetooth scan to connect to Bluetooth LE devices that are paired but offline and displays a pop-up window, showing devices pending pairing. 2. When you tap a Bluetooth LE device to enter its control panel, the App initiates a scan and connects only to this device if the device is not connected. callback method: https://developer.tuya.com/en/docs/app-development/ble?id=Ka5vcxzbglphd#title-30-%E8%BF%9E%E6%8E%A5%E7%A6%BB%E7%BA%BF%E4%B8%AD%E7%9A%84%E8%AE%BE%E5%A4%87.
Due to the upgrade of the bottom navigation bar [Smart]，for the SmartLife OEM App with template 3.34.5 or above, [Smart] will be changed to [Scene], while the function keeps the same. The new [Smart] module will be opened in the future. For more details： 1. The bottom navigation bar name is changed from Smart to Scene. 2. For the apps whose navigation bar name [Smart] has been modified , the tab name will remain unchanged. If you want to keep the unified user experience as before，you can modify it： Edit the tab name: Path：IoT Platform-[App]-[Multi-language]-[App Language]-[App Language Pack], Select the corresponding App, fill in the entry code: ty_home_nav_scene, modify the corresponding tab name, save and release (use the template 3.18 or later, can be dynamically updated);.
Hello, the regular procedure for using the SmartLife SDK is: 1, SDK initialization OK; 2, Account login OK; 3, Call the getHomeList method to get the Home list; 4, You must call the getHomeData method to get the Home detail information, because only after calling the getHomeData method, the attributes in the home instance object will have data; 5, After the above four steps are correct, perform your operation; If you use the scene function (especially if you are using the scene business package), you still need to get the scene data before using it. [self.home getHomeDataWithSuccess:^(ThingSmartHomeModel *homeModel) { // Get scene data in advance [self loadSceneList]; } failure:^(NSError *error) { }]; - (void)loadSceneList { // If the one-touch execution and automation list are empty, call the following method in advance in your code: // If the following code is not written, when using the scene business package, there may be a situation where create scene--add task--choose existing smart scene--data is empty idThingSmartSceneBizProtocol impl = [[ThingSmartBizCore sharedInstance] serviceOfProtocol:@protocol(ThingSmartSceneBizProtocol)]; [impl getSceneListWithHomeId:[SRHome getCurrentHome].homeId withSuccess:^(NSArrayThingSmartSceneModel * * _Nonnull scenes) { } failure:^(NSError * _Nonnull error) { }]; }.
Make sure that the AppKey, AppSecret, and security image are consistent with those used on the Tuya Developer Platform. Any mismatch will cause the authentication to be failed. For more information, see Fast Integration with SmartLife App SDK for Android.
Hello, please follow the steps to troubleshoot 1. After updating the SDK and UI business package version, if the assets configuration file and resources such as values have not been updated, you can update them according to the documentation. https://github.com/tuya/tuya-ui-bizbundle-android-config-values/tree/main/ 2. If you are integrating a custom panel developed with the panel SDK, and it cannot be opened on the generic App (SmartLife) as well, then you need to check the panel logic yourself.
Because the current App has not purchased the official version, it can be eliminated after purchasing the official version, please click Buy Now.
Currently, all new SDK-based apps on the platform are built based on SmartLife App SDK (v4.0 and later) that requires an annual subscription. Legacy free SDKs (earlier than v4.0) are not supported in the app development. The Trial edition is available for free, but it supports only up to 20 registered end users in total. Note: If you have created apps with the SmartLife App SDK earlier than August 26, 2022, these SDKs can still be used for free. You can also purchase an annual subscription and upgrade to the SDK version v4.0 or later. If you do not require this upgrade, do not click the Upgrade button next to your SDK-based app, as shown in the following figure. For more information about the differences between the Trial and Official editions of the SmartLife App SDK, visit: Differences in features between Trial and Official editions.
After the paid SDK versions are released, if no significant faults or security compliance issues occur, Tuya will not release fixes to the legacy versions for free. Routine iterations will focus on the paid versions.
SmartLife: Connect to smart devices across brands and categories and work as a smart home control hub. Smart Home Lighting: Support smart home lighting UI design and scenario services and implement interconnections in the Tuya ecosystem. Smart Workbench: Suitable for presales packaging and promotion for smart products. Smart Audio：Smart Audio is built for audio equipment, providing a more complete service package for professional selection and professional selection of work. Smart travel: Provide a new experience of smart travel, and carry travel SaaS to realize full-link detection and management of vehicles.
According to the regionCode property in the TuyaSmartUser object in the SmartLife App SDK Android： iOS ：.
Tuya is no longer maintaining this Github repository. If encountered with new issues, assistance or fixes will not be provided. In the process of using TuyaSmartActivator, if you have created a SmartLife SDK App on the Tuya developer platform and commercialized it, you will need to pay an annual fee for the SmartLife App SDK. (Annual Fee Introduction) If you are aware of and agree to the above two points and still wish to use the TuyaSmartActivator SDK, you need to provide your GitHub account, and we will whitelist it for you. After that, you can use it.
Refer to the developer documentation: https://developer.tuya.com/en/docs/app-development/ipccamera?id=Ka8qhzhuq9anj#title-17-%E8%AE%BE%E7%BD%AE%E9%A1%B5%E9%9D%A2%E9%85%8D%E7%BD%AE Value-added service title: cameraSetting_valueAddedSectionHeaderCfgItem Value-added service: cameraSetting_valueAddedCfgItem Set the following in the application's Application:.
No, it will not. The upgrade will not affect the app in service.
If you do not renew the initial subscription after expiration, the following problems will be caused: You will not be allowed to check the key information, SHA256 certificate, custom domain name settings, and other important data for the SDK-based app on the Tuya Developer Platform. You will not be allowed to build and download the latest version of SmartLife App SDK. You can go to Value-Added Services and renew the official edition as needed. Based on your ongoing and long-term collaboration with Tuya, Tuya can waive certain basic fees, for example, those for O&M and traffic to your app. Your renewal cost can thus be reduced. Then, after renewal, your app can still run as expected and user experience will not be affected. If you confirm the potential cessation of your broader collaboration with Tuya, you might incur charges for ongoing traffic and basic O&M costs brought by the app. Alternatively, Tuya might explore more solutions with you to meet your supplier needs in the future and gradually phase out the respective app services.
The specific Xcode print error logs are as follows: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSCFString stringByReplacingCharactersInRange:withString:]: nil argument' *** First throw call stack: (0x181cdfc800x199505ee40x1833871bc0x10511a5100x1051027400x1051010680x18199f0940x1819a00940x1819428580x18194fb940x18195039c0x1dd0f0dd40x1dd0f093c) libc++abi: terminating with uncaught exception of type NSException terminating with uncaught exception of type NSException *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSCFString stringByReplacingCharactersInRange:withString:]: nil argument' (lldb) If your project is a Widget project, you need to refer to [Configure Widget Project] , and configure your project as: [ThingSmartSDK sharedInstance].appGroupId = APP_GROUP_NAME;.
No, you cannot. To launch the SDK-based app for commercial use, perform the following steps: Go to the Tuya Developer Platform and purchase the official edition of SmartLife App SDK. For more information, see Subscription. Rebuild and downloadthe SDK packages of the official edition, and replace the SDK packages in your project with the downloaded ones. For more information, see Build and download the SDK for iOS and Build and download the SDK for Android. Repackage and launch the app.
No，cannot be integrated together.
Controlling devices without network configuration through a local area network is possible, but most devices such as Wi-Fi and Bluetooth require an external network setup, otherwise, they cannot be cloud-activated.
Before running the SDK demo, you need to adjust the Gradle and JDK versions in Android studio to the versions shown in the attachment images and then run it.
SmartLife App SDK supports the development of apps for tablets. However, the existing UI BizBundles involve UI logic that does not adapt to tablets yet, and thus do not support the development of apps for tablets at present.
It's recommend you can check if the IPC SDK dependency is also version 5.0, the vertical category SDK version needs to be consistent with the SmartLife SDK version.
v3.x, v4.x, and v5.x respectively represent a series of SmartLife App SDK versions. SmartLife App SDK is upgraded from v3.x and v4.x to v5.x. Compared with SDKs v3.x and v4.x, SDK v5.x additionally supports the following features: Pairing and controlling devices over Matter. The development on top of Smart MiniApp. The entry to pairing with QR code. Known issues of SDKs v3.x and v4.x have been fixed. For more information, see Changelog for SmartLife App SDK for iOS and Changelog for SmartLife App SDK for Android.
Hello, currently the SmartLife SDK only supports armeabi-v7a and arm64-v8a architecture models, and does not support x86_64. You can use a phone with the corresponding architecture for testing. You can use the following command to query the current model architecture, and then use a supported architecture model for support. adb shell getprop ro.product.cpu.abi.
Problem cause: The account does not exist and the account has not registered for the skill App . Solution: Confirm the phone number or email of the current account in the App's account information, verify it and bind again. In the App , click "Me", click the top right corner settings, click "Account and Security", and confirm account information here.
Problem cause: In this page, the App name is displayed based on the correct account information, so it is mainly due to the password being incorrect. Solution: It is suggested to check if the account password is correct in the application. If the account currently does not have a password, it can be set first before binding it to the skill.
Problem cause: The data display logic in the device panel of a third-party app depends on the app itself. If the product's functionality can be controlled through voice commands, it indicates that the product's voice capabilities are functioning properly. Solution: This problem may be resolved by suggesting users contact the third-party app developer for assistance with how their app displays synchronized data from voice control capabilities of smart home devices.
Tuya App 4.6.0 and above support Beacon 2.0 devices.
Visit https://cli.im/, and enter the URL to generate the QR code. Then, use the Tuya App to scan the QR code to activate the device. Note: Ensure that the network connection of the device is stable.
a. PWM-RGB indicates that three I/O pins on the module separately generate one channel of PWM signals to control the current and on/off of the RGB lamp. b. PWM-IIC indicates that two I/O pins on the module separately transmit SCL clock signals and SDA data signals to the LED control ICs to control the brightness and color temperature of the RGB lamp. The ICs use different protocols. The I2C SoC solutions on the Tuya developer platform support only SM726EB and SM2135. If you select another control IC, use custom firmware.
You can add a sub-device to SS190 by using one of the following three methods: 1. Say "configure network" to the speaker. After the speaker responds with "Are you sure you want to configure the network", say "Yes". The speaker enters the sub-device pairing mode. Follow the instructions to add the sub-device. 2. Open the Tuya App and go to the Zigbee settings page to add the sub-device. 3. Press and hold the mute button and the volume up button for more than 5 seconds to add the sub-device.
Ensure a good network connection. Make sure to use iOS system version V16.3 or above, or Android system version V6.0 or above. Use the Tuya App version V4.9.0 or above.
Method 1: Open Tuya App -- Top right "+" sign -- Scan -- Enter Matter device setup code Method 2: Pair the device with Tuya App, enter the device details interface, and share Matter.
We recommend: 1.Home door lock Bluetooth solution: Enter the lock panel in the Tuya or SmartLife app, add other members, and add sharing accounts for other members. 2.Home door lock PRO Bluetooth solution: Enter the door lock panel on the App side to add sharing members.
Devices that can be networked within the APP SDK/integrated small program SDK provided by Tuya/SmartLife/Integrated Tuya can be controlled by APIs provided from the cloud.
This feature is currently only available on the “Tuya” App. You can share your device by clicking on its details page and using the "Share over Matter" feature, as shown below.
Yes, App version: v4.7.0 and above.
In the app, you can customize "automation" scenes, such as automatically turning on the hallway light and air purifier when unlocking with fingerprint. Please note: Zigbee and Bluetooth smart door locks require connection to a gateway, while Wi-Fi smart door locks do not need to connect to a gateway.
Scenario 1: You cannot open the App by tapping the notification after its process is killed. If a third-party channel is used, the activity of the pop-up window must be named SpecialPushActivity.Take U-Push as an example: SpecialPushActivity is inherited from UmengNotifyClickActivity, and the complete bundle name path is com.activity.SpecialPushActivity. Scenario 2: You cannot open the App by tapping the notification when the App runs in the background. When the App is running, it uses custom push (Tuya push). Therefore, by default, the App will not be opened. In this case, the developer needs to call the callback function of Tuya push to resolve this issue.
Hello. If you are uploading the SDK panel package for the first time, this is not supported, you can carry out real machine debugging in the RN debugging app, if there is no problem, you can release it directly. If you have uploaded the SDK panel before, you can select the development panel, set the test whitelist after uploading the new panel package, and then use the network with the whitelist account to add devices, so that you can use the real machine to debug the uploaded panel package.
Hello, our app supports usage on tablets (the latest version of the app requires iOS ≥ V12.2 or Android ≥ V6.0). Related:Does SmartLife App support tablet landscape mode?
Message Reporting Billing Rules I. Billing Basis Billing is based on the daily reported dp (function point) data volume of a single device, counted separately for each device. II. Scope of Application Products created on or after January 1, 2025, 00:00:00, will have their device message reporting volume included in the billing statistics. III. Free Quota and Excess Definition Each device enjoys a daily free message reporting quota of 3500 messages, which is counted based on the dp data reported by the device. The portion of dp data reported by a single device that exceeds 3500 messages in a day is counted as excess messages for billing. If the device messages exceed the quota, you can apply for a one-time (only once) free excess message gift on the message reporting statistics page, ensuring you have enough time to optimize your firmware and perform firmware OTA upgrades to reduce the number of messages reported by the device. IV. Excess Message Purchase and Deduction Rules The standard for purchasing excess messages is 1.6 yuan / million messages, and the purchased quota can be used across all devices corresponding to the account's PID. The excess messages generated by devices will be uniformly deducted from the excess message quota purchased by the account; once the quota is exhausted, a new purchase is required. V. Regional Calculation and Data Query Excess messages from different regions (such as China, the United States, etc.) are combined for calculation. The excess messages generated by all regional devices on the day will be deducted from the account's available excess message quota 1-2 days later, with specific data subject to the actual display on the platform page.
This log appears when the MCU sends a reset command (0x04, 0x05, 0xF4), and this record will be generated.
Referring to the image, when the "Repeat" option is checked, the temporary password can only be used if it's within the validity period and meets the repetition time requirement. Otherwise, the MCU only checks whether it's within the validity period.
Method 1: Operation in the App that needs to be bound (using SmartLife App as an example here) 1. Download the Alexa App and register/login to your Amazon account. 2. Open the App that needs to be bound, go to Home - Me - Third-party Voice Services - Alexa. 3. Click "Sign in With Amazon" and the Alexa App will be launched. Click "LINK" to complete the binding. Method 2: Operation in the Alexa App 1. Download the App that needs to be bound and register/login to your account. 2. Open the Alexa App and click "More" in the lower right corner. 3. Click "Skills & Games" and then click the search button in the upper right corner. Enter the name of the skill you need to bind, using SmartLife as an example here. 4. Click the SmartLife skill to enter the skill details page (ENABLE TO USE), click "Agree and link", and return to the Alexa App. 5. Click "CLOSE" and then click "DISCOVER DEVICES" to complete the binding. Common commands Control the device via voice commands, now you can control your smart device with Echo. You can control your device (such as your bedroom light) with the following commands: Alexa, turn on/off bedroom light. (Turn on/off the light) Alexa, set bedroom light to 50 percent. (Set the light to any brightness) Alexa, brighten/dim bedroom light. (Increase/weaken the brightness of the light) Alexa, set bedroom light to green. (Adjust the color of the light).
There are several conditions to determine the country and region where the user is located: 1. Based on the SIM card on the mobile phone, if a domestic card is used, China can be selected. 2. If the device used is a tablet, the system region is read. If China is required, the region must be switched.
Please see the agreement document for details：https://developer.tuya.com/en/docs/iot/door-lock-mcu-protocol?id=Kcmktkdx4hovi.
No. The RST pin is used to reset the module's software. Long press time of reset indicates a 3s press of any light control button.
Please ensure that you select the correct country/region. Currently, only three countries/regions are available based on the server location: Europe, America and China. Determine the device's home country based on the country code.
When receiving the module, it is suggested that, before start coding, you run the provided module debugging assistant, and connect the Zigbee module in MCU simulation mode to check if the module can work properly. Meanwhile, you can get familiar with the protocol interaction process, which will help you to proceed with development debugging. In MCU simulation mode, the debugging assistant simulates the MCU to automatically respond to the module with the correct protocol data. After you configure the network through the mobile phone, you can test DP data reporting and sending. The procedure of operating the assistant and module network configuration is as follows. Before the operation, you need to learn about the operation instruction of the Tuya module debugging assistant. For beginners, see Module Debugging Assistant Instruction. 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 Zigbee 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, you will see the initial protocol interaction between the module and the host. Note: If the module does not send data after power on, check if the peripheral circuit of the module is correct. Click Configure Module, and the module enters network configuration mode. Configure network on the app according to the status. See the app operation instruction for network configuration operation. Note: Before configuring a sub-device, you need to configure the network of the gateway on the Tuya app or SmartLife app. Then, the Zigbee sub-device can be added. For more information, see the documentation Zigbee Network Configuration Description.
Troubleshoot: Check if the sub-device is powered off. Check if the sub-device is too far away from the gateway. Check for the walls and metal objects between the sub-device and the gateway. Check for significant interference from the 2.4 GHz Wi-Fi network near the sub-device or gateway. Check for interference caused by channel overlap between the Zigbee network and the 2.4 GHz router. How to identify channel overlap: Use a Wi-Fi analyzer app to view nearby 2.4 GHz Wi-Fi networks and their channels. Then, compare them with the Zigbee channels shown on the SmartLife app gateway for overlap.
Efficient and convenient: Tuya OEM App service enables you to quickly have a self-branded app. You do not need to set up a technical team or seek an outsourcing vendor, but only need to log in to Tuya IoT platform and configure online. Flexible and customizable: Tuya OEM App service provides powerful functions for flexible configuration. You can customize the brand attributes such as app name, logo, and background color. Function upgrade: OEM App functions will be continuously enriched depending on continuous update of the common-version apps (Tuya and SmartLife). One-stop service: Tuya OEM App service provides a full process from app creation, to function configuration,offering an ultimate experience. Low cost: the price is far lower than the standard service price in the market. You do not need to worry about the uncontrollable development expense.
Yes. Zigbee single fire switch can drive thyristor. Under hardware debugging, set the relay type to thyristor.
Yes, the Wi Fi metering socket supports power-off memory settings. When creating a product, click "Modify Firmware" on the "Hardware Development" page to make the settings.
When creating a development free socket product, you can modify the firmware on the "Hardware Development" page of the product to set the power on status of the socket, and set the power off memory function.
When the BL0942 is used in the category of sockets/power strips/circuit breakers, the ratio of voltage division resistance to current sampling resistance refers to the official reference schematic of BL0942. Voltage sampling division ratio is 390K*5: 0.51K, and the current sampling resistance is 1 milliohm. When the BL0942 is applied in the category of metering circuit breakers, the voltage sampling division ratio is 390K*5: 0.51K. The current sampling uses a current transformer with a ratio of 2000:1, matched with a 1 ohm resistor.
The specific Xcode output log is as follows: *** Terminating app due to uncaught exception 'ThingSmartSDKException', reason: 'Domain config file not found!' terminating with uncaught exception of type NSException t_cdc.tcfg does not exist. Your project does not include a domain configuration file. To use a custom domain name, please go to the Thing IoT Development Platform and download a domain configuration file. read local domain config : (null) *** Terminating app due to uncaught exception 'ThingSmartSDKException', reason: 'Domain config file not found!’ Reason: The SmartLife 5.0+ SDK was not correctly integrated. Solution: 1. If you have already integrated an earlier version of the SDK, after updating to the 5.0 SDK, please delete the t_s.bmp safety image file in the project, and obtain the new 5.0 version AppKey, secretKey from the Tuya IoT Development Platform. 2. Refer to Integrating SDK in step 5 and step 6: Unzip ios_core_sdk.tar.gz to obtain the following two important file information: Build: Holds your app-specific security SDK, it's as important as the app key information, please keep it safe, prevent resource leaks or public exposure. ThingSmartCryption.podspec: Used for reference and integration with the 5.0 SDK. (Recommended) Keep these two files at the same level as the podfile for easy referencing in subsequent operations.
Related to firmware key. Keyukhs5 will not be retransmitted, Keyyayjm 2.3.5 version will be retransmitted, Keyysck3 will be retransmitted, and the universal firmware of BF6H module also supports retransmission.
If all involved channels are correctly configured, SmartLife and ODM apps have the same stability. If not, their service quality may vary.
YouTube: https://youtu.be/b14c4GFThOE The Data page provides Overview, Devices Analytic, App Analytic, Faults Analytic, Feedbacks, and Device Conditions Analytic. Regardless of OEM, or SDK, or Custom App data support viewing.
It will resend it every 5 seconds until the upgrade times out and fails.
Turning on the time notification service is equivalent to message subscription, and new time is only sent when the cloud is synchronized; directly sending commands to obtain weather data is generally done after connecting to the cloud. Protocol reference: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-wifi-time?id=Kd2fzooztuuqt.
You can call this function, bk_err_t bk_uart_deinit(uart_id_tid), uart_id_tid fills in the serial port ID, this deinitialization function needs to be placed after the mf_init production test function.
It may be caused by a problem with the IO configuration or a failure to mount the external Flash.
No, the network status can be checked by checking the status of the 0x03 command. The 0x2B command is generally used to obtain the network status of the actual network configuration.
No, it can only be initiated by one end at a time, otherwise it will cause congestion. When viewing the video on the APP and there is a doorbell call, you can make a "cat's eye busy" alarm mechanism, which will provide a better user experience.
We currently support general MCU integration and LinkSDK docking: General MCU integration is suitable for new products LinkSDK is for those products that have already been certified and cannot change their hardware and modules but still need to support Tuya products Current module solutions include: WiFi+BLE dual-mode modules, recommended: CBU-IPEX (reserved IPEX antenna seat for external antenna) CBU-IPEX module specification sheet 4G+Bluetooth combo modules, recommended for: China L511C-Y6E, Europe/Southeast Asia L511E-Y6E, North America L511A/MA510-GL-00.
External antenna Zigbee modules are ZSU-IPEX, TYZS15S, TYZS3, TYZS5.
NM1, NM1-CT, NM1-GL The serial port level of the three modules is 1.8V, and the serial port level of the NX1-CT is 3V, so the voltage domain of the application system is 3.3V, and the NX1-CT does not need a level conversion circuit .
The high level of NM1 series is 1.8V, and the TTL level of NX1 series module is 3V.
Module model: NM1 conforms to 3GPP R13 Module model: NM1-GL/NM1-CT/NX1 conforms to 3GPP R14.
NB modules include NM1,NM1-CT,NM1-L,NX1-CT, you can be connected through serial port protocol.
You can view GNSS modules: https://developer.tuya.com/en/docs/iot/gnss-modules?id=Kaiuymmd906yg.
Yes, such as: WBR3D, WBR2D, WBR1D, WBR1D-IPEX modules. Details can be found in the module details introduction under the Wi-Fi & Bluetooth dual-mode module category in the document center.
Select the module and configure the firmware on the Tuya platform. When placing an order, if the quantity is greater than or equal to 100, Tuya will burn the firmware for the module and send it directly to you. Users do not need to burn it themselves. If the order quantity is less than 100, you need to purchase the burning tool and burn it yourself. View tutorials: https://support.tuya.com/en/help/_detail/Kdvkkr15m4f9v, https://support.tuya.com/en/help/_detail/Kcw9sivkaaki0.
Hello, according to the error log analysis, the system cannot find the com.thingclips.smart.stat.StatPipeLine class. This is usually caused by not updating the configuration files in the assets directory synchronously after updating the SDK and business package versions. Please follow the steps below to solve it: Please visit the official GitHub repository to obtain the latest configuration files: https://github.com/tuya/tuya-ui-bizbundle-android-config-values/tree/main/assets Replace the latest configuration JSON file obtained into the assets directory of your project Make sure your business package version matches the SDK version Recompile and run the project.
If there is a power outage or other abnormality during the upgrade process and the MCU does not reply to the upgrade, it will prompt that the upgrade has failed. Secondly, after the module sends the firmware, it will directly prompt that the upgrade is successful, and the app will not have a pop-up window indicating upgrade failure. So, if the upgrade fails midway, it will prompt, and if the upgrade fails due to an exception at the end, it will not prompt failure. Upgrading the terminal failed. Our recommended practice is not to refresh the firmware. Simply power on and send the previous version number to continue the upgrade (upgrading the terminal network requires checking the MCU side).
https://www.wi-fi.org/product-finder.
Android Documentation: https://developer.tuya.com/en/docs/app-development/devicemanage?id=Ka6ki8r2rfiuu Read the schema in the DeviceBean device information data type iOS Documentation: https://developer.tuya.com/en/docs/app-development/device?id=Ka5cgmmjr46cp Read the dps in the ThingSmartDeviceModel data model, schemaArray.
The plugplay function needs to be enabled in the "Advanced Features" definition on the Tuya platform. Once enabled, the option "Skip, switch to Bluetooth connection" will be displayed during the module network configuration when placing an order for burning. If the order is placed before enabling, it will not be supported.
When the MCU responds to product information, it needs to configure which version of the upgrade protocol to use; create extended firmware on the platform, starting the channel from 11, and when the MCU reports information, it also needs to report the version of the extended firmware; when there is an upgrade task, the module will inform the MCU which channel's firmware needs to be upgraded.
You can set the starting position and the length to be intercepted in the basic configuration.
After setting up the hardware, you need to configure the working mode on the MCU side to module self-processing and fill in the corresponding indicator light pins. Refer to the protocol: https://developer.tuya.com/en/docs/mcu-standard-protocol/ltecat1-base?id=Kd3qbdrt42uqv#title-7-Report%20network%20status%20(0x03).
To ensure compatibility with inaccurate time, the dynamic password has a tolerance of 5 minutes forward and backward, so the maximum validity is 10 minutes.
Yes, it is possible. Set the network configuration mode to:PARING_MODE_WIFI_AP. Set the connection mode to:TUYA_IPC_LINK_WIFI | TUYA_IPC_LINK_WIRE | TUYA_IPC_LINK_BT. Refer to thislink for specific configuration methods.
This issue is usually caused by the lack of a network card reset mechanism. According to the design specifications of the sweeper SDK, when the device fails to successfully connect to the network within 5 minutes, the system will not automatically perform a router disconnection and reconnection operation. It is recommended that the business layer independently implement the network card reset function, and it is usually suggested to develop a network monitoring script to detect the network connection status in real-time. When a network disconnection exceeding 5 minutes is detected, automatically execute a network card reset and reinitiate the network connection.
When the device reports the upgrade progress to 100%, the cloud will close the timeout timer. However, if the upgrade fails and the new version number is not reported, the app will not be able to detect the timeout status. Therefore, it is recommended: When the device reports progress, even if the upgrade is complete, only report 99% to avoid triggering the cloud timer closure; If the upgrade fails, the device can quickly exit the upgrade interface after restarting to avoid status retention.
Maximum number of connections: Supports up to 200 SigMesh/BeaconMesh devices, or real-time control of 16 single-point devices.
Yes, the echo reference signal is close to the speaker side, requiring re-collection at the PA output end.
After the SDK connects to the router, it will activate the device in the cloud. If it fails to activate successfully 10 times, it will proactively call TUYA_IPC_Reset_System_CB.
RST reset is required during burning. When designing hardware independently, a reset circuit needs to be added, refer to the schematic diagram.
Currently, Tuya does not directly support modules with the 485 protocol. You can choose the general MUC docking method, and the MCU side can perform serial port conversion by itself.
Does not support reconnection,long connection maintains the link, but the action of linking requires external triggering, usually the MCU needs to send the 0xA5 command to let the device reconnect to the gateway.
Please refer to the following code: uint16_t tal_util_crc16(uint8_t* buf, uint8_t size, uint16_t* p_crc) { uint16_t poly[2] = {0, 0xa001}; //0x8005 ---- 0xa001 uint16_t crc; int i, j; crc = (p_crc == NULL) ? 0xFFFF: *p_crc; for (j=size; j0; j--) { uint8_t ds = *buf++; for (i=0; i8; i++) { crc = (crc 1) ^ poly[(crc ^ ds) & 1]; ds = ds 1; } } return crc; }.
Please ensure that the correct version of Python (3.8.10), Git, and the required IDE, such as Keil, are installed. After installation, add them to the system environment variables, and they will take effect after restarting the computer.
If the module is frequently sending heartbeat packets at 1-second intervals, it indicates that the module has not received a response from the MCU; please check if the response content is correct and if the level conversion circuit is functioning properly.
The same DP value with the same timestamp cannot be reported multiple times, and record-type reporting must wait for the previous response before reporting the next one.
Please confirm whether it is the Chinese version of the module; if it is the overseas version of the module, after inserting the overseas version SIM card, you need to inform the module of the correct APN when replying to product information, otherwise it may lead to incorrect connection. It is also recommended to use the SIM card sold by Tuya.
In the network state of the no-code development PIR product, the off-network command will only be received after triggering wake-up, and it will start to enter the indicator light flashing state to begin network configuration; after the MCU SDK APP is unbound, it enters the unnetworked state, and the MCU must send a reset command to re-enter the network configuration state.
Problem description: When the mobile phone language system is in English, the device name is displayed in Chinese. Solution steps: 1. Log in to the IoT platform https://iot.tuya.com/ 2. In Product Development -- Product Configuration -- Multilingual, click Settings to modify the corresponding copy content. 3. If multiple national languages are supported, you can also choose to export for copy addition, and import after configuration is complete. 4. After the operation is completed, if the panel display has not been updated, please clear the app cache or re-network, and then test and verify after clearing the app cache here.
You can proceed as follows: Open the App, click "Me Home Management Select the family to operate Permission Management Transfer Home Ownership" in the lower right corner. This operation is only available if your account is the current owner of the home (i.e., the home creator). If you are the home owner but cannot find the "Transfer Home Ownership" option, please ensure that other members have already been added to the family.
Advantages: 1. Tuya Beacon is mainly applied in chips. It features ultra-low cost, which is much lower than that of standard Bluetooth. 2. Tuya Beacon provides a lightweight smart solution for products with low security requirements. 3. Tuya Beacon-enabled devices can be remotely controlled using a mobile phone through a direct connection or a gateway, featuring flexible networking capabilities. 4. Tuya Beacon enables local scene linkage and small- and medium-scale group control. 5. Tuya Beacon-enabled devices are not prone to 2.4 GHz communication interference. Disadvantages: 1. Tuya Beacon has lower communication capability than standard Bluetooth. It features short-range communication, weak wall-penetrating ability, and weak concurrent message processing capability. It supports only the minimalist communication protocol, which may cause network congestion. 2. OTA is not supported. 3. The chip resources and supported product complexity are limited. 4. Certification can be implemented only by reducing the power, which is risky.
No, the current production test is to detect the router, which is named as tuya_mdev_test.
The device panel is the control interface displayed on the user's mobile app. At the same time, the panel will display the interactive UI of product functions. Devices can be controlled through the device panel, such as adjusting light brightness, setting light colors, etc.
Tuya serial ports come in two types, green board 3M, blue board 2M Download Model: TYUSB_UART 📎 Green board CP2102 3M drive USB UARTTS.rar Blue 2M high-speed serial port board Serial port model: TS-NUSBUART-00 📎 Blue board ch340ckqd 2M drive USB UARTTS.rar.
If you encounter this prompt, it is usually because the accounts of the inviter and invitee belong to different data centers. Due to data protection policies, accounts from different countries or regions may belong to distinct data centers, preventing cross-region invitation operations. General Case: Verify Account Country/Region Both parties should log into the app, navigate to the Account Settings page, and check the Country/Region information selected during registration. If they differ, you may need to re-register with accounts from the same country/region and attempt the invitation again. Special Case: Specific Countries/Regions If the account belongs to regions such as Vietnam, Laos, Cambodia, Thailand, Myanmar, Malaysia, Singapore, Indonesia, Philippines, Brunei, Timor-Leste, Papua New Guinea, Solomon Islands, Hong Kong (China), Macau (China), Taipei (China), due to recent data storage service upgrades, the binding might still fail even if the country/region is the same. We recommend following these steps: For home owners: Successively go to “Me” - “Home Management” - select your home - click “Add Member” - select “Copy”. Send the generated text containing the invitation code to the invited person. For invited members: Go to “Me” - “Home Management” - click “Join a home” - enter the invitation code - carefully read and confirm all the necessary notes regarding switching data centers - complete the process. Note: The invited account must be registered with a mobile phone/email. If a third-party quick account or a third-party account bound to a mobile phone/email is used, an independent mobile phone/email account must be registered before operation. If the problem persists, you can provide feedback through the feedback channel in the App.
"Zigbee Certification Transfer" process:1. Submit information and quotation on the platform; 2. Make payment; 3. Sample testing; 4. Submit certification; 5. Complete certification. "Zigbee Certification Transfer" cycle:Certified products require 1-2 months of testing, and the certificate transfer is expected to take about 1 week. "Zigbee Certification Transfer" cost:Quoted based on actual conditions, it is recommended to contact the corresponding business personnel for consultation.
Most of it has been released, and it is subject to the hardware development page of product development.
This situation is typically related to the product's own settings. Please first take a screenshot of the error message in the app and then contact the seller for assistance in resolving the issue.
Illegal Client Error Code: ILLEGAL_CLIENT_ID 1. Confirm whether the security component, Appkey, AppSecret, and package name are consistent with the IoT platform SDK configuration 2. Whether the SHA256 has been added for the SDK application 3. Whether the signature information is configured in the app module's build.gradle 4. If an illegal client error occurs when downloading from Google Play, check if the re-signature feature is enabled. If enabled, the SHA256 key generated by Google needs to be configured on the Tuya IoT Development Platform 5. After configuring SHA256, you need to wait for a while for it to take effect If upgrading from version 3.x or 4.x to 5.x, note that after configuring the security component, delete the original security image in the assets folder of the project.
Report a resolution similar to the protocol, for example, if the actual cat eye resolution is 800 * 480, you can choose 640x480. Protocol reference:https://developer.tuya.com/en/docs/iot/WBRL_cateye_protocol?id=Kd5lman9g4py4#title-15-Initiate%20transmission%20(0x63).
Check if the driver version of Te-link is correct; Te-link is not connected to the module, power on and check the status of the red, green, blue, and yellow lights: 1. The data cable only provides power without data function, all four lights of Te-link will be constantly on. 2. If only the blue or green light of Te-link is on, it means the Te-link firmware is the latest and not compatible with the cloud module upper computer. 3. For a normally compatible Te-link driver with the cloud module, after connecting to the computer USB, all four lights will turn off, and the blue light will flash during the burning process. *Kind reminder, due to poor compatibility of Te-link and slow burning speed; to improve development and debugging efficiency, it is recommended to purchase an EVK burner.
Dear user, we are sorry for your inconvenience. If you do so: When there are more than two “Smart Cameras” in the list, click the "Smart" option below, and the "Multi-Video Preview" feature will Appear in the "Smart" Page. After you click to enter, you can view the video multiple cameras in one screen. Our App currently supports up to 16-way preview (you can set 4 channels, 9 channels and 16 channels in your needs), camera devices that come through sharing from others cannot support this feature. Note: Currently, the tablet version of the App does not support the multi-channel preview function, so stay tuned. If you are viewing the real-time monitoring screen of multiple cameras in one page, but one or more cameras cannot see the monitoring screen (when you click on a single camera, the monitoring screen can be displayed normally), this is because you are viewing the real-time monitoring screen of multiple cameras at the same time. And this feature needs more network resources, this phenomenon will occur if your network is not stable. For more troubleshooting methods, please click to view: Failed to build encrypted channel/video stream has stopped working？.
Log in to the Tuya Developer Platform and click on the "Tech Support" menu at the top of the page to access the Service Center homepage (https://service.console.tuya.com/). You can follow the page instructions to submit your issue and also manage and track your submitted tickets here. Ticket Type Description: Quick Ticket: An entry point for resolving specific types of issues. Providing the correct information allows for processing without interaction. It is recommended to first check if there is a Quick Ticket category corresponding to your issue. General Ticket: An entry point for submitting tickets for general issues. If there is no matching Quick Ticket category, you are advised to submit a General Ticket and select the correct issue category. Tips: Submitting the correct technical ticket issue category can expedite the resolution of your problem. Arbitrarily filling in ticket categories may impact processing speed. Tuya technical ticket processing hours: 24/7.
OEM App basic version contains various functions of smart device control, just a simple configuration of 10 minutes to build your branded smart App, to help you get a quick start in the business track. Key Value: Brand-specific: 0 code to quickly configure the App, App User Rating and Review helps to build up a good user reputation. Safe and stable: OEM App provides safe and stable App control experience for hundreds of millions of consumers worldwide for many years. Continuous update: Continuously update the various functions of the App, and continuously add new categories of products and accessible protocols, and you can update the App without limits. OEM App Advanced Version adds Custom App Tools on top of OEM App Basic Version to create a differentiated brand image. It also adds Siri access, Adapt to tablet and other advanced smart control functions to enhance user experience; App page advertising space provides App user-oriented marketing to help . Key Value: Enhanced competitiveness: Custom configuration of App pages, functional components and visual styles for different business scenarios to enhance differentiated competitiveness. Experience upgrade: Adapt to Tablet, Siri Access, and Display Category by Territory help to enhance user experience. Value realization: App page advertising space provides in-app operation and marketing capabilities to accelerate App user value realization.
OEM App can help you quickly get branded IoT App built with zero-code, design unique UI and functions quickly, continuously improve brand awareness and business growth with data-driven operations. Key product advantages: Brand-specific: Quickly configure the branded App logo, pages and functions, smart user rating helps to accumulate App reputation; Constantly updated: Constantly iterate on various functions of the App, and continue to add new product categories and protocols; Stable global service: Provides safe and stable App control experience for hundreds of millions of consumers around the world; Value realization: Provide user-oriented marketing capabilities to accelerate App value realization. OEM App provides two versions, basic version and advanced version, different versions are suitable for customers with different needs.
Zigbee Certification Transfer is a new Certifcation program that makes it easier for companies to join the Zigbee Alliance ecosystem of Certified Products.Tuya, as a Zigbee Alliance Participant, can transfer Certified Products to you. You can then easily and affordably certify the products under your company name, as long as the products have not undergone any functional changes from the Tuya-provided Certifed Products.
Bluetooth BQB Listing provides technical services that allow you to quickly obtain Bluetooth certification for Bluetooth products based on Tuya's Bluetooth-certified modules without testing.The advantages are as follows: 1. Tuya is authorized to use QDID acquisition directly 2. Short certification cycle, 3–4 days 3. No additional testing fee.
If the components have not reached a deliverable state, you may need to wait until the components are deliverable before making a purchase. During this period, you can follow the product status updates.
Process for handling issues: First, confirm if the same issue occurs when viewing the real-time footage. a. If the same issue occurs, it is a device malfunction. b. If the same issue does not occur, please submit an IoT platform technical ticket for further investigation, and provide the video of abnormal cloud storage playback, the time point of abnormal playback and the device ID.
If you use an account outside China to log in to the Tuya IoT Platform in China, use a Wi-Fi network that can access the server outside China.
If the Wi-Fi device fails to connect successfully, you can troubleshoot by following these steps: Before starting the connection process, carefully read the product manual to ensure that the app you are using matches the recommended app in the manual. Ensure that the device is powered on and in the correct setup mode. Confirm that the device is using the 2.4GHz network frequency for connection and verify the accuracy of the Wi-Fi password. To rule out router issues, try using another smartphone to create a Wi-Fi hotspot (iPhone users should enable maximum compatibility) for the connection attempt. If the connection is successful, check the router settings; if it still fails, it may involve hardware faults or operational issues, and you should consult the seller. Network Band Splitting: (For most of Routers) How to configure separate Wi-Fi SSIDs for 2.4 GHz and 5 GHz bands?
Whether additional development costs are required for connecting the Tuya module to the Xiaozhi speaker depends on the specific type of your product and the required functions. For most standard categories, automatic activation has been achieved, and basic functions are provided for free. If your product is a non-standard category, it may require Tuya staff to handle the activation, which could involve additional costs.
The 3.x SDK did not impose restrictions, but the 3.x SDK is no longer provided.
Reporting plan: (Only report when only the gateway exists) S1 After power on/network configuration, immediately report 100, which means full power, then try to collect and report as soon as possible (Step 2) S2 After power on/network configuration, report real data after 20 minutes, (randomly collect and report immediately after avoiding transmission) S3 After power on/network configuration, (after steps 1 & 2) during normal use, smooth the interval between two reports (every 4 hours) to a certain range (do not exceed 20%) S4 Report every four hours, reporting the value of the last collection (in wake-up state, not in transmission state), not the percentage value corresponding to the voltage at the moment of reporting S5 After the device's minimum working voltage - such as 20% (or below) - shorten the battery power reporting interval to 1 hour.
Refer to the schematic diagram, the connection circuit is the same as USIM.
It is recommended to use a consistent module syntax within the same project.
The number of scenarios supported by different public version panels varies, usually 8, and each scenario supports 8 color changes. If you need more scenes, you can open the lighting scene library.
When checking the platform configuration, it is necessary to select channels 11-19. Channel 10 is occupied by the module, so upgrade notifications and OTA data cannot be received.
Within 1 month before the expiration of the service, Tuya developer platform will send you a renewal notification email to remind you to renew in time. If you miss the renewal time point and fail to complete the next year's renewal in time, it will not have any impact on the newly added developer platform WeChat Mini Program terminal users during the service validity period. If you do not complete the renewal operation within one month before the expiration of the service, our customer service staff will personally confirm with you whether you will no longer renew the service by phone or email. After confirming with you that you will no longer renew, we will adjust the configuration of your Tuya account and downgrade it from the original "commercial version" to the "experimental version". For the developer platform WeChat Mini Program application under the trial version account, the number of new user registrations will be limited to 10.
Currently, the smart lighting module uses Tuya protocols.
The number of supported sub-devices varies depending on the gateway type. For more information, visit: https://support.tuya.com/en/help/_detail/Kat9nrd8np2lc.
No. You need to configure the mesh category. Or ask the product manager to configure a special remote control panel.
The billing and charging function can be developed on the MCU firmware side according to the defined functions. If you need to activate the cloud billing function, please contact Tuya Business personnel for coordination.
The types of electricity statistics for different schemes may vary. For conventional products, the electricity quantity is reported as full quantity and supports minux statistics, and there may be differences in the displayed statistics after the electricity consumption increases. For some specific schemes, such as Wi-Fi SoC, it may be of incremental DP type and require reporting of open sum type statistics.
If the product was newly created after May 8, 2024, you can configure the cloud storage service purchase feature yourself on the developer platform by following these steps: Developer Platform - Products - Development - Find the corresponding product and enter the product development page - Under "Function Definition," locate "IPC Cloud Storage" in the advanced features section and turn it on. If the product was created before May 8, 2024, it cannot be enabled manually. You can contact your project manager or business personnel. If you are unable to reach them, you can contact the technical support for assistance.
The lighting scene library is an advanced capability in light source products, which synchronizes the newly added scenes in the cloud. Therefore, it is generally not recommended to classify scenes on the device side, otherwise new scenarios may not be distinguishable.
No, PID information will only be broadcasted when the distribution network is in operation.
Zigbee gateway can be replaced with a new gateway using an old gateway. When replacing, the old gateway needs to be powered off first. After the power off replacement, it cannot exist in the current Zigbee network again, and the old gateway can still be used again.
Hello, the uploaded SDK development panel package does not support downloading. You can view the uploaded package information through the history, as shown in the attached image.
The following table describes the local listening ports of the gateway. Listening port No. Description 6668 Communication between the gateway and app through a LAN 6669 Pairing in AP mode of the gateway 6608 RPC communication of the gateway 6681 LAN linkage of the gateway (1) 6682 LAN linkage of the gateway (2) 12476 Airkiss pairing of the gateway 40000–41000 MQTT communication 12121 Gateway Zigbee application (1) 12122 Gateway Zigbee application (2) 5540 Matter device local multicast port The following table describes the ports used on the cloud. Port No. Description 443 TLS communication between the gateway and cloud 1443 TLS communication between the gateway and cloud during OTA upgrade (1) 2443 TLS communication between the gateway and cloud during OTA upgrade (2) 10443 Communication between the gateway and DNS server during OTA upgrade 8883 MQTT communication between the app and cloud 8886 MQTT communication between the gateway and cloud.
Because the module adapts to the baud rate, it will send 32 bytes of 00 data. The MCU can confirm the baud rate by replying to the sent data at a baud rate of 115200 or 9600.
Download not supported.
The serial port used for firmware burning generally refers to USB to UART. The principle of serial port tools is simple, and there are many manufacturers and models with varying quality. Other models of serial ports have not been tested one by one. It is known that some models of serial ports may fail to burn firmware due to insufficient 3.3V power supply. The image below shows several known cases of other serial ports causing firmware burning failures due to insufficient 3.3V power supply. The burning authorization process requires a reset signal, and other serial ports generally do not have RST function. Manual reset operation is complex and has a low success rate. To avoid wasting too much time in the burning authorization process, shorten the development process, and improve debugging efficiency, we recommend that you purchase the Tuya 2M high-speed serial port board Tuya serial port board with 1A high current LDO, equipped with automatic reset download function. The serial port RST can be connected to the CEN or RST of the module to achieve automatic reset.
If the Cat Toilet performs automatic cleaning unusually frequently (such as every 3 minutes), it might be due to drum deformation causing the Hall sensor to incorrectly recognize the magnet signal. It is recommended to follow these troubleshooting steps: Check the drum condition: Inspect the drum for deformation due to external pressure, high temperature, or blockage by foreign objects; Clean the sensor: Wipe the surface of the Hall sensor and magnet with a dry cloth to ensure there is no dust or cat litter obstructing them; Calibrate the sensor: If the drum is not deformed, attempt to recalibrate the sensor in the app (supported by some models); Contact after-sales service: If it is confirmed that the drum is deformed, contact customer service for assistance.
If your Cat Toilet stops rotating or working normally, it may be due to dust blocking theinfrared sensoron the bottom, triggering theanti - pinch protection. Follow these steps: Use a soft cloth to clean the infrared sensor area on the bottom; Ensure no debris is obstructing the sensor; Restart the Cat Toilet after cleaning to restore normal operation.
It is possible that the drum has become deformed, causing the Hall sensor to fail in detecting the magnet signal properly. We recommend thoroughly inspecting the drum's appearance to check for any signs of deformation. If the deformation of the drum is confirmed, promptly contact product support to replace the drum components. This will allow the sensor to recognize the magnet correctly, enabling the cat toilet to resume normal operation.
Create a light source product to view the agreement.
If the network connection is disconnected, the module will automatically try to reconnect. In order to avoid network conflicts, there is a backoff mechanism. The reconnection time is a random value with a maximum of 5 minutes.
There are four possible reasons for this prompt: 1. The MQTT communication protocol supported by the current App is lower than the communication protocol of the hardware, which can be solved by upgrading the App version 2. The LAN communication protocol supported by the current App is lower than the communication protocol of the hardware, which can be solved by upgrading the App version 3. The panel UI package does not support the current version (device.rnFind), which can be judged by capturing the package and viewing the rnFind field of the device entity. When rnFind is false, feedback to RN classmates and release the panel in time 4. The panel did not find a suitable view controller to display (device.uiType).
There is no pickerFontColor attribute in the Popup.datePicker component. You can set the picker text color by modifying the cellFontColor attribute.
The specific logic of "network configuration" is: short press the corresponding button of the remote control 5 times in a row to enter the network configuration state. The short press interval time is required to be greater than 1s and less than 3s.
registry.nlark.com is a Taobao historical mirror, which has been removed from the shelves. You need to replace registry.nlark.com with https://registry.npmmirror.com.
For the stable operation of the server, the current flow limiting rules for the data reported by the device are: reporting more than 1200 data in 10 minutes will trigger the flow limiting, that is, the average should not exceed 2 per second. Multiple DP combined reports count as 1 record. It is recommended to use the combined reporting method if multiple DP data need to be reported at the same time. Please refer to: Group reporting instructions and examples.
Make sure the device has been added to the room, and then you can also query the room device list to see the device. Get the device list in the room: ThingHomeSdk.getDataInstance().getRoomDeviceList(roomid) Get the corresponding device room information: ThingHomeSdk.getDataInstance().getDeviceRoomBean(devid).
When the working mode selected in the 0x02 command is module self-processing, the network configuration indicator light connected to the module is used for judgment. Refer to the protocol When the working mode selected in the 0x02 command is MCU cooperative processing, the MCU can obtain the current network status through two functions: 1. mcu_get_wifi_work_state, this function corresponds to the 0x03 command in the serial port protocol. When the network status of the device changes, the 0x03 command will be used to actively send the network status. 2. mcu_get_wifi_connect_status, this function corresponds to the 0x2B command in the serial port protocol. The MCU actively sends instructions to obtain the connection status of the current module. After sending the status, the MCU can react through different statuses, such as: if the status is connected to the cloud, the green light can be on, and the red light of the connection status indicates the non-network configuration status.
You need to refer to the module specification and fill in the silkscreen number of the general IO pin. Special pins (log pins, etc.) are not available. Take WBR3 as an example: the indicator light and reset button can be filled in 2, 3, 4, 12, 16, 17, etc. Module Datasheet: https://developer.tuya.com/en/docs/iot/wbr3-module-datasheet?id=K9dujs2k5nriy.
Please check whether your AppKey, AppSecret and security components are configured correctly and whether they are consistent with the information on the Tuya developer platform. If any of them do not match, the verification will fail. If you have just upgraded from version 3.x to version 5.x, make sure that the security images in the assets file have been deleted.
Country code adaptation is the newly launched Wi-Fi country code 2.0, which optimizes the process of selecting the country code (channel code) when confirming production data in the old version of firmware, that is, you do not need to select the channel when ordering a module. It is only supported by module firmware versions greater than 3.x.x. You can submit a ticket for consultation on the specific version.
Hello, the copied product B RN SDK panel does not support continued editing. Due to technical solution adjustments, we have officially removed the RN SDK panel creation development portal. The relevant announcement has been sent through platform emails and SMS. The RN SDK panel of product A can continue to be edited and iterated, but subsequent related documents will also stop maintenance and updates. It is recommended that you change the development plan in time and replace it with the mini program development plan. Click here for the mini program development plan guide.
Yes, country code adaptation occurs before network configuration. After OTA, the country code will be adapted when the network is configured again.
Hello, Zigbee packet transmission supports a maximum of 120 bytes for receiving data and a maximum of 246 bytes for sending data.
This is the gateway's on-demand connection strategy. If you exit from the App panel or there is no data reporting from the device side for a while, the gateway will disconnect from the sub-devices. If the device side needs to report data, it can actively request to establish a connection with the gateway by calling the tuya_ble_adv_data_connecting_request_set(UINT8_Ton_off)interface. Once in the connected state, data can be reported normally. /** * @brief Function for process the internal state of tuya sdk, application should call this in disconnect handler. * @param [in]on_off: 0-off ,1 - on. * @note *. * */ tuya_ble_status_ttuya_ble_adv_data_connecting_request_set(UINT8_Ton_off); Fun Fact: Since Bluetooth sub-devices cannot determine whether they are online or offline, in some cases, even if the gateway is offline (such as when the network is disconnected), as long as the Bluetooth is connected to the gateway, the return value of the Bluetooth device's synchronous reporting interface is also successful. In such cases, as long as the gateway's offline status is not caused by a power outage, waiting for the gateway to come back online can synchronize the data reported by the sub-devices to the cloud (the gateway has a certain data caching capability).
Currently, this feature has compatibility limitations on some tablet devices, as detailed below: iOS devices (such as iPad): The "Smart" module is currently not supported for display. Android tablets: Landscape mode: The "Smart" module is currently not supported for display. Portrait mode: The module can be displayed normally; it is recommended to rotate the screen and try again.
Hello, if the app running on Android 12 is compiled based on SDK 31 and above, the three permissions of BLUETOOTH_SCAN, BLUETOOTH_CONNECT, and BLUETOOTH_ADVERTISE are required when using Bluetooth. Please add them and try again. uses-permission android:name="android.permission.BLUETOOTH_SCAN" / uses-permission android:name="android.permission.BLUETOOTH_ADVERTISE" / uses-permission android:name="android.permission.BLUETOOTH_CONNECT" /.
Usually, an ammeter is connected in series to the circuit and a debugging assistant is used to simulate the power consumption of the MCU test module under different working conditions. Debugging assistant reference connection: https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-debug?id=Kd024qnpg4da0.
If the product is exported to different countries, different versions of production materials need to be made and corresponding Wi-Fi channel codes need to be selected.
It may cause network configuration failure or compliance issues, please see Choose Wi-Fi Channel Code.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please confirm whether the device supports Apple HomeKit. Supported devices will have the HomeKit logo printed on the packaging. You can also check in the app under "Me" - "HomeKit Information" to see if there are any supported devices. If controlling through Siri using the one-touch execution doesn't work,please confirm whether your voice command is correctly recognized by Siri, and whether the command recognized by Siri is exactly the same as the command you set when you use "Add to Siri" in the App; After Siri has successfully recognized your instructions, has Siri opened our App on the Siri page? If not, please make sure that your instructions are exactly the same as the command you set when you use "Add to Siri" in the App; If Siri responds successfully, but your device does not respond to the operation, it means that your device should be a Bluetooth or Zigbee device. You need to connect it to the corresponding gateway and make sure that the gateway is online. Currently only iOS systems with iOS 12.0 and above can use the "Add to Siri" function, and then the device can be controlled through Siri. Can I use Siri and Apple HomePod to control smart products? Why I can't add Tap-to-Run / Automation to Siri? After I add a tap-to-run scene to Siri and delete it, I add another tap-to-run scene with the same name to Siri. Why does the system inform me that the name is in use?
Dear user, we are sorry for your inconvenience. The current shortcut function of the system with iOS 12.0 and above can realize the control of intelligent products. The operation modes are as follows： Please confirm whether the device supports Apple HomeKit. Supported devices will have the HomeKit logo printed on the packaging. You can also check in the app under "Me" - "HomeKit Information" to see if there are any supported devices. Click “Add to Siri” on the bottom right corner of the “Scene” page to enter the “Siri Shortcut” page. 【If Siri-related information is not displayed, make sure you have created a one-touch execution and then restart the app.】 You can add any “Tap-to-Run” to Siri On the “Add to Siri” page, you can set custom phrase for Siri to trigger your “Tap-to-Run”（This function is only available for iOS system over 12.0 version） Currently only iOS 12.0 and above can use the "Add to Siri" function. Why I can't add Tap-to-Run / Automation to Siri? The devices cannot be controlled with the iPhone via Siri and Apple HomePod? After I add a tap-to-run scene to Siri and delete it, I add another tap-to-run scene with the same name to Siri. Why does the system inform me that the name is in use?
There are several purchase entry points for C-end users: a. Device panel b. "Smart" section (if the smart section is already enabled) c. Message center - SMS and phone notification entry.
The highest temperature: w.thigh and the lowest temperature: w.tlow do not support real-time acquisition, only forecast data can be obtained, and forecast data requires carrying the w.date.n field for access. Some weather fields are only supported in mainland China and not abroad, for details refer toWeather Service description.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please first check if you have scheduled / automated / countdown tasks set for the device, if any, suggest you delete the tasks instead. Check whether the device is shared with others, which may be caused by the operation of others. If there is a power outage in the home, some devices will be turned on automatically after the power is completely turned off and turned on again. If there is no such situation, please restore the device to factory settings in the App. In this way, the device will remove and delete all device-related information from the App's device list, then you can re-configure the device. There is a problem with the firmware of this device, Please contact the device seller or manufacturer to have the latest firmware sent to you and to perform the upgrade. The power supply voltage of the device is unstable, which causes the networking module of the device reset frequently. Please check whether the power supply of the device is stable. If the device still turns on/off by itself after excluding all the above conditions, it should be a problem with the hardware of the device. Please contact the after-sales person of the device for after-sales.
asm: Assembly code file, contains low-level assembly instructions used for direct hardware manipulation. axf: ARM Executable File Format, mainly used for executable files in embedded systems. bin: Binary file, usually a compiled executable file or firmware. map: Memory map file, shows the distribution of various parts of the compiled program in memory. QIO: Production firmware: includes bootloader, user area firmware, factory production test functions, etc., can be directly used for factory generation and testing, and can be used as a product after testing is completed. UA: User area firmware: only contains normal functional firmware, excluding BootLoader and other functions. UG: Upgrade firmware: used to replace user area firmware.
Check whether the firmware key was created with the current account. If not, the account does not have permission to view the firmware key.
The privacy policy is dynamically effective and does not require re-listing.
You need to enable TUYA_BLE_FEATURE_ATTACH_OTA_ENABLE.
The MCU can actively send this command to the module, allowing the module to request time information from the gateway.https://developer.tuya.com/en/docs/mcu-standard-protocol/mcusdk-zigbee-uart-protocol?id=Kdg17v4544p37#title-48-%E6%97%B6%E9%97%B4%E5%90%8C%E6%AD%A5%EF%BC%880x24%EF%BC%89.
Yes, the hardware ID for each type of unlocking can be set from 0 to 0xFE respectively.
Your device is controlled through a mobile app that connects to our cloud servers, allowing you to operate it anytime, anywhere. Once the device is successfully connected to the network, and you have confirmed that the network environment is stable, you can use the mobile app to control the device remotely when you're away from home. The app will display the device's connection status, so please ensure it is online. If the device indicates "offline," it will be unable to be controlled. Please note that Bluetooth devices require a Bluetooth gateway for remote operation.
If you created a trial version of the App, it is only valid for 30 days, please purchase the official version, if you bought the official version, it is valid for 1 year, after the expiration, please renew.
The password length of the Wi-Fi is up to 64 digits（EZ-Mode）and 64 digits（AP-Mode）.Special characters in the password are not supported. As long as the Wi-Fi password is utf-8 encoded characters are supported, non-utf-8 encoded characters are not supported.
End users can trigger a name change by saying "Give you a name called xxx" through voice control or customize the wake-up nickname for the speaker on the nickname modification page in the app, adding their desired wake-up word. However, since the nickname has not been specifically trained with audio algorithms, the wake-up effect may be relatively poor. After defining the nickname function, the default wake-up word " Tuya Voice Service " will still be retained, but end users can also wake up the speaker with the nickname. Currently, only Linux and Android solutions support the nickname modification function. Additionally, for business users who require more flexible wake-up functionality with guaranteed effectiveness, a custom wake-up word business process is necessary.
Dear user. If you do so: Please confirm whether you are the owner of the device, not the shared device, and whether you are the owner or administrator of the Home (the shared device and normal home members cannot share the device and add home members). Please confirm whether the user has the account of the App (Share devices and add home member must be processed in our App, not in the Alexa or Google Home App). Please confirm whether you and the invitee are registered in the same country/region. You can only add users registered in the same country/region to your home. If you use the invitation code to invite others to join your home, but the invitee's App displays that the invitation code has expired, and the invitation code does not exceed the validity period of 3 days, it means that the account of the invitee and you are not the same country / region. If you are using a shared invitation code to invite others to join the home and you see the message "Invalid invitation code. Please contact the inviter to regenerate," it is because an invitation code can only be used to invite one user. Please ensure that the code has not been sent to multiple invitees. Once it has been used by another person, it cannot be used again to join the home. We recommend contacting the inviter to generate a new invitation code or adding members directly using the app account. Mesh devices/Zigbee devices/Infrared devices/Bluetooth devices/Gateway devices are currently not supported for sharing. For a regular home member, it is recommended that you share all the devices with him/her by adding home members. If you want all family members to use the shared Bluetooth device normally, we recommend that you purchase a Bluetooth gateway and use it together, otherwise the Bluetooth device can only be connected to one mobile phone for one person to use at the same time. Once someone connects successfully, the Bluetooth device in other people's App will be displayed as offline. Only after the user.
You need to check the type information of control data points by querying the schema in DeviceBean to see if there are corresponding dp points, and then query the door lock records. For example, if your door lock does not have the alarm_lock and doorbell dp points, then there will be no corresponding records returned for these functions.
If the device still belongs to the home account that purchased the service after reconfiguring the network, you can continue to use the purchased cloud storage service and access previous video records. If a new device is added to the home account through network configuration, you can use the cloud storage service under that account but cannot access previous video records. If the device no longer belongs to the original home account that purchased the service after network reconfiguration or if the network account has been changed, you will not be able to continue using the previous cloud storage service or view previous video records.
On the 31st day, while no new videos will be uploaded, you can still view videos within their valid cloud storage period. Specifically, if you have purchased a 7-day event cloud storage service, on the 31st day, you can continue to view videos uploaded in the past 7 days that have not been manually deleted. These uploaded videos will be automatically deleted once they reach their cloud storage limit. Once all videos exceed their storage period, you will no longer be able to view them.
Currently, obtaining the Wi-Fi name is not supported.
If you choose a multi-device plan, you can use multiple devices simultaneously within the allowed number of devices for that plan. For example, a single-device plan only supports one device, while a three-device plan allows service for up to three devices simultaneously. You can remove an existing device and reassign the cloud storage service to another device at any time under the household account that purchased the service. If you're unable to do this, please contact the customer support department for assistance. Please refer to the diagram below to learn how to remove a device from the cloud storage service plan and add another device: How to Remove a Device from Cloud Storage or AI Video Patrol Service How to associate a device with cloud Storage or AI Video Patrol Service.
Firmware generally supports it. You can enable the "IPC Cloud Storage Capability" in the Function Definition - Advanced Features section.
After selecting, it is necessary to order modules under the current PID or obtain production certificates for existing modules from the current PID and burn authorization for it to take effect.
ANCS (Apple Notification Center Service) is implemented based on the GATT (Generic Attribute Profile) protocol within the BLE (Bluetooth Low Energy) framework. In the ANCS architecture, the iOS device acts as the GATT Server, while peripheral Bluetooth devices connect as GATT Clients to utilize the services provided by the Server. This mechanism allows Bluetooth devices to access notification information from the iOS device, such as incoming calls, text messages, and notifications from social applications. ANCS comprises three main features: Notification Source, Control Point, and Data Source. The Notification Source is responsible for transmitting all notification information received by the iOS Notification Center. Meanwhile, the Control Point and Data Source work together to facilitate interactive functionality, enabling the iOS device to send control commands to the Bluetooth device and receive response data.
You need to configure the app to prompt for an upgrade on the platform. Typically, after a power outage or entering keep-alive mode, a command is sent to obtain the upgrade. Then, the upgrade data will start to be issued only after the app prompts for an upgrade. You can communicate with Tuya engineers to obtain the low power serial protocol.
The local reset command puts the device into network configuration mode. At this time, it can be re-scanned and bound by other mobile phones or by refreshing the current mobile app page. Currently, the previous device will not be removed during the reset, but this does not affect the reconfiguration of the network.
No.
Dear user, according to the number of calculations, the battery can support about one year for triggered 50 times a day. In low power, in order not to affect your normal use, it is recommended that you replace the battery as soon as possible (within 24 hours).
It is 2.75 volts.
It reports when triggered and maintains low power consumption during normal operation.
Power on the device: on for 5 seconds; Network configuration status: fast flashing; Working mode: off; Data report: flashing once.
The battery uses 3v CR2032 and supports viewing 6 months' history record. The standby current is 3uA, and the reporting current is 5mA.
Yes, currently there are no-code development low power SoC solutions for Wi-Fi door sensors or solutions for MCU integration with Wi-Fi low power general firmware.
It displays 0%.
It may become unreliable when the voltage is below 2.5 volts.
Press and hold the button for 5 seconds to enter the standby state. If the network has not been configurated for 30 seconds timeout, the sensor will enter the hibernation state. If the network is configurated, and the sensor enters the working state, after the work state data being reported, it enters the hibernation state. When the door sensor's state changes, it will enter the working state from the hibernation state.
Yes, the Wi-Fi non-metering switch socket only scans and generates routing signals when powered on.
It sends a heartbeat signal every 4 hours, and if there are no responses for 3 consecutive heartbeats, it will be shown as offline.
The operating current is less than 20mA, and the standby current is less than 6uA.
Battery-powered.
Problem Analysis: The main body of the contact sensor is not aligned with the magnet. Guidance Suggestion: Ensure that the alignment distance between the main body of the contact sensor and the magnet meets the product requirements.
If the wireless signal is weak, alarms will be delayed or will not be pushed. We recommended that you keep the network signal stable.
Tuya provides one-way, two-way, three-way, and four-way Wi-Fi switches using the SoC solution. Press and hold any button to enter the network pairing mode. You can specify the button holding period on the Hardware Develop page on the Tuya Developer Platform.
WPA2 Enterprise is not supported. When the user tries to connect to a WPA2 Enterprise network, login credentials (username and password) are required, so it is not supported. The Wi-Fi module supports WEP, WPA/WPA2, and WPA/WPA2 PSK (AES). To connect to a wireless network, just enter the SSID and Wi-Fi password. Whether WPA3 is supported depends on the module model. Please refer to the module specification for the specific features. Wi-Fi module selection link: https://solution.tuya.com/en/hardware?communicationType=wifi.
General firmware: You can set the network configuration mode to timeout configuration. If the module is not configured for more than 3 minutes, it will enter low power consumption. Send a reset command to put the module back into the configuration state.
European Union EU DECLARATION OF CONFORMITY (DoC) is a document issued by the manufacturer or an authorized representative within the EU to declare that the product complies with all applicable EU regulations and directive requirements. This declaration is typically one of the legal requirements for placing a product on the EU market, especially for products that require the CE marking. By issuing the DoC, the manufacturer acknowledges and ensures that their product complies with all relevant EU health, safety, and environmental protection legislation. These legislations may include the Low Voltage Directive, Machinery Directive, Electromagnetic Compatibility Directive, RoHS (Restriction of Hazardous Substances Directive), etc. The DoC must contain the following information: a description and identification code of the product (such as model, name, etc.). The name and address of the manufacturer and (if applicable) their authorized representative. A list of referenced directives and standards. Where necessary, information on the third-party testing body (notified body) and the certificates they issued. The signature and date of the manufacturer or their authorized representative. Once the product is certified and the DoC is issued, the manufacturer can affix the CE marking on the product and place it on the entire EU market. The DoC is a key document proving the product's compliance with EU requirements and should be kept in the product's technical file for reference and provided upon request by the relevant authorities. Reference template: https://images-weaz.tuyaeu.com/rms-static/2da9b760-a22d-11ef-be03-d1a4feb99779-1731550039510.docx?tyName=RED%C2%A0DOC%20Template%20Files.docx.
Currently, the Wi-Fi communication protocol is not directly opened. You can develop products on our platform: https://developer.tuya.com/en/docs/iot/device-intelligentize-in-5-minutes?id=K914joxbogkm6.
Serial port networking requires the input of three parameters: Wi-Fi name ssid, password, and token. To obtain the token, first go to the Tuya App and click on add device, select "Camera/Lock" choose Wi-Fi class, follow the prompt steps, the generated QR code contains the token, you can use WeChat to scan and get the token. But the validity of the token is 10 minutes.
STA: 11b/g/n/ax + WPA3 + PMF + FFD + KRACK + WPA2. Prepare 2 prototype units. The connection method can be either serial port or USB. The testing method needs to be provided to the laboratory. Specifically, it is divided into: WTS Testing (11n, 11ax, WPA3, PMF, FFD): You need to provide the sigma and the method to call the sigma. Quick track Testing (11n, 11ax, PMF, KRACK, WPA2): You need to provide the corresponding automation method (you can request this from the chip manufacturer), or if using manual testing, you need to provide the test instructions.
Generally written according to the actual occupied bandwidth. 2.4G Zigbee actually occupies about 99% of the bandwidth, approximately 3MHz.
Classic Bluetooth, also known as BR/EDR (Basic Rate/Enhanced Data Rate), refers to traditional Bluetooth technology used for establishing wireless personal area networks (WPAN) and data communication. This technology supports voice and data transmission and is widely used in mobile phones, headsets, car audio systems, computers, and their peripherals. The main features of BR/EDR Bluetooth include: Basic Rate (BR): It provides a maximum data transfer rate of 1 Mbps and is primarily used for voice transmission and lower-rate data communication. Enhanced Data Rate (EDR): Introduced in Bluetooth version 2.0, EDR can provide data transfer rates of up to 2 Mbps or 3 Mbps through improved modulation methods. Connectivity: Classic Bluetooth establishes continuous, reliable connections suitable for applications with continuous data streams, such as audio streaming and file transfer. Power Consumption: Compared to Bluetooth Low Energy (BLE), Classic Bluetooth has higher power consumption, making it more suitable for short-term but high-bandwidth communication. Compatibility: Since Classic Bluetooth technology has been around for many years, it has widespread support and compatibility in the market. Classic Bluetooth and BLE (Bluetooth Low Energy) are two different protocol stacks in the Bluetooth technology specification. Although they share the same radio hardware, their design goals and application scenarios differ. Classic Bluetooth is more suitable for applications requiring continuous data streams, while BLE focuses more on providing low-power periodic data transmission. With the development of Bluetooth technology, many devices now support both Bluetooth modes to meet different application needs.
Electromagnetic Compatibility Directive (EMC Directive), numbered 2014/30/EU, is a regulation of the European Union. This directive stipulates the electromagnetic compatibility requirements that all electrical and electronic equipment sold in the EU market must meet. Electromagnetic compatibility refers to the ability of equipment to operate normally in its electromagnetic environment without causing unacceptable electromagnetic interference to any other equipment in that environment. In short, the purpose of the EMC Directive is to ensure that electronic devices neither emit excessive electromagnetic interference nor are susceptible to a certain level of external electromagnetic interference, thereby being able to operate normally in the intended environment. The EMC Directive requires manufacturers to conduct a series of tests on their products to assess whether the electromagnetic interference emitted by the products is within the permissible range and whether the products have sufficient resistance to external interference. If the products pass these tests, manufacturers need to declare that the products comply with the requirements of the EMC Directive and mark the CE symbol on the products to be sold in the EU market. For devices involving wireless signal transmission or reception, compliance with the EMC Directive is particularly important because these devices may affect the normal operation of wireless communication networks. By complying with the EMC Directive, manufacturers can ensure that their products do not cause interference to other devices and can maintain stable performance in changing electromagnetic environments. Regulation directive text and harmonized standards: https://single-market-economy.ec.europa.eu/single-market/european-standards/harmonised-standards/electromagnetic-compatibility-emc_en.
Situation 1: If the company owning the product is not a Bluetooth member, the Bluetooth SIG has the right to request customs to seize all goods and demand the removal of all products from sale. In extreme cases, the association may file an infringement lawsuit, with infringement costs potentially determined based on the sales value. A small company might be fined around $5,000, while a larger company might face a higher penalty. Situation 2: If the customer is a Bluetooth member, the process occurs in multiple stages, and the association might simultaneously inspect other products on sale: - Day 0: Email notification sent to the primary contact of the registered member. - Day 15: Email notification sent to the primary contact of the registered member. - Day 30: Email notification sent to all contacts of the registered member; a formal letter is mailed to the registered company address. - By Day 44: If the investigated product completes BQB, the penalties stop. - Day 45: A fine of approximately $4,000 to $5,000 is imposed, with email notification sent to all contacts of the registered member. - Day 74: Email notification sent to all contacts of the registered member. - Between Day 45-74: If the investigated product completes BQB and the fine is paid, the penalties stop. - Day 75: Another fine of approximately $4,000 to $5,000 is imposed, with email notification sent to all contacts of the registered member, and consideration is given to terminating the membership (indicating that legally the product cannot continue to use Bluetooth technology).
Radio Equipment Directive (RED) certification refers to a type of certification that complies with the European Union's Radio Equipment Directive (RED) 2014/53/EU. The RED directive is a regulation by the EU for radio equipment sold in the EU market, requiring these devices to meet specific safety, health, and electromagnetic compatibility requirements. The purpose of RED certification is to ensure that radio equipment does not cause harmful interference to radio and telecommunication networks, while also ensuring that these devices do not pose a risk to human health and use appropriate radio spectrum resources. This applies to all wireless devices sold and used in the EU market, including mobile phones, wireless LAN devices, Bluetooth devices, remote control toys, doorbells, etc. To obtain RED certification, manufacturers must conduct a series of tests to demonstrate that their products meet all relevant EU requirements. This usually includes testing for radio spectrum usage efficiency, electromagnetic compatibility (EMC), and product safety assessment. Certified products can be sold in the EU market and must bear the CE mark on the product, indicating compliance with EU requirements. RED certification is mandatory for radio equipment manufacturers wishing to enter the EU market, as it helps ensure product quality and safety, protecting consumer interests. Regulations and harmonized standards: https://single-market-economy.ec.europa.eu/single-market/european-standards/harmonised-standards/radio-equipment_en.
Eurofins Scientific is an international laboratory testing services company headquartered in Luxembourg. Founded in 1987, Eurofins focuses on providing a wide range of testing and certification services in the life sciences fields such as food, environment, pharmaceuticals, and cosmetics. The company's service goal is to ensure the safety, compliance, and quality of client products. Eurofins' service range includes: br Food and Beverage Testing: including food safety, nutritional analysis, food label review, sensory testing, genetic testing, etc. Environmental Testing: providing environmental monitoring services such as water quality, soil, air, and waste analysis. Pharmaceuticals and Cosmetics Testing: including drug efficacy, stability testing, and cosmetic safety assessment. Agricultural and Plant Protection Products Testing: including pesticide residues, plant pathology, and genetically modified organism testing. Consumer Products Testing: such as safety and performance testing of toys, textiles, electronics, cleaning products, etc. Biopharmaceutical Services: providing efficacy and safety assessment of biopharmaceuticals, as well as preclinical and clinical trial-related services.
CQC China Quality Certification Centre (China Quality Certification Centre, abbreviated as CQC) is one of the most authoritative professional certification bodies in China, directly under the China National Certification and Accreditation Administration (CNCA). Established in 1993, CQC is mainly responsible for conducting product certification, management system certification, and other related certification services within China. The certification services provided by CQC are very extensive, covering multiple fields such as electrical and electronic products, mechanical equipment, building materials, automotive parts, textiles and clothing, food, and services. Its certification projects include but are not limited to: CCC Certification (China Compulsory Certification): Mandatory safety certification for products such as wires and cables, switchgear, power tools, and household appliances. br Voluntary Product Certification: Quality certification for products that are not subject to mandatory certification. Management System Certification: Including ISO 9001 Quality Management System, ISO 14001 Environmental Management System, OHSAS 18001 Occupational Health and Safety Management System, etc. Energy Efficiency Label Certification: For energy-saving products, such as household appliances, lighting products, etc. Organic Product Certification: Organic certification for agricultural products and food. Green Product Certification: Evaluation of the environmental performance of products. Information Security Certification: Including information technology security level protection certification, etc.
Bluetooth Low Energy (BLE) transmission rates vary with different versions of the Bluetooth specification. Here are some major versions of BLE transmission rates: Bluetooth 4.0: The initial BLE specification offers a theoretical maximum transmission rate of about 1 Mbps (1 megabit per second). Bluetooth 4.2: Introduced data packet length extension, allowing for larger data packet transmission, thereby improving data transmission efficiency, but the theoretical maximum rate remains 1 Mbps. Bluetooth 5.0: Added new physical layer options, including an enhanced data rate mode of 2 Mbps, and a long-range transmission mode (LE Coded: 125kbps and 500kbps).
Thailand TISI certification is a product certification issued by the Thai Industrial Standards Institute (TISI). TISI is an agency under the Ministry of Industry of Thailand, responsible for developing and implementing standards for industrial products. TISI certification covers a wide range of product categories, including electrical equipment, building materials, automotive parts, chemicals, textiles, and more. For certain products, such as wires and cables, socket switches, household appliances, children's toys, etc., TISI certification is mandatory, and these products must be certified before entering the Thai market for sale. To obtain TISI certification, products need to undergo a series of tests and evaluations to ensure they meet the relevant Thai Industrial Standards (TIS standards). These tests are usually conducted in laboratories recognized by TISI. Certified products will be awarded the TISI mark, indicating that the product complies with Thailand's national standards. For manufacturers and exporters, TISI certification is an important condition for their products to enter and compete in the Thai market. For consumers, the TISI mark is a signal that the products they purchase meet the quality and safety standards set by the Thai government. https://www.tisi.go.th/website/standardlist/comp_thai/en.
Low Energy Bluetooth (Bluetooth Low Energy, abbreviated as BLE), also known as Bluetooth 4.0 or Bluetooth Smart, is a version of Bluetooth technology designed to provide lower energy consumption and cost while maintaining a comparable communication range. BLE was initially introduced in 2010 as part of the Bluetooth 4.0 specification, optimized for short-range wireless communication compared to traditional Bluetooth technology (now commonly referred to as Bluetooth Classic). The design focus of BLE is to achieve low power operation, allowing devices to run for months or even years on small batteries such as button cells. This makes BLE particularly suitable for various low-bandwidth, low-power application scenarios, such as health and fitness trackers, smart home devices, location tracking devices, and wearable technology. The main features of BLE include: Low energy consumption: BLE devices can enter power-saving mode during inactive periods, significantly reducing energy consumption. Low cost: The manufacturing cost of BLE devices is relatively low, making them easy to integrate into various products. Ease of use: BLE supports simple connection and data transfer processes, enhancing the user experience. Wide compatibility: BLE is now supported by most modern smartphones and tablets. Although BLE may not match classic Bluetooth in terms of data transfer rate and distance, its advantages in energy efficiency make it an ideal choice for many emerging mobile applications and IoT devices. As technology advances, BLE has become an indispensable part of Bluetooth technology and continues to be improved and enhanced in Bluetooth 5.0 and later versions.
The Harmonised Standards for the European Union are a set of technical specifications developed by European standardization organizations (such as CEN, CENELEC, and ETSI) that are aligned with EU legislation (such as directives and regulations) to ensure the free movement of products, services, or processes within the internal market of the entire EU. The "CE" mark is an abbreviation for "Conformité Européenne," meaning "European Conformity," and it is a declaration that the product meets the EU's health, safety, and environmental protection requirements. When a product complies with all relevant CE harmonised standards, the manufacturer can affix the CE mark to their product and issue a Declaration of Conformity (DoC) to demonstrate that the product meets the applicable EU directive requirements. The main features of the EU CE harmonised standards include: Uniformity: Harmonised standards are recognized in all EU member states, ensuring the free movement of products between these countries. Comprehensiveness: They cover a wide range of fields from toys, electronic and electrical equipment to construction products and medical devices. Self-declaration: For certain product categories, manufacturers can conduct self-assessment and declare their products comply with CE standards without the involvement of third-party organizations. Mandatory: For products that require the CE mark, compliance with CE harmonised standards is not optional but mandatory. Market surveillance: Although manufacturers are responsible for ensuring their products meet the requirements, market surveillance authorities in EU member states also regularly inspect products on the market to ensure they indeed comply with the prescribed standards. CE harmonised standards aim to simplify technical specifications and promote the integration of the European internal market while ensuring the safety of products for consumers and the environment.
The Low Voltage Directive (LVD) is a regulation of the European Union, numbered 2014/35/EU. This directive stipulates the safety requirements that all electrical equipment sold in the EU market must meet in their design and manufacture. LVD applies to all electrical equipment with a rated voltage between 50 and 1000 volts AC and between 75 and 1500 volts DC. The main objective of the Low Voltage Directive is to ensure that electrical equipment sold in the EU market does not threaten human health and safety, while also protecting property and pets from harm. It requires manufacturers to take appropriate measures to prevent electric shock, fire, and other risks associated with the use of electrical equipment. Manufacturers must ensure that their products comply with the requirements of the LVD and undergo appropriate compliance assessment processes, such as internal production control or third-party testing. Products that successfully pass the assessment will be awarded the CE mark, indicating that the product complies with all applicable EU regulations and directives. The Low Voltage Directive is not only a legal requirement for manufacturers to sell electrical equipment in the EU market but also an important measure to protect consumers from unsafe products. Regulation directive text and harmonized standards: https://single-market-economy.ec.europa.eu/single-market/european-standards/harmonised-standards/low-voltage-lvd_en.
Singapore S-Mark certification, also known as PSB certification, is a product safety certification mark issued by the Productivity and Standards Board (PSB) of Singapore. PSB has now been renamed Enterprise Singapore, a statutory body of the Singapore government responsible for establishing and implementing product safety standards. S-Mark certification mainly targets electrical and electronic products, indicating that the product has been tested and meets Singapore's safety standards and requirements. For certain electrical products, such as household appliances, lighting equipment, and wires and cables, S-Mark certification is mandatory in Singapore, and these products must be certified before they can be sold in the Singapore market. To obtain S-Mark certification, products need to undergo a series of safety tests, which are usually conducted in laboratories recognized by PSB. Products that successfully pass the tests are awarded the S-Mark label, which is usually affixed to the product or its packaging. Currently, the list of products requiring S-Mark certification can be found at the following URLs: https://www.consumerproductsafety.gov.sg/suppliers/cpsr/list-of-controlled-goods/, https://www.cpsaplus.gov.sg/Homepage.
Transferable General Requirements: 1. There are no functional changes between the product accepting the transfer plan and the original certified product; 2. The product accepting the transfer plan is exactly the same as the original certified product in terms of certification standards, equipment type, and equipment function. Only changes to the product brand or appearance are allowed, including packaging, casing, and/or user interface (e.g., casing color, brand logo, and initial screen of the user interface).
Radio Frequency Power Spectral Density (PSD) is a parameter that measures the power distribution of a radio signal in the frequency domain. It describes the distribution of signal power over a frequency range, usually expressed in power units (such as watts/dBm) divided by frequency units (such as hertz), i.e., watts/hertz (W/Hz) or dBm/MHz. PSD is an important indicator because it can show the amount of energy used by a radio transmitter within a specific frequency bandwidth. In wireless communication system design and spectrum management, PSD is used to ensure that radio transmissions do not exceed the specified power limits, and it also helps to assess and prevent interference between different wireless systems. For example, the limit for 2.4G Wi-Fi products in the EU and China is PSD10dBm/MHz. Within a given bandwidth, if a radio transmitter's power is too high, its PSD value will also be relatively high, which may lead to interference with adjacent channels. Therefore, regulatory agencies typically set upper limits on PSD for specific radio services to maintain the health and order of the electromagnetic environment.
2.4GHz Wi-Fi band typically includes channels 1 to 14, each with a width of 20MHz. However, not all channels are available in every country or region. The availability of channels depends on local radio frequency regulations. EU: Channels 1 to 13 are usually allowed (a total of 13 channels). US: Channels 1 to 11 are allowed (a total of 11 channels). China: Channels 1 to 13 are allowed. It is noteworthy that channel 14 is standard only in Japan and is usually only usable in 802.11b mode.
PAHs (Polycyclic Aromatic Hydrocarbons), refer to hydrocarbons containing two or more benzene rings connected together in the molecule. To date, more than 200 types of PAHs have been discovered. PAHs are a class of harmful substances produced under conditions of incomplete combustion or high-temperature treatment of fuels such as petroleum, coal, and wood, as well as combustible gases. They are commonly found in petrochemical products, rubber, plastics, lubricants, rust-proof oil, and incompletely combusted organic compounds, and are one of the important carcinogens in the environment. Various regulations, including the EU REACH regulation, German GS mark certification, and California Proposition 65, have put forward control requirements for PAHs. You can refer to the introduction of CTI: https://www.cti-cert.com/service/3130/5330.html.
Antennas are key components in wireless communication systems, used for transmitting and receiving radio waves. Depending on different design and application requirements, antennas can be divided into various types. 1. By antenna form It can be divided into: PCB onboard, FPC antenna (Flexible Printed Circuit Antenna is an antenna manufactured using flexible printed circuit board technology), Ceramic Antenna, etc. 2. By antenna technology Dipole Antenna: The most basic form of antenna, usually consisting of two opposing metal rods, with a length of about half the wavelength at the operating frequency. Monopole Antenna: A variant of the dipole antenna, with only one metal rod, and usually requires a ground plane as a reflector. Wire Antennas: Include simple straight, bent, or looped wires, commonly used in low-frequency applications. Microstrip Patch Antenna: A type of planar antenna, commonly used in mobile devices and satellite communications. Helical Antenna: A helical-shaped antenna that can provide circularly polarized waves. etc.
Please refer to the document center introduction: https://developer.tuya.com/en/docs/iot/patentability-certification?id=Kaiuzuhpgu05y.
This requires the customer to conduct their own test report to verify product safety. Regarding Tuya's solution, we have a statement on our official website declaring compliance with standard requirements. If the customer wants to obtain a test report for their product, they can consider using Tuya's value-added services to complete it. PSTI has three requirements: Prohibit the use of common default passwords and easily guessable default passwords on products. Require product manufacturers to inform customers of the security update support period at the point of sale. Require manufacturers to provide a public contact point to make it easier for security researchers and others to report product defects and errors. The first point is related to Tuya's solution, while the second and third points require the customer to make announcements on their own website. The technical solution of Tuya OS version 3.3 and above can ensure that the end product meets the technical requirements of PSTI: https://developer.tuya.com/en/docs/iot/Statement_PSTI?id=Kdg394bwcsgu0.
BQB stands for Bluetooth Qualification Body, a Bluetooth certification organization authorized by the Bluetooth Special Interest Group (SIG) (official website: https://www.bluetooth.com). Established in 1998, it is a membership-based alliance organization. Bluetooth products sold in the market must be certified by this organization and meet its standards, which are fee-based.
No, the Bluetooth SIG (Special Interest Group) has strict regulations and there are many risks involved, such as products being unable to clear customs, being reported by competitors, and facing fines and other penalties. Only products that have completed Bluetooth BQB certification can legally use the Bluetooth logo on their appearance. Both modules and finished products need to undergo BQB certification. Bluetooth is a patented technology, and all technical patents belong to the Bluetooth SIG. Even if the logo is not used, as long as the product uses Bluetooth technology, the Bluetooth SIG has the right to pursue infringement. The current situation is that the Bluetooth SIG has made requests to customs in various countries, and any product packaging, nameplate, or manual with the word Bluetooth or logo is a key inspection target for customs. Not having the logo or the words Bluetooth or Bluetooth can only reduce the risk of being inspected. The Bluetooth SIG usually focuses on the products of major brand manufacturers. The official website has a Q&A for reference. https://qualification.support.bluetooth.com/hc/en-us/articles/26704450972813-Do-I-Need-to-Qualify.
Zigbee is an advanced communication protocol based on the IEEE 802.15.4 standard, designed specifically for low-rate, low-power, low-data wireless communication over long distances. Zigbee technology is commonly used in areas such as home automation, smart energy management, industrial control, and medical data collection, and is particularly suitable for applications requiring long battery life and secure networks. Zigbee networks support various topologies, including point-to-point, point-to-multipoint, and mesh networks. In a mesh network, each device (node) can communicate directly with neighboring devices, forming a stable self-organizing and self-healing network system. This design gives Zigbee networks good scalability and reliability, allowing the network to automatically reconfigure paths to maintain communication even if some nodes fail. A notable feature of the Zigbee protocol is its low power consumption design, enabling devices (such as sensors and controllers) to operate for years on battery power. Additionally, the Zigbee protocol provides security features, including data encryption and device authentication, to ensure the security of network communications.
Brazil ANATEL certification refers to a certification system implemented by the Brazilian National Telecommunications Agency (Agência Nacional de Telecomunicações, abbreviated as ANATEL), targeting all telecommunications equipment sold or used in the Brazilian market. ANATEL is a government agency in Brazil responsible for regulating and authorizing telecommunications services and equipment, ensuring they meet national technical requirements and standards. The purpose of ANATEL certification is to ensure the quality and safety of telecommunications products and the rational use of the radio spectrum, to avoid radio interference between different devices, and to protect consumer interests. This includes various wireless communication devices such as mobile phones, wireless routers, radio stations, satellite equipment, etc. To sell telecommunications equipment in the Brazilian market, manufacturers or importers must ensure that their products have passed ANATEL's certification process, which usually includes technical testing, registration, and compliance assessment. Once the product is certified, it will receive ANATEL's mark and certification number, indicating that the product is authorized for sale in the Brazilian market.
No, the low-power product catalog does not include Bluetooth products.
Part 15B is the FCC regulation chapter applicable to the electromagnetic compatibility (EMC) testing of unintentional radiating electronic products. After the manufacturer obtains the FCC part15B report issued by a qualified laboratory, a company within the United States can act as the responsible party on behalf of the manufacturer to make a self-declaration and issue an SDoC document to meet regulatory requirements.
Wi-Fi Adaptive refers to the ability of Wi-Fi devices and networks to automatically adjust their operating parameters to adapt to changing wireless environments. For example, when the current working channel is congested or the signal is weak, it needs to automatically switch to a relatively idle channel for data transmission. CE and SRRC certification testing standards have clear limit requirements for switching time, channel occupancy time, and signal detection threshold. For details, refer to the EN 300328 standard.
40 channels, channel spacing 2MHz, channel center frequency list: 2402MHz, 2404MHz, 2406MHz, ......, 2478MHz, 2480MHz, etc.
TUV Rheinland is an international certification body headquartered in Cologne, Germany, founded in 1872. It is one of the world's leading independent inspection, testing, and certification service providers, offering professional technical services to global clients, including product testing, system certification, industrial services, transportation, and energy systems safety and quality certification. TUV Rheinland has over 500 offices and laboratories worldwide, spanning 65 countries and regions, with more than 20,000 employees. Its service range is extensive, covering multiple fields such as automotive, electronics and electrical, machinery, construction, energy, environmental protection, healthcare, and food safety.
SAR testing (Specific Absorption Rate test) is used to measure the rate at which radio frequency (RF) energy released by wireless devices (such as mobile phones, tablets, etc.) is absorbed by human tissue during use. The SAR value is an indicator of RF energy absorption, usually measured in watts per kilogram (W/kg). This test is to ensure that wireless communication devices do not exceed the RF energy exposure limits set by international safety standards when operating at maximum power. SAR testing mainly focuses on the following two aspects: Local SAR: Measures the maximum RF energy absorption in specific parts of the body (such as the head or wrist). This is especially important for mobile phones and other wireless devices used close to the body. Whole-body SAR: Calculates the average energy absorption rate of the entire body during device operation. Different countries and regions have different SAR limits. For example, the United States Federal Communications Commission (FCC) stipulates that the SAR value of mobile phones must not exceed 1.6W/kg (measured based on 1 gram of tissue), while Europe allows a maximum SAR value of 2W/kg (measured based on 10 grams of tissue). SAR testing is usually conducted in certified laboratories using special testing equipment and liquid that simulates human tissue (commonly referred to as SAR phantom liquid). During the test, the device is placed in a position similar to that of the human body and operated at different frequencies and power levels to simulate actual usage conditions. Then, a specialized probe measures the RF energy absorption in the phantom liquid to determine the SAR value.
KC (Korea Certification) is a mandatory product certification in Korea to ensure the safety of its citizens. It requires that safety management objects, including electronic and electrical products or household goods, meet relevant Korean safety conditions before entering the Korean market. The KC certification uses a unified KC mark (2009), which was formed by merging 13 statutory mandatory marks in Korea. The main requirements for electronic and electrical products to enter the Korean market are in three aspects: safety, electromagnetic compatibility (EMC), and radio frequency (RF) certification. After obtaining the certificate, the KC certification mark and the corresponding certification number need to be printed on the product nameplate. The radio frequency part can reference the certificate of the integrity module.
In theory, all homogeneous materials need to be tested individually to assess whether they meet regulatory requirements. However, if all are tested as homogeneous materials, the cost of chemical testing would be very high. Therefore, many companies accept the method of "assessing risk through mixed testing of finished products, without mixing raw materials" for environmental assessment to reduce environmental risks. The more materials mixed for testing, the lower the credibility of the test results. Therefore, many customers with requirements for environmental testing methods will determine the maximum number of materials they accept to be tested together. For example, if two materials are mixed for testing, and one exceeds the limit while the other does not, if the average value of the mixture is below the limit, it is impossible to determine if a single material exceeds the limit. Environmental control needs to be more focused on the raw material end, and at the finished product stage, compromise through mixed testing is used to screen and reduce risks, balancing cost and efficiency.
Apple HomeKit certification refers to a certification by Apple Inc. for home automation devices produced by third-party manufacturers. These devices are compatible with Apple's HomeKit smart home framework, allowing users to control smart devices in their homes through Apple devices such as iPhone, iPad, Apple Watch, or HomePod, as well as Apple's virtual assistant Siri. The HomeKit framework provides a standardized way to control a variety of different smart home devices, including lights, locks, thermostats, cameras, and outlets. These devices can be set up, managed, and controlled through Apple's "Home" application (Home app). To obtain HomeKit certification, a manufacturer's product must meet Apple's performance standards and security requirements. This typically involves using specific hardware chips to ensure secure encryption and going through Apple's certification testing process. Certified products can display the HomeKit logo on their packaging and can be listed as HomeKit-compatible products on Apple's official website and stores. HomeKit certification means that the product can not only integrate seamlessly with Apple devices but also provide a consistent user experience and meet Apple's high standards for privacy and security. For consumers, this is a signal that the smart home devices they purchase can be used safely and conveniently with their Apple ecosystem.
PFAS, the English abbreviation for per/polyfluoroalkyl substances, refers to perfluoroalkyl and polyfluoroalkyl compounds. PFAS are a class of organic chemicals containing at least one fully fluorinated carbon atom. PFAS are a large family composed of thousands of synthetic chemicals. Due to their extremely stable carbon-fluorine bonds, these substances possess strong chemical stability, surface activity, excellent thermal stability, and hydrophobic and oleophobic properties, making them widely used in industrial production and consumer life fields. PFAS include PFOA (perfluorooctanoic acid), PFOS (perfluorooctane sulfonate), PFDA (perfluorodecanoic acid), PFCAs (perfluorocarboxylic acids), PFBS (perfluorobutane sulfonic acid), PFHxS (perfluorohexane sulfonic acid and its salts), etc.
Wi-Fi Alliance certification and BQB certification, finished products can derive and list the certificate of the finished product based on the module's certificate, obtaining the certificate number belonging to the finished product. The essence of alliance certification is patent authorization, and brand owners cannot use the certification logo without obtaining the alliance certificate. The Wi-Fi Alliance provides a public logo (https://www.wi-fi.org/who-we-are/our-brands), which only indicates that the product has Wi-Fi functionality. Kind reminder: Modules cannot perform Zigbee Alliance certification, only finished products can be certified by the Zigbee Alliance.
For the certification of wired and wireless communication equipment in Egypt, CE and FCC standards are recognized. Only reports from a few laboratories listed in the official directory are acknowledged. The Egyptian NTRA refers to the National Telecom Regulatory Authority, an independent administrative body responsible for regulating the telecommunications industry in Egypt. Established in 2003 under the Telecommunication Regulation Law No. 10, NTRA's main responsibilities include formulating telecom policies, issuing licenses, supervising the quality of telecom services, ensuring fair competition, and protecting consumer rights. NTRA is also responsible for managing and allocating radio spectrum, approving the import and use of telecom equipment, and ensuring that equipment and services comply with national technical standards and regulations. For telecommunications and wireless equipment imported and sold in the Egyptian market, NTRA has mandated registration and certification procedures to ensure that these devices do not interfere with the national communication network and guarantee user safety.
ROHS refers to the EU regulations on the restriction of hazardous substances in electronic and electrical products. All electronic and electrical products and their accessories must comply, with 10 testing items in total. Specifically: 1. Cadmium: less than 100ppm; 2. Lead: less than 1000ppm; 3. Mercury: less than 1000ppm; 4. Hexavalent chromium: less than 1000ppm; 5. Polybrominated biphenyls (PBB): less than 1000ppm; 6. Polybrominated diphenyl ethers (PBDE): less than 1000ppm; 7. Bis(2-ethylhexyl) phthalate (DEHP): less than 1000ppm; 8. Benzyl butyl phthalate (BBP): less than 1000ppm; 9. Dibutyl phthalate (DBP): less than 1000ppm; 10. Diisobutyl phthalate (DIBP): less than 1000ppm. Most countries will refer to EU regulations to convert them into their own national regulations. REACH is the regulation for the control of chemical substances for exports to the EU, and almost all products need to comply. The focus is on SVHC (Substances of Very High Concern). If the SVHC content is 0.1% (mass percentage) and the total amount is ≥1 ton/year, notification is required. As of October 2024, the latest controlled chemical substances under SVHC are 241 items. Additionally, REACH has an authorization list (certain chemicals require authorization for use) and a restriction list REACH Annex XVII (certain chemicals are prohibited from use).
International Laboratory Accreditation Cooperation (ILAC): ILAC is an international organization composed of national laboratory accreditation bodies, established in 1977. Its main goal is to promote international cooperation among laboratory accreditation bodies and achieve mutual recognition of laboratory testing and calibration results worldwide. ILAC ensures that its member bodies can conduct laboratory accreditation according to unified requirements by developing international standards (such as ISO/IEC 17025), thereby enhancing the credibility of testing and calibration results. ILAC's Mutual Recognition Arrangement (ILAC MRA) is a key element, allowing a test or calibration report from a laboratory accredited by an ILAC member body to be accepted in other countries that have signed the mutual recognition agreement. This helps reduce trade barriers by decreasing the need for repeated testing of products when entering different markets. International Accreditation Forum (IAF): IAF is a global association of accreditation bodies, established in 1993, aiming to ensure that certification bodies provide consistent and reliable services worldwide. IAF mainly involves the fields of management systems, products, services, personnel, and other types of certification. IAF promotes and oversees the implementation of ISO certification standards (such as ISO 9001, ISO 14001, etc.) through cooperation with the International Organization for Standardization (ISO). IAF's Multilateral Recognition Arrangement (IAF MLA) ensures that management systems, products, or services certified by its member bodies are widely recognized globally. This means that companies only need to obtain certification once to demonstrate their compliance with international standards in the global market. The cooperation and work of these two organizations are crucial for international trade, as they help simplify the complexity of the global market and provide consumers with confidence in the quality o.
Maximum transmission rate is 250kbit/s.
Transportation appraisal report usually refers to a formal assessment document that certifies the safety and compliance of a certain commodity during transportation. Transportation agencies generally only accept test reports within one year. Domestically recognized report agencies include: UL, Shanghai Chemical Institute, DGM, etc. This type of report is particularly important for items considered dangerous goods, such as chemicals, flammable items, compressed gases, explosive items, toxic substances, etc. According to international and regional transportation regulations (such as the International Civil Aviation Organization's technical instructions or the International Maritime Organization's dangerous goods rules), transporting dangerous goods often requires a detailed appraisal report. This report should include a detailed description of the item, hazard classification, packaging instructions, emergency response measures, and any special handling or storage requirements. The purpose of the transportation appraisal report is to ensure the safety of goods during transportation and to prevent harm to the transport vehicle, environment, cargo handlers, or the public. For goods requiring international transportation, the transportation appraisal report is one of the essential documents for customs clearance and transportation. In some cases, this report may also include other types of assessments, such as the appraisal of the structural integrity, stability, and performance of equipment or machinery to ensure their safety and functionality during transportation.
CNAS (China National Accreditation Service for Conformity Assessment) is one of the most authoritative accreditation bodies in China, established by the Certification and Accreditation Administration of the People's Republic of China (CNCA). It is responsible for accrediting conformity assessment bodies such as certification bodies, laboratories, and inspection bodies within China. Institutions accredited by CNAS can demonstrate that their services meet relevant domestic and international standards and requirements, which helps to enhance the credibility of their services and increase market competitiveness. The CNAS accreditation mark is widely recognized in both the Chinese and international markets and is an important symbol of quality and competence.
802.11b: DSSS 802.11g: OFDM 802.11n(20MHz): OFDM 802.11n(40MHz): OFDM 802.11a: OFDM 802.11ac(20MHz): OFDM 802.11ac(40MHz): OFDM 802.11ac(80MHz): OFDM ; 802.11ax(20MHz): OFDM.
In April 2024, the UK's IOT product cybersecurity PSTI Act will be officially implemented, and subsequent products exported to the UK will need to obtain PSTI certification. According to the requirements of the PSTI certification, manufacturers need to make some policy announcements and provide a vulnerability submission portal on public channels (usually the company website). The UK government has passed the Product Security and Telecommunications Infrastructure Act, abbreviated as "PSTI". The mandatory implementation date for the first part of this Act is set for April 29, 2024. The Act requires manufacturers, importers, and distributors of products connected to the internet or to other products using digital technology to comply with new cybersecurity regulations. Non-compliant companies will face fines of up to £10 million or 4% of their global turnover. Basic content of the Act: The Act is divided into two parts, one proposing security measures to protect consumers and companies from cyberattacks, and the other pertaining to telecommunications infrastructure guidelines. In the first part, the cybersecurity measures stipulated by the Act include the following minimum security requirements: Prohibiting the use of universal default passwords and easily guessable default passwords on products. Requiring product manufacturers to inform customers at the point of sale about the security update support period for the product. Requiring manufacturers to provide a public contact point to make it easier for security researchers and others to report product defects and bugs. The range of products covered by the new Act includes the vast majority of consumer-connected products, such as smartphones, smart appliances, smart home assistants, cameras, smart door locks, alarm systems, smart home hubs and voice assistants, outdoor activity equipment, children's toys, and baby monitors. It also applies to products that cannot connect directly to the internet but can connect to mul.
Canada NRCAN certification refers to the certification that complies with the energy efficiency standards and regulations of Natural Resources Canada (NRCAN). NRCAN is responsible for developing and enforcing Canada's energy efficiency regulations, aiming to improve product energy efficiency, reduce energy consumption and greenhouse gas emissions, and help consumers make more energy-efficient choices when purchasing products. NRCAN's energy efficiency certification covers a variety of household and commercial products, including but not limited to appliances, lighting products, electronic devices, HVAC systems, and building materials. Manufacturers and importers need to ensure that their products meet NRCAN's energy efficiency standards and label them with energy efficiency labels. To obtain NRCAN certification, products may need to be tested by third-party testing laboratories to verify their energy efficiency performance. Certified products will be included in NRCAN's energy efficiency database and can be sold in the Canadian market.
ITS Intertek (Intertek Testing Services, abbreviated as ITS) is a global provider of quality and safety services, headquartered in London, established in 1885. ITS Intertek offers a wide range of services, including testing, inspection, certification, and consulting, aimed at helping clients improve product quality and safety, ensuring compliance with global market standards and regulatory requirements. ITS Intertek's service scope covers many industries, including consumer goods, toys, textiles, footwear, furniture, electronics and electrical, food, medical devices, chemicals, energy, building materials, etc. In the field of electronic product certification, ETL certification is a highly recognized certification in the United States and Canada, aside from the UL certification.
11b: 1,2,5.5, 11 (Mbps) 11g: 6,9,12,18,24,36,48,54(Mbps) 11n: HT20/HT40 MCS0~7 11ax: MCS0~9 Since the IoT industry does not have high requirements for transmission rates, 11ax may only support up to MCS7 in terms of rate. Please refer to the module specification for details.
RF certificates are divided into two types: KC certification and KC Registration. 1. For BT, Wi-Fi, or other low-power transmitters, KC Registration is currently used, and either an English or Korean manual can be provided. 2. For high-power transmitting products, such as WCDMA/LTE, KC certification is required, and a Korean manual must be provided.
Thread and Zigbee are both wireless protocols based on the IEEE 802.15.4 standard, which means they have similar wireless characteristics at the physical layer. The IEEE 802.15.4 standard defines a physical layer and MAC (Media Access Control) layer for low-rate wireless personal area networks. Since both Thread and Zigbee use the 2.4 GHz ISM (Industrial, Scientific, and Medical) band, they have similar range and capabilities in terms of wireless transmission. This includes features such as data transmission rate, modulation methods, and channel allocation. For example, they both use Direct Sequence Spread Spectrum (DSSS) and Offset Quadrature Phase-Shift Keying (O-QPSK) modulation techniques to transmit data. However, despite the similarities at the physical layer, Thread and Zigbee have significant differences at the network and application layers. Thread is an IP-based network protocol that uses 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) as its network layer, allowing devices to connect directly to IP networks and easily integrate with other IP-based networks. Zigbee, on the other hand, typically uses its own network and application layer protocols based on an application layer framework. Overall, Thread and Zigbee have similar wireless characteristics at the physical layer, but they differ in how they build networks and handle data, making them suitable for different application scenarios and requirements.
Modules are divided into limited modules and complete modules. Generally, modules with onboard antennas and shielding covers are considered complete modules. If a customer's finished product uses our complete module, the FCC PART15C radio frequency part can be exempted from testing, and only the FCC part 15B part needs to be tested. If a limited module is used, then the customer's finished product needs to undergo complete testing for radio frequency part 15C and part 15B. Limited modules currently do not have an FCC certificate.
The fixed frequency radiation prototype is used for the radiation test items in certification. The firmware inside the module is fixed frequency firmware, without RF lines, used for some radiation tests, such as radiation spurious emissions. The module is soldered onto the whole machine, powered by the whole machine, and leads out the serial port lines: GND, RX, TX, connected to the computer through a USB serial board, and the module is fixed frequency through test software or test commands.
UL primarily provides certification for access to the U.S. market and is also the developer of U.S. safety standards. The commonly mentioned UL certification can be understood as the UL certificate issued by the UL certification body based on UL standards. Other certification bodies can also issue U.S. safety certifications based on UL standards, such as ETL, cTUVus, etc. UL (Underwriters Laboratories) is a global safety science company that provides safety solutions aimed at promoting innovation, protecting lives and property, and maintaining the safety of global supply chains. Founded in 1894 and headquartered in Northbrook, Illinois, USA, UL is an independent, non-profit organization that develops standards and testing procedures to ensure the safety of products, materials, components, equipment, systems, and services. UL's services include safety analysis, certification, testing, inspection, auditing, consulting, and education. Its business scope is extensive, covering numerous industries such as consumer goods, electronics and electrical, building materials, life safety, environmental protection, food safety, water products, energy, and health sciences. As a well-known certification body, the UL mark is a globally recognized safety mark by consumers and manufacturers. The UL mark indicates that the product has undergone rigorous scientific testing and evaluation and meets specific safety requirements. Additionally, UL collaborates with government agencies, industry associations, and international standardization organizations worldwide to ensure that its standards and certification procedures meet the ever-changing market demands.
NIST 8259 and NIST 8425 are documents published by the National Institute of Standards and Technology (NIST) in the United States, providing guidelines and recommendations on the security of Internet of Things (IoT) devices. NIST 8259 (officially titled "NIST Special Publication 8259, Recommendations for IoT Device Manufacturers: Foundational Activities and Core Device Cybersecurity Capability Baseline") is a guide for IoT device manufacturers, aimed at helping them understand and implement necessary security measures to protect devices from cyberattacks and data breaches. This document proposes a series of foundational activities and core cybersecurity capabilities, including device identification, device configuration, data protection, logical access control, etc., to ensure the security of IoT devices. NIST 8425 (officially titled "NIST Special Publication 8425, Cybersecurity for IoT Program: Status and Next Steps") is a document about NIST's IoT cybersecurity program, describing the current status and future plans of NIST in developing IoT cybersecurity. This document provides an overview of how NIST addresses IoT security issues, including key areas of research and development, as well as collaboration with other organizations. Overall, these NIST-published documents aim to provide guidance to help enhance the security of IoT devices, reduce potential cybersecurity threats, and promote the trustworthy and sustainable development of IoT technology. Currently, if products meet the NIST IoT cybersecurity standards, they can generally claim to meet the product-level cybersecurity requirements of various U.S. states.
BLE: GFSK, in addition, classic Bluetooth BR/EDR: GFSK, π/4-DQPSK, 8-DPSK.
Zigbee usually uses the 2.4G ISM band, with a specific frequency range of 2405-2480MHz.
Fixed frequency conduction module is used for some conduction test items in certification. The firmware in the module is fixed frequency firmware, and an RF cable will be soldered, with the RF cable being an SMA head, connected to equipment such as a spectrum analyzer for testing. The module leads out 3.3V, GND, RX, TX to connect to a USB serial port board, which can be connected to a computer through the USB serial port board, and then the module can be fixed frequency through test software or test commands, allowing it to work fixedly on a certain channel with the maximum duty cycle. It is mainly used for RF certification test projects of conduction direct connection type: fixed frequency conduction module is used for some conduction test items in certification: maximum output power (EIRP), power spectral density (PSD), occupied channel bandwidth, out-of-band emission, emission spurious (conduction), reception spurious (conduction), etc.
4pc normal.
Zigbee is classified as a low-power technology by the Radio Management Bureau of the Ministry of Industry and Information Technology, so in principle, it does not support Zigbee modules to independently apply for SRRC as a complete module. For finished products using Zigbee, if the EIRP transmission power is greater than 10dbm, it is necessary to apply for SRRC certification as a 2.4G spread spectrum communication device; if the EIRP transmission power is less than or equal to 10dbm, it is considered a low-power product, and relevant warning statements should be added.
No, after the version update, you need to purchase a new DID to relist.
CEC certification is mandatory, and products must apply for CEC certification to enter the California market in the United States. Electrical products must be tested by qualified laboratories according to the corresponding U.S. standards, and only after proving compliance can they be sold in California. CEC stands for the California Energy Commission, and CEC certification is the energy efficiency certification issued by this commission. The regulations aim to save energy, improve the efficiency of electrical products, and reduce greenhouse effects and gas emissions. CEC certification covers a wide range of electrical products, including but not limited to products using external power supplies, such as mobile phones, cordless home phones, portable music players, handheld game consoles, toys, etc. These products need to use energy more efficiently in both standby and active states. CEC certification specifications require 58 categories of products, covering almost all electronic and electrical products, specifically including power products (such as external power supplies, power adapters), information products (set-top boxes, monitors, etc.), audio-visual products (DVD players, etc.), televisions, small battery charging systems (Bluetooth headsets, Bluetooth speakers, fitness trackers, dash cams, mobile phones, tablets, laptops, and other battery-powered products), large battery charging systems (products other than small charging systems), lighting products (LED lighting, fluorescent lamps, fluorescent lamp ballasts, etc.), household appliances (refrigerators, air conditioners, washing machines, dryers, ovens, microwaves, pool heaters, etc.), transformer products, motor products, and bathroom products (such as showerheads, faucets, toilets, sinks, etc.).
Halogen-free, in materials science and electronics manufacturing, refers to a material that does not contain halogen elements (fluorine, chlorine, bromine, iodine, and astatine), especially chlorine and bromine, as these two elements are commonly used in flame retardants. When materials such as plastics, circuit boards, or cable insulation do not use flame retardants containing chlorine and bromine during production, these materials can be called halogen-free. Although halogen flame retardants can improve product safety in the event of a fire, they may release toxic gases at high temperatures, posing risks to the environment and human health. Therefore, increased environmental awareness has prompted many manufacturers and industry standards to adopt halogen-free materials to reduce these potential risks. Halogen-free products are crucial for enhancing consumer safety, protecting the environment, and complying with environmental regulations in certain countries and regions (such as the EU's RoHS directive). Halogen-free standards typically require the total halogen content in materials to be below a certain proportion, for example, the halogen-free circuit board standard defined by IEC 61249-2-21 requires the content of chlorine and bromine to be below 0.09%, and the total halogen content must be below 0.15%.
The United States Energy Star certification is an environmental program aimed at promoting the use and production of energy-efficient products. This is a voluntary certification. Some major brands use this certification to promote the energy efficiency of their products. The program is jointly managed by the U.S. Environmental Protection Agency (EPA) and the U.S. Department of Energy (DOE), providing a recognition mark for energy-efficient products in the market. The Energy Star label is a trusted symbol indicating that a product meets government-mandated standards for energy efficiency. These products typically use less energy than non-certified products, helping to reduce greenhouse gas emissions and other environmental impacts while saving consumers on energy costs. Energy Star certification covers a wide range of product categories, including household appliances, office equipment, lighting, HVAC systems, building materials, and electronics. Manufacturers must undergo a series of energy efficiency tests and meet or exceed Energy Star's efficiency criteria to use the Energy Star label on their products. For consumers, choosing Energy Star certified products is a simple and effective way to reduce energy consumption, lower electricity bills, and help protect the environment. For manufacturers, obtaining Energy Star certification not only enhances product market competitiveness but also demonstrates their commitment to environmental protection and sustainable development.
Not possible, certification is required after the hardware and software are basically finalized, usually during the DVT stage. There is concern that hardware and software revisions may affect the test report. The subsequent certification report will also be used for customer inspection and product consistency in cooperation.
Germany's GS certification mainly focuses on safety testing, and the required documents are as follows: 1. Label; 2. Manual (English, German); 3. Circuit schematic; 4. PCB Layout and silk screen diagram; 5. Exploded view; 6. BOM table corresponding to the exploded view; 7. List of key components and certificates and specifications; 8. Factory audit cooperation to provide relevant quality system documents and production documents.
2402MHz-2480MHz.
TUV SÜD is a leading international technical service provider headquartered in Munich, Germany, established in 1866. It offers testing, certification, auditing, and consulting services, particularly in the fields of industry, transportation, and consumer products. TUV SÜD is renowned for its expertise in safety, quality, environmental protection, and cost-effectiveness. TUV SÜD's services are extensive, including not only product certification and testing but also management system certification, industrial services, training, and knowledge services. Its goal is to help companies optimize technology, systems, and expertise in the globalization process, ensuring that products and services comply with international standards and regulatory requirements.
The firmware in the adaptive module is not fixed frequency firmware and cannot be used for fixed frequency testing. It is used for testing adaptation and reception blocking, commonly used in CE certification. The module will have an RF cable soldered for connection to a spectrum analyzer, CMW500, etc. The module needs to have serial port lines: VCC, GND, RX, TX, connected to a USB serial port board, and through the USB serial port board connected to a computer, commands are sent via serial software to control the module. Devices with EIRP ≤10dBm can be exempt from adaptive testing. For our company's Bluetooth modules, all are low-power Bluetooth with power less than 10dBm, so adaptation testing is not required.
UKCA (United Kingdom Conformity Assessed) is a new UK product marking used to indicate that products comply with the regulations and legal requirements of the UK market. This marking came into use on January 1, 2021, following the UK's exit from the European Union (Brexit), as a replacement for the EU's CE marking. The UKCA marking applies to most goods sold in England, Scotland, and Wales that previously required the CE marking. It covers a wide range of product categories, including toys, electrical equipment, construction products, and personal protective equipment. Manufacturers need to ensure that their products comply with applicable UK technical regulations and undergo the appropriate conformity assessment procedures when necessary. If a product requires third-party assessment, this assessment must be carried out by a UK-recognized body. Although the UKCA marking is now in effect, the UK government has provided a transition period to allow businesses time to adapt to the new requirements. During the transition period, for most products, the CE marking is still accepted in the UK market.
The battery UN 38.3 report refers to a series of tests and evaluations conducted according to Section 38.3 of the United Nations Manual of Tests and Criteria, with the aim of ensuring the safety of lithium batteries during transportation. At the same time, the battery's UN 38.3 report is also an essential document for conducting transportation identification tests for the entire device. Lithium batteries, due to their high energy density and light weight, are widely used in various portable electronic devices, but they also pose risks of overheating and combustion, especially when subjected to mechanical damage, overheating, or circuit shorting. Therefore, the UN 38.3 test has become a mandatory standard for the global transportation of lithium batteries, whether they are standalone batteries or installed in devices, they must pass these tests to be allowed for transportation. The UN 38.3 tests include: Altitude simulation test: Simulates pressure changes during flight. Temperature cycling test: Battery performance under varying temperature conditions. Vibration test: Simulates vibrations that may be encountered during transportation. Shock test: Checks the safety of the battery after impact. External short circuit test: Ensures the battery does not overheat under short circuit conditions. Impact/crash test: Tests the safety of the battery after physical impact. Overcharge test: Verifies battery performance under overcharge conditions. Over-discharge test: Checks the safety of the battery in an over-discharge state. Mechanical test: Ensures the mechanical strength of the battery. Batteries that pass the UN 38.3 tests will receive a test report proving they comply with international transportation regulations. This report is usually a necessary document for the air or sea transport of lithium batteries, and without it, the batteries may not be transported.
Zigbee Alliance certification refers to a certification issued by the Zigbee Alliance to verify whether a product complies with Zigbee standards, ensuring interoperability between products. The Zigbee Alliance is a global non-profit organization composed of hundreds of companies, aiming to promote Zigbee technology based on the IEEE 802.15.4 standard, which is a technology for short-range, low-power wireless communication. The purpose of Zigbee Alliance certification is to ensure that devices using this technology can be compatible and work effectively together worldwide. This is especially important for devices in fields such as smart homes, industrial automation, and energy management, as these fields rely on seamless communication between different devices. To obtain Zigbee Alliance certification, products need to pass a series of tests designed to verify whether the devices meet the technical standards and protocols set by the alliance. This includes tests in areas such as hardware, software, security, and interoperability. Products that pass Zigbee Alliance certification can use the Zigbee logo on their devices, indicating that they have been verified to meet the standards and can seamlessly interact with other Zigbee-certified products. For manufacturers, this is an important market advantage as it enhances consumer confidence in product compatibility and reliability.
SRRC new standard MIIT No. [2021] 129 document has very strict requirements on the conducted spurious of the sideband. The original manufacturer adjusted the transmission characteristics of channel 13 (modified the spectrum template and reduced power) to meet the standard requirements in response to this regulation. Therefore, there are two firmwares, and the application uses the country code setting to make the application emit the spectrum required by China.
The term must refer to "information technology equipment and household appliances" of the same series products that embed wireless LAN (including Bluetooth), public mobile communication terminals (including NB-IoT, eMTC) "restrictive non-independent operation use radio transmission modules". Restrictive modules need to obtain an SRRC certificate. "Same series products" must simultaneously meet the following three principles: 1. The product's use and function are completely identical; 2. The product's appearance is roughly the same (such as color changes, slight changes in product size, etc., appearance changes that do not affect the product's RF performance); 3. The "restrictive non-independent operation use radio transmission module" embedded in the series products has obtained a model approval certificate.
For members who have paid the annual fee, each model is approximately 600USD.
HS CODE, the full name is Harmonized System Code, is an international standardized system for the classification and coding of goods. It is formulated by the World Customs Organization (WCO) and is used to uniformly classify and define goods in international trade to facilitate effective management and supervision by customs authorities of various countries. HS CODE consists of numbers, with the first two digits representing the chapter, the middle two digits representing the heading within the chapter, and the last two digits representing the specific item of the goods. Countries can add more digits to the HS CODE based on their own needs for more specific classification. In terms of product certification, the role of HS CODE is mainly reflected in the following aspects: 1. Product classification: HS CODE helps enterprises and customs quickly and accurately identify the category of goods to determine whether specific product certification is required. 2. Tariffs and tax rates: Through HS CODE, the applicable tariff rate for goods can be determined, as well as whether preferential rates under certain trade agreements are enjoyed. 3. Trade statistics: HS CODE is used for the collection and analysis of international trade statistical data, helping governments formulate trade policies and conduct market research. 4. Import and export control: HS CODE is used to identify goods that require special licenses, quotas, or are prohibited from import and export. 5. Risk management: Customs use HS CODE to conduct risk assessments on import and export goods to implement effective regulatory and control measures.
Thread Alliance certification is a certification service provided by the Thread Group to ensure that products meet the standards of the Thread network protocol. Thread is an IP-based, low-power, wireless Internet of Things (IoT) network protocol designed to connect and control various devices in the home, such as smart light bulbs, door locks, thermostats, and more. The Thread Alliance is a non-profit organization composed of industry-leading companies, aiming to promote products and services based on the Thread protocol. Their goal is to ensure that products from different manufacturers can seamlessly integrate and communicate, providing consumers with a secure, reliable, and easily expandable smart home experience. To obtain Thread Alliance certification, products must undergo a series of tests that verify the product's interoperability, security, reliability, and compliance with Thread technical specifications. This includes verifying whether the device can correctly join the Thread network, communicate with other devices in the network, and meet Thread's security requirements. Certified products can use the Thread certification mark on their packaging and marketing materials, indicating that the product has been verified to work reliably in a Thread network. For manufacturers, this certification helps enhance their product's competitiveness in the market and provides consumers with confidence, knowing that the devices they purchase will be able to interoperate with other Thread-certified products.
Need to redo the certification, and any changes in hardware require filing for record.
Korean certification bodies do not accept restrictive modules and wireless chips to apply for KC certification, with the aim of avoiding non-compliant references in finished products. Because restrictive modules and wireless chips lack shielding covers or integrated antennas, it is impossible to ensure that the RF performance of the finished product can also meet regulatory requirements. Complete modules (refer to the FCC's definition of complete modules) with shielding covers and fixed antennas can ensure that the RF of the whole machine remains consistent with the module.
Indoor use of electronic product plastic enclosures and accessories: Mandatory ban on the use of organic halogen flame retardants starting in 2027. Outdoor use of electronic product plastic enclosures and accessories: Mandatory reporting to the Ministry of Ecology for intentional use of organic halogen flame retardants starting in 2024. Determination method: If a total bromine concentration of over 1,000 ppm is detected in the homogeneous material, it indicates intentional addition of organic halogen flame retardants; If a total chlorine concentration of over 1,000 ppm is detected in the homogeneous material, it indicates intentional addition of organic halogen flame retardants; If a total fluorine concentration of over 1,000 ppm is detected in the homogeneous material, and the total phosphorus concentration is below 5,000 ppm, it indicates intentional addition of organic halogen flame retardants. Reference information from SGS and TUV SUD: 1. SGS information link:https://www.sgsgroup.com.cn/en-cn/news/2023/06/safeguards-6923-washington-state-adopts-final-rule-under-safer-products-program 2. TUV SUD consultation link:https://www.tuvsud.com/en-gb/e-ssentials-newsletter/consumer-products-and-retail-essentials/e-ssentials-4-2023/usa-washington-state-adopts-rule-for-safer-consumer-products.
Certification is not mandatory, and wireless products can be sold without certification. However, the Wi-Fi CERTIFIED trademark or text identifiers (such as Wi-Fi Protected Setup, Wi-Fi Direct, Miracast, etc...) cannot be used in market promotions, packaging, or product documentation. These CERTIFIED trademarks are owned by the Wi-Fi Alliance and require certification to be used on products. The Wi-Fi Alliance recommends certification to verify interoperability between wireless products.
Frequency-Hopping Spread Spectrum (FHSS) equipment is a wireless communication technology that transmits signals by rapidly hopping between multiple frequencies within a predetermined time. This technology can provide higher communication security because the signal is not fixed on a single frequency but hops between multiple channels, making it more difficult to be interfered with or intercepted. The working principle of FHSS technology is to spread the data signal over multiple narrowband carriers, which change frequency across the entire available frequency band according to a specific algorithm. The hopping pattern is pseudo-random, so only the transmitting and receiving devices know the correct hopping sequence to maintain synchronization and communicate correctly.
O-QPSK.
Zigbee Alliance certification does not support module forensics, and Zigbee Alliance certification must be obtained by the end product. Because different Zigbee finished products have different functional characteristics clusters, different clusters have different test cases. The SDK on the module cannot cover all categories of functions, and the CSA Alliance also has strict control over the certified appearance of certified products. When there are significant changes in the product appearance and motherboard, re-testing and certification are required.
The FCC certification in the United States is a certification issued by the Federal Communications Commission (FCC). It is a test and certification for the radio and electromagnetic compatibility of electronic products sold in the U.S. market. The FCC is responsible for regulating radio and electromagnetic waves within the United States to ensure that various electronic devices do not interfere with radio communication networks. FCC certification is mainly divided into two categories: FCC ID certification: This is primarily for wireless transmitting devices, such as mobile phones, wireless routers, etc. These devices need to obtain an FCC ID number before being sold on the market, and the corresponding FCC ID number must be marked on the product nameplate. This process involves testing the product to ensure it does not cause harmful interference to radio services. FCC DoC (Declaration of Conformity) certification: This is for non-wireless transmitting electronic products, such as computers, televisions, etc. These devices must meet the electromagnetic compatibility requirements specified by the FCC. Many radio application products, communication products, and digital products require FCC approval to enter the U.S. market. If a product has both wireless and non-wireless functions, the standards involved in both types of certification need to be tested.
No, it is necessary to burn a dedicated fixed frequency test firmware.
DEKRA (Deutscher Elektrotechniker-Technischer Überwachungsverein) is a global professional organization that provides safety inspection and certification services. Founded in 1925 and headquartered in Stuttgart, Germany, DEKRA is currently one of the largest technical service providers in Europe and operates worldwide. DEKRA's services mainly focus on vehicle inspection, industrial inspection, product testing and certification, personnel certification, and management system certification.
1pc conduction fixed frequency (requires burning BQB test firmware). 2. Requirements are as follows:.
2-3pc normal samples.
China's Network Access Permit certification, commonly referred to as the Network Access Permit (NAP), is a certification system overseen by the Ministry of Industry and Information Technology (MIIT) of China. This certification primarily targets telecommunications equipment, especially those devices that need to connect to the telecommunications network, such as mobile phones, data cards, wireless modules, etc. The purpose of the Network Access Permit certification is to ensure that these devices meet national standards and regulations in terms of technical performance, safety, electromagnetic compatibility, and do not cause interference or damage to the telecommunications network, while also protecting the legitimate rights and interests of users. To obtain China's Network Access Permit certification, manufacturers need to submit detailed technical information of the relevant equipment and send product samples to designated testing laboratories for a series of tests. These tests evaluate key parameters such as the device's radio transmission characteristics, reception sensitivity, and anti-interference capability. Once the tests are passed and the corresponding test reports are obtained, manufacturers need to submit an application to the Ministry of Industry and Information Technology. After review and approval, they can obtain the Network Access Permit certificate. Only devices with the Network Access Permit certificate can be sold and used in the Chinese market. This certification is an important step for market access of telecommunications-related equipment in China, for manufacturers and importers wishing to sell telecommunications equipment in the Chinese market.
TAF (Taiwan Accreditation Foundation) is the authoritative accreditation body in Taiwan, established in 2003, formerly known as the China National Bureau of Standards (CPS, established in 1950). TAF is an independent non-profit organization primarily responsible for the accreditation and recognition of laboratories, inspection bodies, certification bodies, medical laboratories, etc. TAF's accreditations are widely accepted by many countries and regions worldwide, especially in the Asia-Pacific region. TAF is a member of the International Laboratory Accreditation Cooperation (ILAC) and the International Accreditation Forum (IAF), participating in multiple international mutual recognition agreements, and the test and certification results of its accredited laboratories and certification bodies are recognized globally.
Vietnam MIC certification refers to a type of certification that complies with the regulations of the Ministry of Information and Communications (MIC) of Vietnam. MIC is a department of the Vietnamese government responsible for formulating and implementing regulations and standards regarding telecommunications equipment, radio, and information technology products. MIC certification mainly targets devices that need to use the radio spectrum or connect to the telecommunications network, including but not limited to mobile phones, wireless routers, Bluetooth devices, radio stations, and other communication equipment. The purpose of this certification is to ensure that these devices do not cause interference to Vietnam's communication network and comply with national safety and technical standards. To obtain MIC certification, manufacturers or importers usually need to submit the technical specifications and test reports of the product and undergo testing by a laboratory or certification body authorized by MIC. The testing content may include testing of parameters such as the frequency, power, and radiation of wireless signals, as well as the product's electromagnetic compatibility (EMC) assessment. Products that pass MIC certification will be granted the MIC mark, indicating that the product has been verified and can be sold and used in Vietnam. For manufacturers of radio and telecommunications equipment wishing to enter the Vietnamese market, complying with MIC's certification process is very important.
Wireless products entering India need to obtain WPC certification. The Wireless Planning & Coordination Wing, established in 1952, is India's national broadcasting agency. Its main tasks are issuing radio licenses, allocating and monitoring spectrum, and it is under the Ministry of Communications and Information Technology. Wireless products need to obtain WPC certification before entering the Indian market. India's frequency bands are divided into free open and not yet open categories. For free open bands, such devices only need to apply for an ETA (Equipment Type Approval) certificate (applicable to local area network products such as Wi-Fi, Bluetooth, Zigbee, SUB-1G, and accepts EU EN standard reports for conversion); for other bands that are not free open, a License must be applied for. Both ETA and License holders must be locally registered companies.
Japan's mandatory safety certification, proving that electronic and electrical products have passed the safety standard tests of Japan's Electrical Appliance and Material Safety Law or international IEC standards. 116 types of Class A products use a diamond-shaped mark, and 340 types of Class B products use a circular mark. Class A: wires and cables, fuses, wiring devices (electrical accessories, lighting equipment, etc.), current limiters, transformers, ballasts; electric heating appliances, electric power application machinery and appliances (household appliances), electronic application machinery and appliances (high-frequency depilators); other AC electrical machinery and appliances (electric insect killers, DC power devices), portable engines. Class B: simple wiring conduits and junction boxes, simple single-phase motors between 100V-300V, household electric heating products, household electric or electronic products, civilian or household products using light sources, household and commercial electronic products, other electrical products between 100V-300V.
BQB Alliance Membership Application Address:https://www.bluetooth.com/develop-with-bluetooth/join/membership-benefits/. For companies with annual revenue 1 million USD, the annual fee is 10,350 USD. For companies with annual revenue 1 million USD, the annual fee is 48,300 USD. The cost for annual fee members to purchase a DID is 5,520 USD, and for non-annual fee members, the cost is 11,040 USD.
EIRP (Effective Isotropic Radiated Power) is a parameter that measures the total radiation capability of a wireless transmission system. EIRP takes into account the antenna gain and the transmitter's output power to estimate the radiated power of the antenna under the assumption of an isotropic antenna. It is a theoretical value used to compare the transmission efficiency of different antenna systems. The calculation formula for EIRP is usually: EIRP (dBm) = Transmitter Power (dBm) + Antenna Gain (dBi) − Feed Line Loss (dB) where: Transmitter Power refers to the power output at the transmitter's conductive port. Antenna Gain refers to the gain of the antenna relative to an ideal isotropic antenna, expressed in dBi. Feed Line Loss refers to the cable loss between the transmitter and the antenna. EIRP is an important parameter because radio communication regulations often limit the maximum value of EIRP to prevent interference with other wireless services. The limitation of EIRP also helps ensure the reasonable use and management of radio waves, especially in frequently used bands such as commercial radio, satellite communication, and mobile communication.
India's STQC certification is a product certification issued by the Standardisation, Testing and Quality Certification (STQC) Directorate. STQC is an agency under the Ministry of Electronics and Information Technology of India, responsible for providing quality assurance services, including testing, calibration, certification, and standardization services. STQC certification covers a wide range of electronic and IT products, ensuring that these products meet national and international quality and safety standards. It primarily focuses on the performance, reliability, safety, and electromagnetic compatibility of products. Products that obtain STQC certification must undergo a series of tests and evaluations, which are usually conducted in STQC-recognized laboratories. Products that successfully pass the tests are awarded the STQC certification mark, indicating that the product meets the relevant quality and safety standards. STQC certification is regarded as a mark of quality and reliability both domestically and internationally, and for manufacturers wishing to sell electronic and IT products in the Indian market, STQC certification is an important qualification. Additionally, STQC collaborates with other international certification bodies to ensure that products made in India are recognized in the global market.
SGS (Société Générale de Surveillance) is the world's leading inspection, verification, testing, and certification company, headquartered in Geneva, Switzerland, and was founded in 1878. SGS provides a comprehensive range of services designed to ensure that operations and products of organizations comply with international standards, regulatory requirements, and customer expectations. SGS's main advantage is in the field of environmental testing, such as ROHS and REACH. SGS's certification services cover multiple industries, including agriculture, mining, petrochemicals, consumer goods, industrial manufacturing, life sciences, and transportation. SGS's services help companies improve efficiency, ensure the quality and safety of products and services, and also help companies build trust and meet regulatory requirements in the global market.
Brazil INMETRO certification is a product certification issued by the National Institute of Metrology, Standardization and Industrial Quality (Instituto Nacional de Metrologia, Qualidade e Tecnologia, abbreviated as INMETRO). INMETRO is an autonomous agency of the Brazilian government responsible for supervising and controlling the quality and safety standards of products, including metrology, product certification, and technical regulations. INMETRO certification ensures that products meet Brazil's safety, quality, and efficiency standards. The certification process may include product testing, factory inspections, compliance assessments, and ongoing monitoring of the products. For certain product categories, such as electrical equipment, toys, automotive parts, etc., INMETRO certification is a necessary condition for sale in the Brazilian market. Products that pass INMETRO certification will be awarded the INMETRO mark, indicating that the product complies with Brazilian regulatory requirements. This certification is crucial for enhancing consumer confidence in product safety and quality and is a key factor for manufacturers to enter and compete in the Brazilian market.
CMA (China Metrology Accreditation) is the abbreviation for China's metrology certification. It is a professional organization authorized by the Certification and Accreditation Administration of the People's Republic of China (CNCA), responsible for certifying various metrology testing laboratories. Metrology certification is a means of confirming that a laboratory can perform accurate measurements and tests according to national standards, ensuring that the laboratory's test data is accurate, reliable, and meets national and international standards. The main responsibilities and services of CMA certification include: 1. Laboratory Capability Certification: Evaluate and certify the technical capabilities of laboratories to ensure that their testing and calibration services meet national and international standards (such as ISO/IEC 17025). 2. Quality Management System Certification: Ensure the effective operation of the laboratory's quality management system to improve the quality of testing and calibration work. 3. Supervision and Evaluation: Conduct regular supervision and evaluation of certified laboratories to ensure their continuous compliance with certification requirements. 4. Consultation and Training: Provide consultation and training services related to metrology certification for laboratories to help them improve their technical level and management capabilities. The CMA certification mark is an important symbol of the quality of laboratory metrology testing, indicating that the laboratory can provide testing services that meet national standards. For enterprises and consumers, choosing a CMA-certified laboratory for product testing can increase trust in the test results.
Main conditions to be met: 1. The module should have a data buffering/modulation unit; 2. The module's RF unit should have a complete shielding cover; 3. The antenna within the module can be a fixed antenna or a unique connecting line as the sole antenna. 4. Own power supply regulation; 5. The module should be able to be configured independently during testing.
TELEC certification is the mandatory certification for wireless equipment under Japan's Radio Law. TELEC stands for Telecommunication Engineering Center, which is an independent administrative agency responsible for the certification of radio equipment in Japan. The Japanese Radio Law requires that all radio equipment must undergo TELEC certification or confirmation before being sold or used, to ensure that these devices do not cause interference with radio communications and comply with Japan's radio and safety standards. This includes various wireless and RF devices such as mobile phones, wireless routers, Bluetooth devices, RFID devices, etc. The TELEC certification process typically includes steps such as technical document review, sample testing, and compliance declaration. Once the equipment is certified, it will receive a certification number, which must be marked on the product for identification by regulatory authorities and consumers. For companies wishing to import or sell radio products in the Japanese market, obtaining TELEC certification is a necessary step. TELEC certification is also known as MIC R mark certification.
If the product's Zigbee EIRP transmission power is greater than 10dBm, it needs to apply for SRRC certification as a 2.4G spread spectrum communication device; if the EIRP transmission power is less than or equal to 10dBm, it is considered a low-power product. The manual must list the following 8 items according to the requirements of Announcement No. 52 of 2019, and SRRC model approval certification is not required: (1) Complies with the "Catalog and Technical Requirements for Low-Power Short-Range Radio Transmission Equipment" as an F-class device; (2) Unauthorized changes to the usage scenario or conditions, expansion of the transmission frequency range, increase in transmission power (including additional installation of RF power amplifiers), or unauthorized changes to the transmission antenna are not allowed; (3) Must not cause harmful interference to other legitimate radio stations, nor claim protection from harmful interference; (4) Must accept interference from industrial, scientific, and medical (ISM) application equipment or other legitimate radio stations; (5) If harmful interference to other legitimate radio stations occurs, usage must be stopped immediately, and measures must be taken to eliminate the interference before resuming use; (6) When using low-power devices within the electromagnetic environment protection areas of aircraft and radio astronomy stations, meteorological radar stations, satellite earth stations (including telemetry, tracking, receiving, and navigation stations), and other military and civilian radio stations, airports, etc., the regulations of the electromagnetic environment protection and relevant industry authorities must be followed; (7) The use of all types of model remote controllers is prohibited within a 5000-meter radius area centered on the airport runway center point; (8) The environmental conditions of temperature and voltage for the use of low-power devices should refer to the product usage temperature and voltage ind.
If it is a single module solution, it can be referenced. If it is a multi-module solution, it cannot be referenced.
The IFETEL certification in Mexico is a type of certification issued by the Federal Telecommunications Institute (Instituto Federal de Telecomunicaciones, abbreviated as IFETEL), applicable to devices that need to use the wireless spectrum or connect to the telecommunications network. IFETEL is an independent regulatory body in Mexico responsible for regulating and promoting competition in the telecommunications and broadcasting markets. The purpose of IFETEL certification is to ensure that wireless and telecommunications equipment complies with Mexico's technical standards and regulatory requirements so that these devices can be safely used within Mexico without causing harmful interference to other communication services. To obtain IFETEL certification, manufacturers or importers typically need to submit technical documents and send product samples to a local laboratory recognized by IFETEL for testing. These tests evaluate key parameters such as the radio emission characteristics and electromagnetic compatibility of the equipment. Once the equipment passes these tests, it is granted IFETEL certification. Typically, IFETEL certification requires specific markings and numbers to be labeled on the product for identification by regulatory bodies and consumers. For companies wishing to sell radio and telecommunications equipment in the Mexican market, obtaining IFETEL certification is an important step to enter the market.
CE certification frequency is 2.412-2.472GHz, FCC certification frequency range: 2.412-2.462GHz.
BLE rate supports 2M fill in: ≤3M, others fill in: ≤2M.
Can be queried through:https://www.wi-fi.org/membership. Generally, for Wi-Fi module/product development, opening a Contributor level membership costs an annual fee of 25000 USD. For small and medium enterprises (annual revenue 10 million USD), it is 7725 USD per year.
CQC certification is a product quality certification issued by the China Quality Certification Centre (CQC). It is a professional certification body authorized by the Certification and Accreditation Administration of the People's Republic of China (CNCA), responsible for certifying various products to ensure they meet China's national standards (GB standards), industry standards, or enterprise standards. Products that generally cannot obtain CCC certification but wish to prove compliance with China's relevant national standards can opt for CQC voluntary certification. The general procedure for CQC certification is: type testing + factory audit. CQC certification covers multiple product categories, including electrical and electronic products, building materials, automotive parts, textiles, food-related products, etc. Products bearing the CQC mark indicate that they have passed CQC's quality and safety testing and meet the corresponding standard requirements. For enterprises, this is an important proof of product quality and safety, and for consumers, it is an important reference for purchasing and using products.
Apple MFi certification (Made for iPhone/iPod/iPad) is a certification program provided by Apple Inc. for third-party accessories that are compatible with Apple devices such as iPhone, iPod, and iPad. MFi certification ensures that these accessories meet Apple's performance standards and work safely and reliably with Apple devices. The MFi certification program covers a variety of products, including chargers, headphones, cables, speakers, game controllers, and more. Certified products can use the "Made for iPhone/iPod/iPad" logo on their packaging. To obtain MFi certification, manufacturers must participate in Apple's MFi licensing program and adhere to Apple's design, manufacturing, packaging, and compliance requirements. This typically includes using certified components, such as Lightning connectors with Apple-certified chips, and going through Apple's testing process to verify product compatibility and performance. For consumers, choosing MFi-certified products ensures that the accessories they purchase are compatible with their Apple devices and do not cause device damage or data loss due to the use of non-certified products. For manufacturers, MFi certification is an important market advantage that can enhance consumer confidence in their products.
No, they are not the same. Certified RF testing requires the product to be fixed in the test mode to achieve maximum transmission power and maximum duty cycle. Generally, fixed frequency firmware and adaptive firmware are needed. For specific details, please refer to the platform documentation: https://developer.tuya.com/en/docs/iot/description-of-fixed-frequency-prototype?id=Kaiuzueo0a6mf.
Matter certification is a type of certification for the emerging smart home interoperability standard "Matter" (formerly known as Project CHIP, or Connected Home over IP). Matter is driven by the Connectivity Standards Alliance (CSA, previously known as the Zigbee Alliance), and it is an open-source standard supported by Apple, Google, Amazon, and other companies. It aims to enhance compatibility and interoperability among smart home devices. The goal of the Matter standard is to provide a unified connectivity framework for smart home devices, allowing devices of different brands and types to more easily communicate and collaborate with each other, offering consumers a more seamless smart home experience. This includes a variety of devices such as lighting, locks, thermostats, doorbells, and sensors. To obtain Matter certification, products must pass a series of tests to ensure they meet the technical specifications of Matter. Certified devices can display the Matter certification mark, indicating that they support this new standard and are compatible with other Matter-certified devices.
Before ordering the module, you need to fill in the PPID and Product Data configuration information in the advanced features section. This information will be written into the module during authorization. If the configuration is not filled in, the pairing code will not be available.
The Zigbee firmware version occupies a total of 1 byte, with high, middle, and low positions occupying 2 bits, 2 bits, and 4 bits respectively. The maximum values that can be set for the high, middle, and low version bits are 3, 3, and 15, respectively. If any version bit exceeds its maximum value, it is considered an illegal version, and the high bit will be discarded (for example, 1.6.0 will be regarded as 1.2.0), which will result in OTA failure, and errors such as "firmware fingerprint verification failed" during module burning authorization.
Add the following registration code in app_dev_register.c: #definePRIVATE_ATTR_LIST\ {0x0000, ATTR_INT8U_ATTRIBUTE_TYPE, 1, (ATTR_MASK_TOKEN_FAST|ATTR_MASK_SINGLETON), 0, (UINT8_T)0x00 }, /*current positiong lift percentage*/\ {0xFFFD, ATTR_INT16U_ATTRIBUTE_TYPE, 2, (ATTR_MASK_READABLE), 0, (UINT8_T*)0x0002}, constTAL_ATTR_Tg_private_attr_list[]= { PRIVATE_ATTR_LIST}; #defineDEF_CLUSTER_PRIVATE_CLUSTER_ID(a) \ { CLUSTER_PRIVATE_TUYA_CLUSTER_ID, (TAL_ATTR_T*)&((a)[0]), GET_ARRAY_LEN((a)) }, Then add DEF_CLUSTER_PRIVATE_CLUSTER_ID(g_private_attr_list) to g_app_server_cluster_list.
Analysis: 1. You can view the unlocking methods added locally on the Bluetooth lock by using the app. 2. You can delete the local unlocking methods added by members other than the super administrator of the Bluetooth lock in the app. 3. You can modify the local unlocking methods added by members other than the super administrator of the Bluetooth lock in the app. Advice: Check that the unlocking method synchronization function is configured for the Bluetooth lock and takes effect.
Wi-Fi and Zigbee door locks use Greenwich Mean Time, while Bluetooth door locks use Unix time.
Analysis: The time on the lock is inaccurate. Advice: 1. Manually synchronize the time on the clock with that on the Tuya Cloud Platform or manually update the time on the lock. The operations may vary based on the lock brand. 2. If there is no manual way to update the time, you need to contact the business personnel responsible for the door lock integration to resolve it.
Different frequency bands have different rates: 868MHz: data transmission rate is 20Kb/s 915MHz: data transmission rate is 40Kb/s 2.4GHz: data transmission rate is 250Kb/s, actual rate: 2~5Kb/s Currently, Tuya only supports the 2.4GHz band.
Tuya-panel-kit is a component library for developing panel applications. It provides developers with a rich set of UI components and development tools to help them quickly build visually appealing and powerful panels.
There is no limit for the panel itself. It mainly depends on the limitations of the dp function points. For example, character type data should not exceed 255 characters.
First, add DP 22 as a duress alarm feature point in the product function definition (this DP is only available in the cloud, and the door lock does not need to report this DP data). Then, go to the door lock panel - Member Management, and add an unlocking method for members. You can enable it in the fingerprint or password unlocking methods.
Dear user, we are sorry for your inconvenience. You can click the "···" icon on the right side of the “All Device”and “Rooms”, and select the device display mode to be "list view" or "grid view". Note: The "list view" function is cancelled since the App version 6.0, and only the "grid display" is available.
Please contact Tuya staff to obtain the general docking firmware corresponding to the L511A module. Open the firmware burning tool FlashTools.exe, click "Browse..." to select the configuration file config_custom_usb.ini in the firmware burning package, as shown below: Operate the development board to enter download mode, the Com Port automatically recognizes the corresponding port, click "Download" to start downloading the general docking firmware, and the download progress information appears in the status bar, as shown below: "Download progress: 100%" appears in the status bar, indicating that the firmware download is complete. Restart the module to run the newly downloaded firmware.
Dear Customer, Thank you for your attention and support for our company. Our app is currently compatible with HarmonyOS 4.0 and below. For the HarmonyOS next system, we are actively investing resources and manpower for research and maintaining close cooperation with the Huawei HarmonyOS team. We are committed to ensuring a good user experience for HarmonyOS users. At present, we cannot disclose specific timelines. We will continue to monitor the launch situation of the HarmonyOS next system. Thank you for your understanding and support. If you have any questions or suggestions, please feel free to contact us. Thank you again for your trust, and wish you a pleasant life!
The Tuya Developer Platform offers two development methods: Panel MiniApp and RN panels (formerly SDK panels). Developers can choose the appropriate development method based on their business needs. Since the creation of RN panels (formerly SDK panels) is about to be phased out, Tuya will primarily support the Panel MiniApp solution in the future. Therefore, users are recommended to directly choose Panel MiniApp development. For detailed development guidelines, please refer to: Panel MiniApp.
Sandwich Development BoardTaobao Store: https://tuyasmart.taobao.com/ IoT platform purchase link: https://iot.tuya.com/purchase/store?page=1&tag=dev_board&q=&type=commodityName.
Up to 200 DPs can be added. DPs numbered 201 to 255 are system DPs.
Traditional infrared (IR) devices, such as televisions and air conditioners, typically rely on remote controls for operation. Although some modern appliances now support smart Wi-Fi control, many older devices still lack this functionality. To bridge this gap, universal remote controls have emerged. However, the capabilities of universal remotes are somewhat limited. To address this issue, the IR code library was introduced. By integrating with an IR code library, universal remotes can become compatible with a vast majority of IR devices, allowing users to operate these devices via their smartphones, including scheduling and various control methods. The continuous updating of the IR code library plays a crucial role in enabling more IR devices to become smart, highlighting its importance in the smart home ecosystem. In this context, we have introduced the Tuya Code Library. Tuya Code Library is a set of infrared code databases established by ourselves to improve the device capabilities of the Tuya infrared products and to facilitate cross-platform use. At the same time, we are increasingly enriching our Tuya code library to support more infrared devices. The Tuya Code Library not only expands the compatibility range of traditional devices but also provides robust support for their smart upgrades. By leveraging the Tuya Code Library, users can seamlessly transform traditional IR-controlled appliances into smart devices, thereby enjoying the numerous advantages of modern technology. This capability makes the Tuya Code Library an ideal solution for the smart upgrade of traditional devices, significantly enhancing user convenience and the level of intelligence in their daily lives.
The dynamic password is valid for 5 minutes, while the temporary password can be set by the user. The dynamic password is generated by the app using an algorithm based on the cloud's time, and the module's password is also calculated based on the MCU's time. When the dynamic password you enter matches the one calculated by the module, the door lock opens, which means it does not rely on the cloud and can be used even when offline. This also indicates that the time on your MCU must be accurate, and there is a command to obtain the local time. The temporary password must be obtained by the module from the cloud and issued to the lock when connected to the network.
Yes. Contact a Tuya business manager to obtain a solution.
Sub-GHz modules are suitable for developers in the following fields: IoT: Suitable for communication module needs of IoT devices, such as smart home, smart city, smart agriculture, etc. Industrial Automation: Applicable to remote monitoring and data transmission in industrial automation control systems, improving production efficiency and reducing costs. Security Systems: Can be used for networking and data transmission of security devices, enabling interconnection and remote monitoring functions. Logistics Tracking: Suitable for communication module needs of logistics tracking devices, enabling real-time monitoring and management of cargo location and status. Sub-GHz modules offer long-distance communication and low power characteristics, meeting the needs of developers in different fields and providing a reliable solution for remote communication and networking of devices.
No, the dimming switch needs to determine when to perform dimming through the zero-crossing detection signal.
According to your description, it is generally caused by insufficient power supply. When the router is disconnected, the power consumption of the Wi-Fi module can increase to over 120mA. If the power supply is insufficient, it will cause the module to reset, leading to relay operation issues.
The logic for remotely unlocking a Wi-Fi door lock is as follows: Data contained in a remote unlock request does not represent the countdown time. Instead, the MCU sends data values, for example, 60, 59, and 58, every second to ensure the countdown effect. The app panel displays a remote unlock button until it receives a 0. If you tap the button in the app to open the door or reject the door unlock command before the countdown timer reaches 0, the hardware will execute your instruction and report 0 to the server to remove the button from the app. That is, the panel does not count down the time. After you initiate a remote unlock request, the panel will display an unlock button until you exit the page or it receives a 0. If the door is opened, a remote door unlock record will be reported independently. The preceding logic enables the MCU to control display and removal of the button in the app at any time. You can define the MCU report logic to achieve different rules and effects based on your requirements. For example, if you require a request waiting period of 180s, you can configure the MCU to deliver data values indicating the countdown timer at 1s or 2s intervals. If you want to retain the button in the app when the countdown timer reaches 60s and the app rejects the door unlock request, you can enable the MCU to send "false" before the countdown timer reaches 60s. If the app panel receives "false" within 60s, it will report 0 to end the request.
Offline pop-ups in the all-in-one and studio panels are the default and changing the offline popup style is not currently supported. However, you can change the corresponding multilingual text in the pop-up window under Product Multilingual - Public Entries.
You need to wait for the device to connect to the network. Once the module's network status indicates a successful connection to the cloud, the command to obtain the local time becomes effective.
No, you need to purchase two apps first before you can link the account systems between the two apps.
Dear user, we are sorry for your inconvenience, please follow the steps below to troubleshoot the problem. Play Back function/recording function/upload video to cloud storage and SD card： Check whether you have inserted a memory card or purchased the Cloud Storage for Videos service. If your camera has been inserted with a memory card, please directly control the camera to format the SD card in the App. If the formatting fails, and after several attempts, the formatting still fails, it means that the storage format of your SD card is not FAT32 format. It is recommended that you format the SD card into FAT32 format on your computer. If the SD card still cannot be recognized, there should be a problem with the SD card, please replace the SD card; Please choose a high-speed SD card that is compatible with the camera, otherwise the recorded video quality will be poor and accompanied by noise, and the camera will not be able to continue recording due to overheating of the memory card; After insert the SD card, you can find the "storage settings" in the device settings page, and turn on the "recording switch" in it, so that the device will automatically record video (there are two recording modes：event recording and continuous recording), after a period of time Click "Playback" on the camera interface directly to view the record in the SD card. After purchasing cloud storage, it is recommended to enable the motion detection feature. After a period of time, when the camera detects motion, it will automatically record video. You can click on the cloud storage option on the camera interface to view the recorded videos. The "recording" function displayed on the camera interface does not record video to SD card or the cloud, but uses the phone's screen recording function, so that you can record the video which in "Playback", and the video is stored locally on your phone storage； If you find that the recording in the playback is not coherent, it may be caused by unstable networ.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Pairing a Bluetooth device needs to be added in our App, not the Bluetooth adding interface of the phone. Your iphone must be connected to the network, when paring a Bluetooth device, (because the Bluetooth device needs to be registered on the cloud server to be added successfully). If you use an Android phone, you must open the App's location permission. The device may have been added, it is recommended to reset the Bluetooth device and add it again. Whether the distance between the Bluetooth gateway and the Bluetooth device is moderate (less than 3 meters), it is recommended to be as close as possible (if there is no Bluetooth gateway, you can skip it, just connect to the phone directly). Check whether there are other users around using the Bluetooth device (the Bluetooth device can only be controlled and used by one user at the same time due to its characteristics, and it will be offline when other users are using it). The Bluetooth device you added is not our product. Bluetooth devices have certain private protocols, so other brands of Bluetooth devices cannot be added to our App (even if they are added successfully, they cannot be controlled). If all of the above conditions have been ruled out and your device still cannot connect to the Internet, you can provide us with your App account, and we will arrange for a professional engineer to conduct an in-depth investigation for you.
Adding a Zigbee Wireless Gateway: Open the app and click the "+" button in the top right corner of the homepage. On the "Select Device Type" page, find "Gateway Control" and select the appropriate gateway (Zigbee). Choose your home’s 2.4GHz Wi-Fi band, and enter the network name and Wi-Fi password. Follow the product manual and app instructions to reset the Zigbee gateway (usually by pressing and holding the reset button on the Zigbee gateway for 5 seconds until the indicator light flashes; refer to the manual for specifics). Once added successfully, you can find the Zigbee gateway in the homepage list. Adding a Zigbee Wired Gateway: Open the app and click the "+" button in the top right corner of the homepage. On the "Select Device Type" page, find "Gateway Control" and select the appropriate gateway (Zigbee). Connect the gateway to power and link it to your home router, ensuring that your phone and the gateway are on the same network. Confirm that the indicator light is solid. Once added successfully, you can find the Zigbee gateway in the homepage list. Adding Zigbee Sub-devices: Open the app and click the "+" button in the top right corner of the homepage. On the "Select Device Type" page, find the corresponding category and select the appropriate device (Zigbee). Next, choose the Zigbee gateway you want to add the device to (the Zigbee gateway should be no more than 5 meters away from the sub-device). Follow the product manual and app instructions to reset the Zigbee sub-device to pairing mode (usually by pressing and holding the reset button on the Zigbee sub-device for 5 seconds until the indicator light flashes; refer to the manual for specifics). Once added successfully, you can find the Zigbee sub-device in the homepage list.
Removing the entry for creating RN panels does not affect consumer end. If there are issues with historically created RN panels, support for fixing problems and iterations is still provided.
Currently, the Homekit SDK does not support beacon remote control, so neither the no-code development nor the customized solution can support beacon remote control.
Yes. When you create a Bluetooth product, select the CCT solution as the color temperature adjustment mode in hardware development settings.
The no-code development solution is a unique zero-code solution from Tuya, which can accelerate the process of smartification for customer products. Currently, the no-code development solution for Wi-Fi lighting covers a variety of hardware solutions in multiple fields, including light sources, lighting fixtures, ambiance, and professional areas. You can also learn more through the Solution Center.
Shipped devices need to support advanced features such as human-centric lighting, latitude and longitude biorhythm, color temperature value configuration, light adjustment, and scene library. Two conditions need to be met: 1. The firmware supports advanced features after the device OTA; 2. The device to be upgraded can be found through the order query to the device uuid; If the conditions are met, you can pay for the corresponding uuid through the Tuya backend to support related advanced features.
Voltage 3.3V, deviation 5%, continuous current above 200mA, peak current 500mA, ripple voltage less than 100mV.
The module currently has no feedback signal of the cloud to the MCU, and the reported data is stable. Retransmission can be done but there is no need to do too many times. Because if the DP data does not change, it will be filtered out by the module. If you want to know if the DP has been reported successfully, you can use the 0x22 command word. The protocol can be referred to: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-16-Report%20status%20(record-type)%20(0x34%20%26%200x0b).
Please check whether the mode id and manufacturer name are filled in correctly. When a sub-device joins the network, the gateway reads 6 attributes from the sub-device's basic cluster, including manufacturer name and mode ID. The manufacturer name for Tuya's standard version devices is composed of the capability value field + PID field. The manufacture name for connecting to the Tuya gateway is selected based on the capability value, with a fixed prefix of_TZ, and the capability value is determined by 4 bytes. Example: _TZ3000_: Supports capability values of bit0 and bit1 in byte0. _TZ3210_: Capability values of bit0 and bit1 in byte0, bit1 in byte1, and bit0 in byte2. Mode ID can be confirmed through the Zigbee Docking Specification.
Bluetooth LE devices are controlled directly through a point-to-point connection with a mobile phone or gateway and do not network with other devices, making group control impossible.
The access to view the historically created RN panels will not be affected and can be used as usual. You can still enter to view the historically created RN panels and maintain them.
Due to some technical limitations and uncontrollable factors associated with the RN technology, such as: 1. Third-party package management and native dependency issues: RN projects typically rely on many third-party libraries, which may have compatibility issues during RN version upgrades, especially when there are breaking changes. We cannot guarantee that all RN projects will remain unaffected. To address this issue, we have designed Kit capabilities in MiniApp to tackle compatibility challenges. 2. Changes in the community and ecosystem: RN relies on support from the open-source community, and the maintenance of certain key libraries may be unstable or cease updates, posing potential risks. In contrast, MiniApp can rely more on the built-in capabilities provided by the official source or the web or MiniApp ecosystem from the open-source community, ensuring greater stability. 3. Meta's support strategy: RN is led by Meta, and if Meta changes its support strategy for RN, it could impact the development of the entire ecosystem. MiniApp is led by Tuya officials, and as a core business system of Tuya, the device panel business will continue to receive official support and assurance. 4. Platform updates: Updates to iOS and Android platforms may introduce new APIs and changes, requiring RN to keep pace with these updates, during which incompatibilities may arise. MiniApp, being led by Tuya officials, can prioritize responses to updates in iOS and Android platform systems, ensuring compatibility and stability. 5. Compatibility issues with RN version upgrades: Each upgrade of an RN version can lead to incompatibility issues. Given the large number of existing panels and developers at Tuya, it is not feasible to update existing RN panels. At the same time, in MiniApp, we offer a wealth of capabilities that do not exist or cannot be implemented in RN. For specifics, please refer to our API documentation (https://developer.tuya.com/en/miniapp/develop/ray/api/base/framework/g.
A hardware device powered by Tuya's dual-direct-connect solution can directly and simultaneously connect to Tuya‘app and another platform: Amazon Alexa, Google Home, or Apple HomeKit.
The MQTT logic determines that the module is offline if there is no response after 3 heartbeats, i.e. 3min.
In Tuya standard module MCU SDK-based development, Tuya provides you with matching firmware. It can be regarded as a low-code MCU integration solution. In Tuya standard module SDK development, your R&D team needs to develop the firmware itself. It can be regarded as a multi-code module SDK integration solution. The price difference is the cost of purchasing the firmware. If the module cannot implement your required functions, you can use an external MCU to implement these functions and use the module for pairing and communication. If the module hardware meets your development requirements while you want to develop functions yourself, you can select the module SDK development mode.
The no-code development solution for Wi-Fi sockets currently supports up to 7 ways. If you need more than 7 ways, you can create a general integration solution with MCU. You can make up to 25 DP points, if you only need switches, you can have up to 25 ways.
Statement: Whether multiple MCUs under one PID support OTA depends on the firmware version of the module. If developers are unsure, they can submit a ticket for consultation. 1. Platform Configuration When uploading firmware, you need to select extended firmware and choose the corresponding channel number. 2. Configure the "ma" Field (Optional), Cancel the "vt" Field Explanation: The ma field is added in the new version of the firmware. The old version has the vt field configuration, which has now been removed. This field indicates the firmware information of the subsidiary MCU. "t" is the channel number, range (10~19), and "v" is the version number. Example 1: If there is a subsidiary MCU, the channel is 10, and the version is 1.0.0, then "ma":[{"t":10,"v":"1.0.0"}] Example 2: If there are two subsidiary MCUs, channel 10 corresponds to version 1.0.0, and channel 11 corresponds to version 2.0.0, then "ma":[{"t":10,"v":"1.0.0"},{"t":11,"v":"2.0.0"}] Reference Protocol: https://developer.tuya.com/en/docs/mcu-standard-protocol/MCUSDK-wifi-base?id=Kd2bxu84567gk#title-5-Query%20product%20information%20(0x01) 3. Upgrade Start (Upgrade Package Size Notification) 0x0a Command Description: The upgrade start method includes automatic and manual upgrades. When in automatic upgrade mode, the module detects that the cloud MCU has a new version of the firmware and automatically starts the interaction process with the MCU upgrade package. When in manual upgrade mode, the module initiates the interaction process with the MCU upgrade package only after confirmation through the APP. Module sends: Field Length (byte) Description Frame Header 2 0x55aa Version 1 0x00 Command 1 0x0a Data Length 2 0x0004/0x0008 Data 4 Firmware package byte count, unsigned int, big-endian Data 1 MCU type: 10~19 Data 3 Reserved: Reserved for extension Checksum 1 The result of summing each byte from the frame header and taking the remainder of 256 Example: 0x55aa 00 0a 0004 00006800 75 (Firmware package leng.
There are limitations. When setting up a scene, the scene data length cannot exceed 32 bytes. DPs exceeding 32 bytes will not be set successfully.
Beacon does not support relay; Beacon mesh supports relay; BLE does not support relay, Bluetooth mesh supports relay.
When switching combo devices to Bluetooth control, only one device can be controlled at a time.
The way to enter the network configuration mode is related to the burned firmware, generally there are the following situations: For example, for firmware with a no-code development solution, you can check the way to reset the network configuration in the platform firmware configuration; For MCU general integration firmware, please check the protocol content; If it is self-developed firmware, the way to reset and enter the network configuration is defined by yourself.
Custom Delivery: Tuya factory will burn the firmware (i.e., software program) and authorize the module. Customers can use it directly after purchase. Empty Delivery: The module does not contain firmware (software program) and requires developers to burn and authorize it themselves before use. Note: Due to the inability to achieve large-scale production burning for small batch module orders, manual operation is required. Therefore, for orders of less than 100 units, we will charge a burning fee of 200 RMB. For orders of more than 100 units, customized delivery is the default. The content is as shown in the figure below:.
The lighting OEM firmware default by 8 jumps, which also can be customized when more levels are required such as street light scenes.
Please read the product manual carefully before setting up the network, and confirm that the app is the one recommended in the manual. Check if the device is powered on and functioning properly, and ensure that the router is connected to the external network, so that the device is in the correct state for network setup. If all the above conditions are met, please follow the communication protocol below for troubleshooting: Bluetooth device pairing failed Zigbee device pairing failed "Auto Scan" pairing failed Wi-Fi device pairing failed.
The reset operations for different devices may vary, but common methods include: Repeated Power Cycling: For lighting products such as bulbs and light strips, it usually requires toggling the power on and off three times, with a 2-3 second interval between each toggle. Long Pressing the Reset Button/Port: This operation is applicable to various types of products and is quite common. Power Cycling: It is recommended to cut off power for more than 10 seconds before restoring it. Combination Key Operation: Some devices may require pressing specific combination keys to enter the network configuration mode, typically for appliances and locks. It is advisable to refer to the product manual for detailed information. Methods to determine if the device has successfully entered network configuration mode: The indicator light blinks rapidly or slowly. The device emits a prompt sound, which is common for IPC (Internet Protocol Camera) products. The device screen displays relevant information, common in control panels, locks, and other screen-equipped products. Special device indicators: For wireless gateways, the red light blinks while the blue light remains on; for wired gateways, both indicator lights remain on. Note:During the first use, devices typically enter network configuration mode automatically, except for locks, control panels, and speaker products. How to put Bluetooth lighting devices into pairing mode? How to put Zigbee sensor devices into pairing mode? How can Wi-Fi lighting devices enter the pairing mode? How can Wi-Fi electrical devices enter pairing mode?
The fixed frequency test baud of the Zigbee platform module is 115200, including TYZS3, TYZS4.
Common baud for Tuya modules to connect to general firmware are 9600 bit/s and 115200 bit/s.
When a Zigbee module is powered on, it sends instructions at the baud 9600 and 115200 in a polling manner. However, when the instructions sent at either baud is replied to, the baud is fixed. The module will not send instructions at the two baud in a polling manner even if it is powered on again.
115200.
The baud is 9600/115200.
There are several ways to display the split device name: Default name: main device name + dp_code Directly display the name of the dp point (requires Tuya personnel to configure the default name of the product) Display the customer's custom name There is a button in the Tuya app panel to customize and change the dp name. If it can be modified in a third-party app, it can also be directly modified in the third-party app.
The 3.3v pin of the module provides power, and the Vcc pin is the power input pin for the internal level conversion circuit of the module. The actual voltage is the voltage supplied to the module from the outside. For specific details, please refer to WBR1D Module Datasheet and WBRx Series Module Hardware Design.
First, it is necessary to confirm whether the user code matches the byte order. Additionally, if the number of IR function configurations exceeds 44, it will also lead to failure in normal control.
The original order paid for advanced capabilities, and the rework order will also support it.
The newly configured features will only take effect after the value-added service is activated.
When the product needs to support both Fahrenheit and Celsius temperature adjustments, it is necessary to inform the platform which dp is for Fahrenheit and which dp is for Celsius, and how the product determines whether it is in Fahrenheit or Celsius mode. Therefore, it is necessary to select the temperature scale capability.
Because the system detected that the corresponding function point of this capability, i.e., the dp point, does not exist, it is highlighted in red to remind the user to modify the corresponding dp point or delete this capability.
Baud supports 9600 and 115200 adaptive. You can refer to the specifications of the specific module：https://developer.tuya.com/en/docs/iot/nb-module?id=Kaiuymgk901fv.
Zigbee adaptive baud refers to adapting to 9600 or 115200 according to the MCU baud for the first power-on, but one of the baud is locked after communication is established; if a switch is needed, the authorization needs to be re-burned.
When the switch is closed, the thyristor can be turned on. At this time, the power is taken by the thyristor in the vicinity of each zero crossing and then rectified to supply power to the module.
When the low power lamp is loaded, the load impedance is relatively large, and the voltage distributed by the power supply circuit is relatively low. If it is lower than a certain value, it will cause insufficient power supply to the module or drive circuit, causing flashing.
Button: Any one of the switches is reused as a network distribution button. Indicator: The network indicator and the status indicator of the switch are multiplexed with the same light. Networking process: The indicator flashes to indicate normal distribution network Control: The indicator indicates that the load light is on Distributed network: Need to be used with Tuya Zigbee gateway 1. The user long presses any button of the switch for 5S to enter the network configuration state. At this time, the indicator flashes quickly and the load light is on, indicating that it is pairing. And at this time, short press the switch, the load light can not be controlled. 2. Network configuration is successful: the indicator light stops flashing, and the local button can control the load normally. 3. Failed to configure the network: If the network has not been configured, the indicator will stop flashing after 30s. At this time, the local button can control the load switch normally. Reset/delete device: Method 1: The user long presses any button of the switch for 5 seconds, the local device is reset, and the App prompts that the device has been deleted. At this time, the indicator flashes quickly and the load light is on, indicating that it is pairing; Method 2: App panel On the settings page, click "Delete Device", the APP deletes the device, and the local device enters the reset state: At this time, the two load lights are on at the same time, the network LED indicator flashes, and the other indicator is consistent with the load light, indicating that it is pairing in. Off-grid: 1. When the switch can’t find the gateway and the off-grid state appears (the device will try to rejoin 3 times, the duration is 30s), the device enters a low-power standby state, and the App is uncontrollable at this time; 2. Wait for the next local time When the button triggers the control, the switch starts to search for the gateway. After the device is online again, the app can be controlled.
No, the serial port function closed in the low power status does not respond to any data generated by the MCU, but it can receive the sent data.
TX, RX, VCC, GND, low power control pins (which are MCU control wake-up module IO, module control wake-up MCU IO, if you do not need low power function, you can not connect these two IO), basically 6 pins can complete the integration.
Hello, please troubleshoot in the following ways: First, confirm whether the smart switch (no neutral wire required) is used in an environment that is often powered, such as the scenario of inserting a card to take power in a hotel; Return to the company for after-sales service, and ensure that the installation is powered off. It is not recommended to use it in an environment with frequent power supply, as this will cause damage to the internal electronic components of the smart switch (no neutral wire required).
Local unbind, local reset.
30S.
Please troubleshoot in the following way: First, check if the wiring is correct and whether the load light or fixture is working normally; Then check the gateway version and model, whether it is a Zigbee gateway or a Bluetooth gateway, the type of gateway needs to be consistent with the model of the single live wire switch (either Zigbee or Bluetooth); Please ensure that the gateway is our brand, as gateways from other brands may have protocol differences, which could prevent networking; Finally, check if the load light is of too low power (for example: a miscellaneous brand light fixture less than 5W), replace the light fixture and try again.
Due to power consumption issues, Zigbee smart switches (no neutral wire required) currently do not have a relay function.
The smart switch (no neutral wire required) has undergone certain low-power processing; therefore, it does not have relay capabilities, and it is not recommended to deploy only single live wire switches throughout the entire network. It is suggested that the single live wire switches be installed close to the gateway, or that similar high-power devices be added between the gateway and the single live wire switch to provide network relay capabilities.
Dear user, for questions related to device installation, please refer to the product manual or consult the seller. If you encounter problems when using app to control your device, please contact us. Thank you for your understanding and support.
When the switching power supply is working, it will interfere with the control signal. Add a filter capacitor to the IO port of the module that is disturbed to eliminate the interference signal.
Yes, it needs to be reflashed to take effect.
Dear user, Wi-Fi and Bluetooth combo devices can be added at the same time. When the device cannot connect to Wi-Fi for a period of time, it will trigger the device to switch to the Bluetooth channel. At this time, you can control the combo device through Bluetooth. At present, some firmware already supports adding through the Bluetooth channel alone.
With the E0 command, it can be either using Bluetooth's internal time, or the MCU's own time.
Tuya platform supports the Bluetooth mesh smart switch (no neutral wire required) solution.
The panel can not be used directly to switch between different types of modules. You can find PM if you need to communicate.
Yes, you can directly operate the firmware upgrade in the fourth step of product development "Cloud Configuration". You can view the document for details: https://developer.tuya.com/en/docs/iot/configure-in-platform/advanced-features/firmware-upgrade-operation-guide?id=K93ixsft1w3to.
Bluetooth protocols that can be integrated into the Tuya platform include: Tuya Bluetooth LE protocol (referred to as single point, that is, single node connection control), Bluetooth mesh protocol, and Beacon mesh protocol. Tuya Bluetooth Protocol Classification Communication Method Typical Features Typical Applications Tuya Bluetooth LE Communicate with mobile phones or gateways via Bluetooth LE connection Direct connection, low power consumption, fast transmission rate Wristbands, watches, smart toothbrushes, smart body fat scales Bluetooth mesh Bluetooth networking communication following the SIG Bluetooth mesh standard Mesh network, large-scale group control Mesh lighting, commercial lighting, smart home kits Beacon mesh Communication between mobile phones or gateways through Bluetooth LE broadcasting Small data packets, short distance, ultra-low speed, ultra-low cost, support for forwarding Low-cost door magnets, PIR, temperature and humidity sensors, low-cost light strips, low-cost wall stickers, remote controls, scene switches Compared to the other two protocols, the Beacon mesh protocol is very streamlined, and its SDK is particularly suitable for direct porting to various Bluetooth LE Beacon chips, achieving SoC-level low-cost applications. Beacon Mesh SDK Features Extremely simple code: a total of about 1000 lines of C language code, which can run on chips with 2K RAM + 16K ROM. Cross-platform: The design level supports cross-hardware platforms. By implementing less than 10 hardware and Bluetooth broadcasting related functions, porting can be achieved. Complete functionality: The SDK implements rich IoT communication capabilities such as pairing and unbinding, packet assembly and disassembly, group management, self-organizing network, forwarding, encryption and decryption, and security policies.
Bluetooth LE does not support groups, as determined by the protocol.
Under the condition of good hardware signal design and no obstructions or interference with the module's RF, the network configuration and control distance in indoor environments is approximately 40 meters, and the network configuration and control distance in outdoor open areas is approximately 100 meters. In actual projects, factors such as the hardware design of the end product, the physical environment, and the network scale may all affect the control distance. The specific distance should be based on the actual test results of the end product.
No, because the combo module uses Bluetooth LE control, and Bluetooth LE does not support grouping.
You can name a hot spot with up to 27 alphanumeric characters. The displayed hot spot name is in the customized name-xxxx (last four bits of the MAC address) format, for example, smartlife-3012.
Dear user, we are sorry for your inconvenience. You need two smart phones that can provide a network hot spot. One phone turns on the hot spot as the network provider and the other can connect to the device.
The early Tuya Wi-Fi solution and protocol was single Wi-Fi, the device only supported Wi-Fi network control, the product was later upgraded to support Wi-Fi&Bluetooth LE combo module, due to the addition of Bluetooth LE communication protocol, both the product solution and the product creation entrance changed, and a new Wi-Fi&Bluetooth LE PID needed to be recreated to select the combo module.
Power supply voltage 3.3V, ripple less than 100mV. The average current of the Wi-Fi module is about 80mA, the power supply should have the capability to output an average current of 200mA, and when outputting a transient 450mA, the output voltage should not be less than 2.8V. For Bluetooth and Zigbee modules, the power supply needs to have the capability to output an average current of 50mA, and when outputting a transient 100mA, the output voltage should not be less than 2.8V. Parallel a 0.1uF ceramic capacitor near the power supply pins of the module to filter out interference.
There are two modes of products created on our platform, low power mode and power-on flash mode, the conditions for entering production test are as follows: Low power mode: It need to switch to low-power mode to enter production test; Twinkling after power-on mode: When powered on, it will scan for the production test router ( tuya_mdev_test1 ), and upon detection, it will enter production testing.
Preface In the process of MCU SDK solution development, you may not be very familiar with Tuya's common terms, or you may not know how to start with the numerous protocol documents and guidance documents, and you may not know how to troubleshoot when encountering problems. This article will explain the common terms and vividly introduce the MCU SDK solution model, and sort out the high-frequency problems that may be encountered in the development process, hoping to help you. Note: This article only organizes and answers high-frequency questions about Wi-Fi, BLE, Mesh, and Zigbee protocols. Glossary Module, Cloud Module: Networking modules launched by Tuya. Pairing: The process of establishing a binding relationship between the device and the APP. PID: The unique identifier of a product. DP point, DP ID: Refers to the ID corresponding to the function selected on the function definition page when you create a product on the Tuya IoT platform. Universal firmware: Refers to the module firmware that can be used by products with different PIDs but the same protocol. Pairing status: Refers to the state where the module can be searched and added by the APP. MCU SDK Solution Model When you choose the MCU SDK solution, the hardware development page of the Tuya IoT platform shows you the modules and firmware you can choose. This firmware is universal firmware. The module that has been programmed with this firmware only has serial communication function and the function of communicating with the APP or the cloud platform (some firmware also has GPIO wake-up function), and other pins have no software logic, so the application functions need to be completed by your MCU, and the MCU cannot use the module's pins to perform other tasks. The serial communication function is to communicate with your MCU through the serial port, receive and parse the serial port data sent by the MCU according to Tuya's serial port protocol, and then perform the corresponding tasks. Why use Tuya Serial.
High power firmware is used for mains-powered products, which do not typically need low power consumption.
The hibernation current for low power devices: 3uA Normal working current: 5mA Transmitting/receiving instantaneous: 30mA+.
Broadcast interval, 20~10240ms, unit: 0.625ms. Under the same conditions, the larger the broadcast interval, the lower the power consumption. Connection interval, 7.5~4000ms, unit: 1.25ms. Under the same conditions, the larger the connection interval, the lower the power consumption. Transmission power For Bluetooth LE 4.0/4.1/4.2, the transmission power is -20dBm~10dBm (0.01mW~10mW) For Bluetooth LE 5/5.1, the transmission power is -20dBm~20dBm (0.01mW~100mW) Under the same conditions, the smaller the transmission power, the lower the power consumption Main frequency, commonly 6MHz, 12MHz, 16MHz, 24MHz, 48MHz, and 64MHz. Under the same conditions, the lower the main frequency, the lower the power consumption. 32K clock source. Under the same conditions, the more accurate the external low-frequency crystal oscillator, the lower the power consumption. Voltage, generally ranging from 1.8V~3.6V. Under the same conditions, the lower the voltage, the lower the power consumption. Power supply mode, including DC-DC and LDO. Under the same conditions, the DC-DC power supply mode is more power-efficient. Broadcast data length. Under the same conditions, the shorter the broadcast data length, the lower the power consumption. Sleep wake-up time. Under the same conditions, the shorter the sleep wake-up time, the lower the power consumption. Chip peripherals. Different chips have a variety of peripherals, and when measuring chip power consumption, try to exclude the influence of peripheral power consumption. For more power consumption related data, refer to Power Management.
A Zigbee module with low power firmware has the scheduled hibernation feature. When the module communicates with the MCU, it needs to wake up the other party first before sending data.
You can test the power consumption of the module independently. Devices of different categories have different low power working modes. Some devices can enter the deep sleep mode after the pins are pulled down, the low power mode is enabled, and the command for disabling peripherals is sent. For more information, visit https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9eigf2el456o#title-32-%E4%BD%8E%E5%8A%9F%E8%80%97%E5%8A%9F%E8%83%BD%E9%99%84%E5%8A%A0%E5%8D%8F%E8%AE%AE.
If the power of a device is less than 3 W, the current and power data of the firmware will not be displayed, but the power consumption data will. Therefore, if you use a low power device for a while, the accumulated power consumption is reported to the cloud and displayed on the app.
In a low power solution, two GPIOs (PWM1 and PWM2) are reserved between the Tuya Zigbee module and the MCU for a hardware handshake. The Zigbee module uses PWM1 to awaken the MCU, and the MCU uses PWM2 to awaken the Zigbee module. PWM1 and PWM2 are at a high level by default and are active when they are at a low level for more than 10 μs. Before the Zigbee module or MCU proactively sends a command, it needs to initiate a handshake connection. In a strong-current solution, serial interfaces are in a listening state. Hardware does not need to connect I/O1 and I/O2.
3-8ua in sleep mode.
1.The default status is low power status when the module is powered on for the first time. 2. Without anti-mistouch mode,long press the RESET button for 5s to reset the device, wait for more than 10s to power off, and then power on again. It will enter the low power status by default. 3. Use the app to configure the network with the device, click the 'Remove Device' button in the app to remove the device. After removal, wait for more than 10s to power off and then power on. It will enter a low power status by default.
Low power modes include the standby low power mode and connected low power mode. 1. If the lights with T20 enabled are turned off after successful pairing, they will enter the standby low power mode 3s after turn-off. The average power consumption of the entire device is less than 0.2 W. 2. The connected low power mode is a connected state of some devices. In specific connected mode, devices enter the connected low power mode after pairing times out. That is, the devices exit the pairing mode and maintain the steady-on state. Pairing timeout scenes include: (1) Three minutes after being connected (2) Power cycling after blinking quickly or slowly for 10s.
The module is a non-low power module when it is produced and the low power consumption function needs to be enabled through instructions. The module will enter a low power state by pulling down the low power enable pin. The setting will be stored permanently. https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9eigf2el456o#title-33-%E4%BD%8E%E5%8A%9F%E8%80%97%E5%8A%9F%E8%83%BD%E9%99%84%E5%8A%A0%E5%8D%8F%E8%AE%AE.
The Wi-Fi low power solution requires the Wi-Fi module to be powered off, generally using MOS or LDO with enable terminal.
Wi-Fi general solution has a limitation on the number of functional points. The limitation on the number of functional points is actually a limitation of the module file descriptor. The more functional points a device has, the larger the device function description file (schema file) will be. When the device function description file exceeds 8 KB, some RTOS system products will fail to download, resulting in device activation failure. When the cloud interacts over HTTPS and exceeds 8 KB, it will enable chunked mode, but the device does not support chunked mode. Therefore, it is usually recommended that the number of functional points does not exceed 40. What are the impacts of exceeding this limit? During development, if the limit is exceeded, the module may directly report activation failure during network configuration testing, with the phenomenon being that it cannot connect to the cloud consistently, although the panel has been pulled. After development is completed, network configuration testing in China may be normal, but special attention is needed for exported products, which require multiple network configuration tests. Due to different time zones, the amount of data returned during activation may vary, potentially leading to consistent activation failures. How to reduce the impact? 1. Modify the data types of functional points, and try to reduce the number of enumeration type functional points. The impact from large to small is: enumeration type numeric type string type boolean type. This requires actual network configuration testing. 2. Reduce the data of functional points. 40 is not a strict limit, but usually, within 40 is the most stable.
Zigbee universal integration firmware also needs to be configured. There are three integration types: high-power devices, low-power devices, and scene switch devices. High-power devices: mainly used in long-term power supply products. Low-power devices: mainly used in battery-powered products, with wake-up function, and can configure wake-up cycles after configuring low-power firmware. Scene switch devices: mainly used in scene switches or scene switches, and can support scene commands.
Wi-Fi modules are commonly used for general integration: Modules such as WBR* series and WT3.
Check if the TX and RX of the Wi-Fi module are connected to the serial board.
No need, the product gateway + host production test is to find the MAC address through SN, you can test without shielding the room.
There is a problem with the transmitter tube of the host or a problem with the receiver head of the slave machine.
The beacon needs to be set to M1:master mode.
WIN10 64-bit.
Sub-devices cannot be in the network configuration state. If the device is already networked, you need to remove the device from the APP.
You need to choose serverless here, you cannot choose the filing license.
The license will be associated with the PID, firmware key, and version of the corresponding product. The system generates a license based on the corresponding order information; When the customer is in production, they can authorize each device using Tuya's host, enabling connection to the Tuya App.
Create a custom product (no-code development products do not need to get licenses, the product comes with a license). Select development method. Select the module you need. After the selection is completed, the option Get 2 Free Licenses will appear on the right side of the page, click to get them. It takes a certain amount of time to generate the licenses, please wait patiently. After the license is generated, you will be reminded via SMS or Email (2 hours later if the generation is not successful, please submit a Tech Tikect for feedback). Note: Starting from November 12, 2021, the Free Licenses collection function has been adjusted from the original "10 Free Licenses for each PID" to "A total of all PIDs of each IoT account are only allowed to get 2 Free licenses，Get up to 6" . After the Free Licenses is used up, if you want to continue to develop the product, you need to purchase licenses.
The full name is the device cloud activation license, abbreviated as the license. It is the basis for normal use of a device to Tuya IoT cloud activation, and it is also the only product name sold on the platform for cloud authorization. The cloud License code purchased by the customer can be written into the main networking module through two production methods: Use the production certificate to write the cloud License code to the specified number of devices in the production tool provided by Tuya. Directly get the cloud License code list file and use the customer's own tool to write the device one by one. For details, please click to view the cloud license order & pickup instructions.
First, add the device to the app, refer to: How to add a device to the app and connect it to the network (Wi-Fi)? If the device supports it, after authorizing login to the control panel, the device will automatically sync to the control panel.
During the upgrade of the control panel, the mobile panel will always display a progress bar, and other functions will be unavailable. This is by design. Please wait until the upgrade is complete. The control panel end is not affected.
After the control panel is activated, all eligible devices are pulled by default. If you need to hide a device, you need to enter the mobile panel, click on the device, click on the corresponding device, and click the hide icon to hide it. If you need to unhide it, click on the device, click the eye icon in the upper right corner, and select the icon you want to display.
To ensure the security of user panel assets, we have introduced a security verification mechanism. If the same code has been packaged and uploaded, other users will not be able to upload the same code again. Users can modify the code and repackage it for upload.
Except for the two types of passwords that rely on algorithms, dynamic passwords and offline temporary passwords, the length range of other passwords is 6-10 digits, which can be configured at the product PID dimension.
It is recommended to contact the seller to confirm whether the sub-device has enabled the voice plan.
There is no property in the Popup component that can directly modify the base color. You can modify the base color cellBg in the local theme configuration file (src/config/theme.js).
If the MCU does not correctly respond to the data sent, the gateway will repeatedly send the data. The frequency of the gateway sending data is once per second for the first three times, and then once every 10 seconds. Therefore, it is necessary to check whether the MCU has responded and whether the response data is correct.
Currently, Tuya modules do not have so many I/O pins to support an independent button for each channel. We recommend that you use the MCU solution.
AI Video Patrol is an AI intelligent analysis service. It automatically analyzes and checks the device status and video images of specified devices on a regular basis, proactively identifying abnormal device issues (device offline, poor signal, device storage issues) and abnormal image issues (blurry images, image obstructions, abnormal brightness, etc.), and pushes inspection reports to inform users of device status and video image problems in a timely manner, ensuring the normal operation of camera devices.
First, you need to check the reported data against the serial port protocol to see if it is correct. Secondly, check whether the reported time is Greenwich Mean Time. Note that when editing the password on the platform, the password keys need to be configured according to the table, otherwise verification will fail. https://developer.tuya.com/en/docs/iot/door-lock-mcu-protocol?id=Kcmktkdx4hovi#title-23-Lock%20password%20services.
This depends on the panel used. You can select the panel on the device interaction page, then click edit panel, and configure the functions on the configuration pageFlexible password configuration - length configuration andlock password digit configuration. If this configuration item is not available on the function configuration page, you need to contact the Tuya project manager or product manager to confirm whether the panel supports backend configuration.
There are three occasions when WBRL wakes up the cat eye, 1. When initially powered on, WBRL will wake up the cat eye. At this time, if QR code network configuration is needed, the cat eye needs to send QR code information through the 6A command. 2. When the module needs to transmit images or videos, the MCU needs to send the 64 command and wait for the module to return the 64 command, waking up the cat eye to establish the stream. 3. When the panel component "Video Monitoring" is clicked, the module will wake up the cat eye to start transmitting video. This process does not require MCU participation. Note, if the cat eye is woken up upon entering the panel, check whether DP54 is not selected.
Usetuya_ipc_get_device_id(devid,&devid_len);The size of the devid array is recommended to be no less than 30 bytes,The interface is defined as follows: /** * \fn OPERATE_RET tuya_ipc_get_device_id * \brief get device ID * \ * \return OPRT_OK if get device ID success .other is failed; */ OPERATE_RET tuya_ipc_get_device_id(IN OUT CHAR_T *devid, IN OUT INT_T * id_len);.
The IPC SDK itself does not have an interface to close logs, but you can reduce log output by setting the log level as follows: tuya_p2p_log_set_level(TUYA_P2P_LOG_ERROR); tuya_ipc_set_log_attr(0, NULL);.
The log level can control the amount of log output. The higher the level, the fewer the logs. Once a certain level is set, logs below this level will no longer be printed. Highest log level:TAL_LOG_LEVEL_ERRHighest level Lowest log level:TAL_LOG_LEVEL_TRACELowest level The log levels are defined as follows: typedef enum { TAL_LOG_LEVEL_ERR, //! Error 0 TAL_LOG_LEVEL_WARN, //! Warning 1 TAL_LOG_LEVEL_NOTICE, //! Notice 2 TAL_LOG_LEVEL_INFO, //! Info 3 TAL_LOG_LEVEL_DEBUG, //! Debug 4 TAL_LOG_LEVEL_TRACE, //! Trace 5 } TAL_LOG_LEVEL_E; There are two methods to set DEBUG logs in the IPC SDK:tuya_ipc_set_log_attr(4,NULL) or tal_log_set_manage_attr(4).
Okay.
Yes, need to use the host computer software to bind the module authorization SN and the SN of the customer product one by one, or you can directly take the module authorization SN as the SN of the product.
Please check one by one if the following issues exist: Screenshot the QR code and try reading it using another mobile app to verify if the device has a problem with reading the QR code. Check if the device has integrated with a QR code reading algorithm, such as the ZBar library. Check if the YUV or JPEG image the device obtains and passes to the QR code reading algorithm is clear.
In Android 15, the system has made updates to the stop state of software packages. Specifically, in some phone systems, swiping up or clicking clean in the multitasking management card may cause the application to enter the stop state. This change may result in your Bluetooth device not receiving alert notifications properly. If you encounter a situation where your Bluetooth device is unable to receive alert notifications on an Android 15 phone, we suggest checking your app settings to ensure the app is not set to stop state (find and open the settings page of the corresponding app in the app management section of the phone settings). If the app has been stopped, please restart the app to restore normal functionality.
Two methods are available to pair 4G devices: the mobile app scans the device’s QR code, or the smart camera scans the QR code generated on the mobile app. Set the pairing mode to: PARING_MODE_WIRED. Set the connection mode to: TUYA_IPC_LINK_WIRE.
Dear user, we are sorry for your inconvenience. Please check in the following ways: 1.Please ensure that the "SD card recording video switch" on the device is turned on（Device Settings: Recording Settings - Toggle the recording switch to enable. If the button is not available, it is automatically enabled.）; 2. Please check the condition of the SD card: a. Make sure the SD card is compatible with the camera. We recommend consulting the seller of the camera to understand the compatible types of SD cards; b. The SD card may have poor contact. We suggest removing the SD card and reinserting it; c. Check if the format of the SD card is FAT 32. If not, you can use a card reader to format it (for specific instructions, we recommend consulting the seller of the SD card); d. The SD card may be damaged. Try inserting a new SD card into the device to see if it can store videos. If it works, then the original SD card is likely damaged; 3. Remove the device and re-pair it in a stable network environment; If you have already gone through the above steps and still cannot store videos, it may be a device issue. We recommend contacting the seller for after-sales support.
Confirm the lock brand because the setting modes vary depending on the brand. The following shows common methods for restoring factory settings: 1. FingerCrystal smart door locks: Open the rear cover, press and hold the SET button, and restore factory settings based on the voice prompt. To restore factory settings for a new firmware version, the administrator password is required for verification. Note: If you forget the administrator password, first contact customer service personnel to get the required string of digits. Then remove the battery, press and hold the SET button, and power on the smart door lock. After hearing a prompt tone, enter the string of digits obtained from purchasing channels. 2. ZmartPlus smart door locks: Open the rear cover and press and hold the A button under the battery for 5s. After hearing the prompt tone, press ''#'' to restore factory settings. 3. EZVIZ smart door locks: Open the rear cover and press and hold the RESET button. Press ''#'' to restore factory settings. If you hear a prompt tone ''initialized'', the restoration was successful. 4. Dessmann smart door locks: Power off the door lock, press and hold the RESET button, and power on it. After hearing the prompt tone, press ''#'' to restore factory settings. You can also restore factory settings from the menu.
The scenes in the app are divided into three types: cloud-based scenes, local scenes, and LAN scenes. Cloud-based scenes: They can execute across protocols (Wi-Fi, Zigbee, Ble, etc.), and the scene linkage rules are stored in the cloud. When the cloud determines that the conditions are met, it will execute the corresponding actions. Local scenes: The devices involved in the scene belong to the same gateway and do not require cloud-based judgment of conditions or actions. The scene linkage rules are stored in the gateway. Regardless of whether the gateway has external network access, as long as the gateway is functioning normally and determines that the conditions are met, it will execute the corresponding actions. This is common in Zigbee/BLE mesh/multi-mode gateways, where the devices corresponding to the conditions and actions in the automation are all sub-devices under the same gateway. Example: Gateway A has Sigmesh Light 1 and Zigbee Light 2.Create automation: If Sigmesh Light 1 switch (on), then Zigbee Light 2 switch (on).This scene is a local scene. LAN scenes: Two or more gateways in the same household belong to the same LAN and do not require cloud-based judgment of conditions or actions. They are connected via wired or wireless connections on the same router, with the same LAN IP addresses. The scene linkage rules are stored in one of the gateways. Even if the external network of the router is disconnected, the internal LAN network is normal, and the scene can still be triggered. Example: Gateways A, B, and C are all part of the same LAN. Gateway B has Zigbee Light 1, and Gateway C has Sigmesh Light 2.Create automation: If Zigbee Light 1 switch (on), then Sigmesh Light 2 switch (on).This scene is an LAN scene. Change logic: When automations are created, they are initially cloud-based scenes. If they meet the conditions for local/LAN scene implementation as described above, the gateway will take over the scene, and after a period of time, the scene will aut.
This may be because the device is a Bluetooth device and was set up by directly connecting to a smartphone, making it unable to create automation. We recommend connecting the device to a Bluetooth gateway to resolve this issue.
The production testing for general Bluetooth module integration is mainly divided into RF production testing and end product production testing. RF production testing checks whether the RF part of the Bluetooth module is functioning normally after leaving the factory, which is a very important test item. End product production testing is a test channel provided by Bluetooth general integration and is not a mandatory item. RF production testing requires a Bluetooth production test beacon (please contact Tuya to obtain one). For most modules, first, restore your module to factory settings to put the device in network configuration mode. Then, power on the beacon and set it to ty_mdev mode, placing it 0.5m away from the module. The MCU or host computer issues the CMD-0x0E command to the module, and the module will return the RSSI. Generally, if the RSSI is greater than -70, it is considered that the module's RF is working normally. Some modules do not support the host scanning function, such as BK3432. In this case, you can use the UART_CONTROL mode along with a host computer for production testing. For specific details, please contact Tuya. End product production testing requires customers to implement it themselves based on the characteristics of their products.
Hello, the possible reasons for this issue may include the following: Please first confirm if your mobile system (Android 6.0 or above, iOS 11.0 or above) meets the requirements; Please try restarting your phone; please uninstall the App, reinstall it, and try again. If the crash issue persists, please upload the logs from the App: App - [Me] - [Settings] - [About] - [Upload Log]. If you are unable to upload logs due to the App crashing, you can provide feedback on your issue through the feedback path.
Hello, the validity period and notification quota of purchased service packages will not accumulate. Each order will be fulfilled separately. However, the SMS/phone quota of old orders will be consumed first. If the SMS/phone quota of old orders is not fully used within the validity period, it will automatically expire.
The production test gateway cannot be replaced by an ordinary proprietary gateway, but it can be upgraded to a production test gateway through OTA through an ordinary proprietary gateway.
The Cat1 module cannot report data with a data length of 0, but the value can be 0. For example, when clearing a recurring scheduled task, data with a length of 1 can be reported, with the reported value being 0.
The combo module can only receive control data from the Bluetooth remote control after pairing. Due to Wi-Fi and Bluetooth sharing the RF spectrum, Wi-Fi and Bluetooth take turns to use the spectrum within a cycle, which can lead to unstable data reception. The normal test result for data reception stability is around 95%.
Please submit a ticket, provide the PID that needs to be retrieved, describe the problem, and we will verify and handle it for you.
Yes, the Zigbee gateway is added under the 2.4GHz network, and the sub-devices added under the gateway also need to be under the 2.4GHz network.
PHY6230 chip can be used as an alternative chip, but it is not completely pin-to-pin compatible, and adjustments need to be made according to the actual situation.
Please contact the project manager or business for unlocking and processing.
Confirm whether the load being used is a linear lamp? Because the Wi-Fi single live wire switch does not support linear lamps, you can connect a lamp capacitor adapter in parallel at both ends of the lamp to avoid power-on flickering.
Within 20 seconds.
The following are some common ways of after-sales service for general products: Offline channel: If you buy the product in a physical store, you can go to the store to consult the after-sales service. They will provide you with relevant instructions and guide you to do the follow-up operations. Online channel: You can contact the seller through the customer service channel on the e-commerce platform, and state the problems you encounter, so that the seller can better understand the situation. Different brands and products may have different after-sales service methods and policies. You can check the relevant information or official website of the product you purchased, and understand the more specific after-sales process and contact information. I hope this information is helpful to you.
The detailed data and specifications of the Tuya module are as per the datasheet: https://developer.tuya.com/en/docs/iot/nb-module?id=Kaiuymgk901fv#title-2-%E6%A8%A1%E7%BB%84%E5%88%97%E8%A1%A8.
The frequency selection is mainly based on the PWM frequency that the dimming IC can accept. Most PWM dimming ICs on the market are between 500HZ-5K, and the default is 1Khz. If you have special requirements for stroboscopic, you can adjust the frequency to above 8K, and the water ripple phenomenon will basically not appear when the mobile phone is photographed.
That means creating a product with the same configuration information as the current product into current space. Operating procedures: The product owner (here: factory for short) finds the product to be copied in the product list of Tuya Develepoer Platform-Products-My Products. Click Manage Product , and select Copy Product to Current Space in the pop-up box. Click OK in the pop-up box to automatically create a new product into the current space. However, the following information needs to be excluded, they will not be brought to the new product. The smart speaker access service needs to be re-applied, all the smart speaker services connected to current product will not be copied to new product. If the firmware of current product is custom firmware or the firmware uploaded by yourself, the firmware information of new product is empty, you need to reset the firmware. Current product's multi-language name will not be brought to the new product by default, in order to avoid any inconsistency between the name seen by end-users after successful network configuration.
The appearance and functions of a miniapp developed using the mini App SDK are designed and determined by the developers.
This is the default. If you do not fill it, you will not be able to pack it. Still need your company to go to Google to apply for the key and then fill it in. For more details please see: https://developer.tuya.com/en/docs/iot/map-service?id=Kaiuyrmzcp5jd.
The SDK generated from Tuya occupies about 4k of flash, and the ram is about 100 bytes related to the length of the DP point data. If OTA is required, it needs to be more than 260 bytes, and the maximum function nesting is the 9th level. If the MCU can't meet the requirements, the user can connect according to the protocol document.
Yes. Circuits need to be established based on actual pin configuration.
You can bind an unlimited number of development boards to a Tuya Developer Platform account.
Modules cannot be replaced after placing an order. It is recommended to close the order and place a new order.
Wi-Fi and Bluetooth LE modules (mass production supported): CR3L (lighting and electrical devices, home appliances), CR3L-IPEX (lighting devices, home appliances), and CR2S (electrical devices). Bluetooth LE modules: ZTU (all categories), ZT3L (lighting devices), ZTLC5 (lighting devices), ZT2S (electrical devices), and ZT5 (locks and sensors).
For details, please check https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber The left navigation allows you to choose to view the content of different schemes：.
It is a page for sales of licenses and finished materials such as modules, chips, components, and production tools for product development.
The first type: English reports are not available for download at the moment, and only support results viewing. The second type: The test report type is Tuya test, which only supports result viewing.
The buttons, indicators, and I/O pin and level of the network indicator are configurable. Press and hold any button to enter the network pairing mode. The GPIO pins must be configured and cannot be disconnected.
12 months in general.
Because NB is a long connection, it requires an IoT card. NB protocol is generally used when it is inconvenient to deploy Wi-Fi.
The Bluetooth gateway needs to be used for remote control or remote data reporting scenarios.
The power consumption is higher than Zigbee smart door locks, but their functions are similar to those of Zigbee smart door locks.
3 to 6 months in general.
It is globally used as a household product (especially suitable for door locks).
It is mainly used as a household product in countries/regions outside China.
Currently, the default brightness is 50%, which can be tuned when you create products.
The supported wireless communication protocols include Wi-Fi, Zigbee, and Bluetooth.
They apply to smart house systems and apartments.
Generally, weak networking is used, and therefore, the door lock status cannot be obtained in real time. In most cases, data report is one-way.
It is 2 to 3uA in standby, and the peak is 45mA when reporting DP, and the average is 1~2mA.
1.1.5.
They support close control with a mobile phone over Bluetooth and remote control through the app.
It consumes high power when working and goes offline after stops working.
No-code development Wi-Fi, Bluetooth, or Zigbee switches on the Tuya developer platform support a maximum of four gangs.
Strong networking is used to obtain the door lock status in real time. Two-way communication supports various functions and features.
The button is used for turning on or off the lamp and pairing the lamp with the app. To enable more functions for the button, customize the firmware or use the MCU solution.
Yes, it is supported. You can create a RGBC and then configure the firmware information during the hardware development step, as shown in the following image:.
Yes. Tuya modules support independent button control for each way of a 3-way no-code development socket created on the Tuya developer platform.
Remote Control: Remote control to turn the switch on/off. Scheduled Switching: Customizable timing for switch activation based on user preferences, supporting multiple sets and weekly cycles. Voice Control: Control the switch on/off through various third-party voice platforms, freeing up hands for more flexibility. Smart Scene Linkage: Through the app's scene and automation settings, the switch can be linked with other smart devices, such as automatically turning on the lights when motion is detected by a human body sensor.
The power supply range of the Wi-Fi module is 3.0V-3.6V. Actually tested 2.7V working for a short time, there will be no problem. To ensure stable and reliable operation, the center value of the power supply voltage must be set at 3.3V, and the ripple should be controlled within 100mV.
The first three represent RGB, the back H occupies 2 bytes, and S and V each have one byte For example, 00112233334455 resolve into： 1、00 stands for R 2、11 stands for G 3、22 stands for B 4、3333 stands for H 5、44 stands for S 6、55 stands for V.
The module's serial port is full-duplex, meaning that receiving and sending are independent of each other. Therefore, it is possible that while the MCU is reporting data, the module could also be sending data to the MCU.
Yes, they are the same. A long press on the master button resets Wi-Fi, while a short press turns the power on or off.
Hello, all modules within the no-code development solution will be flashed with firmware according to the configuration information provided on this side. Once the modules are dispatched, they cannot be modified. Tuya ensures the security and reliability of customer products, so if there is any modification to the configuration information, you will need to place a new order for the modules, re-flash the firmware, and only then will the changes take effect, as online updates are not available. Refer to the attached figure: if firmware modifications are needed during the debugging process, after making the changes, you must click to regenerate the firmware, and then either claim a free production certificate or purchase one to re-flash the authorization before it can be synchronized to the module. Refer to the attached figure, if the firmware needs to be modified during the debugging process, you must click to Regenerate Firmware, and then obtain/purchase a production certificate for free to re-burn the authorization before it can be synchronized to the module. 1. For batch modules that have not been soldered, it is recommended to arrange rework with the business. 2. For a small quantity and with the conditions for burning, it is recommended to obtain/purchase a production certificate for free and self-burn. Production certificate purchase link: https://platform.tuya.com/purchase/index?type=3 Self-burning reference: https://support.tuya.com/en/help/_detail/Kcyugch1dtuej If you encounter problems during the self-burning process, you can submit a technical ticket to contact us.
Currently, Wi-Fi supports up to 7 channels, while the no-code development solution with Wi-Fi power consumption statistics supports up to 4 channels, and Bluetooth supports up to 5 channels.
Yes. You can change the brightness value on the Hardware Development page during product creation.
Currently, it can be set to 1%.
Yes, it can be set. During the product creation development steps, the number of power-off events to enter pairing mode can be set under "Hardware Development".
No, currently, it does not support switching scenes.
When creating a Wi-Fi no-code development solution for lighting, the current strip lights solution can be configured to use a button for pairing, while the light source solution requires power cycling to enter pairing mode.
The Zigbee light source solution currently does not support a button-enabled configuration. However, the Zigbee SMB driver solution supports the functionality of a button, which can be used to reset the pairing.
Under a good network environment, the standby power consumption of Tuya's no-code development solution for lighting is below 15mA. To pass the T20 power consumption certification, both the module and the circuit need to work together, with their combined power consumption being less than 0.2W.
15pin RXD1 corresponds to IC- P10 16pin TXD1 corresponds to IC- P11.
Yes. You can modify the settings on the developer platform during product creation.
The corresponding design draft size is 667*375.
The voice is issued through the cloud, the pure Bluetooth mode does not work, it can be issued through the cloud after connecting to the gateway.
0~2400mV, please refer to the firmware configuration for details.
Tuya's proprietary USB to TTL converter uses the CP2102 chip.
There are two common methods to enter the pairing mode: "Manual reset and then breathing or twinkling" means that after the module is powered on, it will enter the network distribution state by switching on a specific number of times or pressing a key for a certain period of time. "Always breathing or twinkling after power on" refers to products that are not equipped with a network. After the device is powered on, it automatically enters the fast flash network configuration state.
The Beacon remote control can operate the light during network pairing and will interrupt the pairing process; The Wi-Fi FFC remote control must be paired after the light is connected to the network, so there is no control issue during the network pairing.
There are some momentary spike or shake when pressing the button. To avoid false triggering, recommended to add a 104 capacitor to ground.
The I/O buttons internally have a weak pull-up, and if the button is defined as low-active, it is recommended to add an external pull-up resistor for more reliable operation. If the button is defined as high-active, it is suggested to add a pull-down resistor.
Burn the original SDK demo for testing; if it is successful, re-transplant the business code based on the demo. Check if there is any logic in the code that turns off the Bluetooth broadcast upon power-up. If so, the logic of turning off the broadcast upon power-up needs to be modified (such as adding a 1-minute delay) because using a dongle to perform an RSSI test requires scanning for the device's Bluetooth broadcast, and turning off the broadcast would lead to a test failure.
Hello, account deletion/cancellation is permanent. After deletion/cancellation, the app and product will no longer be manageable, and other services associated with the account on other platforms will also be unavailable. If you wish to change the company account or update the company authentication information, you can simply switch accounts or apply to revoke the existing authentication information without needing to cancel the current account. If you are certain about deleting/cancelling, you can log in to the Tuya Developer Platform - Account - Account Center - and click on the Delete Account button. Note: The system will assist in determining whether the deletion/cancellation will have a significant impact on the product. If it is determined that self-cancellation is not possible due to a significant impact, but you still need to cancel, you can submit a Tech Tikect on the cancellation page for further processing.
https://youtu.be/6IarPHIOdoQ If a brand wants to create a product, he needs a planner to help him create a product plan. He needs his own buyer to purchase modules from Tuya. For products that have been shipped, he needs his own internal market operations staff and customer service to check the market. In the authorization management, the "developer" authority can be authorized to the solution provider, the "purchaser" can be authorized to purchase, the "data operation" can be authorized to the market operation personnel, and the "customer service" can be authorized to the customer service personnel.
Not all panels support web page jumping function. If you have configured it but cannot see it, it is possible that the selected panel does not support this feature.
Production certificate splitting and product replacement are not different on Tuya Developer Platform and PMS. Both the two platforms provide the functions of certificate splitting and product replacement. In the future, production certificate splitting and update will be available only on Tuya Developer Platform.
The default PWM frequency of Wi-Fi, Sigmesh, Zigbee is 1K, and the range is from 300hz to 20Khz. It is generally recommended to use the default value for the frequency. high frequency will lead to PWM instability and therefore is not recommended.
This is because the product uses custom firmware or firmware uploaded by the factory, and therefore, the firmware information of the copied product is empty. In this case, you need to go to theHardware Commission step of the copied product, select a module, and configure firmware again.
This is because the BL0942 and HLW8032 are metering chips with a serial communication interface and need to be connected to the client serial port of the Tuya module. Tuya uses the default configuration recommended by the manufacturer (1 mΩ resistor).
Currently, the mobile phone number registered with the PMS account can log in to the Tuya Developer Platform, but only by modifying the PMS mobile account can the IoT account be synchronized and modified. The reverse is not possible.
Please confirm whether the event name is added according to the document, you can refer to: https://developer.tuya.com/en/docs/iot/common-app-sdk?id=K9m1dldk26u64#title-6-Frequently-used%20event%20name.
If the device can be bound with the Tuya all-in-one App, the control panel is normal and the customized App is abnormal. To resolve this type of issue, contact the customized app owner.
Weather service function data analysis and use, please refer to the document: https://developer.tuya.com/en/docs/iot/weather-function-description?id=Ka6dcs2cw4avp.
Yes. For Android users, the OS version must be 6.0 or above. For iOS users, the OS version must be 11 or above.
For the same module, after the device is networked, it can only be reset and removed on the device side, but it cannot be unbound from the cloud. You need to "unbind and clear data" on the APP to achieve real unbinding. For example: a module uses two sets of MCU programs. After product 1 is networked, the device side sends a reset, and then pairs with product 2. The network can be successfully paired, but after the network is paired, the app will still have the name or icon of the previous product.
Modules using Wi-Fi protocol or dual-mode protocol only require a serial port tool. Modules based on Telink chips for Bluetooth protocol require the Telink official burning tool and a serial port tool. Modules using Zigbee protocol require J-Link and a serial port tool. Both the Telink burning tool and J-Link are official burning tools from other manufacturers and need to be purchased separately. Link to purchase serial port tool:https://platform.tuya.com/purchase/store?page=1&tag=other&q=&type=commodityName.
If your OEM App needs to add a dark mode feature, you must first purchase value-added services. If your OEM App service package is for a lifetime, you can purchase: Custom App Tools. If your OEM App service package is an annual fee version, you can purchase: OEM App Advanced Features. After purchasing, enter the configuration page, enable the feature, and select the App theme template that suits you.
If you encounter the prompt shown in the attached figure when binding the development board Please confirm the model of the development board you purchased, whether it is an MCU development board or an SOC development board. Check the front model silk-screening of the soldered module on the development board. If it is an MCU development board, binding is not required. If it is an SOC development board, take clear photos of both the front and back of the development board (with clear ID and PASSWORD) and submit a technical ticket to contact us for assistance.
These two types of cards are not interchangeable. Choose the NB-IoT card if you use a NB module and choose the 4G card if you use a CatM, Cat.1 or Cat.4 module.
Yes, for details, please refer to the Sub-GHz module datasheet.
Typical power values: 802.11b: 17.5dBm; 802.11g: 15.5 dBm; 802.11n(20MHz): 14 dBm. Note: There are differences among various modules. For details, please refer to the module datasheet: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
You can query the device details interface and return the local_key parameter. Note: This interface is not suitable for sub-devices (such as Zigbee sub-devices).
If you encounter problems when using the template panel provided by us that cannot be run or packaged after development. You need to make sure that: Node version Windows recommends installing Node.js 12 series, Mac recommends installing Node.js 14 series; Installed the special app for debugging provided by Tuya; The tuya-panel-cli tool provided by Tuya is used correctly for template initialization and packaging.
Having EN 303645 certification is beneficial for passing PSTI certification, but there are differences between the two. If a product is sold to the UK, it needs to pass PSTI certification or issue a PSTI compliance statement (SOC) by itself; If not sold to the UK, PSTI certification is not required. Moreover, PSTI is only applicable to the UK market, while EN 303645 applies to the EU, some Asia-Pacific markets, and the market requirements of some global distributors.
Customer products (consumer devices with network connectivity) that need to be shipped to the UK market require this certification.
The default TopBar in the demo does not support modification. You can customize the rendering of the TopBar navigation bar using the TopBar component in the hookRoute. https://panel-docs.tuyacn.com/en/docs/navigation/top-bar.
Yes, you can use the timezoneId field in TYSdk.devInfo to obtain the time zone of the mobile system.
Certified test cases differ Prices differ.
UK PSTI certification is required if the factory uses Tuya Wi-Fi modules, and compliance certification must be carried out. For information about upgrades, please contact Tuya BD to consult Tuya's cybersecurity salesperson Yue Zhi (Huirui) or directly contact yuezhi.hu@tuya.com.
Products using Tuya modules generally support it.
Home appliance productsdo not support the CB series modules.
In the Tuya ecosystem, when a sub-device is powered on or its status changes, it needs to actively report its status to notify the gateway. In cases where there are many devices, unnecessary data packet reporting can cause network congestion. Developers can choose the following methods to reduce message interaction based on product business needs: 1. When the device is powered on or joins the network, it should actively report the DP and can randomly delay the reporting time to avoid a large number of wireless message conflicts during concentrated time periods; 2. When receiving a remote unicast control command for the device, the device should report the status using the QOS_0 message level; QOS_0: Sending data does not have a retransmission mechanism, and the gateway does not need to reply with a Default response QOS_1: Sending data has a retransmission mechanism, and the gateway needs to reply with a Default response QOS_VIP_0: Priority is given to sending this packet of data, which does not have a retransmission mechanism, and the gateway does not need to reply with a Default response QOS_VIP_1: Priority is given to sending this packet of data, which has a retransmission mechanism, and the gateway needs to reply with a Default response 3. When receiving a zigbee standard group control command for the device, the device may not report the status, as the Tuya gateway has a mechanism for actively reading the device status, to avoid a large number of wireless message conflicts during concentrated time periods; 4. When the Tuya gateway sends a zigbee standard scene control command to the device, the device may not report the status, as the Tuya gateway has a mechanism for actively reading the device status, to avoid a large number of wireless message conflicts during concentrated time periods;.
Yes.
The support for radio standards depends on carriers and the network modules. China Mobile supports both 2G and 4G. China Telecom and China Unicom only support 4G. 1NCE supports 2G, 3G, and 4G. Besides the carrier, you must select the correct network module that supports the radio standard you want.
The Internal part of EN pin has been pulled high. It does not need to be processed externally, just leave it open.
Because the back of this module is made of sulfur-free plate, it cannot be screen printed for the time being.
You can use the callback function gpio_func_test(VOID).
The price of the module is composed of the chip and the authorization code. The price of the authorization code will vary depending on the product category, communication method, etc. Therefore, the prices of modules differ for different products.
The completed module order and the license order whose delivery mode is credential.
After you pick up and download new licenses, you can contact the Tuya customer service to obtain new tools for flashing.
It does not support that, only trial production and mass production module orders are supported.
Available licenses = licenses to be picked up - new picked-up licenses That is, the maximum quantity of new licenses that you can download is the quantity to be picked up in the original order. If you have already picked up some new licenses, the quantity shall be deducted. For example, if you place a license order for 1,000 licenses, 600 of which have been picked up, now you want to download new licenses to flash into the module, you can pick up 600 licenses at most. You can pick up the left licenses many times in any quantity. If you pick up the left 400 licenses, you can pick up 400 more new licenses.
With retransmission logic. If it is a Bool type DP, after the module sends data, if the MCU does not respond or the response value is different from the sent value, the gateway will retransmit 6 times.
Zigbee uses a mesh topology, which is a type of mesh network.
The MCU is required to respond with a heartbeat, or close the heartbeat using the 0x25 command.
You can use the no-development-required light string solution, which supports PWM dead zone configuration.
For the currently supported chips, please refer to the documentation: https://developer.tuya.com/en/docs/iot-device-dev/bluetooth_platform?id=Kc6fd92l28kkm.
It is PB5/PD2, for details please refer to the document: https://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty.
If it is 5-channel PWM drive mode, it will change. Because the platform can only modify the white light PWM frequency, other channels (RGBW) will follow the changes after modification.
First, check whether the module can be used normally. If it cannot be used and it is overheating severely, the module may be damaged. If it can be used normally, you can compare the temperature with other modules of the same model. Overheating also indicates that the module may be damaged. You need to check whether the voltage of the module on the device side is overvoltage and whether there is anti-static treatment on the production line.
There are 13 Chanel Central Frequency 1 2412MHz 2 2417MHz 3 2422MHz 4 2427MHz 5 2432MHz 6 2437MHz 7 2442MHz 8 2447MHz 9 2452MHz 10 2457MHz 11 2462MHz 12 2467MHz 13 2472MHz.
When purchasing an OEM App, many may not know how to get the App package for testing and how to publish it to the app store. Here is a summary of the process for both iOS and Android from building the App package to publishing it to the app store, as well as some common issues encountered during the process. The main steps from creating an App to publishing it to the app store include: 1. Create an App 2. Complete the relevant configurations 3. Create and configure the relevant certificates and other configuration items 4. Build the App package and upload it to the developer center 5. Submit for review 6. Publish the App Among these, steps 3, 4, and 5 are where most issues occur. Below we have summarized the common issues for both iOS and Android during these three steps: iOS common issues: Upload the description file permissions statement is wrong, please check whether the right statement or configuration errors: com.apple.developer.authentication-services.autofill-credential-provider,how to solve this problem? The rights statements in the uploaded provisioning profile are incorrect. Check whether the following rights have been stated or correctly configured:com.apple.security.application-groups, how to solve it? When uploading the push extension description file, an error is reported: Please check the permission declaration or configuration: application-identifier, how to solve it? Received e-mail from Apple： iOS Distribution Certificate will no longer be valid in 30 days, what should I do? The error message after uploading the P12 certificate is: The password does not meet the requirements. How can this be resolved? Do we need to select the Critical Alerts capability permission when creating the AppID? Failure to upload ipa application package on the iot platform，how to solve it? Android common issues: Google Play failed to upload APK file The App was rejected when listed on Huawei's store, with the feedback as follows: "Please modify the content of your privacy.
First, it is important to clarify that all the text seen in the App comes from three sources: App local Configured on the platform Issued from the cloud Let's start with the first type--App local Applicable to SDK-developed Apps, Android is configured in the local resource files, and iOS is configured in the local resource filesLocalizations The multi-language resources we currently support are available, click to view The second type--Platform configuration The App's multi-language includes the following, supporting individual modification and batch Finally, the third type--Issued from the cloud Entries that still cannot be adapted after the above modifications are most likely issued from the cloud, commonly seen on H5 pages, such as "Common Questions and Feedback", "Network Configuration Page", "Pages redirected from Google Assistant and Alexa", etc. It also includes entries for scene conditions and so on. If you encounter entries that cannot be modified, you can submit a ticket for consultation Other issues Is it possible to modify the multi-language support in the UI business package? How long does it usually take for the multilingual release to take effect?
Foreword: This article is a compilation and summary of high-frequency questions about programming by Tuya technical support experts based on customer's daily inquiries. From now on, you don't need to search for answers in a multitude of documents, as we have prepared the essence for you. We hope this collection of high-frequency self-service networking questions and answers will be of valuable help to you, and we look forward to your valuable comments and feedback. Whether it is positive praise or suggestions for improvement, they will become our further [guidance for effort] ❤️. Applicable to: Development methods: SoC zero-code development, MCU SDK development Development stage: During development, prototype debugging stage, small batch prototype stage. A product has been created on the IoT platform, and Tuya modules have been ordered during hardware development Order delivery form: Blank delivery module If you need a completeZS series modulenanny-level programming tutorial, please check: https://support.tuya.com/en/help/_detail/Kcw9sivkaaki0 Main Content: 1. What software environment is needed for self-service programming? 1. Software environment: Register a PMS account, download the cloud module from the production solution 2. Download the production certificate, if it is a newly purchased blank delivery module, you can produce the certificate in advance in the order; if it is an old module, or you need to reprogram, purchase the production certificate under the corresponding product ID (Note: For products developed without coding, choose the production certificate as the delivery form, not the authorization code list, not just authorization) 2. How to choose the programming tool? The choice of programming tools is determined by the chip platform inside the module. First, select the programming tool according to the module model: CB series, WBR series, CR series, BP series only need a serial port ZT series, BT series need a serial port, EVK (or Te-link), Bluetoot.
You can control whether to render the OfflineView in hookRoute by using showOfflineView: true to display it, and false to hide it.
OEM App provides default support for text editing in six languages: Simplified Chinese, Traditional Chinese, English, French, German, and Russian. If you need to configure other languages, you can enable the corresponding permissions in the multilingual configuration. Additional expandable languages include: Spanish, Arabic, Japanese, Italian, Greek, Bulgarian, Czech, Korean, Dutch, Turkish, Hebrew, Polish, Hungarian, Vietnamese, Kazakh, Norwegian, Danish, Finnish, Swedish, Portuguese, Indonesian, Thai, Romanian, Hindi, Burmese, Ukrainian, Slovak, Malay, Bengali, Urdu, Uzbek, Uyghur, Mongolian, Macedonian, Filipino, Croatian, Serbian, Slovenian, Estonian, Latvian, Lao, Hausa, Persian, Bosnian, Nepali, Latin, Swahili, Telugu, Marathi, Belarusian, Kinyarwanda, Xhosa, Azerbaijani, Kashmiri, Javanese, Tamil, Gujarati, English (UK), Traditional Chinese (Hong Kong SAR), Portuguese (Brazil), Spanish (Latin America), and Lithuanian. The App currently provides text in twelve languages: Simplified Chinese, Traditional Chinese, English, German, French, Italian, Portuguese, Spanish, Japanese, Korean, Russian, and Arabic. For other languages, you can translate them yourself or choose a multilingual translation service (https://www.tuya.com/vas/commodity/MULTILINGUAL_TRANSLATION).
Within an average of 15mA.
Please log in to the Tuya Developer Platform, go to Purchase Manufacturing Credential, and click on Download Credential. https://iot.tuya.com/purchase/token.
You can find your app on the IoT platform, then go to Optional Setting -- More, set: Disable.
For example: The number of ON/OFF to reset for the device is 3, and the number of reset cycles is increased by 2 after the device is networked. Number of reset cycles for un-networked devices: Remains unchanged, still 3 times. Number of reset cycles for networked devices: Add the increased number of reset cycles for networked devices to the number of power reset cycles for networked devices, which is 5 times in total. Thus,to solve the issue of multiple devices being powered and networked at the same time, if some devices fail to network, they can be reset 3 more times to enter the networking state. Devices that have completed networking will not enter the networking state after 3 resets.
We recommend that you confirm whether the data you reported is in bytes or JSON format. Some panels only support byte format reporting. If you need to set JSON format, you can do so in the device interaction-Edit Panel-Configuration Functions. (If this configuration is not available, it means that the panel does not support report configuration and only supports byte format).
Use a multimeter to check if there is an open circuit between the pins of the LTE module and the SIM card holder, and whether there is a short circuit between the pins and GND. Check if the parameters of the 22Ω resistor and 33pf capacitor are correct. Check the hot-swappable detection of the SIM cardDET pin,to see if it is short-circuited, the voltage on this pin should be 1.8V when the card is inserted. Check the SIM card for any stains, which are usually caused by poor contact with the SIM card. If all the above steps have been checked and the problem has been ruled out, try pressing down on the SIM card and then power on the device for testing.
Customize Hot Categories: Log in to Tuya IoT Platform, select "Operation" -- "Knowledge Base" -- choose the App you are using -- "Add a Primary Category" Customize Display of Frequently Asked Questions: "Operation" -- "Mark as FAQ" As shown in the figure below:.
The possible reason is that the air conditioner belongs to a standalone air conditioner. Air conditioners are divided into two categories, one is the screen air conditioner, and the other is the standalone air conditioner. The screen air conditioner needs to record the last opening state, so the code issued may be in a format similar to M1_T25_S1. The standalone air conditioner, on the other hand, does not have a state record, the switch is the same source, and it only has a temperature adjustment function, which is adjusted by the temperature + and temperature - buttons step by step. You can check the field single_air by calling the following API to confirm whether the air conditioner is a standalone air conditioner: Supported remote control button information: https://developer.tuya.com/en/docs/cloud/ff7882b8a5?id=Kb3oe37sqdjx5.
When you click Update in the app, the cloud will send an upgrade notification to the module. When the module receives the notification, the 0x0A upgrade command is sent to the MCU. Packets are obtained from the cloud based on the packet size defined by the MCU. Packets are transmitted one by one. The MCU processes packets obtained.
The inconsistency between the IoT platform json configuration and the DP function setting leads to the following:.
Log in to the IoT console (https://iot.tuya.com/) -- Find the corresponding PID -- Hardware Development -- Configure Firmware -- Disable Bluetooth function.
First, insert the solder pads at the bottom of the module into the probe, then press down on the module to push the probes on both sides into the middle of the solder pads of the stamp holes on both sides of the module.
Just modify the borderColor color in the tabBarStyle property and it will be fine.
This is due to the dependent python3.exe not being called correctly, it should be noted that: Python 3.8 has been installed and the environment variable has been configured. In the Python 3.8 installation path, copy python.exe and rename it to python3.exe. The Python 3.8 environment variable has higher priority than other Python versions. If you are not sure whether Python 3.8 is installed, open cmd and enter where python to see all the installed Python versions. 1. Copy python.exe and rename it to python3.exe. 2. Add the environment variable.
Check if the network configuration exceeds 15 minutes: Distribution network not exceeding 15 minutes: Remove the distribution network, wait for 10 seconds, power on again, and scan the production test signal to enter the production test. Distribution network exceeding 15 minutes: Need to re-burn the authorization.
Yes, Wi-Fi modules support two types of time acquisition. You can choose to obtain Greenwich Mean Time or local time. Specific protocol: https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb#title-18-%E8%8E%B7%E5%8F%96%E7%B3%BB%E7%BB%9F%E6%97%B6%E9%97%B4(%E6%A0%BC%E6%9E%97%E6%97%B6%E9%97%B4).
In principle, changing the parent PID is not supported. If you want to associate the panel with other products, you can find the corresponding uiid in App-Panel Management-Panels Developed by me, and click on Manage Associated Products. If there are special circumstances that require changing the parent PID of the panel, you can feedback to your customer manager.
RAW is a pass-through protocol that requires the parsing protocol document for decoding. For off-the-shelf products, you can refer to the protocol parsing instructions in the remarks of the corresponding DP points in the functional description. For customized products, please contact the relevant project coordinator to obtain the necessary information.
This is probably caused by a server proxy that has an expired security certificate. You can update the yarn configuration to allow connection to the expired certificate by entering "yarn config set 'strict-ssl' false -g" in the terminal.
This is due to an incorrect version of Node. For Windows, it is recommended to use version 12.0.0, and for Mac, it is recommended to use the Node 14 series.
DP Basic Concepts DP (Data Point) is an abstract way to describe a device object's function point. DP operations represent changing the device's state through predetermined functional characteristics, such as using a switch DP to change a device's on and off state. Tuya defines DPs within 100 as Tuya standard DPs, and 101-255 as your custom DPs. DP Basic Types The common types of DP include Boolean, numeric, enumeration, character, bitmap, and transparent (Raw) types. Purpose of Custom DPs Terminal devices can carry out personalized function development by creating custom DPs when accessing the Tuya cloud. Standardized Access Process 1. Add a private transparent cluster0xEF00. #define PRIVATE_ATTR_LIST \ {0x0000, ATTR_INT8U_ATTRIBUTE_TYPE, 1, (ATTR_MASK_TOKEN_FAST|ATTR_MASK_SINGLETON), 0, (UINT8_T*)0x00 }, /* current positiong lift percentage*/\ {0xFFFD, ATTR_INT16U_ATTRIBUTE_TYPE, 2, (ATTR_MASK_READABLE), 0, (UINT8_T *)0x0002}, const TAL_ATTR_T g_private_attr_list[] = { PRIVATE_ATTR_LIST}; #define DEF_CLUSTER_PRIVATE_CLUSTER_ID(a) \ { CLUSTER_PRIVATE_TUYA_CLUSTER_ID, (TAL_ATTR_T *)&((a)[0]), GET_ARRAY_LEN((a)) }, CONST TAL_CLUSTER_T app_server_cluster_list[] = { DEF_CLUSTER_PRIVATE_CLUSTER_ID(g_private_attr_list) 2. Modify the capability values in the JSON file. Inapps/xxx_demo/appconfig.json, modify"manufacture_name":"_TZ3210_". { "firmwareInfo": { "description": "this is a demon project", "dev_role":"sleep_end_dev", "module_name":"ZT3L", "chip_id":"TLSR8258F1KET", "image_type":"0xD3A3", "manufacture_id":"0x1141", "model_id":"TS0202", "pid": "", "manufacture_name": "_TZ3210_" } } The dev_role item can be selected according to the type of device created, such as router or sleep_end_dev. The script will connect to different libraries based on different configurations. The above pid item can be filled with the product pid created on the Tuya IoT Development Platform. 3. DP transparent transmission business requires the cooperation of the panel. It should be noted tha.
Developing and debugging wireless devices requires setting up a packet capture environment. Packet capture allows you to visually see wireless data exchange, which helps in analyzing and locating issues. Follow the steps below to set up a packet capture environment. Preparation Hardware: CC2531 USB Dongle Software: Ubiqua Packet Capture Tool. This tool is paid software, with a two-month free trial period. After the trial period, it needs to be purchased, priced at 65 US dollars per month. Introduction to Packet Capture The main page of Ubiqua Packet Capture is as follows: 1: Device 2: Main Interface 3: Single Packet Decomposition Window 4: Raw Data Introduction to Common Tools: 1: Save Current Data 2: Scroll Display 3: Auto Select Latest Packet 4: Clear All 5: Current Filter 6: Enable and Disable Filter 7: Create New Filter 8: Edit Current Filter 9: Delete Filter Adding Packet Capture Plug in the packet capture device CC2531 USB Dongle. If the device fails to add, you can download a driver wizard to install the driver. Click on the menu bar DeviceAdd Device. In the pop-up device addition box, select Texas Instruments, check Texas Instruments CC2531, and then click Add Device Channel Checking You need to know the channel of the gateway After pairing Tuya's App with Tuya Zigbee Gateway, you can easily obtain the channel by checking the device information of the gateway. As shown in the picture above, the current channel is on channel 15. Packet Capture Channel Selection 1. Open the packet capture, right-click on Texas Instruments, and select Channel24 (0x18, 2470 MHz). 2. Click the switch button on the device to start. 3. Select OptionsSecurityKeychain, and click Add. 4. Type select Application or Trust Center Link Key, enter the Key 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 and then click Add. Key added successfully, packet capture environment setup is complete. Packet Data Viewing The packet capture needs to capture the complete networking process between the.
The range of Bluetooth connection intervals is 7.5ms~4000ms, with a unit of 1.25ms. The smaller the Bluetooth connection interval, the faster the Bluetooth communication rate, the better the product user experience, and the higher the power consumption will be. The larger the Bluetooth connection interval, the slower the Bluetooth communication rate, the worse the product user experience, but the lower the power consumption will be. Apple's requirements for Bluetooth connection intervals are as follows, see Accessory Design Guidelines for Apple Devices page 114:.
The range of Bluetooth broadcast interval is 20ms~10240ms, with a unit of 0.625ms. The smaller the Bluetooth broadcast interval, the faster the Bluetooth communication rate, the better the product usage experience, and the higher the power consumption will be. The larger the Bluetooth broadcast interval, the slower the Bluetooth communication rate, the worse the product usage experience, but the lower the power consumption will be. The recommended Bluetooth broadcast interval by Apple is as follows, see details on page 113 of Accessory Design Guidelines for Apple Devices:.
Issue Background: Metering products (metering sockets, metering circuit breakers, etc.), report abnormal electricity usage, such as suddenly reporting 1455kWh, and sometimes the reported voltage drops to 0V. Cause: Internal circuit power supply is abnormal, causing the metering chip to restart. Troubleshooting and Solution: A common cause for chip restarts is an abnormal power supply. Disconnect the original 3.3V power supply circuit of the circuit board, and externally connect a 3.3V DC power supply or a 3V battery for comparison testing. If the external power supply testing is normal, use an oscilloscope to monitor the 3.3V power supply waveform and ripple of the circuit board, and contact the power IC supplier for rectification. Module Power Supply Requirements: https://support.tuya.com/en/help/_detail/Kd2eyz8fq172o Ripple Test Reference:https://support.tuya.com/en/help/_detail/Kd2fkobx4krhf.
Please follow the documentation to connect the module properly and put it into the burning mode, then click "Erase" on the original factory tool.
Currently, there are four versions available: Lite Plan, Basic Plan, Business Plan, and Ultimate Plan.
Type Development Method Binding Development Board Firmware Burning Authorization Module IO Breakout MCU Communication Board MCU SDK No Binding Required No Firmware Burning Required Only Module Serial Port Breakout SoC Main Control Board SoC/TuyaOS Binding Required Self-service Firmware Burning Required All Module IOs Breakout For example, using the BT3L Sandwich Development Board: The MCU Communication Board is suitable for the MCU SDK docking solution on the Tuya IoT Development Platform BLE, providing convenient Bluetooth networking capabilities for the MCU. The MCU Communication Board has been pre-burned with a universal docking program, and the hardware only breaks out the module's serial port. When in use, the BT3L Communication Board is connected to the MCU through the serial port for debugging. The SoC Main Control Board supports burning Tuya IoT Platform BLE SoC firmware without development, or developing your own firmware based on the module SDK. It can be used in conjunction with the functional board to build product prototypes. The SoC Main Control Board generally does not have any programs inside. It requires binding the development board's SN and password to obtain the production certificate for burning before use. The hardware breaks out all the module's IOs to the pin headers on both sides.
Preface Confused by the multilingual issues of products? Not sure where to start? The task of modifying and adjusting seems huge and complex, and it's hard to find a clear solution? Don't worry, we have prepared a comprehensive FAQ collection for multilingual issues for you. This tutorial selects the most common multilingual issues on the platform, and we hope our in-depth solutions can help you quickly locate and solve the problems. 1. The multilingual display of the device name is incorrect, including the following situations: The phone system language displays English, but the device name is in Chinese, and it needs to support English Need to modify to a specified device name For the above problems, you can click: How to modify the device name in multiple languages? 2. Multilingual modification of the App network configuration guide page, network configuration guide copy modification You can click: Configure Pairing Information 3. Panel SDK multilingual issues How does the configuration of multiple languages perform in terms of priority on the platform when developing using the panel SDK? Does the panel SDK internationalization i18n support German? Do the UI packages uploaded by the panel SDK need to be in multiple languages at the same time? Why is only English displayed in the app installed on an Android smartphone after other languages are set using i18n, a language customization code, in the panel SDK? 4. App multilingual issues How long does it usually take for the multilingual release to take effect? Is it possible to modify the multi-language support in the UI business package? How to solve the problem that the page language is not effective after modifying the iOS system language on the phone? Can I batch export App Language Pack? How do I modify the language package of an app? 5. OEM App multilingual issues OEM App supports multilingual debugging, viewing the latest added or changed entries, meeting different business needs, you can click here: What is t.
Foreword This article is a compilation and summary of high-frequency questions about self-service networking by Tuya technical support experts, based on customer inquiries. From now on, you don't need to search for answers in a pile of documents, as we have prepared the essence for you. We hope this collection of high-frequency questions and answers on self-service networking can provide valuable help to you, and we look forward to your precious opinions and feedback. Whether it is positive appraisal or suggestions for improvement, they will become our guide to further [efforts] ❤️. Self-service Tools If you encounter networking issues, we recommend that you first consult the logs for resolution. Tuya IoT platform network-related log query address: https://iot.tuya.com/smart/logs/connect Self-check What should I do when my device fails to connect to the network? My device needs to be re-configured, but I don't know how to reset the device into EZ/AP Mode? The Indicator light changed from flashing to regular,but it still fails to connect? Can Tuya devices connect to the network through a 5G router? What are the considerations for configuring a dual-band router? Notes for Different Communication Types How do I configure a Wi-Fi device? How does the device use the cable mode to connect internet？ Door lock network pairing failed? Can I pair multiple combo devices simultaneously? Can I add devices normally without opening the App location permission? How do I configure network connections for Zigbee devices? Why does the app’s search and configuration function fail to add devices? High-frequency Questions How to deal with issues with distribution network after Apple system is upgraded to iOS 13? Why does App shows the device has been bound to another account?How to unbind the device? What is the maximum number of supported bits in a network pairing password? Do I have to reconnect all my devices to the network after I change the Wi-Fi password? Why does the name on the A.
Foreword: This article is a compilation and summary of the frequently asked questions about self-service linkages by Tuya technical support experts based on customer daily consultations. From now on, you don't need to search for answers in a plethora of documents, as we have prepared the essence for you. We hope this collection of frequently asked questions about self-service networking can provide you with valuable help, and we look forward to your precious opinions and feedback. Whether it is positive praise or suggestions for improvement, they will become our further [guidance for effort] ❤️. Self-service Tools: How to query the created scene linkage and the success or failure logs on the platform? Frequently Asked Questions: Scene linkage, when a device reports a certain value for a certain function point, triggers linkage. However, what is the reason for the device reporting but not triggering the linkage? In a smart speaker-based scene linkage, when more than 10 devices are added, the last two or three devices respond with latency. Why? When creating scene linkage, the execution tasks are SMS notification and phone notification. Why did the phone notification fail?
Hello, the panel does not support switching fonts.
Poll Configuration /* * Zigbee poll configuration */ typedef struct { UINT8_T forever_flag; /// TRUE: forever poll if device no network(TAL_ZG_NWK_POWER_ON_ONLINE/TAL_ZG_NWK_JOIN_OK/TAL_ZG_NWK_REJOIN_OK) UINT8_T fast_swicth_parent; /// TRUE: if ack isn't received, will continue polling until the max number of failures is reached before switching the parent UINT16_T interval_ms; /// poll period (bet: ms) UINT16_T max_failed_times; /// enter parent-lost status when poll failed x times. UINT16_T duration_after_data_ms; /// tiemout waitting app ack (bet: ms) UINT_T duration_after_join_ms; /// wakeup time when join success.(for gateway get cluser data) (bet:ms) UINT_T duration_after_rejoin_ms; /// wakeup time when rejoin success.(for app use) (bet:ms) } TAL_ZG_POLL_CFG_T; Rejoin Configuration /* * Zigbee end-device rejoin config */ typedef struct { UINT8_T power_on_active; /// auto rejoin when power on. UINT8_T send_data_active; /// auto rejoin when send data if parent lost. UINT8_T reserved; /// Reserved UINT8_T attempts; /// max rejoin attempts when parent lost. UINT16_T interval; /// rejoin attempt interval when parent lost. } TAL_ZG_REJOIN_CFG_T; Register Device /** * @brief register router or sleep device * @return none */ STATIC VOID_T app_sleep_device_node_init(VOID_T) { // sleep end device node init TAL_ZG_NODE_CFG_T node_config = { .node_type = ZG_SLEEPY_END_DEVICE, .tx_power = 10, .scan_interval = 100, .scan_duration = ZG_SCAN_DURATION_3, .config.sleep_ed_cfg.poll_config.forever_flag = 1, .config.sleep_ed_cfg.poll_config.fast_swicth_parent = 1, .config.sleep_ed_cfg.poll_config.interval_ms = 250, .config.sleep_ed_cfg.poll_config.max_failed_times = 10, .config.sleep_ed_cfg.poll_config.duration_after_data_ms = 1000, .config.sleep_ed_cfg.poll_config.duration_after_join_ms = 60000, .config.sleep_ed_cfg.poll_config.duration_after_rejoin_ms = 15000, .config.sleep_ed_cfg.rejoin_config.power_on_active = 1, .config.sleep_ed_cfg.rejoin_config.send_data_active = 1, .config.
During the network configuration, the Tuya gateway reads 6 attributes under the basic cluster of the device to identify it. After the sub-device responds with data, the sub-device panel will pop up on the App. Zigbee 3.0 requires obtaining the Trust Center (TC) link key during the network entry process. If the TC link key fails to be obtained, the device will leave the network. In summary, the issue of the device going offline immediately after successful network configuration may be due to the failure to obtain the TC link key. The possible causes for this issue could be: The gateway reads the attributes under the basic cluster and registers them to the cloud. Right after the sub-device interface pops up on the App, the user exits the network configuration interface. At this point, because the network configuration mode is exited, the device fails to obtain the TC link key. During mass device network configuration, a large number of concurrent entries can cause the gateway to be busy, resulting in the device's TC link key request not being responded to. Interference and other factors may cause the sub-device's request key, the gateway's transport, and the subsequent verify and confirm as well as their APS ACK not to be responded to, leading to a failure in the TC link key exchange. It is recommended to take the following measures to avoid this: Use the gateway's local button (short press) to initiate extended network configuration. In extended network configuration mode, the gateway will register with the cloud after the device TC link key interaction, thus solving the problem of the device going offline due to not obtaining the TC link key. Do not exit the interface immediately when the sub-device panel appears during App network configuration. Waiting on the interface for 30s allows the gateway to remain in network configuration mode, facilitating the sub-device's acquisition of the TC link key. Refer to Wi-Fi Interference Troubleshooting to investigate the impac.
The neighbor table is maintained by receiving Link Status sent from nearby devices, where the Incoming Cost and Outgoing Cost in the Link Status indicate the signal strength of receiving from and sending to the neighbor devices, respectively. 0 indicates unreachable, and 1~7 indicate decreasing signal strength, with 1 being the strongest and 7 being the weakest. The Outgoing Cost in the above image is0, indicating that it can receive the signal from the other party, but the other party cannot receive its signal. This often occurs whenthe two parties are relatively far apart and the transmission power is not equal or whenthe other party has poor reception performance. An Incoming Cost of0 may be caused by the NWK Frame Counter decreasing during the operation of the device. To prevent replay attacks, neighbors will consider the device abnormal once the counter decreases.Tuya does not allow a device to be re-flashed with authorization while it is connected to the network during normal operation, as this would cause the NWK Frame Counter to start recounting from0. If necessary, the device can be removed from the network before re-flashing with authorization.
Possible reasons are as follows: Network storm. The initial Radius value sent is0x1E, and the Radius decreases by1with each forward. In a normal Tuya network, the maximum number of forwards is about 8 hops. If it becomes0x0D, which means it has been forwarded 17 hops, there may be devices in the network withtoo small a broadcast table or too short a broadcast table lifetime parameter configuration, causing devices that have already forwarded the data to forward it again, leading to a loop. Please check if the broadcast table parameters are normal. End-to-end Route Request did not receive a Route Reply, resulting in the routing table not being effectively established, causing the initiator to keep sending Route Requests. The routing table established through Route Request, the initiator sends data to the next hop, the next hop does not have a MAC Ack, or subsequent relay devices do not effectively relay the data packet and corresponding reply, resulting in transmission failure, causing the initiator to initiate Route Request again to try to establish a reliable path. Investigation can be conducted from the following aspects: Check if there are too few selectable relay devices, and if the distance between hops is too far, in which case a Router device can be added to relay the data. Check if the target device is present in the neighbor tables of other devices; if it is not present in the neighbor tables of other devices, it may be that the device has a problem with wireless transmission and reception. Check if the target device has experienced a decrease in NWK Frame Counter, which would prevent other devices from communicating with it. Check if the target device has weak reception or transmission capabilities. Check if there is 2.4 GHz or radio frequency interference near the target device causing the issue.
Tuya Zigbee sub-devices will record abnormal behaviors and report the recorded anomalies to the gateway after networking and during regular network timing. The following table lists the supported error codes: Error code ID Description 0-15 Original hardware built-in Reset sources1: Unknown error2: FIB reboot3: Upgrade reboot4: External IO abnormal reboot5: Low voltage reboot6: Watchdog reboot7: Software initiated reboot8: Software Crash reboot9: Flash abnormal reboot10: Irrecoverable hardware abnormal reboot11: Hardware internal CPU access error12: Power-off reboot 16 Reboot: Sub-device abnormal reboot 17 Disconnection: Sub-device lost connection with the parent node 18 Active disconnection: Sub-device business layer logic triggered the device to disconnect itself 19 Passive disconnection: Sub-device disconnected after receiving a remote disconnection command 20 IO exception: Device IO remains in a latched state for an extended period (e.g., button continuously pressed) 21 Memory leak: Memory not released causing insufficient SDK resources, etc. 22 Short address change 23 Received ZCL_RESET_TO_FACTORY_DEFAULTS_COMMAND_ID command 24 Received gateway F0 command 25 Wake-up time too long (low power device wake-up monitoring) 26 Received gateway's abnormal factory reset command 27 Device self-recovery failure 28 Device group upgrade failure Error codes are in string format, with every 5 bytes representing one error code data. The first 4 bytes are a little-endian timestamp starting from 2000.1.1 00:00:00, and the last byte is the event ID. Adding 946656000 to this timestamp gives the UTC time, which means the above error code event indicates a remote disconnection event occurred at 2023.12.12 14:33:13. When the sub-device has not successfully synchronized the time, the timestamp carried by the error code data is all zeros.
Many to one route request The Many to One Route Request is commonly used in Zigbee centralized networks, where the coordinator broadcasts and routers relay to establish router routing tables and the gateway's source routing tables. The advantage is that it can uniformly refresh the aging time of the routing tables in routers across the network. The coordinator sends Many to One Route Requests at reasonable intervals, which can reduce the probability of individual nodes initiating end-to-end Route Requests, thereby improving network stability. The Tuya gateway periodically sends Many to One Route Requests. During data forwarding, routers in the network will calculate their Path Cost to the gateway and add their own address to the data packet. After routers in the network forward the Many to One Route Request, if a router has data to report to the gateway and the gateway is not its neighbor, the device will choose the path with the smallest Path Cost from the received Many to One Route Requests as its reporting path. It updates this path into its routing table and sends a Route Record, making the next hop in the routing table the MAC Destination of that Route Record. The next hop will select a path based on its own routing table or neighbor table to forward the data, passing it through multiple hops until it reaches the destination address. Unicast route request When a device needs to send data to a target device, and the target device is not in the initiating device's neighbor table or effective routing table, the initiating device will initiate an end-to-end Route Request to try to establish a data transmission link to the target device. The advantage is that it can quickly establish a routing table to the target device and flexibly establish an end-to-end communication path. After the sending device issues a Route Request, routers in the network that receive the packet will check whether the target device is themselves, their neighbor, or in their effective routing.
Starting from May 9, 2023, new devices created with the Tuya platform Zigbee solution that have not purchased the Tuya authorization code will be restricted by default from accessing. Devices need to go through the authorization burning process to access and recognize the panel. It takes time for the gateway to recognize the device and register it with the cloud. After the sub-device has successfully joined the network, you need to wait for about 30s to confirm whether the panel can pop up normally.
The Tuya gateway periodically reads the Router devices in the network, and if it fails to receive a response after several attempts, it considers the device to be offline. When the gateway reads data from the device, or receives ZCL layer data reported by the device, the gateway will consider the device to be online. Low-power devices will periodically report Power Configuration: Report Attributes as a heartbeat packet. When devices in the network occasionally go offline or appear online, troubleshooting can be done from the following aspects: Due to packet loss in the relay or other issues, the gateway fails to read the device, and can only rely on the device's report to refresh the online status. Packet capturing can be used to confirm whether the gateway's Read Attribute link can normally receive the Read Attribute Response. If the device does not Report, it can only rely on the gateway's reading to refresh the online status. The Tuya gateway reads the attributes under Basic when the device joins the network to identify the device type. The joining device will confirm the network it joined is the Tuya gateway through this behavior, and will actively report data only under the Tuya gateway. If there is no Report data, please re-network the device. Check whether the gateway and sub-device antennas are functioning properly. Incompatibility of the gateway antenna or disconnection of the sub-device antenna can lead to abnormal send and receive functions. Confirm whether there is 2.4 GHz network interference or radio frequency interference near the sub-device and gateway. In an interference environment, data transmission may be intermittent, and the App will display the device as sometimes offline, sometimes online.
Regarding the setup of the Zigbee packet capturing environment, refer to Ubiqua Packet Sniffer Usage.
The production test part of the code is managed by the SDK's underlying layer, and the application layer does not need to implement the related serial port interaction anymore. It should be noted that time-consuming device operations should not be added during production testing, such as initializing I2C operations for peripherals within the production test processing function. Taking too much time will cause the device to fail to receive subsequent data sent by the upper computer. When the problem cannot be located, first upload the Demo compilation product to the Tuya backend for burning authorization to ensure that the Demo burning authorization can be completed normally and that there are no issues with the environment. Regarding the Telink platform: Normal mass production programs should not have preemptive Log output, which should be avoided to prevent related anomalies. Enabling preemptive serial port printing will disable the interrupt source during printing, causing the serial port reception to be abnormal. BOOL_T app_print_get_cfg(UINT8_T *print_type, UINT8_T *disable_irq, GPIO_PORT_PIN_T *gpio) { gpio-port = PORT_C; gpio-pin = PIN_4; *print_type = 0;//select the io for uart function;1:uart,0:gpio *disable_irq = 1; return 0; }.
After the device restarts, there will be a Basic: Report Attributes, where the 0xFFE4 attribute value is 0x01, indicating that the device has restarted. After the device restarts, a device that is connected to the network will first send several Link Status messages to establish a neighbor table, and at the same time, the device's NWK Frame Counter will increase by more than 1024. It can be confirmed whether a restart has occurred by intensively sending Link Status messages and observing jumps in the NWK Frame Counter.
Check if the product hardware and module antenna are obstructed, or if there are devices such as inductors nearby causing interference. Check if there are frequent interrupts occupying the Application (such as Timer interrupts). High-frequency interrupts will prevent Bluetooth interrupts from entering normally, leading to unstable Bluetooth connections. Currently, most platforms used by Mesh do not support interrupt nesting and priority, so it is recommended that the Timer interrupt period should be over 10ms, and it should be enabled as needed and turned off when not in use, in order to minimize the impact on Bluetooth interrupts. Reduce the code execution time in the interrupt callback, and cache the data to be processed later in theOPERATE_RET tuya_main_loop(VOID_T); function.
The Mesh upper transport layer supports a maximum of 380 bytes of effective data. That is, for the access layer packet sending, the opcode + data supports up to 380 bytes. Longer data will be segmented into multiple smaller packets at the lower transport layer, with support for up to 32 packets. It is not recommended to use longer data, as segmentation at the lower level will cause significant delays. For the rules of segmentation and the calculation of data length, please refer to the relevant documentation. Here, only access message data is introduced, which is the common communication data. Additionally, control messages are generally configuration data. Access messages are divided into unseq access messages and seq access messages. Unseq access message, which is the non-segmented access data, has a maximum length of 15 bytes. Subtracting the MIC (4 bytes), the maximum data length is 11 bytes. This includes the opcode, which means when using Vendor Model to send data, the opcode length is 3 bytes, so the maximum data length is 8 bytes. Seq access message, which is the segmented access data, has a maximum single packet length of 12 bytes, so the total length is 12n, where n is the number of segments. The 12n includes the MIC (4 bytes), so the actual user data length is 12n-4, minus the opcode length, which is 12n - 4 - opcode_len. If using Vendor Model, the number of segments is n = (data_len + 7) ÷ 12, and n is rounded to the nearest whole number.
If the connection is directly disconnected during the second network configuration, it is necessary to confirm the effectiveness of the service after the disconnection twice. If a system connection method is used, it is necessary to ensure that the device is broadcasting normally and the authorization information is valid during the second network configuration.
For common Bluetooth peripherals, Bluetooth broadcasting and Bluetooth connection are two different states, which are mutually exclusive. Bluetooth broadcasting: refers to the Bluetooth peripheral periodically emitting radio frequency signals, which are generally non-directional, and any other Bluetooth devices with scanning capabilities can receive this broadcast. Bluetooth connection: refers to the communication channel established between the Bluetooth peripheral and the Bluetooth host (usually a mobile phone/gateway), where both periodically send radio frequency signals to each other to maintain the connection, and other Bluetooth devices generally cannot detect these signals (except for packet sniffers). During operation, Bluetooth peripherals generally switch between broadcasting and connection states. The device enters the connection state when it is close to the phone, or when it needs to send business data, and disconnects from the phone and enters the broadcasting state when they move apart. However, some Bluetooth devices may be in both connection and broadcasting states at the same time. In this case, the device can be considered to have multiple roles. For example, a gateway may have both host and peripheral roles; as a host, it connects to peripherals, and as a peripheral, it is connected by a mobile phone. There are also some peripherals that support multiple connections and can be connected to two hosts at the same time, but this is relatively rare and will not be elaborated here.
After setting a scheduled task for the device panel, the module needs some time to interact with the cloud, including but not limited to synchronizing time, retrieving scheduled content, saving scheduled content, and establishing scheduled tasks. Therefore, it is necessary to wait for 30s-1min before disconnecting the network connected to the device.
It is using a domain name.
After the module is activated and operates continuously for 15 minutes, the production test entry will be closed. Contact the corresponding project manager to manually open the production test function.
No, the Wi-Fi-Ble module production test is closed, programming authorization cannot be performed, and it cannot enter the whole machine production test.
Only Wi-Fi-Ble protocol is supported (firmware version 1.5.21, json configuration version 1.0.5).
The following content will help you better choose the type of account to register, as well as understand how different members should register. Introduction to the CSA Membership System The CSA Alliance divides its members into 4 different levels, with different membership fees and benefits. They are as follows: 1. Associate Member — No annual fee, can only obtain product certification through certificate transfer (Note: Products using the Tuya Matter solution can obtain certificate transfer through Tuya) 2. Adopter — $7,000 per year, eligible to apply for product certification directly 3. Participant — $20,000 per year, eligible to apply for product certification directly 4. Promoter — $105,000 per year, eligible to apply for product certification directly Associate Member Registration Steps 1. Send an email to the alliance to apply 2. State the company you are cooperating with in the email We cooperate with the following company Company Name: Tuya Inc. Member Level: Promoter 3. Wait for the alliance's reply 4. You need to sign a cooperation document.
The current version of the development package does not support it yet, and it is expected that the corresponding bridging will be made available in the next version.
Supports Zigbee and Matter over Thread sub-devices. Zigbee can be bridged to Matter devices.
Currently not supported, will be supported in the future.
Using the SSD202 platform as an example, the gateway memory should be at least 24MB, with a minimum of 7MB for the data part.
There are two scenarios for initiating the pairing mode of a Matter gateway: If the gateway has not been added by any Matter App, it automatically enters the pairing mode within 15 minutes of being powered on. If the gateway has already been added by another Matter App, the App that has added it needs to enable the pairing mode. The operation to enable pairing in the Tuya series App is to enter the Matter settings interface and click onMatter Gateway Sharingto obtain the pairing QR code.
All roles involved in the network configuration and addition, including the Tuya gateway, the third-party App to be added, and the third-party hub to be added, need to be on the same local area network. The Tuya series App does not have to be on the same local area network, but it is best to be on the same network.
The App side has already implemented the related function, but the device side also needs to satisfy this function. The device side needs to have these function points: DP point leave_message, DP point voice_manager, and DP point call_miss_timeout.
Charging records are a premium paid feature, which requires you to select the corresponding advanced features before placing an order, and pay the related fees at the time of the order.
Similarly, if calibration is successful, it remains on; if not successful, it remains off.
Yes, after the Zigbee module production test is closed, it cannot enter the whole machine beacon production test, but it does not affect the firmware authorization.
Of course.
The error message is as follows: Solution: Find the package.json file in the demo, locate the husky and delete the configuration "husky": "^4.3.0",.
Currently, Android has added a new interface validateOpModePassword, and the door lock sdk version has been upgraded to lock-sdk: 5.1.1; iOS has added a new interface validateOpModePasswordWithDevId, and the door lock sdk version has been upgraded to ThingSmartLockKit 5.1.0.
Signal Strength dBm Level Description -30 Excellent This is the maximum signal strength achievable -50 Excellent This excellent signal strength is suitable for all types of network usage scenarios -65 Very Good Can enjoy smooth use of smartphones and tablets -67 Very Good This signal strength is sufficient for VoIP and streaming video usage -70 Acceptable This level is the minimum signal strength requirement to ensure stable data packet transmission, sufficient for browsing the web and sending/receiving emails -80 Poor Basic connectivity is achievable, but data packet transmission is unstable -90 Very Poor Mostly noise, inhibiting the implementation of most functions -100 Worst All noise.
Point the universal remote control towards the remote control at a distance of about 3cm to avoid the influence of ambient light.
Groups do not support local timing, but support cloud timing.
There are two control methods for the dual-channel warm and cool lighting solution, CW and CCT. CW refers to a dimming and color tuning method that uses two PWM signals to control brightness and color temperature. The two signals are CW and WW. CW controls the white light (high color temperature), and WW controls the warm light (low color temperature). CCT refers to a method where brightness and color temperature are controlled separately. One signal, Bright, controls the brightness, and another signal, CCT, controls the color temperature. CW control AC/DC constant current driving solution (switch) Advantages: High efficiency, good constant current characteristics, high linearity. Good dimming effect. Disadvantages: Poor EMI, circuit noise, significant color temperature shift at low duty cycle. Complex circuit layout, high cost. The module outputs two PWM signals, CW and WW. CW control AC/DC constant current driving solution (linear) Advantages: Low cost, no EMI issues, simple PCB layout. PWM dimming without noise. Disadvantages: Low efficiency, poor constant current characteristics within a narrow voltage range. Poor linearity. Fixed output voltage, significant color temperature shift at low duty cycle, etc. The module outputs two PWM signals, CW and WW. CCT control AC/DC constant current driving solution Advantages: High efficiency, good constant current characteristics, high linearity. Good dimming effect. Brightness control can be analog, without noise. Disadvantages: Poor EMI, color temperature shift remains basically unchanged. Relatively simple circuit layout, lower cost (compared to linear CW control, the cost is higher). The module outputs two PWM signals, Bright and CCT.
It is not recommended to use LDO to power the Wi-Fi module. If LDO is used, it is necessary to choose an LDO with a supply current of more than 500mA, and pay attention to heat dissipation. The module's working voltage input is 3.3V. If the input voltage of the LDO is higher than 5V, it is recommended to use a BUCK circuit to step down the voltage.
If the map data drawn by the sweeping robot is reported, it exists in the cloud. At this time, when you open the sweeping robot panel, it will pull data from the cloud, and you will be able to see the previously drawn map data.
No, you can't. Reason: The module will have a dedicated flash area for storing the PID. If there is already data in that area, it will not retrieve the PID from the firmware. If the area is empty, it will fetch the PID from the firmware and write it to the flash. Solution: Taking Telink as an example. Directly modifying the JSON file is useless. You need to use the original manufacturer's tool to completely erase the firmware, and thenclick on the setting and select 1016 to erase all the authorized burning. Finally, re-burn the new firmware and authorize it with the Tuya module, and you're good to go.
OCPP is an open communication protocol between Charging Stations and Charging Station Management Systems (CSMS). It is widely adopted globally (except in China). Meanwhile, the Tuya protocol is a private communication protocol based on the Tuya IoT model used between Tuya devices and the Tuya cloud. The protocol is based on a more intuitive and universal IoT model, and it provides a rich and mature SDK as well as IDE, greatly lowering the barrier to smart device development for developers. Tuya cloud and the protocol correspond to a global connection of hundreds of millions of devices, with tens of billions of device requests daily. After rigorous testing, it can provide a stable and reliable user experience to people around the world, complying with local security and privacy regulations. It can be seen that both OCPP and the Tuya protocol are communications from devices to the cloud, and they are interchangeable. Due to the security and reliability of the Tuya protocol and its extremely low development threshold, many developers have adapted the Tuya protocol, providing PBT home charging stations to users at home and abroad in bulk. Developers only need to integrate once, and then they can choose any Tuya module, enabling the device to support various protocols (Wi-Fi, Bluetooth, Zigbee, LTE Cat.1, Cat.4, Cat.m, NB-IoT, etc.). Tuya cloud provides Tuya devices with a wealth of capabilities, such as OTA upgrades, multi-language support for panels, third-party voice control, customized message push, and so on.
The Tuya Matter Hub includes Thread border router and Bridge functionalities, while also providing all capabilities related to Tuya IoT Pass and the ability for local interconnectivity and interoperability of devices.
Step 1, select "Device Pairing" in the 4th step of creating a product process on the IoT platform, as shown in the figure below. Step 2, select "Custom Mode", then uncheck the "Bluetooth" option. After the above operation, the App will not display the Bluetooth pairing guide page for this PID. This configuration is only for OEM App use.
You can query by yourself according to the following figure. If there is a problem during the query, you can feedback to us. 1. To query device details under the user, you can log in to the IoT account, click "Operation"-"User Management" in the left navigation bar to query, as shown below: 2. Exporting can obtain more detailed user information, such as device id, etc.
The TX3 foot of the module cannot be pulled high, please check if the TX3 foot of the module has been pulled high. In order to prevent TX from being pulled high before turning on, we have designed a serial port level conversion circuit, please refer to the following figure.
RF Transmission Frequency: For 802.11b/g/n-HT20: 2412~2462 MHz For 802.11n-HT40: 2422~2452 MHz For 802.15.1:2402-2480 MHz.
When the gateway frequently goes online and offline, it is important to first address the issue caused by network fluctuations. In this case, the following steps are recommended to resolve the problem: 1. Network Stability Assurance: By examining and analyzing the gateway's log information, utilize the platform's log viewing feature to diagnose and pinpoint issues. Ensure there are no abnormalities or interruptions in the network connection as indicated in the logs, thus improving network stability. 2. MQTT Connection Management: The frequent online and offline occurrences of the gateway may be due to MQTT connection issues. Check if there are instances where MQTT connections are immediately reestablished after being closed. It may be necessary to adjust the configuration of the MQTT client to resolve this problem. Additionally, for ordinary devices, there are throttling mechanisms in place on the cloud side. This means that devices cannot trigger operations rapidly and continuously, as it may trigger the throttling mechanism. Check the data transmission frequency of the devices to ensure they stay within the limits defined by the throttling rules.
Yes, you need to calltal_matter_init_identifyfor each endpoint but only once.
If the device is paired using the Tuya-enabled app, when the mobile app and the device are on the same LAN, control through Matter is preferred. When the mobile app and the device are not on the same LAN, the device is controlled through the data point (DP). If a device is added through a third-party speaker, such as HomePod, Google Home, or Alexa, it is controlled through Matter.
It is not necessary. The Matter version number is used to identify the certified product and configure Matter OTA updates.
Make sure you have added a HomePod that runs tvOS 16.5 or later to the Home app. The mobile phone and the HomePod must be connected to the same Wi-Fi network. The device must be in pairing mode.
Due to permission restrictions of Thread, pairing without an Apple home hub, such as HomePod and Apple TV, can fail. Before pairing, ensure that an Apple home hub is ready and connected to the same LAN as the mobile phone. This can improve the success rate of pairing and avoid potential issues.
If your product is already Matter-certified with an official Certification Declaration(CD), check if you have written the correct official CD to the device.If you are using a test CD, provide your 16-bit Matter PID and Google account to your project manager for allowlisting.
Generally, the development kit can work on all Linux devices. Recommended resources: a minimum of 3 MB of flash memory and 4 MB of RAM.
Method 1: Open the gateway panel on the mobile app and tap Device Information to find the channel. Method 2: After the SDK is started, it will generate a ZigbeeNetInfo.txt file in the directory specified by the .storage_path variable, which stores Zigbee network information such as Zigbee channel and PanID, as shown below: $ cat zigbeeNetInfo.txt Node ID:0 Pan ID:0x0044 # Zigbee network PanID Radio Channel:15 # Zigbee channel Radio Power:13 Extended Pan Id: 158F733C2F2325A6 EUI64: F1F2D3FEFFD76B08 Global Key: A2 42 0D D6 50 DD 3B C3 1E CD BD 82 8A 19 E4 92 Global FC:0xFFFFFFFF Network Key: A5 DA 43 DE 24 A3 7D 54 7A 6B 32 F1 EF 01 E3 A6 Network FC:0x00005001 Network Sequence Number:0x00 Method 3: Find the channel information in the startup log. [01-01 18:12:20:242 TUYA N][z3_slabs.c:147] nodeEuiStr = 588e81fffec70507. [01-01 18:12:20:242 TUYA N][z3_slabs.c:148] nodeId = 0x0000. [01-01 18:12:20:242 TUYA N][z3_slabs.c:149] panId = 0xbc4b. [01-01 18:12:20:242 TUYA N][z3_slabs.c:150] channel = 0x0f. [01-01 18:12:20:242 TUYA N][z3_slabs.c:151] ver = 1.0.8. [01-01 18:12:20:242 TUYA N][z3_slabs.c:152] netStatus = 0x02. [01-01 18:12:20:242 TUYA N][z3_slabs.c:153] extendedPanId: 5eaf522991cdd2e9 [01-01 18:12:20:242 TUYA N][z3_slabs.c:154] manufacturerId: 0x0001 [01-01 18:12:20:243 TUYA N][z3_slabs.c:160] netWorkKey: d7 1d 0f 07 ab 00 46 05 00 46 0b 01 00 30 fe ff.
After the device is activated, you can review the reported data of the device in Device Logs.
To enable gateway failover, the new and old gateways must either have the same PID or share the same firmware key and DPs. Common issues with gateway failover The code for gateway failover is not implemented as described in the developer documentation. For more information, see Gateway Failover. The faulty gateway failed to upload the backup information to the cloud and remained online for less than 15 minutes before the fault occurred. During the replacement, the fault gateway did not go offline. The firmware version of the replaced gateway does not match the new gateway, or the Zigbee firmware is outdated.
Search for the keyword scene in the log, find the logs before and after the linkage is triggered, and follow the troubleshooting steps below: 1. Check if the DP has detected the linkage. For example, DP 25 reportscond stat: 2, indicating the conditions for executing the linkage are met. [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:1402] cond-trig_tp: 1. [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:1411] dp:25 set new bool-val:1 [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:2759] == 1 1` [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:2792] cond:1 strategy:1 curr_stat:1 [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:2805] calc cond.and stat:2 [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:1430] trig_tp : 1 [dp_exp is 1] , is_cond_only_judge : 0 [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:1597] cond stat: 2. 2. Result of the linkage condition detection:true [09-17 18:17:53 TUYA D][condition.c:1660] conditions check begin [09-17 18:17:53 TUYA D][condition.c:1711] time_cond is disabled. skip [09-17 18:17:53 TUYA D][condition.c:1886] conditions check finish. result:true 3. action0 indicates the first action in the linkage. Check if the action is sent to the sub-device. If so, it means the gateway has executed the scene. [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:3522] in work-queue. execute scene:oxyOkOAYPolhVwhi begin [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:3543] rule oxyOkOAYPolhVwhi exe st:0 [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:2535] action0 is rule:EeOpIHKwYTSCZRPQ . begin to execute scene [09-17 18:17:53 TUYA D][scene_linkage_rule_exe.c:2475] action0 is dp cmd:{"cid":"e0798dfffe6ed1f7","dps":{"26":true}}.
Method 1: Open the gateway panel on the mobile app, as shown below. Tap the three-dot icon and then select Device Signal Detection to get the signal strength of the sub-device. Method 2: Search for LastHopLqi in the log and determine the signal strength based on its value. Excellent: 200. Good: 150 to 200. Fair: 100 to 150. Poor: 100 [callback-stub.c:2861] NodeId:0xab3b, LastHopRssi:-39, LastHopLqi:244 [callback-stub.c:2861] NodeId:0xab3b, LastHopRssi:-38, LastHopLqi:248 [callback-stub.c:2861] NodeId:0xab3b, LastHopRssi:-39, LastHopLqi:244 [callback-stub.c:2861] NodeId:0xab3b, LastHopRssi:-39, LastHopLqi:244 [callback-stub.c:2861] NodeId:0xab3b, LastHopRssi:-37, LastHopLqi:252 [callback-stub.c:2861] NodeId:0xab3b, LastHopRssi:-39, LastHopLqi:244 [callback-stub.c:2861] NodeId:0x17ea, LastHopRssi:-68, LastHopLqi:128 [callback-stub.c:2861] NodeId:0x17ea, LastHopRssi:-61, LastHopLqi:156 [callback-stub.c:2861] NodeId:0x17ea, LastHopRssi:-58, LastHopLqi:168 [callback-stub.c:2861] NodeId:0x17ea, LastHopRssi:-60, LastHopLqi:160.
The LAN’s instability causes frequent changes in its topology, leading to control failure. Search for lan_cluster_master_core. For example, node [%s] ip[%x] leave, where the content enclosed in [] is the node and IP address of the gateway. If this message appears in the log of the main gateway, it indicates the node leaves the LAN. When the gateway and the central control are in the same home, the central control serves as the main gateway for LAN linkage. However, if the central control is not using the latest firmware, it cannot deliver LAN messages to the gateway. Contact the central control manufacturer to update the central control.
Triggering scenes frequently within a short period of time results in throttling, causing only the last triggered scene to be executed. If a Zigbee sub-device is in the local scene, check the signal strength of the Zigbee network. A weak signal can cause Zigbee packets to be resent multiple times, resulting in a network storm. If there are multiple actions performed by Zigbee sub-devices in a scene, it is recommended to use the Zigbee standard scene.
Port Protocol Feature 6667 UDP Device discovery on LAN 6668 TCP Control over LAN 6608 UDP Multi-gateway RPC 6681 UDP Multi-gateway leader election 6682 TCP Multi-gateway key agreement 7000 UDP Multi-gateway node search 12121 UDP During the bidirectional communication between a Zigbee host and a Zigbee application, the Zigbee host listens on this port. 12122 UDP During the bidirectional communication between a Zigbee host and a Zigbee application, the Zigbee application listens on this port.
Problem description ASH_FLAG TUYA check, abnormal_data_num:0. ASH disconnected: EZSP_ASH_ERROR_XON_XOFF NCP status: EZSP_NO_ERROR Reason: The module is restarted. Troubleshoot: If the CRC checksum fails more than three times, the NCP will be restarted. When the accumulation of an error reaches a threshold, the system considers that some issues on the NCP occur and will restart the NCP. If you get EZSP_ASH_ERROR_XON_XOFF, it indicates there might be a problem with the flow control of the microcontroller.
tuya_error_code.h includes the definitions of the common error codes. Example: An error occurs when you report a DP that does not exist [09-06 15:29:02:425 TUYA D][smart_frame.c:3437] dp compose null, ret:-3585 #define OPRT_SVC_DP_ID_NOT_FOUND (-0x0e01) //-3585, DP ID not found.
Description: After the SDK is run, the following error keeps appearing in the log. [01-01 18:12:31 TUYA Warn][tuya_z3.c:19931] Zigbee COO ver is not get.[01-01 18:12:31 TUYA Warn][z3_wrapper.c:108] tuya_z3_getZigbeeVer, ret: -1 Reason: The serial communication between the gateway’s MCU and the Tuya Zigbee module failed. Troubleshoot: Check the pin connection between the gateway’s MCU and the Tuya Zigbee module. The RTS/CTS pin must be connected. Check the configuration of the UART parameterstty_deviceandtty_baudratein the code. Check the serial driver of the gateway’s MCU.
When you request the log on the Tuya IoT Development Platform, the SDK will invoke the log callback.
If a third-party sub-device goes offline, check the status of the heartbeat packets between the gateway and the sub-device. For more information, see Heartbeat Mechanism. A default heartbeat mechanism is applied between the gateway and Tuya-enabled sub-devices. Check the network signal and power status of the sub-device, as these issues can prevent the gateway from receiving a heartbeat packet.
tuya_error_code.h includes the definitions of the common error codes, where you can search for the error code. Check error code: #define OPRT_SVC_HTTP_API_TOKEN_EXPIRE (-0x110e) // -4366, token expired. Reason: The description of the error code indicates that the activation token has expired. Try activating the device again and check if the UUID has already been used for another device.
Description: The app has discovered the gateway but failed to pair with it. However, no error messages appear on the app but a blank page. Troubleshoot: Check if errorCode:PRODUCT_OTA_CHANNEL_CONFIG appears in the log. If so, review the Hardware Development on the Tuya IoT Development Platform and add the firmware, as shown below.
Sorting rooms on the app will not be updated accordingly on the SDK. This feature will be implemented in the future.
The maximum number of devices that can be stably connected depends on the processing capacity of the device, theoretically without limit. The result of a comprehensive test on the Tuya-enabled gateway indicates that up to 128 devices can be connected and run properly.
Yes, it does.To enable device control over LAN, a master must be selected from multiple gateways to handle message forwarding. Selecting a master requires an internet connection. Once the internet is connected, make sure to select a master, enabling LAN control even without an internet connection. If no internet is available after a restart, the cached master data will be used to select a master.
The Zigbee module is low power and does not require SRRC certification. The product's SRRC certification is done by you.
Currently, Tuya SoC light source solution does not support the button function, and the light strip solution supports the button and can configure the dimming function.
It means the number of dp created exceeds the limit, the number is recommended under 40. Warm reminder: There are dp prompts for products created on the platform, and it is recommended to operate according to the prompts.
It is recommended that the content you upload does not contain words such as tuya.
When you need to see the running log information of the module, you can lead the module log port and use the serial port tool to view the print log information. wiring TYWE3S general module class Pull out the GPIO2 and GND of the module, and connect the RX and GND of the USB to TTL module respectively. TYWE1S general module class Pull out the U0TX and GND of the module, and connect the RX and GND of the USB to TTL module respectively. Open serial debugging assistant Set the serial debugging assistant: Baud rate: 74880, data bit: 8, parity bit: none, stop bit: 1, data flow control: none Match the COM port, open the serial port: View logs Print ASCII characters, send the screenshot or save the log to the Tuya's engineer.
The trial version limits the number of new user registrations for WeChat Mini Programs to 10. The official version has no relevant restrictions.
At present, there are 3 options for the trigger mode of the SoC lamp in the network distribution platform: 1. Flashing after manualswitching; 2. Flashing immediately after power-on; 3. Some lighting products can enter the network configuration state by long pressing the button.
The Common Functions section shows the data points of the product, which include the dance to music function. The reason why the dance to music function is not displayed on the device control page is that you do not add the dance to music function. In this case, you need to add this function to the standard function list.
There is no such an interface. You need to restart the SDK process on the application layer.
It depends on the Wi-Fi chip functionality. Then, you implement the specific mode on the application layer.
The SDK does not provide such an interface. The app will send an URL to the robot vacuum for the speech package download.
The format must beXX.XX.XXand theXXmust be digits. The version number is used to determine if a firmware update is later than the installed version to make sure the earlier version will not be installed.
Possible reasons are as follows: The incorrect data format of the reported map. Issues with the endianness conversion. Issues with data compression.
Thetypefield of the map data should be set as0x01to differentiate the path types.
The value of the firmware version parameter (as indicated in the figure below) is not updated or is updated to the wrong version number.
You need to reset the robot vacuum and pair it again to make your modification take effect.
The scale specifies the number of decimal places of a value. The pitch specifies the difference between adjacent values. Assume that a value ranges from 0 to 9,999. If the scale is 0, the value is displayed as an integer with no decimal part. In this case, if the pitch is 1, the valid values will be 0, 1, 2, 3 … 9,999. If the pitch is 3, the valid values will be 0, 3, 6 … 9,999. If the scale is 1, the value is displayed with one decimal digit. In this case, if the pitch is 1, the valid values are 0, 1, 2, 3 … 9,999, which are displayed as 0.1, 0.2, 0.3 … 999.9.
There are 4 states in total: 0x00 device is not connected to the network 0x01 device is connected to the network 0x02 device network status is abnormal 0x03 device is in the state of distribution network https://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty#title-13-Report%20network%20status%20(0x02).
Memory: 4KB RAM: related to the DP data length of the device function, about 100B (OTA function needs to be greater than 260B) Function nesting level: 9 levels For reference: https://developer.tuya.com/en/docs/iot/overview-of-migrating-tuyas-mcu-sdk?id=K9hhi0xr5vll9.
A visual doorbell has a physical button that allows visitors to trigger calls to you. You will receive app notifications and can view photos taken by the doorbell camera in the app. If the visual doorbell is embedded with a motion detector, such as a PIR sensor, image recognition device, or radar detector, you can set a sensitivity level to enable the doorbell to take a photo when no motion is detected within a specified time. For example, the visual doorbell automatically takes a photo and sends it to your mobile phone when it detects no motion within 5s if you set the sensitivity to a high level or within 10s if you set the sensitivity to a low level.
Yes. To implement this function, you must configure the required DPs. Please refer to the documentation：https://developer.tuya.com/en/docs/iot-device-dev/IPC_custome_function?id=Kb0lbwks8ta2u#title-15-Lock%2Funlock.
Yes. The Tuya SDK can be used for door intercom systems. However, you must contact Tuya to evaluate your device performance.
This function applies to locks that support face recognition. After the captured picture is uploaded, the users can check the information of the door opener. The following DPs are involved: DP 45: Capture Countdown (optional) DP 46: Capture Countdown Response (optional) DP 47: Capture Again (optional) DP 56: Camera Mode (optional) DP 212: Active message push (required. Contact your project manager to add this DP.).
1、In panel SDK development, the language defined by local code has the lowest priority. 2、If the user uploads a custom multilingual json file for the first time in the 【 Create SDK Panel】 interface, and the custom multilingual Key is added, then the panel's multilinguality will be shown according to the json file uploaded by the user. If the user modifies the corresponding multilingual script in the platform's 【Product Config】—【Multilingual Management】 later, the custom multilingual json file uploaded again will not be displayed in the panel, because of its low priority, it can't cover the scripts changed in 【Product Config】—【Multilingual Management】. Therefore, if the user needs to modify the script content, he can go directly to【Product Config】—【Multilingual Management】 to modify. 3、Uploading added custom multilingual Key is not affected and is displayed normally. 4、At present, the【Product Configuration】—【Multilingual Management】 of the IoT platform has the highest priority. 5、Another point to note: please do not define multilingual languages in local code other than Chinese and English. Other languages involve many regions, and the local code can't be fully compatible. Please set the multilingual configuration of the Tuya IoT Platform on the Product Multilingual page Device Panel. Specifically, you can understand here: https://developer.tuya.com/en/docs/iot/internationalization?id=Ka3lvm6hll3wr.
Hello, if the issued power 0 is normal, and the issued power 1 reports an error, it is possible that your infrared air conditioner is from the same source of power on and off. For example: power 0 is on, then issuing power 0 again is off. You can call this API to check whether the duplicate_power on button and off button are the same. The supported key information of the remote control: https://developer.tuya.com/en/docs/cloud/ff7882b8a5?id=Kb3oe37sqdjx5.
No, you don't need to make multiple language versions, just set it up. Refer to this for processing: https://developer.tuya.com/en/docs/iot/internationalization?id=Ka3lvm6hll3wr.
The reasons are as follows: 1, When the user created the P12 file, the password set and the password entered in the iot platform were indeed inconsistent, please check whether the set password and the entered password are the same 2, The customer is not using a Mac computer, but other computer systems, created using command line terminal,please refer to the document: https://developer.tuya.com/en/docs/iot/ios-push?id=K989rskj262hu#title-7-%E5%88%9B%E5%BB%BA%E8%AF%81%E4%B9%A6%E8%AF%B7%E6%B1%82%20CSR%20%E6%96%87%E4%BB%B6 Note: # openssl version should be 1.x series, 3.x not compatible openssl req -in example.csr -out CertificateSigningRequest.certSigningRequest Most of them are because the 3.x openssl is used incorrectly to create the CSR file, resulting in a p12 import password error.
Visit https://developer.tuya.com/en/docs/iot/data-statistics-related-interface?id=K9m1dlf41ex5f for the APIs related to statistical data.
The panel SDK is based on the React Native development environment. For more information about how to build the environment, visit: https://developer.tuya.com/en/docs/iot/environment-build?id=K9m1ge64e9hr4 .The official website for building the React Native environment is https://reactnative.dev/.
The charging pile involves complex interactions, and there are more raw DPs in the standard DP. Developers need to parse them according to the specified method in the DP interpretation. In order to implement functions such as charging records, Tuya Cloud has also established special reporting methods. Firmware development recommendations: "Auto-restart" mechanism: Charging piles are always-online devices, and the impact of bugs in the program can be significant. It is impossible to find all bugs in limited testing time. It is generally recommended for such device module programs to have an "auto-restart" mechanism. For example, starting at 4 am every day, if the device is not in use, perform a module restart. This will greatly avoid many difficult problems. (4G) Record IoT card and hardware IMEI: Domestic operators require IoT cards to be bound to IMEI for anti-gray market policies. Bound cards cannot be used on devices with other IMEIs (contact the operator to provide the card number ICCID for unbinding). Use Tuya Module Debugging Assistant: Module debugging assistant documentation is available to assist with Module Debugging Assistant.
The default PWM frequency is 1 kHz. In the third step of product development, which is hardware development, the frequency can be modified and can be increased up to a maximum of 20Khz.
Set tabStyle: { display: none }.
Set Notification enableClose to false, and set the autoCloseTime attribute.
Currently, none of our modules use code related to the GPL open source license.
Custom function points are created by the customer, and the backend does not have a configuredContinuous Trigger; solution - contact Tuya technicians to configure the Continuous Trigger.
For data that is reported repeatedly, if no duplicate reporting is enabled, the platform will filter out duplicate data in order to save server resources. For certain special function points/statistical function points such as: work hour statistics, power statistics, etc., if the product's standard function points do not support duplicate reporting, record-type DP reporting can be used instead.
The module enters low power mode because the working mode is configured as "Timeout Network Configuration" or "Misoperation Prevention Network Configuration" when MCU replies to product information. If the device is not configured within 3 minutes in timeout network configuration, it will enter a low power state. If the device has not been networked before (removed by APP or new device), it will enter a low power state if it hasn't been configured within 3 minutes in a misoperation prevention network configuration. After entering the low power mode, sending a reset command will put the module in the Smartconfig mode or AP network configuration mode.
When the Wifi module receives data from the Beacon remote control, it will inform the MCU through the 0x35 command, subcommand 06. The MCU only needs to parse according to the serial port protocol.https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb#subtitle-87-Bluetooth/Beacon%20Remote%20Control%20Function%E2%80%94Data%20Notification.
First, you need to start the Bluetooth remote control service, thenafter the module is powered on and completes the 02 command word interaction, it can enter the pairing state, the pairing time is 30 seconds. At this point, let the Beacon remote control also be in the pairing state.
The switchable one, the directive mode is determined by the latest confirmed selected mode.
The network status reported by the module indicates the status of the module in the Zigbee network. As long as the module has joined the Zigbee network, it will not be affected by the gateway's power outage or internet outage, unless the device is removed from the gateway or the device is locally reset.
You need to check what yourminSdkVersion is, you need toincrease the minSdkVersion to 24 or above.
Apart from the products developed with module firmware key:keyjqsnc and keyf7k87, all other products of the MCU SDK solution are private transparent channel communications and cannot be controlled by Zigbee Standard 3.0 remote control.
This command is not supported at the moment.
No, it does not support grouping gateway lights and colorful light strips, but you can add a sigmesh scheme's colorful light strips through the gateway function of dynamic gateway lights in the "Smart" tab of the APP.
Wi-Fi module is not available, outdoor module requires TAC code.
The product remains online when working normally under the gateway. When the data request interval is 250ms, the standby average current is less than 500uA in 3 situations: connected to the network/device disconnected from the gateway/gateway disconnected from the external network. The average current is less than 10mA during network configuration & OTA.
The module wakes up the MCU pin PB4; the MCU wakes up the module pin PB5/PD2.
After successful network distribution, the device side resets and removes: 1、At the last power-up of the device, the device first restores to the default brightness and color temperature constant light, and then after the software is rebooted and flashes rapidly, the light enters the rapid flash time in 6-7s (from the last power-up to the time of flashing); 2.1、The device performs network distribution. After the network distribution action lasts for 10s, it is powered off and then powered on, automatically connected to the last router, and displayed at a constant light with the default brightness and color temperature; 2.2、The device performs network distribution, after the network distribution action lasts for 3 minutes, it automatically connects to the last route, and displays at a constant light with the default brightness and color temperature.
No. The range of OTA push only has two options, to select a portion of devices to receive upgrade or to select all devices to receive upgrade.
1、The sub-device is in the network configuration; 2、This sub-device includes DP: DP point of the remote control switch.
It is necessary to check whether the module has been successfully set up. If there is no response, it means it is not supported; Some firmware doesn't support this instruction, like the firmware key:keyukhs5.
Partial firmware support; You can send commands to modify the broadcast name while it's in the unbound state, and check if the module returns success. If the module does not respond, it does not support it. For example, the firmware key:keyukhs5 9.3 does not support modification.
iOS devices require you to first install the TestFlight application, then you can just open the link below on your phone https://testflight.apple.com/join/VdPzsEpR.
The order has been cancelled, no need to pay attention.
After supporting dynamic gateway lights and Sigmesh device groupings, you can disconnect Wi-Fi and 4G networks and implement local group control via Bluetooth.
In the condition of having other gateway lamps, the sub-devices can be controlled. When other gateway lamps exist, if the main gateway lamp is disconnected from power or the Wi-Fi network is disconnected, it will trigger the dynamic election mechanism of the main gateway lamp. After a new main gateway is elected, all other sub-devices under the original main gateway will automatically migrate to the new main gateway lamp. The automatic election time is generally around 40s, depending on the actual network environment.
The networking mode of the dynamic gateway lamp is the same as that of the ordinary dual-mode device, which can be carried out through three methods: Bluetooth networking, EZ networking, and AP networking.
Dynamic gateway light can be used as a Bluetooth gateway to add Sigmesh devices, but it does not currently support the addition of BLE and beacon devices.
Beacon lighting products currently have two chips: AK801: Light source: 1~5 paths Beacon; 1~5 paths Beacon mesh; Light strip: 3 paths Beacon, support infrared remote control + local music; 3 paths Beacon mesh, support Beacon remote control + local music + button; PHY6252: Light source: 1~5 paths; Light strip: 1~5 paths, support infrared remote control + local music + button Some products are in white-list release status, if needed, you can contact the business manager/project manager who is interfacing your company.
The current common panel of the phantom strip light:Strip-Classic D003/Strip-Classic L003, is displayed according to the choice of function points, including the length of the strip and the setting of dots, which is closely related to the following three function points. DP ID Function point name Identifier Data transfer type Data type Function point attribute Remarks 46 Strip length light_length Report only (ro) Numeric (Value) Value range: 1-10000, Interval: 1, Multiple: 0, Unit: cm Total length of the phantom light strip displayed on the UI panel 47 Strip dot number light_pixel Report only (ro) Numeric (Value) Value range: 1-1024, Interval: 1, Multiple: 0, Unit: Total number of phantom strip light drive chips 53 Number/length setting lightpixel_number_set Can be issued and reported (rw) Numeric (Value) Value range: 1-1000, Interval: 1, Multiple: 0, Unit: After the phantom light strip is trimmed, the length is reset [Number/Length Setting] is an optional function. If the phantom light strip has been cut after installation, the panel can be set to a second length setting through this DP point to adjust the display length of the phantom light strip. If you select this DP point, the strip-length setting section will appear on the panel, and users can correct and adjust the length of the strip light on the APP to adjust the light display range; If this DP point is not selected, the strip length setting content will not be displayed on the panel, and users cannot make a secondary setting; [Light Strip Dot Number] is a mandatory function, which represents the total number of chips/total points driven by the device. This DP only reports, and the panel can get the total point number of the device through this DP point; [Light Strip Length] is an optional function, which represents the total length of the device. This DP only reports, and the panel can get the total length of the device through this DP point. If you select this DP point, the panel will show the strip lengt.
There are 7 states in total: 00: smartconfig configuration state; 01: AP configuration state; 02: Wi-Fi is configured but not connected to the router; 03: Wi-Fi is configured and connected to the router; 04: Connected to the router and the cloud; 05: Wi-Fi device is in low power mode; 06: EZ mode and AP mode coexist. (For Wi-Fi and Bluetooth LE combo module: Bluetooth is also in pairing mode.).
Problem phenomenon Solution Come to the hardware development of the product development step, click the corresponding edit firmware (if there is no edit firmware here, it means that the owner of the firmware is not yourself, please find the corresponding firmware manufacturer to operate), and then turn on the button of whether to use Tuya production plan .
There are two reasons for this problem: 1. Really entered the wrong password (small probability) 2. When creating the P12 file, if no mac computer is used to create the OpenSSL certificate, the 1.x version needs to be selected. Some users use the 3.x version (the probability is high).
Please confirm whether you have selected "AutoFill Credential Provider" permissions when creating the App ID, as shown in the picture:.
1.Enter: My Space - Authorization, click "Add Authorization", enter the authorized person's IoT account. 2. Click on permission settings, grant him the development permission for the corresponding PID.
You need a Telink writer to flash ZTLC5. 1. Make sure the serial ports of the module are correctly connected to those of the Telink writer: module Tx to Telink Rx, module Rx to Telink Tx, and module SWS to Telink SWM. 2. Please purchase the Terminus Micro Burner EVK on Taobao. 3. Log in to the Cloud Module Burning Authorization Platform and choose TUYA PRODUCTION TOOKIT TYMZ Test Bau. On the page that appears, set the authorized baud rate to 115200. 4. If the wires are too long, the Telink writer and the serial ports of the module must be grounded at the same point.
Because the module currently has a watchdog function, if the module crashes, it will automatically restart. So RESET is generally recommended to be left floating, not connected to anything.
Test functions of the module or check the module logs. Function testing is recommended because it is simpler. Relevant knowledge：How to do incoming inspection for modules purchased from Tuya?
import { TYSdk } from 'tuya-panel-kit'; const { appRnVersion } = TYSdk.mobile.mobileInfo; Points to note: 1. Unless specifically requested, the default version number is 5.1. 2. The larger the RN version number, the higher the requirements for the available App versions on the panel. Please choose according to the usage of the App on the panel. 3. If the RN version number that you entered exceeds the following list, it may cause the panel to be unusable on the app! App version Rn version 3.28.5 5.42 3.28.0 5.41 3.27.5 5.40 3.27.0 5.39 3.26.5 5.38 3.26.0 5.37 3.25.0 5.36 3.24.5 5.35 3.24.0 5.34 3.23.5 5.34 3.23.0 5.33 3.22.5 5.32 3.22.0 5.31 3.21.0 5.30 3.20.0 5.29 3.19.0 5.28 3.18.0 5.27 3.17.6 5.26 3.17.0 5.24 3.16.5 5.23 3.16.0 5.23 3.15.0 5.22 3.14.0 5.21 3.13.5 5.20 3.13.3 5.19 3.13.0 5.18 3.12.6 5.17 3.12.0 5.16 3.11.7 5.15 3.11.0 5.14 3.10.0 5.13 3.9.0 5.12 3.8.0 5.11 3.7.2 5.10 3.7.0 5.9.
Yes, it is possible. For more details, please refer to:https://developer.tuya.com/en/docs/iot/make?id=Kc0nf6nzlvrx0.
"charger_free_fault" refers to a fault occurring during idle time (when the charging cable is not connected to the vehicle). "charger_fault" refers to a fault occurring during charging.
"Associate," "adopter," "participant," and "promoter" are membership levels in CSA. Related Links：https://csa-iot.org/become-member/.
Please go to "Scene Linkage " under "Product Configuration" in Tuya IoT Product Development Process and check if you have set the "Configure Trigger Conditions" and "Configure Tasks" The device functionality must exist in both the "Configure Trigger Conditions" and "Configure Tasks" sections. If you are unable to select the desired device functionality on the Tuya IoT platform, please contact your project manager for configuration assistance.
The forward active power must be reported as a cumulative total, not as an increment. From the activation of the device, the reported value must be increasing. If the reported value is smaller than yesterday's value, the backend system will filter it out, resulting in a reported value for today but the actual power remaining 0. Therefore, if you want to start reporting from 0 again for this data point, you need to first clear the data and then report it.
For Bluetooth remote controllers, Wi-Fi remote controllers, and Zigbee remote controllers, no additional circuit is required. However, for a 433 remote controller, a corresponding hardware circuit is needed.
After pairing the light with the remote control, the light will flash to indicate successful pairing.
Yes, TuyaLink development method can be used.
Each panel SDK is a collection of utilities provided by the panel container to assist you in the development of control panels.You can develop multiple styles and functions in the panel container based on the panel SDK to meet different business requirements. This allows you to manage smart devices, scheduled tasks, and scenes. You can quickly develop various panels based on the Tuya Panel SDK in just 6 steps.
The following compilers are recommended for panel SDK development. Download and install a compiler based on your actual needs. Visual Studio Code: recommended. Common functions, such as formatting and code redirection are provided. The community contribution and activity of Visual Studio Code are high. WebStorm: highly integrated IDE. Sublime Text: compact and lightweight. Atom: compact and lightweight.
Before using the panel SDK, run the following command to install the `yarn add @tuya/tuya-panel-api` dependency. For more information, visit:https://github.com/tuya/tuya-panel-sdk/tree/main/packages/tuya-panel-api.
When you call page components provided by the Tuya IoT Platform shown in the following figure, such as preset point page components, lullaby list, and offline help capability components, you need to package the local code and upload it to the SDK panel in the Tuya IoT Platform for testing. Local testing is not supported.
The size of MCU OTA firmware is mainly limited by the gateway's capability. The wireless small gateway has a relatively small data cache area, theoretically around 512k, but the cache area is also used to store local scenes and other sub-device information, so the specific size is uncertain. Generally, the wireless small gateway is around 200k, and if it is a wired gateway, around 500k is no problem.
Default is high level, and low level is the effective level. The module itself needs to configure three GPIOs for network status indication, network configuration button, and BLE status (optional). The network status indicator light needs to be designed to light up at low level, and pulling down or leaving the network configuration button pin floating will cause the module to reset.
Yes, they can. To do so, they can follow these steps: Go to the IoT Platform. Navigate to Value-Added Services (VAS) in the menu. Select "All Services." Click on "Marketing." Choose "Manufacturing Support." By accessing these services and enabling the Value-Added Services, the factory will be able to create burning work orders on their own.
Check if the router SSID is entered correctly; test1 SSID: tuya_mdev_test1 test2 SSID: tuya_mdev_test2 If the device's network distribution has not exceeded 15 minutes, remove the network distribution, wait for 10 seconds, power on again, and scan the production test signal to enter the production test. If the device's network distribution has exceeded 15 minutes, you need to re-burn the authorization. If the beacon signal is weak, you can move the beacon closer to the device (the ideal distance is 3 meters ~ 5 meters).
No need to connect to the internet, and the correct SSID must be set at the same time.
The device router name for the production test using the upper computer is not fixed and needs to be consistent with the upper computer hotspot name; The device router name for the beacon production test is fixed; for single production test products, it is set to: tuya_mdev_test1. For double production test products, the first production test is set to: tuya_mdev_test1; the second production test is set to: tuya_mdev_test2. (Special firmware will write the hotspot name and need to check the code to confirm).
It is better to be within 1 meters of the test frame or the product to be tested.
Please refer to the document:https://developer.tuya.com/cn/docs/iot/production-test-of-zigbee-lighting-products?id=Kc2q93gd5cf2w.
Yes, you can place multiple beacons.
99% of the reasons for the failure of the power statistics socket production test are calibration issues. For troubleshooting details, please refer to:https://developer.tuya.com/en/docs/iot/faq-prod?id=Kc9s5afvg9f12.
It indicates calibration failure; for troubleshooting details, please refer to:https://developer.tuya.com/en/docs/iot/faq-prod?id=Kc9s5afvg9f12.
For Zigbee production testing, it is recommended that the distance between the gateway and the production test device be within 5 meters. The RSSI range for Zigbee production testing should be set between -45dB and -10dB.
pls refer to the document:https://developer.tuya.com/en/docs/iot/Zigbee-socket?id=Kc2q6lp8781f9.
Both Beacon mesh and Ble mesh networking methods use dual links, i.e., gateway + App.
It is recommended to prioritize BLE or Zigbee protocols, with standby power consumption at the microampere level. Please note that BLE cannot achieve group control, and Zigbee needs to be used with a gateway.
Yes. The second-generation Bluetooth beacon can adjust the signal transmission strength gear through the upper computer in M2 and M3 modes.
Generally, when there is no cellular or Wi-Fi signal, the module will switch from cellular or Wi-Fi to Bluetooth channel within a maximum of 3 minutes. In the actual test of CAT.1 module charging pile category, it takes as fast as 45 seconds to switch from cellular to Bluetooth; while for Wi-Fi to Bluetooth channel, it takes at least 1 minute in the test of circuit breaker category.
Currently, in the IoT platform - Professional Lighting - Classroom Light category, there are two public lighting solutions, Sigmesh and Zigbee, that support constant illuminance capability. The hardware connection between the module and the light sensor is as follows: the UART port of the module is required, and the RX pin of the module is connected to the TX of the light sensor's serial port.
Yes. Wi-Fi_BLE dual-mode light sources and ceiling lamps support beacon remote control without networking in the non-development solution. Please note to use the latest firmware version.
The certification price for the five-way bulb is as follows (Note: The prices for 2-way and 3-way bulbs are currently the same as 5-way bulbs).
Please click on the robot directly on the failure page, and there will be a corresponding solution.
Induction lamp categories support group induction synchronization. When there is induction in each induction lamp in the group, the real-time induction signal (PIR presence) is synchronized to the induction lamps in the group, and all the lamps in the group light up. After the device's delay, it becomes dim or turns off. PS: By default, products with this DP will enable the "Group Induction Synchronization" function after joining a group. In the group interface, turn off the group synchronization function switch or disband the group, and the group induction synchronization function will be closed. All devices in the group must have this DP. Interface display: single device hides the button, and the group displays the "Group Induction Synchronization" button. If the previous lamp was manually turned off, it will switch to the induction mode and turn on the light. When the group is disbanded, the device returns to its previous state.
The ordinary Zigbee universal docking firmware does not support wireless rotary dimmer switches because dimmer switches/remote controls send Zigbee standard commands, which are not supported by the universal docking firmware. If there is a need for MCU universal docking to support dimmer switches/remote controls, please contact your FAE/Project Manager.
If you need to enable Tmall Genie service, you can click to enable it. Note: If you do not find the related icon in the App after enabling, it is because the App will display in a certain logic cycle. Tuya platform currently supports the access of multiple voice solutions.
The public version solution currently supports the standard NEC protocol, and some light strip public version solutions support the preset 24-key infrared remote control. The code values and panel are as follows: Note: For user codes and key codes, please refer to the remarks of the platform hardware configuration and fill in decimal or hexadecimal values.
There is currently a smart lighting solution compatible with thyristor dimmers, which includes both embedded firmware and hardware reference circuits.
No. For developing Sigmesh lighting products using the general MCU docking method, it is recommended to use the TLSR8250 chip platform, corresponding to the BT series modules, such as BT3L, etc.
Please check the power supply stability of the Tuya smart module in the device hardware circuit, especially whether there is a power drop phenomenon at the VCC port of the smart module when the light automatically lights up abnormally.
The infrared remote control supporting the lighting scheme needs to meet one condition: the standard NEC code (most infrared remote controls on the market can meet this requirement). The configuration steps for the infrared remote control scheme are as follows: Step 1: The customer selects an infrared remote control and needs to ensure that the remote control has a standard NEC code. At this time, the number of buttons on the customer's remote control can be confirmed, such as 6 buttons. Step 2: The customer provides the user code of the infrared remote control. The user code can be obtained from the remote control supplier or measured by an infrared remote control coding analyzer. The user code of the standard NEC-coded infrared remote control consists of 2 bytes, usually represented by a hexadecimal number, such as: 00FF. Step 3: The customer provides the key code for each button on the infrared remote control. Like the user code, the key code can also be obtained from the remote control supplier or measured by an infrared remote control coding analyzer. The key code of the standard NEC-coded infrared remote control consists of 1 byte, usually represented by a hexadecimal number, such as the key code for button 1 is 12, button 2 is 1E, button 3 is 04, button 4 is 05, button 5 is 1F, and button 6 is 0A. Step 4: The customer selects the function of each button. The function of each button on the remote control must be selected from the "Tuya Universal Strip Light Infrared Remote Control Standard Button Function Table (see the table below)", which provides 116 common button functions, covering most customer needs. For example, the function of button 1 is selected as "Master Switch", button 2 is "Five-level Color Temperature Switching", button 3 is "Increase Brightness", button 4 is "Decrease Brightness", button 5 is "Countdown 1min", and button 6 is "Warm and Cold Gradual Change". Step 5: Enter the four confirmed pieces of information: the number of buttons, user cod.
In this case, please provide the PID to the docking project manager. After they enable the statistics function for the corresponding DP points under the PID in the background, this prompt will no longer appear, and the panel can display the statistical chart.
The DP data supports up to 220 bytes.
If it is a light that is always on after power-on, it can be directly paired with the remote control for control. If the light flashes after power-on, it needs to be paired with the mobile App before it can be paired for control.
Yes, the SMB solution's distributed intelligence supports Bluetooth local smart linkage.
There are currently two methods: 1) SN query; 2) Test stand query; specific operation steps: https://developer.tuya.com/en/docs/iot/LLJY?id=Kc4bzotbvvt45.
"Currently, there are two methods for transmitting pictures in photo locks, one is UART, and the other is SPI. Different transmission modes can be selected through different instructions. XR1/XR3 module SPI transmission mode IO port and SPI port correspondence: IO port SPI port PA19 SPI_MOSI PA20 SPI_MISO PA21 SPI_CLK PA22 SPI1_CS0 For specific configuration protocols, please refer to: Reference link: https://developer.tuya.com/en/docs/iot/smart-product-solution/product-solution-lock/product-solution-lock-wifi/door-lock-mcu-docking?id=K950t0p1l51k2#title-29-%E6%8B%93%E5%B1%95%E5%8A%9F%E8%83%BD%E5%8D%8F%E8%AE%AE%E8%AF%A6%E8%BF%B0".
"For sandwich development boards with firmware-free, there will be a label with an SN code on the back, which is used to bind the IOT platform to apply for an authorization code. For sandwich development boards with Mcu docking firmware, the firmware has been burned at the factory, so there is no need to bind the IOT platform to re-burn, and therefore there is no such label.".
This is because the TeLink burning tool is missing. You need to purchase Telink first, and then connect the SWM of Telink to the SW pin of the module.
Strong electric devices have relay bridging function, while weak electric devices do not. Single-fire switches also do not have relay bridging function due to power consumption issues.
You need to check the product settings. If there are products with the DP point of the momentary switch, they are supported. After selecting this DP point, you can set the actual delay time on the APP.
It is recommended to choose an ECM microphone with a signal-to-noise ratio of 70dB or a silicon microphone with a signal-to-noise ratio of 65dB.
TYSdk.device.putDeviceData({ switch: true }).
"TYNative.gotoDpAlarm() jumps into the native native page, which is a react native modal problem, and most of the time it is handled with a delay. Add a timer, refer to this. timer = setTimeout (gotoHouseManager();1000);".
When the mobile phone system language is switched to English, the weather data will automatically be converted to English.
Use the command line npm uninstall -g tuya-panel-kit-clinpm install -g tuya-panel-kit-cli and then use tuya-panel-kit-cli package ./.
Change to npm install yarn -g or refer to the yarn official website documentation for installation: https://yarn.bootcss.com/docs/install/#windows-stable.
If the Bluetooth communication method has output, it is normal. If you don't need output, just comment out the success.map(() =&rt; responseUpdateDp(payload)) code in common.js.
The {name}-sources.tar.gz package is a source code package, which has no other use and does not need to be operated.
Other component libraries can be used without restrictions.
Basic functions include: switch, brightness, color, and color temperature.
Yes, the OEM App must be upgraded to v4.8.0 and above.
No, the firmware configuration items are burned into the module, and they need to be re-burned to take effect after changing.
Yes, the SWS of ZT modules needs to be connected to the SWM of the programmer during burning.
After adding 41DP, the remote control function is enabled by default, so the power consumption will be 70+ during normal use. It must be used with a panel with a remote control switch button.
Because RN debugging app is mainly used to debug the development panel function, the component compatibility is not perfect, it is recommended to package and release the next panel, and test whether it is normal in the public app.
This situation is generally caused by the failure of the sel pin switching of the power statistics chip. Under normal working conditions, use an oscilloscope to measure the sel pin voltage to see if there is a 1:10 high and low level switch. If there is no high and low level conversion, please check Whether the circuit between the IO of tuya module and the sel pin of the power statistics chip is a path.
It depends on the specific product form, wireless communication rate, and other external environments. Generally, it is recommended that the indoor distance should be =15 meters, and the outdoor distance should be 120 meters. You can judge it yourself, and the suggestion is to conduct a conduction test and observe the indicators. The distance is only used as a reference for judgment. You can refer to https://developer.tuya.com/en/docs/iot/wifi-test?id=K9hr623embyah.
TUYA's NB module supports three carriers, and TUYA's commercial platform is Telecom, so it is recommended that the SIM card be preferred to Telecom, followed by Mobile. TUYA-NB module connects to China Telecom lwM2M cloud and China Mobile OneNet cloud. China Unicom card when taking the China Telecom lwM2M cloud. Use the lwM2M way to connect directly to the TUYA cloud, access to the domain name: nbiot.tuyacn.com. You can find your own operator to buy NB IoT card, when buying please make sure whether the APN supports PSM or DRX card, you can also buy it in Toodle, please contact the project manager for tariff package.
The page needs to be viewed and debugged on the mobile phone using the Tuya Panel RN APP, and browser viewing and debugging are not supported. After you modify the code of the page, the mobile phone will synchronize the modified page information, and you can directly view the effect on the mobile phone. You can learn more here: https://developer.tuya.com/en/docs/iot/development?id=Kadht64g88du2.
Due to the limited number of the module's IO, the No-Code Development support a maximum of 6-way Advanced Scene Switch. It is suggested to adopt MCU SDK development mode for 8-way Advanced Scene Switch.
The number of switch Data Points as many as the number of switches connected to relays The number of scene Data Points as many as the number of keys that can be used as scene switch The number of mode Data Points as many as the number of switches that can be change to scene switch For example,3 switches and 3 scenes,6-way Advanced Scene Switch,you should select 3 switches Data Points,6 scene Data Points, and 3 mode Data Points For example,6 switches and 2 scenes,8-way Advanced Scene Switch,you should select 6 switches Data Points,8 scene Data Points, and 6 mode Data Points.
Yes, you can created the solution through the "Electrical--scene switch --Custom Solution".
The CBLC5-NA module does not come with an antenna, while the CBLC5 module comes with an antenna.
Products based on Tuya Matter solution can obtain certification through the following four schemes. Scheme 1: Certificate transfer.If the product to be certified uses the same category, chip model and function with Tuya certified product, it can be transferred directly. Scheme 2: Certification by Similarity + Transfer. If the products to be certified use similar categories, consistent functions and chip models with Tuya certified products, Tuya can transfer the products after similarity certification. Scheme 3: Certification by Full Testing+Transfer. If the product to be certified that Tuya does not get the master certificate, use Tuya's CSA Alliance account to apply for laboratory testing, and then transfer the certificate to you. Scheme 4: Certification by Full Testing. If the product to be certified that Tuya does not get the master certificate, use your CSA Alliance account to apply for laboratory testing and get master certification.
The specific price depends on your CSA Alliance membership level and certification solution, please consult the Tuya Business Manager you are in contact with.
All Tuya Matter solution products can apply for Matter certification through Tuya.
Yes, it can be customized for free. On the left navigation bar of the IoT platform, click in order: Purchase/Manufacturing/Information/Go to Develop/Edit/Customize SN/Yes/Go to Configure SN Resources/Create Resource Pool.
1.If the device has not completed Matter certification, consumers may not be able to network the device. 2.If the device has not completed Matter certification, the product packaging is not allowed to print Matter logo. 3.Matter certification can better ensure the security and reliability of Matter products.
Samples need to be sent for testing, with 2 samples sent for each certified product. If you need to apply for a new certification for your device, it needs to be submitted for testing to a third-party testing organization, which usually takes about 4-5 weeks. If your device does not require a new certification, it only needs to be tested by Tuya, which usually takes about 1-2 weeks.
The timeline for certification depends on the appropriate certification solution for you. If your product does not require laboratory testing, it usually takes about one month to complete. If your product needs to be sent to the laboratory for testing, it usually takes about two months to complete.
If a device is online, that is, the external network connection of the module is successful after the Wi-Fi network is reset, a notification is displayed in the app and the device is removed. If the device is offline after the Wi-Fi network is reset, no notification is displayed in the app and the device is displayed as offline on the app. After the device is paired with the network and activated again, the device status in the app is updated. If the device side sets the anti-misoperation mode, when resetting, the APP page will also show offline; until re-networking, the original device will be removed; within the specified time, if no re-networking, the device will reappear online.
You can refer to:https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
The product linkage analysis is the linkage of the PID belonging to your account. You are unable to see the product data of other customers' products.
No. Beacon mesh is a new protocol and is not compatible with Beacon 1.0. Therefore, Tuya does not support the group control of Beacon mesh and Beacon 1.0 devices.
A developer can develop additional functions for a mini App based on an existing App. The IoT WeChat mini program SDK does not provide the functions provided by the App SDK.
Wi-Fi and Bluetooth LE: 30s Bluetooth mesh: 30s Zigbee: 60s.
Bluetooth-based control takes priority. The gateway-based control applies if the light is not in the area where Bluetooth can control devices. The two control modes do not interfere with each other.
No. Static galaxy link light devices can be controlled together with Wi-Fi devices in a group.
No. You can only add a Bluetooth mesh sub-device to a galaxy link light.
The products with the advanced functions enabled can be used directly.
If the advanced functions are not enabled for a lighting product, the basic biorhythm function without latitude and longitude recognition can be used. Color temperature cannot be displayed, and only a few basic scenes are available.
Generally, a module supports no more than 40 DPs. If you configure more than 40 DPs, the module cannot be paired. If a module with more than 40 DPs cannot be paired, you can create a product with less than 40 DPs, and report the corresponding PID to the MCU. If the product can be paired, it indicates that the pairing error is caused by the exceeding of DPs. If you need to configure more than 40 DPs, contact Tuya personnel for firmware customization.
Currently, the weather data cannot be obtained by devices developed based on the Zigbee low-code solution.
Generally, this is because the receive buffer of serial ports has insufficient space. Increase the receive buffer storage capacity and try again.
No. Currently, modification of Wi-Fi RF performance parameters is not supported in low-code development.
This is because the version of the module firmware on the development board is old and does not support short URLs. Please flash the latest firmware or buy a module with the latest firmware version.
This is generally because the number of DPs exceeds the upper limit of 40. You can delete some DPs of the module as needed.
Yes. Traffic consumption is required for communication with the cloud.
Currently, the hotspot name modification is not supported by the general integration solution.
Yes. For more information, see https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb#title-13-%E7%8A%B6%E6%80%81%E4%B8%8A%E6%8A%A5%EF%BC%88%E5%BC%82%E6%AD%A5%EF%BC%89.
Check the GPS antenna. If the GPS antenna of your development board is folded, you must unfold it and test it outdoors in an open field.
This is because the module uses low-power firmware, which does not send heartbeat packets.
You can refer to the topic of the product field configuration query in the following document https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb#title-6-%E6%9F%A5%E8%AF%A2%E4%BA%A7%E5%93%81%E4%BF%A1%E6%81%AF.
Turn on the mobile hotspot on your mobile phone and pair it with the module. Then, turn off the mobile hotspot. The module switches to Bluetooth control mode within 3 minutes.
This is because the MCU has reported invalid DPs or DPs that are not selected on the platform. Solutions: 1. Remove invalid DPs from the MCU. 2. Upgrade the module to the latest version.
When the MCU replies to the 01 command with 1 in the Low field, the low power consumption mode is enabled. For more information, see https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb.
The metering chip measures the active power, which is calculated this way: Active power = Voltage × Current × Power factor (PF). The result equals the displayed power only when PF is 1. For example, the actual load is purely resistive. However, many household appliances are not purely resistive, and the PF may not equal 1. The inequality is not caused by a measurement error. The power consumption calculation of widely used electricity meters also uses the active power.
Cloud scene: A cloud scene can be executed across protocols, such as Wi-Fi, Zigbee, and Bluetooth Low Energy (Bluetooth LE). The scene linkage rules are stored on the cloud. When the rules are hit, the cloud executes the actions accordingly. Local scene: The scene linkage rules are stored on the gateway, and the devices executing the scene must be connected to the same gateway. When the rules are hit, the gateway executes the actions accordingly. Zigbee standard scene: The scene linkage rules are stored on the cloud, scene switch, and devices, and the devices executing the scene must be connected to the same gateway. When the scene switch is triggered, it sends the command directly to the devices, which then execute the action without the control of the gateway.
When you press a physical key to trigger a scene, MCU does not report the values of the scene DPs, nor the value of the DP17 "Scene ID Group ID", but a "scene wake-up command". After the module receives the command, it performs two actions: 1. Sends a scene wake-up command to the group. Devices in the group will execute the scene after receiving the command. 2. Sends the "key value" to the gateway. The gateway will perform the cloud linkage based on the key value. For more information about the serial protocols for the scene wake-up command, seehttps://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty#title-26-%E5%9C%BA%E6%99%AF%E5%94%A4%E9%86%92%E5%91%BD%E4%BB%A4.
Recently, FCC has raised stricter requirements on the antenna materials required for applying for an FCC ID for a wireless product. An antenna report needs to be provided to prove the accuracy of the gain information. FCC has forcibly required Part 15 certificate applicants to provide the antenna report or antenna specifications since September 2022. For the certificates that have been issued, TCB will notify the labs to supplement the required materials when a certificate enters the audit state. Currently, we are not sure whether a spot check or general check will be performed on issued certificates. You can notify customers to prepare the required antenna materials in advance so that they can promptly provide the materials after receiving a notification from TCB. If any entity fails to provide the required antenna materials after receiving a notification from TCB, its certificate may be revoked in the worst circumstances. The antenna gain information is provided in the specifications of most modules. For the antenna report, you can search for the corresponding module materials by using the PID on the Tuya IoT Platform. The antenna report is contained in the module materials. For more information, visit https://developer.tuya.com/en/docs/iot/certification-guide?id=K9wjjdtq8v954.
No, this function is not supported currently. You can request custom development if needed.
Complete App functions After you bind skills to your OEM App, your OEM App can use the skill account linking function (if enabled), obtain verification codes of skills, obtain skill binding status, and unbind skills. Unified user experience A brand-specific App and voice skills contribute to a unified user experience for consumers. For example, if a device of a brand can be controlled by Amazon Alexa, and the Amazon Alexa voice skills of Tuya are bound to the OEM App, you need to perform the following steps for skill binding: Step1: On the OEM App, configure skills and the skill binding tutorial. For more information, visit https://developer.tuya.com/en/docs/iot/oemalexa?id=K989rqpcjiomr. Step2: Bind the voice control skills with the App. After the steps are complete, you can view the "Third-Party Integration" section in the OEM App. You can tap it to view the skill binding tutorial. If the skill account linking function is enabled, you can skip the step of login with your account and bind skills quickly.
Check whether the device uses the low power consumption firmware whose default polling interval is 5s. The firmware requests data from the gateway only after the polling interval ends.
Yes, it is still displayed as online and can deliver data to the MCU.
Yes. The Bluetooth LE device in low-power mode can still be paired only if interaction product information exists and broadcast is not disabled.
You can enable the low-power mode for a Bluetooth LE device only after the cloud module is initialized, that is, after the module reports its working status.
Check whether the low power consumption firmware is used. If yes, wake up the module before you send data.
Check whether the low-power mode has been enabled for the module. If yes, wake up the module before you send data.
The DP type extension service is contained in the protocol of a serial port with standard power consumption. After the service is enabled, the types for delivering DPs can be extended. Main source types include: LAN, WAN, and Bluetooth.
Send the new function setting notification command of the device between the 0x01 and 0x02 commands. Set bit0 of the abv field to 1 to enable the Bluetooth status notification.
There are three modes: long press, short press and double click.
After you download the development framework, if VS Code accesses the current folder for the first time, the message shown in the following figure will be displayed. In this case, select "Yes, I trust the authors. Trust folder and enable all features.".
A dual-band Wi-Fi device supports two frequency bands: 2.4 GHz and 5 GHz.
📎 zigbee_check (1).zip The preceding file can be used for communication detection for a Zigbee module. If the Zigbee version number cannot be obtained due to Zigbee flow control issues, use this solution for testing.
Perform the following steps for troubleshooting: Check whether the PID knowledge in the corresponding language is created. The PID knowledge instead of the general product knowledge shall prevail if any. Check whether the product you view is consistent with the product category of the knowledge. For example, if your product category is lighting/light source/Wi-Fi, but you created general product knowledge under the lighting/light source/Bluetooth product category, the general product knowledge cannot be displayed. Check whether you have set a default language and whether you are viewing the knowledge on a mobile phone.
Tuya provides the editable all-in-one panel of smart locks. You can change the background, picture, and color of the panel. For more information, go togo to Device Interaction Panel Control on the Tuya IoT Platform to learn more.
To use the I2C solution, pay attention to the PCB layout. I2C signals are vulnerable to interference from switch signals (AC-DC drive circuit). If the interference is serious, add a 10 pF to 50 pF filter capacitor to the DAT and CLK signal during the PCB layout design to reduce interference. Pull-up resistors need to be added to the physical circuits of the peripheral I2C DAT and CLK signals. Typically, the resistance value is 4.7 kiloohms, which can be adjusted based on the actual scenario.
If you can't load local bundles in Android: Tap System Settings Application Permission Settings Tuya Panels RN on your mobile phone and check whether the Pop-up window permission is enabled.
The App UIs of some all-in-one products do not support temperature mode switching. For more information about specific product categories, submit a ticket at https://developer.tuya.com/en/docs/iot/troubleshooting?id=K9258orwg9heh.
The power consumption varies with modules. For more information, visit https://developer.tuya.com/en/docs/iot/zigbee-module?id=Kaiuylhfmwnbs.
No. The same encryption algorithm is used for the lock and cloud. A unique available code can be generated based on the time and device information, without the need for an Internet connection.
Possible causes: 1. The online temporary code has not been delivered to the lock due to network issues. 2. The offline temporary code is strongly related to the accuracy of the RTC of the lock. The inaccuracy of the lock time affects the effective time of the offline code. 3. The temporary code has not taken effect.
This is because the Wi-Fi lock is usually in sleep mode. After the code is deleted from the App, the deletion state is not synchronized to the device. In this case, you need to wake up the device so that it can request a temporary code again.
This is because the temporary code is already generated in the App; however, the Wi-Fi lock is usually in sleep mode. In this case, you need to wake up the lock so that it can communicate with the cloud to obtain the code. After you wake up the lock, wait for the password synchronization to complete. Access the App panel to view the status of the temporary code.
Tuya's new firmware provides a production test instruction for connecting to the specified SSID and password. For more information, visit https://developer.tuya.com/en/docs/iot/wifi-general-production-test-documentation?id=K9hhi0xucqxhf.
Test whether the Zigbee device can receive Add Group information. The simple way to judge is whether the Zigbee device can be added and verified successfully in the scene switch panel of the App; if it can be added, it is supported; if it cannot be added, it is not supported.
The Tuya MCU simulation and debugging assistant simulates the MCU data sending and receiving. It is connected to developers' Wi-Fi modules through a USB-to-TTL tool to: verify whether the Wi-Fi modules function properly; test the app panel display before MCU development is completed; offer data to the developers for their reference on how to send or return data to the modules.
If the DP point is changed during the development process, after the program is transplanted, the device needs to be removed and the network is reconfigured.
The Zigbee module must pass through the gateway to communicate with the cloud.
The current voice module protocol is the same as the general.
Analysis: 1. Voice password error. 2. The lock is offline. 3. The remote unlocking function is not enabled in the App. 4. Remote unlocking by voice is not enabled in the App. Advice: 1. Check that the voice unlock code is correct. 2. Check that the lock is online. 2. Check that remote unlocking is enabled in the App. 3. Check that remote unlocking by voice is enabled in the App.
For the sake of security, the validity period of each oauth token is currently two hours, and the validity period of the token for device network configuration is 5 minutes. After expiration, refresh_token needs to be used in exchange for a new token.
Switching too fast may not meet the requirement of switching times.
The device is disconnected from the network for more than 3 minutes； MCU end sends a reset command and enters the network configuration mode. When the network connection or router performance is not good and the interaction between the module and the cloud fails, the module actively disconnects from the network and then tries to connect to the network again.
Analysis: 1. The device is out of power or disconnected from the network during the upgrade. 2. The network environment is unstable during the upgrade. Advice: 1. Make sure that a low-power module has continuous power supply during the upgrade. 2. Make sure that the device and network environment are stable during the upgrade.
The general baud rate of the Bluetooth door lock serial protocol is usually 9600.
There is no time limit.
Remove and restore factory Settings require the door lock to clear all local parameters, remove will not change the device ID information, restore factory Settings will change the device ID information.
The members of the Bluetooth lock directly pull the family member account information of pp. The family members are divided into family owners, family administrators, ordinary family members, and other users created by the panel (you can also share accounts).
The Bluetooth module does not query the PID of the device product.
Supported, the app can be synchronized with the local door opening method through the synchronization function.
At present, the Bluetooth door lock supports both single-point App Bluetooth connection and Bluetooth gateway connection.
Check whether DP44 is checked. Checking DP44 means that the device supports local RTC and can accurately record the time effect of the opening mode, so it is open to sharing users. If not checked, only open bluetooth door permissions for security reasons.
Analysis: 1. Family owners have the permissions to add an unlocking method, and modify, delete, and view unlocking methods of all family members. 2. Family administrators have the permissions to add an unlocking method, and modify, delete, and view unlocking methods of all family members. 3. Common members in the family have the permissions to add an unlocking method, and modify, delete, and view the unlocking methods they add. 4. If the local real time clock (RTC) function is configured for the lock, device sharers have the permissions to add an unlocking method, and modify, delete, and view the unlocking methods they add. 5. If the local RTC function is not configured for the lock, device sharers have no permission to add, modify, delete, or view unlocking methods. Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
Supported, even if the mobile phone and Bluetooth lock are disconnected, the remote can be removed or the lock, but note that this time the lock is not known to be removed by resetting, and a new app is needed to open the search network , Query the cloud via Bluetooth broadcast package information, if the cloud returns unbound, the door lock will automatically reset at this time.
This is possible because when deleting door opening methods such as fingerprints, passwords, cards, etc., there is no need to interact with the cloud. The app directly interacts with the module through the Bluetooth channel; after the mobile phone restores the network connection, the cloud will issue the door opening synchronization command. After synchronizing the local door opening method, the app panel will be automatically deleted synchronously.
Is needed, otherwise it may cause the panel to collapse.
It cannot be built after closing, but the ones built before are still available.
Yes, the Bluetooth module defaults to a 1.2s cycle broadcast, to ensure that the app is connected to the Bluetooth door lock.
Can be changed.
Can be changed.
You need a mobile phone to connect to the external network, because you need to go to the cloud to pull the unlocked user data information.
The default is fully open and cannot be changed.
Full open by default, can be changed.
Permanent by default, cannot be changed.
Please log in to IoT Platform-Operation to check whether there is any data reported in the device log. If the data is reported successfully, the panel is abnormal, please consult Tuya staff.
There are many reasons for the connection failure. Different firmwares must use matching PIDs. For example, single-point firmware uses single-point PID, sigmesh firmware uses Sigmesh PID.
Please use Tuya's MCU simulation assistant host computer to eliminate the format problem of the reported data. Please ensure that the device remains connected and the dp point of this product also exists.
When reporting, you must report the corresponding member ID.
There are 3 states in total: 00: unbound 01: unconnected 02: bind connected.
The current frequency drive range that can be set is 100HZ to 20KHZ.
Currently, we are working the SM2135E constant current driver solution and now the PWM-to-constant current solution is supported.
Yes, but a Bluetooth gateway is required.
Yes. However, to use the timing feature, a gateway is required.
In order to further reduce power consumption, after the low-power control pin (SDA) pulls the pin low, the broadcast time of the module will be changed to 1s. Because the broadcast time is too long at this time, the network distribution time between the module and the App will become very long. The broadcast time can also be set via the serial port (refer to Modify advertising interval in low power mode (0xE2)). Pull up SDA, exit the low-power state, and change the broadcast time to 100ms for fast connection.
Mainly used for the module to query the datapoint status of all "obj" types of MCU, and for the panel to display the initial value.
There are multiple formats for the network time, which can be formatted and set according to the time zone data.
Description of the internal timing of the Bluetooth module: Telink’s modules currently do not use external rtc, and the timing error is relatively large. In low power consumption mode, the 24-hour error is less than 1 minute. Projects that require precise timing need to be timed by the MCU itself and sent using the MCU's own time.
In order to facilitate the user to store some important records in the module when the Bluetooth is not connected, it will be automatically uploaded after the Bluetooth connection.
MCU sends instructions to query module connection status.
MCU sends query module version command.
The module will not send the heartbeat packet after getting the PID information of the device. That is, after MCU replied 01 command, the module will not send any heartbeat packets.
No.
Yes, but for performance requirements, only low-power broadcast interval settings are opened.
In order to reduce the power consumption during sleep, you can use this command to turn off the internal timing function of the Bluetooth module. If MCU does not need the time function, you can turn off the function. When the timing and broadcast function are off, then pull down the low power pin, the module will go into deep sleep, the power consumption reduced to 4ua. After waking up, the module reboot and run again. This setting will be stored permanently.
a. When the MCU receives the "command issuance processing frame, it executes the corresponding datapoint command correctly, and then sends the changed datapoint state to the module through the "status report" frame; b. MCU actively detects that the datapoint has changed, and will Datapoint status is sent to the module;.
There are three distribution methods: 1. Make the module in the network configuration state, open the App on the mobile phone, select the Bluetooth device, the device name will pop up, and click connect. 2. Entering the automatic search page can also enter the distribution network process. 3. Bluetooth mesh products support gateway-to-sub-device network distribution.
When the power supply voltage is lower than the normal operating voltage, the internal flash operation of the chip will have the risk of error, causing the firmware or user data to be abnormally modified. There are two ways to avoid it: 1. When the MCU detects that the battery voltage is too low, cut off the power supply of the module. 2. When the MCU detects that the battery voltage is too low, you can turn off the broadcast and system timing and put the chip in deep sleep mode. Won't work. The minimum working voltage of Telink Micromodule is 1.8V, and the MCU can be set to 2.0V (slightly higher than 1.8V) to turn off the module.
Yes, using Tuya Bluetooth gateway, remote control can be done through the gateway.
Analysis: The manual lock and lock status data points are not configured for the lock. Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
Analysis: The Bluetooth lock is offline. Advice: Check that the Bluetooth lock is online and in the controllable range.
Press and hold any button to enter the net pairing mode.
No.
Yes, but Bluetooth gateway adaptation is required.
The standard power consumption state is 100ms. The low power consumption state defaults to 1s, and its time can be set. The longer the broadcast time, the longer the phone connection time.
Small Bluetooth appliances do not have virtual devices, so you cannot scan the QR code to preview their control panels. This does not affect your use of the app to control the appliances.
When the MCU receives 55 aa 00 A1 00 00 A0 from the Bluetooth LE module, the MCU can be restored through the related operation. Note: Earlier firmware versions do not support this interface, you can operate when the module working status is 1 (unbound).
In a Bluetooth module's CCT firmware, the CW and WW pins are used as the PWM output for brightness adjustment and color temperature control, respectively.
The DP is reported in combination, and the two DPs of weight and impedance must be reported together.
It can be upgraded via mobile phone or gateway.
Within the distance range, no quantity limited.
Tuya module supports secondary development, but if your gateway is not a Tuya solution, it cannot support networking linkage. But we can provide the corresponding open API to support communication with third-party systems. You can refer to: https://docs.tuya.com/en/iot/open-api/quick-start/solution-overview?id=K95ztz6mui51y.
(1) Full verification process of the host computer: requires using of serial communication, limited to PCBA test, but the test is more comprehensive, can verify many functions. (2) Host computer infrared transceiver verification process: This process only verifies part of the function of the infrared transceiver, which can be used in PCBA and finished product testing. (3) Single device infrared transceiver verification process: This process only verifies part of the function of the infrared transceiver, which can be used in PCBA and finished product testing.
When using a module in a lamp with a metal cover, for example, a downlight, spotlight, or outdoor lamp, consider the antenna RF design and use an external antenna if needed. To use the module in a driver, keep the module away from the components such as the transformer and inductor.
Hello, currently this dp point has no practical effect, and the specific function is determined by the motor.
It is recommended to modify the keyword switch to switch_1.
Please check the acceptable length of the MCU program serial port, keyword Wi-Fi_UART_QUEUE_LMT, which can be enlarged according to the memory.
Before the product being shipped, the device is connected to the standard load to calibrate the parameters in the firmware under the production testing circumstance. If the parameters are within the specified range, then the data collected this time will be used for measurement afterwards.
The difference is that the power supply voltage and the calibration load are different, and the two production tests are formulated for sockets of different voltages. Which voltage measurement is used depends on the firmware and the rated voltage of the socket design. If the socket usage scenario is 220V, 220V production test is recommended. If the usage scenario is 120V, it is recommended to use 120V production test.
For electrical products, the key configuration (button or touch) will be selected during product configuration. This configuration will affect the firmware. The touch switch takes effect without releasing the button (perform the corresponding action on/off), and the button takes effect after releasing the button.
High and low levels can exist simultaneously.
Yes，adding Asin will incur a fee.
Yes, only half-wave rectification can be used, and full-wave rectification can be problematic.
Tuya Cloud provides the interface current limiting dimension, as shown below: application layer traffic: 500,000 times / day Interface-level traffic: 500 times / second Detailed description: application traffic is the number of times the calling key assigned to the developer can call the interface each day. Once the interface request is started, as long as the request reaches the Tuya server, the interface request will be counted once regardless of success or failure. In order to prevent a single user from making unlimited requests to the top server, each application limits the total number of requests; Interface traffic is an interface for each developer to call the API itself, and traffic protection will also be set, such as obtaining device information APIs to prevent excessive calls and cause back-end failures. This limit for API traffic is a system protection limit.
No need, Tuya has a supporting production test program solution,you can view the documentation at: https://developer.tuya.com/en/docs/iot/introduction-of-tuya-production-test?id=K962exa4kmgaw.
The protocol difference between the old and new DP: The old DP uses RGB format, and the dimming precision is 255. The new DP protocol uses the HSV format and has a dimming accuracy of 1000.
You can deploy the Wi-Fi module on the temperature controller.
It flickers because the module's driver frequency is low. To solve the problem, increase the module's PWM output frequency to 16 kHz or higher, if the LED driver supports such a high frequency. Alternatively, use a constant-current solution. Adjust the brightness to the lowest level and use a mobile phone camera to check whether your lamp still flickers.
Tuya provides the PWM and I2C solutions with different firmware to control RGB lamps' light colors. If color control is abnormal, the module firmware may mismatch your hardware design.
Tuya provides the CW and CCT solutions with different firmware to adjust lamps' color temperatures. If you cannot adjust a lamp's color temperature, the module firmware may mismatch your hardware design.
Yes, recommended to use small volume modules such as LC5, LC8. Refer to module specification for specific size parameters.
If it flashes twice a second, it means that it has entered the state of network distribution. You need to check whether the platform is configured to "flash immediately after power-on" status.
The advantages of laser navigation is the measurement relatively accurate. Operation in environment outside of direct light is stable, and intuitive path planning and navigation; high positioning accuracy, which enables accurate positioning even in dark environment.
[Single password] Problem analysis: 1) Clearing a single password has expired 2) Clearing a single password will become invalid after being used successfully for one time. 3) The door lock's hardware clock RTC skew is too large (remove the minute, and round the whole point, be inconsistent with the cloud) Guidance suggestions: 1) Confirm whether the clearing single password has expired. 2) Confirm whether the clearing single password has been used. 3) Confirm whether the door lock MCU performs hardware clock RTC calibration automatically. [All passwords] Problem analysis: 1) Clearing all passwords will be invalid automatically after obtaining if it is not used within 24h. 2) Clearing all passwords will become invalid after being used successfully for one time. 3) The door lock hardware clock RTC offset is too large (remove the minutes, round off, and it is inconsistent with the cloud) Guidance suggestions: 1) Please use the clearing all passwords immediately within 24h after obtaining. 2) Confirm whether the clearing all passwords has been used. 3) Confirm whether the door lock MCU performs hardware clock RTC calibration automatically.
Cleaning area: refers to the current cleaning, reported by the device in real time, and displayed on the current cleaning interface. Total cleaning area: the total area reported by the device after one cleaning is completed.
Analysis: Functions related to the message center are not configured for the lock on the IoT Platform. Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
MQTT and HTTPS protocols are used.
Tuya devices work in station mode when connected to the network. When in network configuration mode, they can work in station mode (EZ network configuration mode) or AP mode (AP network configuration mode).
The general solution is to use the serial port for protocol interaction, not the original AT command.
Yes.
Tuya's current Wi-Fi modules that support 5G band routing are: WBR1D, WBR2D, WBR3D, WBR1D-IPEX modules of the W701D chip. The above modules support 2.4G and 5G band routing, as well as connecting via Bluetooth LE network configuration.
Tuya security library uses TLS1.2 and AES128, and all communication data is encrypted.
If you are interested in product cooperation or have problems using it, please send an email to service@tuya.com; if you have a promotion cooperation requirement, you can send an email to one@tuya.com.
NM1 module consumes very low current under PSM which is 3uA. The main purpose of PSM is to reduce module power consumption and extend battery power supply time.
The peak current is 300ma, which is specifically related to the signal strength. The worse the signal, the higher the peak current, and the higher the power consumption of the module during the network search process. After the network search is successful, it will enter the PSM, and the power consumption will be reduced.
Normal operating temperature: -35°C ~ +75°C Extended operating temperature: -40°C ~ +85°C Storage temperature: -40°C ~+90°C.
Yes, NM1 module has extremely low current consumption under PSM mode (minimum current consumption is 3uA).
Yes, it does. Different module models correspond to different network indicator pins, please check the corresponding module datasheet: https://developer.tuya.com/en/docs/iot/nb-module?id=Kaiuymgk901fv.
Different chip modules support different frequency bands, please check and view the hardware documents: https://developer.tuya.com/en/docs/iot/nb-module?id=Kaiuymgk901fv.
The general firmware is not supported to use the extended IO functions.
The method is the same as the Wi-Fi ones, which uses a serial port to complete the communication protocol based on Tuya.
The NB module can be waken up about 4ms, the time can be extended appropriately to ensure the stability of the module.
Single-tone: 25.5kbps (downlink), 16.7kbps (uplink) Multi-tone: 25.5kbps (downlink), 62.5kbps (uplink).
terminal state power consumption measured results of an environment PSM status 3 uA 2.7 uA eDRX idle status 300uA to 2 mA 1 mA DRX idle status 1 to 4 mA 1 mA Connection status sends 200 mA, and receives 65 mA sends 189 mA, and receives 161 mA.
Connected status: The module is in the Active (working) mode, all functions are normal and available, and the data can be sent and received; the module can be switched to the Idle mode or the PSM mode in this mode. Idle state: The module is in the Light Sleep mode, the network is in DRX/eDRX state, and the paging can be received in the paging window. The module can switch to the Connected or PSM mode in this mode. Power-saving state: The module is in Deep Sleep mode, with the CPU powered off and the RTC working inside alone. The network is in a disconnected state and cannot receive the downlink data. The module can be switched to Connected mode in this mode.
NM1 series voltage range: 2.2~3.63V Typical power supply voltage: 3.3V NE1/NX1-CT Voltage range: 2.2~4.5V Typical power supply voltage: 3.3V.
Tuya uses Telecom and Mobile operators.
Tuya's NB module SIM card power supply voltage is 1.8V.
When the module is under sleeping status, resetting is invalid. Resetting will take effect. only if the module is under working status.
Wi-Fi, Bluetooth, Zigbee, NB have corresponding products.
The sensing angle of PIR is 150 degrees, and the best distance facing to object is up to 7 meters. The standby current is less then 20uA, and the reporting current is 5mA, and the corresponding batterie is the CR2450.
Powered on the device: the red light is on for 3 seconds and then goes out; The network status: the green light flashes quickly; The standby state: the light is off; Report the data successfully: the green light flashes three times; Fail to report the data: the red light flashes three times.
The data sent by the APP is HSV data and needs to be converted into RGB data，You can refer to the following documents：https://developer.tuya.com/en/docs/iot/product-function-definition?id=K9s9rhj576ypf#title-7-DP24%3A%20color.
Tuya Module Debugging Assistant is a serial port debugging tool that integrates communication protocols of Tuya modules. With diversified functions and convenient use, it is often used for the development debugging of general MCU connection solutions. It integrates common serial port protocols of Tuya modules, including Wi-Fi, Bluetooth, Zigbee, and NB-IoT. It can simulate the module to verify the MCU code logic and simulate the MCU to debug the network pairing function. Module Debugging Assistant deployment condition： The software is made using Windows Presentation Foundation (WPF) technology. The .NET Framework 4.6.1 is required, specifically: a). The Windows XP operating system is not supported. b). Windows 7 operating system must be installed with .NET Framework 4.6.1. c) Windows 10 system earlier than Version 1511 must be installed with NET4.6.1, and it is not required for Version 1511 and later versions. Downloading: When creating a custom solution on the IoT Platform, you can download it in the Download Documents area on the Hardware Develop tab. Note that when the development platform modifies the function point: If you use the Tuya serial port debugging assistant to debug, you need to download the new function debugging file and import it into the Tuya serial port debugging assistant to use it to synchronize the modified content; If you use the Wi-Fi module for debugging, you need to remove the device and add it again. Because every time a device is added, the local function debugging file of the module will be updated; For detailed guide, please refer to the document link: https://developer.tuya.com/en/docs/iot/module-debugging-assistant-instruction?id=K9hs0cj3lf0au.
Yes, even if it is not an M1 module, as long as it is a standard product and function, it can be controlled.
Tuya Wi-Fi module uses LWIP protocol stack.
Currently, Tuya provides production test videos for lighting products in three communication modes: Production test video for Zigbee RGBCW lights:https://www.bilibili.com/video/BV154411C7on Production test video for Wi-Fi RGBCW lights:https://www.bilibili.com/video/BV154411m7PX Production test video for Bluetooth mesh RGBCW lights:https://www.bilibili.com/video/BV1wt411F738.
Not yet, you can use Tuya's gateway solution for wired connection.
Tuya currently has mass production public version lock protocol types: Wi-Fi, Bluetooth LE, Zigbee, NB-IoT.
Yes. You can create plug-and-play and custom switches with a single live wire under Electrician.
Analysis: Currently, Tuya locks support remote unlocking and locking, and lock status query by using Amazon Alexa and Google Assistant. Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
Dear user, we are not support integrate Z-Wave devices, and there are no plans in this area for the time being.
Yes,Tuya module supports multi-data combination to upload in a package.
Tuya Support Center belongs to Tuya's intelligent service system, which aims to comprehensively improve service quality and service efficiency. As a platform communication tool, solve your communication and collaboration problems with Tuya during product development and after-sales. The Tuya Support Center has quick and easy entry questions throughout the Tuya IOT platform. You can easily submit your questions at the quick entry of product development, App workbench, user feedback, etc. We have a professional technical support team to efficiently respond to your questions. At the same time, you can check the processing progress of the problem in time here, to ensure that the processing progress of the problem can be tracked, and the historical processed problems can be traced back.
Tuya MCU SDK serial port processing mechanism is based on asynchronous communication full-duplex serial port, sending and receiving can be performed at the same time, if you use simplex serial port, there may be packet loss problems.
After the product with electricity statistics is calibrated. The calibration parameters will be reported, and Tuya can query the product calibration parameters to analyze the calibration parameters and determine whether the product has problems.
Support 32-bit computer, the new version of Tuya cloud module burning software has been made compatible, can support both 32-bit and 64-bit computer. If you want to get the burning software, please contact Tuya staff.
Tuya's gateway must be used to develop Zigbee products. Tuya can also directly offer the gateway for your OEM. If you need it, you can contact Tuya's business. The Zigbee 3.0 is a unified standard for the application layer launched by the Zigbee Alliance. All sub-devices that fully comply with the Zigbee 3.0 standard can be interconnected theoretically. Tuya's Zigbee gateway and most of the sub-devices (except door locks and general docking) comply with the Zigbee 3.0 standard. Therefore, the Zigbee sub-devices of other customers can be connected to the Tuya gateway, and the Tuya Zigbee sub-devices can also be connected to other gateways which comply with the Zigbee 3.0 standard. But the Zigbee 3.0 application standard is a comparison Broad application protocol, and some functions are not included in the standard protocol, so some functions may not work normally after the devices of different manufacturers are interconnected. Please take the actual access test verification results as the standard.
YouTube:https://youtu.be/14E-R5X6ERk Tuya provides a variety of TuyaOS development solutions, such as no-code development, microcontroller unit (MCU) SDK development, module SDK development, and Link SDK development. All IoT devices can be upgraded based on these solutions. You can choose among these solutions to fit your device types and development capabilities, and easily connect your device to the network with a few simple steps. Based on the different development methods, the TuyaOS development solutions provided by Tuya are classified into the following types: No-code development This solution is suitable for products with standard functions, such as electrical products, lighting products, and sensors. Tuya provides a visual function configuration interface. You can use this interface to configure the product functions, complete the firmware development, and manage smart products with a few simple steps. No programming experience is required. For more information, see SoC Plug and Play Solution. MCU SDK development This solution is suitable for hardware products that contain MCUs. Tuya provides the MCU SDK. The SDK encapsulates the API operations that enable multiple functions, such as uplink and downlink communication, over-the-air (OTA) updates, and data analysis. You can migrate the SDK to the MCU to define different pins, and call the required API operations to develop the application code and easily manage smart products. For more information about the MCU SDK development, see MCU Connection Solution. Module SDK development This solution is suitable for products that provide simple functions. You can use a module to implement SDK secondary development when you create the smart products. Tuya provides the module SDK. The SDK encapsulates the API operations for the hardware abstraction layer (HAL), system layer, network layer, and OTA updates. You can call the required API operations to develop the application code and easily manage smart products without t.
GNDS means an independent network but not a common ground cable.
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.
Tuya uses big endian mode for the serial communication protocol.
Yes. You can set the time through the parameter related to network pairing in the third step of hardware debugging during product creation.
When creating a product, the customer configures which IO port controls white light and which IO port controls red light or blue-green light at "Hardware debugging/firmware configuration".
Both public and private agreements are used.
Tuya Zigbee networking structure is: Tree.
The test items of a Tuya Zigbee module test include the clock frequency offset, carrier transmit power, adjacent-channel rejection ratio, receiving sensitivity, dynamic output power, spurious emission, spurious receiving, distance, current consumption, low-voltage consumption, high and low temperatures, and RSSI detection precision.
It means the transmission of one or more frequencies other than the necessary bandwidth. The transmission levels of these frequencies can be reduced without affecting the transmission performance. Spurious emission includes harmonic emission, parasitic emission, intermodulation products, and frequency conversion products, except for out-of-band emission. Test method: Enable the transmitter to transmit carriers at a rated power, reasonably set the VBW value in each observed frequency band, and measure the spur level.
It means the difference between the configurable maximum power output and the minimum power output, and measures the dynamic power range of Zigbee. To calculate the dynamic power output range of a transmitter, record the maximum power output and the minimum power output of the transmitter and calculate their difference.
Under a low voltage such as the power supply at the critical level, check whether the DUT's working state is stable, for example, whether read/write of the register is normal, and whether the RF function is normal. A wide voltage range is required during testing to ensure that wireless communication is normal.
Tuya Zigbee is developed based on Zigbee 3.0.
Yes, it supports the Zigbee standard 3.0 protocol.
The average power is 10ma in the fast network cofiguration state, and the average power is 3ma when the module is connected to the network.
Yes.
When Zigbee low-power device is deleted from APP or restore factory setting, the module automatically enters into network configuration mode and network timeout is 180s. The indicator light flashes at intervals of 250ms during network configuration process. After networking timeout fails, the indicator light will always on, and will be off when networking is successful.
Transmit the Zigbee shape modulation waveform through a transmitter. Connect to the power meter or spectrum meter through conduction to test the transmission power. That is, measure the current transmission power in the channel power mode. The rated maximum power output varies with chips. In general, the required maximum power output is more than 8 dBm.
Default starting with 'SmartLife'.
Such status is Wi-Fi configuration successful but not connected to router, general situation is wrong Wi-Fi password input or DP points exceed 25.
The SoC is generally set up after the module is scanned. After scanning the corresponding production test routing signal, the module feeds back the corresponding status data. When the MCU is docked, the customer usually sets the production test result operation and result value.
[No automatic allocation] Problem analysis: 1) Please make sure whether the function is correctly turned on 2) The first data of each user needs to be manually allocated. Suggestions: 1) Confirm whether the device is automatically allocated 2) Confirm whether the current user is weighing for the first time. [Assignment error] Problem analysis: The user's current weight has a large deviation from the historical weight data. Suggestion: It is recommended to re-allocate the latest weight before turning on the automatic allocation.
Not possible. May be held legally responsible.
Auxiliary lighting (ambient lighting) lamps are used for decoration instead of main lighting. These lamps are often used as decorations for Christmas in North America. You are advised to use light strips, light strings, and outdoor lamps. It is recommended that you consider the Bluetooth solution for outdoor lamps.
The broadband network must be 2.4 GHz Wi-Fi network, and the minimum upgrade speed is more than 20KB.
ModuleOrder Process:Purchase intention submitted---Purchase intention confirmed---Production info confirmed---To be scheduled---In production---Order completed Empty ModuleOrder Process:Purchase intention submitted---Purchase intention confirmed---Production info confirmed---To be scheduled---In production---Order completed MaterialOrder Process:Purchase intention submitted---Generate Purchase Order---Pay---Ship---Order completed LicenseOrder Process:Tuya comfirming price---Generate Purchase Order---Pay---Pick up---Order completed Traffic PlanOrder Process:Tuya comfirming price---Purchase intention confirmed---To be effective---Order completed.
If the network configuration fails, you can use the following troubleshooting steps: 1. Check whether the module has entered the network pairing mode 2. Check whether you have selected the correct network pairing mode in the App 3. Check whether the Wi-Fi network is a 2.4 GHz network 4.Check whether you have entered the correct Wi-Fi password 5. Check whether the device's network configuration matches the platform settings.
Please check the GPIO inlet low level for more than 5s to trigger Wi-Fi reset.
When the MCU receives the state query instruction of the Wi-Fi module, the MCU shall report the locally reportable data one by one so as to facilitate the smart phone App synchronizing the device state.
Yes, open the local time in the SDK and then check the macro definition.
The serial interface assistant can send a network pairing command to the module only after the heartbeat packet, product information query command, MCU working mode query command, Wi-Fi working status, and MCU connection status are sent to the module using the basic protocol.
The module notifies MCU Wi-Fi current operating status through the serial port, and MCU provides display support; MCU detects Wi-Fi reset demand and notifies module to reset Wi-Fi through the serial port.
Yes, in the fifth step of creating a product, after confirming that the development is completed, you can fill in a logo with no more than 10 characters when placing an order.
When the MCU receives the Bluetooth LE module status query, the MCU needs to report the locally reportaBluetooth LE DP data one by one, and the App panel will be synchronized the current status of the device.
As the Wi-Fi module consumes a lot of power when transmitting and receiving signals, it will pull down the power supply voltage.
The required supply voltage and current of the Wi-Fi module are 3.3V (3.0V-3.6V) and over 300mA respectively. In case the supply voltage of the module is too low or too high or the current of the module is too low, the module cannot work properly, and the following phenomena may occur: The module cannot be started normally and no normal heartbeat packages are sent. The module is restarted repeatedly or restarted during the network configuration.
It may be due to the following reasons: 1. The serial port pins are connected correctly 2. Whether the power supply of the module is stable, please use a stabilized power supply to test 3. Whether the serial port assistant is connected correctly If you still can't locate the problem, please consult Tuya staff.
It takes about 5 seconds.
For details, visit https://developer.tuya.com/en/demo/robot-demo-based-on-raspberry-pi3-modelb?count=0.8229614641223695.
Yes, but the gateway currently needs to use a wired gateway, and wireless gateways do not support OTA for MCU.
When there are many open door records, the query supports page turning. For the timeout problem, it is recommended that the user should not request too much at a time. This logic Tuya is already being optimized.
The cloud will filter duplicate reported data.If you don't want the duplicate data to be filtered, you need to configure this dp point to not filter.
You can check the SDK migration guide: https://developer.tuya.com/en/docs/iot/overview-of-migrating-tuyas-mcu-sdk?id=K9hhi0xr5vll9.
Analysis: 1. The battery level on the smart lock is too low. 2. The smart lock fails to report its battery level after pairing. 3. The smart lock has reported its battery level after pairing, but the battery level reporting log is missing. Advice: 1. Check that the battery is brand new with a high battery level. 2. Confirm with your Tuya account manager whether the product connection protocol meets the standards. 3. Remove the battery and install it again for the app to re-obtain the battery level. Alternatively, perform pairing again.
Analysis: 1) MCU not support online temporary pwr function; 2) Common member or shared account does not have the access to temporary pwr. Suggestion: 1) Please contact with Tuya Customer service if the Product integration meet standard; 2) Please check the current role is Family owner or Administrator.
Analysis: Yes, it's OK to use offline temporary pwr when Wi-Fi not connected.
Problem solving. 1）Wi-Fi, Zigbee lock can be configured with intelligent automation linkage. (2) Bluetooth door locks support the configuration of intelligent automation linkage under the Bluetooth gateway link.
Analysis: Step 1: Open the app and go to the Smart page. Tap Automation and then the plus (+ ) sign in the top right corner. Step 2: On the Create Smart page, tap When device status changes. The All Devices page appears. Step 3: Tap the smart lock. On the Select Function page, you can specify a trigger condition based on functions, such as unlocking with fingerprint, unlocking with a password, or unlocking with the card. For example, you can specify a condition where the number of unlocking times with fingerprint equals three. Step 4: In the Set up task step, tap Run the device. The All Devices page appears. Step 5: Tap the smart lock. On the Select Functions page, you can specify on/off and brightness adjustment as the tasks to be run.
Analysis: 1. A common family role does not have the remote unlocking permission. 2. The family administrator has disabled the remote unlocking function. Advice: 1. Check the role of the current account in the current family. 2. Check the remote unlocking setting of the lock.
Yes.
Remote control requires the Wi-Fi module to keep online, which consumes much power. You are advised to use a low-power module.
Yes. Bluetooth remote controls can control Bluetooth lamps.
Tuya sells modules. The specific product needs to be developed by the developer. The specific MCU used needs to be developed by the developer.
Yes. Use the I2C 2135E or the PWM for constant-current conversion.
Tuya does not yet provide Sub-1 GHz wireless solutions. We will provide such solutions for LoRa or other low-frequency communications. Currently, we provide gateways to support the transformation from Wi-Fi communications to Sub-1 GHz communications.
Currently does not support exporting the history of door lock opening through the App.
Enterprise authentication information and account number are bound generally and it cannot be unbound. If there are special circumstances, please contact online customer service team to help you deal with it.
Analysis: 1) For One-Off Pwr, 10 pwrs at most in 60mins; 2) For unlimited pwr, in same valid time period, only 1 pwr available; 3) For clear code, 10 pwrs at most in 60mins.
If the product DPs on the old panel are the same as those on the new panel, you can contact Tuya technical support to upgrade the panel.
If Purchase current version is available in the pop-up window, you can ignore the firmware update request and click Purchase current version to order the mass-produced modules that use the current firmware version. If only Update version is available, the update is mandatory because Tuya has updated important technologies. You can purchase modules only after you update the firmware.
You need to re-download the MCU SDK, you can choose to re-port after downloading, or you can modify the changed content into the previous SDK.
This problem is the problem of red light beads. This is because the turn-on voltage of the red light beads is about 2V, and the turn-on voltage of the G and B beads is about 3V. During the process of turning off the lights and powering down, when a certain critical voltage is reached, The GB light is not on, but the red light bead has a low conduction voltage, and the red light can be on at this time, so it will flash red visually. Since the VF of the red light beads is low, the red light will be extinguished at the end of the power off, and the red light will appear to be flashing. This can be optimized by electrolysis and resistive acceleration of electrolytic discharge in the RGB power supply, but cannot be completely avoided.
a. Be sure to find out if it's a power supply problem (light bead supply problem or a module supply 3.3V issue?) or the module output PWM signal problem, or the wiring and terminal connection problem of the structure. b. If the PWM waveform of the module is fine after single testing, but the PWM output is abnormal after putting the module on the PCB, it could be an interference in the relevant pins of the module that causes the module to start abnormally (e.g. IO15 and IO0 of E3L); c. Find out which part of the module has the problem and then detail analysis. If it's a module issue you can contact the relevant people at Tuya. If it is a power driver issue, it needs to be analyzed case-by-case.
a. First find out whether the cause of the shake/flash is the module abnormality, or the power supply design abnormality, or the matching problem; b. Use an oscilloscope to see if the module Vcc and PWM waveform is normal (mainly to verify whether Vcc has small pis, PWM waveform no shake and interference burrs), if the module is normal, then it may be the power control part problem; c. Use an oscilloscope to see the driver power output main Vout waveform is stable or not, whether has small pit, and whether the PWM dimming circuit is stable or not; d. Use DC source power supply to see if the Wi-Fi module is shaking or not(Wi-Fi module power consumption is extremely unstable, the max. instantaneous 450MA above, the min. is only about 20MA); It may be the Wi-Fi module power on which caused the Vout has small pit); e. Check if the light bead is bad, you can replace the light bead to verify.
During transmission, the first three spare bytes are filled with 0. Assuming that the data length of the DP point is 4, the data range is 0x00-0xFF, and the transmission data is 0x19, and the report format is 0x00 0x00 0x00 0x19.
Wi-Fi ： CBLC5、WBR1-IPEX、CBU-IPEX、AXYU-IPEX Bluetooth ：BT7L-IPEX Bluetooth（sig）：BT8C-E Zigbee： TYZS15、ZSU-IPEX、ZTLC5 The platform iterates quickly, please check the specifications for the specific module details: https://developer.tuya.com/en/docs/iot/network-module-overview?id=Ka4z12ojepber.
If you cannot search for your Amazon Alexa Skill, it may be due to the following reasons: 1. Your skill is not listed in the area you are searching for. Solution 1: Because Amazon currently only supports English (US); English (CA); English ( AU); English (IN); English (UK); French (CA); French (FR); German (DE); Hindi (IN); Italian (IT); Japanese (JP); Portuguese (BR); Spanish ( ES); Spanish (MX); Spanish (US); Arabic (SA). So you can register an account through the Amazon-supported area site to use the skills. Recommended registration site: www.amazon.com Solution 2: Log in to your Amazon developer account and confirm which areas your skills are listed in. If it is not listed in the area you searched for, then you can’t find it. You can contact Tuya staff to update your skills to make it available in more areas (additional areas require a second charge) 2. Your There is an error in the search term. Solution: The current Amazon search rules require you to have a complete search of your skill name. For example, your skill name is: hommey smart. Maybe you only search for hommey and you will not be able to find your skills. You need to match all of them. Search it out.
Hello, you can try the following: 1. Replace more modules with IO ports; 2. The power indicator lights use hardware circuits to save some IO ports.
On the Hardware Commission page for creating a socket, select a pin for Power button and set it to Low-level active or High-level active. For details, see the module pin configuration diagram. 1. TYWE3S Wi-Fi module description 2. TYWE2S Wi-Fi module description 3. TYWE1S WiFi module description.
This is because product firmware is configured incorrectly. In this case, check the firmware configuration.
No, it will only be issued once.
If you use a Tuya plug-and-play SoC solution to develop the power strip, you do not need to connect it to an MCU.
I. Before purchasing service: You can start skill customization service only after your OEM App uploaded to the App Market. 2. How to purchase service: (1) Go to Tuya value-added service and purchase the skill platform and service you want to customize (currently available: Amazon Alexa, Google Assistant, Baidu Xiaodu, Tencent Cloud Xiaowei and Tencent Cloud Dingdang). (2) Choose the OEM App you want for skill customization, upload the complete application form and leave your contact information to purchase the service. 3. After purchasing the service: (1) Tuya's staff will contact you through Tuya's helpdesk within 1 day to help you set up an exclusive docking group and assist you in listing skills. (2) After you provide completed data, your skills will be developed and tested within 3 working days, and submitted for review. After 3rd party approved, you will be able to use your skills.
The price covers subscription, testing, and launch fees. If Skills need to be customized when extra DP points are required, quotation is provided after evaluation by development personnel.
No. Because invested service resources cannot be reclaimed, the service fee is not refundable.
Smart speaker access is enabled for PID. Only after it is enabled can your device support voice control. After PID access is activated, you need to search for skill on third-party platforms, and you can control your device by voice after skills are bound. Skill customization is activated for OEM App. After activation, you can search for your OEM skill on third-party platforms.
Cloud standard platform has not yet opened map stream data and IPC stream data.
This is just a label that represents the preview version. It needs to be released before the panel is removed. If there is a demand, you can submit a ticket for processing.
PID does not match with firmware.
It means the PID is bound under a specific App, and used other App to configure the network.
Analysis: 1. App message push is not configured for the lock on the IoT Platform. 2. You do not grant the message push permission to the app on your mobile phone. 3. The message push service is disabled in the App. Advice: 1. Confirm with your Tuya account manager whether the product connection protocol meets the standards. 2. Check that you have granted the message push permission to the app on your mobile phone. 3. Check that the message push service is enabled in the App.
Some packages provide outside mainland China app launch , such as [Annual Package Economic Package], [Annual Package Deluxe Package], if you need outside mainland China app launch service, you can purchase such packages. Other packages do not include the app launch service. If you encounter problems during the app launch process, you can refer to the free guide materials for app launch provided by Tuya or purchase the app launch service.
Authorized information Flash chip and main chip are one-to-one correspondence, the correspondence relationship can not be changed, otherwise the network can not be accessed normally.
If your app SDK contains the FAQ and feedback UI kit, you can go to Operation Knowledge Base, create a knowledge base on the page, and link the knowledge base to your app.
Hello, if there is a problem with your product, we will assist you to fix the problem until the product test passes. In general, you can pass the WWA certification by passing the test. Please refer to Amazon's review and rules for specific certification.
No. Google services and a network accessible to Google services are the prerequisites for using FCM and for using an account registered outside China to test FCM.
Hello, in the multi-language management in the "Product Configuration" of product development, you can modify the multi-language content of the product name, product function, device panel（Does not include Studio Panel）, network distribution guide, device message push, and firmware upgrade. The device panel is multi-language ( Non-product function points) need to be modified by us in the background. After modifying the multi-language of DP, you need to clean up the APP cache and end the APP process. After restarting the APP, you need to remove the device and add it again, and then turn on the device to get the parameters again. Note: For the multi-language of the Sutdio panel, you can select the entry in the Studio workbench to maintain and configure the multi-language separately.
It is recommended that you power the module and probe separately for debugging.
Use a DC source to supply 3.3V to the module, adjust the digital multimeter to the current mA gear, and then connect the multimeter in series to the power supply line (you can cut off the power supply wiring on the PCBA and connect the multimeter into series).
You can solve this problem in either of the following ways: (1) Reduce the AC-DC output voltage. (2) If the LDO loading capacity is insufficient, replace the LDO with one with a larger loading capacity, such as the 1117 LDO.
This problem is related to the hardware circuit and the lamp beads used. It is necessary to perform gamma calibration according to the lamp beads or dimming chip used to ensure accurate color.
LED lamp bead hardware problem: 1. The current of the color light can be adjusted. 2. Adjust the Gamma value of the platform white balance for correction.
Firmwares with or without PTA function are both available.
Analysis: 1. The name of a temporary password is displayed as unknown in the unlocking record. 2. The name of an unlocking method is not displayed in the unlocking record. Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
If you send product samples, Tuya will test them for free to ensure the access quality. If you do not, real devices cannot be tested and possible risks or problems will not be detected.
Background: Apple's third-party login in the App is controlled by an iOS certificate. If you turn on Sign in with Apple when generating a certificate, the Apple login button will appear by default after the App is launched in the App store (The Apple login is turned on by default with Auto-generate certificate). Problem: Your App has already been launched in the App store. When you click Apple login, it prompts that the registration is not completed, as shown in the figure below. Solution: 1. Log into Apple Developer. 2. Click Certificates, Identifiers & Profiles on the left navigation bar. 3. Click Identifiers on the left navigation bar, and select the identifier name that is the same as your App package name on the IoT platform ( Please do not choose the suffixed one but the one the same as App package name). 4. After entering this page, uncheck Sign in with Apple and click Save. Then re-check it and save it again. You do not need to update the App version or re-launch the App to the App store.
It is recommended that you select the dimmer category on the IoT platform to create a product. After completing the function definition and App interface configuration, Tuya will recommend the corresponding module for your product matching on the product hardware debugging or hardware development page according to your category and function.
When the platform creates a product, the default current range is 0-17A, and the reported value out of the range will be ignored. The values of product range created by the platform can be adjusted for testing.
If a module is not initialized properly during development, this function always returns 0xff.
Tuya Support Center belongs to the smart service system of Tuya. It aims to comprehensively improve business quality and efficiency. As a communication tool of the platform, Tuya Support Center enables you to communicate with Tuya during the product development and after-sales processes. Tuya Support Center consists of a development communication zone and an after-sales technical support zone. You can submit product development issues in the development communication zone and ask after-sales questions in the after-sales technical support zone. Tuya provides a professional technical support team to answer your questions efficiently. In addition, Tuya Support Center allows you to view the troubleshooting progress and check historical issues that have been resolved. For details, visit https://developer.tuya.com/en/docs/iot/troubleshooting?id=K9258orwg9heh.
If your product has been debugged, you can arrange production, purchase modules for trial production and mass production, release, and start production. For more details, please see: https://developer.tuya.com/en/docs/iot/purchase?id=K93b8w0ky9k4n.
DP data of door opening and closing events is usually used for alarm and scene trigger linkage.
Single live wire solution is for the power supply, but the Wi-Fi module consumes much power and is not recommended for a switch. You can use Zigbee and Bluetooth modules that have low power consumption.
Divided into 2 situations: If the device is not connected to the Internet after power-on, the time cannot be obtained. The power is not stored on a daily basis, but is stored in a temporary power pool. After the next network connection, it is reported to the cloud. The power in the temporary power pool is calculated to the day of the network. Inside the power record. If the device is connected to the Internet after being powered on but disconnected from the Internet again, the power will be stored daily, and a maximum of 10 records can be recorded, which is 10 days. Records are stored in flash and reported to the cloud after the next network connection.
You can choose a single lamp multiplexing scheme. The network indicator and the power indicator share one light. The light flashes during the network configuration, and the relay status is indicated after the network configuration.
There are two main reasons for the automatic switch problem: One is that the button ripple is too large or the touch button sensitivity is too high to trigger falsely. This situation may happen automatically. The second is that the module VCC is powered off and restarted. Solution: You can first determine the cause of the problem according to the phenomenon. Then implement corresponding measures for testing and verification. If it is a key ripple, you can add 104 capacitors to the key port; If it is a touch switch or socket, you can add RC to the touch terminal to reduce the touch sensitivity; If the module VCC is powered off and restarted, you can add Large output capacitor, increase the power supply IC over current point;.
The power indicator is blank, and the Wi-Fi indicator selects the IO to be used. The Wi-Fi lamp status selection indicates the relay status when not connected to the network (including disconnection) and when connected to the network.
Not supported, need to re-order on the platform.
You can integrate Tuya's embedded Android SDK.
For devices that have been equipped with a network, you need to "remove the device" in the App, wait 10 seconds, and then power on again. Note: If the network has been activated for more than 15 minutes, the production test function will be permanently closed and the production test function cannot be repeatedly entered.
If you only modify the panel UIs and not features, you do not need to upgrade the firmware. You only need to bind the modified UIs to the PID.
When the router is power off, the module will repeatedly scan previous connected SSID at 1s intervals and will print them in the log.
It requires pin TX\RX，PWRKEY and PSM_INT.
Advice: The family owner, administrator, common member, and device sharer can unlock the door remotely.
Analysis: There is no entrance from the device panel to modify or delete family member Suggestion: Please go to APP ‘Me' - 'Home Management' , choose the family member and remove.
You are advised to use Tuya home lighting products for ceiling lamps, panel lamps, and downlights. Tuya home lighting products have the following features: 1. Use similar driver solutions. 2. Support diversified appearance design, and each has higher value than a sphere lamp. 3. Support white light adjustment, and cold and warm light color change.
Usually used IO ports of VCC, GND, U0RX, U0TX, different chip platforms may require special pins to be set high or low.
Yes, you can provide your desired model or specify your requirements.
Try entering the following command to install: sudo npm install -g tuya-panel-kit-cli --unsafe-perm=true --allow-root.
The possible reasons are as follows: 1. Phone setting problem: -Check whether the mobile network is abnormal, try to switch the mobile network, and then try again. -Confirm that the current mode of the phone is normal, and some phones are in low battery, do not disturb mode and power saving mode, and gradually advance a series of network and activity restrictions in the background. -As we all know, some prototypes can only be received after the application's self-launch permission is enabled. -If you use fcm, please make sure your phone has Google services. And can connect to Google normally. 2. Equipment problems -Does the device confirm that the message sending is triggered? -Whether the device is configured with corrective rules for message push -Whether there is a message push record in the mobile application.
Report by way of filling. Such as 19- (256-19=ED)0xFFFFFFED.
The Tuya server only saves the data uploaded for the first time, and the rest will not be uploaded to the cloud. The module will filter repeated instructions.
After the Wi-Fi module enters the network distribution mode, if the router is not connected within 10S and the module is powered off, the next time the module is powered on, it will still maintain the previous network distribution state.
No, the login page will not be able to open, and the skill will be invalid directly; It is recommended to purchase a server for a consecutive monthly/quarterly/yearly to prevent the skill from being invalid.
Hello, you can refer to the document and name the DP point. Click to download: https://docs.tuya.com/en/iot/panel-development/panel-sdk-development/common-sdk-development/equipment-related-interface/equipment-related-interface?id=K9m1dlii6zkf7 link Please use the universal interface in App SDK.
To reach a global audience, you can customize multilingual UI text that appeals to a target market, including product name, data point, device panel, network connection guides, device message notification, and firmware upgrade. For details, please visit: https://developer.tuya.com/en/docs/iot/configure-in-platform/advanced-features/product-language?id=K93ixsjagr67p.
the fixed style template does not support editing, and the interface with a custom style when customizing the template or selecting the interface supports editing. Please confirm whether the APP interface template you selected is a custom template. In order to avoid the situation where the App model cannot be edited. For details, please visit: https://developer.tuya.com/en/docs/iot/app-ui-design?id=K914jpghswnq0.
PWM-I2C indicates that two I/O pins on a module separately generate SCL clock signals and SDA data signals to the LED control ICs to control the brightness or RGBCW five-way dimming and color mixing. The ICs use different protocols. Currently, the IIC SoC solution currently prevails on the Tuya platform. If you select other I2C options, use custom firmware.
Currently Alexa Skill supports the following 16 languages. The choice of language will determine which users can use your skill and will determine whether you can do WWA（Works With Alexa） certification. We strongly suggest that you select which languages your skill wants to support based on the sales country of your product, so as to avoid the situation that you cannot do WWA certification service or customers cannot search for skill or charging for adding languages. For example, you can select all Spanish languages if you want to sell your products in Spain. 16 languages English(US)/English(CA)/English(IN)/English(AU)/English(UK) German(DE) Italian(IT) French(CA)/French(FR) Spanish(ES)/Spanish(MX)/Spanish(US) Portuguese(BR) Japanese(JP) Hindi(IN) Arabic(SA) The option determines the countries and regions in which your customers can enable and use your custom skill. Your customers can access all skills that meet all of the following conditions: You distribute your skill in the customers' country or region. Your skill supports the language your customers selected for their Alexa-enabled devices. Your skill supports the primary language for the country or region in which the customers registered their devices. This support determines whether the skill is available in the skills store; for example: A skill must have an English (US) version to be available to customers who registered their devices with the .com site. A skill must have a German version to be available to customers who registered their devices with the .de site. Important: Customers can choose the language they want to use for their devices, and they aren't constrained by their location when choosing the language. For example, a customer that uses a .de account can choose to use a different language from German, such as English (UK), for their Alexa-enabled devices. However, changing the language doesn't affect the skills catalog available to the .de account in the skills store. Therefore, to make a skill.
Currently, Tuya has two solutions: 1. White balance: in order to correct the visual HSV mode, the RGB LED hardware differences caused 0 saturation, the actual visible to the naked eye is not white. 2. Gamma correction: To correct the hardware difference of RGB LED under each color grayscale.
Use either of the following methods: 1. Connect the socket to a PE cable to test functions. 2. Increase the distance between the high-voltage and low-voltage AC and DC power supplies.
The module will send the connection status to the MCU when the module is powered on or detects a connection status change. The MCU cannot send a command to obtain the module's connection status.
The Boolean type applies to variables that have a value donated either true or false, for example, an on/off switch. To enable a switch to have three states, you are advised to select the enum type.
The detailed application process is as follows: Step1 : The customer places an order in the service market and pays the order to fill in the information. Step 2: Tuya conducts audits based on the information submitted by the customer. When confirm that products have passed software testing we can move forward to next step. Step 3: The applicant sends samples to Tuya, and Tuya will conduct WWA testing after receiving the samples. Step 4: The Applicant sends samples to Tuya. After receiving the samples, Tuya conducts mass production testing and WWA testing. Step 5: Tuya arranges to test the product. If the test fails, Tuya will try its best to cooperate with you to fix the problem. Tuya submits a certification Application to Amazon after passing the test. Step 6: Apply for marking. According to the Application requirements, it can be divided into the following two cases: A. Marking the sales page: Amazon passed the review, and the page was awarded a certification mark to complete the certification. B. Marking for offline packaging: Tuya creates a product in the Amazon developer platform - apply for certification and generate a Project ID.2. Tuya emails customers and provides Project ID and WWA certification logo3. The customer sends the Project ID and packaging design draft to Amazon for review. After the review is passed, the certification is over, and the packaging can be printed.
Some module models will not be shipped with the adapter board. If you confirm that the optional module requires an adapter board, please provide PID information, module model and related pictures, and we will help you confirm whether the order is shipped The goods will match the adapter board.
You can use WirelessMon on a PC or the Wi-Fi analyzer on a mobile phone to scan the signals and analyze the signal strength.
Currently, you cannot check the number of API calls of a device. You can choose Data Device Statistics Functions Analysis to go to the Function page and check the usage count of data points.
Log in to Tuya IoT platform, and you can view device logs in Product-Device-Device Logs. You can use device ID to filter out the device logs within 7 days in a specific time period. If you need longer time device logs, please subscribe Logs Storage Service. For details, visit https://developer.tuya.com/en/docs/iot/log-storage?id=K9j6yqpfzwr3y.
We provide you with the following solutions: Find out whether there is a privacy agreement or service agreement page on your official website and provide us with the link to that page. Provide a document version of the privacy agreement and service agreement. Tuya can help you generate a link (the word Tuyacn will appear in the link), but the link will not be displayed when you open it on the mobile phone When you put the App on the shelf, you have generated a privacy agreement and service agreement, you can provide the link. If you have doubts about the content, you can contact the Tuya staff responsible for skill customization to send you a template of privacy agreement and service agreement. modify the company information in the document, you can generate your own agreement.
Transfer product means that you can let the specified account receive the product after completing the specified setting operation for the product under your name. After receiving the product successfully, your account will not see the product by default. Operating procedures: Please confirm whether the PID has a binding project. For the steps, please refer to: Cloud—Device—Associated Devices—Devices under Associated Products to find the corresponding PID, and click Unbind in the Operation column. If there is a bound item, you need to unbind it first; if it is not bound, you can directly refer to the following process to transfer by yourself. Operation Procedure: Product owner (hereinafter: factory) finds out product to be transferred to customer in the product list of Products - My Products. Click Manage Product link in the action bar, and select Transfer Product in the pop-up box. Review the notes in the pop-up box, enter the IoT console account to receive this product, and click Confirm and Generate Link button. Send the link of automatically copied transfer product to customer. Customer accesses this link after logging in with factory set receiving account, or access via customer's space authorized account, click receiving product, and the current product will be automatically transferred to customer's account name. Notes: Once the product is accepted, factory will lose ownership of the product and will not be able to view and manage data, device, and other information related to this product. Both the factory and factory space authorized account can operate transferring the product. Only when factory transfers the product and the designated receiving account set up by the factory can receive the product, other accounts accessing this link will be prompted with no authorization. If it is an OEM product, in order to ensure the integrity and accuracy of the OEM's upstream and downstream relationship data, the new account number cannot be the same as the account nu.
That means creating a product with the same configuration information as the current product into another account. Operating procedure: Product owner (hereinafter: factory) finds out product that he/she wants to share with customer in the product list of Tuya IoT Console - Product - My Product. Click Manage Product link in the action bar and select Copy Product to Other Account in the pop-up box. Click “Confirm” in the pop-up box to automatically copy the link. Send the link to customer, and after customer accessed this link and created the product, which is essentially the same as current product, it will appear under customer's name. By copying product created under customer's name, product configuration information will not contain the following information: The smart speaker access service needs to be re-applied, all the smart speaker services connected to current product will not be copied to new product. If the firmware of current product is custom firmware or the firmware uploaded by factory, the firmware information of new product is empty, you need to reset the firmware. Current product's multi-language name will not be brought to the new product by default, in order to avoid any inconsistency between the name seen by end-users after successful network configuration.
This topic describes how to subscribe to device control API products, and use API Explorer to check API calls and troubleshoot issues on theCloudpage of the Tuya IoT Platform. Prerequisites A sub-device is added to Tuya Edge Gateway (TEdge). For more information, seeManage Devices on Tuya Edge Gateway. Procedure ChooseAPI ProductsIndustry ProjectIndustrial General Device Control. For more information, seeManage API Products. Subscribed ProductsIndustrial General Device ControlAuthorized Projects (Authorize)New Authorization, and select your project in the dialog box that appears. Cloud&rt;API Explorerand send control commands. For more information, seeAPI Explorer. Send control commands with API Explorer. API ExplorerControl Devicedevice_iddevice_idSub-devicespage of Tuya Edge Gateway. commandsfield. The following code block shows the sample code: View device logs. Go to theLog querypage of the Tuya IoT Platform and enter the device ID to view device logs. View sub-device status. At the edge gateway, you can view the latest status of the sub-device for the edge gateway.
When the device enters the network configuration state, the network configuration status indicator of the device will flash.
Compare the current signal strength of the device with the receiving sensitivity indicated in the module manual. If it is close to the receiving sensitivity, the signal is very poor.
AWS Account Registration Website ↓ https://aws.amazon.com/ AWS Account Registration Tutorial↓ https://t.tuya.com/1D0dvMAN Notice：To register an AWS account, you need to bind a credit card that supports USD payments. If you don’t bind, the account will not be available.You may be concerned about whether you will incur charges, please check AWS FAQ for answers AWS Questions↓ https://support.tuya.com/en/help/_detail/Kayah4bb8lees After the information is provided, please visit Tuya's real-time communication tool: https://iot.tuya.com/im/ Our staff will contact you within 1 working day for the service.
When obtaining the weather service from the module, the geographic location (through latitude and longitude) where the mobile is located during the device pairing process will be firstly applied. When there is no longitude and latitude data, the location will be parsed through the device IP address.
The lamps of the group require the same dp point requirements of the panel, so that the group can be controlled.
a. Generally due to the module received production test signal less than -60db, it is recommended that the distance between the router and the light within 3 meters; b. It is recommended to increase the number of routers, so the router is set as the same production test SSID name. c. Try to power on as few lights as possible, eg., power on 50 lights at the same time, wait for a few seconds and then all 50 lights will enter into production test, then power on another 50 lights at the same time and operate in sequence;.
Yes,you can change the firmware name and panel name in the "Hardware Development" and "Device Interaction".
The following services are available in value-added service: App Service, Smart Voice Service, Certification Service, Smart Operation Service, Functional Expansion Service, IP Camera Service, Marketing Service, and Customization Service. For more details please see: https://www.tuya.com/vas/?from=smart.
Analysis: 1) The pwr under 'Sync'/'Config' status cannot be used; 2) The pwr under 'Invalid'/'Executed' status cannot be used; 3) the RTC drift too much. Suggestion: 1) Check if the pwr succeed in Syncing; 2) Check if the pwr is in 'Valid' or 'In use'; 3) Confirm if the MCU would conduct RTC calibration automatically.
Analysis: The record of unlock with online temporary reported by MCU missed some field. Suggestion: Please contact with Tuya Customer service if the Product integration meet standard.
Analysis: 1) Zigbee or Bluetooth LE lockers do not support to create online temporary pwr when devices offline. 2) The quantity of the valid online temporary pwr reached the limit of MCU definition. Suggestion: 1) Please ensure that the door lock is normally online controllable. 2) Please check the limit of the qty of valid online temporary pwr.
Analysis: 1) The network now stable, which impacts on the sync process; 2) The Wi-Fi locker is not triggered to sync the pwr manually. Suggestion: 1) Please make sure the network OK; 2) Please check if you have triggered the Wi-Fi locker to sycn pwr manually.
After replacing the UI panel on the platform, you need to restart the App to reload the device UI panel.
No, the device App panel will be automatically updated after the platform modification panel.
You can reconfigure the network; the usual way is to exit the control panel, and then pull down the App device list interface, the panel will be updated.
This is related to the performance of the router. Generally, the number of stable connections for home routers is less than 20.
Firmware uses https encrypted transmission, and adopt hmac or md5 verication.
Google services are restricted in China. After clearing apps, you will not be able to receive messages even if you have enabled FireBase Cloud Messaging (FCM).
The firmware has been released in the background, and there are fatal bugs (production problems, crashing problems, etc.) that need to be fixed. Only re-release the version, but the original firmware cannot be modified and can be upgraded via OTA.
SuitaBluetooth LE for electrician, lighting, sensor, large & small home appliances.
Replace the command `sudo npm install yarn -g` or refer to `Yarn official documentation: https://yarn.bootcss.com/docs/install/#windows-stable.
You need to switch the node version to about v10.15.0. Refer to detailed error information.
Report product DP point has a de-duplication filter by default. If the same DP point reports the same parameter many times, it will filter out the value behind by default, Repeated reporting can be enabled through Advanced Features.
Currently, spectrum adjustment solution requires MCU docking, and at the same time, the product operation interface of APP needs to be customized.
If you create a user through the SDK, you need to create a family first. If you create a user through openapi, Tuya Cloud will create a default home for this user. When logging in through the SDK, you also need to fill in the home_id in the SDK.
The dual-band refers to the 2.4G+5G of Wi-Fi, which belong to the different bands of the same protocol. At present, most of the home routers are the dual-band routers.
1、If it is a single production test product, you can repeat test1 production test. However, for products that support dual production test, it is not necessary to enter test1 production test after test1 production test is passed, so as to avoid device with normal test1 production test in the production process from repeatedly entering into production test process, which affects production efficiency; 2. In test1 production test routing environment, it is possible to conduct test1 production test process and complete network configuration test of test1 production test device at the same time, which eliminates the impact of production test route interference of APP network configuration; 3. Adding test2 production test route can support the device to enter into production test process repeatedly (such as product rework and other abnormal process).
Brand or pid changes require recertification. It is recommended that you re-authenticate.
Yes. Select null for the relay status indicator and select Indicate relay status for the network pairing indicator. Alternatively, select null for the network pairing indicator.
The current serial port processing mechanism of our module is based on serial port full-duplex, which can be simultaneously supported by the transceiver. If customer's module is simplex serial port, there maybe a packet loss problems.
MCU communicates with the module via serial port.
Analysis: 1. Multiple Bluetooth Low Energy devices are added to the current family. 2. The mobile phone is not close enough to the Bluetooth Low Energy device. Advice: 1. Control the number of Bluetooth Low Energy devices added to a family. 2. Check whether the device is close to the mobile phone.
Analysis: 1. The device has been connected to another mobile phone. 2. Bluetooth is not enabled on the mobile phone. 3. The distance between the device and the mobile phone exceeds the connection distance range. Advice: 1. Check whether the device is connected to another mobile phone. 2. Check whether Bluetooth is enabled on the mobile phone. 3. Check whether the distance between the device and the mobile phone is within the connection distance range.
The indicator flashes, indicating the network pairing mode. In other cases, the indicator indicates the relay status.
The same indicator is used as the Wi-Fi indicator and the power indicator. During network pairing, the indicator shows the network status preferentially. When the light is connected to or disconnected from the network or in low power mode, the indicator shows the relay status preferentially.
Distribution network: average 5mA, peak value 15mA; power consumption during network operation: 1-3mA; standby power consumption for distribution network: 200-250uA; offline control: 350uA.
R14 is a 1 mR (0.001 ohms), 2 W 2512 resistor. Because a high current flows through the resistor, the resistor is typically made of alloy. The small resistor is used for current sampling and must be connected.
Yes.
A Bluetooth node can provide access to only one mobile phone.
Analysis: 1) The RTC drifted to much (±5min); 2) Dynamic pwr only valid for 5mins. Suggestion: 1) Check if the MCU would conduct RTC calibration automatically; 2) Re-apply for the Dynamic Pwr.
A dynamic password is a temporary password that is calculated based on an algorithm that does not need a network. The app requests a door lock's dynamic password from the Tuya server over a third-party API. When the door lock receives a suspicious dynamic password, it sends the password to the Tuya Wi-Fi or Zigbee module with the current time and administrator password. The module then calculates the password based on the saved initial private key and compares the calculated password with the password that you enter. If they are the same, the module tells the MCU to open the door. If they are different, the module tells the MCU not to open the door.
The output of our module is PWM, firstly we need to provide a stable 3.3V power supply for the module, then connect the PWM of module output to the driver.
The driving principle of CCT and CW is different. CCT has two PWM driving pins, one driving brightness and the other driving color temperature. In the CW drive scheme, one pin drives cold light and the other pin drives warm light.
Please check whether the corresponding DP points are complete, DP20, DP21, DP25, DP28 are required functions. If they are missing, it will affect the generation of the App interface or cause incomplete data during communication.
The leftmost three GPIO ports on Tuya's lamp strip firmware and cold/warm CCT light strip can be used to connect to relays and act as physical switches. If you use the MCU solution, you can use the rightmost U0RXD and U0TXD ports.
Yes, but the network configuration mode of the firmware needs to be redefined to prevent getting into the network configuration through switching multiple times.
At present, Tuya already has a small number of dual-band modules that support 5G. For modules that only support the 2.4G band, the 2.4G routers must be used. Most routers on the market currently support the 2.4G and 5G dual-band. When the two bands of the router are separated to use, the phone needs to be connected to the 2.4G network, and then add the device. If the router is set to converge 2.4G and 5G, there will be a certain probability that the device addition will fail.
If you adopt a no-code solution, you cannot remove the all-on and all-off functions. If you use a custom solution, you can remove the all-on and all-off functions and customize data points.
A curtain control panel can be used only after you choose the Control, Motor Direction, and Fault Alarm DPs.
Currently, RDLC5 is restricted and cannot be changed at will.
Yes, if the device is triggered into the pairing mode by mistake, but no mobile configures with this device, it will be automatically connected to the former mobile phone which had been paired successfully before.
The selection of the module mainly based on the application scenario. First of all, considering the temperature, the temperature of Tuya module includes 85 degrees and 105 degrees. Generally, 105 degrees ones will be selected for bubble bulb, and 85 degrees ones for external drive. Secondly, considering the processing method and volume, the module has the processing method of vertical insertion and flat sticking. Besides, regarding the processing method of the antenna, the WIFI module includes an on-board antenna, an external IPEX antenna, a spring antenna, and so on. It is necessary to choose the module that fits the product structure.
Products embedded with Tuya modules generally need to be connected to Tuya Cloud to achieve intelligent control of devices through App. During this information transmission process, Tuya will ensure data security from two dimensions: 1. User device security: Tuya Cloud provides five-fold security policies to ensure the security of smart devices. 2. Corporate data security: Tuya Cloud isolates corporate data for corporate customers to ensure the security of customer data. At the same time, Tuya Cloud provides different data storage services for different business scenarios to encrypt and store part of the core data.
The Wi-Fi modules have high power consumption. It is recommended to use this power supply for the Bluetooth or the Zigbee devices. The module power of these protocols will be much lower, and you need to pay attention to select the module compatible with the package pin.
Tuya guarantees that your OEM skill can be built. However, whether the skills can be used after OEM depends on the device software and hardware. If any problem is found in the test phase, Tuya will make full efforts to fix it together with you. Amazon reviews skill launch. Tuya cannot control skill launch but will try the best to ensure successful launch of your skills. Generally, there is a small probability of failure.
Yes, Tuya's Wi-Fi camera supports photo taking. For details, visit https://developer.tuya.com/en/docs/iot/smart-product-solution/product-solution-lock/product-solution-lock-wifi/wifi-doorlock-develop-process?id=K9eta08zvx4j7#title-79-%E6%8B%8D%E7%85%A7%E9%94%81.
We leave four bytes is to make a reservation for the data width. If only one byte is used, a low byte can be used to make up the other zero.
If you want to maintain real-time performance, the RF part of the module must be turned on, waiting for data processing at any time. For example, the TYZS3 module has a power of 8mA in receiving mode, if it is always at 8mA consumption, it is fatal to battery-powered places. Therefore, keep the low power can only make the module enter deep sleep (below 10uA) and so turn off the radio.
The unstable network causes data reporting failure. Guidance suggestion: please check the network and try again.
After the uart communication is over, the Zigbee module will get into sleep mode after 100mS. The MCU need to pull low the wake-up pin 10mS before the next communication.
The data is transmitted through the sensor, MCU, chip, and cloud service in sequence.
Advice: 1. Passwords added locally to the lock. 2. Temporary passwords that are added in the app and are in the About to Expire or Effective state.
Production certificate called production Token, is used in the production process to limit the number of authorizations, verify the validity of the information, and complete the corresponding number of cloud authorization codes to write to the device when using the production tools provided by Tuya The basis used. The production certificate is divided into with firmware production certificate and independently authorized production certificate according to the authorization method of the host computer. The difference is that the latter has no firmware and chip information. The former is suitable for firmware that is developed based on Tuya standard chip, using the upper computer to execute firmware burning + device authorization; the latter is suitable for firmware not based on the Tuya standard chip development, and the upper computer is only used for authorization operations.
OEM Skill service can let you quickly builds and releases Smart Speaker Skills for your brand to help you showcase your brand and improve competitiveness. Support Skill: Smart Life, and customized skills (Note: For the smart speaker to control a device bound to an App, the device needs to be connected to the corresponding Skill. Tuya public Skills: Skills corresponding to Smart Life App in the smart speaker is Smart Life. Brand customization skills: After accessing smart speaker, if you want to use your OEM App to connect speakers, you need to OEM Skills. The skills will appear in the speaker kills list to spread your brand. Platform supports customized third-party speakers available on VAS: https://www.tuya.com/vas/?from=smart.
A technical ticket is a means by which you can send Tuya the problems you encounter during development or product use. Tuya's technical team will address your problems.
The development board (demoboard) is a circuit board used for embedded system development to assist the development tool.
A red, green, blue, and cold white (RGBC) lamp has adjustable light colors and brightness.
The number of scenes and automations that the user disabled during the statistical period (the number will only be counted at the end of the period).
RGBCW combines the initials of red, green, blue, cold white, and warm white. An RGBCW lamp has adjustable light colors, brightness, and color temperatures.
An RGB lamp has adjustable light colors. The red, green, and blue (RGB) color model is an industry standard color model in which the red light, green light, and blue light overlay in various ways to reproduce a broad array of colors. The model can reproduce almost all colors that human eye can perceive. It is one of the most widely used color models. Each of the red, green, and blue color channels has values of 0 to 255, indicating grayscale levels. An RGB system can have 16,777,216 (2563) possible colors. The RGB system is also called RGB24 (24-bit mode).
A cold-white (C) lamp produces white light with adjustable brightness.
The peripheral circuits introduced around ZigBee chip technology are called "ZigBee modules". Common ZigBee modules follow the international standard of IEEE802.15.4 and operate in the 2.4GHz frequency band. In addition, the European standard is 868MHZ, and North America is 915MHZ. Click to view all Zigbee module specifications of Tuya: https://developer.tuya.com/en/docs/iot/zigbee-module?id=Kaiuylhfmwnbs.
Amazon provides Works with Alexa (WWA) certification on products with the Alexa voice-based control function enabled, which is designed to ensure excellent performance of products in terms of reliability, response capability, and user experience.
Pulse width modulation (PWM) is an analog control method, which modulates the transistor base or MOSFET gate bias based on changes of the corresponding load to change the conduction time of the transistor or MOSFET and thereby to change output of the switch-mode constant-voltage power supply.
PWM2 is a PWM mode that applies to an STM32 timer. In up-counting, channel 1 is inactive as long as TIMx_CNT is less than TIMx_CCR1; otherwise it is active. In down-counting, channel 1 is active as long as TIMx_CNT is greater than TIMx_CCR1; otherwise it is inactive.
PTA is an arbitration mechanism to solve the interference between Zigbee and Wi-Fi at the same frequency, which requires the Wi-Fi chip to support PTA.
(Printed Circuit Board Assembly) is the board obtained after all printing solder paste on the PCB and then mounting various components like resistors, ICs (Integrated Circuits), capacitors and any other components like transformers depending on the application and desired characteristics of the board.
Stands for "Printed Circuit Board." A PCB is a thin board made of fiberglass, composite epoxy, or other laminate material. Conductive pathways are etched or "printed" onto board, connecting different components on the PCB, such as transistors, resistors, and integrated circuits.
Tuya Platform provides a large number ofsmartsolutions for products, and it also provides the ability to customize smart Appfor brands - OEM App. OEM App can help you: lZero code, you can build your brand-specific IoTApp in 10 mins; lOne App controls 2000+ categories of smart devices,with powerfulsmart scenarios and functional linkages; lAccumulate brand users, manageuser data, operate accurately and accelerate shipment growth.
Fully hosted app launch service helps you enable the app message push function and create content for launch, reducing your app launch time.
FireBase Cloud Messaging (FCM) is a push service and channel that Google has officially launched. It is capable of system-level push outside China.
CBU is a low power embedded Wi-Fi module developed by Tuya Smart. It is composed of a highly integrated radio-frequency identification (RFID) chip BK7231N and a few peripheral components and supports dual connection of AP and STA as well as BLE connection. For more details, please see:https://developer.tuya.com/en/docs/iot/cbu-module?id=Ka8uv3u1q1xxc.
The mcu_start_wifitest() function is invoked only once.
Before mass production of customer products, the calibration parameters in the firmware need to be adjusted according to the hardware circuit parameters. After adjusting the parameters, in the production test before the product leaves the factory, it automatically performs hardware calibration for each product.
The router signal in production test environment is lower than -60dBm.
The network configuration package will continue to be sent for 2 minutes since the start of network connecting. If you don't click to complete it, the mobile App will still send the network configuration package.
Tuya products are developed weekly. The overall completion cycle of a project depends on the development duration of the customer's hardware product. Generally, the SOC mass production is completed within one week, and the MCU mass production is completed within two weeks.
Each product has a corresponding production test program, which can verify the module network performance and product hardware function. Generally, the production test is performed before the product leaves the factory to ensure the normal function of the product. As the production test operation steps are different for each product, please follow the production test document of the corresponding product for specific production test.
Yes, you can change the panel for a developed product. You can change a panel regardless of whether a product is developed or not. However, a panel takes effect immediately after it is released, which will affect the user experience. If a product has already been used by end users, release a panel after testing and acceptance to avoid affecting the user experience.
Advantages: simple scheme, simple peripheral parameters, and low cost. Only two signals, DAT and CLK, are required for control. Disadvantages: linear constant current drive, DAT and CLK signals are easily disturbed.
The cloud assistant is to simulate the communication between the module and the MCU. It mainly depends on whether the MCU can correctly interact with the module. It does not support networking.
It's the test points for the module production.
Analysis: some IPCs are set not to receive continuous rotate order Instruction: check with the supplier if the IPC supports continuous rotation.
If the server time is used, the report will be stored after offline, and the time data will all be the current time of the report. The data will not be recorded accurately.
Sharers can only view their own records. After upgrading to family members, they can view all family records.
It may be that the power accumulation function is not activated, please contact the server to activate the power accumulation function. It may be that the power DP point in the App panel is inconsistent with the actual power DP point of the product. It may be that the accumulated time and accumulated power are too small, and the report has not been triggered yet. Generally, after waiting for 30 minutes, you can see the power data.
Analysis: Firmware of the device does not support the OTA function. Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
There are four possible causes for a message delay: 1. The network conditions are poor or you are far away from the server, for example, you are in a different country or region from the server. 2. The third-party vendor channel is used to push messages in China and FireBase Cloud Messaging (FCM) is used outside China. The time for transmitting a message from the server to your client depends on the load on the third-party server. During congested peak hours, message arrival may be delayed. 3. You are not an active user. Messages pushed to active users who use the app frequently have higher priority, with faster arrival and transmission rates (earlier arrival), than inactive users. 4. Your connection with the push server is abnormal. If your mobile phone is disconnected from the server, you cannot receive push messages. The disconnection can be detected only when the next heartbeat packet is sent, and the message arrival is delayed.
The platform will no longer support the sub-account operation. Please upgrade the sub-account and replace it with a new authorized account.
To see if DP44 is checked or not, checked DP44 means the device supports local RTC, can accurately record the time of opening the door. So this permission is authorized to sharing users; If unchecked, for security reason, only Bluetooth opening door permission provided.
The cloud will send the weather data to the module after connecting to the network and sending the command for the weather data obtaining.
Hello, the reason for this problem is due to some compatibility issues. Please use Postman to make API requests. The Cloud Development Platform allows you to use Postman to make API requests. For example, Postman can be used to get device information or control devices. For information about development environment setup, see Set up Postman environment.
Because the MCU needs to request temporary password instructions of the cloud.
The expiration time is exceeded, or the APP is deleted and the device will be sent in the deleted state.
When the Wi-Fi metering socket is powered on and scans to the production test route signal value below -60dB, the Wi-Fi indicator will flash as an indicator, so please check the weak source test route signal source around the socket, and then close the production test route That's it.
In order to filter out the modules with too weak signal.
The MCU can query the signal strength of the NB module through commands. If the signal strength is less than 10, it means that the signal strength is very poor, and there is a possibility that it cannot connect to the operator's base station. Please check whether the SIM card is activated, whether NB business is handled, whether exceeds the package limitation, and whether the installation is proper. The signal strength is related to the antenna performance of the equipment end covered by the base station. If the signal strength is poor, please make sure the antenna is well matched and the contact is proper.
After the module setting the temporary password, the MCU sends multiple sets of the requests-the APP side will show that it has been sent--- but it cannot be deleted-the module needs to send a request for multiple sets of the temporary passwords to notify the APP side. What is the temporary password for Wi-Fi door lock to be deleted? Why can't the temporary password be deleted after invalidation?
Check whether the DP point data has been modified. If there is any modification, please download the JSON file again.
No, the App panel of the two-way switch and the one-way switch module are different.
GPIO5 and GPIO13 are used for cold light and warm light control, respectively. The PWM pins' duty cycle can be adjusted for brightness control.
Analysis: 1) If the pwr was not used in 24hours after being generated, it would become invalid; 2) The pwr expired; 3) The pwr is been cleared; 4) The RTC drift too much (i.e. remove mins, only keep hours, not sync with cloud). Suggestion: 1) Please use the pwr at least one time in 24 hours; 2) Check if the pwr is expired; 3) Check if the pwr is been cleared; 4) Check if the MCU would conduct RTC calibration automatically.
Check whether parameters such as I/O ports and effective level are configured correctly. Use a demo board to program the problematic firmware to check whether corresponding I/O ports have PWM output: If yes, find other causes. If no, contact the firmware developer to rectify the fault.
The smart lamp products are generally reset by switched on and off three times. If the user has switched on and off twice before, and has powered on again for 3 reset times, the light will enter the fast flashing mode. The accumulation may be due to user misoperation, and the power grid is powered off within 5s of power-on. In actual use, care should be taken to avoid the operation of powering off too quickly after power-on.
To ensure the efficiency of the servers and the rational use of resources, the same data will be filtered out on the module side. If you have special needs, please contact Tuya staff to set no filtering.
Upper and lower bridge arm interconnect damaged power tube.
No requirement, any of the followings are possible: No encryption WEP WPA/WPA2 WPA-PSK/WPA-PSK2.
Analysis: 1) If the pwr was not used in 6hours after being generated, it would become invalid; 2) The pwr expired after used; 3) The RTC drift too much (i.e. remove mins, only keep hours, not sync with cloud). Suggestion: 1) Please use the pwr in 6 hours; 2) Check if the pwr is used; 3) Check if the MCU would conduct RTC calibration automatically.
Determined by the performance of the mobile phone, it is basically about 3-7.
The operation center aims to provide customers operation management tools required in various scenarios, to solve a series of problems of the App, and to enhance device management capabilities and marketing hotspots. The operation center also provides content including pushing messages to App users, pushing splash screens, processing user feedback, and setting alarm information, to solve the notification mechanism required for operations, collect user feedback online, and provide support for targeted products.
Indoor is 10~30m, open outdoor is 150m+.
Expensive, depending on a gateway for control, and low transmission rate.
Z-Wave is a wireless networking specification dominated by the Danish company Zensys. Z-Wave is an emerging short-range wireless communication technology based on radio frequency, low cost, low power consumption, high reliability and suitable for networks. The working frequency band is 908.42MHz, and the effective coverage of the 868.42MHz signal is 30m indoors and more than 100m outdoor, which is suitable for narrow bandwidth applications. Z-Wave technology is also a low-power and low-cost technology that strongly promotes low-rate wireless personal area networks.
The current of Zigbee products after sleep is about 5ua.
Zigbee uses 3 frequency bands: 868MHz (Europe) 915MHz (United States) 2.4GHz (Global).
After being awakened, the maximum duration is valid for 500ms, and it continues to sleep immediately after receiving the data.
After the Zigbee door lock is equipped with a network, if the Zigbee network is reliable and the connection between the Zigbee gateway and the server is stable, the Zigbee door lock will always be online. If the app (server) wants to send instructions to the door lock in the online state, the normal time is 5s. The internal door lock will be received. If the network status is not good, there will be a certain delay (not more than 30s). If it cannot be sent to the hardware after more than 30s, the transmission fails; when the Zigbee gateway is suddenly offline (power off, network off), the Zigbee door The lock will immediately go offline, and if the gateway comes back online, the Zigbee door lock will immediately return to the Internet; if the Zigbee door lock itself disconnects from the network (the door lock is powered off, or the network is disconnected due to a bad signal), the app is the most The door lock will display offline for less than 5 minutes. If the door lock is replaced with a battery or a door opening operation is performed, if the network is reliable, the door lock will immediately resume networking.
Low-power (battery) Ad hoc network (coordinator, router, and terminal) longer communications (15 to 30 m) Secure (internal encryption).
TYZS3. TYZS5 are commonly used modules in the door lock category.
Response timeout is 20ms.
Module radio frequency wakes up once every 5s, duration 8ms, within this time to deal with whether there is a temporary password, remote door opening and other commands issued.
Up to 30 groups.
Serial port wake-up firmware means that the module wakes up the MCU by sending a wake-up command through the serial port; GPIO wake-up firmware means that the module will output a low-level signal through the GPIO port to wake up the MCU before sending serial port data.
This is normal, the module will check every 5s whether the gateway has data to send.
No more than 50 data requests at a time.
PWM1 on the module is effective when pulled low for 10ms. After the serial communication is completed, the 100mS module goes to sleep again.
In microseconds.
Note that the general firmware from version 1.1.2: parameter 00 is reset, 01 is off network and reconfigure. Before 1.1.2, 00 is off network (not in network configuration status), 01 is off network and reconfigure.
No, the module does not recognize other parameter values and will filter out.
The main disadvantages are as follows: 1. High price; 2. Control depends on gateway; 3. Low transmission rate.
If the PID and firmware versions are the same, and the module phase has been programmed, the J-Link and programmed authorization can be ignored; However, a hardware reset test should be added to the test sequence.
Sorry, it is not support.
A strong-powered device such as Door Lock:3mins once, offline timeout 10 mins. Low-power-consumption device: 4hs once, offline timeout 12hs. It will be maintained between the gateway and the device together.
Recommended Zigbee devices be placed within 1 meter of the beacon.
When the Zigbee's MCU is connected to the product, the module will send a 0B command to the MCU when it is connected to the network. The MCU should respond to this command at this time, and it will be displayed correctly after the reply.
Compared with the standard firmware, the low-power firmware adds a wake-up function. And two pins should be added to the circuit for the connection. The PWM1 is used for the Zigbee to wake up the MCU, and the pwm2 is used for the MCU to wake up the Zigbee.
The low power of the bidirectional communication of the Zigbee is: 250uA/250ms.
Check whether the power statistics function is enabled; Zigbee power statistics socket power statistics choose minux type, do not choose sum type.
The Zigbee power statistics socket needs to be displayed on the Internet only after the production test is completed.
Normal use of 210mAh can last more than one year.
The modulation method is OQPSK.
Yes.
Low power sleep current is 3uA. Normal working current is 5mA. Transmitting/receiving instantaneous 30mA+. Different schemes have different currents, see Datasheet for details: https://developer.tuya.com/en/docs/iot/zigbee-module?id=Kaiuylhfmwnbs.
As a replacement to the existing wired control mode, Zigbee modules eliminate the need for cabling, extend the control distance, and support association between devices on a network. Currently, Zigbee modules have been applied to the industrial, agricultural, and petrochemical engineering fields, the Internet of Things, Smart Home, Smart Lighting, and Smart City.
TYZS3, TYZS5, and TYZS7 can all have external antennas.
The advantages of Zigbee modules are Low power consumption, strong penetration, and large number of connected devices.
PWM1, the default is high level, low level is valid for more than 10ms.
Network connection states include: 1. not connected (0x00) The device is powered on for the first time. Network pairing fails. The device disconnects from the network. The device is restored to factory settings or the module is set to the pending network pairing state Remove the device from the App 2. connected (0x01): A Zigbee module reports 0x01 when the device is connected to a network 3. abnormal network connection (0x02): when the module does not obtain the PID but receives a network pairing command. 4. The status of the network to be configured(0x03).
General solution will not automatically connected to the network.
Store locally on device.
Zigbee smart door locks mainly apply to business markets, hotels, real estates, and long- and short-term rental apartments. Zigbee smart door locks are seldom used at homes.
The total length of a Zigbee packet is 128 bytes, but only 64 bytes can be used for user data. That is, the data length in a serial port frame cannot exceed 64 bytes.
Yes, strong-powered Zigbee devices have routing functions.
Yes. You can set it on the Hardware Commission page.
The serial number sent by the command is N, and the serial number returned by the MCU is also N. The subsequent serial number which is reported actively by MCU is N+1, and the module responds with the same serial number after receiving it. This is mainly for the reliable transmission.
It is recommended that Zigbee send and receive the same serial number for the same set of data.
3 minutes for high power firmware, 4 hours for low power firmware.
Yes, Zigbee standard scene is directly assigning group ID or scene ID when binding the scene, and the Zigbee protocol can directly trigger the corresponding device action.
Each button supports two functions: long press to switch distribution network, multiplex scene operation & long press to reset.
Zigbee local scene, when going multicast, creation and association are successful, there is a concept of scene ID group ID, the scene switch corresponding button and the execution device are assigned ID numbers, the scene switch and the execution device are mapped by this ID, The device local exists, and when the scene is executed, the scene switch multicast is sent out. (If the network is disconnected, the local scene can be executed, provided that the addition and verification are successful).
Reset long press time default 5s.
There are more than 60,000 in theory, 200~500 in general.
Yes. On the Hardware Commission page, set the GPIO output pin of the relay to high-level drive.
Yes. On the Hardware Commission page, select a module and click Configure Firmware. In the dialog box that is displayed, set Reset times/s and click OK.
The connection distance between Zigbee single fire switch and gateway is 100 meters outdoors and 30 meters indoors.
A single Zigbee device simultaneously supports up to 56 scenes and groups in total.
The serial number module actively sends data, what response is received by the MCU, and the data sent actively by the MCU can be sent out after +1 on the original basis.
This field can be replied according to the corresponding value issued by the module without special requirements. Door lock products need more attention to report the serial number as required.
Zigbee supports a variety of network topologies, such as point-to-point, point-to-multipoint and self-mesh. The low duty cycle capability provides the possibility of a long battery power supply. It has low latency. It uses DSSS spread spectrum technology. Each network can support up to 65,000 nodes. 128-bit AES encryption collision avoidance, retry and response confirmation are based on the IEEE 802.15.4 standard, and the working frequency is 2.4 GHz (global used frequency).
Yes.
The heartbeat time is 4 hours a time, and the offline timeout period is 12 hours.
The reason is that the Zigbee device is not authorized for burning, and only burns the application firmware, then it will work normally within 7 days, and it will not work normally after 7 days.
The Zigbee production test beacon needs to be placed within a distance of 1.5 meters due to power attenuation, in order to ensure normal operation.
The status of the Zigbee network can be judged according to the command word 02. The status change of the module will be issued actively, so the MCU should display different indicator statuses according to different statuses. You can also connect the TX of the module to the USB-to-serial port. issued order.
Temporary passwords are valid during a specific period of time. After you create a temporary password for a door lock in the app, the server sends the password to the door lock, which stores the password and validity period. After the information is saved, the temporary password is valid during this period unless the door lock receives an instruction to delete or modify the password. Network connection is the basis for password creation, deletion, and modification.
The theoretical value is 0x1E.
It can be exported, the source data is exported, and the TXT text in the production test software folder under the path: C:\Users\Nick\AppData\Roaming;.
Yes. On the Hardware Commission page, select a module and click Configure Firmware. In the dialog box that is displayed, set Default power state and click OK.
Amazon itself does not charge for WWA certification, but if you Apply for WWA through Amazon yourself, a testing fee will be charged by Amazon's testing supplier, the US UL agency. To Apply through the fast track of Tuya, you only need to pay the service fee for Applying on behalf. The specific cost must be assessed based on the Application form. 1. Service price：Electrical （curtains excluded）,Lighting,Diffusers,IPCs( video doorbells excluded) $ 1,250 (USD)；Robot Vacuum $ 2,500 (USD)；Fans, Air Purifiers, Humidifiers, Dehumidifiers $ 2,700 (USD)；Thermostats, Heaters $ 3,200 (USD)；Includes certification fees for five Amazon sales pages. The number of packaging materials for printing WWA logo is unlimited. Note: A brand corresponding to a PID is a product, and different brands or PIDs are regarded as different products. 2. If there are more than five Amazon Standard Identification Numbers (ASIN), new ASIN will be charged according to the following standards: $75 for one. If you have an SDK-developed app, it needs to be quoted because Tuya needs to test the app separately. The quotation standard will be evaluated by your Tuya project manager. 3.Subscribe to this service to obtain the WWA certificate, gain the "Works with Alexa" logo on specified product packages and sales page. The WWA logo can be printed only on the packages of WWA-certified products. Please be aware that printing the WWA logo on the packages of products that have not passed the WWA certification constitutes an infringement. 4. You can apply for the WWA testing and certification application service only for products that have passed the software test. please contact the factory to complete it. But software testing is not covered by the WWA certification service. Therefore, the WWA certification is completed within 12 workdays of the software test being passed.
Note that the software passing the product test is a serious prerequisite for applying for WWA. If your product has completed the software test, we can directly arrange the WWA voice test for you, and the test result will be available in about 10 days. If your product has not completed the software test, please complete the product software test first and provide the test report.
No, product testing does not require disassembly of samples.
A) WWA certification fee: According to the quotation of the certified category（If it is a Tuya fast certification category, it will not be quoted according to the region, if it is a non-quick certification category, it will be quoted according to the region）, please refer to the introduction of the service page for details.(brand, PID has any different, are considered to be different products) contains 5 sales pages. If you have less than 5 applications, you can increase the number to 5 free of charge. More than 5, according to the number of additional charges. B) the amazon sales page charge standard is 750 yuan / 125 dollars per sales page.
Sending one by one.
Advice: On a Wi-Fi lock, you can press the lock buttons to initiate a remote unlocking request and then check and handle the request in the app.
The door lock does not report an instruction to close the remote door opening, and the countdown to report the remote door opening request is 0.
Wi-Fi modules and finished product testing.
The main disadvantages are as follows: 1. The deployment location is limited by the router; 2. Large power consumption; 3. The number of sub-devices is limited.
The main advantages are as follows: 1. High transmission rate; 2. No need for gateway; 3. High market acceptance.
Yes. You can set the indicator on the Hardware Commission page.
The external antenna for the door lock can use TYWE1S-IPEX: TYWE1S external antenna version, the signal is good.
DPID9,10,11.
When the App panel is initialized, the remote door opening interface is hidden. Only when the door lock first triggers the request for remote door opening, the App panel will display the operable interface.
Article 20.
The networking distance is about 10 meters.
Countdown to remote door opening is recommended for 90 seconds.
After the MCU needs to actively issue the network distribution command (03/04 command word), the module will exit low power consumption and enter the network distribution state.
Wi-Fi door lock supports all kinds of door opening methods and time record display.
Confirm whether the mobile phone network is connected normally, and try to refresh the page. Product information does not match the power consumption type, and you need to select a low-power device. In principle, Wi-Fi door locks are low-power devices, and there is no offline situation (online/offline status is not displayed on the App).
Wi-Fi door lock 05 command word report should pay attention to: The status data will be reported directly to the cloud, MCU must wait for the module network status to be connected to the cloud, and then report the data, otherwise the data report fails. This command is a synchronous command. After the MCU data is reported, it needs to wait for the module to return the report result. The waiting timeout time can be set to 5 seconds. Multiple data unit reporting and single data unit reporting can be supported here, and users can choose the way to send group packets according to their needs.
The MCU sends the 07 command word. After the module receives the production test command, it will automatically scan the name tuya_mdev_test Wi-Fi signal and return the scan result and the signal strength percentage.
Analysis: The time of MCU requesting for online temporary pwr from cloud is too short. Suggestion: Please contact with Tuya Customer service if the Product integration meet standard.
The 01 command word is the product information query instruction of the door lock protocol, and the MCU needs to reply the correct product information for initialization.
Wi-Fi door lock protocol 05 command word format: MCU send: 55 aa 00 05 N N DATA1 checksum. DATA1: See DP data unit. The module returns: 55 aa 00 05 00 01 DATA2 checksum DATA2:0x00 success/0x01 failure.
The 03 command word switches the distribution network mode back and forth, and the 04 command word specifies to enter a distribution network mode.
In order to save space, when the embedded is issued, it is issued in the x-900 mode. So when the door lock is reported, the name of the password to open the door must be displayed, and the number +900 needs to be reported.
It means that the password is valid and has been sent to the device.
Wi-Fi door lock serial port protocol version number format is in dotted decimal format, "x.x.x" (0=x=99), x is a decimal number.
The serial port will output a series of garbled characters when power is turned on. This is normal. These data are not framed and will have no effect; when the module is restarted, these garbled information will be printed, such as: power on restart, distribution network restart, etc.
It is recommended to wait for a maximum of 8s. This problem involves the trade-off between the success rate and power consumption of the network. Premature power failure will affect the success rate of the network, and late power failure will affect the power consumption.
Please check the documentation: https://developer.tuya.com/en/docs/iot/wifi-general-production-test-documentation?id=K9hhi0xucqxhf.
You can get both local time and Green time.
The MUC is powered on for the first time and the subsequent heartbeat commands are different.
No, it will not be issued.
Combination Report Description Combination report is used for multiple dp points to report together. Data format 55 AA +03+07+total data length+N (data id | data type | data length | data value) + verification Combination report requires the user create a function in the SDK, fill in the data content of the above example, and then call it where it needs to be reported. After the filling is completed, the debug joint reporting function can use the assistant combination report to verify the correctness of your data.
The distance between device and the router is 3 meters, the signal strength of -60 is the minimum standard, and the signal strength below -60 is a defective product.
The module will reply with network configuration instructions and Wi-Fi status protocol data.
When the MCU does not have extra IO ports for connecting the network buttons and indicator lights, use the self-processing mode, and connect the network buttons and indicator lights to the module.
04 The reset distribution network command can make the module cycle in the EZ and AP network distribution states, and the 05 configuration network selection command can directly specify the distribution network state.
This refers to the time corresponding to the time zone when the device is activated.
You can view the distinction of the firmware name through the module Log print port. The general firmware protocol has a heartbeat command frame, and the low power general firmware does not. The low power device that has been configured with the network, whose speed of power-on and network access is significantly faster than the speed of the general firmware. There is no module self-processing mode in the low power firmware.
After offline, the timer can not issue commands normally after the time expired, it must be online.
The number "x" after SmartLife_xxxx represents the last four digits of the device's MAC address.
There is -60dB signal limit.
The general Wi-Fi network structure is star shape.
Up to 30 schedules can be added.
Low power of Wi-Fi bi-directional communication is 13mA.
a. Production test module will only scan the router's SSID name after power on, no need to connect the router, and the router does not need connect to the network; b. the best for the router placed within 3 meters from the light, if many lights need to do production test at the same time, it is recommended to place a few more routers in the light attachment, because the module received test1 and test2 signal is less than -60db, and can not enter the production test; c. The number of lights powered on at the same time during the production test is as few as possible. For example, power on 50 lights at the same time, wait a few seconds after the 50 lights are in the production test, then power on another 50 lights at the same time. Because the number of channels on the router is limited, there is an upper limit to the number of SSIDs that can be scanned on the router at the same time. d. Currently, SOC firmware is divided into two phases: test1 and test2, test1 can only be entered once, and cannot be entered again after test1 process is over. Test 2 can be entered only after test1 ended, and test2 can be re-entered. Some custom firmware or previous old firmware only has test1, these test1 firmware can be re-entered.
The power supply of the Wi-Fi module is controlled by an MCU. When you want the sensor to report temperature and humidity values, turn on the Wi-Fi power supply. The sensor then reports the temperature and humidity value changes at the scheduled time. If the temperature and humidity values obtained are the same as those obtained last time, the Wi-Fi module does not report the values.
Yes. The protocol in the latest version allows the MCU to proactively obtain the network status. For details about the firmware version, contact related personnel. However, command word 03 can only be sent by the Wi-Fi module when the network status is changed.
256 bytes.
The standby power consumption of different Wi-Fi modules is different. It is recommended that you refer to the data in the "Working Current" section of the module's data sheet.
A Wi-Fi module may have 12, 16, or 18 pins, depending on module packaging.
The peak current differs from the model of the modules. It is recommended to refer to the datasheet of the modules.
The time interval for the Wi-Fi module to query the weather requires the weather macro definition to be turned on first. The first query command in the cloud is issued immediately, and will be issued every half an hour later, and will not be read all the time.
Command word 01 is used to query product information.
If it is a general firmware module, the Wi-Fi module will send a heartbeat packet command when it is powered on.
If you do not check the duplicate report，in order to reduce the pressure on the server, the same data will be filtered.
No.
The Wi-Fi module, MCU docked product, has a data interval of typically 50ms per frame.
There are two general connecting methods for the Wi-Fi module: 1. Module self-processing: The indicator lights and network configuration buttons are led out from the module, and the network configuration indicator processing is handled by the module software. In addition, wiring only needs to connect the serial port to the MCU; 2. The module matches with MCU: The module is only connected to the serial port of the MCU, and other network configuration buttons and indicators are completed by the MCU, and the network configuration logic is also determined by the MCU. The initialization module must report and reply to the working mode.
EZ mode: 1. Connect your mobile phone to a Wi-Fi network, open the app, and tap the plus sign (+) in the upper right corner. Enter the Wi-Fi password to request the network pairing token. 2. Initialize the hardware device and ensure that the Wi-Fi indicator blinks quickly. 3. Enable the mobile phone to send the SSID, password, or token in broadcast or multicast mode. 4. The hardware device obtains the SSID, password, or token in the configuration information based on the UDP packet length in broadcast mode and IP address in multicast mode, and the Wi-Fi indicator is off. Connect the hardware device to the router. After successful connection, the Wi-Fi indicator is on. Send the token and register with the server. After successful registration, log in to the MQTT server. 5. Based on the token, the mobile phone searches for the device on the server and returns the device information. AP mode: 1. Connect your mobile phone to a Wi-Fi network, open the app, and tap the plus sign (+) in the upper right corner. Enter the Wi-Fi password to request the network pairing token. 2. Initialize the hardware device, enable it to enter the AP mode, and ensure that the Wi-Fi indicator blinks slowly. 3. Connect the mobile phone to the hardware device's hotspot (SSID). After successful connection, use UDP packets to send the AES-encrypted SSID, password, or token. 4. After the device obtains configuration information in the UDP packets, connect the device to the Wi-Fi network and disconnect its hotspot. Send the token, register with the server, and log in to the MQTT server. 5. Connect the mobile phone to the Wi-Fi network and search for the device on the server based on the token. 6. The server returns the device information.
If the offline time is within the OTA timeout period, and then go online after offline, the upload will be resumed and the upgrade will continue. If the offline time exceeds the OTA timeout period, the app will display that the upgrade failed.
The frequency band of a Wi-Fi module is subject to that set for the router, which can be 20 MHz or 40 MHz. If 40 MHz is set for the router, the frequency band of the Wi-Fi module is 40 MHz. If no frequency band is set for the router, the frequency band of the Wi-Fi module may be 20 MHz or 40 MHz.
The default display port of ESP8266 or ESP8285 is I/O2, which can be switched to I/O1, and the baud rate is 74880. The default display port of Realtek is log_TXD and the baud rate is 115200.
Our module supports 2.412GHz-2.484GHz, but 2.484GHz is 14 channels, which is not commonly used except in special areas, general speaking is 2.412GHz-2.472GHz.
Yes, for low-power modules with external IPEX antennas, the WBRU-IPEX module is recommended.
Unused IO ports or IO ports that are not configured on the platform. If there is no special requirement, they can be left open.
Around 30-40mA.
The heartbeat packet returned by MCU after restarting is 55 aa 03 00 00 01 00 03.
No.
By default, Tuya Wi-Fi modules work in channels 1 through 14 in all countries. If you want to specify available channels for your product, contact Tuya personnel and tell them your product sales regions. The channels can be specified by changing the firmware settings.
Yes.
Tuya Wi-Fi modules support the WPA and WPA2 security modes，partial support for WPA3.
Our Wi-Fi module supports 1-14 channels, but 14 channels are not commonly used and only used in very few countries.
A Wi-Fi socket can upload data to the cloud and deliver data to the app.
3-3.6V.
Note that the output voltage ripple of 3.3V is less than 100mV, and the DC/DC has the ability to output the current 200mA. And when the output current is 450mA under the dynamic conditions, the output voltage drop does not exceed 2.8V. The LDO supplies power to the Wi-Fi module. If you use LDO, you need to use a chip with a power supply current of more than 500mA, and pay attention to the heat dissipation. It is recommended to use a switching power supply chip when the input voltage is higher than 5V.
There is no uniform standard for judging the strength of RSSI signal strength. According to empirical values, we generally believe that -20~-60dBm is considered a strong signal, -60~-80dBm is considered a medium signal, and less than -80dBm is considered a weak signal.
1117 is generally used.
A Wi-Fi module sends data frames at intervals of about 50 ms.
High level.
Tuya Wi-Fi module has an output driving capacity of 12~16MA for each IO port. There will be some differences between different Wi-Fi modules, but it is greater than 10MA.
How many modules the Wi-Fi can carry at most depended on the router it is connected to. It can carry 30 for enterprise level, and up to 20 for home.
First of all, it is necessary to determine whether the device is reported incrementally or in full. If it is reported incrementally, the power can be obtained in a cumulative form, and the device status value can be obtained with the full amount of power.
Generally, there are two situations, one is to send to the production test immediately after initialization, and the other is that the network condition is poor.
If the indicator keeps blinking quickly Please confirm the Wi-Fi frequency band supported by the module first. If it only supports 2.4G, please confirm whether the router hotspot is 2.4G. Then try again or restart the Wi-Fi module to try. If it still fails, please inform the technical support personnel of the router model and mobile phone model. If the indicator blinks quickly and then becomes steady off Check whether the Wi-Fi connected to the mobile phone can access the external network, and check whether the Wi-Fi name and password entered during network configuration are correct. After confirmation, please remove the device and try again. If the indicator blinks quickly, turns off, and finally becomes steady on Please remove it and re-configure the network test. If the network configuration is still not successful, please contact Tuya staff.
The platform is continuously optimized, you can refer to the scope in the specification：https://developer.tuya.com/en/docs/iot/cbu-module-datasheet?id=Ka07pykl5dk4u.
A Wi-Fi switch with an indicator requires three I/O interfaces for each gang, and a maximum of three gangs are supported.
Send heartbeats periodically at 15s intervals.
No. A Wi-Fi scene switch executes scenes on the cloud.
Long press any button to enter the distribution network.
10S by default, free to configure long press time.
The heartbeat design is used for module to detect whether any problem with MCU serial communication and whether the handshake status has been maintained.
Users who use the official website MCU_SDK for development, only need to download the latest SDK compression package, and replace the original project file and re-transplant. Users who directly connect to the protocol: 1) In the sending frame format, the third byte "version" data is changed to 0x03 2) The command word 0X02 is to query product information, and the reply content format needs to be changed. For details, please refer to the protocol document example. 3) The command word 0X03 is the device networking status, and two statuses will be added. If you write the fixed check value directly, please note that the check value changes due to the version change.
The 02 command is actively sent by the module, which will send the status to the MCU actively when the network status changes.
You can pull the antenna out temporarily or put the module on the surface.
a. Please make sure that the test 1 production test process has been completed. It may need to be verified by turning on the test 1 router. Only test 1 production test process aging is finished that you can enter the test 2 production test. b. Please be sure that the product is not connected to the App. You can repair this device, and then remove the device from the App. After removing the device, the light will be flashing rapidly, let the lighting flashes for more than 10 seconds, and then turn off and on again. c. Please ensure that the test 2 signal strength received by the module is stronger than -60db, which can be verified by changing the distance between the lamp and the router. d. It is necessary to determine whether the module firmware has a customized production test process and to determine whether it is a dual-channel production test firmware, you can confirm this part with the relevant personnel from Tuya.
a. Please make sure that the name of the router has been changed to tuya_mdev_test1, the letter case and underscore have to be the same. b. Please be sure that the signal strength of the module received by the router is higher than -60db, make the module and the router are as close as possible, and the antenna part of the module cannot be shielded by metal. c. Please ensure that the test 1 production testing process of this module has not been completed before, you can turn on the test 2 production test router to verify. If this light can enter the test 2 production testing process, it means that the test 1 process of this module has been finished. d. Please confirm that the product is not connected to the App. You can repair this device, and then remove the device from the App. After removing the device, the light will be flashing rapidly, let the lighting flashes for more than 10 seconds, and then turn off and on again. e. If you still cannot enter the test 1 production test, you need to determine whether the firmware has a customized production test firmware. The method to enter the production test process may be customized. In this case, you can communicate with the relevant personnel from Tuya.
Temporary passwords are created by the app and saved on the server. The door lock will update the temporary password list on the server using specific logic.
The fourth byte of the Wi-Fi serial protocol is the command byte, indicating the function description of the current protocol.
The third byte of the Wi-Fi serial protocol represents the version, which is the identification of the serial port protocol version.
The first two bytes of the Wi-Fi serial protocol 55 AA indicate the data frame header.
2.4G has stronger wall penetration capability than 5G networks.
Usually, the 5G frequency band has a larger bandwidth, less interference, and faster transmission speed; however, the transmission distance is not as far as 2.4GHz.
Wi-Fi door lock temporary password universal docking solution can create up to 10 groups. There is no limit to the number of temporary passwords that can be set on a Zigbee door lock.
Please confirm whether the six wires required for programming are all connected through the serial port. If the RST and the IO0 are not connected, it will prompt failure.
Start bit: first send out a logic "0" signal to indicate the beginning of the transmission character. Data bit: It can be 5~8 bit logic "0" or "1". Such as ASCII code (7 bits), extended BCD code (8 bits). ASCII code is usually adopted. It is transmitted from the lowest bit. The parity bit: after adding this number (0 or 1) to the data bit, the number of "1" should be even (even parity) or odd (odd parity). Stop bit: it is the end of a character data. It can be 1-bit, 1.5-bit, or 2-bit high electrical level. Idle bit: in the logic "1" state, indicating that there is no data transmission on the current line.
The ADC port of the TYZS3 module can be used as normal I/O port.
The physical layer standard of Zigbee module is: IEEE 802.15.4.
ZS3 modules are available with both onboard and IPEX antennas, which can be pin to pin.
Hello, the main difference between these two is the antenna type: TYZS3-IPEX is an external antenna, and TYZS3 uses an on-board antenna. Since the firmware of the module needs to be adapted to the product, it is recommended to create a corresponding product. In the third step of product creation, the modules that can be selected for the corresponding product will be displayed. If it is not displayed, it means that it is not supported.
Maximum 12MA.
The 11th pin of the module IO14 is the pin for the module to wake up the external MCU. When the module needs to send data to the external MCU, the module will pull down IO14 for 200ms, and then send the data. After the transmission is completed, pull the high level.
The main disadvantages are as follows: 1. Private protocol; 2. Control relies on gateway; 3. Low market acceptance;.
Hello, the method is as follows: 1. Keep the device in fast flash or slowly flash mode for three minutes and do not get the device paired to a network 2. Keep the device in fast flash or slowly flash mode for more than 10s, and power the device off and then on.
RST is only the hardware reset pin of the module and cannot clear the Wi-Fi configuration information.
The data of RAW type will not be stored before networking, and need to be reported after networking.
The Raw data is not cached in the Wi-Fi firmware. It is only valid if it is connected to the network and report. You can modify the program and report the Raw data after receiving the 04 status.
Raw data cannot be cached in the Wi-Fi firmware and must be reported through a network. You can report the raw data again after the Wi-Fi firmware is connected to a router or the cloud.
PWM dimming is to control the output current of the power supply by adjusting the duty ratio; 0-10V dimming is to control the output current of the power supply for dimming by changing the 0-10V analog voltage.
The module gives output signals, and the hardware can adjust the current according to the output of the module.
The network environment will affect the data transmission speed. Please confirm the network is stable.
Hello, the general power-off memory will not take effect until 5 seconds after setting.
This product is only suitable for indoor use. It is forbidden to install outdoors. The recommended installation height is 1.6-1.8 meters; it is forbidden to install near air outlets and other places with strong convection, such as fans, windows, air-conditioning outlets, etc., otherwise hot air flow disturbance and personnel walking will cause False alarm, if possible, please close the curtains; Do not install near heat sources, such as direct sunlight, heaters, stoves, etc.; No screens, furniture, large bonsai and other partitions can be placed within the detection range.
Except for the smart voice services, other value-added services that have been activated are not available under the new account by default and need to be activated again.
Advantages: The cost is low enough to meet the wireless needs of general consumer products. Disadvantages: A large PCB space is required and the efficiency is low.
The common wiring shape of PCB antenna is serpentine wiring shape and inverted F wiring shape.
No, the clearance around the PCB antenna needs to be within 5mm, and no copper wiring is allowed. It is recommended that the distance between the antenna part of the module and other metal parts be at least 15mm.
The update message push in the OEM App can be configured in the Tuya IoT platform-Common Tools-Upgrade Notification. The version update reminder of the application market will be available by default in each application market.
NB module is suitable for outdoor scenes without Wi-Fi signal, such as: manhole cover monitoring, street lamp monitoring, fire hydrant monitoring, water quality monitoring, atmospheric monitoring, building energy consumption monitoring, public bicycles, smart gas meters, smart water meters, smart heat meters, smart parking, smart electricity meters, photovoltaic power generation, Battery monitoring, commercial air conditioning, cargo tracking, electric bicycles, smart greenhouses, smart farming, pipe network monitoring, power distribution facility monitoring, smart home appliances, smart access control, smart home, and healthcare.
By working mode, NB-IoT SIM cards are classified into PSM, DRX, and eDRX SIM cards. By specifications, NB-IoT SIM cards are classified into common pluggable SIM cards and mounted SIM cards (eSIM).
Reference Signal Received Power, is the cell common reference signal (CRS) power value received by the terminal. The value is the linear average value of the power of a single RE in the measurement bandwidth and reflects the strength of the useful signal in the cell. It reflects the path loss strength of the current channel, used for cell coverage measurement and cell selection or reselection. The value range of RSRP is -44~-140dBm, the larger the value means the better. when the Rx is less then -105, coverage strength is level 6, indicating the poor coverage. In this condition, the business is basically unable to be connected. when the Rx is -105~65, coverage intensity is level 1, which indicates very great coverage.
Basically around 10 years (AA battery).
Yes. For example, Zhejiang Telecom can resolve such problem within the province in about one week. Solution: Add base stations and optimize the signal transmission direction.
The NB module can be applied abroad, but which operator, which frequency band is used abroad, and whether there is an NB network needs to communicate with the local operator. The Tuya NB module supports frequency bands B1\2\3\5\8\20\26 \28.
The module will generate heat during operation and may also be affected by other high-temperature components. The heat dissipation is considered during the design of this product. When connecting to the system board, please keep the ground thermal pad well grounded. This is of great help to heat conduction and thermal balance, as well as to the electrical performance of the whole machine. Remarks: Try to keep this module product away from the power supply and high-speed signal lines, and protect the wiring of these interference sources. The antenna and the coaxial cable connecting the network card and the antenna should not be placed close to these interference sources. Do not place the module close to components with large heat generation such as CPU, as temperature rise will affect the RF performance.
The PIN35 of the NM1_NB-IoT module is the RF antenna interface, and the impedance of the port is 50Ω. You can find an antenna manufacturer to customize a suitable antenna or consult the project manager of Tuya to contact the antenna manufacturer for you.
The NB modules of Tuya are divided into the PSM type and the DRX type. The two types correspond to two different cloud logics. Before applying for the module, please determine the service type of the product, whether it is used for the PSM or the DRX. The PSM type modules will enter the PSM mode to reduce power. They are often used for battery-powered devices and have a fixed reporting notification type. The DRX type modules will not enter the low-power mode, and will respond to the data sent and received in real time. They are often used for devices that are not sensitive to the power and are the real-time controlling type.
You can use AT+CSQ to query the AT port.
Serial port UART0 can be used for firmware burning, the baud rate is 921600bps. Serial port UART1 is used for user authorization by default and is used for MCU common integration. Serial port UART2 is as log port, the baud rate is 921600bps.
Tuya NB module support Unicom, Telecom, and Mobile. However, Unicom has not deployed completely and Tuya official platform uses Telecom. Thus, it is recommended to choose Telecom, Mobile by following. You can purchase the IoT card, check the card you want to by is for PSM or DPX. Besides, you can contact Tuya PM to purchase the card as well.
Please check whether the power supply is normal, whether the serial port of the module is correct, and make sure the user integrated serial port is UART1. If you want to confirm whether the module is awakened, try to press PWRKEY to wake up the module.
The user should fully consider the EMC problems caused by signal integrity and power integrity when designing the whole machine. When wiring the peripheral circuit of the module, for the wiring of power and signal lines, keep twice the line spacing width. Effectively reduce the coupling between signals, so that the signal has a relatively "clean" return path. When designing the peripheral power supply circuit, the decoupling capacitor should be placed close to the module power supply pin, high-frequency high-speed circuits and sensitive circuits should be far away from the edge of the PCB, and the layout between them should be isolated as much as possible to reduce mutual interference and protect sensitive signals , Carry out shielding design for circuits or devices that may interfere with the operation of the module on the system board side. We suggest that when designing the package pads on the motherboard, the 14 pads in the middle should be designed according to the size in the structure diagram, and for 52 signal pads a week, add a length of 0.3mm or more to the module. The other three sides of the pad Extend 0.05mm outward. For the main antenna, please use 50 ohm impedance line design.
NB is a new 3GPP protocol. It is not the same standard as 2G GSM, but the two are similar. They are also cellular networks regulated by operators. However, NB has lower power consumption and more access points, but NB transmission The rate will be lower. In addition, NB and 2G are not the same base station. Domestic operators switch the base station of 2G to the base station of NB, and deploy NB in the frequency band of 2G.
National coverage. The Ministry of Industry and Information Technology has issued a document: It is required that by 2020, NB-IoT network achieves universal coverage across the country, and achieves deep coverage for indoor, traffic road networks, low-level pipe networks and other application scenarios, with a scale of 1.5 million base stations. If the base station near your position does not support NB devices, you can contact the person in charge of the operator to apply for activation.
It means that the module is not connected to the telecom cloud. Please check whether the power supply of the module is proper, whether the antenna is in good contact, if the SIM card is well placed and ensure the package service is sufficient. Finally, please make sure that the local base station supports NB devices.
The names of the serial ports of different modules are inconsistent, and the modules Pin38 and 39 can be collectively called the log port, and the baud rate is 921600.
The IoT SIM card is used for the NB module. The NB module will not be able to connect to the telecom cloud through the base station without this card. NB cards have different modes, such as PSM, DRX, and eDRX, each mode corresponds to different business logic. Common specifications are: patch (eSIM) and card (uSIM).
The NB module has been included in the 5G standard and will be developed along with 5G.
Tuya module support R14 protocol but the operators have not open location feature.
The MCU reports the command corresponding to the switch and the DP working status at the same time. The motor will not report any data during running period. When the user clicks pause or the device reaches the end, the device needs to actively report the result and the percentage status.
The MCU will report the running time after finishing the whole process once. The panel will control the opening and closing speed according to the running time.
The device will report the value corresponding to the percentage as well as the working status at the same time. Meanwhile, the device is running and no data will be reported during this period. When the user clicks the app panel to pause the action or the device runs to the end, it will report the DP status and the percentage status at the same time.
After receiving the upgrade data, it will be stored in the memory, and the upgrade will not start until the data is received.
60S.
Enumeration variables, in the order of enumeration, are 00, 01, 02... not the value filled in when the product is created. When communicating, just send the serial number.
Failure data points are reported according to bits. There are 8 bits in a byte, and each bit corresponds to a failure point. The lowest is the first failure point created by the corresponding platform. When the position is 1, it means that the failure point is faulty.
The Wi-Fi will resend the heartbeat packets to query the product information after receiving successful upgrade data.
Yes. The MCU debugging assistant simulates the communication between the MCU and the module, which is equivalent to the customer's MCU. You can use the mobile phone to configure the network and connect to the cloud.
There is a Wi-Fi performance test command in the protocol. The MCU only needs to send this command, and the Wi-Fi module will automatically scan the tuya_mdev_test router and return the signal value. The MCU only needs to give corresponding instructions according to the returned signal value.
The Zigbee scene switch must select the DP point of the scene ID group ID. The data structure of this DP point is used to send data when the scene is triggered.
The time obtained by the MCU is the time zone of the distribution network.
It is the current weather status, which is real-time and will be sent every half an hour.
Every time the module is powered on, an initialization process is required. After the initialization process is completed, the module will send the Wi-Fi status.
Tuya’s SDK has two functions: MCU_set_Wi-Fi_mode (unsigned char mode): You can choose to enter EZ distribution network or AP distribution network independently MCU_reset_Wi-Fi(): Wi-Fi module is in EZ and AP Switch back and forth between modes.
Due to version reasons, when the gateway sends a 0B command, the MCU must reply with the correct version number, and the App will display it normally.
First connect the dongle and set the DIP switches. Different DIP switches correspond to different channels. The MCU sends a production test command of 08, and the module will return a signal strength greater than 60, which means the test has passed.
Yes. For specific instructions, please refer to the document: https://developer.tuya.com/en/docs/iot/weather-function-description?id=Ka6dcs2cw4avp.
This depends on whether you have configured low-power networking, if you have configured low-power, the RF will be turned off if the module not networked in 3 minutes. If low power is not configured, the module will always be in network configuration status.
Status DP can be reported continuously, or all DPs can be grouped into one frame for reporting.
Basic protocols are the same for each product and mandatory for modules. Basic protocols include heartbeat detection, product information query, module's working mode, and Wi-Fi status.
Just report it during module query. For passive instructions, developers only need to fill in the variables in the function, and the MCU SDK will automatically handle the reported problems.
It can be filled in during debugging, but the actual product cannot be filled in as a fixed parameter. It is necessary to ensure that each time the App obtains MCU data, it can obtain the real-time status of each function point in the MCU.
When the module does not receive a response from the MCU, it repeats the package actively (5s once, and the time used by the MCU writes the Flash is enough). The same package of data has been sent for more than three times, then the upgrade is judged as a failure.
The possible causes are as follows: 1. The PWM signal cable is too long. 2. The LED light is close to a magnetic component. If either of the preceding problem occurs, modify PCB cabling.
An LC5 module has three I/O pins. Theoretically, it supports up to three PWM outputs for RGB. Due to the module's driver limitations, you are advised to use the I2C pin for RGB control.
No, LC5 module has 3 IO ports and supports output 3-channel PWM signals at most.
It can be done, but it can only be driven by the IIC method because of the limited pins of the module.
Analysis: 1) device restart, the hold would conduct self-test with rotation; 2) if the movement tracking function on, the holder would rotate if the IPC detects movement at some are Instruction: 1) If the device is restarted, then it would stop rotation once self-test finished; 2) Check if the movement tracking function on.
The procurement center supports the purchase of modules in different status such as debugging, trial production, and mass production. The ordering conditions corresponding to different order status are as follows: Ordering condition for debugging order: 1) The module and firmware information of the product must be configured completely; 2) The single purchase quantity must be less than or equal to 100pcs. Order condition for trial production order : 1) The module and firmware information of the product must be fully configured; 2) The product status must be "under development" or "released"; 3) The single purchase quantity must be less than or equal to 1000pcs. Order condition for mass production orders: 1) The module and firmware information of the product must be fully configured; 2) The status of the firmware version bound to the product and module is "Released"; 3) The product status must be "Mass production" . For detailed procurement tutorial instructions, please view: https://developer.tuya.com/en/docs/iot/guidelines-for-platform/purchase-center-/purchase?id=K93b8w0ky9k4n.
Please check the service purchase link for IoT WeChat Mini Program SDK billing：https://www.tuya.com/vas/commodity/detail?code=APPLETS_SDK_CREATE.
No, there is no impact. Due to iPhone limitations, all downloaded test app packages are displayed as untrustable. After your app is launched on the App Store and downloaded by users, this problem does not recur.
Assign the Access Wi-Fi Information permission and re-create the .mobileprovision file. Then, re-create a certificate based on the iOS certificate creation manual at https://docs.tuya.com/en/iot/app-development/oem-app/ios-push/ios-push.
1.The output signal of the IIC scheme is susceptible to interference, so filter capacitors and pull-up resistors need to be added to the SDA and SCL transmission lines 2. Check the drive dimming accuracy of the IIC solution. If it is 255-level accuracy, the jitter is generally obvious at low brightness dimming. It is recommended to replace the high-precision dimming solution such as BP1658CJ, etc.
I2C control only needs two DAT and CLK signals to control three-way or five-way lights, and the control pins are relatively reduced.
Data communication through UART serial port.
No, because the power supply of the HLW8012 chip is 5V, the power supply of the module is 3.3V, and a level conversion circuit needs to be added between the pins.
0.45 W.
The application scenarios of GPRS includes wearable devices, locator and POS machine.
GPRS DTU is a wireless data terminal for the IoT. It uses the public operator network to provide users with wireless long-distance data transmission functions. Adopting high-performance industrial 16 / 32-bit communication processor and industrial wireless module, with embedded real-time operating system as software support platform, RS232 and RS485 (or RS422) interfaces, which can be directly connected to the serial port design to achieve data transparency Transmission function. GPRS DTU has been widely used in the M2M industry in the IoT industry chain, such as smart grid, smart transportation, smart home, finance, mobile POS terminals, supply chain automation, industrial automation, smart buildings, fire protection, public safety, environmental protection, weather , Digital medical, remote sensing survey, agriculture, forestry, water affairs, coal mining, petrochemical and other fields.
Due to the difference in the batch of R, G, and B light beads, when mixing the colors of the three RGB, the color differences will appear. Gamma's adjustment eliminates differences in the light beads and other hardware, resulting in the desired effect of blended light on each color.
CW scheme and CCT scheme, CW and CCT are different realization methods of LED intelligent lighting control to adjust color temperature and brightness. The CW control method is a method of adjusting the current and color temperature realized by the two-channel PWM signal in the mixed adjustment mode. When the brightness is unchanged, the duty ratio of the two-channel PWM signal is adjusted separately to adjust the color temperature value. The total duty cycle of the two PWM signals remains unchanged. When the color temperature is unchanged, the brightness can be adjusted by adjusting the duty cycle of the PWM signal separately, and the duty cycle ratio of the two PWM signals at the high level of the total brightness is unchanged. The CCT control method is to separate the brightness and color temperature control by two PWM signals. One PWM signal controls the brightness, and the other PWM signal controls the color temperature. The PWM signals for brightness control and color temperature control are not related to each other and separate from each other.
CW firmware is used for CCT control. When the brightness is adjusted, the color temperature will change; When the color temperature is adjusted, the brightness will change, the power will not increase.
If the CRC sum check fails, compare the check value with the calculation result in the example. The CRC and check algorithm are as follows:.
Currently, up to 20 kHz is supported. We do not recommend that you set a high frequency because it may affect the PWM stability.
It is because the amount of data sent in real time will be very large, the SigMesh network itself has a slow propagation rate, which is not suitable for real-time data transmission.
No. This feature will come soon.
Analysis: Some Bluetooth LE devices are strong-Bond device, can't pair unless the previous account remove it Suggestion: Check if it was removed from the previous account.
The metering chip tests the 220V AC signal. If strong or weak isolation needs to be considered, there are the following two solutions: 1. Signal terminal isolation: sampling through voltage transformers and current transformers. The metering chip and the MCU can share a set of power supplies. 2. Power supply isolation, output pulse optocoupler isolation: the metering chip power supply and MCU adopt two sets of power supplies, and SEL, CF, CF1 are isolated by optocoupler.
Just connect 3 IOs directly with CF, CF1 and SEL. The module calculates power, voltage, and current by measuring the pulse period of CF and CF1, and then conducts electricity statistics. Only ordinary IO is needed to connect with SEL, switch SEL high and low level to measure voltage or current.
It is generally used to define the fault type to save space. The binary bit indicates whether the corresponding fault exists, and the corresponding decimal system is reported back. Suppose a product has four types of failure: No fault: decimal - &rt; 0, binary - &rt; 0000; The first kind of fault occurs: decimal - &rt; 1; binary - &rt; 0001; The first and second faults occur at the same time: decimal - &rt; 3; binary - &rt; 0011; All faults occur simultaneously: decimal - &rt; 15; binary - &rt; 1111;.
Download the Arduino IDE at https://www.arduino.cc/en/Main/Software.
Analysis: The lock is not restored to the factory defaults in time. Advice: Check that the app sends the data clearing command to the lock in time after the offline lock is removed.
The data sent by the App is transmitted in the form of a string, so the real data is converted from ASCII to HEX.
Please test if PWM signal of the module is normal when the App is adjusted to 1%. If it is normal, generally it is due to insufficient dimming depth of the dimming IC, recommended to adjust the brightness of the module a little higher in the IoT platform, and then re-apply sample for testing and validation.
The color temperature drive mode does not match, the hardware color temperature drive mode is CCT, and the module color temperature drive mode is configured as CW. So please change the color temperature driving mode of the IoT platform to CCT, and then reapply for sample testing.
Tuya supports launching the App on: App Store (in and outside China) Google Play (for Android mobile phones outside China) Android App platform in China The service includes operating instruction video and preview image making, message push certificate application, and app launch.
High Approval rate: Tuya modifies the content and policies based on the platform review rules and real-time status. It detects the rejection risks of the app in advance based on the app function, app content, submitted materials, new policy changes, review process, and other factors. Professional Launch: Tuya provides a full and professional launch service. You only need to provide basic information, such as the app name, app description, and app launch scope. Tuya personnel take on other complex tasks, for example, making operating instruction videos and preview images. Synchronous app message push: The app launch service includes creating a push certificate on the app platform. The certificate enables your app to proactively push messages to app users, improving user loyalty and app activity.
Product name.
The implementations of the two modes are different: It is simple to operate in the SMART mode, which is generally defined that the indicator light flashes quickly. The network configuration is reliable in the AP mode, which is generally defined that the indicator light flashes slowly.
【Short Description template-Hindi】 अपने स्मार्ट घरेलू उपकरणों को नियंत्रित करने के लिए एलेक्सा का उपयोग करें smart 【Detailed Description template-Hindi】 “Replace your skill name" Alexa के साथ सबसे व्यापक आवाज नियंत्रित स्मार्ट होम अनुभव प्रदान करता है। यहाँ स्टेप बाय स्टेप गाइड है: (1)। Google Play या iOS ऐप स्टोर पर हमारा "Replace your App name" ऐप डाउनलोड करें; (2)। एप्लिकेशन लॉन्च करें और एक नया खाता पंजीकृत करें (या यदि आप पहले से पंजीकृत हैं तो लॉगिन करें); (3)। स्मार्ट वाईफ़ाई बल्ब चालू करें और उन्हें "Replace your App name" ऐप से कनेक्ट करें; ; (4)। महत्वपूर्ण: आप "Replace your App name" App के साथ उपकरणों का नाम बदल सकते हैं। इसलिए यदि आप एक स्मार्ट बल्ब का नाम बदलकर "Livingroom Light" रखते हैं, तो इको को चरण 9 में उपकरणों की खोज के बाद वही नाम मिलेगा; (5)। अमेज़ॅन मार्केट, Google Play या iOS ऐप स्टोर से अमेज़ॅन "Alexa" ऐप डाउनलोड करें, और "Alexa" ऐप के साथ इको कनेक्ट करें; (6)। “Replace your skill name" के लिए Alexa skill निर्देशिका खोजें; (7)। “Replace your skill name" के Enable पर क्लिक करें, फिर लिंकिंग पेज पर अपना खाता उपयोगकर्ता नाम, पासवर्ड और क्षेत्र इनपुट करें; (8)। इको से बात करें "Alexa, मेरे उपकरणों को खोजो" (9)। अब सारा सेटअप हो गया। अपने उपकरणों को नियंत्रित करने के लिए इको से बात करने का प्रयास करें। आप इन जैसे अपने घरेलू उपकरणों पर ध्वनि नियंत्रण का आनंद ले सकते हैं: Lights: * Alexa, light चालू कर दो * Alexa, living room बंद करो * Alexa, Livingroom light मंद करो * Alexa, Livingroom light की चमक बढ़ा दो * Alexa, Livingroom light को 20 प्रतिशत पर set कर दो * Alexa, मेरे light के रंग को नीला कर दो। * Alexa, मेरे lights के रंग को daylight कर दो। 【Privacy Agreement Template】 Coming Soon.
【Short Description template-Portuguese】 Alexa, acenda aluzdo quarto；Alexa, apague aluzdo quar 【Detailed Description template-Portuguese】 Você pode simplesmente pedir a Alexa para ligar, desligar ou diminuir a luz. Não há necessidade de ir para o switch para ajustar sua luz doméstica - basta falar com Alexa em seu Amazon Echo. Depois de conectar Alexa aos seus produtosApp nameem alguns passos simples: (1). Faça o download do nosso aplicativo “Replace your App name” no mercado de aplicativos Android ou ios; (2). Registre uma contaApp nameem nosso aplicativo “Replace your App name”; (3). Você precisa ter alguns dispositivos inteligentes “Replace your App name” na mão; (4). Configure esses dispositivos em nosso aplicativo “Replace your App name” e altere o nome apropriado para seus dispositivos que serão usados na Skill “Replace your skill name”; (5). Baixar Amazon aplicativo “Alexa” do Android, ios ou Amazon app mercado; (6). Configure o Echo com o aplicativo “Alexa”; (7). Pesquisar Skill “Replace your skill name” da categoria de Skills do aplicativo “Alexa”; (8). Clique em Ativar Skill de “Replace your skill name”, e você será navegado para a página de login “Replace your App name”; (9). Insira seu nome de usuário e senha da conta “Replace your App name”, você será redirecionado para a página de sucesso; (10). Agora toda a configuração está concluída. Você pode desfrutar do controle de voz em seus dispositivos domésticos como estes: “Alexa, acenda a luz do quarto.” “Alexa, apague a luz do quarto.” “Alexa, ajuste o brilho da luz do quarto em 50 por cento.” “Alexa, aumente o brilho do quarto.” “Alexa, diminua a luz do quarto em 50.” “Alexa, mude a luz do quarto para verde.” “Alexa, deixe as luzes do quarto mais frias.” 【Privacy Agreement Template】The content of the link is only a template, you need to modify the content yourself. https://www.dropbox.com/s/i1sonvp8zpmy9cs/privacy_policy_pt.docx?dl=0.
【Short Description template】 Use Alexa to control your smart home devices! 【Detailed Description template】 You can simply ask Alexa to control your “Replace your device name, Such as: light”. After connecting Alexa to your products in a few simple steps: (1). Download our “Replace your APP name” app in app market then register an account; (2). Configure our devices in our “Replace your skill name” app and change appropriate name for your devices; (3). Download Amazon "Alexa" app from android,ios or Amazon app market then configure Echo with "Alexa" app; (4). Search “Replace your skill name” skill from the "Alexa" app skills category; (5). Enable “Replace your skill name” skill, and you'll be navigated to “Replace your skill name” login page; (6). Follow the instructions on the page to complete linking; (7). Now all setup is finished. You can enjoy the voice control on your home devices like these: “Alexa, turn on the bedroom light.” “Alexa, turn off the bedroom light.” “Alexa, set the bedroom light to 50%.” “Alexa, brighten the bedroom light to 50%.” “Alexa, dim the bedroom light to 50%.” "Alexa, set bedroom light to green." "Alexa, set bedroom light to cool white." 【Privacy Agreement Template】The content of the link is only a template, you need to modify the content yourself. https://www.dropbox.com/s/jd8pg4owdgf0z7b/privacy_policy_en.docx?dl=0.
【Short Description】A quick at-a-glance sentence that describes the skill or what customers can do with it. 【Detailed Description】A more comprehensive description of this skill. Include information about any prerequisites like hardware or account requirements and detailed steps for the customer to get started. This description displays to customers on the skill detail card in the Alexa app. For Flash Briefing skills, list the feeds offered within the skill 【Privacy Policy URL】Link to the privacy policy that applies to this skill. Provide a URL that sends users directly to a legally adequate privacy policy. Please ensure that your collection, use, and storage of users’ personal information complies with your privacy policy. ☞English template ☞German template ☞Italian template ☞French template ☞Spanish template ☞Portuguese template ☞Japanese template ☞Hindi template.
No. A sphere lamp has a high temperature and requires a 105°C module.
The SDK code needs to be tailored.
Some modules can choose white light or warm light for the network configuration reminder color, this option will appear during configuration; some modules cannot be selected, and this option will not be available during configuration.
Due to the high power consumption of the Wi-Fi module, when 12V plus LDO outputs 3.3V, the LDO is too damaged and heats up. It is recommended that 12V plus DC-DC output 3.3V to power the Wi-Fi module.
No. SoC modules have PIDs to identify app UIs. If a 1-way or 2-way switch uses a Wi-Fi module designed for a 3-way switch, the 1-way or 2-way switch will be displayed as a 3-way switch in the app. However, if the 1-way, 2-way, and 3-way switches use an MCU solution, they can use the same Wi-Fi module.
Compared with the 01 protocol version, the 02 protocol version has an SN in the frame format.
The Zigbee gateway of our Tuya is ZHA, so it supports this Zigbee Home Automation protocol.
The current logic of the scene switch is: After the App is controlled, the instruction is directly issued to the controlled sub-device, and the MCU cannot receive the data.
Each OEM App supports the Multilingual Debug Mode. App users in the debugging allowlist can view the recently updated or modified entries, enable Show multilingual code, display the code of each entry, and then switch among different languages in the App. Go to Tuya IoT Development Platform App OEM App CommonTools Debug Allowlist, and add respective OEM App accounts to the debugging allowlist. For more information, see What is the debugging allowlist? Open the OEM App and go to MeSettingsMultilingual Debug Mode to check the code of each entry in the App.
If you just want to use your mobile phone to experience the control, you can open the App and scan the QR code in the second step of creating the product. If you create an MCU-connected product, in addition to the experience in the second step, in the third step, you can click "Device Debug" to receive instructions from the mobile client like a real device, or simulate a real device Report data and debug the App interface.
You can use the Wi-Fi general integration solution. It provides the serial port pairing function, which allows the MCU to send commands to implement pairing.
The platform already supports devices to open the "DP Instruction" function, please refer to the following page for details.
Check whether the pin and level triggering methods in the configuration file are correct. Check whether the PWM frequency of the mood light is correct. Check whether the RGB light bulb is damaged. Check the hardware circuit design.
MU-MIMO stands for multi-user, multiple-input, and multiple-output, and supports up to eight concurrent users accessing Wi-Fi 6 networks in both uplink and downlink scenarios. MU-MIMO in Wi-Fi 6 enables high-speed networking and meets the tremendous demand for large network capacity with increased throughput and efficiency. Compared with Wi-Fi 5, Wi-Fi 6 improves the downlink capacity by two times and the uplink capacity by eight times.
You need to make sure that: The real computer and the development computer are in the same network segment, and the global VPN is not enabled.
To flash the firmware to the WBR3 module, you need to connect the 3.3V, GND, Log Tx, Log Rx, A0, and A13 (silkscreen: Rx) pins. During flashing, the A0 and A13 (Rx) pins need to be pulled up to 3.3V. After the firmware is flashed, the A0 and A13 (Rx) pins must be pulled down. Otherwise, the module cannot be started. See the documentation for details：https://developer.tuya.com/en/docs/iot/burn-and-authorize-wbr-series-modules?id=Ka78imt8pf85p.
During debugging, you can modify them through macro definition in "app_port.h". For production firmware, modify them using production test commands through the host.
The specific algorithm of CRC8 is: CRC8=CRC16 (hardware type, member id, frozen state) & 0xFF. For the specific algorithm of CRC16, please refer to the source code in the door lock SDK: uint16_t crc16_compute(uint8_t * p_data, uint16_t size, uint16_t * p_crc).
Cause: The language key values of different countries and regions on different Android smartphones are varied. For example, the language key value for traditional Chinese may be zh-hant or zh-hk. Solutions: Only zh and en need to be defined in the development environment. Other languages need to be configured on Tuya IoT Platform. Cloud services are displayed based on the region. 1. On the Product page, click Product Configuration and click Settings in the Multilingual area to go to the Multilingual page. Then, select Device Panel. 2. Download the multilingual template, add custom languages based on the template content, and import the template. 3. The following figure shows a custom configuration example. Note: The key value cannot be Chinese. You can edit content based on the example or downloaded file.
There are two methods: (1) Submit a ticket and connect the Zigbee module to the network. 📎 demo (1).zip (2) Call provided APIs. The Zigbee beacon is required. (Only Zigbee modules can be tested.) In the provided SDK, the following two APIs can test Zigbee modules in the offline state: OPERATE_RET tuya_user_zigbee_rf_test_start(UINT_T channel, UINT_T pack_num); //Send pack_num packets to the specified channel. OPERATE_RET tuya_user_zigbee_rf_test_result(VOID); //Obtain received packets. In normal cases, the tuya_user_zigbee_rf_test_start API is first called to send a certain number of packets to the channel with the Zigbee beacon. Then, the tuya_user_zigbee_rf_test_result API is called to obtain the number of returned packets. Finally, the number of returned packets is compared with the number of sent packets. The beacon mode is set to RF, and the channel is the same as that written in the code.
Problem： OEM App, the previous push is available, after a certain point in time all pushes are unavailable. Range： Customers who use Google Play to download apps. Solution: Step 1： 1. Use your Google account to log in to firebase: https://firebase.google.com/?pli=1, and find the project corresponding to the OEM App you have configured (if you don't find the project, you need to confirm whether this is the Google account) 2. After opening the corresponding project, click Settings-Project settings-Cloud messaging, check the Sender ID and key, and check whether these two values are consistent with the Tuya IoT platform. Tuya IoT platform viewing path: App-Requiredsettings-CertificateforAndroid -Configure Google FCM. If the above steps are inconsistent between Google and the IoT platform, or the project has been deleted, the FCM push needs to be reconfigured, and it needs to be rebuilt and launch again. If the above steps show that the two are consistent, please refer to the following steps: Step 2: 1. Log in to the Google Play console, click Settings - Application Integrity, and check whether the Google signature is enabled in the App. If Google signature is enabled, copy the SHA1 value. 2. Log in to the Google cloud platform, enterthe original project , click the credentials, and find the Android key created by firebase. 3. According to the figure below, enter the Android package name and the SHA1 value just copied, click done and save, and re-test the App push after completion, no need to re-launch the App.
Zigbee communication is widely used in various fields such as lighting, sensing, and electrician, such as: commercial lighting, security sensing, smart door locks, etc.
Resetting is to disconnect the Bluetooth connection of the module, unbind the Bluetooth, clear the module cache information, and restart. Unbinding is to unbind the app and disconnect the Bluetooth connection. The difference is that resetting is more thorough than unbinding. Some data (virtual ID, offline cache and other data) is cleared, and you can choose to use the interface according to your functional requirements. For example, the IoT platform configures the MCU upgrade of the A device according to the virtual ID. After using the unbinding command, and then configure the Internet, it will still remind the user to upgrade. After using the resetting command, and then configure the Internet, there will be no upgrade prompt, you need to reconfigure on the IoT platform.
This happens because your App fails to obtain the PID of the Bluetooth device. To troubleshoot, check whether the PID is synchronized as per the protocol. If the protocol works properly, check your network connection. PIDs have restrictions for pairing, and only whitelisted apps can be connected to the network. You can contact Tuya personnel to apply for permission.
The module firmware does not need to be updated. You only need to reset the module and re-pair it. When DPs are modified, the module needs to be re-paired for the modification to take effect. After DPs are modified, firmware DPs in the MCU must also be modified. If you use an MCU SDK for development, you can download the DP file from the platform and port the added DPs to the MCU SDK. If you use customized MCU software, you need to modify the MCU software based on the modified DPs. To update the MCU firmware, you can choose MCU OTA or use a tool based on the scenario.
The term "special pairing" has been changed to anti-misoperation pairing. For more information, see the definition in the "Query product information" section of the protocol document. When a user locally resets a paired module by sending the command from the MCU, the device is in the to-be-paired state. If it remains unpaired for three minutes (the duration is determined by the mt field), it is automatically restored to the network connection before it is reset. If the device is power-cycled after it is locally reset and before it is paired again, it will also be restored to the network connection before it is reset. When anti-misoperation pairing is enabled, the device will forget the last network connection and stop reconnecting to the last network only if it is removed from the app. This pairing mode can prevent resetting devices locally by accident.
Wi-Fi products integrated with the MCU feature the anti-misoperation function, allowing a re-connection. You can view the explanation of command 01 in the MCU integration protocol. https://developer.tuya.com/en/docs/iot/tuya-cloud-universal-serial-port-access-protocol?id=K9hhi0xxtn9cb#title-5-Query%20product%20information.
Wi-Fi 6 proposes a channel spatial reuse technique and introduces basic service set (BSS) coloring. By adding a 6-bit identifier to frames to mark the devices connected to the network, the BSS of different APs in the same channel can be identified. Labels are also assigned to data. This way, data is transmitted to the fixed addresses in order. This improves the device connection efficiency in complex network conditions.
The transmission mechanism of the Wi-Fi module serial port has a certain relationship with the function command: 1. For the commands issued for functions, when multiple DP commands are issued at the same time, in order to ensure the timeliness of control and the user experience, the module is issued without intervals. Therefore, there will be scenarios where sticky packet data is sent; 2. The daily heartbeat query frame is a periodic query every 15s, and the shortest retransmission interval is 1s; 3. For the networking status frames and heartbeat frames, in the scenario of simultaneous triggering, the module sends them at intervals of 100ms. To sum up, the shortest cycle for issuing module commands can be understood as no interval. Therefore, the data reception and analysis of the MCU also needs to support the scenario of sticky packet data processing.
It sends command word 04 to reset Wi-Fi, or sends 05 to redirect Wi-Fi to enter AP mode or EZ mode. If it is the general firmware of Wi-Fi power-off Quicklink, it is different from the above, and you can refer to the corresponding protocol document for details.
After turning on the low power consumption, the cloud module only has the ability to configure the Bluetooth network, and cannot use Bluetooth to control the device.
To obtain Team ID, visit https://support.tuya.com/en/help/_detail/Kb8btpc5e2z3h If the corresponding options are unavailable, you can try to join the Apple developer team first. For more information, visit https://help.apple.com/developer-account/#/dev55c3c710c.
The production testing guidance applies to PCBA modules and describes how to test whether the RF and the serial port of the Wi-Fi module work normally. For more information, visit https://docs.qq.com/doc/DTW16U0F1bnNTdWh1.
The alert feature enables alerting from the app when a lock alert is triggered and provides alerting records. For more information, visit https://docs.qq.com/doc/DTVRmRnNVQXdhdG93. The following DPs are involved: DP 8: Alerts DP 16: Duress Alarm DP 19: Doorbell.
For information about how to locally restore a Wi-Fi lock to factory settings, visit https://docs.qq.com/doc/DTWxvV0VERmVYY29S.
You can select a Wi-Fi lock module based on your requirements. For more information, visit https://docs.qq.com/sheet/DUWVDeHBNTFlOV1dq?tab=BB08J2.
The following DPs are involved: DP 38: Remote Deletion Allowed DP 39: Remotely Delete Fingerprint DP 40: Remotely Delete Response DP 41: Remotely Delete Code DP 43: Remotely Delete Card For more information, visit https://docs.qq.com/doc/DTWhOclRpUFFUTkxJ.
The feature involves the following DPs: DP 34: Query Added Method DP 35: Added Method DP 36: Added DP 37: Added DP 42: Cancel Remote Adding For more information, visit https://docs.qq.com/doc/DTVNoV1VUS0tmQ0NU.
The following DPs are involved: DP 11: Battery Level DP 12: Remaining Battery For more information, visit: https://docs.qq.com/doc/DTWpIWmFSbVp2eG5L?confirmed=1.
The offline code function enables users to generate an offline code in the app for visitors to unlock the Wi-Fi lock within a valid time period. Offline codes can be created and used without a network connection and can be used when the lock is offline. The following DPs are involved: DP 32: Offline Code Unlocking DP 33: Clearing offline codes For more information, visit https://docs.qq.com/doc/DTXlwTUpubXZia0ln?confirmed=1.
For more information, visit: https://docs.qq.com/doc/DTUdWUFR3THNFR1Zt?confirmed=1.
The DPs correspond to the various functions of the lock and provide functional descriptions by category. You can refer to or select DPs when creating a PID. You need to visit https://docs.qq.com/blankpage/DUXRKV05aZ0dWb1VK for more information.
Tuya provides three hardware solutions for the ISM band lower than 1 GHz. 1. Tuya Sub-G Hybrid (TSH) solution, which features ultra-low costs. 2. Tuya Sub-G Mesh (TSM) solution, which applies to complex scenarios. 3. Tuya Sub-G Longrange (TSL) solution, which enables ultra-long-range connections.
Narrowband Internet of Things (NB-loT) is a narrowband cellular communications technology that is designed for network operators and oriented for IoT applications. It is built on the cellular network and limits the bandwidth to 180 kHz. It can be directly deployed on a GSM, UMTS, or LTE network to reduce deployment costs and enable smooth upgrades. NB-IoT is a new technology in the IoT field. It supports cellular data connections of low-power devices on a WAN, which is also known as low-power wide-area network (LPWAN). NB-IoT ensures efficient connections of devices that have long standby time and high networking requirements.
Terminal report data Platform Distributed Data (PSM) Platform Distributed Data (DRX) Platform Distributed Data (eDRX) Air interface delay + delay between private network and client server Air interface delay + delay between private network and platform + maximum sleep period of PSM (maximum one week) Air interface delay (750ms) + DEX paging cycle (maximum 10.24 seconds) Air interface delay (750ms) + eDRX paging cycle (maximum 2.92 hours, minimum 5.12 seconds) Second level (3 seconds to 30 seconds) Hour/day level, depending on the terminal reporting period Seconds, depending on the DRX paging cycle Seconds to hours, depending on the eDRX paging cycle.
There is no such limitation for the same PID for now.
Hardware-related cause: Check whether the power supply to the module is sufficient. The peak current of the module is 450+ mA. Generally, supply 300+ mA current to the module. Add a capacitor to process peak current. Software-related cause: Check whether the MCU returns heartbeat packets to the module based on the heartbeat specifications. Check whether the power supply of the module is controlled by an I/O interface on the MCU and whether the control level of the I/O interface is stable. Check serial port interaction commands to see if the MCU sends two commands to reset the Wi-Fi module. If it does, the module will repeatedly reset and rebooted.
Yes. The connection distance may be affected. However, the connection distance of modules is about 200 meters. Therefore, the impact is little.
Yes, the height cannot be adjusted based on the content. Therefore, you must set the height for the window.
Check whether the buzzer type is consistent with that in the configuration file. For a passive buzzer, check whether the entered buzzer frequency is correct. Check the hardware circuit design.
Check whether the output pins of the atomizer disc output PWM normally. Check whether the fan works properly. Check the hardware circuit design.
OFDMA-MU mode: In small-packet services, where each PSDU contains a few bits, the AP may include the small packets of multiple STAs in the same RU and transmit them to different STAs at the same time.
Wi-Fi 4 (2.4 GHz/5 GHz): electrical, lighting devices, sensors, home appliances, IP cameras, gateways, central control units, and more. Wi-Fi 6 (2.4 GHz): electrical, lighting devices, sensors, home appliances, IP cameras, gateways, central control units, and more. Wi-Fi 4 (2.4 GHz/5 GHz) & Bluetooth LE: electrical, lighting devices, sensors, home appliances, IP cameras, gateways, central control units, and more. Wi-Fi 6 (2.4 GHz) & Bluetooth LE: electrical, lighting devices, sensors, home appliances, IP cameras, gateways, central control units, and more.
Compared with previous Wi-Fi generations, Wi-Fi 6 has the following advantages: 1. Improved speed: Compared with Wi-Fi 5, the speed of a single spatial channel is improved by 40%. The overall transmission speed is faster, and the latency is lower. 2. Support for multiple frequency bands: Wi-Fi 6 supports both the 2.4 GHz and 5 GHz frequency bands, but Wi-Fi 5 supports only the 5 GHz frequency band. This attracts Wi-Fi 4 users to smoothly switch to Wi-Fi 6. 3. Connection to more devices: Wi-Fi 6 supports MU-MIMO (concurrent download and upload by eight users, respectively) and introduces the orthogonal frequency-division multiple access (OFDMA) technology. More devices can be connected without reducing the speed, meeting requirements in different terminal scenarios.
Wi-Fi represents 802.11 series standards for the wireless LAN released by the IEEE in 1997. Technologies developed based on these standards are Wi-Fi. Wi-Fi is called by Wi-Fi alliance manufacturers for brand certification. Currently, the 802.11 series standards have been upgraded to the sixth generation, and the Wi-Fi alliance calls it Wi-Fi 6.
Zigbee represents the IEEE 802.15.4 protocol. It is a short-range, low-power, low data rate, and meshing wireless communication technology. It mainly applies to automatic and remote control and can be embedded into various devices.
Target wake time (TWT) is an important resource scheduling function supported by Wi-Fi 6. It allows devices to determine when and how frequently they will wake up to send or receive data, which ensures that the devices are in deep sleep mode when no data exchange is performed. This helps reduce power consumption and improve the transmission efficiency of devices.
Bluetooth Classic: Audio products and outdoor sports helmets. Bluetooth LE: Electrical, lighting, sensor, home appliance, fitness, wearables, sports, and outdoor appliances. Tuya Beacon: Lighting, electrical, sensor, and home appliances. Bluetooth mesh: Lighting, electrical, sensor, and home appliances.
Currently, Tuya provides Bluetooth products in the following sectors: electrical, lighting, and sensor. For more information, visit https://drive.weixin.qq.com/s?k=AGQAugfWAAkiSYTuQr.
Before the production test, remove the Zigbee module from the App. The Zigbee module can enter the production test state only when it is not paired with the network.
No. Currently, only cooperative processing by the MCU and module is supported.
You can change the heartbeat period of only low-power devices by using a serial port command in the MCU. For more information, visit https://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty#title-28-MCU%20%E9%85%8D%E7%BD%AE%20Zigbee%20%E7%BD%91%E7%BB%9C%E7%AD%96%E7%95%A5%E5%8F%82%E6%95%B0.
No. In a Wi-Fi and Bluetooth LE combo module, the Bluetooth module is used to assist in pairing. After the combo module is paired with the network, the combo module preferentially reports and delivers data over the Wi-Fi link. Only after the combo module is disconnected from the network for more than 3 minutes is Bluetooth used for control.
The MCU does not need to parse this DP. When this DP is selected, the module firmware uses this DP to number scenes.
In self-processing mode, the level of related general-purpose input-output (GPIO) is pulled down to reset the module. In MCU-coordinated processing mode, serial port commands are used to reset the module.
MCU SDK: Tuya provides the pass-through module and the SDK running on a customer's MCU. The customer integrates the MCU SDK into the MCU, and the MCU communicates with the Tuya pass-through module over the serial port to access Tuya IoT PaaS. TuyaOS SDK: Tuya provides the module and the SDK running on the MCU inside the module. Customers perform custom development based on the MCU in the module.
No. The HomeKit certification is performed based on the brand and PID. A HomeKit-certified product belongs to an existing brand. A brand owner cannot purchase a HomeKit-certified product from a factory and sell it directly. The brand owner must apply for the HomeKit certification for the new OEM product. Apple will hold those who sell HomeKit products with inconsistent OEM and certified brands legally liable if found in market channels.
Note: The HomeKit value-added service indicates the WWHK Testing and Certification Application service. The WWHK Testing and Certification Application service is dedicated to devices and OEM Apps. It is used to build the HomeKit capability for the hardware of a device and enable the OEM App integrated with the device to meet the HomeKit integration conditions. In this way, voice control can be implemented by using devices, software, or Apps in the Apple ecosystem, such as HomePod, Siri, and Home App. The OEM App can easily integrate with the Home App to control the device. The Siri Access service is dedicated to OEM Apps. Users can control scenes created in the OEM App by giving Siri commands. (The OEM App cannot directly connect with HomePod or control a HomeKit device.).
Tuya charges HomeKit product development based on the used module and cloud service, the same as that of other products. No extra token fees exist. However, the HomeKit value-added service fee exists. For more information, see: https://www.tuya.com/vas/commodity/detail?code=WWHKIntroduction to the WWHK Testing and Certification Application service https://www.tuya.com/vas/tmpl/apply?code=WWHKWWHK Testing and Certification Application ordering page and ordering description.
Q: Can I enable HomeKit product access through PID marking, the same as the access method for other smart speakers? Q: Can I purchase the HomeKit value-added service to add the HomeKit function for developed products? Q: Can I perform WWA, WWGA, and HomeKit certifications for end products together? A: No. To enable the HomeKit function, you need to perform hardware integration at the product development phase and use the specific module and solution. For more information about the module and solution, contact the value-added service pre-sales team. HomeKit function integration cannot be completed through PID marking. If the HomeKit function needs to be added for an end product, copy or replace the PID and reconfigure it at the hardware layer to develop and certify the HomeKit function of the new product. For certifications related to an end product, it is recommended that the HomeKit certification be performed first. When the hardware conditions become stable, perform the WWA and WWGA certifications.
No. Only the specific HomeKit solutions and modules support the HomeKit function. For more information about the solutions and modules that support HomeKit product development, visit the WWHK Testing and Certification Application ordering page and see the ordering description. https://www.tuya.com/vas/tmpl/apply?code=WWHK (The modules that can be used for HomeKit product development are limited because the chip vendors and chip resources that support the HomeKit solution have high requirements for the modules. The modules need to support both the HomeKit and Tuya platforms. If you have powerful development capabilities, you can develop modules by yourself based on the SDK and license provided by Tuya.).
The module records the number of on and off times. When the number of power-on times reaches the preset value, the module enters the pairing mode. Note: The power-on duration cannot be longer than that configured on the Tuya IoT Platform. Otherwise, the number of on and off times will be cleared.
It seems like the light automatically powered off and then powered on. Check whether the hardware solution, especially the power supply design, has defects that may cause the malfunction of the light. If the problem persists, submit a service ticket on the Tuya IoT Platform to ask for technical support from Tuya.
Non-keep-alive Wi-Fi locks do not have online or offline states and are connected as required. Keep-alive Wi-Fi locks are displayed as offline in a period of time after power-off. Bluetooth locks can be connected as required or actively initiate persistent connections. After the lock is disconnected from Bluetooth, the lock is displayed as offline. Both the lock and App can initiate connection and disconnection. Zigbee locks are in the online state when the power supply and signals are stable. After the power supply or network is disconnected, Zigbee locks are in the offline state. NB-IoT locks have the same logic as Zigbee locks.
For Tuya modules, select QIO. For modules provided by other vendors, confirm the Flash operating mode with the corresponding vendors.
This is because the duty cycle of the PWM light is not 100%. 1. The duty cycle at the maximum brightness of colored lights with Gamma correction is not 100%. 2. The duty cycle of PWM lights not at the maximum brightness is not 100%. Solutions: 1. The higher the frequency of the PWM signals generated by the module, the denser the ripples and stripes will be, and the less visible they will be in the images and videos shot with a mobile phone. Generally, if the PWM frequency is 8 kHz or higher, the ripples and stripes in the images and videos shot with a mobile phone are almost invisible. 2. Use the IIC driver constant current solution.
Possible causes: 1. PWM signals from the I/O pins of the module are sent to the LED driver control chip. If the PWM interface of the control chip has large interference and the PWM signals of the module are controlled at a low level, but the level of the PWM interface of the control chip is not 0V, the light glimmers, especially when the LED driver chip has analog control signals. Generally, you can add filter capacitors at the I/O pins to solve the problem or shorten the PWM trace length. 2. The LED driver control chip has electric leakage. Use another LED driver solution. 3. Generally, the aluminum substrate is used as the LED light panel. If the light panel has electric leakage, the light glimmers after it is turned off in the App. You can connect a resistor to the LED beads in parallel mode to resolve the electric leakage problem.
It depends on whether the light is paired. If the light is not paired: The light keeps the previous state after power cycling. If the light is paired: When the Do-Not-Disturb mode is not enabled, the light is forcibly turned on upon power-on, and the light status is determined based on the configured power-off memory mode, which includes the initial mode, memory mode, and custom mode. The light status upon power-on varies depending on the mode.
A delay exists after a light is turned on and the output of the control signal for the module. When the module initializes I/O signals, the signals are unstable. If an I/O signal does not have a pull-down resistor, the signal is temporarily at a high level. When the signal is transferred to the LED driver control chip, output at full power occurs. When the module is initialized, the I/O signal is pulled down. According to the configuration on the Tuya IoT Platform, the maximum brightness of a light is 50%, that is, half power. The module must be initialized to output the corresponding pulses.
The light status can be configured on the no-code firmware. You can set it to steady-on or blink quickly upon power-on. Generally, blinking quickly upon power-on indicates pairing upon power-on.
The production test of a Zigbee sensor can be performed on a host. 1. Production test over the PCBA serial port: (1) Lead the VCC, GND, TX, RX, or RST test point of the product and connect it to the serial port of the host. Set the baud rate of the host to 115200. (2) Power on the Zigbee dongle, select the RF mode, and set the transmitting power. It is recommended that the transmitting power be set to 10 and the channel ID be started from 11, the same as that on the host. (3) After the environment is built, click Run on the host and perform the test as prompted. 2. Wireless production test for the developed gateway: (1) Use a network cable to connect the gateway to a network port of the computer. Connect another network port of the computer (wired or wireless) to the Internet. Then, power on the gateway. Two green indicators on the gateway are on. (2) Set the Ethernet IP address of the local computer to 192.168.1.xxx (the last three bits need to be less than 254). The subnet mask is 255.255.255.0 by default. (3) Set the host IP address to 192.168.1.254 and port number to 12130. The network delay can be set to 200 ms. Enter the channel ID, which is 11 by default. (4) Press and hold the pairing button on the product for pairing. The pairing indicator blinks quickly, and the product enters the pairing mode. After the product is paired with the gateway, the pairing indicator is steady on for 1s and then off. 5. Click Run on the host and perform the test as prompted.
Generally, this is because the receive buffer has insufficient space. Increase the receive buffer storage capacity and try again.
If the SoC firmware is used, the current of the R, G, and B channels needs to be adjusted on the hardware, respectively. Reduce the current of the channel, of which the color has high intensity and increase the current of the channel, of which the color has low color intensity. Generally, the red channel requires a large current.
HomeKit certification needs to build products starting from scratch. You need to select the corresponding HomeKit solution, module and firmware on the Tuya platform, configure relevant hardware information, and complete the creation of PID.
For high level guidance, Amazon typically do not allow developers to feature the WWA badge on products that are distributed in countries where Alexa have not launched yet. This is because there is no easy way for these customers to access Alexa or enable Alexa skills, leading to a very poor customer experience (we have seen many customer complaints related to this).
Already support Wi-Fi and Bluetooth integrated solution, choose combo module.
The information needs to be confirmed before submitting the review. The service will be completed after the skill or action release.If you need to modify after passing the skill review, you need to operate according to the manual and submit it for review,. Or you can also purchase Tuya skill update service.
Yes, please confirm that your App account system has been bound with Tuya.
SS190 is a smart Bluetooth speaker that supports Tuya Zigbee gateway functions and universal remote control functions.
The SS190 speaker can be used as a Tuya-powered Zigbee gateway and a universal infrared remote control for IoT device control and management in many application scenarios. You can add a sub-device and an infrared signal receiver to the SS190 speaker to implement the control of various AIoT smart home devices and scene linkage. For more information, see the instructions in the Tuya Smart App.
In some cases, you may receive no response from the device in a talk. This is probably because the network connection of the device is not stable, and the collected audio fails to be completely uploaded to the cloud server. As a result, the talk cannot continue.
This function can be triggered only for specific instructions, such as the instructions for setting alarm clocks or configuring sub-devices. For example, you can say "set an alarm clock" to the speaker.
The SS190 speaker supports the functions of most speakers on the market, such as smart chatting, common skills, and voice-based music playback. SS190 supports Bluetooth-based local music playback. You can say "Turn on Bluetooth" and connect the SS190 speaker to a smart mobile phone or tablet to play music stored on the smart mobile phone or tablet. You can use shortcut commands to control music playback without using wake-up words.
SS190 supports the majority of Tuya's Zigbee sub-devices, such as multi-channel switches, scene switches, commercial lighting devices, and contact sensors.
Changing the production certificate is restricted from three dimensions: From the product dimension, you cannot change the product associated with the product certificate if: The product is being debugged. The product has no associated deliverable. The advanced features of the product have been changed. The change causes price gaps. From the deliverable dimension, you cannot change the product associated with the product certificate if: The deliverable does not support authorization. The deliverable does not support delivery based on the production certificate. A product certificate supports only production certificate splitting and product change and does not support replacing the old certificate with a new one.
Data loss may be caused by stack overflow. SDK running requires an MCU with least eight levels of stacks. It is recommended that an MCU with nine or more layers is used. Check whether your MCU meets this requirement.
Yes. To download the demo panel SDK, visit:https://github.com/tuya/tuya-panel-demo/.
The Wi-Fi network resetting command is used to clear the network status of a module. If the module is not paired with the network, this command does not need to be sent. When this command is used, the module does not need to be connected to the external network.
The 02 state indicates that the Wi-Fi network is configured but the device is not connected to the router. Check whether the router used for pairing exists, whether the router password is correct, whether the maximum number of devices allowed to connect to the router is specified, and whether the device is added to the blacklist of the router.
If the MCU does not respond to the heartbeat message sent by the module for consecutive 90s, the module will restart. After the module restarts, it starts to send the first heartbeat packet. If the MCU still does not respond, the device is displayed as offline in the app after 3 minutes.
Only responses retruned within 1 second are considered as valid.
Yes. Space authorization enables you to authorize your space to another organization account. You can set the role type to Data Operation.
To obtain the PID authorization, you need to contact the owner of the PID and provide the owner with your Tuya account. The owner adds your account on the Authorize Partner tab of the Authorizations page and assigns the PID to your account. After authorization, you can view the product on the Production page under the Purchase module.https://iot.tuya.com/purchase/index.
HLW8012 Chip Application Manual HLW8032 Chip Application Manual BL0937 ChipApplication Manual BL0942 Chip Application Manual.
It depends on the product category. You can set the Bluetooth connection interval using the connection interval setting API.
A Bluetooth module must store at least 63 records. After the number of stored records exceeds the limit, previous records will be overwritten. Each record shall contain the record generation time, which can come from the MCU or the internal module time. During each Bluetooth connection, the module time will be calibrated.
A Bluetooth module sends heartbeat messages 3 seconds before the MCU synchronizes PID information and 10 seconds after the synchronization is complete.
Tuya will perform compatibility operations if APIs are updated, and this will not affect the use of online users. Tuya will clarify the updated log information in GitHub if functions are updated.
The serial port sending buffer may be too small in size, resulting in data loss.
No. Tuya personnel will communicate with you, confirm and configure the most suitable Message Notification service plan for your app. Self-service configuration is not yet supported.
Common general integration firmware supports the baud rates of 9600 and 115200, and some products also support the baud rates of 921600 and 1500000.
First, check why the module restarts during pairing. Preferentially check the power supply of the module. Verify that the output power of the power supply meets the peak current requirements of the module during pairing. Then, check the causes for sending a string of garbled characters. 1. Check whether the module correctly sends heartbeat packets and other interactive packets after sending the string of garbled characters. 2. During the module restart, clutters may exist on the serial bus. 3. The garbled characters may also be caused because the baud rate used for baud rate detection is different from the actually used one.
No. Modules that failed to be paired cannot terminate pairing automatically. Devices not paired are in to-be-paired state. If the passive pairing mode or anti-misoperation pairing mode is enabled, the pairing is terminated after the timeout. For more information, see the 0x01 command description in the protocol document.
A module repeatedly sends this group of commands because the module is being restarted. Check whether the output power of the module's power supply meets the peak power requirements of the module.
Yes. Generally, almost every chip platform has a module that supports high temperatures. You can view module information in the document center of the Tuya Developer platform. For example, the E3L and WR3LE modules are high-temperature modules.
The Wi-Fi status 0x00 indicates that the device is in to-be-paired state and needs to be paired. Check whether the routing information used for pairing is correct, the router exists, and the routing frequency band is 2.4 GHz.
It is recommended that you check whether any fields of the data command are incorrectly encoded, for example, whether Chinese characters are used. You can use the open-source online Hex-to-character tool for conversion to check whether your data is the same as predicted.
If the pairing indicator does not flicker quickly after power-on but flickers quickly after a long press of the reset button, the module has been paired during power-on instead of in to-be-paired state. Therefore, the indicator does not flicker quickly after power-on.
Baud rate of Espressif 8266/8285 modules: 74880; Baud rate of other Wi-Fi chip platform modules: 115200. LPT: Different modules have different skill screens. It is recommended that you refer to I/O interfaces marked as "Used to print module information" in the module datasheet.
Determine pin numbers based on the module silk screen planned to be used and I/Os in the function description of the module datasheet. If GPIO1 is displayed in the function description, the data is 0x01.
When a Wi-Fi module detects that the Wi-Fi connection is disconnected, the Wi-Fi module will send the "Report network status" command to notify the MCU of the current network status.
`import { TYSdk } from 'tuya-panel-kit'; `can be called through the TYSdk module embedded in tuya-panel-kit. For more information, see https://developer.tuya.com/en/docs/iot/basics?id=Kade9hn9ied51.
If the SSID, password, or other information of the router is changed after the router is reset, the "Report network status" command will be sent to the MCU to inform it that the network status is changed.
Yes. If the module is disconnected due to a change in the SSID, password, or other information of the router, the module will keep trying to connect to the router again.
Yes. However, it is recommended that you use the AP mode or SmartConfig + AP mode. It is not recommended that only the SmartConfig mode be used.
GMT is the international standard time, with no time zone, daylight-saving time, or other regional difference factors. Local time is the time based on GMT after being affected by time zones and daylight saving time.
The firmware upgrade will apply downward compatibility. Firmware updates are not required for MCU products that have already been delivered. For MCU-connected products, you need to develop and update the MCU firmware that supports the new function.
After adding a device using the Wi-Fi general integration solution, the low field in the command "Query product information" indicates that the module can be connected for a long time with low power consumption—the module's power consumption is kept within 15 mA after pairing and stable operation.
Check whether the serial port is occupied. It is recommended that you try another serial port or disable other tools that may be using the serial port.
During module self-processing, query the MCU to set the working mode of the module and specify the I/O interface information of the corresponding function. Check the specific I/O pins against the module silk screen and the module datasheet according to the I/O interface information you specified. Connect the I/O interface to the corresponding functional hardware according to the required I/O interface and active low settings.
You can check whether the data format is correct.
This may be because the authorized products are of categories like cameras and robot vacuums, which are not directly displayed on the Product Components tab. If so, you need to purchase licenses on the Materials & Licenses tab.
62 bytes, with a 2-byte Seq.
Yes, the command will be resent upon the gateway command sending.
The 06 command is used for active data reporting, and the transmission is considered successful if a response is received from the gateway; otherwise, retransmission is available. However, the retransmission does not necessarily receive a response from the gateway. The 05 command is used only when level signals are sent.
This depends on the reason for the pairing timeout failure. The pairing timeout may be caused by various reasons. If the re-pairing has not been performed after the timeout, you can return the device to the previously paired network by setting the m field of the "Query product information" command to the anti-misoperation pairing mode. If the pairing is performed but the device cannot be routed or connected to the cloud for other reasons such as network or routing error, you cannot return the device to the previously paired network.
The Wi-Fi+Bluetooth LE solution has one more pairing method than the Wi-Fi solution: Bluetooth.
Yes, it will continuously re-send the command until the production information is obtained.
The command will not be re-sent if it is "Send commands". The command will be re-sent if it is a command for heartbeat interaction or product information query.
If the device is online when you remove it from the app, the device will clear pairing data and enter the to-be-paired state. The pairing mode depends on the n field in the "Query product information" function command. The default mode is smartconfig. If the device is offline when you remove it from the app, it cannot receive the offline command and will retain its current state. When the device is back to the online state and receives the removal information, it clears pairing data and enters the to-be-paired state or is locally reset.
If the working mode is Wi-Fi module self-processing and the I/O pin is active low, a steady-on indicator indicates that the Wi-Fi module has been configured and connected to the router or that it has been connected to the router and cloud. If the working mode is Wi-Fi module and MCU, contact the MCU manufacturer for meanings of indicator statuses.
You can use the "Disable heartbeats" function command to stop heartbeats. If you use the MCU SDK-based development solution, you can call the Wi-Fi_heart_stop function to stop heartbeats.
You can use the weather function command with the command under the weather function in the serial protocol. After the weather service is enabled, the module will synchronize weather information to the MCU at intervals of 30 minutes. The MCU can actively obtain weather data by using the command. In this case, the interval to obtain weather data cannot be less than 1 minute.
The RST pin restarts the module (turns off the module and then turns it on) and does not clear pairing data. The reset command clears pairing data and puts the module in to-be-paired mode.
Switching between pairing methods of the WBR3 module depends on the method you use in the app for pairing. If you use Wi-Fi-based pairing, select Wi-Fi. If you use Bluetooth-based pairing, select Bluetooth.
You can change the value of m to one of the following values: 0: active pairing mode 1: passive pairing mode 2: anti-misoperation pairing mode.
Pins are numbered. For example, a module has 16 pins, which are numbered from 1 to 16. I/O stands for input/output and is the function definition of a pin. I/O14 means the 14th I/O pin.
The minimum value varies with the serial data processing rate of the MCU. The faster the MCU processes serial data, the smaller the minimum value can be set. The macro definition Wi-Fi_UART_QUEUE_LMT is changed to WIFI_UART_RECV_BUF_LMT in the latest MCU SDK.
Confirm that the test equipment supports the color function, and to meet the standard Dp point definition, the control color must have the colour_data and temp_value Dp points.
Temporarily support LAN and Bluetooth channel testing.
In development, sometimes there are requirements for the version of node, and sometimes it is necessary to switch to the specified node version to reproduce the problem. When encountering this kind of demand, we need to be able to switch the node version flexibly. Nvm was created to solve this problem. It can easily switch between multiple node versions on the same device. Tuya command line tool mainly executes this command when the panel is packaged. It is recommended to install nvm and then npm to install the Tuya toolkit.
You need to be granted the administrator or developer role.
Traditional mechanical switches in China require only one live wire, but Smart Home switches require both a live wire and a neutral wire. To install Smart Home switches, re-cabling is required, resulting in huge installation and reconstruction workloads. To widely use single live wire intelligent switches, you need to solve the following cabling problems: 1. The wiring methods are different. 2. To install a zero live wire switch, you must ensure that your home is equipped with a neutral wire (identified by N, which can be confirmed by an electrician). A single live wire switch can replace a traditional mechanical switch, without the need for a neutral wire.
Analysis: 1. Hardware standards required for integration with the lock solution of Tuya: a. Reporting upon pairing b. Reporting upon power-on and power-off c. Reporting upon network reconnection 2. Required standards for the MCU (not hardware standards): a. Reporting upon unlocking b. Reporting when the lock is in the standby state c. Other reporting methods Advice: Confirm with your Tuya account manager whether the product connection protocol meets the standards.
Advice: If the network connection is abnormal on your mobile phone, you can enable Bluetooth on your mobile phone and connect the Bluetooth lock to your mobile phone through Bluetooth. If network connection is abnormal on your mobile phone, after the Bluetooth lock is connected to your mobile phone through Bluetooth, you can lock and unlock the door through Bluetooth.
The package name already exists. If the package name exists under your account, skip this prompt. If it does not exist under your account, change your package name. For details, visit https://developer.apple.com/account/ios/certificate.
This needs to print out the logs for further analysis as to confirm which working status is out of power in the network configuration process.
It is possible that the module antenna is blocked or too close to the high-frequency devices.
This is caused by the system default fonts of some Android phones. We can insert this code in src/composeLayout.js in the project: // Solve the problem that the width of Text is truncated in a certain model and certain font if (Platform.OS !== 'web') { const originRender = Text.render || Text.prototype.render; const parent = Text.render ? Text : Text.prototype; parent.render = function(...args) { const origin = originRender.call(this, ...args); return React.cloneElement(origin, { style: [!isIos && { fontFamily: '' }, origin.props.style], }); };
}.
Via mqtt network application protocol.
The development of timing function points requires the local MCU to time the clock. After the time is over, the MCU needs to report data to clear the countdown and execute actions autonomously.
Tap Clear Cache under Me Settings, and then pull down the Home page to refresh it.
The main Tuya is 2 series and 3 series modules, and the series are all pin-pin.
It is recommended that you submit your problem ticket in the upper right corner of the IoT platform homepage [Tech Support], describe your problem in detail, and our technical experts will help you answer it online.
Reason for the issue: If there is a prompt saying "unable to purchase" or "purchase failed" when clicking on the purchase or subscription button in the app, it may be because there is a cloud storage service currently in effect on the device. Process for handling issues: You can check whether the current device has an active subscription or service in the workstation.
The App displays the prompt for video deletion based on the local server time. Videos in the last hour can be partially or totally deleted.
Process for handling issues: 1. Check whether the device was working stably during the time period provided by the user, such as whether there were any offline or reboot events that affected the cloud storage event recording of the device. If there were any, inform the user. If not, proceed to the second step of troubleshooting. 2.It is recommended that users turn on the motion detection switch and adjust the motion detection sensitivity to the highest level. If there are still missed recording events, follow step 3 to troubleshoot. 3.Check if the motion detection alarm area switch is turned on, which may cause some events outside the area to not be recorded. 4. If all the above reasons have been ruled out, it may be that the changes in the screen caused by the event are not obvious enough or there is a malfunction in the device's motion detection function.
The validity of the cloud storage service and data ownership are bound to the device and user information at the same time. For example, after user A purchases the cloud storage service, the video data of the device is stored in the cloud. When user A unbinds the device and user B re-binds it, user B needs to purchase the service again, and user B is unable to view the video data uploaded while the device is under user A's account.
Reason for the issue: It is possible that the device is not in the correct home. Please confirm with the user if they have paired the device to a different home after purchasing cloud storage. If the homes are not consistent, the device needs to be paired to the home where cloud storage was purchased.
The power-off memory feature enables a Wi-Fi lamp to remember information such as the light status, color, and color temperature before it is turned off.
128.
No, it is not necessary. The tuya_mdev_test1 signal is only required when the device initially enters the production testing phase. Once the device has entered the testing phase, the signal is no longer needed.
The strength value of the signal received by the light from the Zigbee remote control during ZLL (offline) pairing.
You need to build the prototype for the BQB test into a prototype for conduction test and use the BQB firmware for flashing. Connection between the module to be tested and the serial port board: Connect the VCC, GND, TX (B1), and RX (B7) ports of the module to the VCC, GND, RX, and TX ports of the serial port board, respectively. Place the module in a shielded box (not required for a prototype for radiation test), and connect the SMA connector to CMW500. CMW500 settings: Select Low Energy for Burst Type, 1Mbps for PHY, USB to RS232 adapter for HW Interface, and 2 wire for EUT Common Protocol, and set the baud rate to 115200. After the prototype is connected, you can test it manually or by using a pre-programmed automation script. The items to be tested include the performance of the transmitter (Tx) and receiver (Rx) and signal modulation characteristics.
The minux type reporting data device should report according to the full amount after the power is increased, that is, how much is reported and how much is displayed. The type of sum is the part that reports the increment, and the panel will automatically overlay.
Wi-Fi is reported in incremental increments by default, and Zigbee is reported in full by default.
Currently, for metering products developed using no-code solutions, the undervoltage protection function can enable the protection mechanism to be triggered when the voltage remains below the threshold after 5 seconds of power-on, which will switch off the button-controlled relay.
In Bluetooth pairing, the default device name is displayed in the scan results, even if you change the device name. You can change the device name after the device is successfully paired.
If the App and module are in the same LAN, only DP data is reported. If the App and module are not in the same LAN, the App sends a command first, then DP data is reported.
The module has a low-voltage protection for the flash memory. If the voltage supplied to the module is below 2.4V, it will enter sleep mode and check the voltage every 1 second. It will only operate normally when the supplied voltage exceeds 2.6V.
On the infrared remote control of the public version LED strip solution, there are a total of 6 DIY buttons labeled DIY1~DIY6. By short pressing any of these buttons, you can execute the color stored in the memory of that button. At this point, pressing the RGB adjustment buttons (R+ R- B+ B- G+ G-) allows you to adjust the color. Once the adjustment is completed, pressing the corresponding DIY button again updates the memory value. If the color for each DIY button has not been changed, the default values are as follows: DIY1/4 default value: HSV:000 1000 1000 DIY2/5 default value: HSV:120 1000 1000 DIY3/6 default value: HSV:240 1000 1000.
By default, the name of the DP is obtained. You can customize the name in the lock management page of device panels.
According to the protocol, when the MCU reports the temporary password of the door lock, it needs to add 900 to the password number data.
Please refer to the Tuya IoT Platform documentation for detailed guidance on this topic.
Because the Wi-Fi door lock product is a low-power product, it has the logic of being permanently online.
Before embedded development, you can use the host to simulate the data reporting and sending logic of the MCU and refer to the DP functions in the following table to get familiar with Tuya's solutions quickly. Visit https://docs.qq.com/doc/DTVl0RkpjQU9heHZ2.
No. Gateways are required to use Tuya Zigbee devices.
You can purchase them in the Purchase section on the Tuya IoT Platform. Moreover, you can purchase them when you place an order for modules, plans, and licenses.You can purchase advanced features for debugging, trial production, and mass production.
Yes. After a device connects to the same network as the control panel, the control panel can control the device without an uplink network. In this scenario, the control panel reads device data from cached files to load the device. (If a device is added, the device cannot be synchronized to the control panel because Tuya Cloud is inaccessible.) Note: The prerequisite is that the control panel is connected to the network for a period of time to initialize LAN control. (After the control panel restarts, LAN control does not need to be reinitialized.).
The power DP corresponding to the product PID is not configured. You need to submit a service ticket and provide the product ID and a screenshot of the product configuration. Tuya technical personnel will solve this problem for you.
OCPP is an open protocol. Therefore, your charging station can be connected to any other platforms. A Tuya Wi-Fi module connects only to the IoT platform of Tuya and cannot be used for OCPP communication. However, you can use a Tuya 4G module for OCPP communication because it provides the AT instruction set for you to create connections to other servers. You need to choose a Wi-Fi module for custom development by yourself.
The total amount of feedback submitted by users through the App.
Each OEM app requires a new and independent account system. You cannot use your existing account system. It is possible to connect through the App SDK.
No, you cannot unlock a video doorbell or building device by using an account that the device is shared with.
Use either of the following two methods: 1. Distinguish the chip platforms based on the PID. When the product model is changed, unbind the device in the original channel and use the PID of the new product to activate the channel. Deploy OTA update for the corresponding PID on the Tuya IoT Platform. 2. Distinguish the chip platform based on the upgrade channel. Extended channels 10 to 19 are supported. When the product model is changed, unbind the device in the original channel and use the upgrade channel (TP) of the new product to activate the channel. Deploy OTA update for the corresponding channel on the Tuya IoT Platform.
Relative to the origin, moving to the right increases the value of the x-coordinate, and moving downwards increases the value of the y-coordinate. Negatives indicate the opposite direction.
Matter products have strict requirements for the format and size of the network configuration QR code label. It must be executed according to the requirements, otherwise, it may cause certification or network configuration failure issues. You can consult the project manager/FAE who is working with your company for specific specifications.
If the module being burned is not an empty module, RF calibration is required when burning a new version; if the module being burned is an empty module, you can directly burn the required version without RF calibration.
The Matter protocol was initially developed by industry giants such as Google, Apple, and Amazon, and now has over 400 companies participating in the development of this standard. The participating companies are mainly divided into three categories: "Promoters", "Participants", and "Adopters". There are a total of 29 "Promoter" companies, which have contributed some of their proprietary technologies to some extent. In addition to the influential Amazon, Apple, and Google, domestic manufacturers include Huawei, Haier, Midea, OPPO, and Tuya Smart. "Participants" have the relevant authority to set standards and can obtain draft specifications and conduct tests earlier, making them part of the protocol standard. "Adopters" mainly refer to companies that develop products using existing, approved standards. "Promoter" member annual fee: USD 105,000 "Participant" member annual fee: USD 20,000 "Adopter" member annual fee: USD 7,000 If you are planning to launch a small number of Matter-related products to test the market, applying to become a "Provisional Member" and obtaining certification transfer from a professional Matter technology solution provider is a relatively lower-cost approach. Becoming a provisional member is free of annual fees, and the cost of transferring product certification is much lower than the annual fee for becoming an "Adopter Member".
Yes. Therefore, for products that need to be installed in inconvenient locations such as roofs, the location of the networking QR code should consider the convenience of customers.
The power-off memory takes effect for at least 5s.
Basic functions: dimming, color adjustment, key reset, power outage memory, mesh remote controller.
Universal knowledge of my product is used to maintain the general knowledge of a product category or all product categories. You can create knowledge in this knowledge base or reference knowledge from Product universal knowledge of Tuya. Universal knowledge of a product category: Scenario Knowledge Maintenance App Display Products of a category have both general and personalized knowledge. Step 1: Maintain the general knowledge of this product category in Universal knowledge of my product. Step 2: Maintain personalized knowledge in product knowledge bases. Step 3: Reference or copy general knowledge of this product category to all product knowledge bases of this product category. Referenced general knowledge and personalized knowledge in product knowledge bases Products of a category only have general knowledge and do not have personalized knowledge. Maintain the general knowledge of this product category in Universal knowledge of my product. The product knowledge bases do not need to be maintained. General knowledge of this category in Universal knowledge of my product General knowledge of all product categories: If the products of different categories under your account have general knowledge, such as the warranty period and warranty scope, you can place knowledge applicable to all product categories to Universal for all categories under Universal knowledge of my product and then reference the knowledge to all product knowledge bases. Display sequence in the app: Knowledge in product knowledge bases Knowledge under a specific product category of Universal knowledge of my product Knowledge in Universal for all categories under Universal knowledge of my product When specific knowledge cannot be found in the product knowledge bases, the knowledge will be searched from other knowledge bases based on the preceding sequence. In a word, Universal knowledge of my product helps you quickly optimize the product knowledge bases. When specific knowledge is not found in the.
Product universal knowledge of Tuyamaintains all-in-one product knowledge applicable to a product category or all product categories for your reference. For knowledge not maintained in product knowledge bases or Universal knowledge of my product, knowledge in Product universal knowledge of Tuya will be displayed in the app.
2 Mbit/s.
Yes, you can use IP cameras (IPCs) to format memory cards.
Yes, you can remove the memory card from an IP camera (IPC).
Yes, you can integrate the tamper alarm function into IP cameras (IPCs). To implement this function, you must configure the required DPs. Reference documents：https://developer.tuya.com/en/docs/iot-device-dev/IPC_custome_function?id=Kb0lbwks8ta2u#title-34-Tamper%20alarm.
Yes, you can configure display settings for the indoor unit.
For IPC SDK 4.9 and below, the maximum bitrate is 1.5 Mbit/s. For IPC SDK above 4.9, the maximum bitrate is 5 Mbit/s.
Can customize the panel by removing the manual control section.
Depending on the panel used, gyroscopic sweeping robot public panel needs to be reported.
The phantom color effect requires the use of SPI pins. The SPI pins of the CB2S have not been led out, so the phantom color effect cannot be realized.
The platform free development firmware shields the small power and small current. When the measured power is less than 3W, it will be filtered out. At this time, the app shows that the power and current are all 0. However, electricity consumption is counted in the accumulation.
1mΩ — 5mΩ 5 types are available. It is generally recommended to choose 1 milliohm. If you choose 1mΩ when creating the product, you must stick a 1mΩ resistor on the hardware. If you choose 2mΩ or other resistance, there will be problems.
Yes.
The data length of the scenario mode sent from the cloud to the gateway is 2 + 26*n, n=8, which is up to 210 bytes. However, a single message of the Zigbee sub-device cannot exceed 70 bytes, in this case, the scene mode data needs to be compressed. The data length after compression is 2+8*n, n=8. The maximum length is 66 bytes.
The recommended Bluetooth wireless gateway is CR3L.
Ensure that the App is granted with the microphone permission. To use the Dance to music function, you need to enable the microphone permission. When you tap the Dance to music function in the panel, the microphone starts to pick up sound and data is then delivered.
A software development kit (SDK) contains materials required for software development, including documents, demos, and tools.
Products that use the low-power firmware, such as the remote control (key7gtvr), or multiplex the serial port, such as the solar light (keynnshp) and motion sensor light (key5wvvr), can be properly authorized after the Prod beacon is enabled.
Normal mode: WCM_OLD, Low power consumption mode: WCM_LOW_POWER, Special distribution mode: WCM_SPCL_MODE, Compatibility mode: WCM_OLD_CPT.
Call the GW_STAT_E tuya_get_gw_status(VOID) function against the GW_STAT_E structure.
Mainly C library and C++.
There is currently no cloud backup and recovery mechanism. The locally generated db file cannot be deleted. The db file saves verification, activation information, local timing and other information.
Chip platforms except PHY6222, TLSR8250, and nRF52832 do not support flashing using the production credential.
Beacon is a broadcast communication protocol based on the Bluetooth LE protocol. Beacon devices are low-power Bluetooth slave devices that use this protocol. In general, Beacon devices are placed at a fixed position indoors and broadcast a data packet to surrounding devices at intervals. An independent Bluetooth master device will receive data packets broadcast by Beacon devices at intervals during scanning. Tuya Beacon is a private protocol based on the preceding principles and is different from the standard Beacon protocol.
Dear user, we are sorry for your inconvenience. You can purchase cloud storage service based on your requirements. For example, if you purchase a 7-day event package, the cloud stores your videos from the latest seven days and deletes the videos that have been stored for longer than seven days. Event recording mode and continuous recording mode are different in how they trigger the video upload. An event recording mode uses the event triggering mechanism, that is, when a device detects a change in a video image, it uploads the video data to the cloud. A continuous recording mode uses the continuous upload mechanism, that is, a device continuously uploads video data to the cloud 24 hours a day. The service may be valid for one month or year. Within the service validity period, you can view videos stored on the cloud. Based on the above characteristics, you can choose according to your personal needs.
Dear user, we are sorry for your inconvenience. Please provide your App account and device ID, we will check it fo you. Thanks for your support.
If you wish to set the timer in a 24-hour or 12-hour format, you can select either option in your phone's settings (Settings - System Management - Date & Time - 24-hour format). Then, the timer in the app will also display in the chosen format. If changing the device's time format doesn't affect the timer display, you can try clicking on the device page and check if there is a time setting option available to modify. If such an option doesn't exist, it is possible that the device itself does not support adjustment of the time format. Note: If it is a 12-hour system, there will be AM and PM options next to the time for selection. After the mobile phone time format is changed, the time format of the history records (message push, device usage record, and video recording, etc.) in the App will not be changed. Only records after the time format changed will use the new time format.
Dear user, we are sorry for your inconvenience. Alexa does not support the voice control of Wi-Fi groups created in this App (Bluetooth groups are supported, but it needs to be used with a Bluetooth gateway). It only supports the voice control of groups created by itself in the Alexa App. After synchronizing all Wi-Fi devices to Alexa App, you can create a group of Wi-Fi devices in Alexa App, so that you can use Alexa to control the voice. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. If you do so: Open the App, click the device icon to enter the device control panel (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be controlled). Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of DingDong (If not found, the device is not supported). After jumping to the connection page, bind according to the instructions of the App (You can also click to view the tutorial). One DingDong account can only be bound to one App account, an error will be reported if the binding is repeated. Since each third-party smart speaker is a closed platform, and therefore it is not possible to discover the device and directly connect it through the Dingdong App nor the "Discover Device" function. It have to achieve connection by binding skills. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. If you cannot find the device in Google Assistan App, please make sure that the device is supported by Google Assistant (enter the device control panel and tap the top right button, the support list is under Third-party Control), then please confirm that your account has linked to Google Assistant is correct (the same as the App which registered the devices your want to controlled by Google Assistant). Please make sure that the device is online (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be synchronized). If your problem still exists, please provide your device ID to us, thank you for your support. Have a nice day.
Dear user, we are sorry for your inconvenience. If you do so: Open the App, click the device icon to enter the device control panel (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be controlled). Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of Google Assistant. (If not found, the device is not supported). If you want to link your camera and camera monitoring screen to Alexa Echoshow/Google Home Hub, but you can't succeed, then you need to contact the device seller to activate this feature for you (for your privacy, this feature is mostly closed). After jumping to the connection page, bind according to the instructions of the App(You can also click to view the tutorial). One Google Assistant account can only be bound to one App account, an error will be reported if the binding is repeated. If your device has recently been offline, upgraded firmware, or completely powered off, you need to repeat the above steps to add the device again, otherwise it may not be able to work with third-party smart speakers (This is because the firmware upgrade and power failure will cause the device to be offline. After the device is back online, the third-party smart speaker sometimes cannot obtain the real-time status of the device, so the third-party smart speaker will think that your device is still offline, and this problem can only be solved by adding it again). Notice：Since each third-party smart speaker is a closed platform, and therefore it is not possible to discover the device and directly connect it through the Google App nor the "Discover Device" function. It have to achieve connection by binding skills. Thank you very much for your understanding and support！ What can I do if my App account cannot be bound with Google Home or Google Action? Cannot connect the device in the Google? Why can't my App account co.
Due to policy restrictions, Google Assistant cannot be used for Chinese App accounts. Please switch between the US App account or the European App account.
Dear user, we are sorry for your inconvenience. Please check in the following ways: If you move your camera to another home, the playback in the previous home will not be found and viewed. If you need to view it, you need to move back your camera to the original home. Generally, the camera's inability to view the video/record is related to your poor network status. Whether you are viewing the video in the SD card or the video in the cloud storage, you need a good network status to be able to stream the video stored in the camera to your App. Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), smart camera equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps), If your device has enabled motion detection and cloud storage functions, each function requires additional 2M uplink bandwidth. Please confirm that your network has sufficient network bandwidth.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), smart camera equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps), if your device has enabled the cloud storage function, additional 2M upload bandwidth is required, please confirm that your network has sufficient network bandwidth. The Wi-Fi signal of the device is too poor (for example: there are several walls separated from the router; the device is surrounded by a metal shell or there are metal objects nearby; nearby high-power Appliances such as air conditioners and refrigerators interfere) The location of the device is too far away from the router (the indoor environment is more complicated, it is easy to go offline after more than 5 meters; the outdoor environment is empty, it is easy to go offline after more than 10 meters).
When connecting to Wi-Fi, most webcams only support Wi-Fi 2.4G, and a few dual-mode webcams support 5G networks. Ask the seller whether they support it or not. For security reasons, not all webcams can be connected via mobile phone hotspots. If you support. Ask the seller whether they support it or not.
Devices that support rotation typically have obvious directional control buttons on the panel. Please check if there are directional control buttons on the device panel. If so, you can adjust the rotation. If there are relevant functions but the camera cannot rotate, it is recommended to contact the hardware after-sales service of the vendor. Note: The boundaries of rotation are usually set by the product itself and cannot be adjusted. If your product does not have a rotation function, you can only adjust the angle of the product itself.
Dear user, 1. The problem may be caused by a problem with the Wi-Fi network. Switch your mobile device's network from Wi-Fi to data. If the video streams normally using your phone's data, your Wi-Fi network may be to blame. You can follow the steps below to troubleshoot: Check the router settings: a. The frequency band of the router is set to 2.4GHz. b. The encryption mode of the router is set to WPA/WPA2 mode. c. Wireless access control is turned off and the black and white list option is cancelled. d. The DHCP server has been enabled. e. It is recommended not to modify the Mac address. f. The Wi-Fi name and password of the router are set to English + number. 2. Please update the App to the latest version. 3. Please ensure that the version of your mobile phone system is running 10.0 or higher if you are an iOS user. For Android users, please ensure that your mobile phone is running Android 5.0 or higher. 4. Check the network environment: You can download network speed test tools and test the network upload and download speed of the location. a. Make sure the upload speed is at least 2 MB/s, download speed is at least 2 MB/s or upload 16 Mbps, download 16 Mbps. b. A single camera requires 8M upload bandwidth, two cameras need 16M, and the bandwidth stacks by the number of cameras. c. Please ensure that your network has enough bandwidth (uplink bandwidth in China is more than 20M, other areas are mostly 50-100M. If you have tried using your mobile data or the above operations still do not fix your problem, please contact our support team. We will provide you with further assistance.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Since this is caused by network instability, it is recommended that you try again when the network is good or switch the network, and upgrade the firmware and App versions to the latest. Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), smart camera equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps), if your device has enabled the cloud storage function, additional 2M upload bandwidth is required, please confirm that your network has sufficient network bandwidth. Our product does not support saving video after it detects movement. You can view the pictures captured by the camera in the message center (If you have purchased cloud storage, you can see the video of the detected movement in the cloud storage). Your mobile phone system version does not meet the requirements of the App (Requires iOS≥V10.0 version, Android≥V5.0 version) If the problem persists, please submit a ticket and provide a screenshot of this page for further troubleshooting.Thank you for your understanding and support!
Hello, please troubleshoot according to the following methods: It might be caused by too low detection sensitivity. It is recommended that you go to the settings page to adjust the detection sensitivity; Please make sure the network environment where the device is located is strong and stable. Troubleshooting method: download a network speed testing App, place your mobile phone at the same position as the device, and then test the upload and download speed of the network at this position (ensure the speed is at least: upload≥2 MB/s, download≥2 MB/s or upload≥16 Mbps, download≥16 Mbps); smart cameras consume a large bandwidth, and at least 4M of bandwidth is required for 1080p quality (0.5MB/s, 4Mbps). If you have activated the cloud storage function for your device, an additional 2M bandwidth is required for uploading; please confirm your network has sufficient bandwidth; The region where you currently live is inconsistent with the region selected when registering the App account, causing the cloud server you access when controlling the device is far from your residence and causes high latency; If none of the above is the issue, you can send us your issue through Help and Feedback.
After you close the door, others cannot open it unless they have the correct fingerprint, password, or key. If you have enabled the automatic locking feature, the door will lock automatically upon the preset time.
Possible causes include: The hardware does not support the temporary password feature, and the embedded wireless module version is too old. The gateway is incompatible with the device. Change to a newer gateway. The gateway firmware version is earlier than 1.1.9. Upgrade the gateway firmware. If a temporary password fails to unlock the smart door lock, perform the following steps: View the temporary password status in the App to check whether it was configured successfully. Check whether the password took effect. Provide the device virtual ID to Tuya technical support for troubleshooting.
View the temporary password status in the App to check whether it was configured successfully. Check whether the password took effect. Provide the device virtual ID to Tuya technical support for troubleshooting.
Check whether the door lock is a Wi-Fi door lock. Check whether network pairing was performed as instructed. Change the network pairing mode from the EZ mode (indicator blinks quickly) to the AP mode (indicator blinks slowly) in the App and on the device. For details on how to change the network pairing mode on the device, see the user manual. Check whether the door lock is connected to a 2.4 GHz Wi-Fi network. If the problem persists, place the door lock closer to the router (within 5 m if there are no obstacles).
It is possible that the lock body is not compatible, in which case you should replace the lock body. The motor may not be functioning and could be damaged. Contact the sales channel for after-sales support. Some door locks support the "always open" mode setting. Usually, you can enter the system settings on the lock screen and open/close the "always open" mode. Please refer to the instruction manual for specific guidance. If you are unable to complete the "always open" setting, you can restore the factory settings. Please refer to the instruction manual for specific instructions. Access the system settings on the door lock screen and choose the option to restore factory settings, or refer to the instruction manual for guidance and long-press the reset button on the door lock.
Check whether the door lock is a Zigbee door lock. Check whether network pairing was performed as instructed. Check whether the gateway is compatible with the door lock. If the problem persists, place the door lock closer to the gateway (within 5 m if there are no obstacles) to ensure normal wireless communications.
Dear user, because the Wi-Fi door lock is usually in a dormant state, it does not support remote unlocking directly in the App. But you can let the visitor ring the doorbell in front of the door to initiate a remote door opening request. After you receive the notification from your mobile phone, you can agree or reject the remote door opening after confirming the identity of the visitor.
Dear user. The length of time that the "device record" in the device control panel can be saved and the maximum record limit that can be saved per unit are set by the product manufacturer . If you think the "device record" function does not meet your needs, you can report this problem to the product after-sales party so that they can make improvements later. Thank you for your support and understanding. Note: If your device cannot update the device record for a long time, it may be that your device is offline. Please reconnect to the network.
If the camera device has a rotation function and is equipped with direction control buttons, you can freely adjust the rotation direction of the camera through the control buttons. These buttons are usually located on the device panel, used to let you remotely control the direction of the camera. However, if your camera device does not support the rotation function, or you cannot find the corresponding direction control buttons, then you may not be able to adjust the rotation direction of the camera through the App. In this case, you may try to manually adjust the camera angle, if you cannot manually adjust, you need to contact the seller or device after-sales, to learn more about the camera's function and hardware limitations.
The cloud storage function of the camera is a service that uploads the dynamic event videos detected by the camera to the cloud for video storage in real time. Users can view and download videos anytime and anywhere through the network, without worrying about video data loss. The advantages of this function include: Convenience: No matter where you are, as long as you have a network connection, you can access the videos stored in the cloud. Security: Since the videos are stored in the cloud, even if the camera or local storage device is damaged or stolen, your videos are still safe. Capacity: Cloud storage usually provides a large amount of storage space, far exceeding the traditional hard disk recorder or memory card. Please note that the cloud storage service requires a stable network connection to work properly. If the network connection is unstable or too slow, it may affect the upload and viewing of videos. I hope this answer is helpful to you!
If the buttons on the remote control don't work after the robot turns on, there are several possibilities: if the remote control doesn't work, but the robot can find the charging base normally, that would be the remote control is out of power or damaged; if the remote control doesn't work, and the robot doesn't rotate to calibrate when looking for the charging base, it means that the receiver head on the robot keypad/display board is malfunction, you need to replace the keypad or receiver head. You can find the seller to submit an after-sales Application.
If the main brush rotate and the side brush does not rotate, or both the main brush and side brush do not rotate, there may be several reasons: check if there is any foreign substance wrApped around the rotating part of the brushe, If there is, remove the foreign substance and check again; If both the main brush and side brush do not rotate, loosen the screws to see if the brushe rotate normally after starting the robot; If none of the above methods work, please contact the seller for after-sales service.
Charging the robot will not affect its networking function. If there is an abnormal offline problem, it is recommended to check the relevant network FAQ in the manual or App.
Possible causes for this issue include: Low detection sensitivity. We recommend that you go to the settings page of the device to adjust the detection sensitivity. Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), smart camera equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps), if your device has enabled the cloud storage function, additional 2M upload bandwidth is required, please confirm that your network has sufficient network bandwidth. The region where you live now is not the same as the region you selected when you registered your App account. As a result, the cloud server you access when controlling your device is far away from your place of residence, resulting in high latency. Our cloud server is not able to cover the area where you live, causing high latency between the cloud server you need to access and your device. If both the detection sensitivity and network signal are good, report this issue to us.
Yes. In scenes with high security requirements, we recommend that you choose phone or message notification in Automation.
Dear user, we are sorry for your inconvenience. Yes, it is, you can open/close the curtains to the extent you want through the device control panel. However, the voice operation requires the support of your device, which is determined by the device manufacturer.
Dear user, sorry for the inconvenience. If you want to know if the device is offline in the App, please open the App and see if the device Appears offline in the list of devices in the App. Thank you for your support.
Dear user, sorry for the inconvenience. If the device cannot power through, could you please try to use other device to test whether the device can power through. If not, it maybe something wrong with device. you need to contact the vendor or manufacturer to deal with it. We are from the App side, sorry for not help you about the problem. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. If you do so: Please reset the device to factory settings first. Uninstall the App, and then reinstall the App to your phone. Then add the device to the App again. If this problem still occurs, there may be a problem with the device hardware, please contact the after-sales personnel to handle after-sales for you. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Read the product manual or the instructions on the network connection page and strictly follow the steps. If your device still fails to enter the network connection state, check whether your device is powered on and turned on and whether the indicator is steady on. If the issue persists, you may need guidance on troubleshooting hardware products. Contact your product’s after-sales service personnel. Thank you for your understanding and support.
Dear user. If you do so: Open App, tap the device, and go to the device control panel. Tap the icon in the upper right corner, and then tap Basic Function Settings—Disable Status Indicator/backlight. If you cannot find Status Indicator on this page, the device may not support this feature. For more information about the device features, see the user manual. If you want this option, you can feedback this problem to the after-sale person so that they can improve it later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. If you do so: 1. On your iPhone, open the Watch App. 2. Tap the My Watch tab. 3. Scroll to the App you want to add. Apps you can install Appear in the Available Apps section. 4. To add an App to your watch, tap Install. If you encounter problems during the operation, you can submit a Question, and we will have professional technical experts to troubleshoot the problem for you.
Dear user, we are sorry for your inconvenience. If it is a normal Bluetooth device, it does not support group control. If it is a Bluetooth Mesh device, when it is near the Bluetooth Mesh device, the Bluetooth Mesh group device control does not require a Bluetooth Mesh gateway. If you need to perform remote operation (for example: you are not within 5m of the Bluetooth Mesh device) or use the timing function, you need to use a Bluetooth Mesh gateway.
Dear user. The convenient operation/shortcut operation of the device belongs to the extended function, and you can quickly use these functions to control the device and understand the working status of the device without enter to the device control panel. This extended function is set by the product's producer, If you want this function, you can feedback this problem to the after-sale person so that they can improve it later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. Device information is bound to your App account. You can use it to log in to the App and control Bluetooth mesh devices under the account, regardless of which mobile phone you use. To use multiple mobile phones to control devices, use the same account to log in to the App on these mobile phones.
Dear user, we are sorry for your inconvenience. Please check in the following ways: This is because all the setting pages and function pages (such as: timing, countdown, scenes, etc.) in the device's console are based on cloud services, so if your network is in poor condition, it will open slowly It even cannot be opened normally; Please make sure the signal of the network environment where the device is located is strong and stable. Troubleshooting: Use the Internet Speed Test App to test the upload and download speed of your network (upload ≥ 2 MB/s, download ≥ 2 MB/s, upload ≥ 16 Mbps, download ≥ 16 Mbps); If the problem persists, please provide your App version number and device ID, and we will help you troubleshoot the problem as soon as possible.
The theoretical transmission rate is 250 kbit/s.
A smart gateway is used to connect devices that use IoT protocols, such as Zigbee, Bluetooth, and Sub-G, to the Internet. It implements remote device control and reporting, local device management, local automation, and other functions.
At present, the Zigbee gateway supports Zigbee3.0, which is compatible with ZHA.
Tuya wired Zigbee gateways support the star, tree, and mesh topologies.
The gateway MCU interconnection solution refers to the way that the Tuya module and the developer’s MCU communicate through the serial port. The Tuya module provides cloud connection capabilities and sub-device management capabilities. The development of specific gateway services and protocol types is completed by the developer’s MCU.
This may be caused by the wrong authkey and UUID or the unadapted network interface. It is recommended that you verify the authkey and UUID uploaded to the device and check whether the network interface is adapted.
Definition of network port indicator status: 1. Plug in the Internet cable: the indicator light is always on 2. The network cable is not plugged in: the indicator light is always off 3. It will flash when there is data Distribution network indicator status definition: 1. No network configuration: the indicator light is always on 2. With Internet access: the indicator light is always off 3. When gamete equipment: flashing.
SDK is not a stand-alone program, it is provided to a third party system in the form of C static library (a file), and the third party system is responsible for the initialization and termination of the SDK as the host program. So to get SDK, user needs to provide corresponding compilation toolchain to generate, and the generated host program needs to run in the Linux environment, the communication between SDK and the third-party system can be achieved through function calls.
It can connect 32 low-powered devices, or 35 strong-powered devices as well as 15 low-powered devices.
Tuya charging stations communicates with Tuya cloud servers over the Open Charge Point Protocol (OCPP). At present, OCPP 1.6-J is widely used. The applicability of the latest OCPP 2.0 is under research. A charging station using OCPP 1.6-J connects to a server over WebSocket and transmits data in the specified format and logic. To use the Tuya Things Data Model (TDM) for App and SaaS development, we have developed the OCPP gateway, which links TDM DPs over the OCPP protocol. This way, an OCPP charging station communicates with other Tuya devices in the same way, making the development easier for App and SaaS developers.
Currently our Zigbee devices can only connect to Tuya's gateway.
Because a single gateway supports up to 128 sub-devices, but the number of sub-devices added in batches does not exceed 32 at a time.
The module will judge according to whether it joins the Bluetooth gateway. When the connected mobile and the gateway exist at the same time, the Bluetooth device will give priority to the local connection.
Different Bluetooth mesh gateways support different pairing methods, including AP pairing, Bluetooth pairing, and wired pairing.
The working temperature is -10℃ to 55℃.
No, it does not support.
The gateway device provides a communication bridge between the Zigbee device and the network router.
Yes. DP 173 is added to set the warning duration for light-on, that is, light-on delay. For more information, visit https://developer.tuya.com/en/docs/iot-device-dev/floodlight_pir_solution?id=Kay7sbwfcv7mh#title-6-%E7%81%AF%E5%85%89%E6%8E%A7%E5%88%B6.
No. Third-party smart speaker access services such as services for connecting to Amazon Echo, Google Home, and Tmall Genie, are enabled by PID on the cloud. You do not need to reburn the firmware. These services will also be enabled for sold products. Before selling the product, it is recommended that you confirm the functions to be supported by the product, and complete the corresponding configuration and testing.
Check whether this PID is under your current account. If not, you cannot find the PID. If yes, click Support and submit a ticket. Our technical support personnel will help you troubleshoot your problem.
Up to 30 remote controls can be added. However, only one remote control can be used at a time.
Reporting only: It means that the data can only be reported from the device and cannot be sent from the cloud. Sending only: It means that the data can only be sent from the cloud, and the reporting of MCU is not supported.
The data length of the Boolean DP is 1 byte.
When creating a product, you can enable the timing function in the cloud function settings area. If the timing function has been enabled but is not displayed on the app, a fixed panel does not support the timing function. You can select a code-free or custom panel template.
Power-off memory refers to the state that it was restored to the state before the last power-off every time it is turned on, but this state must be kept for more than 5 seconds before it is turned off before it is remembered.
This is because you do not select firmware. You need to select firmware before downloading the data point debugging file.
Varistors are used to protect against lightning surges.
If it is a composite distribution network button, it can be shared directly.
The IO port on the module is for the configuration of the no-development solution. You need to create a no-development product on the platform, and the firmware needs to be configured under product creation-hardware debugging. After configuring the firmware, the modules ordered and purchased will be configured according to the IO port on the platform, input or output the corresponding signal. Reference document: https://developer.tuya.com/en/docs/iot/device-development/access-mode-soc/soc-guide/soc-dev?id=K989r8sw7lk61 If it is a custom solution, the module only serves as a transparent transmission, and only VCC, GND, TX, and RX will be used on the module hardware. The driving circuit is driven by the MCU's IO port, and there is no need to use the module's IO port.
The schematic diagram of the module belongs to internal information and cannot be provided at will. If product certification is necessary, please submit a work order for application. The product schematic diagram is also internal information and cannot be provided at will. You need to ask your business manager to make a corresponding application before you can obtain it. If you do not have a business manager, please check the cooperation process.
Dear user, we are sorry for your inconvenience. You can configure the network in the following ways: Locate the wireless gateway (Zigbee) under the category "Gateway Control" Make sure the gateway is powered on, and make sure that the phone is connected to 2.4GHz Wi-Fi Press and hold the reset button of the Zigbee gateway for 5 seconds Until one of the two indicator lights enters a fast flashing state (red light flashes, blue light is always on) Follow the instructions in the App to configure the network Note: When connecting the gateway, make sure that the mobile phone is connected to 2.4GHz Wi-Fi, otherwise the gateway cannot be registered through the cloud, and the connection cannot be successful.
App adding device methods: Wi-Fi Fast Connection (EZ mode), Hotspot Distribution Network (AP mode) These are suitable for Wi-Fi devices, in addition to wired device distribution network, gateway sub-device distribution network, dual-mode device distribution network, Single-point Bluetooth distribution network, scanning QR code distribution network, NB device distribution network, Lightning distribution network, Sigmesh distribution network, TuyaMesh distribution network.
Connecting Bluetooth Devices to a Mobile Phone: Turn on the Bluetooth and location switches in the phone system to ensure that the App has obtained Bluetooth and location permissions. Read the device manual and set the device to pairing mode. Go to the App homepage, click the plus sign in the top right corner to enter the device adding page, and the App will automatically search for nearby devices in pairing mode. If the device is not detected automatically, please choose to manually add the device. Manually Adding a Bluetooth Device: On the App homepage, click the plus sign in the top right corner to enter the device adding page, select the corresponding category, and set the communication method to Bluetooth. Turn on the device, confirm that the indicator light starts flashing, click Next, and wait for the connection. Connecting Bluetooth Sub-devices to a Bluetooth Gateway: Select the Bluetooth gateway device you want to connect to in the device list on the App homepage. Enter the device control interface, click on the bottom to add a device. Ensure that the sub-device is in pairing mode, with the indicator light flashing. If the indicator light is not flashing, please reset the device. Wait for the connection to be successful.
You can set an SSID containing up to 32 characters.
Dear user, the following are the types of devices that support network search. Please confirm whether your device is in the following types: Wi-Fi devices: Only Wi-Fi devices that support lightning network distribution and have HomeKit functions can be discovered in Auto Scan. App location permissions need to be turned on, and mobile phones need to be connected to Wi-Fi. Wired device: the mobile phone and the device need to be under the same router. Bluetooth device: need to turn on Bluetooth and App location permission (Wi-Fi & Bluetooth dual-mode devices can be searched through Bluetooth, so the mobile phone needs to turn on Bluetooth). Zigbee sub-device: Zigbee gateway needs to be configured. If you have multiple Zigbee gateways, you need to manually select the Zigbee gateway.
Dear user, we are sorry for your inconvenience. As it has something to do with the network stability whether the device can work normally, please make sure your network is stable and not overloaded. Maybe you can use a phone hotspot to check whether it is the problem of network. Besides, you are suggested to upgrade your App. Thanks for your support.
Dear user, we are sorry for your inconvenience. After changing the Wi-Fi password, all network settings have been changed. Therefore, you need to reconnect all the Wi-Fi devices and wireless gateways (including Zigbee and Bluetooth gateways). But those devices which under the wireless gateways (including Zigbee and Bluetooth gateways) are not required for reconnection. You can also use Auto Scan mode to add multiple devices at once.
Dear user, if you want the App to be able to read the Wi-Fi SSID directly, you need to open the App's location permission. If the App do not have the location permission, you need to manually enter the Wi-Fi SSID when pairing device. If you want App to save your Wi-Fi password, you only need to successfully pair any device for once, then the App will automatically save the Wi-Fi password. If you fail to pair any device, the App will not save the Wi-Fi password.
Please check in the following ways: Check whether the device is offline, if it is offline, you need to remove the device from the App and add it again. If your device is a low-power device (devices that use battery and various sensor devices), in order to ensure battery life, the low-power device will only display offline in the App after it is offline for more than 24 hours, so it is very likely that your device has already offline, but you don't know. You need to readd it. If the device still has problems after re-configuration, we recommend that you reset the device to factory settings in the App and remove it, and then add it again; Please check whether the distance between the device and the router (no more than 5 meters without separation, no more than 2 meters with walls, metal objects, etc.) is too far, causing loss of signal transmission. To solve this problem, it is recommended that you remove the device first, then reset the device to the network configuration state and perform network configuration again. Please keep the network signal good during the connection process. Confirm whether your account is in the correct region. If the region is selected incorrectly, the cloud server registered by the device is far away from you, which will cause a great delay and cause control failure. If the problem persists, please provide the App version number, the virtual ID of your device, and we will troubleshoot the problem for you as soon as possible.
Dear user, we are sorry for your inconvenience. If you do so: You can use the home function to put the device in different homes, because the devices added in the App do not have to be under the same Wi-Fi (local area network). You can also add these two devices to the same home, because the devices added in the App do not have to be under the same Wi-Fi (local area network).
Dear user, we are sorry for your inconvenience. If you do so: Tap "Me — the Settings button in the upper right corner" to enter the settings page. Tap Account and Security, and tap Pattern Lock on the page that Appears. Then you can record your pattern lock to enable this feature. When pattern lock is enabled, you must draw the same pattern every time you log in to App. If you forget the pattern, tap Forgot Pattern Lock in the lower part of the page. It will let you login the App again, and then you can record your new pattern lock.
Dear user, we are sorry for your inconvenience. Our App supports the use of multiple mobile phones and multiple platforms to log in to one account at the same time. Therefore, all device data under the account will be uploaded to the cloud and synchronized to all phones logged in to the account (whatever iOS or Android). If you encounter a situation where the timing or countdown cannot be synchronized, it is possible that you are using a Bluetooth device and you have not connected the Bluetooth device to the Bluetooth gateway.
Dear user, we are sorry for your inconvenience. If it is a timing in the scene, you can delete the timing in the following ways： Open the App. Click the Scene button at the bottom of the homepage. On the Automation page, click the "" button on the timer box. Click the More Settings button at the bottom. Click Delete. If it is the timing in the device control interface, you can delete the timing in the following ways: Open the App. Click the corresponding device in the device list. Click the timer function in the control interface. Long press or swipe left to delete the timing. Hope the steps can solve your problem. If you delete the timer, but the device still executes the previous timer, you need to restore the device to factory defaults and add it again (restore factory defaults button is at the bottom of the device setting page). Thanks for your support.
Dear user, we are sorry for your inconvenience. If you do so: Open and check your automation,whether the effective period has been set. If yes, you can change it. If no, It is recommended that you delete the original automation then edit a new one so that the task will perform accurately. If the problem still exists, please try to remove device and readd it. Thank you for your understanding and support!
The interfaces for querying the weather always prioritize using the location's latitude and longitude, and only resort to using the IP to query the weather in scenarios where location permissions are not enabled.
Go back the phone settings page: Click on "Battery" - disabled the option "Power saving mode" and "High performance mode" (After opening these two options, the system will block many notification messages). Click to enter "App battery management" and find the App. Open all the switchs.
Dear user, we are sorry for your inconvenience. First, check whether all the devices under your account have activated Baidu service. If yes, speak to your DuerOS smart speaker: find devices. Only devices found by the smart speaker can be synchronized to the App (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be synchronized).
Dear user, we are sorry for your inconvenience. This problem is caused by a delay in communication between our cloud server and the cloud server of a third-party smart speaker. Since each smart speaker has its own cloud server, when you want to use the smart speaker to control the devices on our App, this control instruction must first be sent to the smart speaker's cloud server through our cloud server, and then this instructions will be returned from the smart speaker's cloud server to our cloud server, and then sent to your router / mobile phone. And if you directly control the device through our App, you only need to send commands directly through our cloud server, so there is no delay. There is no way to solve this delay, so if you are more concerned about the delay, we recommend that you use our App directly.
Dear user, we are sorry for your inconvenience. Bluetooth products need to be equipped with a bluetooth gateway to achieve voice control.
Dear user, we are sorry for your inconvenience. The control quantity of the Wi-Fi remote control is related to the load capacity of your router. The number of normal routers is 10 to 30. The quantity that can be controlled by the Bluetooth and Zigbee remote control is 30.
Yes. A Zigbee wall SoCket supports multiple control modes, such as local button control, sensor control, and remote App control. When the wireless network is disconnected, you can still use the local button, asSoCiated sensor, or gateway to control a Zigbee wall SoCket.
Since the water heater only circulates the cold water in the main pipeline for heating, and the cold water already exists in the branch pipe is unable to circulate heating, so there will be a section of cold water after opening the faucet, which is a normal phenomenon.
Even if you don't have Wi-Fi at home, the smart water heater works normally, so you can use it with confidence; In the presence of Wi-Fi, the smart water heater can be controlled remotely, allowing you to have a better experience with the product.
No. You need to use the 2.4 GHz Wi-Fi network of a wireless router or mobile phone hotspot to connect the air conditioner mate to a mobile phone. After you configure the air conditioner mate in the App, you can use the App to control the air conditioner mate.
Dear user, we are sorry for your inconvenience. If you do so: Open the APP, click the device icon to enter the device control panel. Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of the corresponding third-party control to view the operation manual of the third-party control. Only the built-in devices and device functions in the universal remote control support voice control. If you want to use voice to control DIY devices and device functions, you can add the DIY device or device function to one-key execution/automation, and then voice control the one-key execution/automation (currently only Amazon Alexa, Google Assisitant and Baidu Xiaodu supports scene control). DIY equipment has more restrictions on one-key execution/automation support. If you cannot create Tap-To-Run/automation, please provide us with the virtual ID of the device, and we will arrange for a technician to troubleshoot for you. Thank you for your support and understanding.
Dear user, this problem is usually caused by fluctuations in the network connection of the device. Please follow these steps to configure: The router frequency band is set to 2.4GHz. The router encryption mode is WPA / WPA2 mode. Disable wireless access control and cancel the black and white list option. Enable DHCP function. It is recommended not to operate the Mac address. The router's Wi-Fi name and password are set to English + number. Your mobile phone system version does not meet the requirements of the App (Requires iOS≥V10.0 version, Android≥V5.0 version). Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), real-time monitoring equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps). Thank you for your support and understanding.
Avoid mounting it on a magnetic object surface such as a metal doorframe. Keep it powered on to improve the stability of the Zigbee network.
Dear user, according to the number of calculations, the battery can support about one year for every 50 triggers. In low power, in order not to affect your normal use, it is recommended that you replace the battery as soon as possible (within 24 hours).
Dear user, there are usually the following reasons for the device offline, you can check accordingly: The gateway is offline. The device is powered off. The device is too far away from the gateway.
The distance between the product and your app can be up to 30 meters if there is no solid wall between them.
There is no limit on the number of Zigbee gateways that you can add.
It is a local area network gateway address, separating the gateways between local area networks, responsible for forwarding local area broadcasts, and the necessary place for internal and external network data exchange. According to the network protocol, a local area network must set a gateway. It's like a translator that can connect devices with different protocols, allowing users to perform unified operations on an app. For example, users can add sub-devices to the gateway to achieve unified control of devices such as switches, light bulbs, and curtains.
The indicator light will stay on for three seconds after you power on the PIR motion sensor. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
This is because the device reports events at a frequency of less than 10 seconds, which is too high and must be reduced.
The OPERATE_RET uni_time_set_posix(IN CONST TIME_T time, IN CONST INT_T update_source) can be used to set the SDK time. Usually, Unix time refers to the number of seconds counted from midnight (UTC) on January 1, 1970, which can be represented as an integer. This interface might be used to set the system time to a given Unix timestamp.
Zigbee switch local scenes use the multicast mechanism. After a local scene is set and verified, the switch sends scene commands to executing devices in multicast mode, without caching them in the gateway. Unlike switches with a live terminal and a neutral terminal that have the sleep mode, switches with a live terminal but no neutral terminal have a high packet loss rate and scene execution failure rate. If they are added to local scenes, the user experience will be poor.
This configuration is powered on for reconnection of low-power compatible devices.
The Tuya-enabled switch module supports three reset methods to meet different application needs. You can select as needed in the product development phase. Press and hold the master control key. You can specify pressing and holding the master control key on the device for x seconds to reset the switch module. This method applies to easy-to-operate scenarios. Flip the external switch multiple times. If the switch module has an external switch, you can flip the external switch multiple times to reset the module. Power on and off the device multiple times. Power on and off the device multiple times for reset. This method applies when the switch module has no external switch and is not easy to operate.
No, it won't. The Tuya-enabled disinfection controller adopts a human body detection sensor. When it detects humans during disinfection, the controller immediately terminates the disinfection procedure, and the buzzer beeps to generate an alert to inform related personnel to evacuate. The disinfection procedure resumes after the disinfection controller detects no human body.
No. The firmware update of the original PID will not automatically be applied to the OEM PID. To update the firmware of the OEM product, a separate update configuration is required.
It means the module is connected to the router but not the cloud.
Apps running Android 11 are forced to use scoped storage. In this case, these apps cannot directly access external storage. The preserveLegacyExternalStorage flag is provided to enable apps updated to adapt to Android 11 to access previous data stored in external storage. However, the preserveLegacyExternalStorage flag is available only in Android SDK 30. Therefore, this error is reported. To solve this problem, use either of the following solutions: Upgrade the Android SDK compilation version to 30. That is, upgrade the tuyaversion plug-in. Add tools:remove="preserveLegacyExternalStorage" to the application tag of Manifest to remove the preserveLegacyExternalStorage attribute. For more information about the principles, see https://developer.android.com/studio/build/manifest-merge. (It is recommended that the compilation version be updated. Otherwise, the app launch on Google Play will be affected. https://developer.android.com/distribute/play-policies).
This error may occur when the offset value exceeds 1,000.
Hello, please upgrade the following libraries to the latest version and try again com.thingclips.smart:thingsmart-bizbundle-panel:5.5.0-9 com.thingclips.smart:thingsmart-bizbundle-ota:5.5.0-9 com.thingclips.smart:thingsmart-bizbundle-control:5.5.0-9 com.thingclips.smart:thingsmart-bizbundle-panelmore:5.5.0-9 com.thingclips.smart:thingsmart-bizbundle-groupmanager:5.5.0-9 com.thingclips.smart:thingsmart-bizbundle-devicekit:5.5.0-9.
Follow the instructions in the attachment to exclude, then run implementation ("com.thingclips.smart:thingsmart-bizbundle-miniapp"){ exclude group: "com.umeng.umsdk",module: "huawei-basetb" }.
Yes, you can develop the first two modules if you require network pairing and device control functions only. # Home, device, room, and group management pod 'ThingSmartDeviceKit' ,
# Network pairing
pod 'ThingSmartActivatorKit', The following modules are optional: # Single-point Bluetooth
pod 'ThingSmartBLEKit',
# Bluetooth mesh
pod 'ThingSmartBLEMeshKit',
# Smart scene
pod 'ThingSmartSceneKit',
# Device and group timing
pod 'ThingSmartTimerKit',
# Message Center
pod 'ThingSmartMessageKit', # Feedback
pod 'ThingSmartFeedbackKit',.
iOS SDK only supports pod integration.
Import this header file: #import TuyaSmartActivatorKit/TuyaSmartActivatorKit.h.
It depends on the communication type of devices. Wi-Fi devices have the semaphore and IP address, while Zigbee sub-devices do not.
Wi-Fi devices (excluding gateways) NB-IoT devices Cat.1 devices Wi-Fi & Bluetooth LE devices (excluding gateways).
If you encounter the issue where Bluetooth permissions are enabled on your phone, but the network configuration service package still prompts that Bluetooth is not enabled, you can troubleshoot with the following steps: 1. You need to add Bluetooth permission declarations in the project's info.plist file: NSBluetoothAlwaysUsageDescription NSBluetoothPeripheralUsageDescription 2. Set the needBle property in thing_custom_config.json` to `true. 3. Then, you need to integrate the following SDKs into your project: For versions below 5.8.0: pod 'ThingBLEHomeManager' pod 'ThingBLEInterfaceImpl' pod 'ThingBLEMeshInterfaceImpl' pod 'ThingSmartBLEKit' pod 'ThingSmartBLEMeshKit' For versions above 5.8.0: pod 'ThingSmartBusinessExtensionKitBLEExtra'.
Update the SDK to the latest version. This bug has been fixed in the latest SDK version.
deviceModel.capability indicates the communication capability of a device. Example: deviceModel.capability = 4097 4097 is equal to 2 to the power of 10 plus 2 to the power of 0. Valid values: `0`: Wi-Fi. `1`: wired. `2`: GPRS. `3`: NB-IoT. `10`: Bluetooth. `11`: Bluetooth mesh. `12`: Zigbee. 10 indicates Bluetooth and 0 indicates Wi-Fi. Therefore, this device is a device that is capable of both Wi-Fi and Bluetooth.
Firmware that has already been released cannot be deleted, but you can choose to replace it. For detailed operations, please refer to: Select and Manage Firmware Versions.
If you upload a firmware package of an unsupported format, the platform will prompt you for format mismatch. Take note that the formats supported by the platform are those supported by Tuya. You must upload a package of the format supported by your firmware.
This is because upgraded SDKs require more configurations. After the SDK is upgraded to version 3.29.5 or later, you need to configure SHA256 in the project on Tuya IoT Platform and set the signature information signingConfigs in the app's build.gradle file before login. Note: Earlier versions of the SDK include two sets of keys: test and official. Official keys are used uniformly after version 3.29.5. If the test key is used, you need to modify the AppKey, AppSecret, and security image after upgrading the SDK. For more information about the operation process, see the video above.
Manually call the Bluetooth connection method before you enter the panel and try again. For more information, visit https://developer.tuya.com/en/docs/app-development/android-bluetooth-ble?id=Karv7r2ju4c21#title-15-%E8%BF%9E%E6%8E%A5%E7%A6%BB%E7%BA%BF%E8%AE%BE%E5%A4%87.
After creating a scene, call the getSceneDetail interface to obtain the scene details. The iconUrl obtained are the same, because the icon library interface of the SDK is currently not open and temporary does not support obtainment.
No, it's not possible, even after deletion.
Do not add code like Security.insertProviderAt(xxx, 1);, because it is a duplicate with Tuya SDK initialization and will cause the preceding problem. Delete the added code to resolve the problem.
Theoretically, a Bluetooth gateway supports a maximum of 128 sub-devices. However, the theoretical value of 128 may not be reached due to the mutual interference among Bluetooth devices and the restriction on the connection distance (less than 5 m). Theoretically, a wired Zigbee gateway supports a maximum of 128 sub-devices, and a wireless Zigbee gateway supports a maximum of 50 sub-devices. You can remove part of the devices or use another gateway. This problem can also be caused by the performance of your mobile phone. You can change a mobile phone and try again.
This is generally caused by incorrect Google login configuration information. Once you change to the correct configuration information, you will be able to log in successfully.
The prompt for 100 SDK account is as follows: REGISTER_USER_LIMIT - The application which uses the SDK trial version has crossed the limit of registered users. Please visit the Tuya IoT Development Platform: https://www.tuya.com/vas/commodity/SDK_APP_CREATE to buy the official version and remove the limit.
Hello, since some devices do not have a scanning process, but the business package uses composite scanning, Wi-Fi Quick Connect, password-free, gateway routers, and sub-devices actually have no scanning process. Scanning represents the capability of network configuration, and the scanning process is the network configuration process. If this method is not needed, you can set bool name="is_config_activator_ez"false/bool to false in compat-colors, so that after turning it off, these types of devices will not be automatically scanned and will not be automatically configured. You can only configure them manually by entering the network configuration business package and clicking on the corresponding device to configure it.
Check if the calibration is done using a regulated power supply. If calibration is done using mains electricity, voltage fluctuations may cause data deviations. It is recommended to calibrate according to the actual voltage of the region where the device will be sold. For detailed production testing, refer to the document: https://developer.tuya.com/en/docs/iot/wifi-power-socket-production-test?id=K9eiu5skyksp6&from_wecom=1. Additionally, it might be an issue with the circuit design. For more details, refer to the document: https://developer.tuya.com/en/docs/iot/product-troubleshooting-guide?id=K9tp15cht184d.
Cleaning time: The cleaning time refers to the current cleaning, which is reported by the device in real time and displayed on the current cleaning interface. The total cleaning time: the total time reported by the device after a cleaning is completed.
Loss Tolerance or Packet Loss Rate refers to the ratio of the number of data packets lost in the test to the total data groups sent out. The calculation method is: "[(Input messages - Output messages) / Input messages] *100%". The packet loss rate is related to the length of the packet and the frequency of packet transmission. Here are the testing methods for packet loss rate: https://developer.tuya.com/en/docs/iot/wifi-test?id=K9hr623embyah.
Restore the device to factory settings in the app as follows: 1. Start the app. 2. Open the device control page. 3. Tap the editing icon in the upper right corner. 4. Tap Restore Factory Defaults.
You can click the following link to download the test tool: https://developer.tuya.com/en/docs/iot/module-test-tool?id=K9qswhqd5ymnp.
When receiving the module, it is suggested that, before start coding, you run the provided module debugging assistant, and connect the Wi-Fi module in MCU simulation mode to check if the module can work properly. Meanwhile, you can get familiar with the protocol interaction process, which will help you to proceed with development debugging. In the MCU simulation mode, the debugging assistant simulates the MCU to automatically respond to the module with the correct protocol data. After you configure the network through the mobile phone, you can test DP data reporting and sending. The procedure of operating the assistant and module network configuration is as follows. Before the operation, you need to learn about the operation instruction of the Tuya module debugging assistant. For beginners, see Module Debugging Assistant Instruction. 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 Wi-Fi low power protocol and MCU simulation mode. Connect the module serial port to the computer through USB-to-TTL adapter, and select the corresponding serial port and Baud in the assistant. After you open the serial port and click Start, you will see the initial protocol interaction between the module and the host. Note: Wi-Fi low power module will send command 01 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 Module, and the module enters network configuration mode. The module supports two network configuration modes, EZ and AP (The difference between EZ and AP modes). When you click Reset, the mode will be switched. Configure network on the app according to the status. See the app operation instruction f.
The firmware is incorrect, the test is not using a fixed frequency prototype, generally displaying this log should be an adaptive firmware prototype; you can open the SSCOM serial port tool to verify, send the command: ATWT=-s if it is adaptive firmware, it will return tcp_server_func: Bind socket successfully.
You can search for "TUYA" on the Wi-Fi Alliance official website to find out which modules have obtained Wi-Fi Alliance certification: https://www.wi-fi.org/product-finder.
This product operates with the module model CB3S already homologated with the homologation number 08206-21-11765.
The official certification procedure supports adding finished product models directly to the module's NCC certificate. It requires filing the appearance and internal photos of each finished product model with the issuing authority. After completing the filing, the finished product can use the module's NCC certification number. If there are any changes to the product later, it needs to be re-filed. Additionally, considering the risk of market spot checks, Tuya has suspended adding customer finished product models to the Tuya module certificate. Currently, the NCC certification scheme can issue a module NCC certificate held by the customer applicant, and the customer can independently add the finished product to the new certificate.
FCC part B+ICES-003 two standard tests for electromagnetic radiation of non-RF circuits. The wireless module is an RF functional component and does not need to be tested for these two standards. Currently, our integrity module is FCC&IC certified with FCC ID & ICES ID, and after being applied to the whole machine, there are no changes made to the RF output power, antenna gain, or antenna type, so the finished product can directly reference the module's ID; all modules by default do not undergo the EMC part, which needs to be done for the finished product; for restrictive modules to obtain an FCC ID certificate, they must be tested with the terminal use product, and as Tuya is a module manufacturer without a determined end product, it cannot obtain an FCC ID certificate.
You can download the module certification materials on the product development interface (https://platform.tuya.com/pmg/list) by clicking on the product name, which will bring up the product overview page. The materials include: 1. Module certification certificates 2. Schematics, block diagrams, antenna test reports (antenna specifications), module specifications, location diagrams, and principle descriptions required for certification submission 3. Module RF Test tool Introduction: A link to the module certification test guide (download the guide through the link for testing by the institution).
The module has obtained TELEC certification, and the finished product can directly use it. The product should be marked with the module's TELEC certification number.
Zigbee and Bluetooth are proprietary certifications. Certification is required to use the Zigbee and Bluetooth logos, otherwise it will greatly increase the customs investigation of patent infringement.
Currently, the cloud testing App does not support devices with the Matter scheme.
For more information, visit https://docs.qq.com/doc/DUWdQZlJlbEh6S3J2?confirmed=1.
The door lock's Wi-Fi module with low power consumption that Tuya provides has the information cache mechanism to ensure that information reported by the MCU is sent to the cloud end._x000D_ When the door lock is offline, data reported by the MCU will be sent to the cloud end when the door lock is online again._x000D_ The MCU does not require a cache mechanism to ensure successful information reporting._x000D_.
The temporary code feature allows you to create a temporary code and specify the validity period of the code. You can also set a recurring cycle within which the code remains valid. A visitor can enter the temporary code to unlock the door within the validity period of the code. The feature involves the following DPs: DP 3: Unlock with Temporary Code For more information, visithttps://docs.qq.com/doc/DTWZKTWlLSmNIdmFn.
If you select debugging during product development, you cannot purchase a kit. The minimum purchase quantity (MPQ) of kit products is too large and does not support small batch purchase.
Note: The prerequisite is that the control panel supports music playback. You can consult the product manager whether music playback is supported. The tuya_user_voice_dp_report_ctrl_cmd interface provided in the SDK is used to control a DP of the device and cannot control the playback of the previous or next piece of music. In the future, an interface will be encapsulated to support this function.
Yes. Initialization: When a device is started in a LAN, the SDK reads the device information from the locally cached files. The SDK can read previous device and scene information and control the device through the LAN. In LAN initialization scenarios, update events are not pushed. After SDK initialization, you must manually call the tuya_get_dev_brief_info API to obtain the device list and device information. If devices are added at this time, the information cannot be synchronized to the control panel. Control: A master gateway needs to be elected from multiple gateways to perform LAN control. The master gateway forwards messages and performs LAN control. Master gateway election requires a network connection. After the master gateway election is performed once under network connection, LAN control can be performed even when the network is disconnected. If the device is still in a LAN after a restart, the previously cached master data is used to re-elect a master gateway, and the network connection is not required. Note: LAN control indicates that the device is disconnected from the uplink network.
An SDK helps customers implement complex control panel functions, reduce development costs, and quickly develop control panel products. Currently, an SDK is provided to customers in the format of static libraries and header files. Tuya also provides abundant demo programs. Customers develop upper-layer applications and call APIs to initialize the SDK and apply functions. Note: To use the SDK, you can provide the compilation toolchain to the FAE to generate the corresponding toolchain package and then develop programs based on the guide.
If you are a smart home geek and have a bundle of devices from different platforms, this step-by-step tutorial will help you control smart devices with one single app or tool and develop third-platform integration or plugin. Explore our GitHub repo and find information on installation and much more. Home Assistant Integration GitHub Repo Tuya IoT Python SDK Homebridge GitHub Repo Homebridge JS SDK on npm Step 1: Configure on Tuya IoT Platform Note:For the comparison of Tuya cloud development method, seeDevelopment Method. Using Smart Home PaaS Step 2: Install and use integration and plugin Home Assistant How to Migrate the Tuya Home Assistant Integration from the Old Version How to Use Tuya Home Assistant Integration Homebridge How to Use Tuya Homebridge Plugin.
Possible causes: 1. The MCU failed to report the data as required by the protocols when the charging starts and ends. 2. The module does not have the advanced Charging Record on Cloud feature. You can submit a service ticket and provide the device ID. Tuya technical personnel will solve this problem for you.
The total number of registered users of the associated App under the current account.
There are two situations where low power consumption can be entered: If the module is just shipped from the factory, it works in low power mode by default. If configured for power-on networking, there is no low power consumption. If it is in normal working state, you need to configure and remove the mobile phone for 10 seconds, and then power on again, then you can switch to the low power consumption state.
It is possible that the sampling resistance is too large, which results in the measured value not being within the limited range, which will cause the data report to be intercepted.
This situation is generally caused by the failure of the sel pin switching of the power statistics chip. Under normal working conditions, use an oscilloscope to measure the sel pin voltage to see if there is a 1:10 high and low level switch. If there is no high and low level conversion, please check Whether the circuit between the IO12 of the tuya module and the sel pin of the power statistics chip is a path.
The USB circuit uses a flyback isolation circuit to output 5V, while 5V supplies power to the relay, and 5V plus LDO outputs 3.3V to supply power to the module; if USB also needs control, you can add PMOS and triode control circuits to the USB output 5V end, and use the module to control .
Flashing after manual switching, for devices that have been networked: 1、If flashing time is less than 10 seconds, the device powers off, and upon powering on again, the device remains in flashing status; 2、If flashing time is more than 10 seconds, the device powers off, and upon powering on again, the device stays in the constantly lit mode (reconnecting).
The power statistics function requires an external power statistics chip. We recommend the HLW8012 and BL0937 power statistics chips.
You must enable the energy metering function for the product, especially when the product is customized. Log in to the IoT platform, go to Advanced Features, and enable at least "Basic Energy Metering".
Currently, power-failure memory typically only remembers functions such as white light, colored light, and scene modes. The default behavior is for the light to turn on when power is restored, in order to cover the user experience of non-smart products. If users have a specific requirement regarding this, they can choose to add a "do not disturb" mode. With this mode enabled, if the light is turned off using the software before a power cut, the light will not turn on when power is restored. To turn on the light, users will need to toggle the switch twice within 5 seconds.
The universal remote uses an infrared docking protocol with an infrared signal frequency of 38KHz.
No, it can only be used as an actuation device, because the communication between IR remote control and sub-device is one-way, and the electrical appliance can't report the status.
IP cameras (IPCs) use the privacy protection mode to ensure privacy and data security. When the privacy protection mode is enabled, users are not allowed to access real-time video streams or store recordings. When the privacy protection is disabled, IPCs operate in normal mode.
IP cameras (IPCs) support horizontal imaging, vertical imaging, and 180-degree rotation. You can integrate the screen flip function based on your the capabilities of your IPC.
Yes. The playback icon is not displayed if you do not configure memory card-related DPs.
All function points executed by the App to be issued by the device must be deliverable and reportable. After the App is delivered, after the device is executed, the original value must be reported to the App to implement a closed loop, and the control operation is completed.
Streaming services enabled for transmission over streaming data channels.
Data is cached on the robot vacuum.
Current, voltage and power are "current values". [Current reporting method] (Used in the new firmware and some upgraded firmware in February 19, and the corresponding panel needs to support the query function) When you enter the panel, the panel triggers the query and the 5S report once. After exiting the panel, there is almost no initiative to report. [History reporting method] Change judgment standard: current change 10% or power change 10% or voltage change 2%. Comparison interval time: long interval 30S, short interval 5S. If this comparison finds that no change is triggered: the next comparison time is a long interval. If this comparison finds that a change is triggered, the next comparison time is a short interval. If there is no change, it will be reported every 30 minutes.
RAM needs 1K, ROM needs 5K.
1-channel PWM 2-channel PWM (CW, CCT) 3-channel PWM and I2C 4-channel PWM and I2C 5-channel PWM (CW, CCT) and I2C.
Phy6252 Beacon light strip is based on the Beacon mesh protocol, that is, Beacon2.0, which can realize the broadcast jump point to forward data, form a mesh network, more stable and wider broadcast control range.
The advanced settings of App theme color need to be opened for value-added services (service links) before they can be configured online. After purchase the "OEM App Advanced Features" service for your OEM App, go back to the theme color page of the App, and you can see the following configuration items. App Color Theme tab. You can set the following parameters: The background colors of cards, dialog boxes, and tab bars. Modify the text color transparency and configure the right-angle or round corners of cards, buttons, and dialog boxes. The following table shows Previews A and B of each advanced setting for your reference. Item Preview A Preview B Background color of cards Background color of dialog boxes Background color of tab bars Text transparency of headlines Text transparency of headings Text transparency of notes Text transparency of expiration prompts Right-angle or round corner of cards Right-angle or round corner of buttons Right-angle or round corner of dialog boxes.
This is because the image sizes supported by Tuya cannot adapt to all Android phone models. Therefore, the splash screen image may be stretched or not fully displayed when the system trims the image. To resolve this problem, we recommend that you change the mode of uploading the splash screen image to Merge Images.
Scenes to be used: App accounts in the whitelist can view recently edited words or new words in the app’s "Me-Settings-Multilingual Debug Mode". Enable Show Multilingual Code, and quickly switch the app languages. It supports previewing unreleased language packs, which is convenient for checking whether the updated copywriting is accurate. After confirmation, it can be released and then directly pushed to app users. Precautions: Each app can set up to 10 whitelist accounts. If you want to view the multilingual entries of the non-panel and smart applet parts of the App through this debugging service, it only supports Apps created based on v3.20.0 and above templates; If you want to view the multilingual entries of the device-panel and smart applet parts of the App through this debugging service, it only supports Apps created based on v4.9.0 and above templates; Apps created with templates before v4.9.0 only support China region whitelist accounts, and those after v4.9.0 can support whitelist accounts in China region, United States region, Europe region, India region, US East region, and Western Europe region. (If you are not sure about your account region, you can go to the App "Me-Account-Account & Security- Region" to check the account location ).
This option enables you to customize the name of a skill or an app with other content the same as the all-in-one app. If you select the second option, you can customize the document content.
Yes. To implement this function, select the volume control DP. Then, the volume control icon appears on the control panel, and the volume control function becomes available on the lullaby control page.
Check whether the robot vacuum BizBundle pod 'TuyaRNApi/Sweeper' is integrated.
No, you do not. The app developed based on App SDK v3.x still uses the key information including AppKey and AppSecret for v3.x. After you upgrade to v5.x, change the key information to that for v5.x. To get the key information for v3.x and v4.x, perform the following steps: Log in to theTuya IoT Development Platform. Go toApp SDKSDK Development. Find the target SDK-based app and go to itsdetails page. ClickSwitch to Old App SDK: v4in the top right corner of the page to switch to v4.x. 5. Then, you can get the key information for v4.x and v3.x.
No.
No. Matter devices can be put on the market with the Matter badge only after the Matter certification testing.
Yes, Android system version: 6.0 and above.
The client is using Jizhi Light Control (Commercial-License app).
Local scenarios do not require gateways, cloud scenarios require gateways.
Combine several files into a complete package and burn it with Espressif burning tool.
The module sends MQTT heartbeats every 60 seconds. If it does not receive heartbeat packets for the following 42 seconds, the MQTT connection is disrupted and a re-connection try is made.
For lighting products, interactions of DPs, such as on/off control, brightness, color temperature, and color are achieved through the SIG Model. Interactions of other DPs are achieved through the Vendor Model, which corresponds to the TAL_MESH_OPCODE_WRITE command in the SDK.
A profile contains various types of devices. For example, ZHA Profile contains devices such as smart sockets, temperature and humidity sensors, and curtain controllers. Each device in the Profile is assigned a unique device ID.
Similar to attributes in object-oriented programming, an attribute in the custom development of Zigbee describes the characteristics of a type of object, such as the gender, age, and weight of tigers. The Zigbee Alliance predefines several clusters and a set of attributes for each cluster. Developers can customize the attributes of a cluster.
The sprintf interface of telink chip platform is abnormal, please use the snprintf interface, the size parameter needs to be 1 larger than the actual length.
Simply put, a cluster is a collection of attributes. Each cluster is assigned a unique cluster ID and contains a maximum of 65,536 attributes, such as settings of switches, lights, temperature, and percentages in different circumstances.
Mode ID is a convention between a Zigbee sub-device and the Zigbee gateway. The Zigbee gateway uses the mode ID to recognize the device type.
After the gateway installs the new firmware and restarts, the SDK will update the version to the cloud, and the cloud will push a message to the App, and the App prompts that the upgrade is successful.
We can provide the SDK ranther than the source code.
The video cloud storage service uses the AES128 algorithm to encrypt the video data itself, and the encryption process uses a dynamic secret key. At the same time, the data upload transmission process also uses a financial-grade secure TLS encryption channel. In the case of double encryption of data and channels, the data cannot be intercepted during data transmission, and the video data cannot be played without the user app account password, ensuring the absolute security of user data.
Process for handling issues: First, confirm whether the issue still exists after changing the network on the phone： a, If it doesn't exist, it means it's due to a problem with the phone's network during playback； b, If the issue still exists, please submit an IoT platform technical ticket for further investigation and provide the video that cannot be played from cloud storage, the time when the problem occurred, and the device ID.
When the Wi-Fi module is in a low-power state, it will turn off the network card, and it needs to be in a non-low-power state to be obtained.
Please confirm whether the region associated with the customer's Alexa account login is within the area where your skill is available.
The platform you are applying for access does not support this category temporarily, or your product function point (DP point) is customized and will also be closed, you need to apply for customization.
Hello, you can replace "Product PID" with your product PID in the following URL, and then open a new page to visit. https://iot.tuya.com/exp/voice/version?platformId=22&productId=“Product PID”.
Hardware Category Voice Control Solution Single Product Control or Multi-Module Control Device Type Sent to Third-Party Voice Assistants Function Voice Command Supported Language Remarks Infrared air conditioner Solution 1 Single product control Air conditioner On/Off control Turn on the air conditioner Turn off the air conditioner Mandarin Infrared air conditioner Solution 1 Single product control Air conditioner Wind speed adjustment Slightly increase the wind speed level of the air conditioner Slightly decrease the wind speed level of the air conditioner Mandarin Infrared air conditioner Solution 1 Single product control Air conditioner Mode setting Set the air conditioner to Auto Set the air conditioner to Cool Set the air conditioner to Heat Mandarin Infrared air conditioner Solution 1 Single product control Air conditioner Temperature adjustment Turn up the air conditioner slightly Turn down the air conditioner slightly Mandarin Infrared fan Solution 1 Single product control Fan On/Off control Turn on the fan Turn off the fan Mandarin IR remote control fan Solution 1 Single product control Fan Wind speed adjustment Slightly increase the fan speed Slightly decrease the fan speed Mandarin Television with infrared remote control Solution 1 Single product control Television On/Off control Turn on the TV Turn off the TV Mandarin Television with infrared remote control Solution 1 Single product control Television Volume adjustment Turn up the volume of the TV a little bit Turn down the volume of the TV a little bit Mute the TV Unmute the TV Mandarin Television with infrared remote control Solution 1 Single product control Television Channel selection Switch to the next TV channel Change the TV channel Return to the previous TV channel Go to TV channel 18 Mandarin Infrared set-top box Solution 1 Single product control Set-top box On/Off control Turn on the set-top box Turn off the set-top box Mandarin Infrared set-top box Solution 1 Single product control Set-top box.
It takes two workdays to enable a third-party smart speaker access service.
No. Xiaozhi can be directly configured, launched, and activated in the Voice Platform module of the Product Configuration step on Tuya IoT Platform.
A reported fault DP value is a 2-digit number corresponding to the position of a set value in a set of all values of the fault DP, but not the set value. For example, if you set a fault DP that has the values of 1, 2, and 3 to 1, the reported value will be 00. In addition, you need to manually add the DP value to be displayed in the app in Extensions Multilingual.
A string value can contain a maximum of 255 bytes.
For more information, visithttps://developer.tuya.com/en/docs/iot/configure-in-platform/function-definition/custom-functions?id=K937y38137c64#title-6-Fault.
The data length of the enumerated DP is 1 byte.
The app sends a scheduled task to the device through the DP, and the device runs the task. (DP timing is device timing, not cloud timing.) DP timing involves inching switch, random timing, cycle timing, and countdown.
You can choose from the following aspects: 1. According to the antenna, modules are classified into external antennas (I-PEX connector), onboard antennas, and conducting antennas. Select modules with an external antenna (I-PEX connector) for products with a metal cover and lead the antenna out of the cover. Select modules with an onboard antenna or a conducting antenna for products with a plastic cover. Select modules with a conducting antenna, such as LC5, for small-sized products. 2. According to the withstand temperature, modules are classified into 85°C, 105°C, and 125°C modules. For products that have high use temperature, such as sphere lamps, select 105°C modules. For products with normal use temperatures, use 85°C modules. 3. According to the structure, cover size typically, select modules with different encapsulation methods, including the assembly method (surface mounted or through-hole mounted).
A bidirectional triac is an integration of a pair of ordinary triacs connected in reverse parallel, and it works on the same principle as the ordinary unidirectional triac. A bidirectional triac has two main terminals, T1 and T2, and one gate G. The gate allows the device to be triggered to conduct in both the positive and negative directions of the main terminals, so the bidirectional triac has symmetrical V-I characteristics in the first and third quadrants. Once a unidirectional triac is turned on, it will continue to conduct even if the voltage at the control gate is lowered or removed. The conditions for turning off a triac are: reduce or remove the forward voltage applied between the anode and cathode of the triac, making the anode current fall below the minimum holding current.
The accuracy of the calibration resistor affects the measurement accuracy after calibration. If the accuracy of the resistor used is not high, the measurement error will be high. It is recommended to use a resistor with 1% accuracy.
MCU connection method, Hardware Design Reference Precautions: Module power related - The maximum current of the module in working mode can reach 324 mA instantaneously, it is recommended to provide the module with a power supply current of more than 400mA at 3.3V. The capacitors C1 and C2 at the module power input pins should be as close to the power pins as possible during PCB Layout, and it is best if their capacitance is greater than 10uF. Module RF related- When the module comes with a PCB onboard antenna, to ensure the optimal performance of Wi-Fi, it is recommended that the distance between the module antenna part and other metal parts be at least 15mm or more.
Hello, you can download the corresponding protocol document from the third step of product development: hardware development page with detailed data bit content analysis.
Theoretical endurance of 10 years when LoRa battery powered (AA batteries).
It is not recommended to have devices report information frequently for the following reasons: 1. A device should not report more than 3500 records per day; exceeding this number will incur additional charges. 2. If the reporting frequency is too high, the cloud will trigger a rate limiting logic, causing some of the reported data from the device to be lost.
Sampling resistance of different parameters, the corresponding module firmware is common, but the json configuration is different. For the parameters of the sampling resistor used, the corresponding json needs to be configured, which can be configured on the Tuya IoT platform.
No, after the product is created, the burned module can't be modified to other categories.
Power-off memory activation time: Operates for more than 5s.
The essence of ripple is the voltage drop caused by the current flowing through the output capacitor on the ESR of the capacitor.
Light bulb devices typically enter pairing mode using the following methods: Cycling operation: Some light bulb devices may require a specific sequence of switch operations to reset. This is usually achieved by executing a series of power on and off cycles within a given period of time (e.g., switching three times). Power cycle: Turn off the power switch of the light bulb, wait for a few seconds, then turn the power switch back on. Some devices may enter pairing mode when powered back on. Contact manufacturer support: If you are unable to reset the device to pairing mode after trying the above methods, it is recommended to contact the customer support of the device manufacturer for further assistance and guidance. They may provide detailed reset steps specific to the device. Table lamp devices typically enter pairing mode using the following methods: Power cycle: Firstly, try unplugging the power plug of the table lamp device, wait for a few seconds, then plug it back in to see if the device enters pairing mode. Press button: There may be a reset button on the table lamp device. Try pressing and holding it for a few seconds to see if it triggers a reset operation and enters pairing mode. Cycling operation: Usually achieved by executing a series of power on and off cycles within a given period of time. Refer to manufacturer's manual: It is recommended to check the manufacturer's provided manual for specific reset steps for the device. They may provide specific button combinations or sequences for operations.
Dear user, we are sorry for your inconvenience. The difference between the two is: EZ mode: Smartconfig means that the mobile App sends a UDP broadcast packet or a multicast packet containing the Wi-Fi username Wi-Fi password. The Wi-Fi chip of the intelligent terminal can receive the UDP packet, as long as the UDP organization form is known, The Wi-Fi username and password are decrypted by the received UDP packet, and then the Wi-Fi username and password received by the intelligent hardware configuration are sent to the designated Wi-Fi AP. AP mode: App configures the mobile phone to connect to the intelligent hardware (AP of the Wi-Fi chip). The mobile phone and the Wi-Fi chip directly establish communication, and the Wi-Fi user name and the Wi-Fi password to be configured are sent to the intelligent hardware, and the intelligent hardware can be connected at this time. Configured on the router. Compared to the AP mode, the EZ mode is easier to use and quicker during first network pairing. However, some mobile phones and devices are incompatible with the EZ mode and require the AP mode.
Switch devices typically have the following methods to enter pairing mode: Reset Button: Most switch devices come with a reset button. Press and hold the reset button for a period of time until the device indicates it has entered pairing mode (this may be indicated by flashing lights). Specific Combination of Keys: Some switch devices may require pressing a specific combination of keys (such as switching three times) to reset and enter pairing mode. Manufacturers typically specify these key combinations in the user manual. Power Cycle: Try powering off the device, wait for a few seconds, then reconnect the power. Upon restarting, the device may automatically enter pairing mode. Contact Manufacturer Support: If the above methods do not work to reset the device to pairing mode, it is recommended to contact the manufacturer's customer support for further guidance. They may provide detailed reset steps specific to the device. Socket devices typically can enter pairing mode using the following methods: Using the Reset Button: Most socket devices are designed with a reset button. Press and hold the reset button for several seconds to several tens of seconds until the device indicates it has entered pairing mode (this may be indicated by flashing lights). Power Cycle: Disconnect the socket device from power, wait for a few seconds, then reconnect the power. Some devices may automatically enter pairing mode upon reboot. Contact Manufacturer Support: If the above methods do not work to reset the device to pairing mode, it is recommended to contact the manufacturer's customer support for further guidance. They may provide detailed reset steps specific to the device.
Button Reset: Sensor devices typically come with a physical button. Press and hold this button for a period of time to reset the device and enter pairing mode. Power Reset: Some sensor devices require a power reset, such as unplugging and plugging back in the power source or removing and reinserting the battery to reset the device and enter pairing mode. Reset Hole: If your device has a small hole labeled "reset," use a slender object to gently press and hold the reset hole by inserting the tip into it. Hold for a few seconds until you see the device's indicator light blinking, indicating that the device is in pairing mode. Contact Manufacturer Support: If attempts to reset the device to pairing mode using the above methods are unsuccessful, it is recommended to contact the customer support of the device manufacturer for further assistance and guidance. They may provide specific reset steps tailored to the device.
The methods for Wi-Fi bulb devices to enter pairing mode typically include: Cycling Operation: Some bulb devices may require a specific sequence of switch operations to reset. This is usually achieved by executing a series of power on and off cycles within a given time frame (e.g., switching three times). Power Cycle: Turn off the power switch of the bulb, wait for a few seconds, and then turn the power switch back on. Some devices may enter pairing mode when powered back on. Contact Manufacturer Support: If the above methods do not reset the device to pairing mode, it is recommended to contact the device manufacturer's customer support for further assistance and guidance. They may provide detailed reset steps specific to the device. For desk lamp devices to enter pairing mode, the following methods are commonly used: Power Cycle: First, try unplugging the power plug of the desk lamp device, wait for a few seconds, and then plug it back in to see if the device enters pairing mode. Press Button: There may be a reset button on the desk lamp device; you can try pressing and holding it for a few seconds to see if it triggers the reset operation and enters pairing mode. Cycling Operation: Typically achieved by executing a series of power on and off cycles within a given time frame. Follow Manufacturer Instructions: It is recommended to consult the manufacturer's provided instructions to understand the specific reset steps for the device. Specific button combinations or sequences may be provided.
Please check in the following ways: Please reset the device and re-add it. If the offline still occurs after re-adding, please check whether the device firmware is up to date. If it is the latest firmware, it is recommended that you reset the gateway device and re-add the sub-device. If the device is still often offline, please check whether the number of sub-devices under the gateway exceeds the upper limit. If the problem still exists, please provide us with the App name and device ID, and we will investigate further for you. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. If your mobile phone is Android 8.0 or higher or iOS 13 and do not assign the App with the positioning permission, you will need to enter the Wi-Fi name manually.
Dear user, we are sorry for your inconvenience. If you can only control the device when connected to your home's Wi-Fi, and you can't control it with 4G or other Wi-Fi, it means that there is a problem with the connection between the router in your home and the external network. Therefore the device is failed to communicate with our cloud, so it can only operate normally in the local area network (when you connect your home Wi-Fi, you are using the local area network to control the device). Please check your router's connection to the external network and make sure it is smooth before trying again. Thank you for your understanding and support.
Ensure that the device is in the correct pairing mode. Check if the distance between the Zigbee gateway and Zigbee devices is appropriate (typically less than 5 meters) and try to keep them close to each other. Verify that the router connected to the gateway maintains connection with the external network and ensure good Wi-Fi signal quality in the environment.
You can check whether the password format is correct from the following aspects: 1. Currently, a password supported by the TuyaSmart app can contain digits, letters, special symbols, and characters in other special languages, such as Arabic and Spanish. Chinese characters are not supported. A password must contain no more than 64 characters. 2. Check whether the password contains spaces, for example, excess spaces at the end of the string. 3. Check whether the first letter of the password is capitalized. Some typing methods often capitalize the first letter by default, but a router password cannot start with an uppercase letter.
Please ensure that you have granted the necessary permissions for the app, such as location, Bluetooth, and local network permissions, and that your phone is connected to a Wi-Fi network. (For wired devices, make sure your phone and the device are on the same router.) If you are unable to find the device, please verify if the device is in pairing mode. Even if the device is in pairing mode and still cannot be found, it may be because the device itself does not support this function. In this case, you can try adding the device manually.
If your router supports both the 2.4 GHz and 5 GHz bands, but only one Wi-Fi name is displayed on the Wi-Fi search page of your mobile phone, perform these steps: Go to the Wireless page of the router. (The entry address is usually provided on the label attached to the back of the router). Go to the 2.4 GHz setting page, and set the Wi-Fi name (SSID) to （XXX）-2.4G, where xxx indicates the Wi-Fi name. Save setting. Go to the 5 GHz setting page, and set the Wi-Fi name (SSID) to （XXX）-5G, where xxx indicates the Wi-Fi name. Save setting. When the preceding settings are complete, the new Wi-Fi names will Appear on the Wi-Fi settings page of your mobile phone. Note:After the Wi-Fi names are changed, you need to reconnect the devices that use this wireless router. The password remains the same if it has not been changed. The following files describe how to configure the routers of some popular brands. Configure a Netgear router Configure an ASUS router Configure a D-Link router Configure a TP-Link router More settings：How to configure the router as a DHCP server?
Given the diversity of weather conditions, which include but are not limited to various types such as torrential rain, heavy rain, moderate rain, light rain, etc., we are unable to list every possible weather scenario in the weather condition options. Currently, we only display common weather conditions such as sunny, overcast, rainy, snowy, and hazy. It should be noted that cloudy weather is categorized under the overcast type here. Thank you for your understanding.
Whether the automatic notification-receiving function can be implemented depends on the logic of mobile phones of different vendors. Currently, no manual setting is required for Xiaomi phones where the App is installed. By default, notification permission is not granted on Huawei phones. Mobile phones of different vendors have different settings. Self-adaptation is required for specific settings.
Dear user, we are sorry for your inconvenience. If you do so: After adding the device to the App, select the device and enter the device control pannel. If the device supports the timing function, there will be a timing option on the device pannel. Click to set the timing (Cross-day timing is temporarily not supported, two timing tasks need to be set). If you need to repeat all 7 days a week, please check all days. If you need to modify the timing that has been set, just click the existing timing to enter the timing edit page. You can also implement the timing function by adding an automation. Automation allows you to Apply the timing function more flexibly. Cycle timing function and random timing function: Cycle timing function: it will allow you to set a cycle timing, you can set the device turn-on and turn-off within a specified time period. Random timing function: it will allow you to set a random timing, you can set the device turn on and off randomly. Use scenario: For example, after the owner leaves home, by turning on the random timing, it can simulate there is someone at home to a certain extent, so as to prevent thieves from entering the house. Note: It is temporarily impossible to make the timing accurate to the second; because the timing function of the Bluetooth device needs to be used by cloud services, you need to pair the Bluetooth gateway to use the timing and countdown functions. The cyclic timing function and random timing function are set by the product manufacturer. If you want to add the option of "loop timing function and random timing function", you can report this problem to the after-sales of the product so that they can improve it later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. Currently, phone notifications do not contain information about triggered automatic actions (the content of custom notifications is temporarily not supported，too). You are advised to enable both message center notification and phone notification when configuring the reminder method. Thank you for your support. We are optimizing the phone notification service.
Dear user, we are sorry for your inconvenience. The same device can form a group, and a Bluetooth mesh network supports only up to 8 device groups currently.
Dear user, we are sorry for your inconvenience. The system upgrade does not matter with the App, and the App does not prompt for an upgrade.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Check that your iPhone and Apple Watch are properly connected through Bluetooth. Check that you can log in to the App installed on your iPhone. Open the App on your Apple Watch. Tap and hold the screen to update data. If the data is not updated after multiple attempts, open the App on your Apple Watch, restart the App on your iPhone, and update the data again. If the data is still not updated, restart your iPhone and Apple Watch. Connect your iPhone to your Apple Watch through Bluetooth and try again.
Dear user, click "Me — Settings button in the upper right corner — Dark Mode", you can choose to turn on the switch to follow the system. After it is turned on, the dark mode will be turned on or off following the system. You can also turn off the follow system switch and manually select normal mode or dark mode. Note: Whether the dark mode of the device panel is compatible is set by the manufacturer of the product . If you want the device panel to adapt to the dark mode, you can report this problem to the after-sales department of the product so that they can improve it later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. Firstly, you need to make sure that your device can support XiaoDu, and also make sure that the device is online on both Apps. Note：Baidu Xiaodu is currently only available to users in China, and overseas users can no longer use Baidu Xiaodu. If not, it is recommended that you re-add the device and re-bind the skills to Xiaodu App. If it is still not resolved, you can provide us with the ID of the device: Open the App; Click on your device to enter the device details page; Click the icon in the upper right corner to enter the "More" page; Click "Device Information" to view the device ID, We'll troubleshoot for you. Thank you for your understanding and support!
Dear user, we are sorry for your inconvenience. Please check in the following ways: Your router cannot afford to handle simultaneous requests for too many devices at the same time. If you are using a Bluetooth or Zigbee device, it is your Bluetooth or Zigbee gateway cannot afford to handle simultaneous requests from too many devices at the same time. You can choose to distribute the devices to different routers or gateways. If there is still a significant delay, it is recommended that you use the group or the Tap-To-Run function in the App, which can support multiple devices to respond at the same time.
Dear user, we are sorry for your inconvenience. If you do so： Please confirm whether you are using the latest version of IFTTT/Alexa/Google Home App and skills. IFTTT/Alexa/Google Home App does not support such products. So we have to chosen a compatibility solution, so sometimes it cannot be displayed as the incorrect device category (for example: Alexa and Google do not support curtain switches and garage door switches) . Please confirm with the device seller whether the function you need supports third-party voice control, because this function may require additional development by the device manufacturer before it can be used (some device may not be completely suitable for Alexa/Google Home, such as: universal remote control, air conditioner, TV, etc.). When using the Alexa/Google Home App to control the color temperature of the light, the color temperature of the light cannot be completely white or yellow. This is because the setting range supported by Alexa/Google Home is 15% to 75% when the color temperature is controlled by voice. 0 to 100%, so the color temperature of the lamp cannot become completely white or yellow. Note:The third-party voice control options supported by devices are set by the product manufacturer . If you want to add a third-party voice control option for the device, you can report this problem to the after-sales service of the product so that they can improve it later. Thank you for your support and understanding.
This tip is a bit ambiguous, the real reason is that you don't have any devices in your App that support Xiaodu, Xiaodu found 0 device, so this tip is given to you.
When devices are added under a gateway, the gateway executes commands immediately in sequence, which results in Zigbee channel congestion most times. As a result, the last several devices respond with latency. It is recommended that you add fewer devices or set a latency for device response.
Dear user, we are sorry for your inconvenience. No. The Google Home or Amazon Echo speaker connects to a Bluetooth bulb through a bluetooth gateway.
Dear user, we are sorry for your inconvenience. Your devices are controlled by our cloud server through the App, so you can control your devices normally no matter where you are. If the device has been successfully connected to the network, ensure that the device keeps in the same network environment. When you leave home, you can use the our App to remotely control the device (App can monitor whether the device is in the normal connection state, and ensure that the device is in the normal online state). If you can't control your device when not at home,it may be that the device and the mobile phone are connected in the same local area network, but not connected to the network (Ethernet, generally it can also be called extranet).
Possible cause 1: The App account has no device that supports Google Assistant. Solution: Add a device that supports Google Assistant. Then, the skill appears in the binding list. Possible cause 2: A Google bug is triggered. If binding and unbinding are frequently performed within a short period of time, this bug is triggered. Solution: Visit https://myaccount.google.com/u/1/accountlinking to unbind the action.
Dear User, we are sorry for your inconvenience. If you change the network settings, the devices will be offline. You need to reconfigure the devices under the new network. Make sure that the Wi-Fi password you entered is correct, and note that there are no spaces before or after the password. After you connect the device to our App, then you can bind your account to smart speaker App. If you still have the problem,feel free to let us know. Thanks for your support.
Dear user, we are sorry for your inconvenience. If you do so: Open the App, click the device icon to enter the device control panel (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be controlled). Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of DuerOS (If not found, the device is not supported). After jumping to the connection page, bind according to the instructions of the App.(You can also click to view the binding tutorial). One DuerOS account can only be bound to one App account, an error will be reported if the binding is repeated. Baidu Xiaodu is currently only available to users in China, and overseas users can no longer use Baidu Xiaodu. Note: Users who login to the App through a third-party login method need to E-mail first, and then modify the login password (there is no initial password for third-party login) and use this E-mail to login to the App account when binding a third-party smart speaker. Since each third-party smart speaker is a closed platform, and therefore it is not possible to discover the device and directly connect it through the Xiaodu App nor the "Discover Device" function. It have to achieve connection by binding skills. Thank you for your understanding and support. Why can't I find any devices in the App after I linked the App to the DuerOS smart speaker? XiaoDu speaker cannot control smart devices?
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please make sure that your SD card is compatible with your camera. If you make sure it is compatible and the camera still cannot detect it, please remove it form camera and insert it again. You can use the card reader to the computer to format the SD card to FAT 32. You can also consult the sales staff how to format it to FAT 32. If you still cannot access the SD card, it means that the SD card is damaged. The SD card is a wearable product. Excessive reading and writing will greatly reduce the service life of the SD card. Thanks for your understanding and support.
Dear user. If the device is offline after a power outage or network disconnection, the device can automatically reconnect to the network after the network is restored. If not, please troubleshoot in the following ways: There are too many devices in your home that need to be connected to the Internet, which exceeds the load range of the router (ordinary home routers can only load less than 10 devices), so your device cannot connect back to the network. The quality of the network in your home is unstable, so the device cannot connect back to the network in time after the power is restored. If your problem still exists, please contact us and provide the device ID, and we will check for you. Thank you for your support.
Whether the camera can automatically return to a fixed position after losing track of a target depends on the device's own logic. If your device has this feature, it will automatically return to a fixed position after losing track of the target. If your device does not have this feature, you can disable the mobile tracking function and manually adjust the camera to the desired viewing angle.
To view the camera's live video on the phone, you usually need to use a specific application (App). Here are the general steps: 1. Install and launch the corresponding application on your phone. 2. Follow the instructions or App guide to add the camera to your App. 3. Click on the camera connected to your phone on the device page, and the live video will appear. The above steps may vary depending on your specific device and application. If you encounter any problems during the operation, it is recommended that you refer to the device's user manual or contact the device manufacturer for help. Hope this answer helps you!
Perform the following steps to adjust the monitoring sensitivity: Open TuyaSmart and tap the smart camera device to enter the device control panel. Tap ... in the upper right corner. Tap Motion Detection Settings and select the required detection sensitivity. Your mobile phone system automatically disables App's alarm push and alarm, click to view the solution. If the problem persists, we recommend that you remove the device from the App, add it again, and then perform the above steps.
Dear user, we are sorry for your inconvenience. If you do so： If you find the camera microphone can't work, that means you can't hear the voice in the video, please check whether the protective foil on the device has been removed (which may block the microphone). Check if the device supports microphone radio setting. The sound of the monitoring screen in the App is turned off by default, you need to click the speaker icon in the monitoring screen to turn on the sound. Check whether the media volume of the mobile phone is too low, or whether the mute button is turned on Use the dialogue function of the camera to confirm whether there is sound. If not, it considered as a hardware problem. In the device settings, find the device sound option and increase the device volume.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please confirm whether the App you are using is the App recommended by the camera; Enter the mobile Application market/App Store to check whether the App is the latest version; After updating the App to the latest version, check whether the camera's firmware version is the latest. The main function of the camera relies on cloud services, therefore if you do not use the App recommended by the device or update to the latest App, the camera will not be used anymore. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. If you do so: Click the button in the upper right corner on the camera device control panel to enter the device setting page. Find the "Motion detection alarm settings" option (different device will display a slightly different option name). In the "Motion detection alarm settings" page, you can find the "alarm function schedule" option. You can add schedule to choose to turn on and off the camera's motion detection function. You can also turn on/off the camera's motion detection function at the time you need by adding an automated method.（If the camera device is not found in the automation, please click to view the troubleshooting process） Note: The alarm function schedule function of the camera is set by the product manufacturer and cannot be changed by us. We are the App platform, so we do not have the authority to deal with this problem for you. If you want to add the "alarm function timing" option, you can report this problem to the after-sales department of the product so that they can make improvements later. Thank you for your support and understanding.
No. The Google Home or Amazon Echo speaker connects to a Bluetooth bulb through a bluetooth gateway.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please first check if you have scheduled / automated / countdown tasks set for the device, if any, suggest you delete the tasks instead. Check whether the device is shared with others, which may be caused by the operation of others. If there is a power outage in the home, some devices will be turned on automatically after the power is completely turned off and turned on again. If there is no such situation, please restore the device to factory settings in the App. In this way, the device will remove and delete all device-related information from the App's device list, then you can re-configure the device. There is a problem with the firmware of this device, please contact our staff to push the latest firmware for you. The power supply voltage of the device is unstable, which causes the networking module of the device reset frequently. Please check whether the power supply of the device is stable. If the device still turns on/off by itself after excluding all the above conditions, it should be a problem with the hardware of the device. Please contact the after-sales person of the device for after-sales.
After your SoCket is connected to a network, you can turn off or set the turn-off time for Appliances connected to the SoCket in a mobile phone App. However, turn-on or other functions of the Applications are unavailable. To use these functions, use a remote control.
Yes. Zigbee devices require a gateway to convert the Zigbee signals to Wi-Fi signals. Smart devices, such as mobile phones and tablets do not support the Zigbee protocol.
Yes. When the load power exceeds the rated power, the SoCket will automatically power off to protect you and your property.
Check Power and Connections: Ensure that the socket is properly connected to power and functioning normally. Check if the socket is connected to a reliable Wi-Fi network to ensure network stability and prevent any issues causing data transmission failure. Check Applications and Firmware: Make sure that the app you are using is the latest version for compatibility with the socket. Update the socket's firmware if necessary to ensure its proper functioning. Check Data Collection: Firstly, check if the socket provides an interface for energy consumption data collection. If this feature is not visible, it may not be activated. Contact the seller to activate it. If you find the related data collection interface, verify if there are any data records. If no data is present, there may be an issue with the socket preventing the correct collection of energy consumption information. Contact Seller Support: If you are unable to resolve the issue, consider reaching out to the seller's technical support team. They may offer more specialized support and guidance to help address the problem you are facing. Why is the device power consumption statistics in the App ares inaccurate or have errors? Why is the serious mismatch between the device power statistics data on the App and the actual device usage data?
Check whether the time of the smart door lock is correctly set. Check whether the dynamic password was obtained and used within 5 minutes because a dynamic password is only valid for 5 minutes. If the problem persists,please provide feedback in the feedback path.
First, determine whether you are using a Wi-Fi connected door lock or a Bluetooth/Zigbee connected one. If you are using a Bluetooth or Zigbee door lock, please check the online status of the lock. If the lock is currently online, you can directly open the door remotely through the app. If the device appears online in the app but you are still unable to unlock remotely, try using a fingerprint or password on the lock itself to see if the app immediately receives the door opening record. This will help determine if the network is truly functioning properly. If you are using a non-always-on Wi-Fi door lock (meaning you cannot directly remotely open the door through the app and the lock needs to be locally operated first), the app will display a call interface for remote door opening requests after someone initiates the request locally at the lock. The administrator user needs to respond to this request within a specified time frame (usually 60-90 seconds) to approve the door opening. Only after the approval, the door lock will be opened.
First, please confirm that the password you entered is correct. If it is a newly installed door lock, you may need to manually change the default factory password before it can be used properly. Common default passwords include: 000000, 123456. If you are sure that your password is correct and was working before but suddenly stopped working, please contact the administrator of the door lock (the person who purchased the lock) to inquire if the password you are using is a "temporary password" and if the password has expired. If the password is entered correctly and the door lock does not display "Incorrect Password" but instead shows "Password Verification Successful" while still being unable to open the door, this may indicate a motor malfunction or mechanical failure caused by improper installation. In such cases, you can try using a mechanical key to open the door or attempt to temporarily power the door lock using an external power source (such as a power bank). If none of these solutions work, you will need to contact the manufacturer's customer support for assistance.
Hello, the possible reasons for this issue are: 1. It may be caused by the inadequate strength of the wireless signal, resulting in an operation timeout; 2. The smart lock device or gateway device is offline and needs to be repowered or re-networked. 3. The gateway is too far from the door lock, and the signal is weak. Please try to control the door lock by bringing the gateway closer to the door lock.
Possible reasons are as follows: 1) The constant open mode is not closed; 2) During the installation of the door lock, the square steel was not cut or the length of the cut square steel was too long, causing the front and rear panels of the door lock to press against the square steel; 3) During the installation of the door lock, the direction of the clutch plug steel was not adjusted, or it was adjusted in the opposite direction.
Hello, Zigbee smart locks generally support features such as temporary passwords, dynamic passwords valid for five minutes, and offline passwords, etc., for specific inquiries, please consult the seller.
Please troubleshoot and handle according to the following reasons: 1) Finger is too dry; Solution: Blow on it or apply hand cream 2) Finger is wet; Solution: Wipe the finger dry 3) Finger is dirty, fingerprint is shallow or peeling; Solution: Wash the hand, replace the finger and re-record the fingerprint; 4) The surface of the fingerprint head is dirty; Solution: Wipe the surface of the fingerprint head clean; 5) Problem with the recording method; Solution: It is recommended to record multiple fingerprints of the same finger, and each time the fingerprint head light is on, place the finger on it, and when the fingerprint head light is off, remove the finger. Record different positions each time, and press the fingertip on the fingerprint head window during recording to ensure that each position of the same finger is recorded, which can improve the recognition rate.
If the sweeping robot has a problem with not being able to find the charging base properly (it won't turn in a circle when looking for the charging base and can't align the charging base), it means that the receiver head of the sweeper's keypad/display board is malfunction and the keypad or receiver head needs to be replaced.
Yes, you can use the camera to link with other devices, create smart scenes and automate operations. The camera can act as a trigger in the smart home system, when the camera detects motion, people or other specific events, it can start a series of linked operations. Here are some possible application examples: Security alert: When the camera detects motion or detects abnormal activity, it can send an alert to your phone, and automatically turn on the lighting system or trigger the alarm device. Automatic recording: When someone passes by the camera's field of view, the camera can automatically start recording video, to provide record and monitor. Temperature control: When the camera detects that there is no one in the room, it can adjust the temperature to energy-saving mode, to reduce energy consumption. To achieve these scenes, you need to use the smart home system's application or control panel to set and configure. The specific steps may vary depending on the smart home system and camera brand, so it is recommended to refer to the relevant user manual or contact the supplier to get more specific guidance and support.
A smart wall switch (L&N) is a light control switch that uses the Zigbee wireless communications protocol. You need a live (L) wire and a neutral (N) wire to install it and use it as a substitute for a conventional wall switch. When used in combination with a gateway, you can remotely control devices, turn on/off a device at a preset time, and link other smart devices.
You are not advised to carry a temperature and humidity sensor with you. If you have to, place the temperature and humidity sensor in a clean soft sack or plastic bag to prevent small foreign matter from entering the ventilation holes of the sensor. This helps prevent damage to the sensor and ensures its accuracy.
Smart water heater with Wi-Fi networking capability, you can use the App in your phone for remote operation, such as: starting up, shut down, raise &lower the temperature and other smart control. The App also allows you to check the working status of the gas water heater, malfunction, water use and gas consumption information.
No. An air conditioner mate is a Wi-Fi device. It can only send commands to and interact with other devices through the cloud server.
Different products have different function configurations and settings. It is recommended that you refer to the instruction manual, App, or consult the seller for related functions to disable the food dispensing button. Alternatively, you can place an obstruction on the button to prevent pets from using it.
Dear user, we are sorry for your inconvenience. The indicator light of this product will stay on for three seconds after power-on. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
Dear user, we are sorry for your inconvenience. When warm objects like people or animals pass by the detection area of the PIR motion sensor, the IR signal detected by the pyroelectric probe changes. The sensor then reports the change to App. The detailed reporting process is as follows: The PIR motion sensor reports its status to App after successful net pairing. When the sensor detects a possible human motion (an IR signal change), it sends a ''Motion Detected'' notice to App, turns on a 50-second timer, and enters the sleep state (it stops detecting motion within the 50-second sleep period). If the sensor detects an IR signal change within 10 seconds after waking up from the sleep state, it enters another sleep-wake up cycle without reporting to App. If the sensor detects no IR signal change within 10 seconds after waking up from the sleep state, it sends a ''No Motion'' notice to App. The automation-trigger condition-no motion interaction mechanism takes effect if App does not receive a ''Motion Detected'' notice after the sensor has sent the ''No Motion'' notice to App and the service is activated at the backend.
Hello, when the device fails to report heartbeat 3 times and a total of 12 hours have passed, it can be determined that the device is offline; If the gateway is powered off or disconnected from the network, it will be displayed as offline in the app within 3 minutes at the latest. After reconnecting to the network, if the device has a reconnection mechanism, it will be displayed as online within 30 seconds.
TuyaSmart supports storing device records in the cloud for six months.
Dear user, we are sorry for your inconvenience. After an audible and visible alarm reports a communication failure three times, the app determines that it is offline after 12 hours. If the gateway is powered off or disconnected from the network, the PIR motion sensor will be displayed as offline in the app within 3 minutes. After the gateway is reconnected, the detector will be online within 30s.
In an indoor space without walls between the door lock and the gateway, the communications distance can reach 20 m, but the recommended distance is within 15 m. If there are thick walls or high-power electric Appliances between the devices, the recommended communications distance is within 5 m.
Gateway/router signals can pass through a wall, but the distance depends on the thickness and materials of the wall. Technically, passing through a floor is impossible at the moment.
The air conditioner will attach a lot of dust and debris on the inner machine after long-term use, and it will breed a lot of bacteria, mildew and bad smell if it is not clear for a long time, which should be cleaned in time to avoid any health problems.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Firstly, remove the universal remote control in the App. Add the universal remote control to the App again, and then add your device. If you cannot find the device you want to add, you can use the DIY function to learn the remote control of the device. During the learning process, you need to align the infrared emitting area of the infrared remote control with the infrared remote control area of the universal remote control. The distance between the two is no more than 3cm. Press the button you need to learn according to the page prompts. If you can find the device but cannot save it. Please provide your device brand and model, as well as a screenshot of the related error page for us to troubleshoot. Thank you for your support and understanding.
Yes. After you connect a device to a gateway or router, you can view the device status remotely through the App. Zigbee and Bluetooth devices must be connected to a gateway.
Dear user. The length of time that the "device record" in the device control panel can be saved and the maximum record limit that can be saved per unit are set by the product manufacturer . If you think the "device record" function does not meet your needs, you can report this problem to the product after-sales party so that they can make improvements later. Thank you for your support and understanding. Note: If your device cannot update the device record for a long time, it may be that your device is offline. Please reconnect to the network.
Dear user, we are sorry for your inconvenience. You cannot operate devices, device groups, shared devices, or shared device groups without a shortcut switch through Apple Watch, and they are not displayed on the Watch page. Check whether there is a shortcut switch button next to each product on the Home page.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please check the device box or product manual, and make sure that the App recommended is our App. If it is not, compatibility problems are likely to occur, resulting in the situation that the device can only be opened and cannot be closed after the device is successfully added. If your device is a low-power device such as a sensor or devices that use batteries, it cannot be turned off. If you do not need it to continue working, please remove it from the App or completely power off the device. If it's not a low-power device. Please reset the device to factory setting and add it again. Then check whether you can turn off it by App. If you still cannot turn off it, please use the physical button and check whether you can turn off it. If you still cannot turn off it, please use the physical button and check whether you can turn off it. If you cannot turn off it by the physical button, please contact the manufacturer to check the hardware. Thanks for your understanding and support.
Dear user. If you do so: Tap the device in the device list to enter the device's control panel. Tap the button in the upper right corner to enter the device editing page. Tap to remove the required device from the devices list. Note that the automation and tap-to-run scenes asSoCiated with this device will become invalid. You can also reset the status of the net-pairing module to remove the device from your device list. After removing the device, you need to reset the device to pairing mode, and then re-configure the network; after the sub-remote learned under the universal remote control is removed, you must learn one by one in the universal remote control again (The memory function is not supported, and the removed device needs to be added again). Note: to asSoCiate a high-security level device such as a smart camera, video doorbell, or smart door lock with another account, you must remove it from the original account.
Dear user, we are sorry for your inconvenience. If you do so: Please check if your Bluetooth device and Bluetooth gateway have the same protocol. For example: Mesh Bluetooth device must be used with Mesh Bluetooth gateway; Bluetooth mesh Bluetooth device must be used with Bluetooth mesh Bluetooth gateway; if your device is a third-party Bluetooth device, it cannot be done through our Bluetooth gateway Controlled (Bluetooth 5.0, 4.0 and Bluetooth Mesh have different protocols). Please check if the gateway is within ten meters from the device for execution. If there is another network formed by mesh devices between the gateway and the device, please make sure the mesh devices in the middle are not low-power-consumption devices, such as door sensors, because they only transmit but not receive. When commands are received by these devices, the devices won't transmit them out. A combination such as gateway - door sensor - mesh light does not support communication.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please first check if you have scheduled / automated / countdown tasks set for the device, if any, suggest you delete the tasks instead; Check whether the device is shared with others, which may be caused by the operation of others; If there is a power outage in the home, some devices will be turned on automatically after the power is completely turned off and turned on again; If there is no such situation, please restore the device to factory settings in the App. In this way, the device will remove and delete all device-related information from the App's device list, then you can re-configure the device; There is a problem with the firmware of this device, please check whether the firmware is the latest firmware; The power supply voltage of the device is unstable, which causes the networking module of the device reset frequently. Please check whether the power supply of the device is stable; If the device still turns on/off by itself after excluding all the above conditions, it should be a problem with the hardware of the device. Please contact the after-sales person of the device for after-sales.
No. To develop Zigbee products, you must use Tuya’s gateway. Tuya can also directly provide gateways for you to OEM. If you need it, you can contact Tuya’s business. Zigbee3.0 is a unified application layer standard launched by the Zigbee Alliance. All sub-devices that fully comply with the Zigbee 3.0 standard can be interconnected in theory; Tuya’s Zigbee gateway and most sub-devices (except door locks and universal docking) are It conforms to the Zigbee 3.0 standard, so the Zigbee sub-devices of other customers can be connected to the Tuya gateway, and the Tuya Zigbee sub-devices can also be connected to other Zigbee 3.0 standard gateways. However, the Zigbee3.0 application standard is a relatively broad application protocol, and some functions are not included in the standard protocol. Therefore, some functions may not work properly after the devices of different manufacturers are interconnected. It is recommended to verify by actual access test The result prevails.
Yes.
The current device does not support this sharing method temporarily: Bluetooth Mesh, ZigBee, Infrared, Bluetooth Beacon devices, and some single-point Bluetooth devices are not supported to share with other users through this method. Recommended device sharing method: Add the user as a family member: If the other party is a family member or a trusted user, you can add them through the family management entrance - add members. After the addition is completed, the devices under the family can be shared in batches.
It supports from 2405M to 2480M, a total of 16 channels, at an interval 5M.
This is possible. When there is a network, the device linkage under different Zigbee gateways is cloud linkage.
Support, Zigbee devices can be connected to apps that support Matter through protocol conversion via a Matter gateway, provided that the Zigbee device is supported by the Matter gateway and the PID is configured on the platform beforehand.
This is because the service order of the product you submitted is in the Processing state. You can go to Value-Added Services My Services and then click the third-party smart speaker to view the service order status. If the service order is being processed, the service has not been enabled. Tuya will process the service order within two workdays. Please wait with patience.
If the sold products are under the PID for which a third-party access service is enabled, the products can be upgraded automatically to connect to the third-party voice assistant or platform without needing re-subscription.
Yes, you can apply for it through the ticket on the IoT platform.
This error may occur when the number of randomly assigned P2P IDs for peer to peer (P2P) transmission on the cloud is not enough. Contact Tuya technical support to add more P2P IDs.
This error indicates that the data in the buffer is too much to send out. It is often caused by poor network connection, and the image bitrate is greater than the network transmission capacity.
This error may occur if the UUID is correct but the authkey is wrong.
Connect devices to the gateway or router using wired, Wi-Fi, Bluetooth, Zigbee, and other network protocols to interact with Tuya IoT Cloud.
When the module sends a command, the MCU needs to first reply with the 09 command to confirm that it has received the instruction; then it should use the 05 command to report the data.
Double-break relay means that two lines can be disconnected at the same time, e.g., the zero live wire disconnected at the same time. Single-break relay can only disconnect one line, e.g. only disconnect the live wire.
The magnetically held relay requires relatively low power and more suitable for using in single fire switch solution, which is difficult to obtain power.
The Tuya-enabled switch module supports two types of external switches in three states. You can change the external switch type in the App to adapt to different application scenarios. The three states are as follows: Rocker switch: The load status changes immediately each time when you flip the rocker switch. Rocker switch: Status sync. The ON/OFF position of the rocker switch is consistent with the load status. For example, the lamp is turned on only when the rocker switch is flipped to the ON position. Self-reset switch: When you press and release the switch, it automatically returns to the initial position and the load status changes once.
Yes. When the recording function is enabled in the app, users can record audio by using the pet feeder.
You can first change the unit of "seconds" for the product feature points to "s", then refresh the workbench, and you will be able to add the unit of "minutes" in the component's style, which allows you to exceed the limit of 999 seconds.
The temperature and humidity sensor solution mainly utilizes the integrated temperature and humidity sensor to detect the ambient temperature and humidity periodically. Through the app, users can view temperature and humidity data anytime and anywhere. Core functions Network connection: After pairing, users can view device data in the app. Temperature detection: The sensor detects the ambient temperature periodically. Users can view temperature data in the app. Humidity detection: The sensor detects the ambient humidity periodically. Users can view humidity data in the app. Scene linkage: Users can create automation scenes in the app. For example, turn on the air conditioner when the ambient temperature is higher than 30°C. Battery level detection: The sensor detects the remaining battery level periodically. Users can view the percentage of the remaining battery level in the app. For example, 100% indicates a full battery level, and 20% or lower indicates a low battery level. Offline notification: If the battery of the sensor is dead and no data is sent to the platform in 12 hours, a notification is sent to the app, notifying users of the device offline. Benefits Standard: The no-code development process ensures a standard configuration. Accurate: The Sensirion SHT30 sensor chip secures an accuracy of ±0.3°C. Low-power: The power consumption is at a microampere level, and the button battery can serve more than one year. Mature: Integrated with the mature MEMS, the temperature and humidity sensor can be mass-produced. Powerful: This solution integrates a full-link of capabilities in hardware, app, and cloud service, enabling smart upgrades for products. Localization: The Zigbee gateway enables local device linkage so that automation can continue to work even if the gateway is disconnected from the Internet. For more information, visit: https://developer.tuya.com/en/docs/hardware/zigbee-temperature-and-humidity-sensor-solution-introduction?id=K9lf9j5icf96d.
PSM.
It means the module is in a low power consumption state.
In the configured alert notifications, you can configure ${device} or ${alarmDevice}, which will be automatically replaced with the name of the current product. For example, if you have a camera product named Tuya Smart and you want to show this product name in motion detection messages, set the alert message as follows: "Motion detected by ${device}." The alert message displayed in the App will be "Motion detected by Tuya Smart." If you still have a problem, submit a ticket for help from Tuya engineers.
If connect the route, you will write the SSID and password in flash, then reset, and after restarting, you will read the SSID and password from flash to connect. But if the front and back PID information is different, the SSID information will be cleared. You need reconfigure the network.
First, we need to clarify the type of pluggable module. Tuya currently supports the following three types: 1. NB module 2. Wi-Fi module 3. Cat.1 module. All three types of devices are activated by first activating the BLE Bluetooth module. During the activation and initialization, the default online status of the device is offline. The module is only activated when it is plugged into the slot. Once the module is successfully activated, for example, the NB module will connect to the carrier, and then report the device's online status through the NB gateway. Wi-Fi and Cat.1 modules connect to the MQTT server, which will report the device's online status. At this point, the cloud will set the device as online. When the module is unplugged, the NB device will update its offline status according to its heartbeat cycle time. Wi-Fi and Cat.1 module devices will no longer maintain a heartbeat with the MQTT service after being unplugged. After 2.5 heartbeat cycles, the MQTT service will disconnect from the device, and the cloud will set the device as offline.
Enable GPS on your mobile phone and grant related location permissions to the App. Then, try again.
Google has added some Bluetooth permissions to Android 12. If your App is compiled based on SDK 31 or above, you need to enable three permissions, namely BLUETOOTH_SCAN, BLUETOOTH_CONNECT, and BLUETOOTH_ADVERTISE, for Bluetooth pairing. If your App is compiled based on a version earlier than SDK 31, you can use Bluetooth pairing with the old permissions on Android 12. For more information, visit https://developer.android.com/guide/topics/connectivity/bluetooth/permissions.
error message： java.lang.IllegalAccessError: Class okhttp3.EventListener extended by class com.tuya.smart.android.network.http.HttpEventListener is inaccessible (declaration of 'com.tuya.smart.android.network.http.HttpEventListener'***) Run the following command to update the version number ofokhttpthat the SDK depends on: implementation 'com.squareup.okhttp3:okhttp-urlconnection:3.12.3'.
There are currently no issues. If the App has more than 100 registered users, some functions might not be available after December 31, 2023.
After the SDK was updated to version 3.34.x, the api was changed and two services needed to be implemented, as follows： TuyaWrapper.registerService(PanelMoreMenuService::class.java, PanelMoreMenuServiceImpl()) TuyaWrapper.registerService(PanelMoreItemClickService::class.java, PanelMoreItemClickServiceImpl()).
Check whether the permission to allow Start in background is enabled on your mobile phone. If not, apply for this permission based on your mobile phone model when the App is started.
It is possible that Tuya's plug-ins are included in the classpath, for example, classpath 'com.tuya.android.module:tymodule-config:0.4.0-SNAPSHOT'. To solve this problem, delete any Tuya plug-in in the classpath.
After manually scanning the connection with startScanWithScanType, the status of isMeshBleOnline will change to YES.
Type means device or group, and its value refers to the enumeration of HomeDataType. ID is the ID of corresponding type.
Call the following code:TuyaSdk.getEventBus().post(PageCloseEventModel()).
To bind a mobile number, you must purchase the value-added service for Verify with Mobile Phone SMS at https://www.tuya.com/vas/commodity/APP_SMS. API for obtaining a binding verification code: bindMobileSendCodeForVas API for binding a mobile number: bindMobile.
For an expression that has a map structure, such as TimerRule\SunSetRiseRule, the SDK has encapsulated the outer list array. For an expression that has a list structure, such as ValueRule\EnumRule\BoolRule, the list array must be encapsulated by the user.
Perform the following steps for troubleshooting: 1. Check whether the configurations are correct. 2. Clear the App cache by using the clean/rebuild project feature. 3. Check the Gradle version; currently, we recommend the 7.x version of AGP.
The Android sdk adds prerequisite conditions preConditions when creating scenes, it needs to call the interfacegetSceneDetail to get scene details based on IDto obtain preConditions information. Currently, the simplified scene list query interface does not return prerequisites.
Upgrade your gif library to 2.6.0 and keep the SDK version consistent with the Tuya SDK version. api "com.facebook.fresco:animated-base:2.6.0" api "com.facebook.fresco:animated-gif:2.6.0".
Confirm that the requested object is a global variable, otherwise it will be released early, for example: self.feedBack = [[TuyaSmartFeedback alloc] init].
By default, CocoaPods 1.8.0 uses the CDN Repo source. For more information, seeCocoaPods documentation. If you cannot access the source due to network conditions, you can edit thePodfileand restore the source toMaster Repo. - source 'https://cdn.cocoapods.org/' + source 'https://github.com/CocoaPods/Specs.git'.
This happens because there is no request to get the family, call the interface (void) getHomeDetailWithSuccess: (void (^) (TuyaSmartHomeModel ** homeModel)) successfailure: (TYFailureError) failure; Reference: https://gitbook.tuyacn.com/tuyasmart_home_ios_sdk_doc/en/.
No. Smart voice services are not supported for UID-based login and are available only for mobile number- and email-based login.
This error may occur because the device is offline. You can only send commands to the device when it is online.
This is likely because your OEM App uses a different device panel from that of the all-in-one App. Your OEM App uses a private panel generated by studio, which does not support DP query. Therefore, when you enter the device panel, it does not refresh immediately. The all-in-one App uses the all-in-one panel, which supports DP query. Therefore, when you enter the device panel of the all-in-one App, it queries the values of device DPs immediately and refreshes the panel after the results are obtained. To support DP query in an OEM App, we recommend that you replace the panel bound to the product on the IoT platform with an all-in-one panel.
Troubleshooting steps are as follows: 1. Authorize the current App to use "Precise Location", configure "Location Permissions" in info.plist; 2. Enable the following in the project's Signing & Capabilities: Access Wi-Fi Infomation Wireless Accessory Configuration.
The following conditions must be met: (1) Have a navigation controller UINavigaionController (2) The user must be logged in (3) Integrated with related UI business package (4) Implement the protocol method getCurrentHome in ThingSmartHomeDataProtocol If sceneDelegate is used in the project, you also need to call this code otherwise it will cause the UI business package interface to not jump normally [[ThingSmartBizCore sharedInstance] enableSceneDelegateCompatibility];.
We recommend that you follow the following troubleshooting steps: 1. Check whether power supply to the module is normal. The module's normal average working current is around 100 mA, and the transient current may exceed 400 mA. Check that power supply to the module is normal throughout the network connection process. You can use electric load to test the circuit load capacity. 2. Monitor the power supply voltage of the module with an oscilloscope to check whether the module is abnormal or burned down due to abnormal circuit design, excessive power supply voltage, or wild voltage fluctuations (a normal voltage ripple should be less than 100 mV). 3. Check hardware connections. The TX, RX, EN, and GPIO15 pins affect module startup (TX/RX/EN pins must be high level and GOIO15 must be low level upon power-on). Make sure that these pins work normally and are not interfered by the circuit. 4. Some circuit modules have large capacitance and may not be fully discharged when the power is frequently turned on or off. Try to extend the turn-off time and check whether the product can connect to the network. 5. If network connection still fails after the hardware is normal, try EZ, compatible mode, and mobile Wi-Fi to connect the product to the network. If the fault persists, provide us the product PID, a video of indicators during network connection, and a video of operations on the cellphone or a detailed description of your operations for analysis by Tuya. 6. Weak module signals may cause Internet connection failure. Enter the AP Internet connection mode and use Wi-Fi analyzer (available on the Android APP Store) to check whether the module signal is too weak. 7. With a USB to TTL converter, connect the RX port on the serial port tool to the printer port on the module (TX or IO2, confirm it with Tuya personnel) and GND to GND. Set the baud rate to 74880 and select ASCII for display. Provide the printing information in the whole process to Tuya for analysis.
Currently, most of the electrical and lighting products with no-code solutions can be tested by using the Tuya Cloud Test app. You can check whether a product can be tested by using the Tuya Cloud Test app in the Test Services step during the product configuration.
Metering method error or calibration error，for details, please check: Reasons for Measurement Value Error.
Adapter boards are all custom-developed, and whether the adapter board is certified does not affect the direct submission of the complete machine for certification. The important thing is to ensure that the internal firmware is developed based on a secure version of the firmware. If the client's procurement system strictly requires the adapter board to obtain a RED network security certificate, then consider having the adapter board certified. Additionally, the adapter board model can be associated with the module certificate of the same chip solution's public firmware. If the client insists on using custom firmware for testing or there is no public module certificate to rely on, the adapter board will need to undergo separate certification. The cost should be negotiated between the business line and the client.
The Value-Added Service Center offers a Zigbee certification transfer service, allowing clients to obtain a Zigbee certificate without becoming members themselves:https://www.tuya.com/vas/commodity/detail?code=ZB_AUTH_TRANSFER Typically, the costs for clients to obtain Zigbee certification themselves include the following: Adopters Membership: Annual fee, $7,000/year New Product Certificate Fee: $3,000 per product Use of Zigbee Trademark: $500 per product Zigbee Testing Fees: 3W RMB Therefore, opting for the transfer can save the annual membership fee.
Firmware is incorrect, rx 0 command corresponds to Railtest firmware, showing No such command. The firmware that should be flashed is Plugin firmware.
BQB: Bluetooth Qualification Body is authorized by the Bluetooth Special Interest Group (SIG), established in 1998. It is a membership-based alliance organization, and Bluetooth products sold in the market must be certified by this organization and meet its standards before they can be sold. For more information, please refer to: https://developer.tuya.com/en/docs/iot/bqb?id=K9xukntrhoifr DID: Declaration ID is an identification mark obtained after a product completes qualification certification, which can be understood as a certificate. There are two ways to complete qualification certification: 1. Testing required: The qualification certification process will obtain a new QDID (automatically generated by the system) and a new DID (purchased) to correspond to its product listing. 2. No testing required: The qualification certification process will obtain a new DID (purchased) and reference one or more QDIDs to correspond to the product listing. In summary: A DID can include (Listing) one or more QDIDs, and a QDID can also be referenced (Listing) by one or more DIDs. QDID: Qualified Design IDs are assigned to new Bluetooth designs during the qualification certification process that requires testing. QDID can be referenced by other companies during the certification process (can only be referenced to product types of End Product or Subsystem). For example, if a member company produces a Bluetooth module that is applied by another member company to their consumer products, the module needs to pass the qualification certification that requires testing as an End Product. After this certification process is completed, a QDID will be generated to provide to the member company purchasing the module. The member company purchasing the module can directly reference the QDID provided by the module manufacturer member company and choose the qualification certification process that does not require testing. In simple terms, if the Bluetooth of our company has passed BQB certific.
T3 Open does not support external Ethernet.
A firmware SDK is the software development kit of the firmware.
After SDK-based development is completed, the compiled firmware is shown in the following figure. Among the compiled bin files, the one whose file name ends with QIO indicates the production firmware and is used in production. The one whose file name ends with UA indicates the user area firmware and is used in debugging. The one whose file name ends with UG indicates the upgrade firmware and is used in the OTA update. File Name Description tuya_demo_elp_1plug_QIO_1.0.0.bin The production firmware, which is intended for modules whose flash working mode is QIO. tuya_demo_elp_1plug_UA_1.0.0.bin The user area firmware, which is used for chip flashing tools. tuya_demo_elp_1plug_UG_1.0.0.bin The upgrade firmware, which is used to upload the user area firmware and OTA firmware to the Tuya IoT Platform. You need to upload the compiled firmware to the Tuya IoT Platform to obtain the corresponding licenses. Perform the following steps to upload firmware: Log in to the Tuya IoT Platform and select a product that you developed. On the Hardware Development page, select Tuya Standard Module SDK and then click Add Custom Firmware. 3. Enter related firmware information and click Upload Firmware. 4. Upload the compiled firmware to the corresponding positions and click Save. 5. Publish the firmware. If the information shown in the following figure is displayed, the firmware is successfully published.
Whether Bluetooth pairing is displayed on the App depends on the device firmware. If the broadcast module of the device does not support Bluetooth pairing, the App does not display this function. The version of App SDK matters. You can contact Tuya technical support to obtain the latest SDK package.
The source device can send a command to a cluster of the target device. When the target device receives the command, it performs operations related to the cluster, such as modifying the attributes of the cluster. Each cluster contains a set of specific commands, which means that a cluster receives only the commands that it contains. Two types of commands are supported: basic commands and attribute association commands.
The production firmware of this chip platform needs to be synthesized using tools. Download GR551x_flash_tool_v1.0.2.0916, open the windows command line, and enter the command in the following format to merge and generate production firmware: GR551x_flash_tool_v1.0.2.0916.exe merge 2 "path where second_boot_fw.bin is located" "path where gr551x_tya_demo_fw.bin is located" name of the generated production firmware.
The device firmware records the initial version when the PID was created, and a new module firmware version will be generated after OTA verification and upgrade; the module firmware records the latest version on the current IoT, as shown in the following figure:.
heartbeat keepalive mechanism is adopted between the gateway and the Zigbee device. The gateway periodically checks whether the Zigbee device is online. If the Zigbee device does not respond in several periods, it is displayed as offline.
If your product supports this function, you can directly enable it in the Advanced Functions section in Function Definition during product development. If you do not find the Multi-ControlAssociation switch option in the advanced function,you can submit a Technical ticket.
Reason for the issue: It may be that the cloud storage product or app's configuration is incorrect. You can check the configuration of the product's region, currency, and other settings in the workstation to see if they match the user's information.
The login region of you app account may not be the same as the region where the redemption code applies.
Reason for the issue: 1) For V1 or old product group： If the corresponding device for the subscription is reset or removed, the subscription will be automatically cancelled. If the end user claims to be unaware of the subscription cancellation, it is generally due to the aforementioned reason. Process for handling issues: You can check the reset or activation records of the device logs and compare them with the subscription's unsubscribe time to confirm if the time is consistent, then it is for that reason. Step 1: Find the corresponding subscription in the Smart Protect workstation and click to enter the details page to view. Step 2，Find the corresponding device ID in the device management of the IoT platform and check the time when the device was removed or reset in the device logs： a, If the device removal time and subscription cancellation time are the same, it indicates that the subscription was cancelled due to the user removing or resetting the device； b, If these two times are inconsistent, you can submit an IoT platform technical work order to confirm the specific reason and provide the device ID and subscription ID. 2) Old product group and v1, v2 products. Possible reasons for automatic subscription deduction failure include insufficient funds and payment timeout, which may result in automatic unsubscription after exceeding the payment waiting time. Customers can find the unsubscription record of the subscription in the management background of the third-party payment platform. Users can also check the subscription details and unsubscription reasons in the payment platform's APP.
First enable the weather service API permission on the Tuya IoT platform, and then refer to the weather API documentation to make API calls. Weather Service API: https://developer.tuya.com/en/docs/cloud/weather-service?id=Kaiuyesukz1v3.
No. To support this function, contact Amazon for interconnection development.
Yes. RAW data is user-defined.
Raw functions apply to data points transparently transmitted in binary format and are not recommended. You may use raw functions to implement complex features that the Boolean, value, enum, fault, and string functions are not capable of.
The length of warning data is 1 byte. Each bit of bit0-bit7 can represent a warning. Set to 1 to indicate that a warning occurs, and to 0 to indicate no warning. A total of 8 types of warnings are supported.
Set a total cycle time, within this time period, you can set the opening time period and the closing time period to achieve a certain time for the cycle to turn on and off.
Pins are important during product function confirmation and typically are fixed. After pins are confirmed, they cannot be modified.
Isolated converters apply to labs and scenarios with high-security requirements. Typically, power frequency transformers are deployed based on the number of input power supplies to isolate the input power from the mains power. This protects lab personnel from electric shocks when they touch a cable because the isolated power supplies are not connected to the ground. Common LED fluorescent lamps on the market have non-isolated and isolated drive power designs. The non-isolated drive power design applies only to double-isolated products, for example, substitute products for bulbs. The LED and complete device are sealed in a non-conductive plastic container, with no electric shock risks. Level 2 products use isolated converters and are expensive. These products are necessary if the LED and output cable can be touched, for example, in LED lighting and street lighting scenarios. When an isolated LED drive converter is used, you can touch the LED lamp with bare hands without electric shock risks. When a non-isolated LED drive converter is used, a protective cover can isolate some mechanical components. In this case, do not touch the LED tube when the lamp is turned on.
The accuracy of the calibration resistor affects the measurement accuracy after calibration. If a 5% resistor is used, the measurement error may increase by 5%. Please select the calibration resistance accuracy according to product requirements.
The power-off memory feature configured for a device takes effect after the module is reburned with firmware. In addition, you need to use the device for 8s and then power it off for the preset state to take effect.
1.5A means the battery can be used for 1 hour according to 1.5A continuous discharge, so it can be used for 2 hours with 0.75A discharge. C represents the discharge rate, the battery is 1.5Ah, 1C, then the max. charge and discharge current of the battery is 1.5A charge and discharge multiplied by both.
For different metering chips, the corresponding module firmware is common, but the json configuration is different. For the measurement chip, the corresponding json needs to be configured, which can be configured on the Tuya IoT platform.
If there are multiple options available for page display, you can choose another one. If only the Link SDK option is available, it cannot be deselected.
Downloading: When creating a custom solution on the IoT Platform, you can download it in the Download Documents area on the Hardware Develop tab.
Hello, if it is a product under development stage, you can return to the third step "Hardware Debugging" to replace the appropriate module. If your device has been developed, you need to return the product to the "under development" state.
Connect them to the corresponding pins. When the high level is effective, normally pull it low; when the low level is effective, normally pull it high.
Problem description: During self-burning, the cloud module cannot be opened, and it prompts that access is denied or occupied. Solution: Close the computer antivirus software, or add the production solution to the antivirus whitelist and try again. Common problems during the burning process can be found at: https://support.tuya.com/en/help/_detail/Kcyugch1dtuej If there are still other abnormalities during the burning process, it is recommended to submit a technical support ticket to contact us.
The state before power-off is saved only if it is retained for over 5s. If it is retained for over 5s but not saved, contact Tuya personnel to check the fault. 1. Record a video about the power-off process and send it to Tuya personnel. 2. If Tuya personnel cannot locate the problem based on the video, you will need to send the device to Tuya for troubleshooting.
Perform P2P transmission initialization for the device. After the initialization is successful, the SDK receives a callback from the server. The callback function __TUYA_APP_p2p_event_cb is used. After that, the operation page can be displayed.
Submit a service ticket in Technical Support (https://service.console.tuya.com/8/3/create?source=support_center). Tuya technical personnel will process it for you. Attach the PIDs for which the function needs to be enabled and verify the account to which these PIDs belong.
App panel is RN structured, the screen will be refreshed after entering into the sub-interface, and the screen refresh delay will be different for different phones.
Cumulative data at the machine side can be reported in one time, real-time notification, and the full amount can be obtained from the APP side, which is suitable for reporting the map data of laser sweeping robot.
Single packet data incremental reporting at the machine side and real-time receiving at the APP side, applicable to inertial sweeping robot.
The calibration parameters in the module firmware should be adjusted according to the hardware circuit parameters. After calibrating and adjusting the parameters, each product will be performed on the hardware calibration in the production test before delivery.
A power statistics socket supports up to two channels for separate control due to the module's I/O pin limitations.
Yes.
The button on the Wi-Fi light can be switched on and off, with the network, brightness color temperature scenario switching and other functions, the specific function to see the actual product on the setting.
Yes. To achieve such requirements, use the MCU solution or customize the firmware.
Yes. However, we do not recommend you to reserve redundant buttons to prevent incorrect triggering.
Currently, some lighting products on the platform, such as light sources, support Beacon remote control with zero-code implementation. Upgrading the firmware to the latest version allows the lights to be used without network configuration, and can be paired with the remote control offline, greatly improving the convenience of product use.
It will be recorded that the power value is stored in the flash when not connected to the network. After the network is connected, the power data is reported and the data in the flash is cleared.
Due to possible differences in hardware, the power parameters of the measuring socket are calibrated in the module firmware according to the corresponding parameters of the device hardware, thereby correcting the voltage, current, and power parameters. Production Test on Wi-Fi Energy Monitoring Socket: https://developer.tuya.com/en/docs/iot/wifi-power-socket-production-test?id=K9eiu5skyksp6.
The power consumption data is obtained through an API interface, not in the form of data points (DP). Therefore, it cannot be refreshed in real-time. To update the data, you need to re-enter the control panel.
It is not supported, the music light function currently planned for the public version of the lighting panel has only considered the method of colored lights, and the white light does not currently support music rhythm;.
Flash after manual switch, network configuration for the first time: 1, If the flashing time ＜10S, the device is shut down and restarted, the device is still in a state of flashing; 2, If the flashing time ＞10S, the device is shut down and restarted, the device remains in a constantly on state.
If the error message "Business apiName: tuya.m.device.upgrade.status.update errorMsg: device module does not exist" is displayed, check whether the passed parameters are correct, whether the type of Bluetooth is 1 in the bean and 0 is passed in the method, and whether the type of the MCU is 9 in the bean and 1 is passed in the method.
YouTube：https://youtu.be/A12CMWfEcNU Tuya provides extensive lighting product solutions applicable to different phases, including module solutions, semi-finished PCBA solutions, and finished product solutions. Tuya's lighting product types include the A60 bulb, A70 bulb, BR30 bulb, PAR bulb, GU10 bulb, filament lamp, light strip, downlight, spotlight, ceiling lamp, panel lamp, light string, fluorescent tube, table lamp, and night lamp.
There are two modes: ‘CW-Flash/Warm Light’ and ‘CCT-Brightness/Color Temperature’.
Fast flash frequency: 250ms on, 250ms off, slow flash frequency: 1500ms on, 1500ms off.
This is because the record type data is not enabled. Contact Tuya personnel to enable it. Then, the unlocking record will be displayed.
You can create a product in IoT, select: Smart Lock-Residential Lock Pro, Protocol: Wi-Fi, Power Type: Low Power Consumption, then you can see the corresponding functions of this product solution.
The Tuya MCU SDK reserves an API for the MCU to request time from the server at any time. After invoking the void mcu_get_system_time(void) function defined in mcu_api.h to request the server time, the MCU invokes the following mcu_write_rtctime function to verify the RTC clock. void mcu_get_system_time(void) { wifi_uart_write_frame(GET_LOCAL_TIME_CMD,0); } #endif.
The Product Components tab shows the deliverables for purchase. Deliverables are the "items" that Tuya delivers (provides) to developers when they develop IoT-enabled products on Tuya IoT Platform.
During product creation, you can specify whether to deliver the default name. If you specify not to deliver the default name and the default DP name is not changed, you cannot obtain the DP name. This does not affect the usage of the product. You can change the DP name on the app device panel, which will be synchronized to the device.
Use temperature and humidity as examples, value = dp-dp_value.prop_value.value / pow(10, dp-dp_value.prop_value.scale). Use the obtained value to divide the scaling coefficient raised to the power of 10. Based on this formula, the DP value can be calculated.
Yes. You can create a scheduled feeding plan to dispense a specified amount of pet food at the specified time.
Under the current account, the total number of corresponding devices reported through the faulty DP function point today, one device can report multiple times.
The total number of faults reported by the corresponding device under the current account.
On the statistical day, the number of devices reported under the account through the failed DP point. Multiple times can be reported by one device.
The door lock supports issuing and creating temporary passwords, cloud API reference document: creating temporary passwords Remote door opening with secret currently only supports zigbee door lock, interface address: POST /v1.0/devices/{device_id}/door-lock/open-door Body field: password, String type, the original length of the password is 6, the password, the transmission uses the encryption algorithm using AES, the mode: ECB pkcs7padding data block 128 bits, the secret key is the localKey in the door lock information.
The platform is turned off by default, and the function will not be affected if it is not turned on; if you need to turn it on, you need to configure the signature information on the Tuya platform when you enable Google signature or re-sign yourself.
Please troubleshoot in the following ways: Please make sure that your App is not in the two states of "Release" and "Releasing". Please make sure that your OEM App has the number of rebuilds. After you modify the OEM App configuration, you have not saved it, so the system thinks the OEM App has not been changed, so the rebuild button is not displayed. If you modify the OEM App, you do not need to rebuild the OEM App (for example: after the 3.18 branch, add App store functions, modify privacy policies, change network distribution information, and modify Multi-language and other functions can take effect without rebuilding), so the system believes that the OEM App has not been changed, so the rebuild button is not displayed.
No.
This situation is mostly because the product is composed of different protocol modules. It is recommended that customers check the default network configuration in the product configuration.
When the doorbell button on the doorbell system is pressed, DP154 is reported from the interface. When the app is running in the foreground, the call answering screen appears. Depending on the macro definition selected by the reporting interface, an image or video is displayed on the call answering screen. You can design the doorbell answering screen as needed. Please refer to the documentation：https://developer.tuya.com/en/docs/iot-device-dev/sdk?id=K95019g5w3eiq#title-40-Devices%20are%20woken%20up.
Yes.
Matter supports: Air conditioners, air purifiers, gateways, fans, faucets, garage doors, humidifiers, lighting devices, sockets, curtains, thermostats, sensors, shower heads, and switches.
Advanced Features:Switch gradient, color temperature configuration, latitude and longitude biological rhythm, cloud scenario library, curve dimming, depth dimming, dimming gradient, color gradient, QR code networking.
Local timing does not require a gateway, cloud timing requires a gateway.
Make sure that the supported applications of the device match the current application being used. Even if the device is successfully added, if the supported applications of the device do not match the current application, control operations cannot be performed. Refer to the product manual to confirm that the device has been reset and is in network pairing mode. Ensure that the distance between the phone and the Bluetooth device is moderate (usually less than 3 meters), and it is recommended to be as close as possible. If adding a device via a Bluetooth gateway, ensure that the device is at a moderate distance from the gateway. Make sure that all necessary permissions (such as location information, Bluetooth permissions, etc.) have been granted during the network pairing process.
Dear user, we are sorry for your inconvenience. Unless otherwise specified, the devices only support 2.4GHz Wi-Fi. There is a possibility that the 2.4GHz and 5GHz mixed network will not be successfully configured, so please ensure that the Wi-Fi connected to the mobile phone is 2.4GHz. All routers have a 2.4GHz network frequency band. You only need to separate the 2.4GHz and 5GHz mixed networks to connect the device to the 2.4GHz network normally. Note: Only the device manual clearly states that devices that support 5G wireless networks can connect 5G wireless networks.
Dear user, we are sorry for your inconvenience. If you do so: You can click the device to enter Device control panel. Click Setting button in the upper right corner to enter Settings page. Click Check device network option, the network diagnosis will help us solve the problem faster for you, the diagnosis time is about 1 minute ( Only Wi-Fi devices support this function). Note: If your Wi-Fi device is a low-power device (such as a sensor device or a device that uses a battery), you will not be able to use this function (it will directly display the poor network status), because the low-power device is not connect with internet in the non-triggered state.
Dear user, we are sorry for your inconvenience. A Bluetooth device can connect to only one mobile phone at a time. To troubleshoot connection failures, follow these steps: Ensure that your mobile phone's network is working smoothly, and then reconnect the device to your new mobile phone. Ensure that your mobile phone's Bluetooth service is enabled. Ensure that the Bluetooth device is turned on and the power supply is normal. Ensure that the device is close to your mobile phone. Ensure that the device is in the pairing mode. If this device has been added before, reset the Bluetooth device and add it again; If the problem persists, contact our customer service personnel.
By default, the TP-Link router Wi-Fi names ( SSID ) for the 2.4 GHz and 5 GHz bands are the same. To distinguish the SSIDs for the two bands, follow these steps: 1. In the lower-right corner of the page, click Setting. 2. Click Wireless. 3. In the 2.4G Wireless area, set SSID to （XXX）-2.4G, where xxx indicates the Wi-Fi name. Saving setting. 4. In the 5G Wireless area, set SSID to （XXX）-5G, where xxx indicates the Wi-Fi name. Saving setting. When the preceding settings are complete, the new Wi-Fi names will Appear on the Wi-Fi settings page of your mobile phone. Note: After the Wi-Fi names are changed, you need to reconnect the devices that use this wireless router. The password remains the same if it has not been changed.
If the DHCP function of the router is disabled, IP address conflicts may occur when multiple home devices are connected to the router. To solve this issue, perform these steps: Go to the LAN page of the router. Locate the DHCP setting option. Enable DHCP. Save setting. The following files describe how to configure the routers of some popular brands. Configure a Netgear router Configure an ASUS router Configure a D-Link router Configure a TP-Link router.
Dear user, we are sorry for your inconvenience. A bluetooth mesh network supports 128 sub devices at most.
Dear user, we are sorry for your inconvenience. Smart devices can be controlled in LAN. The device only needs to connect to the external network through the router and register to cloud server when it is added for the first time, but after the cloud server registration is completed, even if the external network is disconnected, it also can be controlled through the LAN. Note: Not all smart devices can be controlled in LAN, such as: cameras, video doorbells and other smart devices that most of functions rely on cloud servers. Such as Zigbee devices, Bluetooth devices and some Wi-Fi devices (SoCkets, light bulbs, etc.) can all be controlled within the local area network (the local area network control function needs to be set by the manufacturer during production, if it is not set, it cannot be used).
Yes.
Dear user, we are sorry for your inconvenience. You can pair the gateway in the following steps: Locate the wireless gateway (Bluetooth) under the category "Gateway Control" Make sure the gateway is powered on and turn on the Bluetooth switch of the phone Press and hold the reset button of the Bluetooth gateway for 5 seconds Until one of the two indicator lights enters a fast flashing state (red light flashes, blue light is always on) Follow the instructions in the App to configure the network Note: When connecting the gateway, make sure that the mobile phone is connected to 2.4GHz Wi-Fi, otherwise the gateway cannot be registered through the cloud, and the connection cannot be successful.
Dear user, you can try to reset a new timing to refresh the cloud settings. Or you can try to "Restore factory defaults" your device (note: this will make the device disAppear from the list) and add it again. If your problem persists, please contact us again and let us know the specific time and device ID for further investigation.Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. The time zone of your device is set based on the time zone configured on your mobile phone (or other smart devices) when it is used to connect the device to the network. To change the time zone of your device already connected to a network, first change the time zone in the system settings of the mobile phone. Then remove the device, reconnect it to the network, and add it again (Currently, except for readd device, it does not support other ways to change the daylight saving time). Please delete the original timer then edit a new one to accommodate the DST. If the problem still exists, please remove the device and add it again. We will try to optimize the problem and do better to provide our users with a better experience! Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. Both wired and wireless gateways support local scene-based control. We recommend that you update the App and the firmware of all devices to the latest versions for a better experience.
Dear User, we are sorry for your inconvenience. This "scene" is set by the product's producer . If this mode is not what you want, you can feedback this problem to the after-sale product so that they can improve it later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. The App uses data from a third-party operator, which is Moji Weather for cities in China and Weatherbit for cities outside China. The specific data is displayed based on the home location you have set. If the App has connected to sensors such as an air purifier, a hygrometer, and a thermometer, the App preferentially displays weather information retrieved from the sensors (data from weather operators will no longer be available). Note: As the weather data is from the difference weather operators, thus there is a deviation of each weather App. Thank you for your understanding and support. How frequent is the weather and other data updated on the App Why isn't weather information displayed on the Home page of my App How do I sort the weather information items The weather forecast function in the App does not match the actual weather. Can I turn off this service?
Dear user, after you configure the device to the network, the device will interact with the server closest to you according to the area you selected during registration: For example, if your device is in US, and you choose to register for US to log in, the device will connect to the corresponding server in US, and select the nearest server, which can make your remote control of the device faster and more stable. If your device is in US, but you choose to register for the UK region and log in, then the device will connect to the corresponding server in the UK region. In this way, the interaction will be farther and the data transmission will be delayed. Note: To comply with the stricter data protection and localization principles of countries and/or regions, we has restricted cross-regional data transmission, after that, cross-regional access will be prohibited.
The App and device control page are controlled separately. The temperature switch in the App settings is to switch the weather temperature of the main interface. If the device page supports temperature switching, you need to switch the operation in the control page. If there is no option to switch units in the device control panel, it means that your device does not support this function. If you want this option, you can feedback this problem to the after-sale person so that they can improve it later. Thank you for your support and understanding.
Dear user. If you do so: If firmware needs an upgrade, a window will be popped up when you open the App. Simply tap "Upgrade" when you see it (the device will be temporarily offline when upgrading the firmware, and will automatically connect back to the network after the upgrade is complete). Alternatively, after you enter the device page, tap it in the top right corner and tap "Check for firmware upgrades" to see if any firmware needs an upgrade. Note:Once the device firmware is upgraded, it cannot be downgraded.
Refer to the attached figure, in the APP settings, enable the access to geographical location in the privacy settings.
Dear user, we are sorry for your inconvenience. If you do so: Tap a device in the device list to enter the device's control panel. Tap the button in the upper right corner to enter the device editing page. Tap Create Group. On the Select Device page, all devices that have been added to the account and have the same model as the device are displayed. On the device group page, click the button in the upper right corner to enter the settings page, and click the "Dismiss Group" button at the bottom of the page to dismiss this device group. If you want to manage different types of devices or devices that don't support groups, you can add these devices to one "Tap-To-Run/Automation" to meet your needs. If you want to achieve more complex group control functions, you can also add these devices to one "Tap-To-Run/Automation" to meet your needs. If the group creation fails, please click to view the solution. Thank you for your supporting and understanding. Unable to create a device group? The Third-party smart speaker can't control the group in voice? Some features missing after the device grouped or control group does not perform how it is?
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please confirm that the models and functions of the devices in your group are exactly the same. Ensure that all devices in your group are powered on and turned on. Ensure that all devices in your group are online. If the devices in your group are connected to a gateway, ensure that the gateway is online. If you find that some functions are missing after the equipment is grouped, this is because the equipment manufacturer has not added these features to the group control, you can feedback your needs to the after-sales personnel of the equipment. Note: The App now supports the grouping of devices of different models and functions, but because of the device models or functions are different, only on/off function can be use normally. If the issue persists, delete the group and create a new group. How do I create a device group? Unable to create a device group? The Third-party smart speaker can't control the group in voice?
We need to check if the FAQ in the backend configuration is enabled.
Dear user, we are sorry for your inconvenience. Set different names for these devices and use voice commands to control them.For example, name the lamp in the living room as "living room light" and that in the bedroom as "bedroom light". Then, tell your Alexa Echo speaker "Alexa, turn off the living room light" or "Alexa, turn off the bedroom light" to turn off the lamp. This method also Applies to Tmall Genie.
Dear user, we are sorry for your inconvenience. If you do so: Open the App, click the device icon to enter the device control panel (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be controlled). Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of Alexa (If not found, the device is not supported). If you want to link your camera and camera monitoring screen to Alexa Echoshow, but you can't succeed, then you need to contact the device seller to activate this feature for you (for your privacy, this feature is mostly closed). After jumping to the connection page, bind according to the instructions of the App (You can also click to view the tutorial). One Alexa account can only be bound to one App account, an error will be reported if the binding is repeated. If you cannot find the Skill in Alexa, it may be that this Skill is not supported in your region, please contact the sales representative for confirmation. If your device has recently been offline, upgraded firmware, or completely powered off, you need to repeat step 6 to add the device again, otherwise it may not be able to work with third-party smart speakers (This is because the firmware upgrade and power failure will cause the device to be offline. After the device is back online, the third-party smart speaker sometimes cannot obtain the real-time status of the device, so the third-party smart speaker will think that your device is still offline, and this problem can only be solved by adding it again). Since each third-party smart speaker is a closed platform, and therefore it is not possible to discover the device and directly connect it through the Alexa App nor the "Discover Device" function. It have to achieve connection by binding skills. Thank you for your understanding and support. Can devices synced to the Alexa App create routines in the A.
Dear user, we are sorry for your inconvenience. The smart speaker may fail to accurately identify or understand your command. You can change the device or scene name to a simple one such as bedroom light or living room light and use the new name to control the device or scene. If the problem persists, contact our customer service personnel.
Turn on Bluetooth on your mobile phone. In the App, tap the plus sign (+) in the upper right corner. Select a Bluetooth smart door lock and add it as prompted.
First, determine whether you are using a Wi-Fi connected door lock or a Bluetooth/Zigbee connected one. If you are using a Bluetooth or Zigbee door lock, please check the online status of the lock. If the lock is currently online, you can directly open the door remotely through the app. If you are using a non-always-on Wi-Fi door lock (meaning you cannot directly remotely open the door through the app and the lock needs to be locally operated first), you need to initiate a remote door opening request at the lock. The common way to initiate the request is by pressing the doorbell button on the front panel of the lock. For some older models of locks, you can try pressing 3#, 8#, 0#, etc.
When a smart door lock is installed, the anti-pry sensor may not be installed properly. As a result, anti-pry alarms are triggered. Re-install the smart door lock and ensure that the anti-pry sensor is installed properly.
First, determine whether you are using a Wi-Fi connected door lock or a Bluetooth/Zigbee connected one. If you are using a Bluetooth or Zigbee door lock, please check the online status of the lock and also pay attention to the signal strength. Make sure the distance between the gateway/router and the lock is not too far. If you are using a non-always-on Wi-Fi door lock (meaning you cannot directly remotely open the door through the app and the lock needs to be locally operated first), you can wake up the lock and try using the newly created temporary password. The first time you use this password, there may be differences due to network environment, so you may need to wait for 4-10 seconds. If the first attempt fails, you can try again.
There are two ways to open the door: If you have a mechanical key, you can insert it into the lock and open the door, then replace the battery after entering; If you forget to bring the key, you can use a power bank to connect to the emergency charging port of the lock via an Android phone data cable. After powering on, you can use fingerprint or password to open the door, then replace the battery after entering.
After setting up fingerprints and passwords on the lock, you need to download the App on your phone, register and bind the lock. In addition, you need to configure it separately to receive door unlocking records. Your home needs to have a 2.4GHZ Wi-Fi network, and the router should be as close as possible to the door lock to ensure a good signal. If the distance is too far, it will affect the signal push.
It is recommended that you troubleshoot as follows: If you find the device microphone can't work, that means you can't hear the voice in the video, please check whether the protective foil on the device has been removed (which may block the microphone). Whether the mobile phone is enabled to allow App to use the mobile phone microphone; Whether to open the microphone function of the App video interface; Whether the in-call volume is turned on, and whether the in-call volume is turned on is too low (when using the conversation function, the in-call volume is used instead of media volume. This is determined by the communication protocol of the mobile phone. ) In the device settings, find the device sound adjustment option, and increase the device sound. (the "device sound adjustment—volume" option in the device settings is set by the product manufacturer and cannot be changed by us.) In the device settings, find the device sound adjustment option, you can change the type of camera/doorbell ringtone (the "device sound adjustment—ringtone adjustment" option in the device settings is set by the product manufacturer and cannot be changed by us). The camera's offline alarm and pairing notification are usually set by the product manufacturer and cannot be changed in the App. Remove the device on the App side and rebind the camera Check whether there is sound when recording video on the SD card of the device. If there is no sound, the microphone or speaker may be faulty. If all of the above are normal and you still can't talk, you can click "Continue Feedback" to submit your question.
Dear user, we are sorry for your inconvenience. If your operation is reversed, this is because the camera is adjusted to the inverted mode. If there is a phenomenon that the settings cannot be saved, this is a problem of the product itself, please contact the equipment seller for handling. Thank you for your support and understanding. The following is an example (subject to the actual device page):.
Dear user, we are sorry for your inconvenience. Please check in the following ways: If the App can only save the screenshots of the record by the camera, it means that your App is not the latest version and is not compatible with your phone's electronic photo album. This problem can be solved after updating to the latest App. If there are only pictures in the message sent by motion detection, this is because motion detection does not support sending alarm videos. If you need motion detection video, you need to purchase cloud storage service. You also can change the continuous recording mode to the event recording mode. App store locally on the phone: 1). iOS will store the saved screenshots and videos in the photo album of our App. You can export the files in our App photo album to the iPhone's system photo album 2). By default, Android will generate a "Camera" folder in your phone's asset management folder. Screenshots and videos will be saved there (different folders are generated for each device). Note：If you are unable to save the screenshot, it means that your phone system does not authorize App storage related permissions, and you need to open all App storage related permissions in your phone system.
For security purposes, you cannot perform net pairing for devices in a Wi-Fi network without passwords.
Proper installation and positioning of the smart camera is key to ensuring its normal operation and maximum benefit. Here are some steps and suggestions to help you properly install and position the smart camera: Choose a location: First, choose a suitable location to install the camera. You need to consider the following factors: Field of view: Determine the area and field of view that the camera needs to monitor. Height: Install the camera at an appropriate height so that it can clearly see the target area. Protection: Try to choose a location that is not easily accessible or damaged to prevent it from being tampered with. Fix the device: Use the bracket or support that comes with the camera to fix the camera in the selected location. Make sure the installation is secure to prevent the camera from being knocked down or shifted. Network connection: Connect the camera to your wireless network or wired network. Follow the instructions provided by the camera and follow the corresponding steps to set up and connect. Power supply: Connect the camera to the power outlet. If your camera supports PoE (Power over Ethernet), you can use an Ethernet cable to transmit data and power at the same time. Adjust the angle and direction: As needed, adjust the angle and direction of the camera to ensure that it can monitor the area you want to monitor. You can use the camera's movement function or adjust the camera angle to achieve the best field of view. Test and configure: After the installation is complete, make sure to test whether the camera is working properly and configure and adjust it according to your needs. Prepare the application or web interface for accessing the camera and set up alerts, video recording and other required functions. Please note that when installing and positioning your smart camera, you need to comply with applicable privacy regulations and respect the privacy rights of others. Make sure your camera is used correctly for legal and appropriate monitoring.
Dear user, our App supports fast forward and double-speed of playback. If your device does not support it, it means that your device manufacturer has not adapted this function. You can report this problem to the product after-sales party so that they can make improvements later.Thank you for your support and understanding.
Dear user. Data may be unavailable under the following conditions: You have just purchased the cloud storage service. In this case, it is normal if there is no data. The SD card in your device is not in FAT 32 format and cannot store data in the SD card. You are using an SD card to store videos, and you have selected Event recording mode, but you have turned off the camera's motion detection function, so the camera will not record events. Your device is offline. Offline devices cannot upload data to the cloud or record. Your device is damaged and cannot upload data to the cloud. In this case, contact the device supplier to repair your device. Please check whether your login account is the account that was bound when purchasing cloud storage. To use a camera that has purchased cloud storage, you must log in to the account when purchasing cloud storage and bind the corresponding camera. If you replace a new account with a camera that has purchased cloud storage, you have to purchase cloud storage for the new account again. If you have purchased more than one camera, you need to purchase a cloud storage service for each camera before it can be used normally.
Dear user, normaly the floodlight will only turn on when the motion detection function is turned on or the floodlight is set to be always on. If your camera's floodlight cannot be turned on when movement is detected, it may be that the firmware or hardware of your device is malfunctioning. Please contact the sales of the device.Party to give feedback.
To safely clean and maintain the smart camera, you can follow these steps: Power off: Before performing any cleaning or maintenance, be sure to disconnect the camera from the power source. This can prevent accidental electric shock. Clean the case: Use a soft, lint-free cloth or paper towel to gently wipe the camera case and lens surface. Avoid using chemical cleaners, solvents or alcohol-containing liquids, which may damage the lens or case. Clean the lens: Use a lens cleaning tool or a dry, lint-free lens cleaning cloth from a professional camera equipment cleaning kit to gently wipe the lens to remove fingerprints, dust and stains. Avoid rubbing hard to avoid scratching the lens. Check the cables and connectors: Check whether the camera's cables and connectors are intact, without breaks or looseness. If any problems are found, they should be replaced or repaired as soon as possible. Software update: Make sure to download and install the latest firmware or software to ensure the security and functionality of the camera. Record and backup: According to your needs, regularly back up the video data or configuration files stored in the camera. This can prevent data loss and provide backup content when recovery is needed. Regular inspection and maintenance: Regularly check the operation and video quality of the camera. Ensure the normal operation of the video media (such as SD card or hard disk) and replace the damaged or full-capacity media when needed. Please note that if you are not familiar with the internal structure, circuit board or other high-risk components of the camera, do not attempt to disassemble or repair it yourself. If you have any questions or need more in-depth maintenance, it is best to contact professional technical support!
This situation should be caused by a problem with the robot's motherboard, so please contact the seller for after-sales service.
Hello, after the power is turned on, pressing the power button cannot be turned off, which may be due to the following reasons: If the equipment switch is used frequently, please check whether the switch button is damaged; Please check whether the connection cable of the face shell is loose or falling off; If no abnormality is detected, please contact the seller for after-sales treatment.
You can refer to the instruction manual to locate the position of the rolling brush/side brush, disassemble and clean it. If the problem is not resolved, it is recommended to contact the after-sales service of the purchasing channel.
A smart wall switch (L only) is a light control switch that uses the Zigbee wireless communications protocol. You can install it without changing the original lighting equipment or wiring. It is a substitute for a conventional wall switch. When used in combination with a gateway, you can remotely control devices, turn a device on/off at a preset time, and work with other smart devices.
Dear user, we are sorry for your inconvenience. You only need to slide to the left to delete it. If it cannot be deleted, there may be a compatibility problem with the control panel or firmware of the device. You can contact the after-sales service of the product to improve it.
You can trigger a wireless switch by tApping it, double tApping it, or tApping and holding it.
The Zigbee scene switch category does not support the creation of groups.
Dear user, we are sorry for your inconvenience. This is because the lowest value of brightness defined by most of Lamps is 25%. So when you adjust the brightness of the lamp below 25%, the lamp will turn off (some lamps can support lowering the brightness below 25%, but the lamp will flickering, and it will cause irreversible damage to the lamp itself).
Dear User, Sorry for the inconvenience. If it's the App unable to turn plug on, you can try to remove it and adding it again. If it is the physical button unable to turn plug on, we recommend that you reset it to see if the indicator light can light up. If the problem persists, it is recommended that you consult the after-sales of the product, that is, the customer service or the person in charge of the purchase channel, to troubleshoot the hardware problem, and I believe they will give you a satisfactory answer.Thank you for your support and understanding.
A water leak detector and a gateway use the Zigbee protocol for communication without needing cabling. Zigbee is a short-range, low-power wireless communications technology for smart home control systems that has become popular in recent years. It features ultra-low power consumption, high security, ad-hoc networking, and connection to multiple devices.
Dear user, please troubleshoot in the following ways: Confirm that the battery is new and has sufficient power. Remove the battery and re-install it for the App to obtain the battery level again. Turn off and on the device. The device will report the power data again.
Dear user, the voice of the device is set by the device manufacturer. If you want to add the "device's voice" option, you can report this problem to the after-sales of the product so that they can improve it later.Thank you for your support and understanding.
Hello, we suggest you first remove the device and re-add it under a stable network environment. If your problem still exists, please provide us with your device ID and firmware version number, and we will check for you. Open our App； Enter the control panel of the device you want to view, then click the button in the top right corner； Click "Device Information", you will see the "Virtual ID" of the device； Click the "Check for Firmware Upgrade" button, you will see the firmware version number of the device. Thank you for your support and understanding.
This product supports only 2.4 GHz Wi-Fi networks.
An air conditioner mate is a smart air conditioner control converter. It uses Wi-Fi and IR communications technologies to make a conventional air conditioner smart. It enables you to control the air conditioner's power switch and timer/delay switch remotely through TuyaSmart. It also allows you to record and view the power consumption data of high-power Appliances like air conditioners.
Dear user, according to the number of calculations, the battery can support about one year for triggered 50 times a day. In low power, in order not to affect your normal use, it is recommended that you replace the battery as soon as possible (within 24 hours).
Due to the sensing and detection principle of the sensor, there are the following requirements for the installation environment: This product is only suitable for indoor use and is prohibited from being installed outdoors. It is recommended to install it at a height of 1.2-2.1 meters above the ground; It is prohibited to install it near the air outlet, such as a fan, window, air conditioning outlet, etc.; It is prohibited to install it near heat sources, such as direct sunlight, heaters, fireplaces, etc.; It should not be blocked by large furniture or objects; Moving objects such as pets can also trigger the sensor to report.
This product is designed for indoor use only. We recommend that you install it at a height between 1.6 to 1.8 meters. Do not install the sensor near any air outlets, such as fans, windows, and air conditioners. Hot airflows and moving objects may cause false alarms. If possible, close the curtains. Do not expose it to heat sources such as direct sunlight, a heater, or a stove. Do not place large objects in the detection area, such as furniture and large bonsai.
If your pet feeder has a built-in battery, it can dispense food normally; if it does not have a built-in battery, it will not work after a power outage, and it will not be able to dispense food normally.
Different products have different function configurations and setting methods. It is recommended that you refer to the instruction manual, App, or consult the seller whether there is a function to adjust or disable the volume. If the pet feeder has the relevant function but no sound, it is recommended that you contact the seller for after-sales consultation.
When the refrigerator needs to be discontinued for a long period of time, you should clean the internal and external surfaces and accessories of the refrigerator, the door should be left with proper space, and then place the refrigerator in a dry and ventilated place to avoid undesirable odor. Note: Once the refrigerator is enabled, it is best to use continuously. Under normal circumstances do not stop using to avoid compromising the lifespan of the refrigerator.
Check whether the smart curtain motor is connected to a Zigbee gateway. You cannot connect the smart curtain motor to a Bluetooth gateway or a router that does not support the Zigbee protocol. Place the smart curtain motor close to the Zigbee gateway (within 5 m) and reconnect the motor to the gateway. If the problem persists, contact Tuya customer service personnel.
Dear user, we are sorry for your inconvenience. Please check according to the following conditions: Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), smart camera equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps), if your device has enabled the cloud storage function, additional 2M upload bandwidth is required, please confirm that your network has sufficient network bandwidth. The region where you live now is not the same as the region you selected when you registered your App account. As a result, the cloud server you access when controlling your device is far away from your place of residence, resulting in high latency. Our cloud server is not able to cover the area where you live, causing high latency between the cloud server you need to access and your device.
Dear user, we are sorry for your inconvenience. If you do so: Tap the device in the device list to enter the device's control panel. Tap the button in the upper right corner to enter the device editing page. Tap Check for Firmware Update to check whether any firmware updates are available.
Dear user, we are sorry for your inconvenience. You are advised to follow the troubleshooting gUIDe below: Check whether the device itself is operating abnormally, and attempt a reset if needed. You can also try disconnecting and reconnecting the device. Check if the router connected to the gateway is connected to the Internet. Make sure that the Wi-Fi signals are strong. Try to re-add the gateway if necessary. Check if your device is too far from the gateway or other routers to form a mesh network. You are advised to move the device in close proximity to the gateway or another controllable device. If the above conditions have been ruled out, your device is still unable to connect to the Internet, you can provide the App account number to us, we will arrange a professional engineer to conduct in-depth investigation for you.
Dear user, we are sorry for your inconvenience. If you do so: Tap the faulty device in the device list to enter the device's control panel. Tap the button in the upper right corner to enter the device setting page. Tap “Remove Device—Disconnect and wipe data” to remove the device from the device list and clear all data related to the device. If your device is offline, your device will unable to restore factory settings, because the device cannot communicate with the App and the cloud after it is offline. Note: If you just click Disconnect, the App will only remove the device from the App, and will not delete any data on the device, nor will the device enter the pairing mode (some devices have their own logic to automatically enter pairing mode after disconnection).
Only devices connected to a Zigbee gateway need to support third-party voice control.
Yes.
Pls check the indicator to determine if the gateway is under the network configuration mode. The red light flashes rapidly in the EZ mode, which is the default mode on the App. The red light flashes slowly in the AP mode, which needs to be switched on the App.
Zigbee 3.0 and physical layer IEEE802.15.4.
Sorry, it is not supported for now, the third party cloud needs to control the devices through Tuya cloud.
Fixed for 1 minute.
The gateway that supports LAN linkage, can realize the linkage of sub-devices of different gateways under the same LAN.
Currently, it is not possible, as each packet sent by the app is encrypted. The application layer decrypts each packet, and if it is opened, it will lead to the inability to decrypt the data, resulting in network configuration failure.
Pairing in EZ mode has been removed from the SDK. You need to specify WIFI_INIT_AP or WIFI_INIT_CONCURRENT for MODE.
Yes. To enable a breaker to enter the network pairing mode, reset the device and configure the number of power cycles on the ”Hardware Development“ page on the Tuya IoT platform.
The capacitor in the circuit stores electrical energy. If you quickly power on and off the module, the external power supply is disconnected, but the module may still have electrical energy and is not completely powered down. In this case, the power-off count does not increment when you power on the module. Therefore, after the module is powered off, you can wait for a few seconds until the module is completely powered down before you power it on again.
After re-power on, according to the success/failure flag bit in the reply command, module tells MCU whether the time acquired successful or not.
Networking: 15mA; Sleep: 3.2uA; Press and hold the button: 1.06mA; After the button is released, within 3S (with network): 170uA.
Products created through the wireless switch_dimmable version scheme can bind to lighting devices with the same communication protocol under the same gateway through the App panel. After binding, the wireless switch can adjust the brightness and color temperature of the lighting device. The wireless switch_basic version scheme does not have this capability.
This solution supports customized development, provides simple data points, and has low hardware requirements. However, the motor limit cannot be controlled, and motor self-processing may result in high temperature. In this solution, the motor is generally an AC motor, and the module is not directly connected to the motor. SoC curtain switches have a large market share and short production cycle.
It may cause your device to go offline abnormally and damage the Wi-Fi module permanently.
The wrong uid is used, please call GET {{url}}/v1.0/apps/{{schema}}/users?page_no=1&page_size=10 to get the correct uid.
OEM product refers to customer provided unique link via product owner (hereinafter referred to as the factory), who can directly create a new product similar to factory product configuration information to customer account. Meanwhile, factory can directly help customer managing this product, and using customer's product to place order and produce finished goods for customer. Operational Procedure: Factory could find the product that customer wants for OEM in the product list of Tuya IoT Console - Product - My Product. You can also quickly filter product by clicking the Search button next to Show Only OEM Product. Click the Manage Product link in the action bar of the corresponding product, and click OEM Product in the pop-up box. Understand Operation Mode and Notes. Click “Confirm” in the pop-up box to automatically copy the link. Send the link to customer, and when customer accesses this link and creates a product, the same product similar as current product will appear under customer's name. Notes: Currently only products that are in mass production and using Tuya firmware are supported to get online OEM link to create a new product. If factory's product has already enabled the smart speaker access service, when creating a new product, customer can select the required service directly within the smart speaker service range already enabled by the factory's product. System will automatically establish a management relationship between customer's new product and factory space, and subsequently factory can continue to manage product for customer and place order for this product. If product uses Tuya custom firmware, when factory uses customer's product to place order for the finished product in future, the finished product data of the corresponding order will belong to the customer by default. If current product uses Tuya General firmware, when factory uses customer's product to place order and produce finished goods, please make sure MCU file is burned with product I.
The previously purchased module can be used because the modules have the same firmware.
OEM products are developed products and their functions, module information, and firmware information cannot be modified. If you need to modify a function or firmware information of an OEM product, use the account to which the OEM product belongs to submit a ticket for changing the product status to Developing. To submit a ticket, perform the following operations: Use the account to which the OEM product belongs to log in to the Tuya IoT Platform. Click Tech Support in the top right corner. On the Technical ticket page, click Create. After evaluating the ticket and risks, Tuya will change the product status within two workdays. The ticket template is as follows: Title: Apply to Change the Product (PID) Status Content: PID: xxx Product name: xxx Target status: Developing Reasons for change: xxxx Shipments: xxxx Account contact: xxx Contact information: xxx After the product status is changed to Developing, you can click Submit in the Custom Requirements section on the product page of the Tuya IoT Platform to submit your customization requirements. After the manufacturer evaluates and confirms your customization requirements, you and the manufacturer can modify the corresponding function and firmware information.
It means the module is in smartconfig network configuration state.
The module is in AP network status.
You can mute alarms for individual devices in the alarm settings.
No, hyperlinks cannot be pushed as messages. If you need to push a webpage or website to users, perform the following operations: Enable Jumping page in the Advanced Functions section in the Function Definition step of your product. Click Add link in the Function descriptions column. In the Add Link dialog box, enter a name and the URL of the webpage or website. Then, the entry to the webpage or website will be displayed on the device panel.
You need to use the account to which the PID belongs to perform the following operations: Log in to the Tuya IoT Platform. Choose Product—Device—Device Details in the left-side navigation pane. On the page that appears, select the region to which the device belongs from the drop-down list in the top right corner, for example, Europe. In the search box, select Device ID, Device name, UUID, Module SN, or Device SN, and enter the corresponding information. If no information is displayed, the PID is not under your account.
Gateways do not have log data. You can view logs of devices connected to a gateway. Only devices report data through a gateway, and gateways do not generate data. In addition, device logs only contain reported DP data and do not contain the gateway status (online/offline). A gateway periodically sends heartbeat messages to the cloud to keep alive its status (online/offline).
This topic describes different firmware versions that support multiple protocols, such as Wi-Fi, Zigbee, Bluetooth mesh, Bluetooth Low Energy (Bluetooth LE), and Narrowband Internet of Things (NB-IoT). The following tables list the acronyms and full names of the firmware versions. This allows you to learn more about firmware uploads and updates. For more details, please see:https://developer.tuya.com/en/docs/iot/firmware-version-description?id=K9zzuc5n2gff8.
The uploaded package will not be split up and is sent without changing the format.
1、After the WIFI module is tested on production test 1 and production test 2, it can enter production test 2 again when powered on; 2、If the firmware configuration information in the PID on the IOT platform chooses not to support re-entry into production test 1, production test 1 cannot be re-entered; if support is selected, re-entry into production test 1 can be achieved through the following operations: —— In the production test environment (routes for production test 1 and production test 2 exist), power on three times in a row to enter production test, and if the time for the first two entries into the test is less than 5S, it will enter production test 1 the third time powered up. 3、If the device is connected to the app for more than 15 minutes, it will not enter production test. If you want to re-enter production test, you need to connect the device to the app, maintain the network connection, copy the device ID provided on the App, and we can operate it in the background to allow re-entry into the production test. —— The app cannot have the signal of tuya_mdev_test1 or tuya_mdev_test2 when pairing devices.
After modifying the color temperature value in the firmware configuration, you also need to modify the value of the DP point using the conversion algorithm: 1000000 / color temperature value. Example: 1000000 ÷ 2700 ≈ 370; 1000000 ÷ 6500 ≈ 153.
The new feature is written in Kotlin, while the old functionality is still maintained in Java.
The delay time of a single scene cannot exceed 300 minutes. If this limit is exceeded, the scene becomes invalid. If there is only one task in a scene, the last action cannot be a delayed action. Otherwise, the action fails.
This error message does not have any impact and can be ignored. This error message is returned because our SDK supports the LAN. If two channels are available to receive messages reported by devices in the LAN, this error message is returned.
If you add a maven repository in the root directory's build.gradle, you need to add it to both buildscript and allprojects. If you add a maven repository in settings.gradle, you need to add it to both pluginManagement and dependencyResolutionManagement.
You can try replacing the previous method's ty/tuya/tuyasmrt with thing/thingclips to see if it works. If it still doesn't work, you can submit a ticket.
The automated conditions and actions in the SDK do not support the raw type.
No. It indicates a Bluetooth mesh device.
This happens because you have frequently called the interface within a short time frame when there is non-compliance in stress testing or other activities. Your account is blocked for seven days.
The implementation methods are different. For SDK 4.0 and above, see the implementation method in the demo: https://github.com/tuya/tuya-ui-bizbundle-android-demo For SDK 3.2.x, use AbsPanelMoreExpandService. For SDK 3.3.x, use PanelMoreMenuService/PanelMoreItemClickService.
The device reports the MAC address to the cloud, and then the cloud sends the address to the client. The SDK does not perform any processing during this process. The hardware needs to provide the processing logic of the device's MAC address. Therefore, you need to contact the product vendor.
For more information, seeiOS Version Adaptation.
Make sure that the project you open is .xcworkspace and not .xcproject. Reference: https://guides.cocoapods.org/.
Objective-C.
If a DP is normally sent through the Message Queuing Telemetry Transport (MQTT) channel, a "changed DP" is received. However, if the MQTT connection with the App is interrupted, the DP will be sent through the HTTP interface. After the DP sending is completed, the device information will be pulled again to notify all DPs in the device information through a callback. This is why "all DPs" appear in the callback.
Check if the corresponding localization language is set in the project's "Localizations".
Example as follows: - (void)viewDidLoad { [super viewDidLoad]; // Monitor whether the home has been switched [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(homeIdDidChangedTest) name:@"kThingTPNotificationHomeIdDidChanged" object:nil]; } - (void)homeIdDidChangedTest { NSLog(@"\n== The home has been switched"); idThingFamilyProtocol familyImpl = [[ThingSmartBizCore sharedInstance] serviceOfProtocol:@protocol(ThingFamilyProtocol)]; ThingSmartHome *home = [ThingSmartHome homeWithHomeId:[familyImpl currentFamilyId]]; NSLog(@"\n== The current home is: %@" , home.homeModel.name ); }.
It depends on whether the function of reset notification push is set, which is set in the module.
You can solve this by hooking the current controller's thing_enableTYNaviRender method.
Ensure the system environment Node.js version =16.y.z(opens in a new tab) Use the latest version ofMicrosoft Visual C++(opens in a new tab) During the installation process, please turn offantivirus software to avoid affecting the installation. Or pay attention to whether theantivirus software has intercepted files during the installation process.
After you release the new MCU firmware, the old firmware becomes invalid. However, the released firmware cannot be deleted.
Development guide link: https://developer.tuya.com/en/docs/iot-device-dev/product-solution-ipc?id=Kaiuzp2w9wymy.
The hardware version is usually written on the version number of the PCBA silkscreen of the motherboard for easy inspection and consistency verification. For example, the module WBR1 version silkscreen "101" represents the hardware version V1.0.1, and the IPC motherboard silkscreen "SC-12011 V1.0.1" indicates the hardware version "V1.0.1". The software version can be checked by connecting the functional prototype to the APP, and viewing the device information on the APP, where the software version number is listed.
The official certification procedure supports adding finished product models directly to the module's NCC certificate. It requires filing the appearance and internal photos of each finished product model with the issuing authority. After completing the filing, the finished product can use the module's NCC certification number. If there are any changes to the product later, it needs to be re-filed. However, considering the risk of market spot checks, Tuya has suspended adding customer end product models to the Tuya module certificate. Current NCC certification plan: Tuya has obtained NCC certification for the module and issues an NCC sub-certificate with the customer's company as the main entity. The customer then uses the sub-certificate to list the product, and if other finished product models using the same module need to be added later, they can directly contact the agency for addition; Regarding NCC certification, you can go through Tuya's value-added service - NCC certification https://www.tuya.com/vas/commodity/CERTIFICATION_SUPPORT.
Tuya has stopped adding all new end product models directly to the Tuya module NCC certificate, and will also conduct a comprehensive review of previously added products to remove non-compliant additions. In recent years, the intensity of NCC spot checks has been increasing. We also understand that NCC spot checks will test the conduction and radiation projects of end products with normal functions, which are not included in the type tests for NCC module certification. They will also check whether the product's hardware is exactly the same as when the addition was applied for. Since the technical compliance of end product conduction and radiation and hardware change control are not under Tuya's control, if each manufacturer's end product model is added to a certificate held by Tuya, in case the subsequent end product spot check fails, it will lead to the cancellation of all products' NCC certificates, posing a great risk to Tuya and all parties involved. Currently, the NCC certification plan: Issue a module NCC certificate with the customer as the applicant (the applicant is the customer, the manufacturer is still Tuya), and the subsequent end product model additions are handled by the customer themselves. Spot checks are also handled by the customer themselves. If Tuya's certification fixed-frequency test module is needed, subsequent cooperation will be provided. NCC certification certificate held by the customer (only changing the applicant company to the customer's company, the manufacturer is still Tuya) can be completed through Tuya's value-added service - NCC certification https://www.tuya.com/vas/commodity/CERTIFICATION_SUPPORT.
The alliance has detailed usage requirements,https://www.bluetooth.com/develop-with-bluetooth/marketing-branding/.
The error "errorCode":"PRODUCT_OTA_CHANNEL_CONFIG" generally has the following reasons: 1. No corresponding firmware is created under the PID. 2. The created firmware type is not module firmware, it needs to be changed to module firmware as shown in the picture:.
Product empowerment: The continuously optimized value-added service enhances the market competitiveness of your smart cameras. Security and regulations compliance: Both the data and channel are encrypted in compliance with privacy regulations, such as GDPR. Customized package: Tuya customizes suitable service packages for your camera products for the markets in the target sales countries. Continuous operational revenues: After you sign a service contract with Tuya, Tuya will share the order benefits with you based on a fixed billing cycle. Service tracking: After enabling this service, you can view the information about area-based subscriptions and sales for different video cloud storage packages. Tuya provides purchase order records of the service, including the order creation time, payment status, and order amount, to help you better understand sales of the service.
Your product and app use Tuya solutions. Your IPC product's firmware already has video cloud storage capabilities. For specific support details, please consult your solution provider or supplier.
If you are operating on the PC side, you can contact your business manager to help you activate it; before activating the service, please confirm whether the product firmware itself supports the cloud storage function, so as to avoid the user's failure to activate. If you operate on the App, please refer to: How to purchase video cloud storage on the App?
Reason for the issue:It may be that the service entry was not found or the wrong page was entered. It is necessary to determine based on the user's video whether the user is in the correct interface.
As long as the product is embedded with the Tuya module and successfully connect to the third-party control service of Google Speaker, the relevant smart products in Tuya App can be controlled through the voice of the Google Speaker. You can view the relevant operation guide.
Failed to link skill, with the message "We were unable to link Tuya Smart at this time. Please try again later" As shown in the picture,you need to switch to the Google browser to link your own skills.
Like other common Tuya products, you only need to pay for modules and cloud services. Tokens are not charged.
If your products want to support control through smart speakers, you need to enable the voice access service for the products. For example, Just say to Echo: "Alexa, turn on the light", Alexa can help you open it. Tuya provides voice access services for 10+ mainstream voice assistants in the world, such as Alexa, Google, SmartThings Bixby, etc., allowing users to control your smart devices by voice and realize voice interaction.
Currently, our module can only be connected to the App of our platform, not yet connect to the App of third-party platform. But we have connected with Xiaomi's XiaoAi. Review the document and proceed to configure the voice console. After configuration, go to the value-added services to activate and implement the service.
The general infrared function can make the existing products expand the basic infrared functions, including the following functions: 1. Use the infrared code library of Tuya. 2. The panel function of the universal remote control. 3. The firmware supports infrared sending and receiving functions. 4. Voice function and other common functions.
Yes. A DP can be customized to display the storage capacity of an SD card in percentage mode (used space %/free space %). For more information, visit https://developer.tuya.com/en/docs/iot-device-dev/IPC_custome_function?id=Kb0lbwks8ta2u#title-20-SD%20%E5%8D%A1%E5%AE%B9%E9%87%8F%E7%99%BE%E5%88%86%E6%AF%94%E6%98%BE%E7%A4%BA.
Yes. You can use DP 194 (buzzer duration) and DP 195 (buzzer volume) to set the siren duration and volume, respectively. For more information, visit https://developer.tuya.com/en/docs/iot-device-dev/ipc_basic_solution_configuration?id=Kayhjmxb2v9li#title-25-%E8%9C%82%E9%B8%A3%E5%99%A8%E8%B0%83%E8%8A%82.
You can add the ipc_alarm_ind DP to decouple sound detection and crying detection. For more information, visit https://developer.tuya.com/en/docs/iot-device-dev/IPC_custome_function?id=Kb0lbwks8ta2u#title-22-%E5%93%AD%E5%A3%B0%E4%BE%A6%E6%B5%8B%E5%BC%80%E5%85%B3.
Yes. You can use either of the following methods to set the alert interval: Set the alert interval for the device through a custom DP (pir_alarm_interval). For more information, visit https://developer.tuya.com/en/docs/im-project-services/ipc_customize_solutions?id=Kb3k9q8daole7#title-25-%E7%A7%BB%E5%8A%A8%E4%BE%A6%E6%B5%8B%E6%8A%A5%E8%AD%A6%E9%97%B4%E9%9A%94%E8%AE%BE%E7%BD%AE. Set the alert interval through the Message Push Interval parameter on Tuya IoT Platform.
TLS and SSL encrypted channels with AES-128 encryption are used.
You can delete the corresponding DP from the Function Definition on the Tuya IoT Development Platform.
Yes, it is possible. This operation can work fine on the app side.
In the smart scene settings, the switch state reversal setting can be supported, but this function is not enabled by default. If you need to enable it, you can submit a work order to ask Tuya internal staff to configure it in the background. Currently, it does not support customer self-service platform opening.
It supports 15 hops.
The default frequency is 1kHz. If you need a different frequency, you would have to customize the firmware or modify the firmware yourself.
For the module and power statistics chip, if the power supply is a non-isolated BUCk, a single diode must be used for half-wave rectification. If bridge rectification is used, there will be problems.
Frequently press the reset button for more than 5S, the Wi-Fi indicator will flash quickly, and the flash will continue to flash for more than 10s. After the next power-on, it will enter the low power consumption mode.
1.Verify that the current sampling conforms to the differential wiring, which possible cause of interference. 2.The load is not connected, the relay is not conducting.
The Wi-Fi light power on will breathe and blink when it scans a signal value below -60dB, so please check the weak signal source of the production test router around the light, then turn off the product test router.
First connect the I/O port on the Wi-Fi module to GND for testing. If the indicator still blinks abruptly, check the circuit of the lighting product's drive.
The platform free development firmware shields the small power and small current. When the measured power is less than 3W, it will be filtered out. At this time, the app shows that the power and current are all 0. However, electricity consumption is counted in the accumulation.
No. As the voltage of the grid fluctuates, the current and voltage of appliances are unstable. Real-time data update is meaningless and puts much pressure on the server. In normal cases, the data is updated when the data change exceeds a certain proportion.
At present, in addition to directly opening the metering function without developing the metering socket, other MCU-developed products need to be opened for you in our background. You can submit the technical work order and finally we will handle the opening for you.
To enable this functionality, the PID (Product ID) needs to be provided to the Tuya integration personnel, who will activate it in the backend. Once this feature is enabled, the smart scene execution conditions can include a maximum of three options: switch, white light, and colored light.
Not supported, versions above V5.1 need to go through the host computer for production testing.
Dynamic password is an offline available password, valid within 5 minutes.
The tuya_get_dev_brief_info_list API of the SDK is used to obtain the device information, and devices without standard DPs will be automatically filtered out. You can search for not have std dp in the log file. If "id xxxx not have std dp" is found, the device does not have standard DPs. You cannot obtain the DP information of the device through this API. To check whether a device with a specific PID has standard DPs, consult Tuya‘s staff.
The tuya_ctrl_center_sync API can be used to refresh devices and rooms. The tuya_scene_sync API can be used to refresh scenes. It is recommended that these two APIs be called when data needs to be synchronized.
If the trial version of the App expires, the downloaded App will not be able to be used normally, you can log in to the App Service to complete the OEM App payment, the App can be used normally, and the system will retain all previous configurations.
The unique identifier used for launching apps in app stores.Every app has a unique package name that is the app's primary identifier. The application package name should be set using the company domain name information as much as possible to avoid repetition. It is recommended to enter letters and numbers, with . in the middle. The format recommends 3 segments, each segment starts with a letter, and each segment is controlled within 3-20 letters. Other symbols and spaces are supported, and "tuya" information cannot be included. (For example: Tuya domain name is tuya.com, then the package name can be com.tuya.smart ) If the app shows that it already exists when it is released in the app store, please modify it in time. Since the package name information is more important, you need to submit an Issue on the Tuya platform to modify it. The premise of modification is that the app has not been released in the app store. If it has been released, it cannot be modified.
No, you do not need to re-build your OEM app after you enable the skill customization service of third-party platforms. To enable the device to support the third-party platform-based skills, you must activate the corresponding third-party service for the device.
Yes. You can configure a DP to control how long the light is on in a single-PIR scene.
To obtain a mall UI BizBundle, perform the following steps: Log in to Tuya IoT Platform. In the left-side navigation pane, choose App App SDK SDK Development. Click an existing app in the app list or create an app if you have not had any app. Select Mall UI BizBundle in the UI Biz Bundle section and click the file that you want to download.
No, the account system will not be affected by the upgrade to v4.0.
If the module contains firmware, the Matter module needs to be calibrated with RF using the Extreme Hui instrument during burning; if the module does not contain firmware, the Matter module can be directly burned with authorization.
New product SKUs support Matter. 1. The current specifications of Matter provide limited standard categories and functions. Therefore, if you upgrade the existing devices to support Matter, the product performance and capabilities may be reduced, thus affecting the user experience. 2. Tuya modules support OTA and have been verified. However, only a part of the chips, such as the chips of the CB series Wi-Fi modules, can be upgraded. The cost is high for users to learn about and implement the upgrade. 3. To properly use Tuya devices with third-party Apps that support Matter, users have to upgrade the Apps, not to mention the many limits, which results in a poor user experience. In general, we recommend that you use new product SKUs for Matter compatibility integration. If you need to make existing devices compatible with Matter, contact Tuya technical support for a solution with custom functions.
Yes, iOS system version: 16.1 and above.
Matter (formerly known as Project Connected Home over IP or Project CHIP) is a networking technology built on top of the Internet Protocol (IP) to enable communication between smart home devices, mobile applications, and cloud services.
The device is powered on in the shielding box environment, the device broadcasts product-related information, the Tuya-specific dongle in the box obtains the corresponding product data, transmits it to the Tuya upper computer through the serial port, and the upper computer obtains the corresponding networking code for the product through the cloud interface.
There are two types: ordinary sticker label printing and laser engraving label printing.
Basic functions:Dimming, color adjustment, scene setting, music rhythm, linear dimming, power-off memory, M+N, timer, key reset.
The gateway is essential.
Applicable scenarios: 1. Environments without network: factories, warehouses, classrooms; 2. Simple linkage scenarios: offices, retail stores, museums, etc.
You can find the corresponding address in the (*.S) file and add printing to locate the problem. Fatal exception (28): epc1=0x4025bfa6, epc2=0x00000000, epc3=0x00000000, excvaddr=0x0000000f, depc=0x00000000 For example, if user1.bin is used, you can find the address 0x4025bfa6 in user1.S and check out the corresponding function.
Just define a pre_app_init empty function in the application code.
Two types of chips based on the method of data transmission to the Wi-Fi module: Pulse counting: HLW8012/BL0937 For these chips, the Wi-Fi module calculates the number and frequency of pulses and converts them into electrical data. Serial port integration: HLW8032/CSE7759/PL7211/V9801 For these chips, the Wi-Fi module receives data sent by the power consumption metering chip through the serial port and converts it into electrical data based on the agreed protocol. For more information, see: BL0937 Chip Application Manual, BL0942 Chip Application Manual, HLW8012 Chip Application Manual, and HLW8032 Chip Application Manual.
Call the function of GW_Wi-Fi_STAT_E tuya_get_wf_status(VOID), the returned parameters can be compared with GW_Wi-Fi_STAT_E structure.
You can register the interrupt callback function by using the hal_gpio_set_interrupt_init API.
Only wireless switches and sensors support Bluetooth LE.
If the first authorization is successful and the authorization area is not erased in subsequent flashing, re-authorization is not required.
During flashing, the original factory tool for serial port flashing needs to be used to erase the whole flash memory. If not, the bound mark cannot be removed, and pairing fails.
Only authorized devices can be discovered by the App. Check whether authorization is performed.
The mac address is a physical address and cannot be changed.
Yes.
Not supported yet.
For Linux system, the user provides cross-compilation toolchain, and Tuya compiles the SDK according to the toolchain and gives it to the customer; For Andriod system, if the customer does not provide the toolchain, the customer needs to provide the Android system bit number and API version number, and Tuya uses the toolchain generated by ndk to compile.
Module Firmwareis the version selected on the current IoT platform Device Firmwareis the firmware version currently authorized in the device.
There are 40.
The local timing deviation for Bluetooth is 30 seconds within a 24-hour period.
No rollback function is available. It is recommended that you delete the DP and add it again.
There is no charge for these. Module purchase is chargeable. The price depends on the platform. You can refer to the Hardware Development section to check the module price.
Yes.
First, confirm whether the module you purchased has been programmed. Refer to the link: https://iot.tuya.com/exp/bulletin/detail/?id=0000000sko. Starting from November 21, 2022, the platform will charge a programming fee of 200 yuan for orders with a single product module quantity less than 100 pcs. No separate programming fee will be charged for orders of 100 pcs and above. You can also choose empty delivery when placing an order and complete the programming yourself after receiving the goods. If it is an empty delivery, refer to the link for guidance on completing the programming yourself: https://support.tuya.com/en/help/_detail/Kcb5emurz0j6h. If the program has been programmed, it is recommended to use an adjustable DC power supply of 3.3V to power the module for testing and verification. Module power supply requirements: 1. Output 3.3V voltage ripple less than 100mV. 2. Wi-Fi module average current is about 80mA, module power supply needs to have an output of 200mA average current capability, power supply output dynamic current needs to reach a peak of 450mA. 3. Bluetooth and Zigbee module power supply, module power supply needs to have an output of 50mA average current capability. And under dynamic conditions, when the output current is 100mA, the output voltage is not lower than 2.8V. If the same peripheral circuit, other modules work normally, only the newly purchased module cannot work (such as no power output, device does not work, etc.), you can use the A-B-A test to lock the fault point, which will be faster than random testing to verify which components caused this fault. A-B-A exchange is a simple and direct cross-check test that can confirm that the observed problem is not systemic. The A-B-A exchange operation method is as follows: 1. Remove the suspicious component (A) from the original faulty board. 2. Replace the suspicious component (A) with a known good component (B) and check if the original board is now working properly. 3. Install the suspici.
The main reason for the failure of empty delivery burning is the insufficient power output capacity of the serial port. Refer to the attached figure, serial ports with a similar structure will lead to burning failure. To avoid wasting too much time during the burning process and to improve debugging efficiency, it is recommended that you purchase Tuya serial port. For other burning failures, it is suggested to take photos of both sides of the serial port, the wiring photos of the module and the serial port, and submit a technical work ticket for processing.
You can submit a ticket, specifying your product ID, development method, and the module you need to add. Tuya staff will evaluate and help you with the issue.
Both magnetic latching relays and ordinary relays are commonly used components in electrical control circuits, but there are some differences between them. 1. Working Principle The ordinary relay works by generating a magnetic field through an electromagnet, causing the contacts to close or disconnect, thereby achieving circuit switching control. When the electromagnet is powered on, the generated magnetic field attracts the contacts to close. When the electromagnet is disconnected, the magnetic field disappears, and the contacts return to their original state. The magnetic latching relay also generates a magnetic field through an electromagnet, but its contacts can be maintained in a closed or open state. When the electromagnet is powered on, the contacts close. When the electromagnet is disconnected, the contacts still remain closed until another signal comes to break the contacts. 2. Main Usage Ordinary relays are usually used in circuits that require frequent switching, such as robot control, motor control, and so on. As the contacts of the ordinary relay close or disconnect instantly, it is easy to generate arc during frequent switching, which leads to the burning of the contacts and reduces the service life. Magnetic latching relays are suitable for circuits that need to maintain the state of the switch for a long time, such as power switches, single fire switches, main circuit breakers, and so on. Due to the contacts of the magnetic latching relay can be maintained in a closed or open state, it can avoid the arc generated by frequent switching and extend the service life. In short, the two types of relays need to be selected according to specific application scenarios and requirements to achieve the best effect.
You may have created a custom solution, the module is just a networking function, generally does not need to be configured, except for special common firmware that may need to configure the wake-up pin or baud rate.
Problem phenomenon In the hardware development step of product development, the copy below will be prompted. Solution If the firmware is not maintained by Tuya, please contact the firmware manufacturer to check the following items to ensure that there is available firmware: 1. Make sure there is a firmware version in the firmware management, the firmware package contains the production firmware, and the shelf status is Shelf. 2. Make sure that the listing scope of the firmware version you list is unlimited, or if you have a limited scope, please add the corresponding product ID or the account of the corresponding owner of the product to the authorized scope whitelist, so that the corresponding product can be selected. this firmware version.
For U series modules (taking CBU as an example in the attached figure), align the pins on the bottom of the module with the probes on the fixture. Press the module downward and adjust it from side to side to ensure the probes are successively locked in the middle of the solder pads.
Dear user, we are sorry for your inconvenience. You can follow the steps below: On the "Home" page, click the "+" icon in the upper right corner to enter the device selection page. Select the right category and find the device (Wi-Fi) that needs to be added. After clicking, you need to enter the Wi-Fi password (most devices only support 2.4G wireless network). Click the button in the upper right corner, you can select the pairing mode of the device (fast blinking is EZ Mode, slow blinking is AP Mode). If your indicator is not flashing, it means that you have not reset your device to the status of network configuration, please click "The indicator is not flashing" for help. After selecting the indicator status of your device, you will enter the corresponding network distribution process. If the process of adding a device is stuck in the "Scan devices" stage, please refer to "What should I do when my device fails to connect to the network?" If it is stuck in the "Register on Cloud" and "Initialize the device" stage, please provide your device Virtual ID and the time, we will arrange a technician to check for you.
Dear user, we are sorry for your inconvenience. Yes, you can connect to a bluetooth product only after passing the authentication on the Cloud.
Dear user, we are sorry for your inconvenience. You can follow the steps below (this is a general method, please refer to the product manual for specific methods): Devices with a reset button: Firstly, make sure the device is powered off for more than 10 seconds before powering on the device. Then long press the reset button on the device for about 5 seconds (for switch devices, the reset button is mostly the switch Button itself). Wait a few moments until the indicator light starts blinking rAPIDly. The device enters the pairing mode. You can add it now. Lighting equipment: Firstly, make sure the device is powered off for more than 10 seconds before powering on the device. Then turn on and off three times (on-off-on-off-on) power of the device (2 to 4 seconds between each on and off). Wait a few moments until the lighting starts blinking rAPIDly (Bluetooth lamp will not blink all the time, it will be on after a few times). The device enters the pairing mode.You can add it now. Note: Bluetooth devices do not support individual sharing, only sharing by adding family members. After sharing with family members, only one person can control the Bluetooth device at the same time. Other people's Apps will show that the Bluetooth device is offline. Only when the user exits the App, another person can control the Bluetooth device.
Dear user, we are sorry for your inconvenience. Please check in the following ways: When you remove the device from the App, the device is simply removed from the network, which does not mean that the device will automatically enter the pairing mode (most of bluetooth devices and lighting devices will automatically enter the pairing mode after you removed them in the App). If the device you removed is a Zigbee device, the Zigbee device just disconnected from the Zigbee gateway when you removed it from the App. If you need to add it again, you need to reset the Zigbee device to pairing mode.
Dear user, we are sorry for your inconvenience. As the Android mobile phone system considers Bluetooth broadcast to have a positioning function, so it must authorize the positioning permission before scanning for Bluetooth devices. Therefore, only after you turn on the location permission of our App in the phone permission settings, then you can scan the Bluetooth device normally, so that you can correctly add the Bluetooth device to our App.
Dear user, we are sorry for your inconvenience. First, check whether you are using a 5 GHz/2.4 GHz dual-band router. If the Android mobile phone is connected to a 2.4 GHz Wi-Fi and has no problem connecting to the device while your iPhone is randomly connected to the 5 GHz Wi-Fi and cannot connect to the device, you need to manually connect your iPhone to the 2.4 GHz Wi-Fi.
Dear user, we are sorry for your inconvenience. To screen all notifications from Message Center, use either of the following methods: In the App, choose Me—Settings—App Notification. On the Notification Settings page, switch off Enable notifications. In the App, choose Me—Message Center, and tap the gear icon in the upper right corner. On the Notification Settings page, switch off Enable notifications. To screen notifications from the Alarm, Home, or Bulletin tab pages, go to the Notifications Settings page and switch off Alarm, Home, or Bulletin as needed.
It is recommended that you try again when the network is good or switch the network, and upgrade the firmware and App versions to the latest. If the problem persists, please provide feedback in the App feedback path.Thank you for your understanding and support!
Dear user, we are sorry for your inconvenience. In the background, a scenario trigger involves an edge trigger and a continuous trigger. After you set the temperature threshold of 0°C, lights will be turned off when the threshold is reached. If a continuous trigger is adopted, lights will be automatically turned off after you manually turn them on if the temperature is higher than 0°C. To avoid this problem, an edge trigger is adopted. Lights are turned off only when the temperature rises above 0°C.
After resetting the device, you need to reconfigure automation/one-click execution.
Dear user, we are sorry for your inconvenience. The inconsistency is mainly caused by the protocol and CPU usage, and hardware factors such as the memory usage. In addition, the network throughputs of different devices affect the number of connected devices.
Dear user, we are sorry for your inconvenience. Theoretically, Bluetooth mesh devices can cover an indefinitely large space because they can function as trunks to transmit data to each other. The effective communication distance indoors between each two Bluetooth mesh devices is about 10 m (there are no metal barriers or multiple walls in the middle). To ensure an effective Bluetooth mesh communication network, a Bluetooth mesh device that is powered by a SoCket must be available within the 10 m radius circle of another Bluetooth mesh device. Battery-powered devices, for example, low-power sensors, do not have data relay functions.
Dear user, we are sorry for your inconvenience. Each user account will have its own Bluetooth mesh Network ID. During the process of adding a device, the information will be synchronized to the device to be added to complete the basic configuration. Once configured, Bluetooth mesh devices will no longer be discovered by others, nor will other users control your Bluetooth mesh device. We also use multiple encryption during communications to keep your information secure.
Dear user, we are sorry for your inconvenience. Whether the device supports "Cloud Storage" is set by the product manufacturer. If you want to add the "Cloud Storage" function, you can report this problem to the after-sales of the product so that they can make improvements later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. The third-party smart speaker currently only supports the created Bluetooth groups (lights and SoCkets). It does not support Wi-Fi groups created in the our App. But you can use the Group function in the third-party smart speaker App to create Wi-Fi groups, these Wi-Fi groups can be controlled by third-party smart speakers. You also can create an Automation or Tap-to-Run to instead of Wi-Fi groups in our App, they are able to be controlled by third-party smart speakers, too (only Alexa supports the control of "Tap-to-Run and Automation"). Thank you for your support and understanding. Amazon Alexa Google Home Tencent Xiaowei Baidu Xiaodu.
Dear user, we are sorry for your inconvenience. Xiaowei does not support the voice control of Wi-Fi groups created in this App (Bluetooth groups are supported, but it needs to be used with a Bluetooth gateway). It only supports the voice control of groups created by itself in the Xiaowei App. After synchronizing all Wi-Fi devices to Xiaowei App, you can create a group of Wi-Fi devices in Xiaowei App, so that you can use Xiaowei to control the voice. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. Google Home does not support the voice control of Wi-Fi groups created in this App (Bluetooth groups are supported, but it needs to be used with a Bluetooth gateway). It only supports the voice control of groups created by itself in the Google Home App. After synchronizing all Wi-Fi devices to Google Home App, you can create a group of Wi-Fi devices in Google Home App, so that you can use Google Home to control the voice. Thank you for your understanding and support.
Dear user. We have supported to Xiaomi Xiaoai. If you want to use Mihome to control our device, firstly you need a Xiaoai speaker, and then you need to make sure that the device supports Xiaomi Xiaoai voice control (Whether the product is supported can refer to the manual or consult the seller). Then you can use the Xiaoai speaker to control the device. Limited by Xiaomi's restrictions on us: We can't tell you how to connect the App to Xiaoai. We recommend that you consult Xiaoai's customer service. The devices in our App cannot be synchronized to the Mihome App's device list. You must have a Xiaoai speaker, after synchronizing the device to Mihome, you can only control our device through the Xiaoai speaker. Thank you for your understanding and support. Note: Only Xiaoai can be used to control our devices, but Mihome App cannot be used for control, and our App does not support adding Mihome devices.
This back button is a function of Xiaomi App, it is not available to be modified by Tuya side. The process is jumping from 'Xiaoai Speaker' App to 'Mijia' App, so they made a return button to return to Xiaoai from Mijia. Unfortunately, it needs to be modified by Xiaomi. Even if this condition results in Xiaoai App restarting. it is also a compatibility issue of the Xiaoai App.
Dear user, we are sorry for your inconvenience. If you do so: Open the App, click the device icon to enter the device control panel (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be controlled). Click the button in the upper right corner to enter the device settings page. You can view the third-party controls supported by the device under "Third-Party Control". Click the icon of Tecent Xiaowei (If not found, the device is not supported). After jumping to the connection page, bind according to the instructions of the App (You can also click to view the tutorial). One Tecent Xiaowei account can only be bound to one App account, an error will be reported if the binding is repeated. Tencent Xiaowei is currently only available to users in China, and users in overseas regions can no longer use Tencent Xiaowei. Note: Users who login to the App through a third-party login method need to E-mail first, and then modify the login password (there is no initial password for third-party login) and use this E-mail to login to the App account when binding a third-party smart speaker. Since each third-party smart speaker is a closed platform, and therefore it is not possible to discover the device and directly connect it through the Xiaowei App nor the "Discover Device" function. It have to achieve connection by binding skills. Thank you for your understanding and support.
If a smart door lock has a screen, view the firmware version directly from the screen. If a smart door lock does not have a screen, use one of the following methods based on the lock brand and model: For a FingerCrystal smart door lock, press 0 and the pound key (#). The numeric keyboard flashes and displays the version number. (''*'' represents ''.'') For a ZmartPlus DS04/05/08 smart door lock, press *# and enter the administrator password to enter the administrator mode. Check the firmware version based on the voice prompt and record the version number. Tap the smart door lock in the device list of the App to open the device's control panel. Tap the button in the upper right corner to enter the device editing page. Tap Check for Firmware Update to view the firmware version.
Hello, under the condition of no solid walls blocking indoors, the communication distance can reach 20 meters, and the recommended stable use distance is within 15 meters; if there are thick solid walls or high-power appliances blocking, the distance may be closer, it is recommended within 5 meters.
Dear user, we are sorry for your inconvenience. If you do so: Open the App camera device-click the "..." button in the upper right corner Click the motion detection setting Click the motion detection alarm to open-check the detection Sensitivity. If motion detection is often delayed and unable to capture moving objects, it means that the network in your home is poor or the connection delay with the cloud server is high. If it still does not take effect, it is recommended that you remove the device and add it again, and perform the above steps again. Thanks for your support and understanding. The difference between high, medium and low alarm sensitivity is: High sensitive: the camera detects that there is an object is moving, as long as there is a slight shaking, it will alarm; Medium sensitive: the camera detects that a clearly visible object is moving, and it will alarm when the object has a large movement; Low sensitive: the camera detects that there is a clearly visible object moving, and it will alarm when the object moves significantly.
Hello, if you have a 4G camera, it can be used without Wi-Fi because it uses a physical data card or a virtual data card. Other non-4G cameras only support Wi-Fi communication and require a Wi-Fi connection to be used.
The video image of the smart camera may appear black and white reversed for the following reasons: Insufficient light: If the scene is not bright enough, the camera may automatically switch to black and white mode to improve the brightness and clarity of the image Infrared night vision function turned on: The infrared night vision function of the smart camera can provide better image quality in low light conditions, but it will cause the image to become black and white Photosensor blocked: If the photosensor of the camera is blocked, it will also cause the image to become black and white Camera failure: If the camera's image has a fault, where the color storage and transmission have problems, or the camera and camera aging, may also cause the color to become black and white The solutions are as follows: Insufficient light: Increase the light in the scene, or adjust the position of the camera so that it can receive more light. Infrared night vision function turned on: Turn off the infrared night vision function, or adjust the brightness of the infrared night vision lamp. Photosensor blocked: Clean the photosensor of the camera, or adjust the position of the camera so that it can receive light normally. Camera failure: Replace the camera or camera, or contact after-sales service for repair.
This issue may be due to a malfunction of the device. You can try resetting the device (unplug and plug it back in) and observe the display. If the problem persists, we recommend contacting the seller for further assistance and troubleshooting.
If Wi-Fi is disconnected, the camera's work will depend on its specific functions and settings. Here are some possible situations: Real-time monitoring function: If you use a real-time monitoring camera and rely on Wi-Fi to transmit real-time video streams, once Wi-Fi is disconnected, you will not be able to remotely view real-time video. However, some cameras have LAN functions that allow you to continue monitoring the camera in the local network environment. Local storage function: Some cameras have built-in storage or support SD cards, so even if Wi-Fi is disconnected, the camera can still continue to record video and store it on the local storage device. Cloud storage function: Cloud storage function may be affected when Wi-Fi is disconnected.
Dear user, for questions related to equipment installation, please refer to the product manual or consult the seller.If you encounter problems when using App to control your device, please contact us. Thank you for your understanding and support.
If you can't turn on the device by pressing the switch button, there may be several reasons: If the device has been left idle for an extended period of time and the battery is depleted, it needs to be charged using a charging dock or adapter; Please check if the battery cable is loose or fall off; If you operate the device frequently, please check if the switch button is damaged; If none of the above reasons, please contact the seller for after-sales service.
This problem may be caused by the following reasons; first check if the left and right wheels are stuck by foreign substance, and if the SoCkets are loose; if only one wheel does not turn. Please exchange the SoCket to check if the machine still with the same wheel does not turn. If yes, it means the wheel does not rotate is broken and needs to be replaced. If it is not, the motherboard needs to be replaced; The robot starts with leaning to one side, stop and move again or stop after hitting a wall, indicating that the motherboard is broken and needs to be replaced.
Hello, it is recommended that you restore factory settings and try adding it again. If the problem persists, please click the "Feedback Issue" button and submit your question. (Choosing the "Select Problem Device" information in the "Submit Question/Advice" interface will help your feedback get quicker and better handling) The feedback result can be viewed in "My - Frequently Asked Questions and Feedback" page under "My Feedback". Thank you for your understanding and support!
Dear user, we are sorry for your inconvenience. If you do so: Please reset the device to factory settings first. Uninstall the App, and then reinstall the App to your phone. Then add the device to the App again. If this problem still occurs, there may be a problem with the device hardware, please contact the after-sales personnel to handle after-sales for you. Thank you for your understanding and support.
Dear user, we are sorry for your inconvenience. Please check in the following ways: You completely cut off the power of the device, and the device needs a weak power to maintain the connection with network. Therefore, if the device is completely powered off , it will enter the pairing mode, which will keep blinking. In order to prevent you from completely cutting off the power of the device, please use the App to turn off the device. The device will only needs a weak power to maintain the connection with network, have no worry about energy waste. You switch the device too frequently, causing the device to enter the pairing mode. If the problem persists, it may be that the equipment hardware is malfunctioning. Please contact the buyer for after-sales service. Thanks for your understanding and support.
The Smart Guard feature enables lights to be automatically turned on and off randomly at the preset time period to simulate someone at home when you are on holiday or go out, ensuring home safety. Application scenarios Worktime guard Whole-day guard during holiday The light source 007P panel is used as an example to describe the functions. The functions may vary depending on the panel. During usage, the actual panel shall prevail. Example When the time period 6:00 P.M. to 1:00 A.M. and Saturday and Sunday are selected for the Smart Guard feature, the lights are automatically turned on and off in the period of 6:00 P.M. to 1:00 A.M. at random on Saturday and Sunday to simulate someone at home.
Hello, please troubleshoot in the following manner: First, check the gateway version and model, whether it is a Zigbee gateway or a Bluetooth gateway. The type of gateway needs to match the model of the switch (both Zigbee or Bluetooth); Please ensure that the gateway is our Tuya gateway and has the latest firmware version. Gateways from other brands may have protocol differences, which could lead to network pairing issues.
A water leak detector detects water leakage and leakage resolution. When water leakage occurs, the water leak detector triggers the gateway to send audible and visual alarms and push a message to the mobile phone. It can also control other asSoCiated smart devices through the gateway. When the leakage is resolved, the device triggers the gateway to push a message to the mobile phone.
The indicator light of this product will stay on for three seconds after power-on. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
Yes. Currently, the interaction is implemented through cloud channels. To allow smart devices to operate efficiently when being disconnected or when a problem occurs in the cloud, Tuya is planning to link multiple gateways in the same LAN.
This product triggers an alarm through an automatic interaction. The alarm keeps ringing until you disable it manually or the specified alarming period is reached.
The indicator light of this product will stay on for three seconds after power-on. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
Dear user, sorry for the inconvenience. We suggest you remove the device and add it again in a stable network. If your problem still exists, please provide your device ID and device firmware version to us, we will check for you. Open up our App Enter your device and click top right button Enter "Device Info", to get "Virtual ID" Click “Check for Firmware Update”, to get device firmware version Thank you for you support and understanding.
Dear user, please troubleshoot in the following ways: If the device statistics are always none, it should be that your device has not activated the statistics function in the cloud. You need to contact the product after-sales personnel and ask them to activate it for you. After activation, you will You can use this function normally. If the data is partly missing, it may be because of your network is unstable, the device has been disconnected due to network reasons many times during the period of use, and the data cannot be counted normally during the period of the device being disconnected. If there is still a problem, it may be that the firmware of the device is malfunctioning. Please contact the seller to let them repair the firmware of the device. Thank you for your understanding and support!
Matter is a new application layer protocol launched by the CSA alliance based on IPv6, which allows for local network connections between phones and devices via the Matter protocol. When using features with Matter characteristics, it is recommended to maintain the Matter connection between the device and the phone for a better user experience. If connection issues occur, you can troubleshoot following these steps: 1、Check if the phone is connected to Wi-Fi, and the signal strength of the Wi-Fi 2、Check if the phone and the device are connected to the same Wi-Fi 3、Check if the device is malfunctioning, keep the device in a normal online status 4、Try to keep the device as close to the phone as possible.
Dear user, we're sorry for that we don't have the contact support phone number. We're the App side. If you buy it from Amazon.com, there're must some ways for you to reflect your problem with the product itself. Hope your problem can be solved soon. Thanks for your support.
Dear user, we are sorry for your inconvenience. We recommend that you can clean the cache of the App. Then click Restore Factory Settings on the device settings page to remove the device, and then add it again. If the problem persists, please provide us with the device ID and App version number, we will Investigate for you. Thank you for your support!
Dear user, it is recommended that you troubleshoot as follows: Whether the ringtone of the mobile phone is turned on, and whether the volume of the ringtone is too low (some devices do not sound, and the ringtone channel of the mobile phone must be used). In the device settings, find the device sound adjustment option, and increase the device sound (the "device sound adjustment—volume" option in the device settings is set by the product manufacturer and cannot be changed by us). In the device settings, find the device sound adjustment option, you can change the ringtone type of the device (the "device sound adjustment-ringtone adjustment" option in the device settings is set by the product manufacturer and cannot be changed by us). The offline alarm sound and network configuration prompt sound of the device are usually set by the product manufacturer and cannot be changed in the App. Note: Currently, our App does not support changing the type of notification sound.
You can share a device or add a home member to share the device(s). Below are the steps on how to share a device and add a home member: To share a single device: 1.Tap the setting icon in the upper right corner of the device panel. 2.Select Share Device - and then click Add Sharing (You can check and manage the shared account here). 3.It can be shared via an App account, email, or another method of your choice. 4.The person accepting the shared device. Please be aware that the share a single device feature does not manage permissions. To share home devices: 1.Access the App homepage and click the Me option and then click Home Management. 2.Please select the home that needs to be shared, and then click Add Member. It can be shared via an App account, email, or another method of your choice. You can also manage home members on this page. 3.The person accepting the shared home. All devices in the shared Home will be shared, and you can set rights for the member(s) of the shared Home, and the member(s) can be set up as administrators or members to manage. Click the link to know more about What's the difference between a Home member, Administrator and Home Owner? App accounts allow you to log in to the same account on multiple mobile devices simultaneously. If you cannot share the device or add home members normally, please click to view "Unable to share devices to my family/others?" for more help.
Dear user, we are sorry for your inconvenience. No, because they use different protocols.
Dear user, we are sorry for your inconvenience. If you can only control the device when connected to your home's Wi-Fi, and you can't control it with 4G or other Wi-Fi, it means that there is a problem with the connection between the router in your home and the external network (For example, if there is a problem with DNS or UDP forwarding, please contact your network operator or router after-sales service for details). Therefore the device is failed to communicate with our cloud, so it can only operate normally in the local area network (when you connect your home Wi-Fi, you are using the local area network to control the device). Please check your router's connection to the external network and make sure it is smooth before trying again. Thank you for your understanding and support. If the device is online normally, please check if your mobile phone has enabled mobile data permissions for the corresponding Apps. iPhone: Settings—Cellular—Find Corresponding App—Enable Cellular Network Android phone: Settings—Data Traffic Management—Application Connections—Find Corresponding App—Enable Mobile Data Note: the bluetooth devices and Zigbee devices must have a suitable gateway.
If you refer to the App, please remove the device and then readd it in a stable network. If the problem is still not resolved, please provide your device ID for us to further troubleshoot the problem. If it is the physical button, we suggest that you consult the after-sale of the product, the customer service or the person in charge of the purchase channel, to troubleshoot hardware problems. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. Please check in the following ways: The device may be reset by someone. When the smart device is reset by others and connected to the network, the device under the original account will automatically disAppear. If your device is a Zigbee device or a Bluetooth Mesh device, when your gateway is reset, your sub-device will disAppear from the App. Please check whether your gateway device is working normally. After you entered the account, you selected the wrong family (devices cannot be displayed at the same time in different families). You have logged in to the wrong account. Logging in to the App through a third-party login method is actually registering a new App account, so it cannot be bound to the account you registered with your phone number/email before. In the same way, after logging in through third-party method, you cannot inherit the equipment of the account you have previously registered with your mobile phone number/email. If the problem still exists after excluding the above situations, there should be a problem with the device firmware or device hardware. Please contact the device after-sales person for help.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please check the device box or product manual, and make sure that the App recommended is our App. If it is not, compatibility problems are likely to occur, resulting in the situation that the device can only be opened and cannot be closed after the device is successfully added. If your device is a low-power device such as a sensor or devices that use batteries, it cannot be turned off. If you do not need it to continue working, please remove it from the App or completely power off the device. If it's not a low-power device. Please reset the device to factory setting and add it again. Then check whether you can turn off it by App. If you still cannot turn off it, please use the physical button and check whether you can turn off it. The smart device still needs very little power after you turn it off remotely. This is to maintain the connection to the network so that you can turn it on and operate it remotely when needed. If you need to turn off the smart device completely, you need to manually cut off the power of the device. If you cannot turn off it by the physical button, please contact the manufacturer to check the hardware. Thanks for your understanding and support.
Dear user, we are sorry for your inconvenience. For the first time, the mobile phone and device must be placed under the same Wi-Fi network environment. After the device is connected to the network with Wi-Fi, the phone can be switched to other network control. Make sure that the device must be connected to the Wi-Fi at all times so that the App can be used for normal linkage. Note: Networking devices requires a 2.4G network. Why I can only control the device when connected to my Wi-Fi, but not controlable through 4G or other Wi-Fi?
Dear user, we are sorry for your inconvenience. When a device is connected and controlled through Bluetooth, the maximum theoretical distance is 50 m in an unblocked, interference-free, and open area. When using at home, it is recommended to control the distance within 10 meters.
If the login page is a domain name purchased by the customer, it may be that the customer has not synchronized to Tuya after the certificate had been updated. The other possible reason is that the certificate has been expired or revoked. In this case, the SSL certificate needs to be updated again.
If the tuya_adapter_wifi_station_get_status function is called and returns WSS_GOT_IP, the tuya_adapter_wifi_station_connect function will not be called to establish the network connection. Please return the network status in real time.
This is because you have enabled the cloud storage function but have not paid for it.
This is because no firmware key or extended firmware is created under the PID.
It supports the power-off memory function. If a module is powered on again after a power failure, it resumes its state before the power failure.
Yes.
The distance depends on the use environment. The test data shows that the indoor distance is about 35 m.
Yes.
Blue: Indicates Zigbee status (Blinking: indicates that sub-device is allowed connecting to the network; Always on: indicates no activation; Always off: indicates activation) Red: Indicates Wi-Fi status (Blinking: indicates pending connection; Always on: indicates connected; Always off: indicates Wi-Fi information has been configured but cannot be connected) Reset method: Press and hold the key for 5s and the blue LED will blink several times to reset, that's successful.
Yes, only 32 low-power firmware devices can be accessed. If want to add more than 32 devices, you need to add high-power device as relay routes before you can add low-power devices. Each additional high-power device can add about 20 low-power devices, and so on, until the maximum number of gateways is added.
Devices developed using Tuya Zigbee modules and the standard Zigbee 3.0 protocol can connect to third-party gateways that are also developed based on the standard Zigbee 3.0 protocol at the network layer. However, vendors use private protocols at the application layer. Therefore, problems or defects may occur.
Smart switches (no neutral wire required) and low-power sensors do not support the relay function.
Check whether ports 12121 and 12122 of the gateway are occupied by other processes. Check whether the Zigbee module supports flow control and whether the corresponding configuration is correct. If the Zigbee module supports flow control, the RTS/CTS hardware pin must be connected. Check whether communication over the serial port used to connect to the Zigbee module is normal.
First, check whether the SDK is of a wired or wired + wireless version. Then, check whether the wired adaptation interface is correctly adapted. Finally, check whether the IP address returned by the gateway adaptation interface for obtaining the IP address is in the same LAN as the App. Automatic discovery depends on UDP broadcast. Check whether port isolation, broadcast suppression, or VLAN is set for the router.
The function of Both of Bluetooth gateway is to support remote control of sub-devices, support cloud schedule, scene and automation.
Since the Bluetooth Mesh devices do not have the ability to access the Internet directly, they need a device that has both Bluetooth communication capabilities and networking capabilities. This device is a gateway. The gateway is the springboard for the Bluetooth Mesh device to connect to the Internet, so as to realize the function of remote control. The Bluetooth Mesh devices use Bluetooth communication and cannot directly communicate with the server. The Commands sent from the cloud will be issued to the Bluetooth Mesh device through the Bluetooth Mesh gateway; the status of the Bluetooth Mesh device can also be reported to the server through the gateway. Different from the Zigbee gateways, the Bluetooth Mesh gateways and Bluetooth Mesh devices have no affiliation. Without a Bluetooth Mesh gateway, the Bluetooth Mesh devices can also work normally.
In AP mode, the configuration locally cached is used. After pairing, you must go to the device control panel to pull streams and perform other related operations. Then, switch to the AP mode.
The light_color_control DP is used to control the light color, saturation, and brightness. For more information, visit https://developer.tuya.com/en/docs/iot-device-dev/floodlight_pir_solution?id=Kay7sbwfcv7mh#title-6-%E7%81%AF%E5%85%89%E6%8E%A7%E5%88%B6.
Dear user, if you deactivate the third-party voice function that has been activated for this product, all users under the product pid will not be able to use the third-party voice service normally, which may cause problems such as customer complaints. If you still need to deactivate the third-party voice service after the risk is known, please submit a work order to deactivate the third-party voice function.
Currently, the SDK does not provide the API. However, you can contact Tuya personnel to customize the API.
We have a separate network button and a combination of the network button and the switch button, but the composite button requires corresponding firmware to support. The purpose of using the separate network button is to avoid the battery draining too fast after the switch button is pressed for a long time. .
After switching to wireless switch function, the relay has no output.
Please make sure the module is wired correctly with the serial tool and the baud rate is correct.
No. You can select the developer mode when you open the software.
Yes, currently the minimum brightness is set to 10%. Going below 10% may cause flickering.
The meaning of the PlugPlay network configuration capability is that when unable to connect to a router, if the device has the ability to be activated through Bluetooth, enabling the PID of this advanced feature allows the device to bypass Wi-Fi network configuration and instead be activated by connecting to a mobile phone via Bluetooth.
If you have a product under your name created by OEM, you can click to enter the product details and find the Device panel to replace it. But every time you adjust the panel, please confirm that the latest panel is available before publishing. Note: If you want to change the device panel, you must be the owner of the device's PID. If you are only the user of the device, you cannot change the device panel.
You can use the original product SDK because the SDKs are the same. However, the PIDs are different. You can modify the PID in the SDK.
The door opening and closing status DP is of raw type, which is different from the bool type. Here, 1 represents the door is open, and 2 represents the door is closed.
This situation may be caused by the following reasons: 1. Network error. If the network is not stable or the location of your device is far away from the server, for example, the device and the server are in different countries or regions, there may be a delay in the reception of messages. 2. The time required for receiving the message depends on the pressure of the third-party server. In the case of message push congestion during peak hours, there may be a delay in the reception of messages. 3. Connection error. If the mobile phone is disconnected from the server for some reason, message push may fail. In this case, you cannot receive a push message until the next heartbeat packet is sent.
Yes. The device's total online duration is calculated continually.
Yes. Under the case that the code scanner is unavailable. Find the requested PID replacement certificate on the IOT platform, export the replaced SN, and manually enter the SN number to replace it. (Manual output is risky and is not recommended).
The free version can only query logs for nearly 7 days, including online and offline, device restart, device activation, device reporting and issuing, scheduling information, etc. The subscription version can query permanent device logs, which is convenient for clients to locate the issue quickly when users report problems.
This is because the firmware version is part of the basic firmware information and can only be edited by the firmware owner. After the firmware owner publishes firmware, the platform will push a new version of firmware to you. You can perform the over-the-air (OTA) upgrade or update the firmware version of the product. If firmware belongs to Tuya, only Tuya can add a firmware version. In addition, if the PID is an original equipment manufacturer (OEM) PID and the firmware owner is the owner of the source PID, you cannot add a firmware version. In such cases, when the firmware is upgraded, an upgrade package will be pushed to you for your verification. To upload custom MCU firmware, perform the following operations: In the Hardware Commission step, click Add custom firmware and add custom firmware. In the Product Configuration step, click Settings in the Firmware Updates Center section. On the page that appears, select custom firmware from the drop-down list and click Add Firmware Versions.
Production firmware: includes bootloader, user area firmware, factory production testing functions, etc. It can be directly used for factory production and testing. After testing, it can be used as a product. User area firmware: only contains normal function firmware, does not include BootLoader and other functions Firmware upgrade: Used to replace the user area firmware.
After the platform pushes the MCU firmware upgrade, the user needs to click and successfully complete the upgrade on their mobile phone. Meanwhile, the device must also report the version number to successfully complete the verification. If the firmware upgrade prompt fails verification, you need to confirm the following: 1. Whether the firmware package is valid 2. Whether the firmware package is successfully upgraded successfully 3. Whether the correct version number is reported after the firmware upgrade is successful.
By default, due to the update of the SDK, the panel information is not returned in the request for device data. To get the device data, call the following API method before the request for device data: // In this call, the panel information will be automatically returned when a list of devices is requested.
TuyaHomeSdk.getDataInstance().setAutoLoadPanelInfo(true).
Please refer to the Tuya IoT Platform documentation for detailed guidance on this topic.
Please check if the module_app.json file is configured. module_app.json is a service configuration file. Copying module_app.json to the assets folder under the app directory will take effect.
It won't happen without significant bugs.
You first submit a Technical ticket on the IoT platform, provide the PID and AppID, and the technician will confirm it. If the panel supports it, the group function will be enabled.
When you register an account in the cloud, your password must be encrypted using the MD5 algorithm so that you can log in to the SDK with it. An MD5-encrypted password is case-insensitive and should be 32 bits in length. You can use a plaintext password to log in to the SDK.
TuyaSmartHomeKit SDK does not support infrared device control.
After SDK initialization, run the following code: [[ThingSmartSDK sharedInstance] setDebugMode:YES];.
No, you cannot check the version of the app that users are using in the backend of the app created by using the Tuya SDK.
Logic for data report from devices: It depends on the logic set for the device. Most of the devices that are developed based on the no-code solution support real-time report. However, data such as electricity consumption is reported in a periodical manner. Periodical report varies with the product category. Devices with an MCU report data based on the embedded code logic written by developers.
You can listen to kNotificationBLEUpgradeProgress messages. The double type of the object indicates the progress of the OTA upgrade.
Use #import "TYModuleManager.h" [TYModule.routeService openRoute:@"ty_multi_camera_panel" withParams:@{@"homeId":xxx}];.
The Bluetooth beacon device uses the ThingSmartBeaconKit library for networking, The related methods are all in the ThingSmartBeaconManager class. The following methods will be mainly used: 1、@interface Current class ()ThingSmartBeaconManagerDelegate 2、[ThingSmartBeaconManager sharedInstance].delegate = self; 3、[[ThingSmartBeaconManager sharedInstance] startScan]; // Start searching for Beacons devices 4、// ThingSmartBeaconManagerDelegate Acquiring devices found by scanning - (void)didDiscoveryDeviceWithDeviceInfo:(ThingBLEAdvModel *)deviceInfo {} 5、// Activate the Beacons device [[ThingSmartBeaconManager sharedInstance] activateBeacon:beaconModel homeId:homeId success:^(ThingSmartDeviceModel * _Nonnull deviceModel) { } failure:^(NSError * _Nonnull error) { }]; 6、[[ThingSmartBeaconManager sharedInstance] stopActivatingAllBeacons]; // Stop activating all Beacons devices 7、[[ThingSmartBeaconManager sharedInstance] stopScan]; // Stop scanning Beacons devices Additionally, you can refer to Bluetooth device related integration documents to help you better and faster integrate the SDK.
To obtain the device's Wi-Fi signal strength: - (void)getWifiSignalStrengthWithSuccess: (nullable TYSuccessHandler)success failure: (nullable TYFailureError)failure;.
Upon login with UID, you must change the password of the account by calling the cloud service API. For more information, visit https://developer.tuya.com/en/docs/cloud/21707ff1ba?id=Kawfjd7120rb0.
Positive active energy refers to the total amount of electricity consumed, while reverse active power refers to the total amount of electricity generated. Please note that both values need to be reported as the total quantity, rather than incremental values, in order to be correctly displayed on the public dashboard.
You need to add this method: registerDeviceListListener.
No, but can be enabled through scene configuration. As shown in the figure, click to enter the scene configuration.
Method 1: Use the Tuya Cloud Test App for testing Go to IoT Platform Product List. Select the product to be tested and click Enter Development. Click Product Testing. Complete the in-depth testing of the product on the Tuya Cloud Test App and generate a detailed report. For detailed steps on in-depth testing, please refer to Tuya Cloud Test App Overview. Method 2: Self-testing Go to IoT Platform Product List. Select the product to be tested and click Enter Development. Click Product Testing. If you do not want to use Tuya Cloud Test or do not have access to the Cloud Test App, you need to conduct self-testing. After clicking the Self-testing button, specific guidance steps will pop up. Follow the instructions to complete the self-testing. Method 3: Purchase Tuya Testing Services Purchase Tuya Testing Value-added Services; Service Type: Tuya Standard Product Testing. Service Fee: 2600 RMB/person-day, specific fees are quoted based on the required person-days for testing. Testing Content: Includes one round of full testing and two rounds of issue fix acceptance testing, totaling three rounds. If additional testing rounds are needed after three rounds, you need to reorder the "Tuya Testing" service. After payment and Tuya's receipt and confirmation of the sample information, Tuya will start implementing the service content. The service ends in the following situations: (1) The test result is "Pass", the service is completed; (2) The test result is "Fail", you can choose whether to fix the issues and proceed to the next round of retesting: ① If retesting is not needed, the service is completed; ② If retesting is needed, after you fix the issues and Tuya receives the fixed sample, Tuya will conduct the next round of retesting. ③ If the total number of testing rounds reaches three, this testing service ends. If further testing is needed, please reorder this service.
You can click the following link to purchase modules for certification: https://iot.tuya.com/purchase/store?page=1&tag=auth_module&q= 1. Ada indicates that the module is an adaptive module whose firmware is used for adaptivity and receiver-blocking test. An adaptive module is often used in CE certification. 2. Rad indicates that the module is a fixed-frequency radiation module, which contains fixed-frequency firmware without an RF cable. A fixed-frequency radiation module is used for testing radiated spurious emission and other radiation properties in a certification. 3. Con indicates that the module is a fixed-frequency transmission module, which contains fixed-frequency firmware with an RF cable. The RF cable has an SMA connector, which connects to a spectrum analyzer or other testing equipment.
Github address: https://github.com/tuya/tuya-panel-demo/tree/master/examples/ipc.
For fan lights that meet the category, the Matter protocol can be supported.
The alliance offers logos that can be used for free, as well as logos that can only be used after certification, see the website:https://www.wi-fi.org/who-we-are/our-brands.
Without approval, companies, businesses, or users are not allowed to change the frequency, increase power, or alter the original design characteristics and functions of low-power RF equipment that has obtained verification certificates. The use of low-power RF equipment shall not affect flight safety or interfere with legitimate communication; When interference is found, it should be immediately stopped and improved until there is no interference before continuing to use. The aforementioned legal communication refers to wireless communication operated in accordance with the Telecommunications Management Act. Low power RF equipment must withstand interference from legitimate communication or industrial, scientific, and medical radio radiation electrical equipment.
In principle, a minimum of 5mm is required, unless the product size is particularly small and cannot be achieved. For Wi-Fi modules, the CE mark can be proportionally reduced for small-sized components, but it must remain clear and visible. Directive 1999/5/EC of the CE, ANNEX VII, Article 2 states, “The CE marking must have a height of at least 5 mm except where this is not possible on account of the nature of the apparatus.”https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:31999L0005; In the RED Directive 2014/53/EU, it is explicitly allowed for the mark to be less than 5mm: Article 19, Point 2 “On account of the nature of radio equipment, the height of the CE marking affixed to radio equipment may be lower than 5 mm, provided that it remains visible and legible.” From:https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0053.
FCC nameplate requirements: Product model, FCC ID number, Warning: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. FCC manual warning requirements: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: —Reorient or relocate the receiving antenna. —Increase the separation between the equipment and receiver. —Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. —Consult the dealer or an experienced radio/TV technician for help. Caution: The user is cautioned that changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. Warning for general non-close-use wireless products: RF Exposure: A distance of 20cm shall be maint.
CE Caution: This equipment has been tested and found to comply with the limits for a EN 300 440 v2.2.1 receiver Category 3. These limits are designed to provide reasonable protection against harmful interference in a residential installation. When placed in the vicinity of other device(s) radiating in the 5735 MHz-5840 MHz band, this device will inadvertently trigger on, or will fail to switch off, its movement sensor ability being impaired. Please take appropriate measure to mitigate this eventuality.
To determine the module and chip model used by the product based on the PID; clarify the certification and the required quantity, common certification quantities are as follows: 1) CE: 1 fixed frequency conduction + 1 fixed frequency radiation + 1 adaptive conduction; 2) FCC: 1 fixed frequency conduction + 1 fixed frequency radiation; 3) ISED (IC): 1 fixed frequency conduction + 1 fixed frequency radiation; 4) SRRC: 5 fixed frequency conduction + 1 adaptive conduction (test interference avoidance); 5) NCC: 1 fixed frequency conduction + 1 fixed frequency radiation; 6) TELEC: 2 fixed frequency conduction; 7) KC: 1 fixed frequency conduction; 8) ANATEL: 1 fixed frequency conduction; It is recommended to confirm the certification items and sample quantity with the certification body before placing an order for procurement. To ensure a one-time pass of certification and save time in handling anomalies, it is recommended to purchase an extra certification sample as a backup. Sample preparation can be done in the following ways: 1. Certified modules and chips on the platform, purchase entry: https://platform.tuya.com/purchase/store?page=1&tag=&q=&type=commodityName 2. For those not listed on the platform, you can apply to Tuya Business (submit "Fixed Frequency Module Certification Sample Production"); or burn it yourself according to the burning guide, guide download entry: https://developer.tuya.com/en/docs/iot/module-test-tool?id=K9qswhqd5ymnp Testing tools: 1. Most modules are tested with a serial port board, purchase entry (open the first link): https://platform.tuya.com/purchase/store?page=1&tag=&q=&type=commodityName 2. BT and ZT series modules, Telink chips are tested with a burner, Taobao purchase entry (for reference only): https://platform.tuya.com/purchase/store?page=1&tag=&q=&type=commodityName.
Under normal circumstances, the following certifications will be obtained: CE, FCC, SRRC, RoHS, REACH. For other regional certifications, such as ANATEL, KC, IC (ISED), TELEC, etc., certification will be arranged according to the actual order situation.
Normal prototype refers to a prototype that can be connected to the APP and can normally achieve basic functions. If only the module is certified, regardless of the firmware, it can be connected to the APP. The firmware for lights/switches is the easiest to set up, so the firmware for lights is generally chosen. The MCU general network configuration firmware also requires a computer to install a debugging assistant for use, which has high testing communication costs and is generally not recommended. Unless a specific firmware version is required for network security testing projects.
Burn the certified firmware samples, always test according to the product specifications. For example, if the module power is 17dBm, then with the software settings, the test result should also be around 17dBm to ensure consistency between the samples and the bulk products.
The specifications of the module will indicate the version of Bluetooth. Generally, Bluetooth used only for network configuration is of the BLE type, while Bluetooth that supports voice audio functions supports classic Bluetooth BR/EDR.
U.S. Cyber Trust Mark is a voluntary certification by the U.S. FCC in September 2024. There are no detailed rules yet, so certification is not possible, and it is expected that it will not be actively pursued. The EU's RED cybersecurity will be mandatory in August 2025, with the official standard also being released in September 2024. Self-developed public version modules and finished products will be done in batches in H1 2025. Customers' finished products can quickly obtain reports based on the module's report by supplementing the difference test at the original testing agency. Currently, TUYA recommends TUV SUD and DEKRA as certification bodies.
The firmware is incorrect, the log shows an unknown plugin command, so the flashed firmware should be the Railtest firmware. Solution: Change to test with Railtest commands, Please refer to the attachment below for details 📎 Railtest Test Instructions.zip.
For the whole machine CE certification, regardless of the method of certification for modules and adapter boards, the whole machine can reference conduction and other data, but it needs to supplement the radiation spurious data. The whole machine cannot use the module's certificate and must be re-certified.
To implement audio and video services, a streaming media SDK needs to create an audio and video buffer. The buffer size is related to the bitrate and buffering duration (in seconds). Buffer size = Bitrate x 1024/8 x Buffering duration.
When "can't find free mqmde" appears in the device logs, DP reporting is blocked. In normal cases, a large number of MQTT messages are reported during device startup. A device can report eight MQTT messages simultaneously. It is recommended that the device sleeps for about 500 ms after reporting eight DPs to prevent message blocking.
Tuya's streaming media SDK has a mechanism of overwriting after the storage of an SD card is full. The SDK monitors the SD card capacity in real time. When the capacity is less than 512 MB, the SDK checks files and preferentially deletes old files.
For the xr806_lowpower_common_ty module, upgrading from version 1.1.4 to 1.1.9 requires configuring a differential update. Otherwise, the module firmware upgrade will fail.
Connect via 485 to serial port.
Enter domain keywords, search, and then select an available domain name.
If your universal remote control cannot connect to Wi-Fi, please try the following steps: 1. Check the stability of the Wi-Fi network to ensure the network connection is normal; 2. Confirm whether the universal remote control is within the coverage range of the Wi-Fi network; 3. Confirm whether the entered Wi-Fi password is correct; 4. Reset the universal remote control and try connecting to Wi-Fi again; 5. If the problem persists, check the router settings to ensure that access control or device quota restrictions are not enabled.
It may be that the power supply is unstable, and there is a periodic voltage drop, which causes the power statistics chip to restart; It may be that there is interference between the signal line between the metering chip and the module.
Please confirm whether the socket is successfully calibrated. The "Wi-Fi light is on" at the end of the calibration indicates that the calibration is successful.
Tuya Zigbee scheme is divided into strong current scheme and weak current scheme. For example, the zero-fire line scheme in the development free scheme of lighting and electrician belongs to strong current scheme, and the default is to quit the distribution network in 3 minutes, while the single fire scheme belongs to weak current scheme and quit the distribution network in 30 seconds.
Voice configuration issue. When switching the voice configuration of the garage door product, it should be associated with the identifier door_control_1 dp point, not switch_1.
Yes, recognize the scenario number in the protocol.
To use a module in a sphere lamp, ensure that the module's antenna is out of the opening groove of the alumina substrate and that the onboard antenna is higher than the alumina substrate. When the light source is not affected and there are no shadows, position the antenna out of the lamp cup's shielding environment as much as possible.
The brightness of white light is controlled by the brightness DP point, the data type of this DP point is numerical, and the numerical range is 10-1000.
Because the current App has not purchased the official version, it will disappear after the purchase of the official version, please click Buy now.
It is recommended that you check whether the current SDK version is ≥5.8.0. If the version is less than 5.8.0, it is recommended that you upgrade to version 5.8.0 and above to ensure normal use. Please note that version 5.8.0 has been adapted to Android 14 system.
Hello, after upgrading to the latest 5.5.0-3 business package, this type of conflict occurred, which can be resolved by adding the following in the build Duplicate class com.thingclips.smart.family.api.AbsFamilyBusinessService found in modules jetified-thingsmart-family-api-5.2.0-rc.4-runtime configurations.all { exclude group:"com.thingclips.smart", module:"thingsmart-family-api" }.
Check whether the supported communication mode is Bluetooth only. Currently, the OTA update is not supported for Bluetooth devices. Call a specific method for the update. For more information, visit https://developer.tuya.com/en/docs/app-development/android-bluetooth-ble?id=Karv7r2ju4c21#title-19-%E6%A3%80%E6%9F%A5%E5%9B%BA%E4%BB%B6%E4%BF%A1%E6%81%AF.
For SDK 3.34.x and above, you need to introduce the Hilt framework and place it under the application main module. For more information about the integration, search on the Internet or refer to the demo at https://github.com/tuya/tuya-ui-bizbundle-android-demo.
It is due to the location permission. If the location permission is turned on, the arrow will be displayed, otherwise, it will not be displayed.
Yes. Set ConditionExtraInfoBean in SceneCondition = TempUnit = "celsius" or "fahrenheit".
This return code indicates that the current region is not supported. You can call the verification code API to check whether the current region is supported. iOS: https://developer.tuya.com/en/docs/app-development/iOS-user-phonelogin?id=Kaixrrhmyknwt#title-0-%E7%94%A8%E6%88%B7%E8%8E%B7%E5%8F%96%E7%99%BD%E5%90%8D%E5%8D%95%E5%88%97%E8%A1%A8 Android: https://developer.tuya.com/en/docs/app-development/usermobile?id=Ka69pu4myrrws#title-0-%E6%9F%A5%E8%AF%A2%E9%AA%8C%E8%AF%81%E7%A0%81%E6%9C%8D%E5%8A%A1%E5%8F%AF%E7%94%A8%E5%9C%B0%E5%8C%BA.
Confirm whether the package name being used is consistent. Since SDK4.0, it is necessary to ensure that the package name is consistent.
The first time the device is successfully bound to the App through pairing is activation, and the accumulated activation number of the device is the total number of activations of the device corresponding to the PID under the current account.
The number of devices reported through the DP under the account on the day of the statistics, a device can report multiple times.
Infrared remote control has no plans to support calling related interfaces in App SDK due to code library issues.
When you create a product, a product knowledge base without any knowledge and in the disabled state is automatically generated on the Product Knowledge page. After the product is deleted, the corresponding product knowledge base is also deleted. If you click Delete in the Operation column of a knowledge base in the knowledge base list, only knowledge in the knowledge base is deleted. The knowledge base is not deleted but is returned to the disabled state.
Yes, it is possible. The Tuya voice skill UI business package provides a one-click fast-binding service for custom voice skills of Amazon Alexa and Google Assistant. If you do not use this business package, you need to Bind your account (phone number or email) through Alexa, such as on the Alexa App's "More" page -- select "Skills & Games" -- search "Smart Life" -- click "ENABLE TO USE" ; The page will pop up "Link your smart life account with the Amazon account"; Here you need to select "Use other account", click and choose the corresponding country and enter the account in the new page, then Next Step; On the "Choose App" page, select the App to which the account belongs, enter the account password, verify the login, authorize, return to Alexa, bind. This process is complicated and we recommend integrating the Voice Skill UI Business Package for a one-click fast binding service for custom voice skills of Amazon Alexa and Google Assistant.
You can set activatorCompletion to NO to automatically navigate to the device panel page after configuration. Note: Ensure that the channel identifier in thing_custom_config.json is consistent with the SDK channel identifier in the Tuya developer platform.
None.
getDpsInfos can obtain the current cloud record's Dp point status, queryDps can trigger a query report, and the device can report the latest status of the device once.
You can submit a work order to let our background change the status to the developing status for you, but products that have been shipped cannot be changed. Shipped refers to the sale of actual products. If the product has been sold, your operation will affect the cloud function of the product already sold, please consider carefully.
Yes. During the networking stage, the mobile phone system's Bluetooth search and App can all search for Bluetooth signals. But only the corresponding App can pair with the Bluetooth device and load the operating interface for control.
Bluetooth LE devices do not support local timing. Therefore, a gateway is required. A Bluetooth LE device automatically connects to the gateway or mobile phone depending on which Bluetooth channel has strong signals. It is recommended that disable the Bluetooth function of the mobile phone while adding the Bluetooth LE device to the gateway. In this way, scheduled tasks can run properly.
Some special pins of the XR3 module cannot be set as the Wi-Fi reset button. For more information, see the module datasheet https://developer.tuya.com/en/docs/iot/xr3-datasheet?id=K98s9168qi49g.
The account systems of different OEM apps are independent and unavailable in the Tuya backend. After completing the configuration of the app and putting it on the app store, the developer can register an account through the email and mobile phone number.
This is because at present, Tuya supports three image sizes, which cannot adapt to all iPhone models. As a result, the splash screen image may be stretched or not fully displayed when the system trims the image. To resolve this problem, we recommend that you design a simple splash screen image.
At present, there is no Italian in the reference document that is temporarily not available, and you need to translate it yourself. However, files in Italian are supported for uploading.
No, you only need to activate the cloud storage service for the NVR.
Check whether the following requirements are met: The values of AppKey and AppSecret configured in your project are the same as those displayed on theTuya IoT Development Platform. The security image is deleted from the project. The project has the security component configured. For more information, seeUpgrade Guide for iOSandUpgrade Guide for Android.
It is not supported, Matter is networked through scanning the code, there is no AP networking mode.
Cost Composition: 1. Module cost; 2. Basic license fee; 3. Advanced capability fee.
Advanced features: One-thousandth dimming, dimming curve, switch gradient, dimming and color tuning gradient, multi-segment dimming linkage.
The charges include: 1. Module costs; 2. Basic license costs; 3. Distributed capability costs.
Local linkage does not require a gateway, cloud linkage requires a gateway.
The application entry function of our SDK is OPERATE_RET device_init(VOID).
You need to build a VM, a compiler and have to be familiar with the secondary development documents.
Check whether the product has been delivered. If yes, the Cloud Storage for Videos service cannot be disabled because it will affect the use of end users.
Routines are shortcuts in Alexa for saving you time by grouping together a bunch of actions across devices. You can create a Routine by using one of the following methods: 1. In the Alexa app, click a device and tap Create a Routine. Enter the name of the Routine and specify the rule and associated devices. 2. In the Alexa app, go to More Routines. A common Routine example: To enable your room light to automatically turn on when the contact sensor detects that the door is open, you can configure a Routine rule for the contact sensor and set the action of the Routine to turning on the light.
Alexa skills are divided into regions, and only the Amazon account of the corresponding region can be searched. For example, if the OEM skills are only available in the UK area, the Amazon account in the US cannot find the skill, and it needs to be replaced with an Amazon account in the UK area.
Customizable features include capability language, capability name, capability type (switch, level, and mode), voice commands for the switch, mode, and level, alias name for the level, and voice capability description.
It can be obtained by the protocol command command word as 2D.
The reason is that the sub-device has been networked, and the networking time has exceeded 15 minutes which locking the production test.
Tuya Cloud timing function, including setting switch time and weekly cycle, does not require hardware embedded development, and is actually implemented as a module of Tuya. After the App is set up, the timing data will be updated to the Tuya module, and it can still be executed after the device is disconnected from the network. Tuya Cloud's timer function allows you to set the on/off time and intervals and does not require hardware development. It is actually executed by Tuya’s module. After the App is set, the timing data will be updated to the Tuya module, and it can still be executed after the device is disconnected.
For example, with the button active on low level, when the button is pressed, the circuit is connected, and the module IO port is at low level. After releasing the button, the circuit is disconnected, and the module IO port is at high level. Reference for button part of the circuit.
Dear user, we are sorry for your inconvenience. When the indicator of a device flashes slowly, it is in AP mode. Auto Scan only works with devices in EZ mode. In addition, some devices can be found only after you configure the Wi-Fi account and password and then connect them to a 2.4 GHz network.
Dear user, we are sorry for your inconvenience. Please follow the steps as below: First, make sure that the device is powered off for more than 10 seconds before powering on the device. Then long press the restart button on the device for about 5 seconds, until the indicator light of the device starts blinking rAPIDly. The device enters the network configuration state. Follow the prompts in the App to select the 2.4GHz wireless network (most products do not support 5GHz wireless networks, nor mobile hotspot networks and passwordless networks) Click "Continue" , the mobile phone displays a QR code. Use the camera to scan to the QR code 15cm to 20cm away from the mobile phone. After the scan is successful, you will hear a beep sound from the camera, click "I hear a Prompt", and the camera will enter the network distribution process. If the camera still fails to connect successfully through the above steps, please refer to "What should I do when my device fails to connect to the network?" Or "（For most of Routers）How to configure separate Wi-Fi SSIDs for 2.4 GHz and 5 GHz bands?"Split your network into 2 frequency bands.
Dear user, we are sorry for your inconvenience. If you have a lot of devices, you can add all the devices in your account at one time through the “Auto Scan” method, The following is the specific operation : On the homepage, click "+" in the upper right corner, and then you will enter the "Auto Scan" page. If you need to add Wi-Fi and Bluetooth devices at the same time, it is recommended that you enable Wi-Fi and Bluetooth, and then click "Start Search". At this time, you can click "Add" and then click "Finish" .You will see these devices on the homepage. You can use the "Auto Scan" mode to configure multiple types of devices simultaneously: For Wi-Fi devices, only Wi-Fi devices that support lightning network configuration and have HomeKit functions can be discovered in Auto Scan mode. For Zigbee devices, you can configure network connections for three or four devices simultaneously after configuring the Zigbee gateway. If you configure more than four devices simultaneously, the network will become slow and network configuration may fail. For Bluetooth devices, Bluetooth mesh devices now support to be added multiple devices at the same time, and other Bluetooth devices (single-point Bluetooth devices and Wi-Fi&Bluetooth dual-mode devices) need to be added one by one. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. The flashing indicator shows the user that the device is ready to be connected to the Internet. It is not a prerequisite for network connection.
On the app homepage, click on the plus sign in the top right corner to add a device. Plug in the device and connect it to the home router. Ensure that the phone and device are in the same network environment. Follow the product manual's instructions to put the device in pairing mode. Usually, press and hold the reset button on the device for about 5 seconds. Refer to the product manual for specific instructions. The app will automatically search for devices in pairing mode nearby and display the corresponding devices to be added. Click on add. If the device is not detected automatically, you can manually select the device category, confirm that the device is in pairing mode on the device addition page, then click next and wait for the connection to be established.
Dear user, we are sorry for your inconvenience. You can follow the steps below (this is a general method, please refer to the product manual for specific methods): Devices with a reset button: Firstly, make sure the device is powered off for more than 10 seconds before powering on the device. Then long press the reset button on the device for about 5 seconds (for switch devices, the reset button is mostly the switch Button itself, you can try long press). Wait a few moments until the indicator light starts blinking rAPIDly. The device enters the pairing mode. You can add it now. Lighting equipment: Firstly, make sure the device is powered off for more than 10 seconds before powering on the device. Then turn on and off three times (on-off-on-off-on) power of the device (2 to 4 seconds between each on and off). Wait a few moments until the lighting starts blinking rAPIDly. The device enters the pairing mode.You can add it now. Note: Zigbee devices do not support individual sharing, only sharing by adding family members.
Dear user, we are sorry for your inconvenience. There are two types of our Bluetooth gateway: One is the Bluetooth mesh gateway. The Bluetooth mesh gateway must add Bluetooth mesh device (also a Bluetooth mesh device, please consult the seller for the details of the agreement) under the Bluetooth mesh gateway control pannel. Then you can remotely controll Bluetooth mesh device through the Bluetooth mesh gateway. The other one is a Bluetooth gateway that uses our proprietary protocol. This protocol gateway does not need to add a Bluetooth device (the same Bluetooth device as our proprietary protocol, please consult the seller for details of the agreement) under the Bluetooth gateway device control pannel. You can add it in the same way as the Bluetooth device. If you purchase a Bluetooth mesh gateway with Bluetooth mesh protocol, you can see the option of adding sub-devices in the device control pannel of the gateway. If you buy a Bluetooth gateway with our proprietary protocol, you enter the device of the gateway there is no option to add sub-devices in the control pannel.
Dear user, we are sorry for your inconvenience. To troubleshoot, follow these steps: Check whether your device is powered on, the device may have been powered off due to poor contact, etc. Check whether your device is powered off or disconnected from the network. If so, it will take some time to go online again. Wait for two minutes and then check whether your device is online (Not all devices support power-off memory, so the device will go offline after power-off). Ensure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Use the Internet Speed Test App to test the upload and download speed of your network (upload ≥ 2 MB/s, download ≥ 2 MB/s, upload ≥ 16 Mbps, download ≥ 16 Mbps,); Check whether the home Wi-Fi network is normal or whether you have changed the Wi-Fi name or password. In the latter case, reset your device and add it again. If the network is normal but your device is still offline, check whether too many devices are connected to the Wi-Fi network. If this is the case, restart the router, power off the device, and power it on again. Then wait for two to three minutes and check whether the device is connected. Check whether the firmware is the latest version. To check this on the App, choose Home—Tap device icon—Top right button—Check for Firmware Updates. You can also use a phone hotspot to check whether it is the problem of network. If the issue persists, we recommend that you remove your device and then add it again. If the issue persists, select your device in the user feedback area on the App, submit your issue, and provide us with your login account and device ID. We will arrange for technical support engineers to troubleshoot this issue.
At present, serial ports of Tuya SDKs do not support flow control configuration.
In the Zigbee protocol, a profile refers to an application scenario. Several profiles are defined in the Zigbee protocol, such as the Zigbee Home Automation (ZHA) profile for home automation and the Zigbee Light Link (ZLL) profile for lighting.
When multiple products of the same type are configured network, the name on the App will have a number based on the product quantity. For example, there are 5 SoCkets of the same type in total, then the names of four of them will have numbers of SoCket 2, SoCket 3, SoCket 4 and SoCket 5.
Dear user, we are sorry for your inconvenience. If your device is a Bluetooth device, you must open the App location permission. If your device is a Wi-Fi or Zigbee device, you do not need to open the App location permission, but if you do not open the App location permission, you need to manually enter the Wi-Fi SSID during the adding process.
1、On the D-Link home page, click the Settings tab and select Wireless. 2、In the 2.4GHz area, set Wi-Fi Name (SSID) to <xxx&rt;-2.4G; and in the 5GHz area, set Wi-Fi Name (SSID) to <xxx&rt;-5G, where xxx indicates the Wi-Fi name. 3、The last step is to Save the settings。 When the preceding settings are complete, the new Wi-Fi names will Appear on the Wi-Fi settings page of your mobile phone. Note: After the Wi-Fi names are changed, you need to reconnect the devices that use this wireless router. The password remains the same if it has not been changed.
The number of power cycles refers to the process of entering the network configuration mode after multiple power on/off cycles, with the default set at 3 times, and options ranging from 3 to 10 times; The default power cycle reset time is 3 seconds, and it can be configured within a range of 3 to 10 seconds. If you currently have the reset time set to 5 seconds, and the setting to enter network configuration mode is after 3 power cycles, then on the second power on, if the power is maintained for 5 seconds, the power cycle count will be reset.
Dry: Humidity ≤40%. Suitable: 40% < Humidity ≤ 70% Moist: 70% < Humidity ≤100%.
Third-party Matter devices must be placed under a Matter gateway in order to create scenes.
Dear user, we are sorry for your inconvenience. Please check in the following ways: If you are using an Apple ID to log in to the App, you can only log in on the iOS. It is not possible to log in on the Android. You need to bind a mobile phone number/E-mail so that you can use your phone number/E -mail to log in; A server failure, a network issue, or incorrect email settings may be causing the problem. We recommend that you try again at a different time or in a different network environment, or use another mobile phone or mobile device and log in again.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please click on the upper right corner of the device to enter the interface, and check if you can see the "Create Group" function. If you can see it, click on it and create a group. If you do not see "Create Group" on device setting page, it means that the device does not support group settings (Not all types of equipment support group functions). If you want to manage different types of devices or devices that don't support groups, you can add these devices to one "Tap-To-Run/Automation" to meet your needs. Thank you for your supporting and understanding. How do I create a device group? The Third-party smart speaker can't control the group in voice? Some features missing after the device grouped or control group does not perform how it is?
Dear user, we are sorry for your inconvenience. Available areas are specified for the cloud storage service. If the area setting for the service is different from that of your account, the platform notifies you that the service is unavailable in your area. In this case, you can contact the device supplier.
Hello, if you encounter this situation, you can go to the App market to upgrade the App and try again; If your App is the latest version, you can re-configure the device to check whether it is feasible; If your problem persists, please report to us.
Dear user, you can set in your mobile phone system to set the App to only use "Wi-Fi". The specific setting method depends on your mobile phone brand and system version. It is recommended that you ask the customer service staff of your mobile phone.
Dear user, we are sorry for your inconvenience. Please check in the following ways: There is no device that supports Google Assistant under the App account. You can try to add a device that supports Google Assistant in the App, and the skill will Appear in the bound list. Google's bug. Since frequent binding and unbinding process within a short period of time will trigger this bug, you can visit https://myaccount.Google.com/u/1/accountlinking to unbind. If this problem still occurs, Please provide feedback in the App feedback path.
Dear user, we are sorry for your inconvenience. This is because after the device automatically comes back online, it can automatically connect to our cloud server. However, third-party smart speakers have their own independent cloud servers, and our devices cannot be automatically connected. We suggest you to remove the devices from the App (device removal method: enter the App and enter the device control page, click the icon on the top right corner, then click "remove device" on the bottom of your screen ) and add them again with a stronger and more stable network ( for example, the personal hotspot on your phone ). When devices go offline frequently, they're unable to be controllable in Alexa/Google Assistant/IFTTT. If the offline issue persists, please provide the virtual IDs of your devices ( 1.enter the App 2.tap the icon of your device and click the icon on the top right corner of the screen 3. enter "device info", check "virtual ID") so that we can better troubleshoot. We are looking forward to your reply and we'll be glad to help. Thank you for your support and understanding！.
Dear user, we are sorry for your inconvenience. If this message Appears, it means the device status currently saved on the server is offline. It is recommended that you switch your phone's network to 4G and enter the device's App (non-Alexa App) to view the device's status. If you find the device is actually offline, you can try the following troubleshooting method: Please confirm whether the device is energized; Please confirm whether the device or the network has been cut off . If so, there is a process to go online. Please check whether it is online after 2 minutes. Please confirm the network is stable.（Check methods: put the phone or Ipad besides your device and make sure they’re in the same network environment, try to open a website to judge if the network can be used.) Confirm whether the home Wi-Fi network is normal, or whether the Wi-Fi name and password have been modified. If so, remove the device and add it again. PS:5G Wi-Fi is temporarily not supported, only 2.4G Wi-Fi can be used. If the network is normal, but the device is still offline, check if there are too many Wi-Fi connections. .Please try to restart the router, wait 3 minutes and observe the status of the device; Check if the firmware is the latest version, the App side checks the path: Me - Settings - Device Update; If all is normal after check, we recommend that you remove the device and add it again.(Device Removal Method: Open the App and enter the device control page, click "..." button which is in the top right corner, click on the bottom of the page "remove device") Note: If your device is a Bluetooth device and is not connected to the Bluetooth gateway, the device may not be able to be controlled by Alexa normally. Please connect the device to the Bluetooth gateway and re-bind the skills. If there is still a problem,Please provide feedback in the App feedback path.
Dear user, we are sorry for your inconvenience. Since the device will be offline when the device is upgrading the firmware, if your network is unstable, after the firmware upgrade is completed, the third-party speaker will fail to synchronize with the device, so it cannot be controlled. Please check in the following ways: Remove the device and add it again with stable and strongly network. Unbinding with our App, then re-bind our skill and try again. Please confirm that you enter your account password for logging in to App. If the problem still exists, please provide your account ID, your device ID and device firmware version to us，we will help you to solve it. Open up our App Enter your device and click top right button Enter "Device Info", to get "Virtual ID" Click “Check for Firmware Update”, to get device firmware version Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. A Bluetooth mesh gateway is required to connect a Bluetooth mesh device to a third-party smart speaker because the Bluetooth mesh device uses the Bluetooth communications mode and cannot directly communicate with the server. The Bluetooth mesh gateway sends commands from the cloud to the Bluetooth mesh device and reports the Bluetooth mesh device status to the server.
There is no limit on this.
Dear user, we are sorry for your inconvenience. You can turn on the private mode/standby mode of the camera in device settings, so that the camera will turn off all functions. If you want to power off the camera completely, you can only achieve the purpose of completely turning off by cutting off its power. This "private mode/standby mode" is set by the product's producer . If you want this option, you can feedback this problem to the after-sale person so that they can improve it later. Thank you for your support and understanding.
Dear user, we are sorry for your inconvenience. The reason for the camera's own movement may be that you have turned on the "movement tracking" function, the camera has captured a certain area of the image has changed, so move to shoot in the past. "Motion tracking" function can not only track moving objects, the light and shadow changes in the area will also be captured, so even if nothing or people move in that area, the camera will capture and move past to shoot. The difference between high, medium and low alarm sensitivity is: High sensitive: the camera detects that there is an object is moving, as long as there is a slight shaking, it will alarm; Medium sensitive: the camera detects that a clearly visible object is moving, and it will alarm when the object has a large movement; Low sensitive: the camera detects that there is a clearly visible object moving, and it will alarm when the object moves significantly. Note: If the sensitivity of your device has been set to the lowest, it will still send too many alarms and take photos, indicating that there are too many moving objects in the area where you placed the device. You can block it for a specific period of time by shieldingDevice message.
It is recommended that you troubleshoot as follows: Whether to enable the mobile phone to allow the App to use the phone's microphone; Whether to turn on the voice intercom function of the App video interface; Remove the device from the App and re-bind the camera; Check if there is sound when recording video on the SD card of the camera. If there is no sound, it may be a malfunction of the camera's microphone or speaker. If all of the above are normal and you still can't talk, you can click "Continue Feedback" to submit your question.
Hello, yes, the intelligent camera can still function normally without inserting a Micro SD card. You can still view real-time monitoring footage and use cloud storage, motion detection, and push notification features. However, the playback of locally recorded videos and the ability to transfer them will not be available. Note: To install the SD card, please locate the SD card slot on the device. If your device is a PTZ camera, the SD card slot may be located below the lens and you may need to push it up manually to access it.
To be GS certified, the device must comply with safety requirements by using a dual relay or a magnetic latching relay.
If the backend locks the JSON, the frontend still cannot make changes when reverting to 'In Development' status, and can only view it.
Push-pull output can directly output high or low level according to the signal, while open-drain output must be connected with external pull-up resistor to use.
The Wi-Fi indicator and the power indicator are multiplexed, indicating the state of the network when the network is configured, and the priority of the relay is indicated when the network is disconnected/low power consumption/connected to the Internet. The specific multiplexing scheme can be configured on the Tuya IoT platform.
Non-Tuya serial ports do not have an RST pin and require manual reset operations: first disconnect the module's GND, click run and then reconnect the GND to the module. If manual reset is difficult, or the operation is inconvenient, please purchase Tuya serial port 5V: USB Interface Power GND: Power Supply Ground 3.3V: 3.3V Power Output TXD: Transmitting End RXD: Receiving End IO0: Output RST: Output DSR: Input CTS: Input.
These two refer to the SPI connection mode of the chip and FLASH, QIO is the 4-wire connection mode, DOUT is the 2-wire connection mode, the two software also need to correspond to each other, otherwise it can not be burned normally, TYWE2S can only use DOUT way.
SIM Card Check: Contact the SIM card provider to verify the status of the SIM card, ruling out abnormalities such as overdue fees or lack of data usage. SIM Card Reinsertion: After powering off, reinsert the SIM card and reconnect the device to check if the device is offline due to poor contact or incorrect insertion of the SIM card.
Dear user, we are sorry for your inconvenience. Please check according to the following conditions: Please make sure that the signal of the network environment where the device is located is strong and stable. Troubleshooting: Download the Internet Speed Test App, place your mobile phone in the same location as the device, and then test the Internet upload and download speed at that location (ensure that the speed is at least: upload ≥ 2 MB/s, download ≥ 2 MB/s or upload ≥ 16 Mbps, download ≥ 16 Mbps), smart camera equipment occupies a large amount of upload bandwidth, and at least 4M of upload bandwidth is required for 1080p image quality (0.5MB/s, 4Mbps), if your device has enabled the cloud storage function, additional 2M upload bandwidth is required, please confirm that your network has sufficient network bandwidth. The region where you live now is not the same as the region you selected when you registered your App account. As a result, the cloud server you access when controlling your device is far away from your place of residence, resulting in high latency. Our cloud server is not able to cover the area where you live, causing high latency between the cloud server you need to access and your device.
Dear user, we are sorry for your inconvenience. In theory, up to 128 sub-devices can run stably under the Bluetooth gateway at present, but due to the mutual interference between Bluetooth devices and the limitation of the connection distance (within 5 meters), the theoretical value of 128 may not be reached. In theory, up to 128 sub-devices can be stably operated under the wired Zigbee gateway, and up to 50 sub-devices can be stably operated under the wireless Zigbee gateway.
You can try restarting the device to see if it resolves the issue. There could be several reasons why this problem is occurring: First, check if there are any foreign objects stuck in the left/right wheels or if the socket is loose. If only one wheel is not turning, swap the left/right wheel socket and start the machine to see if the same wheel is still not turning. If it is, then the wheel needs to be replaced. If not, then the motherboard needs to be replaced. If the robot starts to move diagonally, stops and starts, or pauses after hitting a wall, then the motherboard is likely damaged and needs to be replaced.
If you want the same App on multiple phones to control the device, and the light bulb is Wi-Fi class, there are two methods: 1. You can click on the device icon to enter the device control panel, click on the button in the upper right corner to enter the device settings page, click on the share device option, and you can achieve multiple phones controlling the same device through sharing the device. 2. The App settings can be logged in on multiple devices, and you can log in to the same account on different phones.
Dear User, sorry for the inconvenience. This "Color/brightness/color temperature" is set by the product's producer and cannot be switched in the App. If you want this option, you can feedback this problem to the after-sale person so that they can improve it later. Thank you for your support and understanding.
If you are using an SD card for storage, currently only selective deletion of videos and photos stored in the SD card is supported via a computer (video files are encrypted and cannot be viewed on a computer, but this will not affect your deletion of video files). Deleting via the app is not yet supported, but the latest recording will automatically overwrite the oldest recording on the SD card, so there will be no problem with recording. If you are using cloud storage services, you can delete the replays and photos you want to delete through the app by selecting them (not all products support deleting all replays, depending on the manufacturer's settings). Note: Once deleted, it is impossible to retrieve any replays or photos, whether from the SD card or cloud storage.
The camera may have different reasons for flickering, blurring, and noise, so the solutions are not the same. Here are some common reasons and solutions: Insufficient light: If the scene is not bright enough, the camera will automatically switch to black and white mode to improve the brightness and clarity of the image. Increasing the light in the scene, or adjusting the position of the camera so that it can receive more light, can alleviate this problem. Lens contamination: If the lens of the camera is contaminated, it will also cause the image to become blurry. Cleaning the lens of the camera, or replacing the lens, can solve this problem. Camera failure: If the camera's image has a fault, where the color storage and transmission have problems, or the camera and camera aging, may also cause the image to become blurry or noisy. Replace the camera or camera, or contact after-sales service for repair.
Dear user, we are sorry for your inconvenience. The indicator light of this product will stay on for three seconds after power-on. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
The indicator light of this product will stay on for three seconds after power-on. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
Dear user, usually the reset button of the switch device is the switch itself. You can make the device enter the standby state by long pressing the switch itself. After entering, the power light will enter the flashing state.
Dear user, we are sorry for your inconvenience, we suggest you troubleshoot in the following ways:Please make sure that the battery you replaced is correct (whether the battery voltage and current match your device). Please make sure that the battery you replace is sufficient. If device still showing low battery after replacing the battery, you can try to reset the device and try again later. If the problem still exists, consider the problem of the equipment itself, please contact the seller for after-sales treatment.
Dear user, we are sorry for your inconvenience.To display specified devices and scenariOS in the App installed on your iPhone on the paired Apple Watch and adjust their display order, perform the following steps: Open the App on your iPhone. Tap Me—Watch—Device or Available Scene. Select devices or scenariOS to display on the Apple Watch and adjust their display order. Tap Save. A notification is sent to your Apple Watch to synchronize the data.
Dear user, we are sorry for your inconvenience. A possible cause for this issue is that your mobile phone restricts App from running at the backend. We recommend that you grant App permission to run the App at the backend in Settings.
Dear user, we are sorry for your inconvenience. Please check whether the Bluetooth controller is offline.
Dear user, we are sorry for your inconvenience. Delayed for at most 1s.There is no Spinner page.
There are three methods: 1. You can click on the device icon to enter the device control panel, click the button in the top right corner to enter the device settings page, click on the share device option, and then you can control the same device with multiple phones through device sharing. The operation is as follows: 2. App settings allow for multi-end login, logging into the same account on different phones. Normally, accounts are by default supported for multi-end (different phones) login, (if not supported, it may be specially processed, please submit a ticket for confirmation) 3. You can add family members, and add the family/friends who need to control the devices to the family, so they can control and operate the devices in that family. The operation is as follows: How to share a device? Get more help If you still cannot share the device normally or add family members, please click to view "Unable to share the device with others, or add them to the family?" Get more help.
Dear user. Yes. Go to the Home page and tap the microphone icon in the upper right corner toenter the voice assistant page. You can also control the device by binding a third-party smart speaker/voice assistant. Note: The voice command of the control device is set by the manufacturer of the product and cannot be changed by us. If you want to modify the voice command of the control device, you can report this problem to the after-sales party of the product so that they can improve it later. Thank you for your support and understanding.
Hello, Zigbee gateway needs firmware development, and Zigbee module does not require firmware development and can be used directly.
Once the App receives a progress update, the timeout period will be re-timed, which is also controlled by the gateway side. If network is interrupted during the period of downloading the firmware, the SDK will keep reconnecting. If the network is disconnected for over 60s, the App will determine to time out and the OTA fails.
Fixed 10 minutes.
For a small number of sub-devices created based on Tuya solution, you can visit Tuya Go and purchase gateways that match the protocol type. For a large number of sub-devices, you can ask your business manager to purchase required gateways for you.
Electrical Smart Socket Socket_Sigmesh Two-way power strip_Sigmesh Three-way power strip_Sigmesh Four-way power strip_Sigmesh Five-way power strip_Sigmesh Wall socket_Sigmesh Smart Switch Switches that require no neutral wire need the gateway to support multi-packet sending. One-gang switch pro_Sigmesh Two-gang switch pro_Sigmesh Three-gang switch pro_Sigmesh Four-gang switch pro_Sigmesh One-gang switch_no neutral wire required_Sigmesh Two-gang switch_no neutral wire required_Sigmesh Three-gang switch_no neutral wire required_Sigmesh Four-gang switch_no neutral wire required_Sigmesh Card switch_Sigmesh Scene Controller Four-gang wireless switch_Sigmesh Knob wireless switch [with three groups]_Sigmesh One-gang wireless switch_Sigmesh Two-gang wireless switch_Sigmesh Three-gang wireless switch_Sigmesh Four-gang wireless switch_Sigmesh One-gang scene switch_Sigmesh Two-gang scene switch_Sigmesh Three-gang scene switch_Sigmesh Four-gang scene switch_Sigmesh Five-gang scene switch_Sigmesh Six-gang scene switch_Sigmesh Smart Switch Module One-gang concealed switch module_Sigmesh Two-gang concealed switch module_Sigmesh Three-gang concealed switch module_Sigmesh Four-gang concealed switch module_Sigmesh Digital & Power PD adapter 2-port PD power_BLE 3-port PD power_BLE 4-port PD power_BLE Valve Pump Water valve_BLE Lighting General Lighting Filament lamp/PAR light/LED tube/Candle lamp/G9/GU10/Indoor lights smart solution/Ceiling light/Panel light/Downlight/Spotlight/Magnetic fastening light/Batten light/Cabinet light/Chandelier/Selfie light/Pendant light/Linear luminaire/Mirror light/Makeup light/ Dimmable light (C)_Sigmesh White light (CW)_Sigmesh Multicolor light (RGB)_Sigmesh Multicolor light (RGBC)_Sigmesh Multicolor light (RGBCW)_Sigmesh Atmosphere Lighting Strip lights/Floor lamp Strip lights (CW)_Sigmesh Strip lights (RGB)_Sigmesh Strip lights (RGBC)_Sigmesh Strip lights (RGBCW)_Sigmesh The low-power settings for PIR lights, disinfection lamps, or outdoor lights nee.
When the control is stable and there is no obstruction, the maximum distance indoors is 30m, and the maximum distance outdoors is 200m.
The Bluetooth mesh gateway (CR3L module) supports Beacon mesh devices. However, the firmware version of the gateway must be V1.9.9 or above.
"undefined reference to"FAQ_lovemysea Column-CSDN Blog Target files are missing during link connection. Library files are missing during link connection. Another library file is used in the linked library file. The linking sequence of library files is incorrect. The library that depends on other libraries must be placed in front of the depended library. The definition of a referenced interface is inconsistent with the actual implementation of the interface. In the C++ code, a library using C language is linked. (Solution: Add statement of extern "C" in related files.).
Screenshot of problem: Problem cause 1: The devices associated with the account do not support the voice platform. Solution: Check whether the corresponding device supports it by querying its device ID for PID on the IoT platform, and confirm whether it supports the corresponding voice platform according to the PID. Problem cause 2: The user has confused the account to which the device belongs. The user may have multiple accounts, and the device is bound to account A, but entered account B during binding", which will result in the device not being visible. Solution: Suggest that users confirm whether the account binding skill is correct in the app where they can see the device. Click "Me", click the top right corner settings, click "Account and Security", and confirm it here.
To enable the feature where the speaker shows the camera video on its screen when a user says "show me camera", two services need to be purchased: 1. Product PID voice control activation: This grants the speaker the ability to parse and respond to user commands. This service is compatible with multiple platforms including Alexa, Google Home, and Yandex Alice. 2. Device UUID video streaming activation: This enables the cloud server to successfully access the device's live video feed. If the product has already been enabled with Alexa or Google Assistant, it is necessary to check whether the "IPC Video Streaming Push Service" has been activated for the device. Activation link: https://www.tuya.com/vas/tmpl/apply?code=IPC_MEDIA_PUSH Note: If the service is already activated on the device, it cannot be purchased again.
This is because the UUID is not contained in the database.
This error may occur due to authorization failure. The UUID is inconsistent with that specified in a Tuya database. Make sure that the UUID is correct.
If TUYASA is contained in the P2P ID, and a low-power SDK is used, update the UUID to a low-power UUID because SA indicates that the UUID is a non-low-power UUID. For more details, contact Tuya personnel.
If you apply to replace the PID which is using OEM firmware, the system will approve it in 3s after submitting. If you want to replace the PID which is using customized firmware but generated from OEM PID, the system will also approve it automatically in 3s after submitting it. For other cases, using MCU common integrated firmware, for example, the review will be finished in 2 working days.
Sorry, this library has been deprecated. We recommend that you perform native development.
In the SceneBean field of Android SDK, there are two fields, newLocalScene and boundForPanel, which can be used to distinguish whether the scene is a local one-click execution. The newLocalScene is created through the smart page tab, while the boundForPanel is created through the panel. Depending on the source of creation, the fields to be judged are different.
Use TuyaHomeSdk.getUserInstance().sendBindVerifyCode(phoneCode, phone, new IResultCallback() { @Override public void onSuccess() { } @Override public void onError(String s, String s1) { } to send the verification code. On the binding page, select the country code, enter the phone number, and send the verification code. The phoneCode is the selected country code, and the phone is the phone number. After getting the verification code, enter the code and go through the binding process. The countryCode is the country code selected in the previous step; the username is the phone number entered in the previous step, and the vertificationCode is the entered verification code.
If the request to the family-related interface exceeds 150 times within 10 seconds, you will be added to our block list. Please do not call the interface frequently, we do not support stress testing. If it is not available, you can check if there is a problem in the code, such as being trapped in a dead loop, etc.
Hello, if your device has dp points related to device power, you can get data through dps in DeviceBean. Please refer to the documentation on Device Management for more information.
Currently, the iOS SDK obtains the local language based on [[NSBundle mainBundle] preferredLocalizations], so the project created the English language. To change the language, change the preferred localization value.
Make sure thatPush Notificationis enabled in Xcode. Log in to the Thing IoT Development Platform and upload the push certificate. Call thedidFinishLaunchingWithOptionsAPI method to initialize thePushmethod. Log in to theThing IoT Development Platformand go to the Marketing push page. For more information, see Integrate with Push Notifications.
Log: Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'data parameter is nil' Scenario: This problem occurs when opening the device details page through the device control package or directly calling the device detail package Reason: When integrating the 4.0.0+ SDK, the "deviceDetailConfig.json" file is not configured in the project Solution: Refer to Configuration file , put the "deviceDetailConfig.json" file into your main project.
Use the "- (void)setTempUnit:(NSInteger)tempUnit" method in TuyaSmartUser to change the temperature scale. Value 1 indicates Celsius (°C), and value 2 indicates Fahrenheit (°F). Other temperature scales, such as the Rankine (°R) scale, Réaumur scale, and Newton scale, are not supported. We recommend that you save the used temperature scale to userdefault.
No.
First, confirm whether the module is a restrictive module or an integrity module. This can be verified by the model approval code CMIIT ID on the module's SRRC certificate. If it includes (M), it is a restrictive module. Module certificate download location: In the product development interface (https://platform.tuya.com/pmg/list), click on the product name, and the product overview page will pop up to download the module certification materials. If it is an integrity module, the terminal product must also be listed in the "Information Technology Equipment and Household Appliance Equipment" product catalog that embeds "Radio Transmission Modules for Non-Independent Operation." Link (https://ythxxfb.miit.gov.cn/ythzxfwpt/hlwmh/tzgg/xzxk/wxdhwxtx/art/2020/art_2dedb238ea0e44e78207420098eba959.html) The catalog is as follows: One, Information Technology Equipment Catalog Serial Number Equipment Name 1 Computer (such as desktop computers, portable computers, tablets, self-service platforms, etc.) 2 Display devices used with computers (such as computer monitors, projectors, etc.) 3 Printer 4 Plotter 5 Scanner 6 Copier Two, Household Appliance Equipment Catalog Serial Number Equipment Name 1 Refrigeration appliances (such as refrigerators, beverage coolers, etc.) 2 Cleaning appliances (such as washing machines, dryers, electric irons, vacuum cleaners, water purifiers, automatic sweepers, automatic locks, etc.) 3 Kitchen appliances (such as electric stoves, induction cookers, electric ovens, rice cookers, dishwashers, disinfection cabinets, water heaters, food processors, smart cups, etc.) 4 Electric heating appliances (such as electric blankets, heaters, etc.) 5 Personal care appliances (such as massagers, electronic scales, foot massagers, etc.) 6 Audio-visual appliances (such as televisions, sound systems, microphones, digital cameras, digital camcorders, etc.) 7 Air conditioners (such as air conditioners, air purifiers, fans, etc.) 8 Lighting appliances (such as lamps,.
Without a shield, it is a restricted transmitter. The whole machine FCC certification cannot directly reference the module certificate report, and all tests must be conducted.
The module has done BQB, and the finished product also needs to do BQB. After quoting the module BQB certificate's QDID/DN, the finished product only needs to be listed. If there is an addition of profile functions, generally, supplementary testing of the added profile part is required (very rarely added). The customer's BQB cannot be done under Tuya's BQB account, as BQB is linked to the brand. Therefore, the listing process requires the customer to purchase a DID, and then list the terminal product model in the customer's BQB application account.
The integrity module has obtained the KC certificate for the RF part. The RF part of the finished product can reference the KC certification number of the module certificate, but the safety and EMC parts still need to be retested to obtain their respective KC certification numbers. The final shipped product needs to be marked with the module's KC certification number, the finished product's safety KC certification number, and the KC EMC certification number to complete the overall KC certification. The Korea Energy Efficiency Certification is considered separately based on the product category.
The transmitter sends commands, and the last two commands are "settxdelay 0" and "tx 0". "settxdelay 0" indicates the maximum duty cycle, and "tx 0" indicates continuous packet transmission. It is recommended that the test laboratory use a spectrum analyzer set to the time domain to detect if packets are being continuously transmitted.
Yes, but it is recommended to report the device status. Otherwise, the device's real-time status will not be synchronized after it comes back online.
'closed' indicates that the device cannot interact with the server and automatically goes offline. 'keepalive_timeout' indicates that the device is turned off by the server after the server has not received a heartbeat from the device in a specific period.
255 is the initial value assigned by the SDK, not the network status issued by the module. The steps to handle this issue are: 1. Check whether the module and MCU are interacting normally. 2. When the module and MCU successfully interact, a new network status value will be issued through the 0x03 command, changing the 255 status.
No, RST is the module software reset pin; long press the socket switch button to configure the network.
For device security reasons, the production testing channel will be closed after the device has been connected to the network for a cumulative total of more than 15 minutes. If you need to reopen it, you can provide the device ID in the work order to reopen the production testing and burning authorization function for a single device. Note: This operation only supports Wi-Fi and Wi-Fi+BLE devices, and other protocol devices are not supported.
Typically, the driver chip cannot identify the PWM pulse width when the brightness is reduced to a specific ratio. To solve the problem, reduce the PWM frequency.
Yes.
Yes.
Local Bluetooth Mesh group controls sub-devices.
Troubleshoot the fault as follows: 1. Check whether the power supply is normal. 2. Check the network connection. If the switch is a sub-device of the gateway, check whether the power supply and network connection of the gateway are normal. 3. If the power supply and gateway are normal, re-pair the switch and upgrade the switch version. If it is a sub-device of the gateway, ensure that the latest gateway version is used.
Log in to Tuya IoT Platform, and choose Purchase Information on the left-side navigation pane to go to the page of editing production materials. The system will initialize the production material based on the module and firmware of the product. The information about the product, module, and firmware can be modified only on the Product Development page. The name, delivery method, and basic settings of the production material can be modified as needed. For more information, visit https://developer.tuya.com/en/docs/iot/production-manage?id=Karo7ugwfx3q5.
The output of the module is a PWM signal, which can be converted to an analog signal by an external circuit to adjust the 0-10V drive.
YouTube：https://youtu.be/xT2ghKOe88I lWhen people get into sleep, the human brain will generate a large amount of melatonin to inhibit the excitability of sympathetic nerves, reducing blood pressure, slowing the heart rate to rest the heart. A smart lighting system can adjust the light to affect the secretion of melatonin in the body to improve sleeping quality. lEnd users are able to choose whether to turn on the repetition of this function, the repetition time is from Monday to Sunday. lThefade-out setting: the minimum time interval is 5mins, and the maximum is 2h. the brightness of the light will decrease and the color temperature will gradually change to warm in the fade-out duration. lEnd users can add up to 4 light to sleep tasks which will be sorted by time lExample:set a light to sleep task at 11:00 PM from Monday to Friday, the fade-out time is 30 minutes. At 11:00 PM every weekday, the light will be adjusted to a status with low brightness and low color temperature, gradually dimming until the lights are completely turned off at 11:30 PM.
YouTube：https://youtu.be/90eFxphbbQo lAt the time of sunrise, the light will gradually become brighter to simulate the real sunlight, awakening users intimately. Tuya smart light will accompany you to embrace every new day. lEnd users are able to choose whether to turn on the repetition of this function, the repetition time is from Monday to Sunday. lThe fade-in setting: the minimum time interval is 5mins, and the maximum one is 2h. the brightness of the light will increase during the fade-in. lLast time setting, after the fade-in duration ends, the light will keep turn-on status all the time by default. The last time function can be turned on to set the lasting time of light-on status, which will turn the light off automatically after the last time period finishes. lEnd users can add up to 4 light to sleep tasks which will be sorted by time. lExample: set a light to wake task at 7:00 AM from Monday to Friday, the fade-in time is 30 minutes. At 06:30 AM every weekday, the light will gradually get brighter until the lights are completely turned on at 7:00 AM.
The Do-Not-Disturb upon outage restoration feature prevents lights from being automatically turned on when the power is restored after an outage. If this feature is enabled, users will not be disturbed after the power is recovered from a power failure in the middle of the night. If users enable this feature and the power is cut off and then restored, users must switch between the off and on states twice within 5 seconds before they can turn on the light. Example: Enable the Do-Not-Disturb upon outage restoration feature and use the App to turn off the light. If the power is cut off and then restored, the light is in the off mode. To turn on the light, switch between the on and off states twice within 5 seconds.
If the power-off memory DP is selected and the power-off memory function is enabled in the JSON configuration, then the function will be executed as expected, and it can be disabled through the panel settings. If the power-off memory DP is selected, but the power-off memory function is disabled in the JSON configuration, then the function will not be executed. If the power-off memory DP is not selected, but the power-off memory function is enabled in the JSON configuration, then the function will be executed normally and cannot be disabled through the panel settings.
In the console, choose Product Development and go to the developing page of the remote control. Then, choose Device Interaction Advanced, and enable "Display sub-devices in tile mode".
Check whether the one-way talk mode is enabled (A microphone icon is displayed). The one-way talk mode allows voice collection either from the app or the device at the same time. In this mode, when you touch and hold the talk icon in the app, you cannot hear the sound from the device. If you enable the two-way talk mode, you can hear the sound from the device when you talk through the app.
Yes, IP cameras (IPCs) can display the total capacity, occupied capacity, and available capacity of memory cards.
Yes. Users can click Restart Device in the app. The device will reboot after receiving the DP instruction.
Yes. The destination of the jump follows the "videos stored on the cloud playback real-time video" priority. To implement this function, contact your Tuya project manager to display the corresponding button for jumping to the corresponding videos.
If you use QR code-based pairing, a maximum of 20 characters are allowed for the Wi-Fi name and password respectively in the app. If the name or the password exceeds the length limit, you will be prompted but can still go to the next step. If you use the IPC SDK, a maximum of 32 characters are allowed for the Wi-Fi name, and a maximum of 64 characters are allowed for the password. If the name or the password exceeds the limit, the pairing will fail.
You can customize a DP. When the customized function is enabled and the recording duration is set to 30s, if no recording event is triggered in consecutive 10s during the recording duration, the device can end the recording event in advance. If an event is triggered in 10s, the event is recorded until the set recording duration reaches. For more information, visit https://developer.tuya.com/en/docs/iot-device-dev/IPC_custome_function?id=Kb0lbwks8ta2u#title-26-%E7%A7%BB%E5%8A%A8%E4%BE%A6%E6%B5%8B%E5%BD%95%E5%83%8F%E6%8F%90%E5%89%8D%E7%BB%93%E6%9D%9F.
Yes. You can set the duration for motion detection recording through a custom DP (ipc_recording_time). For more information, visit https://developer.tuya.com/en/docs/im-project-services/ipc_customize_solutions?id=Kb3k9q8daole7#title-23-%E7%A7%BB%E5%8A%A8%E4%BE%A6%E6%B5%8B%E5%BD%95%E5%83%8F%E6%97%B6%E9%95%BF%E8%AE%BE%E7%BD%AE.
Yes. You can draw polygon areas with four or more edges after setting a custom DP (ipc_polygon_switch). For more information, visit https://developer.tuya.com/en/docs/im-project-services/ipc_customize_solutions?id=Kb3k9q8daole7#title-26-%E5%A4%9A%E8%BE%B9%E5%BD%A2%E5%A4%9A%E7%A7%BB%E5%8A%A8%E4%BE%A6%E6%B5%8B%E5%8C%BA%E5%9F%9F%E8%AE%BE%E7%BD%AE.
For more information, visit https://developer.tuya.com/en/docs/im-project-services/ipc_ota?id=Kb5rgntp3nbcw.
The parameters of the overcurrent fault dp point are mainly reported to the App panel for push messages after overcurrent protection occurs,notify the user that the device is abnormal.
Yes. On the Hardware Commission page, select a module and click Configure Firmware. In the dialog box that is displayed, set Pairing reminder color and click OK.
The role of this pin is to reduce standby power consumption. During standby, through an IO port output high and low level to shut down a line (similar to SM726 chip), so that this part of the line stop working to achieve low-power.
In the lighting solution, except for the ZSU package, other 3L, 2S, LC5, etc. are interchangeable. In the other solution, the Zigbee protocol scheme is not necessarily compatible with the Wi-Fi protocol scheme.
A Wi-Fi module is typically installed in the bulb base and not covered by the lampshade. In this case, there is no signal blocking risk. In some cases, a Wi-Fi module may be installed in the metal part of the lamp tail, where signals may be affected.
Some Wi-Fi products allow only one TCP connection at a time. If a device has established a TCP connection with the App, the control panel cannot establish a TCP connection with the device. You can close the app control page and then use the control panel to control the device.
Before a Linux control panel SDK is released, it is submitted to professional test personnel for functional tests to ensure the SDK stability. When a bug is found, the bug will be fixed in a timely manner, and a new version will be released. Currently, the SDK is stable.
The total number of faults reported by the corresponding equipment yesterday under the current account.
Today only counts the number of dp function points that can be read and written.
When your OEM App enters the build queue, the interface configuration and function configuration of the App will be in an uneditable state. Only when your OEM App is not built, successfully built, or failed to build, you can edit it again.
Dear user, please log in to IoT Workbench-App Workbench-select your App-Required Setting. 1. Click Add version to add a new Privacy Policy and User Agreement. After editing, click Enable to activated: 2. If you don't know how to write a Privacy Policy and User Agreement, you can click on the reference template above to download the template:.
On the Privacy Policy and User Agreement tabs under OEM App Required Setting, you must specify the privacy policy and user agreement of the English edition before you can specify them in other languages because the default language of an OEM app is English. If you do not have customers outside China, you can enter Chinese content for the English edition and save it. Then, you can specify the user agreement and privacy policy in other languages.
Features An adaptable interface is available on iPads and Android tablets to improve the visual experience. A real-time preview of videos from smart cameras is supported on larger devices, bringing a full-screen viewing experience. More devices can be displayed simultaneously on a larger screen for more efficient device control. FAQ Q1: Which version of the smart life OEM app template supports Adapt to Tablet? A1: Adapt to Tablet is available for the smart life OEM apps of template version 3.32.5 or later. Q2: How do I activate the Adapt to Tablet service for my OEM app? A2: 1. Activate the Adapt to Tablet service on the Tuya VAS website. 2. Log in to Tuya IoT Platform and go to App OEM App App Creation. Click Configure in the Operation column of your app. In the Customize UI step, enable Adapt to Tablet. 3. On the Splash Screen for iOS tab, configure the splash screen images for your OEM app for iPads. On the Splash Screen for Android tab, configure the splash screen images for your OEM app for Android tablets. On the More Custom Settings tab, upload the background image and app logo for the login and sign-up pages. 4. Configure and build your OEM app. Download and install the latest app installation package on a tablet device and perform acceptance testing. 5. After the app passes the acceptance testing, launch it on app stores. Q3: What are the differences between the Upload One Image and Merge Images options on the Splash Screen for Android tab? A3: Upload One Image: You can upload only one image that contains the app logo as the splash screen image. The splash screen image will be displayed in the screen aspect ratio that best fits Android devices. However, sometimes the splash screen image may not be displayed in its entirety. Merge Images: You need to upload a background image and an app logo image. Your app will adapt to the PM ratio of devices to cover the entire device screen with the background image and display the app logo in a proper position. This o.
No, you only need to activate the cloud storage service for the sub-devices.
A valid value for a region contains a maximum of 8 Chinese characters, 10 English characters, and no invalid characters. Otherwise, an alert message displays. The data parsing for the corresponding map is correct.
You can enter App-App SDK-SDK Development, create an App, and then directly download the required iOS Podfile/Android SDK package: If you have problems during the development process, you can check the document: https://developer.tuya.com/en/docs/iot/app-development/sdk-development/app-sdk-creation-instruction?id=K989rt8rm8lc6.
Please finish the upgrade to v5.0 or later prior to January 1, 2024. Follow the instructions inUpgrade Guide for iOSandUpgrade Guide for Androidto upgrade the SDK.
You can pair a Matter device by scanning the QR code of the device or entering the Setup Code. Each Matter device has a unique Setup Code, which is the most evident characteristic that distinguishes Matter devices from non-smart or traditional smart products.
Matter is promoted by Amazon, Google, Apple, and CSA.
No, it can be disconnected from the network.
Yes, module SDK development is also part of the customized solution. If you need to carry out secondary development of the module, you need to create a customized solution on the platform. Related documentation: https://developer.tuya.com/en/docs/iot/device-development/access-mode-link/module-sdk-development-guide/module-sdk-development-guide?id=K9tjznxb6vf2x.
You need to compile in root mode, please provide logs to Tuya for analysis if it still fails to compile.
Yes. However, you need to develop the tool for writing the license list to the flash memory yourself.
Yes.
It means restoring the factory setting.
This is likely because the UUID is not recorded. You can contact Tuya personnel to record the UUID.
There is no need to delete the database, which has been processed inside the SDK.
Hello, after creating a product on the IoT platform, the modules generally embedded in the Tuya solution can call Tuya Cloud to achieve intelligent control of the device through the App. If you don’t use Tuya modules directly, you need the developer’s own but strong hardware development capabilities to embed the Tuya SDK for secondary development of the modules. If your company’s current secondary development capabilities are not relevant, it is recommended to create a product to embed Tuya. For some modules, follow-up product development.
The CBU module is a board-mounted PCB antenna, while the CBU-IPEX module uses an external antenna through an IPEX connector. Refer to the attached figure for the difference in appearance.
Currently, consumers outside China can pay through PayPal and Stripe. On the PayPal payment page, they can choose to not log in to PayPal but pay through a bank card. PayPal is available in more than 200 countries/regions and support 25 currencies (you can check via the link). On the Stripe payment page, they can pay directly by credit card. Stripe now supports 135 currencies in more than 35 countries (you can check via the link).
Homekit is a software framework by Apple that lets users configure, communicate with, and control smart-home appliances using Apple devices. By designing rooms, items, and actions in the HomeKit service, users can enable automatic actions in the house through a simple voice command to Siri or through the Home app.
Wi-Fi, network cable connection, single-node Bluetooth, and connection through a gateway (bridge), including Zigbee, 433 MHz RF, and Bluetooth mesh gateways.
HomeKit ADK, short for HomeKit Accessory Development Kit (ADK), abstracts the details of the HomeKit Accessory Protocol so that chipset vendors may focus on their hardware platforms and the manufacturers on the accessory application layer. Chipset vendors develop the HomeKit SDK by adapting ADK's Platform Adaptation Layer (PAL), and accessory manufacturers use the HomeKit SDK to create HomeKit accessories to implement the functions of home automation-enabled accessories.
It is supported, as long as they are Google Assistant voice assistants and devices that can bind Google Action.
There is no limit to the number of PIDs for which a third-party smart speaker is enabled.
Possible reasons: 1. Your product does not support the third-party voice platform. For example, products such as strip lights and switch modules are not supported by Xiaomi Xiao AI. 2. Data points of your product are all customized. In this case, you need to contact your Tuya project manager to customize a third-party voice platform integration solution.
To enable your PID to support voice control of third-party speakers such as Xiaoai, you need to apply for the corresponding voice service for PID. If the product function and category meet the conditions, the background will pass the review within 1-2 working days after submitting the application. You can view the third-party access service guide https://docs.tuya.com/en/iot/service-market/smart-speaker/third-access/thirdaccess?id=K9j6yqoadn2ad.
Hardware Category Voice Control Solution Single Product Control or Multi-Module Control Device Type Sent to Third-Party Voice Assistants Function Voice Command Supported Language Remarks Curtain Solution 1 Single product control Curtain Pause Pause the curtain motor Mandarin Curtain Solution 1 Single product control Curtain Curtain status control Open the curtains Pull open the curtains Close the curtains Draw the curtains close Mandarin Drying rack Solution 1 Single product control Drying rack Position adjustment Raise the drying rack Lower the drying rack Pause the drying rack motor Mandarin Drying Rack Solution 1 Single product control Drying rack Drying mode on/off control Enable the drying mode Disable the drying mode Mandarin Drying Rack Solution 1 Single product control Drying rack Disinfection mode on/off control Enable the disinfection mode Disable the UV disinfection mode Mandarin Pet feeder Solution 1 Single product control Pet feeder On/Off control Turn on the pet feeder Turn off the pet feeder Mandarin Pet feeder Solution 1 Single product control Pet feeder Manual feeding Dispense one serving of pet food Mandarin.
The Bluetooth device is calibrated through the App, and the App directly obtains the system time of the mobile phone and sends it.
iming is divided into cloud timing and local timing. Cloud timing means that after the app sets the timing, it executes the timing task directly in the cloud and delivers it to the device at the point in time. Advantages: There is no limit to the number of timings. Disadvantages: If the device is disconnected from the network during timing execution, it will not be executed. Local timing means that after the app sets the timing, it is directly delivered to the Tuya module, and the module executes the timing task, and at the time point, the module directly sends it to the device. Advantages: The equipment can also be executed when the network is disconnected when it is executed. Disadvantages: the number is limited to 30. Currently, the product is set to local timing by default (timing settings path: IoT Platform-Product-Product Development-Function Definition). If you need to configure cloud timing, please provide feedback to the business manager for further handling.
The astronomical timing panel is enabled by default. If your device supports astronomical timing, it will be displayed in the panel. If it does not support it, it will not be shown in the panel.
Up to 30 fault values.
Yes, the fault DP is displayed in bytes, which can support multiple faults to be displayed simultaneously.
When the network is allocated, the network has priority, and the network is disconnected/low power consumption/connected to the Internet. Priority indicates the status of the relay.
Convert high level to low level.
Tuya Smart Networking Module's RTS/EN pins have an internal RC reset circuit, so the RST/EN can be left floating during hardware design.
Set the oscilloscope to AC coupling, bandwidth 20MHz, and test with the smallest loop method of the probe.
When needed, you will have to design the circuit board during the hardware development stage.
During the development and debugging process, some unexpected faults may occur, such as burning failure or new modules unable to work. If you try to detect randomly, it might take you quite a long time to determine which components caused the fault. Here is a simple method to help us quickly verify the location of the fault in the system. A-B-A swapping is a simple and straightforward cross-checking test that can confirm that the observed issues are not systemic. A-B-A Swap (1) Remove the suspicious components (A) from the original faulty board. (2) Replace the suspicious component (A) with a well-functioning component (B), and check whether the original board is now functioning properly. (3) Install the suspicious component (A) on a well-functioning board and see if the good board has the same fault. Step 3 is very important because it can help us rule out the possibility that the fault is caused by any systemic problems or interaction of multiple minor defective components on the good board.
If you are a TuyaOS development solution, upload the new firmware here in Firmware Management, and then follow the instructions in the documentation to operate. If you are using a no-code development solution, you need to modify it in hardware development, regenerate the firmware, and then purchase a production certificate to burn into the module to take effect, or reorder the module. (To ensure the security and reliability of customer products, the content of hardware development cannot be upgraded via OTA) 1. If your module has not been soldered and used, it is recommended to contact your account manager to arrange for rework; 2. If the number of firmwares that need to be re-burned is small and you have the conditions for burning, you can purchase the authorization code to burn it yourself;.
Click the plus sign in the top right corner of the App's homepage, then select "Add Device" to enable this feature. Ensure the device is powered on, and reset it to pairing mode following the instructions in the product manual. Typically, devices that are not yet paired will automatically enter this state upon initial power-up. If automatic discovery is unsuccessful, you can manually add the device. Here are some common methods for putting devices into pairing mode for reference. Please refer to the product manual for precise instructions: Bluetooth Devices: Ensure the device is powered off for over 10 seconds, then power it back on. Press and hold the reset button on the device for about 5 seconds until the device indicator light starts flashing, indicating the device is in pairing mode. Zigbee Devices: Ensure there is an available Zigbee gateway device in the home and it is online. Power off and then power on the device for over 10 seconds. Press and hold the reset button on the device for about 5 seconds until the device indicator light starts flashing, indicating the device is in pairing mode. Wired Devices: Ensure the phone and device are on the same network. Power off the device for over 10 seconds, then power it back on. Press and hold the reset button on the device for 5 seconds until the indicator light stays on, indicating the device is in pairing mode. Lighting Devices: Toggle the device power switch three to five times (on-off-on-off-on) until the light starts flashing, indicating the device is in pairing mode. Ensure there is a 2-4 second interval between each switch.
Dear user, we are sorry for your inconvenience. Possible causes of this issue include: You returned to the App before your mobile phone connected to the smart device's hotspot. A non-2.4 GHz Wi-Fi was selected during network pairing. The Wi-Fi password is incorrect. If the problem persists after the preceding issues are resolved, contact our customer service personnel.
Dear user, we are sorry for your inconvenience. Zigbee devices must have a gateway to control. The Zigbee protocol and Wi-Fi protocol are different. Currently, mobile phones do not support the Zigbee protocol. To manage your Zigbee devices with your mobile phone, you need a Zigbee gateway to convert the Zigbee protocol into a Wi-Fi protocol. Furthermore, a Zigbee gateway centrally manages Zigbee devices and ensures that these devices are working properly and securely. In addition, a gateway can connect to these Zigbee devices even when the network is disconnected.
Dear user, we are sorry for your inconvenience. Read the product manual or the instructions on the network connection page and strictly follow the steps. If your device still fails to enter the network connection state, check whether your device is powered on and turned on and whether the indicator is steady on. If the issue persists, you may need gUIDance on troubleshooting hardware products. Contact your product’s after-sales service personnel. Thank you for your understanding and support.
Step1:Put device into Pairing Mode【Please refer to the product manual for details】 Switch on and off a lighting device 3 times. For other devices, long press the reset button for 5 seconds. The indicator flashes to indicate networking start. Step2:Tap"+"button on App to add device On the "Add device" page, select the category of the device and select the Wi-Fi type. Step3:Connect device to home network Select a 2.4 GHz Wi-Fi at home and enter the Wi-Fi password to connect the device to the network. Wait for 2 minutes, and the device will be added. If the device pairing fails You can retry as follows： 1. Reset the device and reconfigure the network. See the first step for the reset operation. 2. Move the device close to the Wi-Fi router to connect the network 3. Confirm whether the device distribution network frequency band is consistent with the current distribution network frequency band，If inconsistent, please adjust. 4. How to switch the Wi-Fi to 2.4G?
Operation Confirmation:Confirm if the device has been removed or frequently turned on/off, or if the device's switch button has been accidentally triggered. When the indicator light keeps flashing, it usually indicates that the device is in pairing mode. Reconfiguration:Attempt to reconfigure the device network. If the indicator light continues to flash even after successful reconfiguration, it may be due to a hardware malfunction. It is recommended to contact the seller immediately for after-sales support.
Dear user, we are sorry for your inconvenience. Firstly, you need to make sure that you are connected to a 2.4GHz network. If you are not sure what your network is, you can follow"How to configure separate Wi-Fi SSIDs for 2.4 GHz and 5 GHz bands?". It is recommended that you use the AP mode (the AP mode will automatically select the 2.4GHz network for connection), and then add it again. If you can connect to the device but have problems, you can provide us with the device ID. Thank you for your understanding and support!
Dear user, we are sorry for your inconvenience. We can't delete any schedule from the system. You can restore the device as factory defaults, and clean the cache in the App and then readd it. If you still have the problem, feel free to let us know. Thanks for your support.
Dear user, we are sorry for your inconvenience. Use either of the following methods: Choose Me—Settings—App Notification. Choose Me—Message Center, and tap the gear icon in the upper right corner. On the Notifications Settings page that Appears, tap Do-Not-Disturb Schedule. If you are setting the schedule for the first time, you must first add a device for which you want to enable this feature.
Dear user, we are sorry for your inconvenience. The Do Not Disturb function takes effect only after you enable it, set a time range, and select a device. It could be that the messages were received outside of the time range, or on an unselected device.
Dear user, we are sorry for your inconvenience. This is the function of the product itself. After entering the product control panel, you can click the icon in the upper right corner to view the product settings page. If there is an "Offline Notification" option and you turn it on, the App will push notifications when the device is offline. If the function is not available in the product settings page or you do not turn on the "Offline Notification" function, the App will not have relevant notification. Thank you for your understanding and support, and have a nice day.
Dear user, we are sorry for your inconvenience. After timing is set, a Bluetooth device will run the timing program locally. Common Bluetooth devices do not have an RTC chip and cannot ensure accurate running of the timing program. After a time, the timing information will be inaccurate. To solve this problem, a Bluetooth device needs to connect to a Bluetooth gateway to calibrate the time periodically with the cloud or mobile phone. However, the mobile phone may not always be connected to the Bluetooth device. To use the timing feature and ensure its accuracy, a Bluetooth gateway is required.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Ensure that your device is powered on and turned on. Ensure that your device has strong and stable Wi-Fi signals and is in the online state in the App. After the device is scheduled, the device has not been shut down or reset, because shutting down or resetting the device will interrupt the timing process of the device; Ensure that the validity period of the scheduled task is correct. Tap Timing and check whether Repeat covers the required validity period (Monday to Sunday available) of the task. If it is a Wi-Fi device, the device may be disconnected from the network, so time-related functions are invalid. If it is a Bluetooth device, it cannot always be connected to the phone, so it must be equipped with a Bluetooth gateway to ensure that the time-related functions of the device remain normal. If it is a Zigbee device, it must be connected to a Zigbee gateway in order to obtain time and keep time-related functions normal. If the timing does not take effect at the time you set, it may be that the time zone of your device is inconsistent with the time zone of your location; If the problem is not improved, pleaserestore the device to factory defaults through the App, set the timer task again after adding the device again. If the issue persists, provide us with your device ID and the specific time when the task failed (the configured validity period, time when the task failed to run, or time when the task ran but at an unexpected time). We will arrange for technical support engineers to troubleshoot this issue.
Dear user, we are sorry for your inconvenience. Please confirm that the time zone of your device under "Device Information" is correct, and then check whether the time zone under "Personal Center" in the App is correct, because these time zone settings will affect all " Schedule, Timing "and other time-related fuctions. You can fix these issues in the following ways: If the time zone of the device is incorrect, you need to remove the device after changing the time zone, and then adjust the time zone correctly in the phone settings, and then add the device again. This is because the device's time zone is based on the time zone in your phone settings, not the time zone under "Personal Center" in the App. If the time zone under "Personal Center" in the App is incorrect, after you change the time zone, you need to remove all "Schedule" and "Timing" and add it again. If the above two situations occur at the same time, please perform step 1 first and then step 2. If the problem is still not resolved effectively, please contact us again, and we will check for you what time the "sunset" time you set for the device for further investigation.
Dear user, we are sorry for your inconvenience. Please check in the following ways: The device may have performed the task, and some devices will cancel the countdown after the device has performed it. It's recommended that you delete the original timer then edit a new one so that the schedule task will perform accurately. If the problem still exists, please try to remove the device and add it again. If it is a Wi-Fi device, the device may be disconnected from the network, so time-related functions are invalid. If it is a Bluetooth device, it cannot always be connected to the phone, so it must be equipped with a Bluetooth gateway to ensure that the time-related functions of the device remain normal. If it is a Zigbee device, it must be connected to a Zigbee gateway in order to obtain time and keep time-related functions normal. If it still does not work, Please provide feedback in the App feedback path.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Try to update or reinstall the App and restart the phone to check if it can solve the problems. Restore the malfunctioning device to the factory settings in the App, and then add it again to check if the malfunction can be solved. If the problem persists, please provide the App version number and the virtual ID of the device with abnormal functions to our customer service staff, and we will help you solve the problem as soon as possible.
Dear user, we are sorry for your inconvenience. If you do so： Ensure that the network environment has strong and stable signals. Please restart your phone, and try again. Please reinstall the App, and again. If the problem still occurs, there may be compatibility issues between the App and your phone. Please submit feedback in the App, provide us with the App version, login account, phone model, and system version, so we can help you to check it.
Dear user, we are sorry for your inconvenience. Please refresh the device list and enter the view again. If this function still cannot be turned on, please remove this device and add it again and try again. If this problem persists, there maybe some changes in the setting as for the latest version, and you can't get it back. You can give us a description what your need is, and provide your App version, your device ID and contact us again. We will reflect your issue. Thanks for your support.
Dear user, we are sorry for your inconvenience. This is because the product manufacturer has not configured the correct language pack for your device. The language of the notification message and the device options are set by the product manufacturer and cannot be changed by us. If you want to change the language of the notification message and the device options, you can report this problem to the after-sales service of the product so that they can improve later. Thank you for your support and understanding.
It is possible that the firmware is still in the testing phase, and the device manufacturer has not yet initiated a comprehensive rollout. We recommend being patient and waiting for the firmware upgrade notification to be pushed. If you still wish to upgrade to the latest firmware, we suggest contacting the retailer for further assistance.
Click "My - FAQ and Feedback" at the bottom of the App to enter the "Help and Feedback" page to view frequently asked questions; If you have any questions, click "Smart Assistant" to ask questions to the smart assistant; If the problem has not been solved or you have other suggestions, click "Feedback Questions" below to submit your questions or suggestions; (The selection of the "Select Problem Device" information in the Submit Question/Suggestion interface will help your feedback to be improved. faster and better processing) Feedback processing progress: Click "My - FAQ and Feedback", and then click "My Feedback" in the upper right corner to view.
Dear user, we are sorry for your inconvenience. Zigbee devices need to be equipped with a Zigbee gateway to achieve voice control.
Dear user, we are sorry for your inconvenience. Please check in the following ways: First of all, you need to confirm that the new device you add to the App supports the third-party smart speaker, and the unsupported device cannot Appear in the device list of the third-party smart speaker you have bound. Normally, the new added devices in the App will also Appear in the device list of the third-party smart speakers you have bound. If the device you added to our App does not Appear in the device list of the third-party smart speaker, you can try to command the speaker to "discover device". If the device you added to our App still does not Appear in the device list of the third-party smart speaker, it may be that the network fluctuates and the new device cannot be synchronized normally. You need to cancel the App account and the third-party smart speaker App Bind and bind again. If the problem still occurs, please provide us with the device ID and your account ID, and we will arrange for a technician to troubleshoot for you.
Dear user, we are sorry for your inconvenience. First, you need to make sure that the device supports the third-party control: Please confirm whether the device supports voice control and whether it has been successfully bound to the voice speaker. For details, refer to the Third-party control instructions. Please confirm whether the device is online normally. You can see if it is normal through the App operation. Different types of devices can operate different voice commands. Please confirm with the device manufacturer whether the device supports this voice command (the device may not have all functions connected to the voice control module). If the device does not support the voice command, you can add the function as Tap-to-Run/Automation in our App, so that you can control the Tap-to-Run/Automation by voice to meet your needs (currently only Amazon Alexa, Google Assisitant and Baidu Xiaodu supports scene control). Please confirm the device name is easy to identify, it is recommended to take 2 simple and common words, such as "living room light". Please confirm whether the smart device App account bound in Alexa Echo/Google Home has changed. For example, reset the device and add another account (one Third-party control account can only be bound to one App account, an error will be reported if the binding is repeated). If the speaker or Siri responds successfully, but your device does not respond to the operation, it means that the device you are operating should be a Bluetooth or Zigbee device, and you need to match the corresponding gateway to be able to use the speaker or Siri to operate. Check that the device has been discovered and joined to the third-party control App： It is possible that your App and device are under the LAN and can be controlled under the LAN, but the device is already offline under WAN. Unbind the App and third-party smart speakers, and re-bind the skills. Check that the voice instructions you are giving to the third-party control are co.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please confirm whether the device supports voice control and whether it has been successfully bound to the voice speaker. For details, refer to the Third-party control instructions. Please confirm whether the device is online normally. You can see if it is normal through the App operation (Bluetooth devices must be connect with a Bluetooth gateway, and then they can be synchronized). If you want to link your camera and camera monitoring screen to smartspearker, but you can't succeed, then you need to contact the device seller to activate this feature for you (for your privacy, this feature is mostly closed). Please confirm whether the smart device App account bound in the third-party control has changed. For example, reset the device and add another account (One Third-party control account can only be bound to one App account, an error will be reported if the binding is repeated). If the problem still exists after performing the checks above, use the Report Issue feature in the App Help Center to let us know about the problem. Be sure to include your App account user name and the ID of the affected device.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Currently, after modifying the device name in our App, it cannot be synchronized to the third-party smart speaker (because the third-party smart speaker is a closed platform), and the new name of the device can only be synchronized after you rebinding the third-party smart speaker to our App. You can rename multiple devices or a single device name in the third-party smart speaker App, so that you can achieve your needs. When you set the new name, please try to modify the device name to be easily recognized by the third-party smart speaker, otherwise the control command will not be recognized and the control will fail. After excluding the above problems, it still doesn't work. Please provide us with relevant information (third-party smart speaker App account, your App account, device ID, Approximate time of occurrence), and we will serve you wholeheartedly.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please confirm whether the device supports voice control and whether it has been successfully bound to the voice speaker. For details, refer to Alexa Echo/Google Home instructions. Please confirm whether the device is online normally. You can see if it is normal through the App operation. Different types of devices can operate different voice commands. Please confirm with the device manufacturer whether the device supports this voice command (the device may not have all functions connected to the voice control module). If the device does not support the voice command, you can add the function as Tap-to-Run/Automation in our App, so that you can control the Tap-to-Run/Automation by voice to meet your needs. Please confirm the device name is easy to identify, it is recommended to take 2 simple and common words, such as "living room light". Please confirm whether the smart device App account bound in Alexa Echo/Google Homehas changed. For example, reset the device and add another account (One Alexa Echo/Google Home account can only be bound to one App account, an error will be reported if the binding is repeated). If the speaker or Siri responds successfully, but your device does not respond to the operation, it means that the device you are operating should be a Bluetooth or Zigbee device, and you need to match the corresponding gateway to be able to use the speaker or Siri to operate. If you still can not solve, please provide an account (email or phone, be sure to call the area number of the phone) to contact our customer service, we will let the technical staff to find the cause of the problem and help you solve it.
The issue of your account not existing might be due to not selecting the correct data center. If you are a user located outside of mainland China, please switch to the International Data Center. If you still face any issues after switching to the Data Center, please do not hesitate to contact our customer support team. We are more than happy to assist you in resolving any problems you may encounter. Thank you for your understanding and cooperation. We appreciate your continued support.
This issue occurs because the wireless signal strength is weak. Slide the App page downwards to refresh the page.
Restart the Zigbee smart door lock and gateway and reconnect them. Check the strength of signals that the lock is receiving. Place the smart door lock 5 m or less away from the gateway. Confirm the firmware version. Typically, Zigbee door locks with a module firmware version earlier than 1.0.7 may encounter this issue. To resolve it, reset the gateway. If the problem persists, ensure that the smart door lock and gateway are in the same channel.
After you turn on Bluetooth in your mobile phone, the maximum communications distance between the smart door lock and the mobile phone is 10 m if there are no obstacles. We recommend that you place your mobile phone 3 m or less away from the Bluetooth smart door lock.
Yes. The smart door lock's fingerprint recognition module can automatically identify and reject fake finger films to ensure secure unlocking with a fingerprint.
Usually, to add fingerprints to a door lock, you need to access the system settings on the lock screen, then go to User Management and select Add/Delete Administrator/Member fingerprints. Please refer to the instruction manual for detailed guidance on how to enroll or modify fingerprints. If you cannot find the electronic or physical version of the manual, try contacting the manufacturer's customer support hotline at 400 for assistance. If you are unable to reach the manufacturer's support, you can try one of the following methods to enter "Management Mode": 1、Press *# and follow the voice prompts to enter the administrator password for identity verification. Afterward, access the management menu options and follow the voice prompts to enroll fingerprints. 2、Press 0# and follow the voice prompts to enter the administrator password for identity verification. Afterward, access the management menu options and follow the voice prompts to enroll fingerprints. 3、Press *# followed by the administrator password# to enter Management Mode.
Please follow the following steps to troubleshoot and handle the issue: 1) Turn the key to 90° and turn the handle; 2) The key is incorrect, replace the key; 3) The latch of the lock body is stuck, and the door is tightly against the door frame. Try turning the handle or using your hand to hit the lock tongue and the position of the door frame; 4) The lock cylinder is stuck, disassemble the lock for inspection.
The camera mainly has two mechanisms of manual storage and automatic storage: Manual storage: Manually click on the App to record and store it locally on the phone: iOS will store the saved screenshots and videos in the App's built-in photo album, which can be exported to the iPhone's system photo album; By default, Android will generate a "Camera" folder in the phone, where screenshots and videos will be saved (different folders are generated for each device). Automatic storage: SD card storage: The video will be automatically stored in the SD card. The SD card supports event video and continuous video mode switching. When it is full, the new video will overwrite the oldest video. cloud storage: After purchasing and activating the video cloud storage service, the device can encrypt and upload the corresponding type of video data to the server. Even if the device is artificially damaged, the SD card is damaged, or the device is stolen, etc., as long as the device is still in the user account, the cloud history Videos are still viewable. Relevant knowledge: I cannot find the way to buy the cloud service?
Dear user, we are sorry for your inconvenience. Please make sure that your SD card is compatible with your camera. If you make sure it is compatible and the camera still cannot detect it, please remove it form camera and insert it again. You can use the card reader to the computer to format the SD card to FAT 32. You can also consult the sales staff how to format it to FAT 32. If you still cannot access the SD card, it means that the SD card is damaged. The SD card is a wearable product. Excessive reading and writing will greatly reduce the service life of the SD card. Thanks for your understanding and support.
Dear user, sorry for the inconvenience. If you do so： Check whether the router is powered off or disconnected from the network. If so, the router will take some time to recover. Wait for two minutes and then check whether your device is online. Check whether the router has been replaced, or the Wi-Fi name or password has been changed. If so, remove your device and then add it to the network again. Check whether the firmware is the latest version. To check this on the App, choose Home—Tap device icon—Top right button—Check for Firmware Updates. If the device goes offline after a period of use, but after restarting the router or re-networking the device, the device returns to normal. Indicating that the router is overloaded due to long-term high-load use, and you need to replace it with a more powerful one, or reduce the number of devices connected to the router. If your device still fails to connect to the network after the preceding steps, place your device in a network environment with strong and stable signals and connect it to the network again. If your device is still offline, please give us feedback. We will arrange for technical support engineers to troubleshoot this issue. Feedback path：How do I report issues that I have encountered?
Dear user, we are sorry for your inconvenience. If you have any problem with adding device to the App, please refer to the following steps to troubleshoot:The device has entered the net pairing state. The Wi-Fi name is short and simple, and does not contain any Asian or special characters. The scanning distance is set properly. The lens of the camera is operating properly (the camera is not out of focus) and is able to scan the QR code. The Wi-Fi account and password are entered correctly. The camera is connected to a 2.4 GHz network. If your device still fails to connect to the network after the preceding steps, provide us with your App account. We will arrange for technical support engineers to troubleshoot this issue. "Auto Scan" pairing failed EZ mode pairing failed AP mode pairing failed.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Please make sure that the noise in the video has nothing to do with the background sound of the environment where the camera is located. It is recommended that you use another mobile phone to log in to the account to watch live video to see if there is noise. If there is no noise in the real-time video, but there is noise in the video being played back, it is caused by your network speed is slow or the read and write speed of the inserted SD card does not reach the standard. If users watch real-time video through multiple mobile phones and find that the device is always accompanied by the same noise, the problem may be the camera itself, which requires you to contact the seller for after-sales.
Generally speaking,the privacy mode/sleep mode of the camera is a similar function. In this mode, the camera may stop audio and video collection and turn off some functions related to audio and video control, ensuring that the camera usage environment is in a non-"visible and audible" scene, thus protecting the privacy of consumers. The specific functional logic may vary for different products; please refer to the product manual for details!
Hello, you can click on the relevant device to access its settings page, then click on "motion detection settings" and toggle the button to enable or disable the motion tracking feature. If you want to receive alerts in the app when motion is detected, you can also synchronize the motion detection alarm switch.
Dear user, we are sorry for your inconvenience, you can contact the seller and provide the corresponding transaction information to let the seller help you after sale.
Although both 2.4 GHz Wi-Fi and 2.4 GHz Bluetooth work in the 2.4 GHz frequency band, they use different radio frequency bands and protocols. Therefore, you cannot control a Wi-Fi bulb directly with a Bluetooth remote control.
A Zigbee wall SoCket can replace traditional SoCkets, control power-on and power-off of electric Appliances, support various control modes such as local button control, asSoCiated sensor control, and remote App control, and measure the power usage of electric Appliances.
The number of devices that can connect to a gateway varies, depending on the gateway model. A Tuya-developed gateway can connect to 50 to 128 Zigbee devices.
Dear user, we are sorry for your inconvenience. If the camera supports sending notifications, open App, choose Me &rt; Message Center, tap the gear icon in the upper right corner of the page that appears, and then tap Enable notifications. Turn on your smart camera's alarm switch, and allow notifications from App in system settings of your mobile phone.
You can stop it in TuyaSmart, or quickly press the reset key of the audible and visible alarm three times.
A 220 V three-pin flat plug powers an audible and visible alarm. The alarm also has a built-in lithium battery that can last for one hour after you power off the alarm.
The indicator light will stay on for three seconds after you power on the PIR motion sensor. If the light is not working, first check the battery level, and then check whether the battery is making good contact with the device. If the problem persists, contact customer service for help.
Q: How long is the battery life? Temperature and humidity are collected by default once every 5 minutes, reported up to 100 times a day. The CR2450 battery lifespan is over 1 year; if the collection frequency is less than 1 minute or reported over 100 times a day, it is recommended to use a battery with a capacity of size 7 or above. Q: What types of batteries does it support? Regular batteries are 3.0V, such as two size 7, two size 5, CR123, CR2, etc. If using three size 7 or 5 batteries, or rechargeable batteries, the hardware design should have a voltage reduction circuit. Q: Any other considerations for the battery? It is advisable to choose high-quality batteries with good discharge performance. When high-frequency reporting occurs in usage scenarios, avoid using button cells.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Remove the universal remote control in the App. Add the universal remote control to the App again, and then add your device. If you cannot find the device you want to add, you can use the DIY function to learn the remote control of the device. During the learning process, you need to align the infrared emitting area of the infrared remote control with the infrared remote control area of the universal remote control. The distance between the two is no more than 3cm. Press the button you need to learn according to the page prompts. If you can find the device but cannot save it. Please provide your device brand and model, as well as a screenshot of the related error page for us to troubleshoot. Thank you for your support and understanding.
The air conditioner mate supports wall-mounted air conditioners with 16 A plugs. If you use a cabinet air conditioner or central air conditioning, the air conditioner mate may not provide a good user experience because of the installation position of the air conditioner, and some features may unavailable.
Dear user, if you do so: Firstly, add the new gateway to the App. Click the new gateway to be replaced to enter the device setting page. Click the "Replace a damaged gateway" function at the bottom of the page. Enter the S/N code or device ID of the old gateway. Confirm and wait for the successful migration of the gateway. After replacement, the sub-devices and related scene functions under the original gateway will be synchronized to the new gateway. Note: Not all gateways support the "Replace a damaged gateway" function. This function requires support of hardware and firmware. For details, please consult the device seller or manufacturer.
Dear user, we are sorry for your inconvenience. The human body is most comfortable in an environment with a humidity of 40% to 60%. Selecting the cooling mode is mainly based on cooling, suitable for environments with low humidity; dehumidification is mainly based on removing indoor moisture, suitable for environments with high indoor humidity.
Hello, this product supports wall-mounted air conditioners with 16A plug specifications. If your air conditioner is a cabinet or central air conditioner, you may not get a good product experience (affected by the product installation position), and some functions may not be available, please pay special attention.
YouTube：https://youtu.be/MWqG4N0TVZU Dear user, we are sorry for your inconvenience. At this stage, only the Security App and our latest version App support this feature. When there is at least one security gateway in the device list, the "Smart security" function will be activated. This function supports basic arming and disarming functions. At this stage, general gateways are not supported to use "Smart security"function. In the future, we will add this feature to all our gateways. At that time, you can update the normal gateway to a security gateway by upgrading the gateway firmware.
This series of products supports only 2.4GHz Wi-Fi networks.
Dear user, we are sorry for your inconvenience. Please check in the following ways: Low-power devices (devices that use batteries are usually low-power devices) are designed for low power consumption, so the device will not report the offline status of the device in real time. Only if the device fails to report for three consecutive heartbeat cycles (the heartbeat cycle duration can be customized by the manufacturer, with the default being 4 hours per cycle), the App will display that the device is offline. (So if your sensor device has stopped working, but it still shows online in the App, you can pairing the device again to get it back to work as soon as possible.) If it is the normal device powered off or disconnected from the network, the device will display offline in the App in 3 minutes, and it will display online within 30 seconds after device reconnecting to the Internet. If it is the gateway powered off or disconnected from the network, the gateway and the sub-devices under the gateway will display offline in the App in 3 minutes, and it will display online within 30 seconds after gateway reconnecting to the Internet.
If you have any questions about using the app to control the device, you can: Tap on "Me - FAQ and Feedback" at the bottom of the app to access the "Help and Feedback" page and view common questions. If you still have questions, you can tap on "Chat Bot" to ask the virtual assistant. If your issue remains unresolved or if you have any other suggestions, you can tap on "Feedback" at the bottom to submit your questions or suggestions. (Selecting the device information under "Select the Problem Device" when submitting will help us handle your feedback faster and better.) To check the progress of your feedback: Tap on "Me - FAQ and Feedback" and then tap on "My Feedback" in the top right corner. For information regarding product functionality and settings, we recommend consulting the product manual or contacting the device seller for better assistance in resolving your issues.
Dear user, If you want to buy a smart device suitable for our App, it is recommended that you search for the name of our App from a third-party e-commerce platform, and consult the seller for products that support our App.
Dear user, we are sorry for your inconvenience. Please upgrade the App to the latest version and make sure Bluetooth device is successfully connected. And select the Bluetooth device as the playback device in your phone system. Thanks for your support.
Hello, this is because the device has not uploaded the MAC address to the app. In this case, you can try the following methods to find the MAC address of the device: 1、In general, manufacturers usually place the MAC address on the packaging or the device itself. You can try looking for it there. 2、Additionally, you can also try logging into the router's backend to find the MAC address of the connected devices. If none of the above methods work, I suggest contacting the point of sale or the device manufacturer for further assistance.
Dear user, we are sorry for your inconvenience. You can remove Bluetooth mesh devices only in a connected state. You can also reset the Bluetooth mesh device, and then remove it from the App.
Dear user, we are sorry for your inconvenience. The device might be a Bluetooth device. Bluetooth devices can be shared through home sharing, but one Bluetooth device can only be connected to one phone.
Dear user, we are sorry for your inconvenience. If your mobile phone that is connected to your Bluetooth mesh device is within the communication range of the Bluetooth mesh device, you can control the device in the App directly. If a gateway is used between your mobile phone and Bluetooth device, you need to reconfigure the connection between your mobile phone and the gateway, but not the connection between the gateway and the Bluetooth mesh device.
Dear user, we are sorry for your inconvenience. Due to the limitations of streaming music Apps, only the music stored locally on the phone can be displayed in the music list of our App: Android phones: the music in the music App needs to be downloaded to the phone's local music folder before it can be displayed in the playlist of our App. iPhones: the music needs to be synchronized to Apple's official music App before it can be displayed in the playlist of our App.
Dear user, we are sorry for your inconvenience. The sudden failure of App control may be caused due to network reasons or the device is offline. Please confirm whether the device is powered on. It is recommended that you keep the App open and wait for about 3 minutes to see if the device is still online. If you find that the device is offline, you can follow the "What should I do if the device is offline?" in the FAQ. If it is still online, please place your phone next to the device, and then connect to the same Wi-Fi as the device, and try to open the webpage to see if it is smooth to judge the network status. If the device is online and the network is good, but still can not control, please provide feedback in the App feedback path.
Dear user, we are sorry for your inconvenience. You need a Bluetooth mesh gateway, and connect all Bluetooth mesh devices to the Bluetooth gateway to achieve remote control of the Bluetooth mesh device.
Yes.
Yes, the repeater can extend the transmission distance of the Zigbee gateway.
When there are sub-devices in the gateway, it will not automatically switch; when there are no sub-devices in the gateway, you need to restart the gateway to automatically select the optimal channel.
If the linkage scenario is set up in advance with an extranet connected, when Zigbee gateway is not connected to an extranet, it can be linked locally as long as the scenario is triggered.
The no-code solution for multi-functional gateway and the general Wi-Fi integration for WRG1 module gateway in the custom solution.
No, except for the multi-mode gateway, there is a separate reset button that will clear the settings. After the gateway is removed, it re-enters the pairing mode, if: 1. It is paired by the original account and original family, then the sub-device data is restored by default; 2. It is paired by the original account but a different family: the sub-device data is cleared by default (the cloud will send a factory reset command to the gateway, and the sub-device data in the cloud is also cleared); 3. It is paired by a different account: if it is a different family, then the sub-device data is cleared by default (the cloud will send a factory reset command to the gateway, and the sub-device data in the cloud is also cleared); if it is the same family, then the sub-device data is restored by default; 【Note】: Applicable for Zigbee, Sub-G, infrared, 485, and other protocols After the gateway is removed and re-enters the pairing mode, if: 1. It is paired by the original account and original family, then the sub-device data is restored by default; 2. It is paired by the original account but a different family: the sub-device data is not displayed by default, if later it is paired by the original account and original family, then the sub-device data is restored; 3. It is paired by a different account: the sub-device data is not displayed by default, if later it is paired by the original account and original family, then the sub-device data is restored; 【Note】: Applicable for Bluetooth protocol.
Check whether the reported DP ID is the same as that defined. For new DPs, you must unbind the device and re-pair it with the network for the DPs to take effect. The SDK verifies the validity of DPs and checks whether the reported value exceeds the defined range and whether the reported DP type is the same as that defined. The SDK performs flow control. When the reported value is the same as the locally cached value, the SDK does not report the DP.
Common sub-device control and management operations are delivered to the gateway through the App. After protocol conversion is performed, the gateway controls and manages sub-devices. For local automation, the gateway calculates automation rules to control sub-devices.
The permissions on basic device functions and operations can be shared. Configuration-related permissions cannot be shared. You are not allowed to control a single permission.
No. Control using a third-party voice speaker is a function that needs to be enabled on the cloud. Contact Tuya engineers to enable the function for you. Note: We recommend that you use the standard categories and standard function points of the platform for your products. This will help your products get better and faster access to third-party speakers.
You can view the enabled three-way voice services in the product list and product details in the developer platform. Product List Product Details.
For the color temperature, Amazon Echo and Google Home receive a specified color temperature value, which is calculated as a percentage and issued to the firmware. Amazon Alexa： warm, warm white 2200K incandescent, soft white 2700K white 4000K daylight, daylight white 5500K cool, cool white 7000K Google Home： warm white/soft white 3000K cool white 4000K white/daylight white 5000K.
Not possible. If you uses the OEM APP of the Tuya system or the APP developed based on the SDK, Tuya needs to provide key internal configuration information of the system. Therefore, you cannot independently complete the skills used with OEM APP.
This error may occur if you do not configure DPs for the product corresponding to the PID. You need to use a product with DPs or re-create a product.
This is because the Echo Show initialization function is not called.
Customers are required to develop their own firmware, with various data points, which can be combined with motor hardware to control the stroke, steering switches, and motor load detection. However, the firmware has complex functions and requires a high degree of qualification from the manufacturer. The product's development cycle is long. Typically, this solution uses Percentage motors and connects the motor to the module through a protocol.
It is recommended to create a product in the Electrician-Wireless Switch_Dimmable Version entrance and choose a custom scheme. Note: 1. dp52, scene_switch dp points must be selected; 2. If you do not customize the panel, please find the project manager responsible for docking to open the whitelist and add the debugging panel. 3. Please choose the firmware name: zigbee ZS3L universal docking scene firmware, firmware key: keym3vpw for development. 4. For dimming-related protocols, please refer to the last three sections of the following link: https://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty#title-39-%E4%B8%8B%E5%8F%91%20kid%20gid%20sid(0x41).
No, the IO port drive current is only 12mA, which is not enough to drive conventional relays.
No, adjust by the module.
Visit Tuya IoT Platform, to 'Development-My Products', select 'Products available for OEM' in the upper right corner.
Only products in the status of mass production and non-customized firmware under their own name can be sent to brand customers for OEM operations. 1. Production completed: It can ensure that the key information of the product will not change again, and the products that can be created by OEM in the future are highly consistent, which is convenient for the factory to manage and maintain firmware and other information for brand customers in the later stage. 2. Non-customized firmware: Because the customized firmware writes the PID in the firmware and cannot be modified in production, if the newly generated product also uses this customized firmware, the produced equipment will be unusable. The following custom firmware products do not currently support OEM: Custom firmware products associated with multiple different PIDs (such as all-in-one air conditioners).
As shown in the figure below, you can set a device's total online duration as the trigger condition to automatically send a message to users. For example, a message can be pushed to users in time to remind them of replacing consumables or applying for appropriate maintenance and other after-sales services. Notes: 1. The trigger condition of the device's total online duration cannot be implemented together with other trigger conditions. If you have set the device's total online duration as the trigger condition for a device, no other trigger condition can be set. 2. Currently, the device's total online duration supports only the T+1 message push mode. For example: The T+1 mode indicates that the trigger condition is determined at a regular interval every day. If the trigger condition is met after the regular determination, the message is pushed the next day.
In response to this situation, boolean, enumerated, numeric, and other types of data reporting will be filtered out by the module, and no information can be found; however, raw data can.
Yes. You can enter the UUID on the Tuya Developer Platform under Products - Device Management to check the status of the device.
Firmware, which is the program writing to EROM (erasable and read-only memory) or EEPROM ( erasable or programmed in read-only memory). Firmware refers to the device 'driver' stored inside the device. Through the firmware, the operating system can implement the operation of a specific machine in accordance with the standard device driver. For example, optical drives and burners have internal firmware. Firmware is the software that serves as the most basic level of a system.
It's Identification of the firmware.
The product needs to be connected under a gateway to be online and function properly.
The Bluetooth mesh solution requires both the remote controller and the lights to be connected to the app before local pairing or adding lights in the app can occur. Local pairing needs to be done within 30 seconds after the light is powered on. If the firmware configuration includes a group switch function, you need to long-press the "group on" button to pair.
The latest version of SDK has already removed the relevant interface (after 5.0.0). If you want to continue using this feature, it is recommended to use the "Feedback and FAQ" UI business package.
This is due to the lack of com.thingclips.smart:thingsmart-login-plug-api:4.5.0-rc.2 in the integrated business package, and the current solution is Add dependency com.thingclips.smart:thingsmart-login-plug-api:5.0.0, currently, this problem only occurs on Windows.
No device details json file added, please addjson file (Here is a demo, which added a custom item, it can be deleted if not needed).
Reference link： Android：https://github.com/tuya/tuya-home-android-sdk-sample-java iOS：https://github.com/tuya/tuya-home-ios-sdk-sample-objc.
In the SDK development method, the push function needs to be developed by yourself. In the SDK development method, the push function needs to be developed by itself. You can classify according to the category field in the received message, and process the message in the callback received by Google, and display different notifications according to the category.
Select all the types for scanning and obtain the configType value from the scan results to check the corresponding pairing method.
Use the AbsPanelLifecycleService listener management class in the TYRCTSmartPanelActivity page to detect device removal and check whether the current control panel belongs to the removed device. If yes, the TuyaSmartSdk.getEventBus().post(new PageCloseEventModel()) method is sent to close the control panel.
You need to add the following URLs to the root directory build.gradle: maven { url 'https://dl.bintray.com/tuyasmartai/sdk' } maven { url 'https://maven-other.tuya.com/repository/maven-releases/'}.
When the Android SDK calls the inviteShare interface to send an invitation to other users, you need to add 86- and the shared account in the userAccount parameter. The iOS SDK calls the confirmInviteShareWithShareId interface to confirm the sharing invitation. If 86- is not added in the userAccount parameter, errorCode: NOT_EXISTS sharing invitation does not exist will appear.
It is necessary, and the demo also needs to have the package name, security components, Appkey, and AppSecret configured properly to function normally.
Please refresh the developer platform SDK page, then rebuild and download the latest compressed package, and delete the security component configured in the project to reconfigure it.
You can query the room list and device list of the room in the home through the following interface: ListRoomBean rooms =ThingHomeSdk.getDataInstance().getHomeRoomList(homid); ListDeviceBean deviceBeans =ThingHomeSdk.getDataInstance().getRoomDeviceList.
The DPs in one device control command must not conflict with each other. For example, the lamp brightness and cold/warm DPs can be sent together. However, if on/off, brightness, and cold/warm are sent together, one or more of them may not respond. Therefore, it is recommended that you combine non-conflicting DPs in one command.
It is because the referenced SDK components are inconsistent. Please confirm whether each version of the referenced library is unified (the highest bit and the median are the same, for example: 3.12.1, 3.12.5), if not, please use pod update to update and recompile.
Check the podfile.lock file in the root directory of the project.
In iOS 5.0+ versions, the visibility of the "Scan" button is controlled by configuring "needQRCode": true, in the "thing_custom_config.json" file.
/** * order all device or group * Sort the devices and groups of the entire family* * @param orderList order list [@"devId", @"groupId"] * @param success Success block * @param failure Failure block */-(void)sortDeviceOrGroupWithOrderList:(NSArray *)orderList success:(TYSuccessHandler)success failure:(TYFailureError)failure.
Modify the version number of the SDK corresponding to the podfile, or do not specify the version, execute pod update in the root directory of the project.
Yes, please see the details here: https://developer.tuya.com/en/docs/app-development/ios-device-firmware?id=Kaj1ck2g3jaqs#title-9-%E9%94%99%E8%AF%AF%E7%A0%81.
#import "TYModuleManager.h" To load the scene log page, create a [Button] event and execute the following code: [TYModule.routeService openRoute:@"ty_scene_log" withParamas:nil].
This problem happens when you use the TuyaSmartTimer().getAllTimer(withDeviceId: devId) API to obtain TYTimerModel. You should use the timer.getListWithTask API instead.
If you encounter a pop-up like "Account behavior is abnormal, use has been restricted", or a pop-up stating " This account has been restriced due to illegal operations ", this is because the account is calling the same interface at a high frequency in a very short (millisecond level) period of time, which results in its use being restricted for one hour. After one hour, the restriction will be lifted automatically. At this time, you need to verify the code logic, to see if there is any bad behavior of frequent calls to the SDK interface in a certain code module. Or provide the following informationfor related personnel to help you find out which interface has been frequently called: 1、App Name 2、Specific time range when the problem occurred (data for up to three days can be retrieved) 3、uid: NSLog(@"\n == The user ID: %@",[[ThingSmartUser sharedInstance] uid]);.
The field in ActionModel and ConditionModel indicates whether the device in the action or condition has been removed. /// If this action is a device type action and this device has been removed from the current account, this flag is YES. @property (nonatomic, assign) BOOL devDelMark;.
The App classifies the countries/regions into: Globally, Outside the Chinese mainland, and In the Chinese mainland. OEM App: If you selected Outside the Chinese mainland when you created the OEM App, you cannot select the Chinese mainland during registration. All-in-one App: If your App is available only in countries and regions outside the Chinese mainland (which can be downloaded from an App market outside the Chinese mainland), you cannot select the Chinese mainland during registration. To register an account in the Chinese mainland, download the App from an App market in the Chinese mainland with a mobile number that starts with +86 in the Chinese mainland. If you use a global App, but your mobile number is not supported in the Chinese mainland, that is, not started with +86, or the local region of the iOS device is not the Chinese mainland, you cannot select the Chinese mainland during registration.
Check whether the requested object is a global variable. If not, the request will be released at an early time. For example, self.feedBack = [[TuyaSmartFeedback alloc] init] requests a global variable.
This error may occur if third-party authentication is configured for the App and the authentication fails. You can disable third-party authentication to resolve this problem.
The debug mode can be set through changeDebugMode. For native development of mini programs, use Tuya.changeDebugMode Be sure to turn it off before going live. Tuya.changeDebugMode({ isEnable:true, success:function () { console.log('success') }, fail:function (e) { console.log('fail', e) } }).
Tuya MiniApp IDE debugging is achieved by generating a virtual device through the virtual device plugin, and presetting the basic hardware and device capabilities that the panel applet depends on, making it convenient for developers to quickly carry out UI rendering and restoration in Tuya MiniApp IDE. However, it is not possible to realize all the hardware or device capabilities that the App side has, such as scanning, phone calls, and other hardware environments, as well as device capabilities like Mesh direct connection. Therefore, the following usage is recommended: Tuya MiniApp IDE debugging: In the early stages of development, when you need to quickly implement UI restoration and basic functional logic. Real device debugging: In the middle and later stages of development, after the basic functional logic has been completed, when you need to test capabilities that depend on the App side.
After the product is created, it is under development. After you complete the function definition, panel configuration, module selection, firmware configuration, and cloud testing, you can click "Release Product" in the fifth step of creating a product on the platform.
It is necessary to check whether the compatible protocol support switch function is enabled in the Edit Panel - Configure Functions. After enabling it, functions such as dynamic password, one-time password, and timed password will not be displayed.
Yes, the fan product has a wind speed dp, and the remaining products can be customized. Increase the wind speed function DP point.
Tuya currently does not support BR, EDR for the vast majority of modules, so there is no need to test BR, EDR during certification testing; testing should be conducted according to the module specification and testing guidelines. It should be noted that if it is a smart selection product (such as a central control screen) certification, testing should be conducted according to the product specifications, and if BR, EDR is supported, it should be tested.
Tuya Zigbee module does not have SRRC certification. According to the "Announcement No. 52 of 2019 by the Ministry of Industry and Information Technology of the People's Republic of China" link: https://www.miit.gov.cn/zwgk/zcwj/wjfb/gg/art/2020/art_4f2c890530cc4837b2113cf977e249c4.html Radio transmission equipment that complies with the "Catalogue and Technical Requirements for Micro-Power Short-Range Radio Transmission Equipment" does not require SRRC certification. The frequency of the Tuya Zigbee module is 2.4G, and according to the "Catalogue and Technical Requirements for Micro-Power Short-Range Radio Transmission Equipment," it is classified as F-type equipment. (1) Frequency used: 2400-2483.5MHz. (2) Emission power limit: 10mW (e.i.r.p). (3) Frequency tolerance: 75kHz. The emission power limit is 10mW, so products below 10mW are considered micro-power devices and do not require SRRC certification. If it exceeds 10mW, SRRC certification is required. Micro-power devices should specify the following in their product instructions (including electronic display manuals): (a) Specific clauses and usage scenarios that comply with the "Catalogue and Technical Requirements for Micro-Power Short-Range Radio Transmission Equipment," the type and performance of the antenna used, and methods of control, adjustment, and switching; (b) Do not change the usage scenario or conditions, expand the emission frequency range, increase the emission power (including additional RF power amplifiers), or change the emission antenna without authorization;(c) Do not cause harmful interference to other legitimate radio stations and do not request protection from harmful interference; (d) Must endure interference from industrial, scientific, and medical (ISM) application equipment or other legitimate radio stations; (e) If harmful interference is caused to other legitimate radio stations, usage must be stopped immediately, and measures must be taken to eliminate the interference before con.
The open-source materials are all included in the module certification data package and can be downloaded and used directly. However, BOM, complete schematics, and other materials are confidential hardware information and cannot be released. During the whole machine certification, the module is just a component, and providing the whole machine information is sufficient. If the institution (laboratory) insists on obtaining it, the customer needs to sign a letter of commitment first, then apply for the release of the open-source hardware solution through business channels. Once approved, the hardware R&D engineer will provide it and directly release it encrypted to the institution (laboratory). Commitment letter template: requires filling in the module model, name, date; and stamping.
No need, SAA is the Australian safety standard and does not involve RF testing, you can directly test the finished product; Australian RCM involves RF, basically the same as CE requirements, and can be converted through CE certification; only RF-related certifications require the use of certified modules.
Simple determination method: Products where the wireless function is the main function cannot reference module certificates, such as wireless gateways, wireless Bluetooth smart speakers, etc. If the product can still function normally without the wireless feature, and the function operated remotely via wireless can also be achieved manually on the product, module certificates can be referenced (a module is a separate module that can be soldered, a chip onboard is not considered a module). The official text is as follows:https://sei.anatel.gov.br/sei/modulos/pesquisa/md_pesq_documento_consulta_externa.php?eEP-wqk1skrd8hSlk5Z3rN4EVg9uLJqrLYJw_9INcO7eVbix077b3KzBHx-n7Uo_SYAnZTOIBfYpeNCFu5zvgqXNsg68q0fPZ4Xmuj7GNY2KbsQ2C4Du9iqajcF9H9BE.
Common Points: Focus on Device Security: All these standards emphasize enhancing the cybersecurity of devices, particularly in the IoT (Internet of Things) field. They generally focus on potential security vulnerabilities throughout the design, deployment, and usage processes. Authentication and Access Control: These standards require devices and systems to implement effective authentication and access control mechanisms to prevent unauthorized access. Data Protection: They emphasize data protection, including data privacy, integrity, and security, ensuring that data is not subject to unauthorized access or leakage during transmission and storage. Vulnerability Management and Security Updates: Most standards stress that devices should have robust vulnerability management mechanisms and be able to release security patches and updates promptly to address newly discovered vulnerabilities and threats. Differences: Regulatory Nature and Enforcement: RED: A European Union directive that is mandatory for all radio equipment that can directly or indirectly connect to the internet sold in the EU market. This means any compliant networked radio equipment must meet RED's cybersecurity requirements before entering the EU market, adhering to specific cybersecurity requirements from design and production to market entry. Other Standards: Breadth of Security Requirements: RED: In terms of cybersecurity, RED includes three basic requirements, including that devices should not harm networks or misuse network resources and should protect user data privacy, financial privacy, and data security. Other Standards: Scope: RED: Covers all networked radio equipment below 3000 GHz, including specific cases such as radio equipment designed for child care, equipment within the scope of the Toy Safety Directive (2009/48/EC), and radio equipment meant to be worn or attached to the body. The scope includes household smart appliances, basic wireless communication facilities, industrial wireless eq.
As a component, the network security assets of the adapter board are completely different from those of the complete machine, and the testing conditions according to the standards are also different. Therefore, the certificates and reports of the adapter board cannot exempt the complete machine from certification. Just like when a module has a CE RF EN 300328 report, the complete machine still needs to redo most of the testing when undergoing CE certification RF testing. Additionally, if the custom firmware is developed by adding custom features to the Tuya public baseline firmware (with most network security requirements reflected in the baseline SDK firmware), then if the public baseline firmware meets regulatory requirements, the custom firmware should also meet these requirements. Furthermore, Tuya has initiated displaying "firmware version (internally the security version number) + firmware code (original firmware number)" to address certification report control over firmware versions. Custom firmware developed based on the Tuya public baseline and the public firmware have the same security version number. Therefore, the certification team suggests that for custom firmware adapter boards based on the Tuya public baseline, there is no need to deliberately use the custom version for testing. The custom firmware can be directly used with the complete machine for network security certification. If the client insists on using custom firmware for the adapter board testing, any resulting certification testing costs will need to be borne by the client.
No, a simple way to determine the applicable scope of products is to only control products that can be directly accessed by the network. Regular Zigbee and Bluetooth sub-devices require corresponding gateways for connection, so only the upstream device needs to undergo RED network security certification.
Only certified products can bear the Zigbee and Matter logos. Refer to the Zigbee logo usage guidelines: 📎 Trademark Usage Guide.pdf Refer to the Matter logo usage guidelines: 📎 Matter Logo Usage Guidelines.pdf.
When the domain name parsed to Tuya's Tuya is detected by cybersecurity to have issues, please refer to the following suggestions: 1. The content of the Server field in the response header of the Tuya domain name, Sec, has been custom obfuscated and does not involve any technical framework. It is not sensitive information, thus it does not constitute a vulnerability of leaking framework information. 2. Both the Tuya application domain name and the public version application use this request header, and no danger warnings have been received so far. 3. If users still have doubts about the feedback from cybersecurity, it is recommended to communicate directly with cybersecurity to find out what specific risks they perceive. 4. Since the Server field is a general configuration, it cannot be modified individually for a single domain name at the moment. 5. If the communication results with relevant institutions are unsatisfactory, you can contact Tuya's business or project personnel to form a discussion group. 6. Tuya officially confirms that this issue is not a vulnerability and does not require further processing.
We build white-label Tuya apps, IoT dashboards, and custom integrations for your business.
🚀 Schedule a Call