Tuya doesn't work

[BorisAbakumov]

The problem

Tuya receives information from cloud devices only once - during boot or restart. No further additional information is received from cloud devices. Integration can still change the state of the device, but it cannot receive confirmation of its actions. As an example: the switch works when you try to turn it on, this action successfully switches to the cloud, but the Tuya integration considers that it has failed to send data and switches the switch state back to the off position. However, the switch remains on in the cloud.

What version of Home Assistant Core has the issue?

2025.4.3

What was the last working version of Home Assistant Core?

Maybe 2024?

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

Hey there @tuya, @zlinoliver, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tuya can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tuya Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tuya documentation tuya source _{^{(message by IssueLinks)}}

[sovest77]

Yes, the same problem. The status of sensors and switches does not change.

[grig27]

binary_sensor.contact_sensor_door not changed... In Toya Smart Life door sensor worked.

[jose2068]

todos los controles de acceso tuya han dejado de funcionar desde hace horas con home assistant

[CTAPOCTA]

Такая же херня...

[blackjec69]

The same thing. After restarting the integration, it receives data from the smart outlet for a while, then stops until the next restart.

[GeeGee-be]

Same here. Tuya integration doesn't work anymore after a restart of HA. What a mess.

[Vlad939b]

I am experiencing an issue with my Tuya Zigbee devices .The device state (on/off) updates correctly ONLY ONCE after restarting the Home Assistant service, or after restarting Tuya service.

[Whiteypio5150]

Same issue here

[CAHbKA-A]

I have the same problem. It started about a month ago. То же самое. началось примерно месяц назад. потом после рестарта неделю работало и опять отвалилось. в логах ничего интересного.

[Aleksey14ru]

Same issue here

[Dianov1982]

Same issue here

[GeeGee-be]

Is someone even looking at this? For a non-custom integration I would think there is at least a reply, info or progress message. Even a temp solution.

[ryrun]

I'm having the same issue with an LCO-351 (Light Strip). Sometimes it suddenly shows up as "On" in Home Assistant even though it's not actually active. When I try to turn it off using the switch, it just flips right back to "On" afterwards.

[IgorTihonov]

I confirm the problem. Home Assistant 2025.4.4, data reception from Tuya devices occurs only once at the moment of HA restart or the integration itself. The reaction of devices to commands from HA is either incorrect or absent. Is there any solution?

[dengi76]

Hello! Unfortunately I have the same problem!

[Preen59]

I'm also experiencing exactly the same issue. If I use the Tuya app I can confirm that the devices are still functioning but HA can't interact with them.

[impas1k]

This has been happening to me for the last 3 weeks. Integrations used to work,, but some devices were offline in the app, so Tuya Hub was working fine with devices that was online without interruptions. Now my Tuya app is showing that all devices are online and nothing is going offline in the app. But after I restarted HA, the Tuya Hub failed to initialise.

[impas1k]

This has been happening to me for the last 3 weeks. Integrations used to work,, but some devices were offline in the app, so Tuya Hub was working fine with devices that was online without interruptions. Now my Tuya app is showing that all devices are online and nothing is going offline in the app. But after I restarted HA, the Tuya Hub failed to initialise.

Okay, so I think I know what happened. Tuya did some changes on their end, and now, after the core update, those changes have made Tuya unavailable. Developers need to check what happened with the Tuya API and integration.

[vic-tor71]

Unfortunately I have the same problem!

[denis-samsonov]

Same issue here

[Frikkie50]

Same issue my end, all my power monitoring plugs entities stop working after a while. Reload the tuya integration it's works for a bit then stops again.

[GeeGee-be]

I came to find out that logging in and status changes are just very very slow. It seems that polling frequency is about 5 minutes. I just did a test with a switch and after about 5 minutes it updated in Tuya.

[anton-kozhevnikov]

The same issue since April, 16. But it looks like a network one, changing a provider to another helps, however is not much promising. Mb it’s another restriction. I tried to install WireGuard client directly into HA, it works, but Tuya is still numb.

[Vlad939b]

The symbiosis between Tuya and Roskomnadzor is the absolute bottom. I'm not buying any more cloud-dependent devices, switching everything to Zigbee. Hopefully, they won't be able to break it anytime soon..

[sovest77]

The symbiosis between Tuya and Roskomnadzor is the absolute bottom. I'm not buying any more cloud-dependent devices, switching everything to Zigbee. Hopefully, they won't be able to break it anytime soon..

What does Roskomnadzor have to do with it? Smart Life works fine. This is something from integration При чем тут роскомнадзор? Smart Life работает нормально. Это что то со стороны интеграции

[Preen59]

For those playing along, I switched to local Tuya, which after some messing about worked. I then switched to this fork: https://github.com/xZetsubou/hass-localtuya and that gave me full functionality of all devices again.

Local Tuya is much faster and more reliable so far. Plus the privacy benefits of local polling. I do however already hard a wireguard gateway on my network already, so no loss of access issues for me.

[Vlad939b]

The symbiosis between Tuya and Roskomnadzor is the absolute bottom. I'm not buying any more cloud-dependent devices, switching everything to Zigbee. Hopefully, they won't be able to break it anytime soon..

What does Roskomnadzor have to do with it? Smart Life works fine. This is something from integration При чем тут роскомнадзор? Smart Life работает нормально. Это что то со стороны интеграции

This is unrelated to Smart Life. The issue concerns Home Assistant's access to Tuya API endpoints hosted on Amazon Web Services infrastructure, which are being actively blocked by Roskomnadzor's TSPU (Deep Packet Inspection) systems. The operational principles of TSPU and the reason only initial packets pass through have been documented in detail elsewhere.

[anton-kozhevnikov]

The symbiosis between Tuya and Roskomnadzor is the absolute bottom. I'm not buying any more cloud-dependent devices, switching everything to Zigbee. Hopefully, they won't be able to break it anytime soon..

What does Roskomnadzor have to do with it? Smart Life works fine. This is something from integration При чем тут роскомнадзор? Smart Life работает нормально. Это что то со стороны интеграции

This is unrelated to Smart Life. The issue concerns Home Assistant's access to Tuya API endpoints hosted on Amazon Web Services infrastructure, which are being actively blocked by Roskomnadzor's TSPU (Deep Packet Inspection) systems. The operational principles of TSPU and the reason only initial packets pass through have been documented in detail elsewhere.

Then it pretty much explains why it’s not available through MTS, which are most likely to tighten filters, but is still working using Yota. Introducing vpn or switching to tuya local might do a thing if nothing else remains

[Vlad939b]

For those playing along, I switched to local Tuya, which after some messing about worked. I then switched to this fork: https://github.com/xZetsubou/hass-localtuya and that gave me full functionality of all devices again.

Local Tuya is much faster and more reliable so far. Plus the privacy benefits of local polling. I do however already hard a wireguard gateway on my network already, so no loss of access issues for me.

As observed in practice, Local Tuya also turned out to be not entirely local. For several days, devices experienced intermittent connectivity—they might work or fail unpredictably. While currently operational, they are no longer considered trustworthy. Additionally, router logs demonstrate that these devices actively establish connections to Tuya's cloud resources despite being configured for local-only operation.