AIRCON going unavailable randomly

[eXqusic]

HA core version

2025.1.3

Current integration version

0.6.6

Last known working integration version

Unknown.

Device type and model

Air Conditioner 00000Q18 (8)

Working mobile app

SmartHome

The detail description of bug/problem

Hi,
I have two aircons, both same brand and model. One randomly disconnects but the other does not. During this time if I check the Smarthome app, it still shows as online and can be controlled.
When its unavailable I can still ping the device successfully and it shows as connected to the wifi.

Tried the usual fixes, rebooting, reconnecting and adding back to homeassistant.

Aircon 1: 192.168.98.12
Aircon 2(With issue): 192.168.98.13

If I leave it, it will sometimes randomly reconnect but others it wont until I enable and disable the device in homeassistant multiple times or reboot it.

The logs

home-assistant_2025-01-23T06-23-26.283Z.log

[wuwentao]

1. from midea_ac_lan side, any device should be the same, if you have both AC device, one works well, and one is always not stable, I think this device should have some ERROR or exception(a brief check).
2. Smarthome app may NOT update the status quickly as it may doing cloud check and control, so you can check and confirm the control feature to trigger the status check from Smarthome app, but these control also maybe cloud based control, anyway , we can test and check it to confirm the result.
3. from your debug log, we can found this device have TCP connection ERROR, after this error exist, your device always works in an error status with auth message len 13 bytes error, and caused auth failed, so you can't control or get response from this device anymore.

[36m2025-01-23 17:21:25.937 DEBUG (bedroom) [midealocal.device] [30786325851757] Connection reset by peer�[0m
�[36m2025-01-23 17:21:25.937 DEBUG (bedroom) [midealocal.device] [30786325851757] Error while closing socket: [Errno 107] Socket not connected�[0m
�[36m2025-01-23 17:21:25.937 DEBUG (bedroom) [midealocal.device] [30786325851757] Socket is None, try to connect�[0m
�[36m2025-01-23 17:21:25.937 DEBUG (bedroom) [midealocal.device] [30786325851757] Connecting to 192.168.98.13:6444�[0m
�[36m2025-01-23 17:21:26.039 DEBUG (bedroom) [midealocal.device] [30786325851757] Connected�[0m
�[36m2025-01-23 17:21:26.039 DEBUG (bedroom) [midealocal.device] [30786325851757] Authentication handshaking�[0m
�[36m2025-01-23 17:21:26.244 DEBUG (bedroom) [midealocal.device] [30786325851757] Received auth response with 13 bytes: 83700005200f00004552524f52�[0m
�[36m2025-01-23 17:21:26.244 DEBUG (bedroom) [midealocal.device] [30786325851757] Received auth response len 13 error, bytes: 83700005200f00004552524f52�[0m
�[36m2025-01-23 17:21:26.244 DEBUG (bedroom) [midealocal.device] [30786325851757] Authentication failed�[0m
�[36m2025-01-23 17:21:26.244 DEBUG (bedroom) [midealocal.device] [30786325851757] Disabling device�[0m
�[36m2025-01-23 17:21:26.244 DEBUG (bedroom) [midealocal.device] [30786325851757] Status update: {'available': False}�[0m
�[36m2025-01-23 17:21:26.246 DEBUG (bedroom) [midealocal.device] [30786325851757] Socket closed�[0m
�[33m2025-01-23 17:21:26.246 WARNING (bedroom) [midealocal.device] [30786325851757] Unable to connect, sleep 5 seconds and retry�[0m

you can reboot this device to confirm the result. and you don't need to reboot HA.
once this device reboot, it may recovery to normal status for sometime, and once it works in error status , you still may got this error result.

so you need to do more checks with this devices, confirm it's hardware feature.
especially for the device hardware wifi module.

[eXqusic]

I have done a bit more testing with the SmartHome app and during it showing as unavailable in Homeassistant, I can still control it successfully through the smarthome app. If I turn it off and then back on in the Smarthome app, it then shows up as available again in Homeassistant.

Seeing as its still working fine with the smarthome app during it showing as unavailable in homeassistant, this would mean that the wifi module is working fine?

Do you have any other suggestions on methods I can use to check what could be causing this?
Is there a script I could run on my PC instead to manually control it so I can see if it is in an error state while showing as unavailable in Homeassistant?

[wuwentao]

sorry, I don't have any script or tool, as HA and midea_ac_lan debug log is enough for HA side software error info.
but we can't debug Midea device WIFI hardware module, and also can't debug with the device protocol, this should be the root cause.
and I don't have any good idea for it now.