Is anyone else having a problem with Tuya?

For the moment that the problem is there (for over a month now I guess) is there no local script that can be applied to reload all Tuya appliances in 1 go maybe every 30 minutes or so?
I think I have seen a script for which you have to reload every singe device which is clearly a lot of work for some people. If you can do it with 1 mouse click on the integrations page then why should it not work with a simple script?

Any solution? I have the same behavior.

sorry i was late to the party .

What problem everyone is talking about ? using localtuya or TuyaV2 ?

Tuya integration in 2021.12 stops working after 1 hour. Reload makes it working again for 1 hour. The old integration works well.

1 Like

same here , workaround is localtuya

you can create an automation:

In configuration.yaml add (or confirm it contains):

system_log:
  fire_event: true

In automations.yaml, add:

- id: "TuyaIOT"
  alias: "TuyaIOT Restart"
  trigger:
  - platform: event
    event_type: system_log_event
    event_data:
      level: ERROR
      name: tuya_iot
  condition:
  - condition: template
    value_template: >-
      {{ "error while get mqtt config" in trigger.event.data.message[0] }}
  action:
  - service: homeassistant.reload_config_entry
    data:
      entity_id:
        - switch.living_room_lamp

Important! Change switch.living_room_lamp to the id of one of your system’s own Tuya entities.

Works like a charm by resetting Tuya when error while get mqtt config occurs.

3 Likes

Is this not fixed in 2021.12.6 from Update tuya-iot-py-sdk to 0.6.6 by frenck · Pull Request #62858 · home-assistant/core · GitHub ?

I’m facing issue with Local Tuya

I’ve defined two smart plugs yesterday and they were working fine.
Then I’ve unplugged both from electricity and this morning I’ve plugged again, but both are in an unknown state in HA.

They work fine from Smart Life app and I can see online from the IOT Tuya webpage.

I’ve tried also the automation in this thread, but both are still not working.

What else can I check?

Thanks

Its really strange what is going on with Tuya , I faced the same issue you just mentioned and it was only fixed
once I rebooted the router !!! Please don’t reboot your router but this gives you an indication that the connectivity is an issue with tuya at the moment , You could try again to restart HA and if you do not have a lot of devices then reconfigure them again . All of this is really just a trail and error at the moment and I could not see a fits all solution

Wish you all the best

I’ve already restarted HA more than 1 time.
I can try to reconfigure them, because I’ve just two (I just started using Local Tuya and devices smartplugs that cannot be modified with Tuya-convert to install Tasmota).
I will try tomorrow.
Thanks

Was having the same behavior and fixed it…so far. Went into Tuya IoT and created a new Cloud Project. I was very careful to select communication API Authorizations during creation. I have not found where they are visible after the project is created. In any event, selected Device Status Communication and added Location Service just to keep the communication going. So far it corrected this concern. The switch in HA follows the switch now. I’ll update if that changes.

It worked for several hours and then stopped working.

1 Like

Exactly the same problem as in the topic here.
Tuya light bulb works as supposed in Tuya mobile app and in Google Home app, but weird behavior appears in both Home Assistant environments - one in Virtual Box (old but updated instalation on Debian 10 Buster Lite) and the other one on RPi4 freshly install Debian 11 Bullseye, both installed as Home Assistant Supervised.
Looks like poor communication HA with Tuya integration.
P.S. I`m planing to test tuyalocal soon.

Armi, same issue here. Last year in October and November this happened and now it is happening again.
Last couple of weeks at night I can sometimes switch stuff on but after a couple of seconds it goes off on home assistant but it is actually switched on.
Now again I just checked, at 11am what happened to some really power hungry things I switched on last night and it showed that they were still switched on on the dashboard. If it really was the case my electric bill would not be a laughing matter. (as it already is way to high)
Every time I have to reboot the home assistant on my pi4 here. It has become so ridiculous that I am about to throw it all out. Oww btw it all seems to work on the ‘normal’ Tuya application.
The original switches in one room from my house build in 1956 still work without a glitch.

I`ve solved my problem by moving to Local Tuya addon. No more problems.

Armi, where can a relative newbie like me find current instructions on how to install Local Tuya in Home Assistant? I’ve spent days following directions on one webpage or another until I find something has changed. Thanks for your reply. Regards

I have the same problem, but found a workaround: Disable IPv6 in Supervisor → Host → Ip-Adress.
When setting the logger for tuya/tuya_iot to DEBUG you will notice, that there is often missing the PUBLISH answer from tuya after a POST of the switch-command. When IPv6 is disabled this happens nearly never.

3 Likes

This worked for a bit but then stopped again

1 Like

Also worked for me for some time and now it does not.