Local Tuya stopped working once update core to 2025.1.0

Configuration
1

When updating core to 2025.1.0, entities from the local Tuya integration no longer work, restored to previous version and local Tuya integration works (definitely issue with updating)

3 Likes
2

I had the same issue but only for lights - ceiling fans with lights still have functional fans. I haven’t rolled back yet. Hoping there’s a solution soon!

3

I had the same issue Local Tuya and with blind covers. I found the only way around was to roll back

4

Same issue. All Tuyalocal assets disconnected. Hoping they patch soon or will roll back to see if that will do it.

5

Same as me so I decided to rollback to previous version before it’s fixed

6

Found an interim solution. Delete the entities that are unavailable (lights) and add them back via the integration, not as a light but as a switch. It then sees them and you can edit the entity to show as a light in the entity setting. This automatically updates any automations as long as you use the same name as the old light entity which was deleted.

7

Yeap. Happened to me also. lost almost all weekend , thought it was on my end the problem.

8

All my local tuya devices became unavailable and I did not update HA. my tuya devices I flashed with esp are working fine so looks like I will be flashing all of them soon. Yay

9

Hi - I have the same problem too. Localtuya has been working flawlessly and with this update it no longer functions. I really could use some help - is there a way to roll back this update? I have a backup file but I can’t find a way to upload it.

Any help is appreciated, thanks!

10

Yep, I had the same problem too. To roll back to the previous version do ha core update --version 2024.12.5

11

I had to rollback as well. Was losing my mind with this one. Hopefully it gets fixed quickly.

12

Same here, just rolled back

13

Had to roll back too.

14

Ran into this problem as well, i ended up rolling back to 2024.12.5 since i don’t really have time to experiment with this at the moment but i’ve read that the main repo of local tuya isn’t really maintained anymore.
However this fork might have the necessary workarounds for the issue:

1 Like
15

I can confirm that this workaround works flawlessly.
Just remove the integration from HACS (not from HA!! so press ignore when deleting)
And install the xZetsubou fork.
Now reboot HA done.
No reconfiguring required.

If the main repo gets fixed you can always do the same thing in reverse to go back.

4 Likes
16

I can second that this works perfectly! Very easy transition.

17

Same issue for me…had to restore.

18

Same here. Rolled back to before the 2025 update and it started working again.

19

Rolled back and subscribing to this thread.

20

I can confirm too that switching to the new fork (ignoring to avoid complete removal) solves the problem.
Thanks for the suggestion.

As a bonus I noticed already that

  • all device names when editing via the integration are now showing correctly whereas I had several showing only their cryptic virtual ID before.
  • there is an option to save entity configuration as template. Which is a feature I have been longing for, have to try it to confirm it does what I need it to.

Cheers.
BigT.

1 Like