Closed elninosi closed 1 year ago
Same here, started some time ago.
I have six smart plugs and two thermostats, all of them have now state "unavailable". State returns to normal to short time, if I changing state of plug by using SmartLife application. But after short time state goes to unavailable too
Cloud tuya integration works normally...
I also have the same issue
i also have the same issue, the device randomly changes status to unknown and then to unavailable, restarting temporally fix the issue
I think there may be a limit in the number of threads Home Assistant is letting an integration start. Because the underlying tinytuya library is not async, this integration starts a thread per device to receive updates asynchronously from the device.
@make-all I only have 1 device, the pool heatpump. Can we activate any additional logging ?
Is any suggestions about this bug? I have stopped all automations... :(
I see this as well, it only started happening recently (last few days), likely related to upgrading tuya-local to latest.
I only have a single pool heater connected and HA shows it as offline - using the Tuya app (Cloud) to change the pool heater state makes the entity in HA come online again but then shortly after it will go offline again.
I have the same issue with just one pool heat pump. @adamkoch which version you have used before (which was stable for you)? I have switched from local tuya to tuya local due to the device is supported out of the box but if it is not working reliable it will not be that useful. Is there any idea what we can try to log? I'm experiencing this behavior just after a while. The wifi connection to the pump is not the best so my guess is, that it has something to do with a reconnect of the pump. Perhaps the loss of connection is bringing the integration somehow to the limit?
If your protocol version is set to auto, you will get faster recovery times after a network disconnection if you set the protocol version to the version actually used by your device. If you don't know what that is, download Diagnostics for the device when it is working, and the version detected will be in the diagnostics file.
I have the same issue with just one pool heat pump. @adamkoch which version you have used before (which was stable for you)?
It may have been a red herring. I had never seen the device go "unavailable" for 1+ years and then I upgraded to the latest version and it went unavailable constantly all day. However, for whatever reason, it seems to be stable again today and no longer going offline. I will report back in case I see more issues going forward.
Same problem here. Tonight all my 16 devices went unavailable :( Only restarting HA did bring them back to live :(
If your protocol version is set to auto, you will get faster recovery times after a network disconnection if you set the protocol version to the version actually used by your device. If you don't know what that is, download Diagnostics for the device when it is working, and the version detected will be in the diagnostics file.
I've tried to set protocol to version 3.3 and this is much more stable. I still sometimes get an unavailable state, but it comes back very quick...
I'm new to HA and started to use tuya-local a few weeks ago and already "became" with this behave, which is very annoying, my automation fails constantly. However, my devices are set with protocol = auto. Changing to the correct protocol and crossing my fingers to reduce this behavior.
To identify the correctly version, I'm using tinytuya , which works very well.
I noticed this as well, restarting home assistant seems to fix it until it happens again after a period of time.
@make-all , just a note.
I'm trying since yesterday to change thru the interface the protocol version of my devices. They are working and available, however, when I go to the configuration and change the protocol from "auto" to the correct version they give an error that aren't able to connect, the problem should be interment... I restarted my HA, my S.O. and the problem persists... To force the protocol I was forced to shutdown my HA and change manually the core.config_entries file.
Same issue here, Slowly, all my devices becomes "unavailable", I might corelate this behavior with the upgrade of HA to 2023.5
@georgef333 I have the issue for home assistant 2023.4.6 as well. Before 2023.4 I have not used the integration so I cannot say to much.
The workaround is as @make-all suggested, figure out the protocol and configure it directly, haven't had a device going unavailable in over a week.
The workaround is as @make-all suggested, figure out the protocol and configure it directly, haven't had a device going unavailable in over a week.
Can confirm my devices aren't going offline with this
Confirm working after updating tinytuya to 1.12.7, Thanks!
Confirm working after updating tinytuya to 1.12.7, Thanks!
Hallo how to uodate tintuya? Whats tintuya?
If you use HACS, tinytuya is automatically updated to match the version specified in the manifest when you upgrade to the latest version of this integration.
If you install manually, you should understand how to also install the dependency libraries.
Hi, I'm using the last version of Tuya Local, the last HA, devices set with the IP and Protocol on their settings, and still with considerable frequency devices getting unavailable at the point to fail few automation. Happens again last night when a smart socket became unavailable, however, I was able to turn it on thru SmartLive without issue at the same moment.
@make-all, please, can you give some tip on how to enable logs or how I could debug this situation to try to identify where is the problem?
Just to illustrate, this occur at this dawn when the heater should turn on and didn't. Then I turned it on manually thru Smart Life app because appear as unavailable at HA.
The logger documentation is here: https://www.home-assistant.io/integrations/logger/
Tuya local is under custom_components.tuya_local
, for communication issues, probably just enabling debug on custom_components.tuya_local.device
is enough. The low level communication is handled by tinytuya
, and you should be able to enable debug logging for that also if you cannot spot anything at the tuya-local level.
This issue is closed, but the problem still exists. Why is this closed? I do not find duplicate etc.
Please open and fix.
I noticed that my Tuya devices go into "unavailable" state. After reloading, integration is restored for some period.
Diagnostic for device that goes to unavailable state most often: