Unsupported Packet - Possible conflict with midea_ac_lan

[DoerakkerHA]

did this:

• Search or browse the existing open and closed issues for your problem.
• Make sure you are running the latest version of the integration. Version v0.6.9

error: 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: September 14, 2025 at 17:05:04 (10 occurrences)
Last logged: 11:13:39

Network error 192.168.178.105:6444: Error packet received.
Network error 192.168.178.105:6444: Unsupported packet: 9648ba84c5e7f3df7d37f451f1c6e66c3121b0520be4534f6033441101eb69393262786068aee5a2f54f44d2085cb5653f7c6c8750d081b6dd0b0ef014be538c
Network error 192.168.178.102:6444: Error packet received.
Network error 192.168.178.32:6444: Error packet received.

specific log entry:

msmart.base_device] Network error 192.168.178.105:6444: Unsupported packet: 9648ba84c5e7f3df7d37f451f1c6e66c3121b0520be4534f6033441101eb69393262786068aee5a2f54f44d2085cb5653f7c6c8750d081b6dd0b0ef014be538c
2025-09-14 17:05:24.014 WARNING (MainThread) [msmart.lan] Send failed to 192.168.178.105:6444. Error: Error packet received.
2025-09-14 17:05:24.015 ERROR (MainThread) [msmart.base_device] Network error 192.168.178.105:6444: Error packet received.

~config_entry-midea_ac_lan-01K511C94EYWKW1KD79QB37H8H.json~ Wrong integration

[mill1000]

Does the device generally function or is it completely non-responsive?

It looks like you're running this integration (Midea Smart AC) along side Midea AC LAN which I would not recommend. We've seen issues before when both integrations are trying to communicate with the device simultaneously.

[DoerakkerHA]

I will disable the AC smart and keep an eye on it 

Kind RegardsROnald Groeneveld Sent from my iPhone +31 650 989 689On 15 Sep 2025, at 18:25, Tucker Kern @.***> wrote:mill1000 left a comment (mill1000/midea-ac-py#381) Does the device generally function or is it completely non-responsive? It looks like you're running this integration (Midea Smart AC) along side Midea AC LAN which I would not recommend. We've seen issues before when both integrations are trying to communicate with the device simultaneously.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[DoerakkerHA]

Generally functions fine (forgot to answer)

Kind RegardsROnald Groeneveld Sent from my iPhone +31 650 989 689On 15 Sep 2025, at 18:25, Tucker Kern @.***> wrote:mill1000 left a comment (mill1000/midea-ac-py#381) Does the device generally function or is it completely non-responsive? It looks like you're running this integration (Midea Smart AC) along side Midea AC LAN which I would not recommend. We've seen issues before when both integrations are trying to communicate with the device simultaneously.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[seanomat]

I get a similar error, about 4 times a day, since a month or two:

2025-09-17 02:14:38.330 WARNING (MainThread) [msmart.lan] Send failed to 192.168.17.34:6444. Error: Error packet received.

Everything is working fine, no other related integrations installed. This error did not occur before. It is does not correlate with any activity on the device.

Device: midea Portasplit

I'm not sure, if this is related. If it isn't please ignore.

[mill1000]

Can you enable debug logging and post the log when the error occurs?

[seanomat]

Sure:

2025-09-18 05:15:43.378 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.17.34:6444: 8370008e20662be0b7547d99d3815553e8a9da427ad644366b353ea8d173c748813dede83483731aa137b029e0297a78e76b6ee998e1566cb7ca701172f7c44ef87d440e4b7ad4785fed14b62b17f1ed3a00982b7185b9b4b31d2bd7cc5cb81be7ad008378434a67a42e53bf763bd8278ff4f892a25b4446d8adae295764baa728ca07913f33b83a668889d2e5291b17ae2bae27c994
2025-09-18 05:15:43.395 DEBUG (MainThread) [msmart.lan] Received data from 192.168.17.34:6444: 83700005200f00204552524f52
2025-09-18 05:15:43.396 WARNING (MainThread) [msmart.lan] Send failed to 192.168.17.34:6444. Error: Error packet received.
2025-09-18 05:15:43.398 DEBUG (MainThread) [msmart.lan] Disconnecting from 192.168.17.34:6444.
2025-09-18 05:15:43.400 DEBUG (MainThread) [msmart.base_device] Sending command to 192.168.17.34:6444: aa14ac00000000000003b10348003900e300ec3306
2025-09-18 05:15:43.400 INFO (MainThread) [msmart.lan] Creating new connection to 192.168.17.34:6444.
2025-09-18 05:15:43.415 DEBUG (MainThread) [msmart.lan] Connected to 192.168.17.34:6444.
2025-09-18 05:15:43.417 INFO (MainThread) [msmart.lan] Authenticating with 192.168.17.34:6444.
2025-09-18 05:15:43.418 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.17.34:6444: 8370004020000000a7f599013e7352674abbeaff5942f5018f828400453fbfff2951c5cdb01d460ef5bd6dc326176c93abbeffd875c7e63d9ea133d8940ba6b4f97f89a91e4b0218
2025-09-18 05:15:43.452 DEBUG (MainThread) [msmart.lan] Received data from 192.168.17.34:6444: 837000402001564e6525ca05373e3680595899951279f075f38fe05c2aac7b9d914de62fad5ed016f6fff8bc4e5041859b493aac6c48cc2f5d5eab337c5ccecb4b610ad6f6483b61
2025-09-18 05:15:43.453 INFO (MainThread) [msmart.lan] Authentication with 192.168.17.34:6444 successful. Expiration: 2025-09-18T15:15:43+00:00, Local key: ba6fb7b65941bb4c873ebca5eda22b8cd7ecb548287ab90adf1809400f2306e3

The previous reauthentication was:

2025-09-17 23:36:15.001 INFO (MainThread) [msmart.lan] Creating new connection to 192.168.17.34:6444.
2025-09-17 23:36:15.006 DEBUG (MainThread) [msmart.lan] Connected to 192.168.17.34:6444.
2025-09-17 23:36:15.006 INFO (MainThread) [msmart.lan] Authenticating with 192.168.17.34:6444.
2025-09-17 23:36:15.006 DEBUG (MainThread) [msmart.lan] Sending data to 192.168.17.34:6444: 8370004020000000a7f599013e7352674abbeaff5942f5018f828400453fbfff2951c5cdb01d460ef5bd6dc326176c93abbeffd875c7e63d9ea133d8940ba6b4f97f89a91e4b0218
2025-09-17 23:36:15.053 DEBUG (MainThread) [msmart.lan] Received data from 192.168.17.34:6444: 837000402001564ee8b291e04c46a8a4b2769c1708d5c87fac37445b75d4cc648e40ed7f417dbcc88bc28bc085a4f3cf5ef387cb179a83810dc1e3db6a65a2564f54fdd0217b6deb
2025-09-17 23:36:15.109 INFO (MainThread) [msmart.lan] Authentication with 192.168.17.34:6444 successful. Expiration: 2025-09-18T09:36:15+00:00, Local key: 94cc09c050b30f395fdf0bd5a62b19fd74ac063b42ce8879c1483832f5493691

My Timezone is +0200 at the moment with DST. Let me know, if you need the whole log (it's a whole day and around 10 MB).

[seanomat]

The more I think about this, the more I suspect this to be a connection-issue. I just reduced the reconnect interval to 1 hour. let's see.

[mill1000]

Gotcha, the other possibility is the authentication could be expiring sooner than expected.

I added the expiration on a bit of a whim (https://github.com/mill1000/midea-msmart/pull/67) not because I knew exactly what the devices wanted.

[seanomat]

That makes even more sense. The error in my case has not reoccurred.

Thank you for your service 😉

[mill1000]

Closing as stale. Feel free to re-open as needed.