-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Device unavailable - does not respond to energy usage requests #273
Comments
Hi, could you provide full debug logs for a timespan of about 5 minutes? The capability request failing shouldn't be a fatal event so something else must be wrong. |
msmart_logs.zip Let me know if I can help in anything else. |
Hi @mill1000. You're totally right. Disabling the power sensor fixed the constant disconnection... However, testing over the time I still see some random disconnection of both devices (as the classical report you already now, where there is a temp disconnection every 3-4 hours). I tried several different connection time outs like 45, 60, 90, 120 and the issue is still there. If I start a debug collecting for a few hours until I catch one of those issues, are you willing to check it ? |
Absolutely, I'd be glad to take a look |
Hey @mill1000 sorry for the late, it's being a though week over here. So, I was finally able to catch one of those disconnection events and contrast them with debug information. I'm attaching here the screenshot where we see the device going unavailable at 00:17:50, and the debug information for exactly that time frame. |
Could you provide the full debug log and not the trimmed version? |
Sure, here is the complete file |
Hello,
first of all, thanks for your great work.
I've two Midea AC, one of them works correctly, and for the other it works for "seconds" before it goes unavailable, I tried all the suggestions about adjusting the connection time, without any luck.
So, when doing some in deep check in log files I found this:
As soon as the Checksum error comes for the Capabilities Query, the device goes unavailable. A simple "integration reload" triggers it back to normal for a few seconds again... and so far, so on.
Checking more in deep in HA logs I also figured that right after this checksum error, a connection error to the device is shown:
Network timeout 10.100.200.222:6444: No response from host.
No response from 10.100.200.222:6444 in 6.010000 seconds.
No response from 10.100.200.222:6444 in 6.000000 seconds.
Network timeout 10.100.200.222:6444: Read cancelled.
No response from 10.100.200.222:6444 in 2.450000 seconds.
Just to be clear, there is no network issue to that IP address, and indeed other integrations do work with it.
Do you have any idea about how to fix this? let me know if you need any extra information from my side.
Thanks
The text was updated successfully, but these errors were encountered: