设备通电后首次添加可以使用，一旦重新加载或重启home assistant后就不可用 - Device rejects connections

[without-yy]

出现不可用后，删除设备重新加载也不行，必须设备断电并重新添加

config_entry-midea_ac-01JR23S760Z2VSD6472K6MBBWJ.json

home-assistant_midea_ac_2025-04-05T04-39-22.141Z.log

[without-yy]

下面是home assistant中显示不可用时执行的日志

msmart-ng discover --debug
DEBUG:asyncio:Using selector: KqueueSelector
INFO:msmart.cli:Discovering all devices on local network.
DEBUG:msmart.discover:Discovery sent to 255.255.255.255:6445.
DEBUG:msmart.discover:Discovery sent to 255.255.255.255:20086.
DEBUG:msmart.discover:Waiting 5 seconds for responses...
DEBUG:msmart.discover:Discovery response from 192.168.10.245: 5a5a0111a8007a800000000000000000000000004bf4000000320000000000000000000000000000b8ea842ef77000812f844c504d150d0c3ea60914b3b21560276a01747bad86320a7851d7fcedf09d1a566362aa23170c2de0033610372eff681bd06b41e1e856deb4d25414d7e5b68ee8369523d57203610c9402c97fc0e05d1bd9a530b1c22706c416020931f48926620dfe95e23111b96e5b0db232aa8da5b30dd984c7211f
DEBUG:msmart.discover:Decrypted data from 192.168.10.245: f50aa8c02c19000030303030444231313133383131313434333137413235323130343936303030300d6d696465615f64625f303439360000000001000000000000000000db00323100000000345bbbbfbcca0570040420260103000000000000000000000000000000000000000000
ERROR:msmart.discover:Device class Device has not implemented refresh().
DEBUG:msmart.discover:Discovery response from 192.168.10.214: 5a5a0111a8007a8000000000000000000000000065850100000800000000000000000000000000001212471ef2b77c51c9cf2c430a82c42097ca122ea2ff782fa9a347c1ed60de1d7e948edcc9d089920433d9d0d887a8bbbb271ad2137e37fccd8b7e436836cf1f3e85334ea195502ba5d73ed7244fe3f5eb70e3e508ad4f89a49982fd54f80e0034051eeb93982aa88e7775c716f3a2b8b7c3a6b9697ba27da43c220793c34697
DEBUG:msmart.discover:Decrypted data from 192.168.10.214: d60aa8c02c19000030303030303032313132323031313832353733323030323530353331303030300d6d696465615f61635f303533310000000001000000040000000000ac00000000000000382187c728b201080001021601030000000000000000000000000000000000000000
DEBUG:msmart.base_device:Sending command to 192.168.10.214:6444: aa21ac00000000000003418100ff03ff0002000000000000000000000000030169fe
INFO:msmart.lan:Creating new connection to 192.168.10.214:6444.
DEBUG:msmart.discover:Discovery response from 192.168.10.103: 5a5a011178007a80000000000000000000000000ea220b0000400000000000000000000001000000911c22c5bd24e59b36bf6f4c4b8a79005fad6865d79f521a75ffd98e511143056d4235a42fb09f9ab5134658d74dcc87a23ed04892395069e84a02964ca9a5cb658a9f553fd97baa65c36525278570ae
DEBUG:msmart.discover:Decrypted data from 192.168.10.103: 670aa8c02c19000030303030303032313132323235303736333639323830323831303235303030300d6d696465615f61635f31303235
DEBUG:msmart.base_device:Sending command to 192.168.10.103:6444: aa21ac00000000000003418100ff03ff000200000000000000000000000003028bdb
INFO:msmart.lan:Creating new connection to 192.168.10.103:6444.
DEBUG:msmart.lan:Connected to 192.168.10.103:6444.
DEBUG:msmart.lan:Sending packet to 192.168.10.103:6444: 5a5a01116800200000000000571e350405041914ea220b000040000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b372946460bceafc6eae86e4200896522a2f2c998033e1118f4064e3bd2c45af985f098d320b19ad0a828992da924158e1
DEBUG:msmart.lan:Sending data to 192.168.10.103:6444: 5a5a01116800200000000000571e350405041914ea220b000040000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b372946460bceafc6eae86e4200896522a2f2c998033e1118f4064e3bd2c45af985f098d320b19ad0a828992da924158e1
DEBUG:msmart.lan:Received data from 192.168.10.103:6444: 5a5a011168002080000000000000000000000000ea220b000040000000000000000000000100000087d5fe6c12997a1582790f215b9e0e70ce02f0c7b52f2d9435031c587c1083bb5553abe16fff1908d6612f38cf7b33a4b233a1cabe7f7b8e9d9cdcfb47abd5cc
DEBUG:msmart.lan:Received packet from 192.168.10.103:6444: 5a5a011168002080000000000000000000000000ea220b000040000000000000000000000100000087d5fe6c12997a1582790f215b9e0e70ce02f0c7b52f2d9435031c587c1083bb5553abe16fff1908d6612f38cf7b33a4b233a1cabe7f7b8e9d9cdcfb47abd5cc
DEBUG:msmart.lan:Received response from 192.168.10.103:6444: aa21ac00000000000203c00048667f7f00000000005aff0c0000000000800002e7f4
DEBUG:msmart.base_device:Response from 192.168.10.103:6444 in 1.220000 seconds.
DEBUG:msmart.device.AC.device:State response payload from device 70368744907498: c00048667f7f00000000005aff0c0000000000800002
DEBUG:msmart.discover:Discovered 3 devices.
WARNING:msmart.base_device:Network timeout 192.168.10.214:6444: Connect timeout.
WARNING:msmart.base_device:No response from 192.168.10.214:6444 in 5.000000 seconds.
INFO:msmart.cli:Found 3 devices.
INFO:msmart.cli:Found device:
{'ip': '192.168.10.214', 'port': 6444, 'id': 8796093121893, 'online': False, 'supported': False, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'midea_ac_0531', 'sn': '00000021122011825732002505310000', 'key': None, 'token': None}
INFO:msmart.cli:Found device:
{'ip': '192.168.10.245', 'port': 6444, 'id': 54975581451339, 'online': False, 'supported': False, 'type': 219, 'name': 'midea_db_0496', 'sn': '0000DB1113811144317A252104960000', 'key': None, 'token': None}
INFO:msmart.cli:Found device:
{'ip': '192.168.10.103', 'port': 6444, 'id': 70368744907498, 'online': True, 'supported': True, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'midea_ac_1025', 'sn': '00000021122250763692802810250000', 'key': None, 'token': None}

[mill1000]

Hi.

The HA log shows the devices at 192.168.10.214 and 192.168.10.103 are OK. Whats the problem?

[without-yy]

@mill1000
The malfunctioning AC has the IP address 192.168.10.214. After a power cycle, it can be controlled by the Midea Smart AC integration. However, once I click "Reload" in Home Assistant, the AC becomes unavailable. At that point, it cannot be controlled anymore and requires another power cycle to recover. Even removing and re-adding the device does not help when it's in this unavailable state.

2025-04-08.11.28.02.mp4

[mill1000]

Thanks for the video.

Could you provide another log while you reload the integration? Wait at least 30 seconds after reloading before grabbing them.

Your last log terminates before the integration had a chance to query the AC for its state.

[without-yy]

@mill1000
Thanks for your reply.

The following log was captured after powering on the device and adding it to Home Assistant. The device initially appeared as available on the interface. After waiting for 10 minutes, I reloaded the integration. Following the reload, I waited another 5 minutes, but the device remained unavailable on the interface.

home-assistant_midea_ac_2025-04-10T02-15-05.274Z.log

config_entry-midea_ac-01JREPTDSMEJW9GHTE63AXAHE3.json

[mill1000]

Thanks. The logs are perfect.

I wonder if your device (192.168.10.214) has a hard limit on the number of connections it accepts. After the reload, the device rejects all attempt to establish a new connection.

Maybe because the code isn't properly closing the connection. Have to ponder this one.

[mill1000]

The latest release has some updates to the network handling. It should be better about closing connections and "backing off" when a device actively rejects the connection. Maybe it will help fix your issue.