New OH3 Binding - Midea Air Conditioning (LAN)

Ok, thanks. I try figuring out what does “already connected” means in this particular case. @atyec89 got the same error. I’ll revert soon.

I thank you for your commitment

Background: Recently installed Cooper & Hunter split AC with the WiFi dongle. Searching internet found this (and many other split ACs) are manufactured by Gree or Midea. Did download WiFi app from Cooper & Hunter first (Apple Store) and worked. In email exchange with Cooper & Hunter about integrations, they suggested NetHome Plus as better able to integrate with Alexa, etc. This also works, but not with OH.

With OH, I tried using the Gree binding first with no success and then started searching the OH forum for Midea and found this thread and one other of interest. Used the Python program referenced in that thread and posted above (around 220 on Jan 7) successfully but could not see how to use the output in OH (see below). Then tried the latest binding in this thread (details below). Hopefully the observations will help with the binding development or with a first time user.

General observations: (note did not read through all the posts, so likely missed somethings.)

Python app
Used my WSL test environment to run the python program and get the TOKEN and KEY. Encountered some problems about the PATH$ but was able to resolve with MS Copilot.
midea-beautiful-air-cli discover --account ACCOUNT --password PASSWORD --address IP –credential
OUTPUT from App

id 000000P0000000Q1B88C295643BC0000/151732605161920
  id      = 151732605161920
  addr    = 192.168.0.246
  s/n     = 000000P0000000Q1B88C295643BC0000
  model   = Air conditioner
  ssid    = net_ac_43BC
  online  = True
  name    = AirCon_43BC
  running = False
  target  = 18.0
  indoor  = 20.0
  outdoor = 22.5
  fan     = 102
  mode    = 2
  purify  = False
  eco     = False
  sleep   = False
  frost   = False
  comfort = False
  F       = True
  error   = 0
  supports= {'eco': 1, 'heat_8': 1, 'mode': 1, 'fan_swing': 1, 'electricity': 1, 'filter_reminder': 0, 'strong_fan': 1}
  version = 3
  token   = TOKEN
  key     = KEY

Also was able to use the set command the turn it on and change the setpoint.

midea-beautiful-air-cli set --ip 192.168.0.246 --token TOKEN --key KEY --running True
midea-beautiful-air-cli set --ip 192.168.0.246 --token TOKEN --key KEY --target-temperature 17.0

Midea Air Conditioning (LAN) binding
Added the last binding in this thread (post 255). Added the TOKEN and KEY from the Python app. Left the Cloud provider, email and password blank. Disabled the Reauthorization. Everything seemed to work initially.

I noticed a lot of event traffic on the developer tool bar so tried to change the polling time to 600 seconds. The next time I checked the device was UNKNOWN and I was concerned the TOKEN and KEY were the problem as possibly expired?. The log entries at the DEBUG level (with the bytes as BYTES).

2024-05-04 20:40:51.556 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Disconnecting from mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-04 20:40:51.566 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-05-04 20:40:51.567 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-05-04 20:40:51.568 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-04 20:40:51.569 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:5fe6116d01 from UNKNOWN(NONE) to ONLINE
2024-05-04 20:40:51.570 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5fe6116d01@192.168.0.246 require authentication, going to authenticate
2024-05-04 20:40:51.574 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:5fe6116d01@192.168.0.246 authenticating
2024-05-04 20:40:56.614 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 72
2024-05-04 20:40:56.616 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: BYTES
2024-05-04 20:40:56.619 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Authentication successufull
2024-05-04 20:40:57.621 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:5fe6116d01 at 192.168.0.246 bytes.length: 104, bytes: BYTES
2024-05-04 20:41:02.624 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 150
2024-05-04 20:41:02.625 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: BYTES
2024-05-04 20:41:02.626 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response length: 104
2024-05-04 20:41:02.654 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-04 20:41:02.659 [DEBUG] [eaac.internal.handler.MideaACHandler] - MideaACHandler config for mideaac:ac:5fe6116d01 is org.openhab.binding.mideaac.internal.MideaACConfiguration@19d7e40
2024-05-04 20:41:02.662 [DEBUG] [eaac.internal.handler.MideaACHandler] - Configuration valid for mideaac:ac:5fe6116d01
2024-05-04 20:41:02.663 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPAddress: 192.168.0.246
2024-05-04 20:41:02.665 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPPort: 6444
2024-05-04 20:41:02.667 [DEBUG] [eaac.internal.handler.MideaACHandler] - ID: -129742371548736
2024-05-04 20:41:02.668 [DEBUG] [eaac.internal.handler.MideaACHandler] - Version: 3
2024-05-04 20:41:12.656 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check OK for mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-04 20:41:12.658 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Requesting status update from mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-04 20:41:12.660 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:5fe6116d01 at 192.168.0.246 bytes.length: 104, bytes: BYTES
2024-05-04 20:41:12.662 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.NullPointerException: Cannot read the array length because "bytes" is null
at org.openhab.binding.mideaac.internal.Utils.bytesToHex(Utils.java:23) ~[?:?]
at org.openhab.binding.mideaac.internal.security.Security.encode_8370(Security.java:231) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.sendCommand(MideaACHandler.java:1000) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.requestStatus(MideaACHandler.java:966) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.checkConnection(MideaACHandler.java:1262) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.lambda$0(MideaACHandler.java:713) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]

I had other things to do, so did not investigate further, but changed the polling time back to 10 seconds.
The next day, with an OH restarts (for other reasons) everything is ONLINE. Logs were at INFO level

2024-05-05 09:58:49.059 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-05-05 09:58:49.062 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-05-05 09:58:49.065 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-05 09:58:53.923 [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing 'mideaac:ac:5fe6116d01' takes more than 5000ms.
And today
2024-05-06 08:41:00.979 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-05-06 08:41:00.981 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-05-06 08:41:00.984 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:5fe6116d01 at 192.168.0.246
2024-05-06 08:41:06.003 [WARN ] [core.thing.internal.ThingManagerImpl] - Initializing handler for thing 'mideaac:ac:5fe6116d01' takes more than 5000ms.

Again overall it is working for my Cooper & Hunter split AC, but my guess is there is some interaction I don’t yet understand between the polling frequency and the device becoming unknown. Also the WARN message from the good startups indicate it takes a while for the device to come online. I sometimes get that WARN message with other bindings during OH startups as a lot of action is occurring. This is running on an Rpi3b.

Java Error during new installation

  • I have a fresh openhab 4.1.2 on debian 12.
  • I have copied the org.openhab.binding.mideaac-4.1.0-SNAPSHOT.jar (from zdanhauser, Apr21) to /usr/share/openhab/addons/
  • mideaac bindig has installed fine …
  • msmart-ng works fine as well

But when I try to create a new thing (with IP, DevicID or 0, Token, Key ), the new thing remains “UNINITIALIZED” with HANDLER_REGISTERING_ERROR

16:56:35.081 [ERROR] [.core.thing.internal.ThingManagerImpl] - Exception occurred while calling thing handler factory 'org.openhab.binding.mideaac.internal.MideaACHandlerFactory@1e6365e7': MideaACHandlerFactory could not create a handler for the thing 'mideaac:ac:04a575ae60'.
java.lang.IllegalStateException: MideaACHandlerFactory could not create a handler for the thing 'mideaac:ac:04a575ae60'.
        at org.openhab.core.thing.binding.BaseThingHandlerFactory.registerHandler(BaseThingHandlerFactory.java:131) ~[?:?]
        at org.openhab.core.thing.internal.ThingManagerImpl.doRegisterHandler(ThingManagerImpl.java:531) ~[?:?]
        at org.openhab.core.thing.internal.ThingManagerImpl.registerHandler(ThingManagerImpl.java:512) ~[?:?]
        at org.openhab.core.thing.internal.ThingManagerImpl.registerAndInitializeHandler(ThingManagerImpl.java:927) ~[?:?]
        at org.openhab.core.thing.internal.ThingManagerImpl.setEnabled(ThingManagerImpl.java:1009) ~[?:?]
        at org.openhab.core.io.rest.core.internal.thing.ThingResource.setEnabled(ThingResource.java:609) ~[?:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
        at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
        at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) ~[bundleFile:3.6.2]
        at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) ~[bundleFile:3.6.2]
        at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:201) ~[bundleFile:3.6.2]
        at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:104) ~[bundleFile:3.6.2]
        at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) ~[bundleFile:3.6.2]
        at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) ~[bundleFile:3.6.2]
        at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:265) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:225) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:304) ~[bundleFile:3.6.2]
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPut(AbstractHTTPServlet.java:234) ~[bundleFile:3.6.2]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:520) ~[bundleFile:4.0.4]
        at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:279) ~[bundleFile:3.6.2]
        at org.ops4j.pax.web.service.spi.servlet.OsgiInitializedServlet.service(OsgiInitializedServlet.java:102) ~[bundleFile:?]
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1656) ~[bundleFile:9.4.52.v20230823]
        at org.ops4j.pax.web.service.spi.servlet.OsgiFilterChain.doFilter(OsgiFilterChain.java:100) ~[bundleFile:?]
        at org.ops4j.pax.web.service.jetty.internal.PaxWebServletHandler.doHandle(PaxWebServletHandler.java:320) ~[bundleFile:?]
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:234) ~[bundleFile:9.4.52.v20230823]
        at org.ops4j.pax.web.service.jetty.internal.PrioritizedHandlerCollection.handle(PrioritizedHandlerCollection.java:96) ~[bundleFile:?]
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:722) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487) ~[bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.52.v20230823]
        at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.52.v20230823]
        at java.lang.Thread.run(Thread.java:840) [?:?]
16:56:35.085 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:04a575ae60' changed from UNINITIALIZED (HANDLER_REGISTERING_ERROR): MideaACHandlerFactory could not create a handler for the thing 'mideaac:ac:04a575ae60'. to UNINITIALIZED (HANDLER_MISSING_ERROR)

What am I missing? Thanks for your help!

Hello,

my config is OpenHab 4.1.2 on ubuntu 22.04. I tryed this binding, version 4.1.0.
I have two midea AC split. The older one use v2 protocol and seems it works with no issue.
The newest one use the v3 protocol. With this one I also have the OFFLINE/error, and the “Response data is not 25 long!” message.

Did I do something wrong?
I can change some values/config if it can help to find the cause.
Below some logs.

Thank you for your committment. It is a great work.

2024-05-21 17:15:17.073 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:15:34.074 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:15:51.075 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:16:08.563 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:16:25.563 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:16:42.564 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:16:59.564 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:17:17.946 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_1_125__18151693380281__net_ac_2c0a from ONLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2024-05-21 17:17:45.197 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_1_125__18151693380281__net_ac_2c0a from OFFLINE(COMMUNICATION_ERROR) to OFFLINE(COMMUNICATION_ERROR)
2024-05-21 17:17:45.454 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-05-21 17:17:45.455 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-05-21 17:17:45.455 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_1_125__18151693380281__net_ac_2c0a at 192.168.1.125
2024-05-21 17:18:00.455 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:18:18.209 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:18:35.210 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:18:52.960 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:19:11.537 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:19:28.537 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:19:46.123 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:20:03.123 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_1_125__18151693380281__net_ac_2c0a from ONLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2024-05-21 17:20:31.562 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_1_125__18151693380281__net_ac_2c0a from OFFLINE(COMMUNICATION_ERROR) to OFFLINE(COMMUNICATION_ERROR)
2024-05-21 17:20:31.819 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-05-21 17:20:31.820 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-05-21 17:20:31.820 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_1_125__18151693380281__net_ac_2c0a at 192.168.1.125
2024-05-21 17:20:46.820 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:21:03.821 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:21:20.822 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-05-21 17:21:37.822 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!

Hi all
I don’t understand what midea air conditioner v2 and v3 mean?
Is MIDEA AURORA 3 MSAX-09N8D0-C Inverter supported?

V3 has encryption, V2 does not.

Yes, with my AC V3 I can also query/set the AC status with ‘midea-beautiful-air-cli’ using the TOKEN/KEY.

i have same problem, did you risolved it?

No, I’m sorry. I’m unable to control the AC split V3 with openhab at the moment.