Certain devices go unavailable and only come back after restarting HA

[felipecrs]

Description

Tuya Local improved so much recently in this regard (#1804). I am very grateful for this.

But I found a situation today where my Tuya Local device went unavailable and while it was working from the official Tuya integration:

To be clear, the device from the official Tuya integration was disabled when such issue happened (I keep it disabled to avoid potential conflicts). I only enabled after noticing the issue to check if the device was really offline or not.

I tried reloading the entry and these were the logs produced:

tuya_local_debug_logs.txt

After reloading the entry, nothing happened. The device kept unavailable.

I did a HA restart, and then it came back right after the restart.

Steps to reproduce

Sorry, I don't know. I hope the logs I captured are useful.

Expected behaviour

The device should have functioned, as it was functioning through the official Tuya integration.

Additional context

No response

Confirmation

• I am sure this is a bug or improvement, that is well enough described that it can be implemented.

• This report is for tuya-local, not for localtuya.

• If this is for a specific device, the device config is mentioned above, or diagnostics are included.

• Log messages or diagnostics relevant to the issue are included.

• This is not requesting addition of a new device.

[emanuelegreco29]

I'm having the same issue with some LEDs. I have thermostats and other lights, all working flawlessly. However one LED strip keeps becoming "unavailable", I even tried giving it a static address but nothing changed. Any fix or workaround?

[MrUndefined09]

i have some issue.

[felipecrs]

@emanuelegreco29, @MrUndefined09, in your case did restarting Home Assistant help too?

[MrUndefined09]

yes, if i do restart, my device come online. i have same issue with you.

[emanuelegreco29]

@emanuelegreco29, @MrUndefined09, in your case did restarting Home Assistant help too?

Restarting the whole Home Assistant yes, reloading the LED configuration does not fix it. Removing the device and re-adding it fixes it. Restarting the whole integration (not HASS) does NOT fix it.

EDIT: not always restarting Home Assistant fixes it, whereas a full reboot of the VM does it.

[adamkoch]

Running into same issue, seems to be a recent thing (past week or two), I can't remember if/when I upgraded tuya_local, but my current version is 2025.2.2.

As per others, reloading the integration doesn't help, but restarting HA does fix it. The Tuya app still works and i can ping and see the device connected fine to my network.

The error in logs is:
Failed to fetch device status for Madimack Pool Heat Pump.

[MickPBduece]

It might be helpful to check the Tuya app and see if the device can be controlled from there and for my own system, I can reconnect devices to the network thru the router interface. Restarting the router might be a good alternative to that.

I have the same experience for just one bulb. My next step is to try changing the location of the troublesome bulb with a location that is working corrrectly or submitting a warranty claim for it

[felipecrs]

In my case the device is fully controllable through both the Tuya App and the Tuya Official integration while it's unavailable in Tuya Local.

I highly recommend you open a separate issue if that's not your case, @MickPBduece.