forked from rospogrigio/localtuya
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: No a need to stop heartbeat due to one timeout #236
Labels
bug
Something isn't working
Comments
This has been changed and handled, but I haven't pushed it yet. |
Just in case, it is worth to make a similar change in |
xZetsubou
added
the
master/next-release
Fixed in master branch, Will be ready in the next release
label
May 18, 2024
github-actions
bot
added
stale
and removed
master/next-release
Fixed in master branch, Will be ready in the next release
stale
labels
May 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LocalTuya Version
2024.5.0b1
Home Assistant Version
2024.5.3
Environment
What happened?
I suggest to replace these lines:
hass-localtuya/custom_components/localtuya/core/pytuya/__init__.py
Lines 920 to 926 in fcc6911
with
This is running in my HA server. I didn't see more than 1 time of failures in a row. With the version with the sleep after the query (i.e. no a delay after the timeout), once I saw 3 times, and never more.
I've changed the order of lines 922 and 923 based on your suggestion in #227, and to make a delay after a timeout with minimum changes.
Steps to reproduce.
Don't know.
Relevant log output
2024-05-16 09:55:57.426 WARNING (MainThread) [custom_components.localtuya.core.pytuya] [bf8...m91] Sub-devices heartbeat failed due to timeout 1 times
Diagnostics information.
No response
The text was updated successfully, but these errors were encountered: