Midea AC regularly becomes unavailable

[lumbarthought]

First off, love the integration. Controls my AC well and reports good info....when it's connected. It regularly goes unavailable for various periods of time. I've tried max connect times of 90, 60, and 45 sec. I could try shorted but it seems like the problem is it can't authenticate with the AC for many tries....until it does, and then its good for a while....until it's not.

Any thoughts?

home-assistant_2025-08-01T01-01-32.251Z.log

config_entry-midea_ac-01K1CGEH2NE36EF8MCBHA9MQEA.json

[mill1000]

Thanks for the logs.

I wonder if part of the problem is the network code doesn't back off after an authentication failure. Your device is resetting the connection ([Errno 104] Connection reset by peer) but we try again after a short timeout (multiple times).

Maybe in this situation I need to disconnect and back off until the next refresh interval.

Could you try keeping debug logging on and catching a situation when it goes from working to failing authentication?

[lumbarthought]

This has some short disconnects but not any of the longer ones I see sometimes. I'll keep debugging on for a while and see what it catches.

For what it worth, any time I make a change in the integration settings – changing the max connection time, for example – it fails to authenticate for some period of time. Maybe that's related.

home-assistant_2025-08-01T18-21-10.733Z.log

[mill1000]

For what it worth, any time I make a change in the integration settings – changing the max connection time, for example – it fails to authenticate for some period of time. Maybe that's related.

Not too surprising. Adjusting the options causes the integration to reload, which causes it to authenticate.

I wonder if your device has stringent authentication limits. E.g. can't reauth more within X hours. If so maybe we could cache the auth data and try to reuse it.

[MikeLDPT]

Hi,

I've just started using this integration for 3 midea units recently installed. It was excellent until this morning at just after 05:10 when all three units seemed to become unavailable. I wouldn't know if this is a frequent event or not as I have not noticed a disconnection issue before that has lasted long enough for me to notice.

Interestingly 1 unit recovered almost immediately and is still contactable using HA.

The other 2 units are rejecting connection.

Maybe this will prove to be slightly different to the connection issue noted .... but I'm not able to tell.

What I have noticed (and I should qualify that I am not very familar with the "under the bonnet" area of HA) is that the IP addresses allocated by the router for the two ACs that are now not available seem to be different to the ones that the MIDEA AC Integration is using in its failing attempts to connect. The one that recovered, remains with an IP address where the router allocated IP does match the one used by this integration. I am wondering if the router reset in some way and on restart it allocated two AC units with different IPs and one with the same IP.

Is there a way for the locally allocated IP Address to be "refreshed" by this integration in these situations, as perhaps that might resolve this issue and match them up again? I can't see a way to manually amend the IP address assumed by the Midea AC integration... is there one?

Perhaps HA users need to set the the IP addresses as static in the router once allocated to an installed AC, to make sure that it cannot be altered, and so the Midea AC integration will then more likely have a consistent IP address?

Hopefully this makes some sense and is a useful contribution to this discussion.
Thanks.

[MikeLDPT]

Just to add.... I have now changed the Router allocated IPs back to the ones that were stored in the Midea AC integration at installation and made them static. Rebooted the router, and powered off/on some ACs to ensure new IPs were taken up. Checked using "Ping" that they were back in action. It is now all working as it was for both Smarthome and HA seeing the 3 ACs.
I should mention that the transition wasn't entirely smooth: I had to re-add one of the ACs back into the Smarthome app as when I changed the IPs, for some reason, that one became unavailable in Smarthome.

[mill1000]

I just added support for reconfiguring the integration, which should help if IP addresses change.

I haven't released it yet though.

[lumbarthought]

Checking back in since there's action here. Since I set 45 sec reconnection time, set static ips on the devices, and reinstalled the integration and reconfigured, it's all been solid. My only gripe now is that one of my two ACs is returning all power sensors as unavailable. Works fine in the smarthome app. But I haven't investigated it much so maybe simple reconfig will fix it.

…

On Wed, Aug 27, 2025 at 6:34 PM Tucker Kern ***@***.***> wrote: *mill1000* left a comment (mill1000/midea-ac-py#366) <#366 (comment)> I just added support for reconfiguring the integration, which should help if IP addresses change. I haven't released it yet though. — Reply to this email directly, view it on GitHub <#366 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGNKX4ZWDBAB5C3TR3D3BWL3PYW6BAVCNFSM6AAAAACC3M6WSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMRZHE2DKNBZHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mill1000]

My only gripe now is that one of my two ACs is returning all power sensors as unavailable.

Did they work in HA at one point and then stop?

[otiskujawa]

Similar issue,
2 AC units
All of them constantly go unavailable and then go back online.
Reserved IP (47,48)

This error originated from a custom integration.

Logger: msmart.base_device
Source: custom_components/midea_ac/coordinator.py:42
integration: Midea Smart AC (documentation, issues)
First occurred: October 26, 2025 at 19:22:19 (13217 occurrences)
Last logged: 13:21:42

Network error 192.168.0.48:6444: Error packet received.
Network error 192.168.0.47:6444: Transport is closing or closed.
Network error 192.168.0.48:6444: Transport is closing or closed.
Network timeout 192.168.0.47:6444: No response from host.
No response from 192.168.0.47:6444 in 6.000000 seconds.

home-assistant_2025-11-02T12-18-42.485Z.log

Installation method Home Assistant Supervised
Core 2025.10.4
Supervisor 2025.10.0
Frontend 20251001.4

State history for one with IP 192.168.0.47
history.csv

Integration version 2025.9.1