midea-ac-py icon indicating copy to clipboard operation
midea-ac-py copied to clipboard
verified publisher icon mill1000

Support 0xCC device type - CRC/Checksum Failures on Midea Multi-Head System — All Units Unresponsive

Open 11sas11 opened this issue 3 months ago • 16 comments

Hi team, I'm attempting to integrate a Midea multi-head split system (4 indoor units) using the latest midea-ac-py with msmart-ng. All four units are detected, but every payload fails CRC and checksum validation, and capabilities cannot be queried. Environment:

  • Home Assistant 2025.8.x (Core + Supervisor)
  • Integration: Midea Smart AC via HACS
  • Backend: msmart-ng
  • Location: Australia Errors: Payload failed CRC and checksum. Received: 0xFF, Expected: [varies] Failed to query capabilities from device [ID]

Device IDs:

  • 151732606461936
  • 151732606461934
  • 150633094836508
  • 151732606461938 Notes:
  • All units are part of a single outdoor system. Would love to help get multi-head support added. Let me know what else I can provide. Log below Thanks! Simon

This error originated from a custom integration.

Logger: msmart.device.AC.device Source: custom_components/midea_ac/coordinator.py:42 integration: Midea Smart AC (documentation, issues) First occurred: 19:59:45 (28 occurrences) Last logged: 20:01:18

Payload '01fe00000043005000728c8000f900728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0xF3 or 0x96. Payload '01fe00000043005001728c7b011800728c728c7b7b00010141ff010203000603010000000300000001030103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0x58 or 0x7E. Payload '01fe00000043005000728c8000f800728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0x25 or 0x97. Payload '01fe00000043005000728c8000ec00728c728c808000010141ff010203000603010007000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0x3C or 0x9C. Payload '01fe00000043005000728c8000e300728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0x75 or 0xAC.

11sas11 avatar Aug 31 '25 10:08 11sas11

Okay, lets see if we can figure out what's going on.

Can you enable debug logging and reload the integration? That will give some additional information I can use.

How comfortable are you on the terminal? I might need you to run some msmart-ng commands to test things.

mill1000 avatar Aug 31 '25 14:08 mill1000

I thought I had debug logging going, so please excuse my ignorance.

I put :

logger: default: info logs: custom_components.midea_ac: debug msmart: debug

into my configuration.yaml

I am happy in the terminal so let me know what you want me to do.

11sas11 avatar Sep 01 '25 00:09 11sas11

That should do it. You probably just need to grab the full log instead of just the warnings.

mill1000 avatar Sep 01 '25 01:09 mill1000

full log:

2025-09-01 14:32:39.557 INFO (MainThread) [homeassistant.setup] Setting up midea_ac
2025-09-01 14:32:39.557 INFO (MainThread) [homeassistant.setup] Setup of domain midea_ac took 0.00 seconds
2025-09-01 14:32:39.558 INFO (MainThread) [custom_components.midea_ac] Starting midea-ac-py for device ID 151732606461934 (192.168.0.148:6444). Using msmart-ng version 2025.9.0.
2025-09-01 14:32:39.558 INFO (MainThread) [msmart.lan] Creating new connection to 192.168.0.148:6444.
2025-09-01 14:32:39.561 INFO (MainThread) [custom_components.midea_ac] Starting midea-ac-py for device ID 151732606461936 (192.168.0.149:6444). Using msmart-ng version 2025.9.0.
2025-09-01 14:32:39.562 INFO (MainThread) [msmart.lan] Creating new connection to 192.168.0.149:6444.
2025-09-01 14:32:39.564 INFO (MainThread) [custom_components.midea_ac] Starting midea-ac-py for device ID 151732606461938 (192.168.0.150:6444). Using msmart-ng version 2025.9.0.
2025-09-01 14:32:39.565 INFO (MainThread) [msmart.lan] Creating new connection to 192.168.0.150:6444.
2025-09-01 14:32:39.568 INFO (MainThread) [custom_components.midea_ac] Starting midea-ac-py for device ID 150633094836508 (192.168.0.151:6444). Using msmart-ng version 2025.9.0.
2025-09-01 14:32:39.568 INFO (MainThread) [msmart.lan] Creating new connection to 192.168.0.151:6444.
2025-09-01 14:32:39.617 DEBUG (MainThread) [msmart.lan] Connected to 192.168.0.149:6444.
2025-09-01 14:32:39.617 DEBUG (MainThread) [msmart.lan] Connected to 192.168.0.150:6444.
2025-09-01 14:32:39.617 INFO (MainThread) [msmart.lan] Authenticating with 192.168.0.149:6444.
2025-09-01 14:32:39.618 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.149:6444: 83700040200000001fdd1797be3fb7697ab433eeb84f2f20d5d54474042b91fafaf6a4bd8c3ba4a22096b54cc635e274e8dac5ca27f4ee2b3e8006610692911078de628eab88733f
2025-09-01 14:32:39.618 INFO (MainThread) [msmart.lan] Authenticating with 192.168.0.150:6444.
2025-09-01 14:32:39.618 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.150:6444: 837000402000000040d4b725520312df241e93e719cec57b09dd759a580cbee4020cc9cff70c55e979aa6f47b019f8425f25135311011850b0bb3a5eb3a829a6e5f81cec29417382
2025-09-01 14:32:39.624 DEBUG (MainThread) [msmart.lan] Connected to 192.168.0.151:6444.
2025-09-01 14:32:39.625 INFO (MainThread) [msmart.lan] Authenticating with 192.168.0.151:6444.
2025-09-01 14:32:39.625 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.151:6444: 83700040200000003a7c43d7333cc1b0e495e7f7888a74e7fdce0d97ee0fbacec4304de02bbe4211b0471e56c12b73c4197f4e4bf6cae06dd067ececb4812005a10a06c15a241c45
2025-09-01 14:32:39.633 DEBUG (MainThread) [msmart.lan] Connected to 192.168.0.148:6444.
2025-09-01 14:32:39.634 INFO (MainThread) [msmart.lan] Authenticating with 192.168.0.148:6444.
2025-09-01 14:32:39.634 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.148:6444: 8370004020000000d576f94b03b3e892fe0c03c4c7ba95d24f869e28cdff51fbecc4c6a4a593e141ade90febf02b20496599b2298351397f3fadba638c4b8c9c90d05a8c45a05b0c
2025-09-01 14:32:39.649 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.149:6444: 837000402001d44afa96d82cda3c71bed3f5333502fd55ae253ad68bd756cbcdfff04d5698169d5ce6ba0e6448a78aaf963aa325a28f257c5b4fc64887a69643026e1081ad0f9e3d
2025-09-01 14:32:39.680 INFO (MainThread) [msmart.lan] Authentication with 192.168.0.149:6444 successful. Expiration: 2025-09-01T16:32:39+00:00, Local key: 5525c91ed3c6386f91c3d1d51af3a4d576c6fc023189b535e8803661bd354658
2025-09-01 14:32:39.683 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.151:6444: 837000402001414e0e4e6c51bcaefc6cbeb7b3de7de43e129a4997268eebeeedfa8056c17255c04d1eb46f399489494215f4cf7c5e593163e94fd10f71c16c17db52dd2e0959346f
2025-09-01 14:32:39.757 INFO (MainThread) [msmart.lan] Authentication with 192.168.0.151:6444 successful. Expiration: 2025-09-01T16:32:39+00:00, Local key: 05845c9b9035245cfdc6c68231adc9e0d1ab0a1bc0e2203412cb012097b79073
2025-09-01 14:32:39.769 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.148:6444: 837000402001514f0fdba74a4273674e8dc8b50ab91186b0c0c3c58a48e60c3e67ba01fea3b5cd9e347cbc0a4a8fb4621a37a3d6899ba6989a4a4a625c3c36e0be99c690f488c067
2025-09-01 14:32:39.796 INFO (MainThread) [msmart.lan] Authentication with 192.168.0.148:6444 successful. Expiration: 2025-09-01T16:32:39+00:00, Local key: eb145d003e03aee0e1371e53f9b1b714f5b76409e40229a525d9b8ee76a667d5
2025-09-01 14:32:39.819 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.150:6444: 837000402001dc435d5defa24371eafd97eba252801f1484e7e663906497b34ad0e3f9a3d9013d68b77cadf22a634468c61a55e7afe61e7fc5a2f51567601c3572d7476739e7bf2f
2025-09-01 14:32:39.892 INFO (MainThread) [msmart.lan] Authentication with 192.168.0.150:6444 successful. Expiration: 2025-09-01T16:32:39+00:00, Local key: 282d8935f0f2f947e1ac46149fb29ec87e3ded7b6488f6722c4fa9cb88f9ea4e
2025-09-01 14:32:40.681 INFO (MainThread) [custom_components.midea_ac] Querying capabilities for device ID 151732606461936.
2025-09-01 14:32:40.683 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.149:6444: aa0fac00000000000003b5010001e5a6
2025-09-01 14:32:40.705 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.149:6444: 5a5a011158002000000000004628200401091914f0e71b00008a00000000000000000000000000000542065231b95b9123b7f675b1de90ae915c618b02ed2747fad73f2ffa0db1d3d13d77e050fc170acac7a014b2ee9a31
2025-09-01 14:32:40.707 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.149:6444: 8370007e2066ddd766064098630012ec2ec431d1ecdf8bae24319d5e8317975e5fe08a7b57fdc17e9b8fcfc5b43b854fcb80b97554d992a170ddfff13e6655fbbff3384e56896ce011da6511b6e351e5b02a5fb5ca42bf2d939a8ab416d62d46bdfdcaa94f7bea2c2712374ac6494af4fc80db49474c2cce431ac2dfa64539f2f8a2088aead1
2025-09-01 14:32:40.759 INFO (MainThread) [custom_components.midea_ac] Querying capabilities for device ID 150633094836508.
2025-09-01 14:32:40.760 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.151:6444: aa0fac00000000000003b50100020783
2025-09-01 14:32:40.760 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.151:6444: 5a5a011158002000000000004c282004010919141cf11b0000890000000000000000000000000000eaf378645833f63847a298e5e0f73437915c618b02ed2747fad73f2ffa0db1d366effa6532aadc2773402a7377f7c974
2025-09-01 14:32:40.762 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.151:6444: 8370007e2066e9ee00378cf95923a4de068c5251d7348562301c5b3e5bcce3948add3070f5c459e6ba7b8aa47fd002f579ccb63a22c91923822b9d92b52706809be63b1f26d4cb2e8d2fe608cf6d39f69be5574ad51d2aa2331556923c90629ac79bd88a626056af94bc72d487206a720094d3e55995da1fe13609eecc37a73e4ebc5f927c40
2025-09-01 14:32:40.797 INFO (MainThread) [custom_components.midea_ac] Querying capabilities for device ID 151732606461934.
2025-09-01 14:32:40.798 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.148:6444: aa0fac00000000000003b50100035930
2025-09-01 14:32:40.798 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.148:6444: 5a5a011158002000000000004f28200401091914eee71b00008a0000000000000000000000000000c37edb467c53bf24f807ba2357dbf56e915c618b02ed2747fad73f2ffa0db1d3a09d41d886560678c7ceaede4ea82b40
2025-09-01 14:32:40.801 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.148:6444: 8370007e2066ab794f96b68b4b74933118af34c512ab7702d83250bc8c0317553c6709cb0c61179a0d94e4283032aee6c94771bbcb6a561c96b525cfe3d767f544a5a18d7ddda4daa33f1ae8abd4597393c44dbc744e30dd9d8c5be972b6ca133d9f7bd7d009fb4d469273bbcd835134f8a97e796e81f45e2d0d4f2c45ea0ff948ce308a84a6
2025-09-01 14:32:40.894 INFO (MainThread) [custom_components.midea_ac] Querying capabilities for device ID 151732606461938.
2025-09-01 14:32:40.894 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.150:6444: aa0fac00000000000003b5010004daae
2025-09-01 14:32:40.895 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.150:6444: 5a5a011158002000000000005928200401091914f2e71b00008a0000000000000000000000000000dff03eda745c11213f9fece02b221508915c618b02ed2747fad73f2ffa0db1d3604c1aa952869c760a37c6e69c1ce370
2025-09-01 14:32:40.901 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.150:6444: 8370007e2066c315bb167b9505475bfcd056458d80a9732f16e194737650a2fb662fdbba42805b4dc51c9d41f1c38fd5f361ebf410775777516eb8dc9cc96b326394e43a1230b56d8a72553ffcfaf2cc9559fa9712a07df9b2f6b33b2403914ecc22cd41e1a60756ed3318a18d3c50de76a8ba787056f2433ba6cb63f0967c5f7a74d98dcc72
2025-09-01 14:32:40.945 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.149:6444: 837000ce2063626c7643784034638315da7aecab4d4a529e1f6a968c5bca6977eeb9602bbae4be157a46f67893cb7455be5c45f93bb9e2225693f8238399367604468fcaca5fa826d000a3f0d23f64b587a049da0d55c7c5ec0ff55a87a91466f8be5cb57c7d4002cbc4d75a6e1c156b0d4d8d9dce8321525a01c0e7276283f48e7ec806a5ea7cb9947abea5bf85893e1324d67d8896cab77e59d54761c00c38e2f3c6ffb48d2378a7513aae6c7f62bae5a4d096e10ec420aed8373602690362b8c284e9325deb0810854ba84efec07f3fa08b550586
2025-09-01 14:32:40.948 DEBUG (MainThread) [msmart.lan] Received packet from 192.168.0.149:6444: 5a5a0111a800208000000000c34d200401091914f0e71b00008a0000000000000000018000000000118868356eac0e018d04b91f46e87f13c210672005f7dbfd31dc6393f72394ede44409e215c25bb99f1af337467f8272204cfc39bd06fdb2313a5df3223f32d7e2dc548312bbc7f02e6088873e3d829acbbe1c11221a0ea29a98a9890c656e0f6807e30ee1552f17b72c5cf8a73de665505074d3a4409e2f0c5343964aca4014
2025-09-01 14:32:40.949 DEBUG (MainThread) [msmart.lan] Received response from 192.168.0.149:6444: aa63cc0000000000000301fe00000043005000728c8000bc00728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ffa2
2025-09-01 14:32:40.949 DEBUG (MainThread) [msmart.base_device] Response from 192.168.0.149:6444 in 0.270000 seconds.
2025-09-01 14:32:40.949 ERROR (MainThread) [msmart.device.AC.device] Payload '01fe00000043005000728c8000bc00728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0x29 or 0xD3.
2025-09-01 14:32:40.950 ERROR (MainThread) [msmart.device.AC.device] Failed to query capabilities from device 151732606461936.
2025-09-01 14:32:40.964 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.149:6444: aa21ac00000000000003418100ff03ff00020000000000000000000000000305085b
2025-09-01 14:32:40.965 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.149:6444: 5a5a011168002000000000006028200401091914f0e71b00008a000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b36a2496698f54e23033e012109731f93dc6be20c19674d4c970ec45aff30c4d43d2f75892624a94997150cdb0c54504a2
2025-09-01 14:32:40.965 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.149:6444: 8370008e20661f01025e3c31f4ee60b7c27050205fc6e6d766e06e02faf244d52431970704065c64e8de083d0512cbdd4a53c357ac27bbeff4146bb5b4d150023bc6ce7020dc68244875b37ebe3f99ec05db7111707253e766f43b38decaa03880bc66185d93d66a4e1ca287c51310282a9e55ea3c47261612fb1f9bc1917a03b5e72f14d49a7f4002cc35499f0134b8bfe20066c53a
2025-09-01 14:32:41.006 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.151:6444: 837000ce20637bd35162242bce41669c9e139d7417bdfd42875189c5480697413bc5e7d6e0db68e512371de955daeeead864912c1e5e5a576c923465b58b762894082d121960ed3752f9b82abdc6fd7322a9383f4da6d68b3e3b4bdc6176f5fc8c8b07936ae8150e88b6f1ea23754cce9e0991a9b5bd70e08edd24c641eedcc1e0118f1ecf0f9dca965fe1394e2c61d0b8acbfac295f516de69f6bc8eccdcb8c42f7b89e889d5711629dc6a1f5f3522ad7f8bd644a496c0fffa7825a9e304e26a39b547f13359484fc5cf767fe317a7a3bc0b0c69ef9
2025-09-01 14:32:41.009 DEBUG (MainThread) [msmart.lan] Received packet from 192.168.0.151:6444: 5a5a0111a8002080000000000ec62004010919141cf11b0000890000000000000000018000000000118868356eac0e018d04b91f46e87f13300569f5771aed77c7545c1ee3450f82e44409e215c25bb99f1af337467f8272204cfc39bd06fdb2313a5df3223f32d7e2dc548312bbc7f02e6088873e3d829acbbe1c11221a0ea29a98a9890c656e0fe8a5b9c6e595d93cce62a1298fa495509fe0e6d846f01c2c4bae43d05ca61a06
2025-09-01 14:32:41.010 DEBUG (MainThread) [msmart.lan] Received response from 192.168.0.151:6444: aa63cc0000000000000301fe00000043005000728c8000b700728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ffa7
2025-09-01 14:32:41.010 DEBUG (MainThread) [msmart.base_device] Response from 192.168.0.151:6444 in 0.250000 seconds.
2025-09-01 14:32:41.011 ERROR (MainThread) [msmart.device.AC.device] Payload '01fe00000043005000728c8000b700728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0xAC or 0xD8.
2025-09-01 14:32:41.011 ERROR (MainThread) [msmart.device.AC.device] Failed to query capabilities from device 150633094836508.
2025-09-01 14:32:41.025 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.151:6444: aa21ac00000000000003418100ff03ff00020000000000000000000000000306ea78
2025-09-01 14:32:41.027 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.151:6444: 5a5a0111680020000000000002292004010919141cf11b000089000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b3062fc0a1cd7d96dbe819b07b3b0e41b8d11694b185604954465f3b17a281749f27ef7002a3e19e714e61072d73229201
2025-09-01 14:32:41.028 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.151:6444: 8370008e206625718c51a7cd51c7b88c3fd554ce155dcac265bdaa2f2a7098b7266c7f8a667a7ccc3a2c6410dc6003ba8fd0de20de35d3965fff784d3c46c15534e331ed38740c306b9f5424e35cf966cb873a5b46f78232a66a3851be87e8a761e47689cbd65ebc4a644a1d915f6a87ffe592ec2200e5390e1659745e69b8258b2f4851ca53b5c45f8e70434fb194c2206467340730
2025-09-01 14:32:41.039 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.148:6444: 837000ce2063cd848e1fefd4d90d0f827a7800f3cbf9f7a1790284a938a460c7c98fa853b1813690e9cdf6e3b98344142d3739ca83008b62a26cc3de62b056d0a573cdbf7615312d17ea29475d3859b1ace69d85951c9e292c98c72e1707b44d78b3b58146fa961a0f8f078c5d92ced5a559ed0911981adfef870cfabae609049350c40c5c4f8a1521c3920c00fe05ec89fe891aaf7e9d3439a3fb433c78a1f5979ef7710866ccc06029b4d1a2a461c43777f606056d445b65883d8d46fcdd7bb75cb118756435d8f2b104a593196af8423059271e01
2025-09-01 14:32:41.045 DEBUG (MainThread) [msmart.lan] Received packet from 192.168.0.148:6444: 5a5a0111a800208000000000348c200401091914eee71b00008a0000000000000000018000000000118868356eac0e018d04b91f46e87f134a5f11e1bbd21679cb42b2e86b95d984e44409e215c25bb99f1af337467f8272204cfc39bd06fdb2313a5df3223f32d7e2dc548312bbc7f02e6088873e3d829acbbe1c11221a0ea29a98a9890c656e0f1c9883c455be4c9e42fd80e10829818fc94169214d7de07540ae562c3ab705e5
2025-09-01 14:32:41.046 DEBUG (MainThread) [msmart.lan] Received response from 192.168.0.148:6444: aa63cc0000000000000301fe00000043005000728c7a00cf00728c728c7a7a00010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ffa1
2025-09-01 14:32:41.046 DEBUG (MainThread) [msmart.base_device] Response from 192.168.0.148:6444 in 0.250000 seconds.
2025-09-01 14:32:41.046 ERROR (MainThread) [msmart.device.AC.device] Payload '01fe00000043005000728c7a00cf00728c728c7a7a00010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0xF0 or 0xD2.
2025-09-01 14:32:41.047 ERROR (MainThread) [msmart.device.AC.device] Failed to query capabilities from device 151732606461934.
2025-09-01 14:32:41.059 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.148:6444: aa21ac00000000000003418100ff03ff00020000000000000000000000000307b4ad
2025-09-01 14:32:41.061 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.148:6444: 5a5a011168002000000000000629200401091914eee71b00008a000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b36ecff7bf9e9fe8567b674002630ed398b87b27e9c3447179f0aa84eead20534de925715ce42add6f4e3c8f3cb91b8228
2025-09-01 14:32:41.061 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.148:6444: 8370008e2066c04761f2a5ed8988dde9f8fafd99f210954acf7921b52832cc0d4231dbbeffd0da6a28785c81041cbc92f3e3b2acd74ebd7392077fa30875f51ed0490c6167cd8dd02de49eb37e0c5062bca16d8d8ae7796f7bb72fdb7d458246481c9aea95a83d328f3c3a21442da5dc38a4655e295c35f485ab231516bc229af59a578dd87bb4f5f592af0d818a1b199752029540c6
2025-09-01 14:32:41.120 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.150:6444: 837000ce2063135932cddc32b741351260825312b579dc68a0ec2009619f5258bcfbaa5517a9343b291957a158cd9f9bbf5a0111891984f19d2d81fb4cd125579eecc321ad0a2e85e601ba81c31cb7e83672fc1a825567be87d5aec7183e41be13d2835e70e5a93209620437d4cf113cae1668ec8a90bb5b9be271b3e2d366c893c32ddcce37723c7458b513d5c6ac5e49af15f6ee54cd7006e15740f178b808c429a777e1906d21a7c812f4f9646bbcd1d56172dd5e3792eddd54e7d349c285a1619fb2000ea6f5ea055da9c658615c2fb772d44c60
2025-09-01 14:32:41.121 DEBUG (MainThread) [msmart.lan] Received packet from 192.168.0.150:6444: 5a5a0111a800208000000000e322200401091914f2e71b00008a0000000000000000018000000000118868356eac0e018d04b91f46e87f13b76c8a22f2def95faa08dad1225e26c27a42ef50b1febcb443192267fadf77fc204cfc39bd06fdb2313a5df3223f32d7e2dc548312bbc7f02e6088873e3d829acbbe1c11221a0ea29a98a9890c656e0f26fec4e274d87f0196b079839f67f929b6e8956676c21f66e257327b5134b5a2
2025-09-01 14:32:41.121 DEBUG (MainThread) [msmart.lan] Received response from 192.168.0.150:6444: aa63cc0000000000000301fe00000043005000728c8000ae00728c728c808000010141ff010203000603010007000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ffa9
2025-09-01 14:32:41.122 DEBUG (MainThread) [msmart.base_device] Response from 192.168.0.150:6444 in 0.230000 seconds.
2025-09-01 14:32:41.122 ERROR (MainThread) [msmart.device.AC.device] Payload '01fe00000043005000728c8000ae00728c728c808000010141ff010203000603010007000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0xF6 or 0xDA.
2025-09-01 14:32:41.122 ERROR (MainThread) [msmart.device.AC.device] Failed to query capabilities from device 151732606461938.
2025-09-01 14:32:41.134 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.0.150:6444: aa21ac00000000000003418100ff03ff00020000000000000000000000000308f56b
2025-09-01 14:32:41.135 DEBUG (MainThread) [msmart.lan] Sending packet to 192.168.0.150:6444: 5a5a011168002000000000000d29200401091914f2e71b00008a000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b32de3ee43a85a38d3e77ee80be0616b851712a2f12d69dc7678095a12792c996af6c3f6f6aad950f7b5437f14a7ea3da9
2025-09-01 14:32:41.135 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.0.150:6444: 8370008e2066c7934f6a4f0a84ad36499376d09eed15b09c098c35dc8965679c005ccaeccb7e9d8fc80191660f19d15a303ae627fb6d100e129827123401afe80a5e869fcb3d4af84cb2ce39e4737d5e3202d23b254ee2d3f270f6136bf0277d05997cf6de0cc0306323bc323d54a47d806728ef00b69b5f629e48d382e283ceb01f24b1109eeb861358f248131e5f237f544bc192dc
2025-09-01 14:32:41.156 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.149:6444: 837000ce20635891369469fd9b8cb6dc10406dda83b2cd9ea1950aaf688b566aded16077d2750289367ca9caa448a493250ff576940baf14c22a03d30a43b7400c4fbb9727cdb8c17c44a303bf66db01d050cf5cc87254784f0dfb431496b172ec3fcae4ccbae0a9dc23c9bbfdc05409be44e56569fcf0d0b4fb396a92de68f23886dd6b6972ca2dc1a058a05b0d775879017253ce5866f386d04419d6b2173fcaa133b3ac8c96017e3efc375dc319bce60e56050d9b1b2e4db28b88ea77e212b83c10e7a40b6883feafd92e96940488f709cc9298cb
2025-09-01 14:32:41.157 DEBUG (MainThread) [msmart.lan] Received packet from 192.168.0.149:6444: 5a5a0111a800208000000000c34d200401091914f0e71b00008a0000000000000000018000000000118868356eac0e018d04b91f46e87f13c210672005f7dbfd31dc6393f72394ede44409e215c25bb99f1af337467f8272204cfc39bd06fdb2313a5df3223f32d7e2dc548312bbc7f02e6088873e3d829acbbe1c11221a0ea29a98a9890c656e0f6807e30ee1552f17b72c5cf8a73de665505074d3a4409e2f0c5343964aca4014
2025-09-01 14:32:41.158 DEBUG (MainThread) [msmart.lan] Received response from 192.168.0.149:6444: aa63cc0000000000000301fe00000043005000728c8000bc00728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ffa2
2025-09-01 14:32:41.158 DEBUG (MainThread) [msmart.base_device] Response from 192.168.0.149:6444 in 0.190000 seconds.
2025-09-01 14:32:41.158 ERROR (MainThread) [msmart.device.AC.device] Payload '01fe00000043005000728c8000bc00728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0x29 or 0xD3.
2025-09-01 14:32:41.158 DEBUG (MainThread) [custom_components.midea_ac.coordinator] Finished fetching midea_ac data in 0.195 seconds (success: True)
2025-09-01 14:32:41.212 DEBUG (MainThread) [msmart.lan] Received data from 192.168.0.151:6444: 837000ce2063710e29a037f555f12e58b4fd6dae04527ac335f70b9533590bdca3e3233aeb80c80ab264c8b12a56ead2e02898a7fd30b62c0ba048ca8d76514af802b34e81753d5469ff116e593f87979fc678b78842507b5e0a58ce0a531dfa13072fdaf088e79f73dd1e526d179abd083bf98bdf8f2668fc5a3e0b5d127d063d079ba5ba6fba421417cd59a8fdb851593a685206d48c7616c5f3df0448d153d6942973d3b14541d4d07405214ac8237a361caa7e22ce59dcaa10c397fbc464d0f742d65d3e3039d36e9cfc2e6c68a8d5a15392d4e0
2025-09-01 14:32:41.215 DEBUG (MainThread) [msmart.lan] Received packet from 192.168.0.151:6444: 5a5a0111a8002080000000000ec62004010919141cf11b0000890000000000000000018000000000118868356eac0e018d04b91f46e87f13300569f5771aed77c7545c1ee3450f82e44409e215c25bb99f1af337467f8272204cfc39bd06fdb2313a5df3223f32d7e2dc548312bbc7f02e6088873e3d829acbbe1c11221a0ea29a98a9890c656e0fe8a5b9c6e595d93cce62a1298fa495509fe0e6d846f01c2c4bae43d05ca61a06
2025-09-01 14:32:41.216 DEBUG (MainThread) [msmart.lan] Received response from 192.168.0.151:6444: aa63cc0000000000000301fe00000043005000728c8000b700728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ffa7
2025-09-01 14:32:41.216 DEBUG (MainThread) [msmart.base_device] Response from 192.168.0.151:6444 in 0.190000 seconds.
2025-09-01 14:32:41.217 ERROR (MainThread) [msmart.device.AC.device] Payload '01fe00000043005000728c8000b700728c728c808000010141ff010203000603010000000000000001000103010000000000000000000001000100010000000000000000000000000001000200000100000101000102ff02ff' failed CRC and checksum. Received: 0xFF, Expected: 0xAC or 0xD8.
2025-09-01 14:32:41.217 DEBUG (MainThread) [custom_components.midea_ac.coordinator] Finished fetching midea_ac data in 0.192 seconds (success: True)

11sas11 avatar Sep 01 '25 04:09 11sas11

Oh I see. Your devices are of type 0xCC which is unsupported by this integration.

If you download the protocol and plugin I can look at what adding support for these devices would take. e.g.

msmart-ng download IP_ADDRESS

Otherwise you might want to look at this project which supports more device types: https://github.com/wuwentao/midea_ac_lan

mill1000 avatar Sep 03 '25 19:09 mill1000

I tried wuwentao's and it found the units okay, but got bad data back. Bad as in wrong numbers, so I tried yours. I can raise an issue on that one as well.

msmart-mg download 192.168.0.148
{
  'ip': '192.168.0.148',
  'port': 6444,
  'id': 151732606461934,
  'online': False,
  'supported': False,
  'type': 204,
  'name': 'midea_cc_17H7',
  'sn': '0000CC341171PNL0160HLYT817H70000',
  'key': None,
  'token': None
}

Also I ran msmart-ng discover

INFO:msmart.cli:Discovering all devices on local network.
INFO:msmart.lan:Creating new connection to 192.168.0.149:6444.
INFO:msmart.lan:Authenticating with 192.168.0.149:6444.
INFO:msmart.lan:Creating new connection to 192.168.0.150:6444.
INFO:msmart.lan:Authenticating with 192.168.0.150:6444.
INFO:msmart.lan:Creating new connection to 192.168.0.151:6444.
INFO:msmart.lan:Authenticating with 192.168.0.151:6444.
INFO:msmart.lan:Creating new connection to 192.168.0.148:6444.
INFO:msmart.lan:Authenticating with 192.168.0.148:6444.
INFO:msmart.lan:Creating new connection to 192.168.0.149:6444.
INFO:msmart.lan:Authenticating with 192.168.0.149:6444.
INFO:msmart.lan:Authentication with 192.168.0.149:6444 successful. Expiration: 2025-09-04T13:02:47+00:00, Local key: 3a3e103b6334edf00f29e32b34857b7e3672a5bebf0a6ccf2d9fbdd97b3e262f
INFO:msmart.lan:Creating new connection to 192.168.0.150:6444.
INFO:msmart.lan:Authenticating with 192.168.0.150:6444.
INFO:msmart.lan:Authentication with 192.168.0.150:6444 successful. Expiration: 2025-09-04T13:02:48+00:00, Local key: 5075d7b8cc72ca33c37cb4b5af0ae11061285d3bb3f741d0e766506c069572fe
ERROR:msmart.discover:Device class Device has not implemented refresh().
INFO:msmart.lan:Creating new connection to 192.168.0.151:6444.
INFO:msmart.lan:Authenticating with 192.168.0.151:6444.
INFO:msmart.lan:Authentication with 192.168.0.151:6444 successful. Expiration: 2025-09-04T13:02:48+00:00, Local key: c1396602c5d77dc9a6af9ec9986d281b09ec2b0a3e1cfca75e5428163a5e7acf
ERROR:msmart.discover:Device class Device has not implemented refresh().
INFO:msmart.lan:Creating new connection to 192.168.0.148:6444.
INFO:msmart.lan:Authenticating with 192.168.0.148:6444.
INFO:msmart.lan:Authentication with 192.168.0.148:6444 successful. Expiration: 2025-09-04T13:02:49+00:00, Local key: f3138797a337e99a3b79dc91604e4cedc4f9e8ad1f87e3fc03ff24da5c54407d
ERROR:msmart.discover:Device class Device has not implemented refresh().
ERROR:msmart.discover:Device class Device has not implemented refresh().
INFO:msmart.cli:Found 4 devices.
INFO:msmart.cli:Found device:
{'ip': '192.168.0.150', 'port': 6444, 'id': 151732606461938, 'online': False, 'supported': False, 'type': 204, 'name': 'midea_cc_7VT6', 'sn': '0000CC341171PNL0160HLYT87VT60000', 'key': '356e515429ef4eefa0a130688c9464cd019658e673e8440d862955b1b78a7723', 'token': '4b59575641570849a5bc6836665b6ee05bd2e2b9f0b9d97af0acb3568e9304c62b8cd7763ec5f117c31b3e6b0a10bc91f9dc1e9c4912681916a5b1ad817b9530'}
INFO:msmart.cli:Found device:
{'ip': '192.168.0.151', 'port': 6444, 'id': 150633094836508, 'online': False, 'supported': False, 'type': 204, 'name': 'midea_cc_WYF1', 'sn': '0000CC341171PNL0160HLYT7WYF10000', 'key': '3ec45baf9e52485e8578a15ae986138d442e159e5ac04031a41c96815459c559', 'token': 'f0f2826b3c2513a65fc05f6c99fc92ee38ac11b51de6cb824dc4811599e862d6869fd0b4e6eb560a0e4d9c2d9823c08df69d0bf9afc82e2f178f8aea42f3282d'}
INFO:msmart.cli:Found device:
{'ip': '192.168.0.149', 'port': 6444, 'id': 151732606461936, 'online': False, 'supported': False, 'type': 204, 'name': 'midea_cc_4TP3', 'sn': '0000CC341171PNL0160HLYT84TP30000', 'key': '0160b6e7c3e64d3ca3b643e4d51cd8b151cd8670fe764e01aff01f176ab084e1', 'token': '4bc5687457e2df0b7f1d53caf3c9b39c0eba9628b16797fa36873e44fd8a2469d8221af525fc060f5ff05d28b2f46f8356789f679f948cd33b419af0de7df0fe'}
INFO:msmart.cli:Found device:
{'ip': '192.168.0.148', 'port': 6444, 'id': 151732606461934, 'online': False, 'supported': False, 'type': 204, 'name': 'midea_cc_17H7', 'sn': '0000CC341171PNL0160HLYT817H70000', 'key': '9b3da65ef1ec4a559c3f795fda72e82084cbcf6051484430b0b78216e86266b1', 'token': '749274ca15f4168375dc18692839b0351f48b92ffefe0066a92c2cec258514b8cadb4e59b3a3f946ff599d316217e55e57de30b2069de53b8b6c6f54f5d6d548'}

11sas11 avatar Sep 04 '25 02:09 11sas11

Did msmart download pull down the Lua and Plugin? I'd need a copy of those to implement support

mill1000 avatar Sep 04 '25 19:09 mill1000

No Lua or plugin files were downloaded. I searched the install path and root directories for anything with .lua or plugin in the name—nothing turned up. I'm going to try and figure out the commands with wireshark and a bit of help. Hopefully I can come back to you with something shortly.

11sas11 avatar Sep 05 '25 07:09 11sas11

I'm having a similar issue, not sure if my device is 0xBB like a previous issue or 0xCC, but I ran those commands and it didn't download anything, but on one response it said not supported and on another response it said supported, which I'm a bit confused about.

% msmart-ng download 192.168.2.81
INFO:msmart.cli:Discovering 192.168.2.81 on local network.
WARNING:msmart.discover:Reported device IP 192.168.2.18 does not match received IP 192.168.2.81. Using received IP.
INFO:msmart.cli:Found device:
{'ip': '192.168.2.81', 'port': 6444, 'id': [redacted], 'online': False, 'supported': False, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'net_ac_7144', 'sn': '[redacted]', 'key': None, 'token': None}
WARNING:msmart.cloud:Request to https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=/mj/user/login timed out.
ERROR:msmart.cli:Failed to establish cloud connection. Error: Code: 3144, Message: login failed, login ID is empty, please login again.
% msmart-ng discover
INFO:msmart.cli:Discovering all devices on local network.
WARNING:msmart.discover:Reported device IP 192.168.2.18 does not match received IP 192.168.2.81. Using received IP.
INFO:msmart.lan:Creating new connection to 192.168.2.81:6444.
INFO:msmart.lan:Authenticating with 192.168.2.81:6444.
INFO:msmart.lan:Creating new connection to 192.168.2.171:6444.
INFO:msmart.lan:Authenticating with 192.168.2.171:6444.
INFO:msmart.lan:Creating new connection to 192.168.2.81:6444.
INFO:msmart.lan:Authenticating with 192.168.2.81:6444.
INFO:msmart.lan:Authentication with 192.168.2.81:6444 successful. Expiration: 2025-09-06T00:17:15+00:00, Local key: 9abf8323b39f4fc4fbbcd1b93e12bf9e8c4e7ed0620a4c0e07f894a72988ca30
INFO:msmart.lan:Creating new connection to 192.168.2.171:6444.
INFO:msmart.lan:Authenticating with 192.168.2.171:6444.
INFO:msmart.lan:Authentication with 192.168.2.171:6444 successful. Expiration: 2025-09-06T00:17:15+00:00, Local key: 852e4519526b3a0130f8cd8c1e108837da9a543869e7b4a4776fc30e8dfc7686
INFO:msmart.cli:Found 2 devices.
INFO:msmart.cli:Found device:
{'ip': '192.168.2.171', 'port': 6444, 'id': [redacted], 'online': True, 'supported': True, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'net_ac_F410', 'sn': '[redacted]', 'key': '[redacted]', 'token': '[redacted]'}
INFO:msmart.cli:Found device:
{'ip': '192.168.2.81', 'port': 6444, 'id': [redacted], 'online': True, 'supported': True, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'net_ac_7144', 'sn': '[redacted]', 'key': '[redacted]', 'token': '[redacted]'}

Elizabeth695739 avatar Sep 05 '25 12:09 Elizabeth695739

@Elizabeth695739 Your device type is 0xAC, and the 'supported': True should indicate we can properly parse responses from the device.

You can verify this with msmart-ng query <IP> --auto --debug

mill1000 avatar Sep 05 '25 20:09 mill1000

This is the output of that, but I'm a little confused because I keep getting occasional errors on home assistant that say the checksum has failed. Does that happen sometimes with devices that are supported?

% msmart-ng query 192.168.2.81 --auto --debug
DEBUG:asyncio:Using selector: KqueueSelector
INFO:msmart.cli:Discovering 192.168.2.81 on local network.
DEBUG:msmart.discover:Discovery sent to 192.168.2.81:6445.
DEBUG:msmart.discover:Discovery sent to 192.168.2.81:20086.
DEBUG:msmart.discover:Waiting 5 seconds for responses...
DEBUG:msmart.discover:Discovery response from 192.168.2.81: 837000c8200f00005a5a0111b8007a800000000022851c1405091914e8cb190000890000000000000000018000000000e2721c80fe910edbf13704efa3961c8515b4065f33d196f09a1083e730f109f84dd8cb2be9c93562d6f7eae1fb90ba76909d345c9cb22f0c334e794ce6b41a5ac2cdfc424dff352d4d7eb0ba9503d5ad2d20f672ea7810c93b8e0c47d51f577e4bdfb3e16e33d88768cc4c3d0658937d0bb19369bf0317b24d3a4de9e6a13106ad6fb0656c4d24b9e09ff1f79b4e4d2b43323e113a66de0ee41175ab61ab9180
DEBUG:msmart.discover:Decrypted data from 192.168.2.81: 1202a8c02c19000030303030303050303030303030305131424330343335313337313434303030300b6e65745f61635f373134340000bf0302000000000000000000ac00080000000000bc0435137144150080012311010301000000000000000000000000000000000000000000000000000000000000000000
WARNING:msmart.discover:Reported device IP 192.168.2.18 does not match received IP 192.168.2.81. Using received IP.
INFO:httpx:HTTP Request: POST https://mapp.appsmb.com/v1/user/login/id/get "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:Cloud response: {"msg":"ok","result":{"loginId":"[redacted]"},"errorCode":"0"}
DEBUG:msmart.cloud:Received loginId: 471329c3-ad2a-48bf-a55c-53866ed6b331
INFO:httpx:HTTP Request: POST https://mapp.appsmb.com/v1/user/login "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:Cloud response: {"msg":"ok","result":{"nickname":"[email protected]","sessionId":"0dcc44ffdfa543f0953f14b034ddaa4420250905202821465","accessToken":"[redacted]","userId":"[redacted]","versionCode":"","leftCount":""},"errorCode":"0"}
DEBUG:msmart.cloud:Received sessionId: 0dcc44ffdfa543f0953f14b034ddaa4420250905202821465
DEBUG:msmart.discover:Fetching token and key for udpid 'c1695403c7a1fd29545da3870fede522' (little).
INFO:httpx:HTTP Request: POST https://mapp.appsmb.com/v1/iot/secure/getToken "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:Cloud response: {"result":{"tokenlist":[{"udpId":"[redacted]","key":"[redacted]","token":"[redacted]"}]},"msg":"ok","errorCode":0}
INFO:msmart.lan:Creating new connection to 192.168.2.81:6444.
DEBUG:msmart.lan:Connected to 192.168.2.81:6444.
INFO:msmart.lan:Authenticating with 192.168.2.81:6444.
DEBUG:msmart.lan:Sending data to 192.168.2.81:6444: 83700040200000004b202ebb6ff9b592ff71d3c62c373d7043556a2648781e14dbd7dafb3dabe3353182b9df150ac31fe6d0ecfcdb5cf2e3672f8c8ef93bf5267802c4cff356699d
DEBUG:msmart.lan:Received data from 192.168.2.81:6444: 83700005200f00204552524f52
DEBUG:msmart.lan:Disconnecting from 192.168.2.81:6444.
DEBUG:msmart.discover:Fetching token and key for udpid '[redacted]' (big).
INFO:httpx:HTTP Request: POST https://mapp.appsmb.com/v1/iot/secure/getToken "HTTP/1.1 200 OK"
DEBUG:msmart.cloud:Cloud response: {"result":{"tokenlist":[{"udpId":"[redacted]","key":"[redacted]","token":"[redacted]"}]},"msg":"ok","errorCode":0}
INFO:msmart.lan:Creating new connection to 192.168.2.81:6444.
DEBUG:msmart.lan:Connected to 192.168.2.81:6444.
INFO:msmart.lan:Authenticating with 192.168.2.81:6444.
DEBUG:msmart.lan:Sending data to 192.168.2.81:6444: 837000402000000051c6ff4818d7937853ee61ca0257fdd2f4d7a37c12d5eb652ddce70c36fa03b7d9708ab0b602a57fa4d42d4252fef984f7958f24e96c2f5a564a50286ea2a708
DEBUG:msmart.lan:Received data from 192.168.2.81:6444: 837000402001f44f4f4e36d70547624b9955df850162e55c674674a8a6986b12dbafb22d1df451b49682bcecbec0e6cd45d4f4c193f139408b98983d31e80aa61d6754f46087c7a7
INFO:msmart.lan:Authentication with 192.168.2.81:6444 successful. Expiration: 2025-09-06T08:28:22+00:00, Local key: 122ee387e828aeeb953ab8213ae700734a2c38d8beb1a6f20a709d25dad1cb4e
DEBUG:msmart.base_device:Sending command to 192.168.2.81:6444: aa21ac00000000000003418100ff03ff0002000000000000000000000000030169fe
DEBUG:msmart.lan:Sending packet to 192.168.2.81:6444: 5a5a011168002000000000000d171c1405091914e8cb19000089000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b3e10c552981b23022cb71ea0fc54dc25e29ff4bed361a3a2fbe593a9d1a721035872484fac8bb219b8d967d3dc042f096
DEBUG:msmart.lan:Sending data to 192.168.2.81:6444: 8370008e206640a96fe83bc8e2960e8269e5eb739a670ddb0d1d7be0d2cb0cac5e6d8bf4291df7d104a21b839bd01cc81ed3849ecdc1fbb6aed7d37f5c6b040aa6d019f5a4ad16dbf8581f79a40d4d87eacbe7ed6e88db73bf0f4b3d68c63cef3005df0d62ddb4d6f701366f2754f21d348dd25731b9d021f1cd43615aed6031dc3f21e6469631ee0bec839beedd503b95a4d1e52f00
DEBUG:msmart.lan:Received data from 192.168.2.81:6444: 8370008e2063e6da6a6f8f355bf1b7511dea40f8d26f3fd48d7a03fdd500f50afbdc48e1cbc0f4a0c8d4e5feafefb1ad18e61059a5d701eb16a2f5505809687cac2ed645152dcd9acf9af5a7c780a8f101e3d9211b4bf35270dce2e6ab557d63d71659c501391c46c86ebccc2e4b890e270c7806b89d5b0a5b4722d4dfbd8d513be9731d30edf8e6e332dcd3b78c807c9da340a58718
DEBUG:msmart.lan:Received packet from 192.168.2.81:6444: 5a5a0111680020800000000022851c1405091914e8cb1900008900000000000000000180000000007cf123345c022e6be211c0f6289fa787329dcc253ebdf980b7e41153a519030173978cb08f08c69fb2b8f58606989ad85bd967d069630911666a70106020beb9
DEBUG:msmart.lan:Received response from 192.168.2.81:6444: aa28ac00000000000803c00057667f7f003300000460610b0053000000000000000100000000012d21
DEBUG:msmart.base_device:Response from 192.168.2.81:6444 in 0.170000 seconds.
DEBUG:msmart.device.AC.device:State response payload from device 150633094695912: c00057667f7f003300000460610b005300000000000000010000000001
DEBUG:msmart.discover:Discovered 1 devices.
INFO:msmart.cli:Querying device state.
DEBUG:msmart.base_device:Sending command to 192.168.2.81:6444: aa21ac00000000000003418100ff03ff000200000000000000000000000003028bdb
DEBUG:msmart.lan:Sending packet to 192.168.2.81:6444: 5a5a0111680020000000000022191c1405091914e8cb19000089000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b372946460bceafc6eae86e4200896522a2f2c998033e1118f4064e3bd2c45af9818a077529165b88f785d6ad2260bb8ab
DEBUG:msmart.lan:Sending data to 192.168.2.81:6444: 8370008e20662bf27a991c7689f51e499624297b22ef2187cd0f2213ca9b00c28159ec3343e5213c2d4a27e5857abe9053ab8e9d4fa6f326b3d7e82f030281e63c6004e6d84a05d72ddb3b77e32363566e22126d4835bca74cef765f7feb39b8fa8d979533e3001bc36349ff19a1f4b7e298c0da19cf0bcf7d7505353703319cf6a51ac8cfb3f9dfd70598e97817b3728fbe3978c4ca
DEBUG:msmart.lan:Received data from 192.168.2.81:6444: 8370008e2063a3df7cfef00df7ff2ea0f8500135775e5529b94404b08087e4425501789da5765497cbf3706b90630001f4885afab6a8af70a7bd2147783146b5cbc6d1ceab228a946a4c26eb0915475cbd62176975f423749d877f570964d5da08420d756cb2443d0b37bf76a84ad19129fbb58f9146177e398b33847e93e2af76130eab0d66de94161026b5b1eb80351a4e51e64084
DEBUG:msmart.lan:Received packet from 192.168.2.81:6444: 5a5a0111680020800000000022851c1405091914e8cb1900008900000000000000000180000000007cf123345c022e6be211c0f6289fa787329dcc253ebdf980b7e41153a5190301782dd14afdd91c329aee49eb44fa92cc00f9a131e0b232dde9f2ac62c4a79f81
DEBUG:msmart.lan:Received response from 192.168.2.81:6444: aa28ac00000000000803c00057667f7f003300000460610b005300000000000000010000000002cf7e
DEBUG:msmart.base_device:Response from 192.168.2.81:6444 in 0.170000 seconds.
DEBUG:msmart.device.AC.device:State response payload from device 150633094695912: c00057667f7f003300000460610b005300000000000000010000000002
WARNING:msmart.device.AC.device:'total_energy_usage' is deprecated. Please use 'get_total_energy_usage()' instead.
WARNING:msmart.device.AC.device:'current_energy_usage' is deprecated. Please use 'get_current_energy_usage()' instead.
WARNING:msmart.device.AC.device:'real_time_power_usage' is deprecated. Please use 'get_real_time_power_usage()' instead.
INFO:msmart.cli:{'ip': '192.168.2.81', 'port': 6444, 'id': [redacted], 'online': True, 'supported': True, 'type': <DeviceType.AIR_CONDITIONER: 172>, 'name': 'net_ac_7144', 'sn': '[redacted]', 'key': '[redacted]', 'token': '[redacted]', 'power': False, 'mode': <OperationalMode.COOL: 2>, 'fan_speed': <FanSpeed.AUTO: 102>, 'swing_mode': <SwingMode.HORIZONTAL: 3>, 'horizontal_swing_angle': <SwingAngle.OFF: 0>, 'vertical_swing_angle': <SwingAngle.OFF: 0>, 'cascade_mode': <CascadeMode.OFF: 0>, 'target_temperature': 23.5, 'indoor_temperature': 23.0, 'outdoor_temperature': 23.5, 'target_humidity': 0, 'indoor_humidity': None, 'eco': False, 'turbo': False, 'freeze_protection': False, 'sleep': False, 'display_on': True, 'beep': False, 'fahrenheit': True, 'filter_alert': False, 'follow_me': False, 'purifier': False, 'self_clean': False, 'total_energy_usage': None, 'current_energy_usage': None, 'real_time_power_usage': None, 'rate_select': <RateSelect.OFF: 100>, 'aux_mode': <AuxHeatMode.OFF: 0>}

These are the errors I'm getting on home assistant.

2025-09-05 14:42:23.982 ERROR (MainThread) [msmart.device.AC.device] Payload 'c1210144000005450000000000000000000046000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0x3F or 0x49.
2025-09-05 14:45:54.900 ERROR (MainThread) [msmart.device.AC.device] Payload 'c12101440000050a000000000000000000001e000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0x3F or 0xAC.
2025-09-05 15:02:24.017 ERROR (MainThread) [msmart.device.AC.device] Payload 'c1210144000005450000000000000000000046000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0x3F or 0x49.
2025-09-05 15:42:39.912 ERROR (MainThread) [msmart.device.AC.device] Payload 'c12101440000050a000000000000000000001e000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0x3F or 0xAC.
2025-09-05 15:47:10.897 ERROR (MainThread) [msmart.device.AC.device] Payload 'c1210144000005450000000000000000000046000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0x3F or 0x49.
2025-09-05 16:03:39.892 ERROR (MainThread) [msmart.device.AC.device] Payload 'c12101440000050a000000000000000000001e000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0x3F or 0xAC.
2025-09-05 16:20:55.891 ERROR (MainThread) [msmart.device.AC.device] Payload 'c1210144000005460000000000000000000078000000000000000000000000' failed CRC and checksum. Received: 0x0, Expected: 0xF1 or 0x16.

Elizabeth695739 avatar Sep 05 '25 20:09 Elizabeth695739

Your device is supported.

Those checksum/CRC errors are from energy usage messages. It's possibly a device quirk, and something that could be solved/ignored in msmart-ng.

mill1000 avatar Sep 05 '25 20:09 mill1000

Ok. Thank you for your help/reassurance

Elizabeth695739 avatar Sep 05 '25 20:09 Elizabeth695739

@11sas11 I'm hacking together support for 0xCC devices here: https://github.com/mill1000/midea-msmart/tree/feature/cc_device_support

Mostly based on the Lua file from here: https://github.com/hasscc/meiju/blob/main/custom_components/meiju/lua/T_0000_CC_6.lua

I don't know if the reference is terrible out of date though.

mill1000 avatar Sep 05 '25 22:09 mill1000

@11sas11 I've got the branch far enough along that it could use some testing.

I've put a small example script in the PR here: https://github.com/mill1000/midea-msmart/pull/233

Could you checkout the branch and try to run the example?

mill1000 avatar Sep 08 '25 17:09 mill1000

@mill1000 yep! Got it sorted! Responded in https://github.com/mill1000/midea-msmart/pull/233

11sas11 avatar Sep 09 '25 02:09 11sas11