New OH3 Binding - Midea Air Conditioning (LAN)

So I transferred the unit to.NethomePlus.

Also tried beautiful-midea to generate token /key

same result. InvalidKeyException Illegal Key size

So @justaoldman where and how do you generate token / key? Is the new 4.1.0 binding working for you at all?

what I have realized after transferring the unit to NethomePlus, the AC received a different IP address in this case 192.168.2.27, it was also registering the unit and switching to online status in OH but then my log pushed out errors with previous IP address 192.168.2.90 even after I deleted the whole Thing and created a new one still it communicated first to x.x.x.27 and then faults from x.x.x.90

Hours invested again, sadly without success or a good result

Solong
B

so a couple question if you do not mind.
can you tell me about your OH version and hardware?

if you use the python script is it able to retrieve temp and other values after discovery?
I can try to help you but I need a little more info the part about getting old device ip and errors is concerning me.
did autodiscover work for you when you moved to nethome and when you put your creds in did it return key/token pair?
the IP change is a little surprising also since all you had to do was reset the a/c put it back in the setup mode but mac would not change so wondering why it got new ip from dhcp.
but lets step back a moment and just try talking to the a/c locally using the midea-beautiful python script and nethome credentials and tell me what you get. Before we dive too deep into OH and the binding functionality
and to answer your question I let the binding populate my key and token using nethome creds but the binding version I use is not The latest from @zdanhauser since I have not seen his source code for it I cannot tell you how it works . What I use is the previous version that he had modified from @JacekDob original version I then ported to it work on 4.1 and added some debug statements as I mentioned in previous comments.

OH Version 4.1.0, working on Synology Docker in Host Mode

Yes after I changed unit to NethomePlus Auto discovery was possible
and it found it on different IP as I deleted my previous setting to IP x.x.x.90 in router

After putting in NethomePlus credentials it can not retrieve Key / token and gives back following fault in OH logging:

04:01:14.156 [WARN ] [nding.mideaac.internal.security.Cloud] - Error logging to Cloud: invalidSession

previously in logging:

04:03:04.034 [INFO ] [dler.MideaACHandler$ConnectionManager] - Retrieving Token and Key from cloud
04:03:04.035 [DEBUG] [nding.mideaac.internal.security.Cloud] - Request json: {"appId":"1017","format":2,"clientType":1,"language":"en_US","src":"1017","stamp":"20240108040304","udpid":"159aa1eccd9b611ba542e7d1615677ad"}
04:03:04.036 [TRACE] [ng.mideaac.internal.security.Security] - url: https://mapp.appsmb.com/v1/iot/secure/getToken

Device is set up in NethomePlus Cloud and values / On/ Off through app works fine

Credentials I also double checked and logged out and in with same password in app which I use in OH

Oh and after the Auto Discovery Thing is online, but in all connected Items it shows NULL, so no values retrieved

Is there a way of how you could supply me the version of Binding which you are using please?

I am almost out of ideas…

Solong
B

disregard the time stamps in debug protocol as I had to re-start pulling the key/token while I was writing here

So I am confused now are you able to run the python and retrieve values like temp back or not?
does this work?

midea-beautiful-air-cli status --ip APPLIANCE_IP_ADDRESS --token TOKEN --key KEY

I can give you link to my debug version but I never tried it on docker or on a raspi or any openhabian builds either. I have only used it on a linux debian VM and on a windows 10 and 11 VM
.
.

so thing is online but when you pick a channel and then create a new item for that channel it does not update the value in that new item?

No update of channel in item. all stays NULL even that AC shows ONLINE in status

with midea beautiful and requesting status with token ans key, I get status as result so that works

And yes please provide me your Binding pls, at least I give it a try

Thanks
B

ok if it was me I would leave my prod version of OH alone for now and maybe stand up a test version to test with. that bypasses all the docker and other Synology nuances with network and such
a simple OH install on windows is fastest and easiest to quickly spin up and get rid of if you want . it is nothing more then pulling down zulu 17 installer for windows run it and allow it to update your environment variables. dl the windows version of OH 4.1 stick it in a folder and then unzip it . launch the
start.bat then go to http://127.0.0.1:8080 walk through basic setup and maybe only add the ntp binding and astro binding just so you know the install worked this way you have nothing remnants of any past whatevers. The OH will not care about any other OH instances running or your other devices as long as you do not add any other bindings and I have had the midea binding running on several OH at same time before and it did not seem to be a issue when testing.
Should not take you more then 10 minutes or so and you have a nice clean isolated environment that will be easy to troubleshoot in and not impact your other automations.

yeah I am about to give up again, I had the binding running on Openhab 3.4 and then my system updated finally to 4.0 / 4.1 and from there on it was anyway impossible of using it.

I use the AC only in summer to produce our hot water with it and instead of using a software switch to turn the unit on and off in Openhab I have soldered two very small isolated copper wires to the remote button which turns the unit on and off which works very well untill the batteries are dead :slight_smile: The button is activated via a small single shot time based relais.

in the AC Unit I disabled the indoor part and replaced it with a heat exchanger into the hot water circle.

Setting up another windows system, probably not, will just hook up another Openhab Container in Docker which is clean and try in there…

In the meantime I think it is also NOT an connection / token / key issue I think it is more likely a decrypting issue of the reply which the AC Unit is sending.

But therefor my knowledge is not far enough into Openhab and development of bindings.

I appreciate your time and help though

Solong
B

BTW could you still supply your binding?

ok here it is but I really think you want to use a clean stand alone test OH build as I never tested this on anything more then what I already mentioned.

removed to prevent confusion
the snapshot jar file works in 4.0 and 4.1 versions
I have a crap load of debug statements in it that may not be as insightful as they should be so take it for what it is I was chasing many different issues with the other version mostly related to version 2 A/c that quit working after Zoltan merged his changes to Jaceks version. .
Pull it down as quick as you can I do not think it is a good idea to leave up very long as folks may get confused on which versions they need and this is not a ready for public use version by any means

build a 3.3 volt power supply and solder that to the battery terminals and then it will never die :wink:

you would not have to build a new windows system any win 10 desktop would be fine as a temp testing approach and it is easy to remove when done delete key on OH directory and 1 click in settings to remove java :stuck_out_tongue:

1 Like

Here I am again (not) on my own :wink:

so after re-booting Openhab, things look different, not better but different

Retrieivng token and key brings up this fault:


14:35:06.445 [TRACE] [dler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_2_90__-135239930205742__net_ac_7107@192.168.2.90 writing handshake_request: 83700040200000003F3EECEE0A54D1D4191DF4888C801DAFB116E35E794217CF5ED920D8AF37622FD4EB1477D83F7869DE9083BC90C437F1FFD5DBB83EF7DB79AD328D0BB0E65B62
14:35:06.974 [DEBUG] [dler.MideaACHandler$ConnectionManager] - Response received length: 13
14:35:06.976 [DEBUG] [dler.MideaACHandler$ConnectionManager] - Response bytes: 83700005200F00004552524F52
14:35:06.978 [TRACE] [dler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_2_90__-135239930205742__net_ac_7107@192.168.2.90 response for handshake_request length: 13
14:35:06.979 [TRACE] [dler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_2_90__-135239930205742__net_ac_7107@192.168.2.90 response for handshake_request: 83700005200F00004552524F52
14:35:06.980 [WARN ] [dler.MideaACHandler$ConnectionManager] - Authentication reponse unexpected data length (13 instead of 72)!
14:35:06.982 [DEBUG] [dler.MideaACHandler$ConnectionManager] - Invalid Token. Correct Token in configuration

with this status line:
Screenshot 2024-01-08 at 14-38-50 openHAB

and with token and key generated externally it is this fault message:

14:43:59.355 [TRACE] [ng.mideaac.internal.security.Security] - Size: 64
14:43:59.357 [TRACE] [ng.mideaac.internal.security.Security] - Header:      837000402000
14:43:59.359 [TRACE] [ng.mideaac.internal.security.Security] - Data:        000055C031C8E5E2315E230F1E8C9E4B9C63F8BC8F021152EAC71B48F5C1B4A67FA6A9AFF5F43EF4A18F464FD6E1124D486962C2E45B0049A1B081117726F4309764
14:43:59.360 [TRACE] [ng.mideaac.internal.security.Security] - Result:      837000402000000055C031C8E5E2315E230F1E8C9E4B9C63F8BC8F021152EAC71B48F5C1B4A67FA6A9AFF5F43EF4A18F464FD6E1124D486962C2E45B0049A1B081117726F4309764
14:43:59.362 [TRACE] [dler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_2_90__-135239930205742__net_ac_7107@192.168.2.90 writing handshake_request: 837000402000000055C031C8E5E2315E230F1E8C9E4B9C63F8BC8F021152EAC71B48F5C1B4A67FA6A9AFF5F43EF4A18F464FD6E1124D486962C2E45B0049A1B081117726F4309764
14:43:59.869 [DEBUG] [dler.MideaACHandler$ConnectionManager] - Response received length: 72
14:43:59.870 [DEBUG] [dler.MideaACHandler$ConnectionManager] - Response bytes: 8370004020010000E8BF4923F2C81008A23A31357B9A28AA57D064B81149016457059F1EE4EB93EA333F5D6B5152D143AD64C6D06DF9DDEE52C391526FA1072D67DC05952A98E576
14:43:59.872 [TRACE] [dler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_2_90__-135239930205742__net_ac_7107@192.168.2.90 response for handshake_request length: 72
14:43:59.874 [TRACE] [dler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_2_90__-135239930205742__net_ac_7107@192.168.2.90 response for handshake_request: 8370004020010000E8BF4923F2C81008A23A31357B9A28AA57D064B81149016457059F1EE4EB93EA333F5D6B5152D143AD64C6D06DF9DDEE52C391526FA1072D67DC05952A98E576
14:43:59.877 [WARN ] [ng.mideaac.internal.security.Security] - AES decryption error: InvalidKeyException: Illegal key size

But with key size I think it is more towards not being able to decrypt the information what came back from the device.

and status line looks like this:

until I send a command to switch on and then it looks like this:

Screenshot 2024-01-08 at 14-48-10 openHAB

I have no idea anymore…

Solong
B

Part of why I asked if you could build out a standalone non docker build was to eliminate docker related conditions but Since it is docker if you think it is a encrypt decrypt issue you could try this.
https://hub.docker.com/r/openhab/openhab/#java-cryptographic-strength-policy

Java cryptographic strength policy

Due to local laws and export restrictions the containers use Java with a limited cryptographic strength policy. Some openHAB functionality may depend on unlimited strength which can be enabled by configuring the environment variable CRYPTO_POLICY=unlimited

Before enabling this make sure this is allowed by local laws and you agree with the applicable license and terms (see OpenJDK (Cryptographic Cautions)).

The following functionality depends on the unlimited cryptographic strength policy:

  • KM200 Binding
  • Linky Binding
  • Loxone Binding
  • MQTT Binding
  • openHAB Marketplace

Parameters

Keep in mind that the list above is not all inclusive of only bindings that could be impacted.

@justaoldman Justan, you made my day…

Was set to:
CRYPTO_POLICY=limited

Now set to
CRYPTO_POLICY=unlimited

The Midea Binding immidiately started to work.

Therefore my Sonos Binding discontinued to work with Update to 4.1.1 OH, but it comes and goes so on some versions it is there a couple weeks later its gone again on my Tablet Kiosk on the Wall in Living Room…

Look at that:

Solong
B

I am a bit confused, could someone link me to a binding/jar file which works on 4.0/4.1 ?

Got a bit confused about what is the correct file to use for now

Try @zdanhauser new version.
The one I shared is just a debugger version has lots of extra debug messages and statements that may not be intuitive to you without having code open to see what they mean. Also, my version It may not be friendly with your setup as it was only tested for a just few OS types like pure Linux build and Windows build.

Just installed the binding, thank you for linking it, now the logs show this really really often:

2024-02-09 15:27:28.630 [ERROR] [mideaac.internal.handler.CommandBase] - SSWING id 0

2024-02-09 15:27:28.633 [ERROR] [mideaac.internal.handler.CommandBase] - SSWING id 0

Hello Everyone!
I just tried to install with latest addon “org.openhab.binding.mideaac-4.1.0-SNAPSHOT.jar” to my OH4.1.1 a Midea AC. I’ve succesfully created thing, got the right keys with msmart-ng, and getting connected. But not able to control the AC unit or get some temperature readings. Once, I try to switch on the unit, connection going to lost, and reconnecting back. Similar reconnection happening after few minutes without any interaction.

I already went thru briefly on the complete topic, but didn’t find any solution yet.
Can somebody give a hint in troubleshooting, where to look in my case?

Thanks!

In the log I am getting following errors:

2024-02-11 19:35:26.918 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:35:28.457 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:35:38.595 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:35:48.739 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:35:58.887 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:36:09.974 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:36:20.110 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:36:30.252 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:36:35.533 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Midea_Air_Conditioner_Power' received command ON
2024-02-11 19:36:35.534 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Midea_Air_Conditioner_Power' predicted to become ON
2024-02-11 19:36:35.536 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Midea_Air_Conditioner_Power' changed from OFF to ON
2024-02-11 19:36:35.799 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.
2024-02-11 19:36:41.323 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. to ONLINE
2024-02-11 19:36:41.831 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Midea_Air_Conditioner_Power' received command OFF
2024-02-11 19:36:41.832 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Midea_Air_Conditioner_Power' predicted to become OFF
2024-02-11 19:36:41.833 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Midea_Air_Conditioner_Power' changed from ON to OFF
2024-02-11 19:36:42.086 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.
2024-02-11 19:36:41.324 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:36:51.466 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. to ONLINE
2024-02-11 19:36:51.467 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:37:02.472 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:37:12.611 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:37:22.750 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:37:33.016 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.
2024-02-11 19:37:53.018 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. to UNKNOWN
2024-02-11 19:37:53.268 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Broken pipe
2024-02-11 19:38:04.280 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from OFFLINE (COMMUNICATION_ERROR): Broken pipe to ONLINE
2024-02-11 19:38:04.279 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:5a3ba29334 at 192.168.10.100

Detailed logging with TRACE below:

2024-02-11 19:50:54.322 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:5a3ba29334 at IP 192.168.10.100
2024-02-11 19:50:54.323 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:50:54.323 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:50:54.323 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:5a3ba29334 at 192.168.10.100:6444
2024-02-11 19:50:54.326 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:50:54.326 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:5a3ba29334 from OFFLINE(COMMUNICATION_ERROR) to ONLINE
2024-02-11 19:50:54.326 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5a3ba29334@192.168.10.100 require authentication, going to authenticate
2024-02-11 19:50:54.327 [TRACE] [ler.MideaACHandler$ConnectionManager] - Version: 3
2024-02-11 19:50:54.327 [TRACE] [ler.MideaACHandler$ConnectionManager] - Key: 20448b7c16a74103934de26959cc987118d94f5f754444c582259e8f421d26ce
2024-02-11 19:50:54.328 [TRACE] [ler.MideaACHandler$ConnectionManager] - Token: e91f73e7d2d76032fcaf3480d91d781bb6372c5e888cf800215c487bf9392664cc8a1737003e47acc2e32d3f11123931a9241cf80e35fa119aa1aff5bfb43a32
2024-02-11 19:50:54.328 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5a3ba29334@192.168.10.100 authenticating
2024-02-11 19:50:54.328 [TRACE] [g.mideaac.internal.security.Security] - Size: 64
2024-02-11 19:50:54.328 [TRACE] [g.mideaac.internal.security.Security] - Header:      837000402000
2024-02-11 19:50:54.328 [TRACE] [g.mideaac.internal.security.Security] - Data:        011FE91F73E7D2D76032FCAF3480D91D781BB6372C5E888CF800215C487BF9392664CC8A1737003E47ACC2E32D3F11123931A9241CF80E35FA119AA1AFF5BFB43A32
2024-02-11 19:50:54.328 [TRACE] [g.mideaac.internal.security.Security] - Result:      837000402000011FE91F73E7D2D76032FCAF3480D91D781BB6372C5E888CF800215C487BF9392664CC8A1737003E47ACC2E32D3F11123931A9241CF80E35FA119AA1AFF5BFB43A32
2024-02-11 19:50:54.329 [TRACE] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5a3ba29334@192.168.10.100 writing handshake_request: 837000402000011FE91F73E7D2D76032FCAF3480D91D781BB6372C5E888CF800215C487BF9392664CC8A1737003E47ACC2E32D3F11123931A9241CF80E35FA119AA1AFF5BFB43A32
2024-02-11 19:50:54.543 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 72
2024-02-11 19:50:54.543 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: 8370004020010000DDA2C412E848F0C0C0C0D45A4DCF200097BFC42A9BC07D13E03C5531CA9FD697B6EBD294FD693B952A6777BB0EE3C5C0216D326A136D1332E0BFFFDDEA145B6C
2024-02-11 19:50:54.543 [TRACE] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5a3ba29334@192.168.10.100 response for handshake_request length: 72
2024-02-11 19:50:54.544 [TRACE] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5a3ba29334@192.168.10.100 response for handshake_request: 8370004020010000DDA2C412E848F0C0C0C0D45A4DCF200097BFC42A9BC07D13E03C5531CA9FD697B6EBD294FD693B952A6777BB0EE3C5C0216D326A136D1332E0BFFFDDEA145B6C
2024-02-11 19:50:54.544 [TRACE] [g.mideaac.internal.security.Security] - Payload:   DDA2C412E848F0C0C0C0D45A4DCF200097BFC42A9BC07D13E03C5531CA9FD697
2024-02-11 19:50:54.544 [TRACE] [g.mideaac.internal.security.Security] - Sign:      B6EBD294FD693B952A6777BB0EE3C5C0216D326A136D1332E0BFFFDDEA145B6C
2024-02-11 19:50:54.544 [TRACE] [g.mideaac.internal.security.Security] - SignLocal: B6EBD294FD693B952A6777BB0EE3C5C0216D326A136D1332E0BFFFDDEA145B6C
2024-02-11 19:50:54.544 [TRACE] [g.mideaac.internal.security.Security] - Plain:     8BCAF68D1B5373AF829BF1ADCA57F3AC0673F2AD221573AD4487F3ADD634F3AD
2024-02-11 19:50:54.545 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:    AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:50:54.545 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Authentication successufull
2024-02-11 19:50:55.545 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:50:55.546 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:5a3ba29334 at 192.168.10.100 bytes.length: 104, bytes: 5A5A011168002000000000000118010B13323700D5CA0100008300000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B5D83C3D3BF05B1F7B20AFD3884FC5234FABD9611A01068EAC9C473549748254212EA614F667594EBFF456903F20B9982
2024-02-11 19:50:55.546 [TRACE] [g.mideaac.internal.security.Security] - Size: 104
2024-02-11 19:50:55.546 [TRACE] [g.mideaac.internal.security.Security] - Padding size: 6, size: 142
2024-02-11 19:50:55.547 [TRACE] [g.mideaac.internal.security.Security] - Header:      8370008E2066
2024-02-11 19:50:55.547 [TRACE] [g.mideaac.internal.security.Security] - Data:        01205A5A011168002000000000000118010B13323700D5CA0100008300000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B5D83C3D3BF05B1F7B20AFD3884FC5234FABD9611A01068EAC9C473549748254212EA614F667594EBFF456903F20B99827EF7D565BC42
2024-02-11 19:50:55.547 [TRACE] [g.mideaac.internal.security.Security] - Sign:        25524DDA7F1A65492AD133C4EB0CE51C69C5C875680F4D215202C48C438BB70E
2024-02-11 19:50:55.547 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:      AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:50:55.547 [TRACE] [g.mideaac.internal.security.Security] - EncSignData: 6E263FC23294E9F5A96037A10CF9B453684B042D3FEAF6CF1D5A11EDC171125752EB4554135C8BC0A356BD5915A8B49E88D65B622531D6DFE110865F6EEAA679DFCDF35B7ABBAA22384C108D50FE539057CBC5C6C348CFCC2B5E46C0315821D264F8E02A7FC0BE3FC374FACABA6BC16B25524DDA7F1A65492AD133C4EB0CE51C69C5C875680F4D215202C48C438BB70E
2024-02-11 19:50:55.547 [TRACE] [g.mideaac.internal.security.Security] - Result:      8370008E20666E263FC23294E9F5A96037A10CF9B453684B042D3FEAF6CF1D5A11EDC171125752EB4554135C8BC0A356BD5915A8B49E88D65B622531D6DFE110865F6EEAA679DFCDF35B7ABBAA22384C108D50FE539057CBC5C6C348CFCC2B5E46C0315821D264F8E02A7FC0BE3FC374FACABA6BC16B25524DDA7F1A65492AD133C4EB0CE51C69C5C875680F4D215202C48C438BB70E
2024-02-11 19:50:55.687 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 150
2024-02-11 19:50:55.687 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: 8370008E2063D0D6919C540D8EDBDB02195087F3DDF55B8DFD6F3D5DF488861E53ADA6AF7044C82519ED024EDE97FE4C4815E0BA9A4540DCF3574ED3C7E05F9E707A989F50446F63F4D24D5F4B4E1E371DC3E163CD1C140B474CBED4BA5EF312CC98D898CCF032F73348C44113B93548550BD2EBFB9BDBBE667FE2C87912B8EB20AFB6392876DBCC83316A765E086D6D39D793C10360
2024-02-11 19:50:55.687 [TRACE] [g.mideaac.internal.security.Security] - Header:        8370008E2063
2024-02-11 19:50:55.688 [TRACE] [g.mideaac.internal.security.Security] - Size: 150
2024-02-11 19:50:55.688 [TRACE] [g.mideaac.internal.security.Security] - Padding: 6
2024-02-11 19:50:55.688 [TRACE] [g.mideaac.internal.security.Security] - MsgType: MSGTYPE_ENCRYPTED_RESPONSE
2024-02-11 19:50:55.688 [TRACE] [g.mideaac.internal.security.Security] - Sign:        DBBE667FE2C87912B8EB20AFB6392876DBCC83316A765E086D6D39D793C10360
2024-02-11 19:50:55.688 [TRACE] [g.mideaac.internal.security.Security] - SignLocal:   DBBE667FE2C87912B8EB20AFB6392876DBCC83316A765E086D6D39D793C10360
2024-02-11 19:50:55.689 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:      AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:50:55.689 [TRACE] [g.mideaac.internal.security.Security] - Data:        04015A5A011168002080000000000000000000000000D5CA0100008300000000000000000000000000009BFA18B38F323BDE46315D57F4FAC2493A440AA98B843D494D61E4D1BA19ABC7E7873C9FF6CB7C7AB1F0D1EFC56991CB858D00C85293C86859E9DB4CBA575B7F605D9DAC0906
2024-02-11 19:50:55.689 [TRACE] [g.mideaac.internal.security.Security] - Response_count: 1025
2024-02-11 19:50:55.689 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response length: 104
2024-02-11 19:50:55.689 [TRACE] [ler.MideaACHandler$ConnectionManager] - Packet: 8370008E2063D0D6919C540D8EDBDB02195087F3DDF55B8DFD6F3D5DF488861E53ADA6AF7044C82519ED024EDE97FE4C4815E0BA9A4540DCF3574ED3C7E05F9E707A989F50446F63F4D24D5F4B4E1E371DC3E163CD1C140B474CBED4BA5EF312CC98D898CCF032F73348C44113B93548550BD2EBFB9BDBBE667FE2C87912B8EB20AFB6392876DBCC83316A765E086D6D39D793C10360
2024-02-11 19:50:55.689 [TRACE] [ler.MideaACHandler$ConnectionManager] - Bytes decoded and stripped without header: length: 26, data: C0008E667F7F003300000069FF1200050000000000000037B0E1
2024-02-11 19:50:55.690 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:50:55.690 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:00.363 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Midea_Air_Conditioner_Power' received command ON
2024-02-11 19:51:00.364 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Midea_Air_Conditioner_Power' predicted to become ON
2024-02-11 19:51:00.366 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Midea_Air_Conditioner_Power' changed from OFF to ON
2024-02-11 19:51:00.372 [DEBUG] [eaac.internal.handler.MideaACHandler] - Handling channelUID power with command ON
2024-02-11 19:51:00.373 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:5a3ba29334 from ONLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2024-02-11 19:51:00.625 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.
2024-02-11 19:51:05.838 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. to ONLINE
2024-02-11 19:51:05.690 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:5a3ba29334 at IP 192.168.10.100
2024-02-11 19:51:05.691 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:05.692 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check OK for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:05.692 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Requesting status update from mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:05.693 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:5a3ba29334 at 192.168.10.100 bytes.length: 104, bytes: 5A5A011168002000000000000118010B13330500D5CA0100008300000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B449B1D426C81EE680E7E3E131C202D14D8D099A9DDEF36EBD7BD8013F6738E82C53E408D21C968B3EAA15518249BF489
2024-02-11 19:51:05.693 [TRACE] [g.mideaac.internal.security.Security] - Size: 104
2024-02-11 19:51:05.694 [TRACE] [g.mideaac.internal.security.Security] - Padding size: 6, size: 142
2024-02-11 19:51:05.694 [TRACE] [g.mideaac.internal.security.Security] - Header:      8370008E2066
2024-02-11 19:51:05.694 [TRACE] [g.mideaac.internal.security.Security] - Data:        01215A5A011168002000000000000118010B13330500D5CA0100008300000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B449B1D426C81EE680E7E3E131C202D14D8D099A9DDEF36EBD7BD8013F6738E82C53E408D21C968B3EAA15518249BF4894E21BDF1C8BA
2024-02-11 19:51:05.695 [TRACE] [g.mideaac.internal.security.Security] - Sign:        B55311CD89E1EC28EF3BCEB1FC3CB38CADE0FE8AB370338750416CF00088B7D4
2024-02-11 19:51:05.695 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:      AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:51:05.696 [TRACE] [g.mideaac.internal.security.Security] - EncSignData: 4BF43BAD3E3E6E4C776BD3C5D8EAF2D1E164EF6A2E4637BF8FF0E9DC2A6C10BC09C498344D35245F0789E75A35E0FE5A73EC2F1DB1A268BE706ED61960EF9158994A5CA6B2AACE0960D13C7A90F33963C968967BE39A2F82EAD3E101B6C48418D24124AF7E2CDBB7DB819B426F93DDF7B55311CD89E1EC28EF3BCEB1FC3CB38CADE0FE8AB370338750416CF00088B7D4
2024-02-11 19:51:05.696 [TRACE] [g.mideaac.internal.security.Security] - Result:      8370008E20664BF43BAD3E3E6E4C776BD3C5D8EAF2D1E164EF6A2E4637BF8FF0E9DC2A6C10BC09C498344D35245F0789E75A35E0FE5A73EC2F1DB1A268BE706ED61960EF9158994A5CA6B2AACE0960D13C7A90F33963C968967BE39A2F82EAD3E101B6C48418D24124AF7E2CDBB7DB819B426F93DDF7B55311CD89E1EC28EF3BCEB1FC3CB38CADE0FE8AB370338750416CF00088B7D4
2024-02-11 19:51:05.836 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 150
2024-02-11 19:51:05.836 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: 8370008E2063AC99C08213F3021DF49574C66A717E06AE0DCDD9F63D9EAD48C4558F58811A811DF43CC07F2E706A98B3B1DE2FFC6F811A52D87FFDA43546BA0220BDDFB5EFB4561894C64DD051A0BD8A0D51C3E90F099270E49FF039707DE4BD40C607CE3E3BD7674E273F456D7394200ED02597F35E84AF1EDCE88B8DD38613E2455458BC20C1796D54C5B8AF9B7FEC25D7D91FA378
2024-02-11 19:51:05.837 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:5a3ba29334 from OFFLINE(COMMUNICATION_ERROR) to ONLINE
2024-02-11 19:51:05.838 [TRACE] [g.mideaac.internal.security.Security] - Header:        8370008E2063
2024-02-11 19:51:05.838 [TRACE] [g.mideaac.internal.security.Security] - Size: 150
2024-02-11 19:51:05.839 [TRACE] [g.mideaac.internal.security.Security] - Padding: 6
2024-02-11 19:51:05.839 [TRACE] [g.mideaac.internal.security.Security] - MsgType: MSGTYPE_ENCRYPTED_RESPONSE
2024-02-11 19:51:05.840 [TRACE] [g.mideaac.internal.security.Security] - Sign:        84AF1EDCE88B8DD38613E2455458BC20C1796D54C5B8AF9B7FEC25D7D91FA378
2024-02-11 19:51:05.840 [TRACE] [g.mideaac.internal.security.Security] - SignLocal:   84AF1EDCE88B8DD38613E2455458BC20C1796D54C5B8AF9B7FEC25D7D91FA378
2024-02-11 19:51:05.841 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:      AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:51:05.841 [TRACE] [g.mideaac.internal.security.Security] - Data:        04025A5A011168002080000000000000000000000000D5CA0100008300000000000000000000000000009BFA18B38F323BDE46315D57F4FAC2494177AC899D040473F9950341472F612B5648B66171FB61398ADA6EE239F453CE1A8F16092C20FCF2E5385B56404480D2EE3228945AC1
2024-02-11 19:51:05.841 [TRACE] [g.mideaac.internal.security.Security] - Response_count: 1026
2024-02-11 19:51:05.842 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response length: 104
2024-02-11 19:51:05.842 [TRACE] [ler.MideaACHandler$ConnectionManager] - Packet: 8370008E2063AC99C08213F3021DF49574C66A717E06AE0DCDD9F63D9EAD48C4558F58811A811DF43CC07F2E706A98B3B1DE2FFC6F811A52D87FFDA43546BA0220BDDFB5EFB4561894C64DD051A0BD8A0D51C3E90F099270E49FF039707DE4BD40C607CE3E3BD7674E273F456D7394200ED02597F35E84AF1EDCE88B8DD38613E2455458BC20C1796D54C5B8AF9B7FEC25D7D91FA378
2024-02-11 19:51:05.843 [TRACE] [ler.MideaACHandler$ConnectionManager] - Bytes decoded and stripped without header: length: 26, data: C0008E667F7F003300000068FF1200040000000000000005B114
2024-02-11 19:51:05.843 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-02-11 19:51:07.830 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Midea_Air_Conditioner_Power' received command OFF
2024-02-11 19:51:07.832 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Midea_Air_Conditioner_Power' predicted to become OFF
2024-02-11 19:51:07.835 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Midea_Air_Conditioner_Power' changed from ON to OFF
2024-02-11 19:51:08.094 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.
2024-02-11 19:51:07.841 [DEBUG] [eaac.internal.handler.MideaACHandler] - Handling channelUID power with command OFF
2024-02-11 19:51:07.842 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:5a3ba29334 from ONLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2024-02-11 19:51:15.986 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:5a3ba29334' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. to ONLINE
2024-02-11 19:51:15.844 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:5a3ba29334 at IP 192.168.10.100
2024-02-11 19:51:15.844 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:15.844 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check OK for mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:15.844 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Requesting status update from mideaac:ac:5a3ba29334 at 192.168.10.100
2024-02-11 19:51:15.845 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:5a3ba29334 at 192.168.10.100 bytes.length: 104, bytes: 5A5A011168002000000000000118010B13330F00D5CA0100008300000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BD8843C397DEAD052D9DAE3B48BF3B3B56CA53BB8C5A00C97CBBFA3FE254FFE83C085F90ABF9FEE3A28825229742FE87E
2024-02-11 19:51:15.845 [TRACE] [g.mideaac.internal.security.Security] - Size: 104
2024-02-11 19:51:15.845 [TRACE] [g.mideaac.internal.security.Security] - Padding size: 6, size: 142
2024-02-11 19:51:15.845 [TRACE] [g.mideaac.internal.security.Security] - Header:      8370008E2066
2024-02-11 19:51:15.846 [TRACE] [g.mideaac.internal.security.Security] - Data:        01225A5A011168002000000000000118010B13330F00D5CA0100008300000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BD8843C397DEAD052D9DAE3B48BF3B3B56CA53BB8C5A00C97CBBFA3FE254FFE83C085F90ABF9FEE3A28825229742FE87E5BB297FE99B8
2024-02-11 19:51:15.846 [TRACE] [g.mideaac.internal.security.Security] - Sign:        746440A7AC8B2B097DD1839D1675C80E3B832C94039C17E62716FF562B2ADCC5
2024-02-11 19:51:15.846 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:      AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:51:15.846 [TRACE] [g.mideaac.internal.security.Security] - EncSignData: B5109A4A483410838FA3B7DC0DEB87E5052C72B54BB468821ACF2AECCC8DB82B24797537B10B78F52EB0209CBA071288E7AC3E8CDB7F5FB3387A779AEBB77D64513CF0001B5A6577A56BD184939CF71039F7AB17ADB30FB8878ADB95D235BD3C822354ACB566099F64A2D95DF9BB440D746440A7AC8B2B097DD1839D1675C80E3B832C94039C17E62716FF562B2ADCC5
2024-02-11 19:51:15.846 [TRACE] [g.mideaac.internal.security.Security] - Result:      8370008E2066B5109A4A483410838FA3B7DC0DEB87E5052C72B54BB468821ACF2AECCC8DB82B24797537B10B78F52EB0209CBA071288E7AC3E8CDB7F5FB3387A779AEBB77D64513CF0001B5A6577A56BD184939CF71039F7AB17ADB30FB8878ADB95D235BD3C822354ACB566099F64A2D95DF9BB440D746440A7AC8B2B097DD1839D1675C80E3B832C94039C17E62716FF562B2ADCC5
2024-02-11 19:51:15.984 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 150
2024-02-11 19:51:15.985 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: 8370008E20630CEF8027822BDFD3706F24E098CB2AE0DA2FEA193C919BF07154DF5CF8A94FA80CF68B866BA0354B5B6F1C4FDC3C881CF302902CBCD7220B48CE5918EDB03AD09661B298A2F835AD8B32767F817842CF2601FD89261E07CE08B1C8E5385DCD23036E5DB30677C3A7665F05FC87C0F6F8862A8527C5BFD154E100A5D0F9B244967FCD909044BDFDB82B34684F1824B7C0
2024-02-11 19:51:15.985 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:5a3ba29334 from OFFLINE(COMMUNICATION_ERROR) to ONLINE
2024-02-11 19:51:15.985 [TRACE] [g.mideaac.internal.security.Security] - Header:        8370008E2063
2024-02-11 19:51:15.986 [TRACE] [g.mideaac.internal.security.Security] - Size: 150
2024-02-11 19:51:15.986 [TRACE] [g.mideaac.internal.security.Security] - Padding: 6
2024-02-11 19:51:15.986 [TRACE] [g.mideaac.internal.security.Security] - MsgType: MSGTYPE_ENCRYPTED_RESPONSE
2024-02-11 19:51:15.986 [TRACE] [g.mideaac.internal.security.Security] - Sign:        862A8527C5BFD154E100A5D0F9B244967FCD909044BDFDB82B34684F1824B7C0
2024-02-11 19:51:15.987 [TRACE] [g.mideaac.internal.security.Security] - SignLocal:   862A8527C5BFD154E100A5D0F9B244967FCD909044BDFDB82B34684F1824B7C0
2024-02-11 19:51:15.987 [TRACE] [g.mideaac.internal.security.Security] - TcpKey:      AB8E7DF10DF432AC11D613C4939B6BDD1EAABDF257513768C6A26D229429D563
2024-02-11 19:51:15.987 [TRACE] [g.mideaac.internal.security.Security] - Data:        04035A5A011168002080000000000000000000000000D5CA0100008300000000000000000000000000009BFA18B38F323BDE46315D57F4FAC2494177AC899D040473F9950341472F612B5B4F2225AD147F3C6FD761AD9AC2B3173B464C57CC7E68744BBF5311969ABFC9BDFBB88C0708
2024-02-11 19:51:15.987 [TRACE] [g.mideaac.internal.security.Security] - Response_count: 1027
2024-02-11 19:51:15.987 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response length: 104
2024-02-11 19:51:15.987 [TRACE] [ler.MideaACHandler$ConnectionManager] - Packet: 8370008E20630CEF8027822BDFD3706F24E098CB2AE0DA2FEA193C919BF07154DF5CF8A94FA80CF68B866BA0354B5B6F1C4FDC3C881CF302902CBCD7220B48CE5918EDB03AD09661B298A2F835AD8B32767F817842CF2601FD89261E07CE08B1C8E5385DCD23036E5DB30677C3A7665F05FC87C0F6F8862A8527C5BFD154E100A5D0F9B244967FCD909044BDFDB82B34684F1824B7C0
2024-02-11 19:51:15.988 [TRACE] [ler.MideaACHandler$ConnectionManager] - Bytes decoded and stripped without header: length: 26, data: C0008E667F7F003300000068FF120004000000000000000FCFEC
2024-02-11 19:51:15.988 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!

Sorry it is my fault. Accidentally, I left a debog log entry in it. Please ignore it.

It clearly appears that you are receiving inappropriate-sized data packets from the device. What is the USB dongle hardware version?