[Bug]: Tuya version 3.5 becoming unavailable in Home Assistant

[jackmtl71]

LocalTuya Version

2024.7.0

Home Assistant Version

2024.8.2

Environment

• Does the device work using the Home Assistant Tuya Cloud component?
• Is this device connected to another local integration, including Home Assistant and any other tools?
• The devices are within the same HA subnet, and they get discovered automatically when I add them

What happened?

I have several devices detected as Ceiling Light+, some of them are tuya firmware 3.4 and some 3.5 (same make and model but bought separately) The 3.4 lights behave perfectly, but the 3.5 lights become unavailable after a while and stay that way until powered off and on again.
however, they are still controlable by the SmartLife App, but NOT by the tuya cloud HA integration.

I have searched and tried many solutions, reloading HA, pinging the lights, etc with no success.

They get discovered and configured no problem, just wont stay connected.

The debug logs have this line every 8 seconds:

2024-08-22 22:12:40.030 DEBUG (MainThread) [custom_components.localtuya.coordinator] [eb7...hda - Studio2] Trying to connect to: 192.168.200.99...

and same for all of the 3.5 ceiling lights.

Additional fun fact: the light does not ping, even when it is on, but the 3.4 devices do. Is there somethign inherent to this version that makes them lose connection to HA?

Steps to reproduce.

power off device, power on device, it gets detected by HA and can be controlled, after an undetermined period of time, ALL of the 3.5 lights become unavailable at the SAME time.

see example availability below

Relevant log output

No response

Diagnostics information.

localtuya-67374c222746252ba93660db22971075-Studio2-8c6b8143cda071421339525aeda1f980.json

[xZetsubou]

This is the same behavior of #299 #329

Out of curiosity what If you test with 1 or 2 devices "disable the others" to be fair this also happened to me before I don't know what actually trigger it so I'm still looking for a way what may causing it. In #234 it mentioned that making multi commands trigger it can you test it if it's the same behavior?

[jackmtl71]

I have never used "all lights off/on" bulk like commands, the lights are managed in a group.

For example, in the graph I showed, I turned the lights off when going to bed and they went unavailable, all at the same time (which is that part that is odd), an hour or 2 later.

I do notice that the lights that are unavailable to Home assistant cannot be pinged, but when they are, they are pingable.

However, even in that state that they cannot be pinged, the smartlife app can wake them up and control them after a few seconds.

Wonder how I could capture this behavior.

[xZetsubou]

I have never used "all lights off/on" bulk like commands, the lights are managed in a group.

I know I just asked to test if this one of the reason may causes this.

I do notice that the lights that are unavailable to Home assistant cannot be pinged, but when they are, they are pingable

If the devices went to that weird state yeah I have no way to reach them which is makes me wondering if this behaviors caused by the device it self or localtuya.

the smartlife app can wake them up and control them after a few seconds

Smart life communicate with the device through internet not locally so even if the device reject and "local" connection it still connected to network. one more thing you may want to test "network signal strength" from Smart life as well it probably would failed.

[bobloadmire]

I have never used "all lights off/on" bulk like commands, the lights are managed in a group.

I know I just asked to test if this one of the reason may causes this.

I do notice that the lights that are unavailable to Home assistant cannot be pinged, but when they are, they are pingable

If the devices went to that weird state yeah I have no way to reach them which is makes me wondering if this behaviors caused by the device it self or localtuya.

the smartlife app can wake them up and control them after a few seconds

Smart life communicate with the device through internet not locally so even if the device reject and "local" connection it still connected to network. one more thing you may want to test "network signal strength" from Smart life as well it probably would failed.

Yes I tried the network test from the app on a Wi-Fi light switch that fell off local tuya, and it did fail. Still respond in the app oddly though

[bobloadmire]

Updated today, still same issue unfortunately

[xZetsubou]

Updated today, still same issue unfortunately

Any changes after 2024.9.0 update? also can you share your entry diagnostics

note: by changes I means it no longer happens after 1st reboot for the device and success connection.

[Leo83-hash]

Hello xZetsubou

First of all, thank you for your awesome work, I realy apreciate it.

I've been watching this topic, as I have a similar problem, some devices start to ramdomly become unavailable. Is this the same problem?

localtuya-01J6Q64YXDR3H3Y6D9BC60JEJX-Sala de TV C-d3e0a81498537f56299e3eac630f463e.json