Unreliable device work on latest HA CORE

[djkocurr]

The problem

After last update, my Tuya devices integrated with Home Asisstant became unreliable in HA. it’s laggy, doesn’t show right status or after turning on - showing like it’s turned on but it doesn’t for real.

What version of Home Assistant Core has the issue?

core-2024.3.3

What was the last working version of Home Assistant Core?

No response

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

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[cmgestevao]

Same problem here.
Had to restore to core-2024.3.1

[TheRaptorius]

The same problem is also for me. Devices are going unreachable for 2-3 minutes almost every hour. I've just restored 2024.3.1, but also noticed, that 2024.3.3 was already released. Anyway changelog contains only two changes, which seem to be not related to this issue (but maybe I am wrong)

[home-assistant]

Hey there @tuya, @zlinoliver, @frenck, 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)}}

[TheRaptorius]

Ok, so my devices are unavailable again. Maybe this was not the case for me.

[stasminaev]

same problem

[TheRaptorius]

After a day being back on 2024.3.1 I can confirm I still have a problem with Tuya devices being randomly unavailable. It is a pretty frequent problem, as you can see on the attached screenshot where

"bylo nedostupné" means "was unavailable"
"vypnuto" means "off" - in this case, it is a recovery state from "was unavailable"

I would say, that today, devices are unavailable even more often, than yesterday.

[kovu94]

Same here. Now I have to reload integration every time I want to switch a plug on or off. Very annoying.

Core 2024.3.3
Supervisor 2024.03.1
Operating System 12.1
Frontend 20240307.0

As I'm on holiday the next days it's not that important but I think about to replace all tuya stuff with Tasmota devices.

[mlittle408]

I am having the same problem. All my devices are periodically unavailable and, when the are available, the response very slow.

[cmgestevao]

Maybe a tuya server problem, mine are connected to this:

I have about 40 tuya devices and lattely they are working fine,

Also the "most essential" are disabled in tuya integration and controled by tuya local custom integration!

Core 2024.3.1
Supervisor 2024.03.1
Operating System 12.1
Frontend 20240307.0

[caitotheonlypotato]

My Tuya integration frequently becomes unavailable. Normally about once every 2 hours or so. I have 151 devices.
What I've had to resort to is installing a spare Zigbee switch behind a power point. I have an automation that toggles it and an input_boolean evert 2 minutes and 30 seconds, then waits 5 seconds to see if they match. If Tuya has an excessive delay or is unavailable then it reloads the integration automatically.

Unfortunately with so many devices even on an i7 laptop that runs HA it takes nearly 2 minutes for Tuya to reload.

[kovu94]

Same here. Now I have to reload integration every time I want to switch a plug on or off. Very annoying.

Core 2024.3.3 Supervisor 2024.03.1 Operating System 12.1 Frontend 20240307.0

As I'm on holiday the next days it's not that important but I think about to replace all tuya stuff with Tasmota devices.

I used my vacation last week to check all my Tuja devices. I was able to flash 22 of 30 devices with Tasmota. I sold the devices I couldn't flash and bought 8 new Tasmota sockets.
For some devices I had to solder cables and flash via a serial adapter, but this worked without any problems. For others I was able to use tuya-convert on an old rasperry pi 3b.

Now I only have 4 unimportant Tuja devices in my list, which are bearable.

I am now super happy how well tasmota performs compared to the tuya cripple software. I spent a total of three days on it, but it was worth it.

[TheRaptorius]

My situation somehow fixed itself. Now my HA is running up to date, without problems with Tuya devices. On the other hand, I was completely rebuilding my home network. I've bought 4 mesh devices and replaced the unreliable WiFi connection from my Turris Omnia router (I can warmly recommend ASUS ZenWifi XD5/XD6 devices - even in AP mode they are offering so many options to set, to difference with for example Mercusys systems). Now, the mesh is completely doing wireless connection in AP mode, and Omnia is taking care of everything else. I was facing many problems while pairing some of my Tuya devices to the new system (even though I have the same SSIDs and passwords). Some of my devices refused to connect to wireless, and for two days I was messing with all of the WiFi settings, starting with disabling WiFi6 and ending with advanced settings. I was even reconfiguring Tuya Developers cloud. Nothing was working, until I've done one easy thing. With the default settings without doing any IoT optimizations, I've changed SSID to some simple one, paired all of the devices to the new SSID (surprisingly after two previous days it was working like a charm), and then changed it back to my SSID, reset devices, and after this step devices can be paired to my old SSID without problems.

During this journey, I found so many people with similar problems, not able to solve them, that I've decided to write down my notes, and put it also here, if anyone is facing similar problems:

TUYA Devices & Problems

Tuya knowledge base:
Reset Types (many of us is using only EZ mode, and AP mode was not described in the manual for my device for example, so I've decided to describe it here):
EZ mode - hold the reset button for 10 seconds, the LED will start to blink quickly. This method is usable for automatic pairing with device discovery.
AP mode - hold the reset button for 10 seconds. after the LED starts blinking quickly, press & hold the reset button hold the next 10 seconds. The LED will blink slowly, and the Tuya device will create an AP named SmartLife_xxx, or SL_xxx. Now you should start Manual pairing, but first of all, connect to the standard 2.4GHz WiFi AP. Then during the pairing process, change WiFi to SmartLife when requested. During manual pairing, ignore all Pop-up created by auto-discovery

How to reset Tuya device correctly:

• from my discovery, resetting the Tuya device once, or twice is not enough sometimes. Reset the device 5 times in a row to be sure, that the device is reset properly

After changing the WiFi router:

• even when you keep the same SSID & password, the device may not be able to connect, even when changing various WiFi settings (e.g. b/g/n mode, beamforming, turning off WiFi 6, ...)
• even when you've already reset the device XX times, the Tuya device somehow remembers network info and is not able to connect to a new device with the old SSID & password
• What showed, as a solution for me is to
  -- temporarily change SSID to something very simple, without capitals, numbers, or special characters (to avoid issues with unsupported characters in SSID). For example: "helloworld"
  -- reset Tuya device 5 times in a row (without any pairing tries during the reset)
  -- connect the device in the Tuya Smart mobile app to WiFi with temp SSID
  -- device will probably connect without a problem
  -- then change SSID back to the old one
  -- reset Tuya device 5 times as before
  -- connect the device to your standard SSID
  -- Tuya device should connect without problem.