Hi, we haven’t spotted any issues in the system logs; we only see OTA update failures. If the device is bricked due to the failed OTA, this cannot be resolved remotely. End customers need to contact their seller to arrange a replacement via after-sales service.

Alright, we’ll look into this and figure out what’s causing it.

I can see a device named "2-433" under your account with the virtual device ID a3e086b1ada82864726kmt. Is this the device you are referring to?

Please provide the following information:

1. What is the name of your app?
2. Which country did you register in?
3. Approximately when did the issue you described occur?

If you have the virtual IDs of any other devices, please provide them as well. We need these to identify the data center your service is connected to.

oh，Please remove the passwords; we only need your app accounts. The device virtual ID can be viewed by tapping the icon in the upper-right corner of the device panel in tuya app.

hi, could you please provide your app account and device virtual ID？

We sincerely apologize. Since this SDK is shared across multiple business lines, testing for Home Assistant was insufficient. We have repackaged it with bug fixes and completed full testing. Please upgrade to version 0.2.13.

Thank you for your feedback.

Please provide your device ID and approximate call time for our troubleshooting, thank you.

pls try again