For version 3 Token and Key must be provided. It can be automatically obtained from Cloud by entering email and password for MSmartHome, not Midea Air!. Not need to add devices in MSmartHome, only creating account and logging in is required.
Swing mode is not supported for v3 (neither cloud nor LAN protocol)
Many thanks for @justaoldman for contribution: protocol verification, device via VPN sharing, tests and many more
Tested on openHAB 3.2.0 - Release Build
Thanks for this binding, really happy with it.
Unfortunately, I do have some issues getting it working. Could you take a look to the logs?
Used both auto discovery and a manual creating Thing.
When I use my manual created Thing, the following logs are shown:
2021-02-09 22:37:19.783 [DEBUG] [eaac.internal.handler.MideaACHandler] - MideaACHandler config for mideaac:ac:2af1d3ba53 is org.openhab.binding.mideaac.internal.MideaACConfiguration@a68dc6
2021-02-09 22:37:19.789 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPAddress: 192.168.0.134
2021-02-09 22:37:19.790 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPPort: 6444
2021-02-09 22:37:19.793 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-09 22:37:19.799 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:19.800 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNKNOWN(NONE) to ONLINE
2021-02-09 22:37:19.812 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A0111680020000000000001150109162513008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BC34434DCF8B3D50C422CC227583DA33AFCA5CF91D6D609EF6FBF6E4BFE2E934021D528ABA84EADA753AF458B2B8264BD
2021-02-09 22:37:19.767 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2021-02-09 22:37:19.792 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from INITIALIZING to UNKNOWN
2021-02-09 22:37:19.807 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from UNKNOWN to ONLINE
2021-02-09 22:37:23.814 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Disconnecting from mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:23.815 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from ONLINE(NONE) to OFFLINE
2021-02-09 22:37:23.817 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from OFFLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2021-02-09 22:37:24.070 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:23.818 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from ONLINE to OFFLINE
2021-02-09 22:37:23.820 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from OFFLINE to UNKNOWN
2021-02-09 22:37:24.072 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Read timed out
2021-02-09 22:37:34.072 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:2af1d3ba53 at IP 192.168.0.134
2021-02-09 22:37:34.084 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:34.085 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:34.088 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-09 22:37:34.091 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:34.092 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from OFFLINE(COMMUNICATION_ERROR) to ONLINE
2021-02-09 22:37:34.093 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:37:34.096 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A0111680020000000000001150109162522008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BB8FD313676651C24F6A79E1ED661AE4751A1911793778FEBE1BFC0B33F600E14FA797D3595E90CF8371F46988AC56BDA
2021-02-09 22:37:34.097 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from OFFLINE (COMMUNICATION_ERROR): Read timed out to ONLINE
When I do use auto-discovery now the following errors are shown:
2021-02-09 22:38:49.405 [DEBUG] [al.discovery.MideaACDiscoveryService] - Stop scan for Midea AC devices.
2021-02-09 22:38:49.455 [DEBUG] [al.discovery.MideaACDiscoveryService] - Start scan for Midea AC devices.
2021-02-09 22:38:49.457 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 6445
2021-02-09 22:38:49.459 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 20086
2021-02-09 22:38:49.460 [DEBUG] [al.discovery.MideaACDiscoveryService] - Midea AC device discovery returned package with length 192
2021-02-09 22:38:49.462 [DEBUG] [al.discovery.MideaACDiscoveryService] - Midea AC discover data (192) from 192.168.0.134: '837000B8200F04165A5A0111A8007A800000000000000000000000008F7A00000012000000000000000000000000000047932C79C0D562B61613413CE63185AA7C5179B1DE29DA3850D76D9BEB6696C47334F12E1B1BBE130E804BF44E734F15387CE42D8219955D5CDD4D1D89EA7042D95A234C982BBD7E2E4FD984AACE85051FCA94541303884C52E880DDEFC03190F31443D17C3AAC03A7656614AE1DCA4492D862B4969D333100415C58A4FC2A259ED437779EFC49135EB2D2E1D8AB492D'
2021-02-09 22:38:49.463 [TRACE] [al.discovery.MideaACDiscoveryService] - Device supported
2021-02-09 22:38:49.467 [TRACE] [al.discovery.MideaACDiscoveryService] - Version: 3
2021-02-09 22:38:49.468 [TRACE] [al.discovery.MideaACDiscoveryService] - Id Bytes: 000000000000
2021-02-09 22:38:49.470 [DEBUG] [al.discovery.MideaACDiscoveryService] - Id: '0'
2021-02-09 22:38:49.471 [DEBUG] [al.discovery.MideaACDiscoveryService] - Encrypt data: '000000000000000047932C79C0D562B61613413CE63185AA7C5179B1DE29DA3850D76D9BEB6696C47334F12E1B1BBE130E804BF44E734F15387CE42D8219955D5CDD4D1D89EA7042D95A234C982BBD7E2E4FD984AACE85051FCA94541303884C52E880DDEFC03190F31443D17C3AAC03A7656614AE1DCA4492D862B4969D333100415C58A4FC2A25'
2021-02-09 22:38:49.487 [ERROR] [nternal.DiscoveryServiceRegistryImpl] - Cannot trigger scan for thing types '[mideaac:ac]' on 'MideaACDiscoveryService'!
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.thingDiscovered(MideaACDiscoveryService.java:196) ~[?:?]
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.discoverThings(MideaACDiscoveryService.java:103) ~[?:?]
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.startScan(MideaACDiscoveryService.java:73) ~[?:?]
2021-02-09 22:38:58.276 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:2af1d3ba53 at IP 192.168.0.134
2021-02-09 22:38:58.277 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:38:58.278 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:38:58.279 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-09 22:38:58.281 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:38:58.282 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNINITIALIZED(DISABLED) to ONLINE
2021-02-09 22:38:58.283 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-02-09 22:38:58.284 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:38:58.286 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010916263A008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BDE4F2B588DC2921FDDF07250DB6C06B34D05A824584A61AFE6A47C30DB38097929A336B3995162575D469785AEF532CB
2021-02-09 22:39:02.290 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Disconnecting from mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-09 22:39:02.300 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNINITIALIZED(DISABLED) to OFFLINE(COMMUNICATION_ERROR)
Thanks! Did try the new version, the reported logs are changed. The DeviceID is now reported back (removed this from the log).
When using auto-discovery the logs tell:
2021-02-10 21:10:46.982 [DEBUG] [al.discovery.MideaACDiscoveryService] - Stop scan for Midea AC devices.
2021-02-10 21:10:46.988 [DEBUG] [al.discovery.MideaACDiscoveryService] - Start scan for Midea AC devices.
2021-02-10 21:10:46.990 [TRACE] [al.discovery.MideaACDiscoveryService] - Discovering: 255.255.255.255
2021-02-10 21:10:46.993 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 6445
2021-02-10 21:10:46.995 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 20086
2021-02-10 21:10:46.999 [DEBUG] [al.discovery.MideaACDiscoveryService] - Midea AC device discovery returned package with length 192
2021-02-10 21:10:47.002 [DEBUG] [al.discovery.MideaACDiscoveryService] - Midea AC discover data (192) from 192.168.0.134: '837000B8200F04365A5A0111A8007A800000000000000000000000008F7A00000012000000000000000000000000000047932C79C0D562B61613413CE63185AA7C5179B1DE29DA3850D76D9BEB6696C47334F12E1B1BBE130E804BF44E734F15387CE42D8219955D5CDD4D1D89EA7042D95A234C982BBD7E2E4FD984AACE85051FCA94541303884C52E880DDEFC03190F31443D17C3AAC03A7656614AE1DCA4492D862B4969D333100415C58A4FC2A259ED437779EFC49135EB2D2E1D8AB492D'
2021-02-10 21:10:47.003 [TRACE] [al.discovery.MideaACDiscoveryService] - Device supported
2021-02-10 21:10:47.005 [TRACE] [al.discovery.MideaACDiscoveryService] - Version: 3
2021-02-10 21:10:47.006 [TRACE] [al.discovery.MideaACDiscoveryService] - Id Bytes: xxxxxxx
2021-02-10 21:10:47.023 [DEBUG] [al.discovery.MideaACDiscoveryService] - Id: 'xxxxxxx'
2021-02-10 21:10:47.025 [DEBUG] [al.discovery.MideaACDiscoveryService] - Encrypt data: '47932C79C0D562B61613413CE63185AA7C5179B1DE29DA3850D76D9BEB6696C47334F12E1B1BBE130E804BF44E734F15387CE42D8219955D5CDD4D1D89EA7042D95A234C982BBD7E2E4FD984AACE85051FCA94541303884C52E880DDEFC03190F31443D17C3AAC03A7656614AE1DCA4492D862B4969D3331'
2021-02-10 21:10:47.036 [ERROR] [nternal.DiscoveryServiceRegistryImpl] - Cannot trigger scan for thing types '[mideaac:ac]' on 'MideaACDiscoveryService'!
java.lang.NullPointerException: null
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.discoveryPacketReceived(MideaACDiscoveryService.java:252) ~[?:?]
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.thingDiscovered(MideaACDiscoveryService.java:207) ~[?:?]
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.discoverThings(MideaACDiscoveryService.java:107) ~[?:?]
at org.openhab.binding.mideaac.internal.discovery.MideaACDiscoveryService.startScan(MideaACDiscoveryService.java:77) ~[?:?]
at org.openhab.core.config.discovery.AbstractDiscoveryService.startScan(AbstractDiscoveryService.java:194) ~[bundleFile:?]
at org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl.startScan(DiscoveryServiceRegistryImpl.java:377) [bundleFile:?]
at org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl.startScans(DiscoveryServiceRegistryImpl.java:362) [bundleFile:?]
at org.openhab.core.config.discovery.internal.DiscoveryServiceRegistryImpl.startScan(DiscoveryServiceRegistryImpl.java:211) [bundleFile:?]
at org.openhab.core.io.rest.core.internal.discovery.DiscoveryResource.scan(DiscoveryResource.java:105) [bundleFile:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [bundleFile:1.0.9]
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [bundleFile:1.0.9]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:201) [bundleFile:1.0.9]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:104) [bundleFile:1.0.9]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [bundleFile:1.0.9]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [bundleFile:1.0.9]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [bundleFile:1.0.9]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [bundleFile:1.0.9]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [bundleFile:1.0.9]
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [bundleFile:1.0.9]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [bundleFile:1.0.9]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [bundleFile:1.0.9]
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [bundleFile:1.0.9]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [bundleFile:1.0.9]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [bundleFile:1.0.9]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [bundleFile:3.1.0]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [bundleFile:1.0.9]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:852) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:544) [bundleFile:9.4.20.v20190813]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [bundleFile:?]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1581) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1307) [bundleFile:9.4.20.v20190813]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) [bundleFile:?]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:482) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1549) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1204) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [bundleFile:9.4.20.v20190813]
at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [bundleFile:?]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.Server.handle(Server.java:494) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:374) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:268) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) [bundleFile:9.4.20.v20190813]
at java.lang.Thread.run(Thread.java:834) [?:?]
When using manual created Thing:
2021-02-10 21:14:06.201 [DEBUG] [eaac.internal.handler.MideaACHandler] - MideaACHandler config for mideaac:ac:2af1d3ba53 is org.openhab.binding.mideaac.internal.MideaACConfiguration@26564f
2021-02-10 21:14:06.203 [DEBUG] [eaac.internal.handler.MideaACHandler] - Configuration valid for mideaac:ac:2af1d3ba53
2021-02-10 21:14:06.204 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPAddress: 192.168.0.134
2021-02-10 21:14:06.205 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPPort: 6444
2021-02-10 21:14:06.205 [DEBUG] [eaac.internal.handler.MideaACHandler] - ID: xxxxx
2021-02-10 21:14:06.207 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-10 21:14:06.213 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:06.215 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNKNOWN(NONE) to ONLINE
2021-02-10 21:14:06.226 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010A150E06008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BF295FCC1F4B9CE80E506AB2A879FE3C5A8A539F3DED2B04298069292E4AD666EB3BACF7400B7FBD6DB91C744D19F0C61
2021-02-10 21:14:06.183 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2021-02-10 21:14:06.208 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from INITIALIZING to UNKNOWN
2021-02-10 21:14:06.218 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from UNKNOWN to ONLINE
2021-02-10 21:14:10.232 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Disconnecting from mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:10.233 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from ONLINE(NONE) to OFFLINE
2021-02-10 21:14:10.235 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from OFFLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2021-02-10 21:14:10.488 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:10.236 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from ONLINE to OFFLINE
2021-02-10 21:14:10.238 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from OFFLINE to UNKNOWN
2021-02-10 21:14:10.489 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Read timed out
2021-02-10 21:14:20.490 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:2af1d3ba53 at IP 192.168.0.134
2021-02-10 21:14:20.492 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:20.492 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:20.495 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-10 21:14:20.498 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:20.499 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from OFFLINE(COMMUNICATION_ERROR) to ONLINE
2021-02-10 21:14:20.501 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-10 21:14:20.504 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010A150E14008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B243C759FEA50480FE9BA4C8F48883C98FF174AA9E74463E03EEDF2F22B80DA1EF5FA2CB5F9DD3EFDF18F3BA3D3AC3E50
2021-02-10 21:14:20.503 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:2af1d3ba53' changed from OFFLINE (COMMUNICATION_ERROR): Read timed out to ONLINE
Now the device seems to be discovered correct, only there are some errors. Channels are created but don’t work. Here the logs:
2021-02-11 17:50:29.548 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-02-11 17:50:29.549 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:33.447 [DEBUG] [al.discovery.MideaACDiscoveryService] - Stop scan for Midea AC devices.
2021-02-11 17:50:33.464 [DEBUG] [al.discovery.MideaACDiscoveryService] - Start scan for Midea AC devices.
2021-02-11 17:50:33.465 [TRACE] [al.discovery.MideaACDiscoveryService] - Discovering: 255.255.255.255
2021-02-11 17:50:33.471 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 6445
2021-02-11 17:50:33.472 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 20086
2021-02-11 17:50:33.572 [DEBUG] [al.discovery.MideaACDiscoveryService] - Midea AC device discovery returned package with length 192
2021-02-11 17:50:33.575 [DEBUG] [al.discovery.MideaACDiscoveryService] - Midea AC discover data (192) from 192.168.0.134: '837000B8200F04025A5A0111A8007A80000000000000000000000000xxxx000000000000000000000000000047932C79C0D562B61613413CE63185AA7C5179B1DE29DA3850D76D9BEB6696C47334F12E1B1BBE130E804BF44E734F15387CE42D8219955D5CDD4D1D89EA7042D95A234C982BBD7E2E4FD984AACE85051FCA94541303884C52E880DDEFC03190F31443D17C3AAC03A7656614AE1DCA4492D862B4969D333100415C58A4FC2A259ED437779EFC49135EB2D2E1D8AB492D'
2021-02-11 17:50:33.576 [TRACE] [al.discovery.MideaACDiscoveryService] - Device supported
2021-02-11 17:50:33.578 [TRACE] [al.discovery.MideaACDiscoveryService] - Version: 3
2021-02-11 17:50:33.579 [TRACE] [al.discovery.MideaACDiscoveryService] - Id Bytes: xxxx
2021-02-11 17:50:33.580 [DEBUG] [al.discovery.MideaACDiscoveryService] - Id: 'xxxx'
2021-02-11 17:50:33.582 [DEBUG] [al.discovery.MideaACDiscoveryService] - Encrypt data: '47932C79C0D562B61613413CE63185AA7C5179B1DE29DA3850D76D9BEB6696C47334F12E1B1BBE130E804BF44E734F15387CE42D8219955D5CDD4D1D89EA7042D95A234C982BBD7E2E4FD984AACE85051FCA94541303884C52E880DDEFC03190F31443D17C3AAC03A7656614AE1DCA44'
2021-02-11 17:50:33.588 [DEBUG] [al.discovery.MideaACDiscoveryService] - Length: 109, Reply: '8600A8C02C19000030303030303050303030303030305131353032444242353938414536303030300B6E65745F61635F384145360000000001000000040000000000AC00000000000000502DBB598AE6069FCD0300080103000000000000000000000000000000000000000000'
2021-02-11 17:50:33.589 [DEBUG] [al.discovery.MideaACDiscoveryService] - Reply: '���, xxxx
2021-02-11 17:50:33.591 [DEBUG] [al.discovery.MideaACDiscoveryService] - IP: '192.168.0.134'
2021-02-11 17:50:33.592 [DEBUG] [al.discovery.MideaACDiscoveryService] - Port: '6444'
2021-02-11 17:50:33.594 [DEBUG] [al.discovery.MideaACDiscoveryService] - SN: 'xxxx'
2021-02-11 17:50:33.595 [TRACE] [al.discovery.MideaACDiscoveryService] - SSID length: '11'
2021-02-11 17:50:33.596 [DEBUG] [al.discovery.MideaACDiscoveryService] - SSID: 'net_ac_XXX'
2021-02-11 17:50:33.597 [DEBUG] [al.discovery.MideaACDiscoveryService] - Type: 'ac'
2021-02-11 17:50:38.463 [DEBUG] [al.discovery.MideaACDiscoveryService] - Stop scan for Midea AC devices.
2021-02-11 17:50:39.551 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:2af1d3ba53 at IP 192.168.0.134
2021-02-11 17:50:39.552 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:39.552 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:39.553 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-11 17:50:39.556 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:39.558 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNINITIALIZED(HANDLER_MISSING_ERROR) to ONLINE
2021-02-11 17:50:39.559 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-02-11 17:50:39.560 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:39.561 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010B11322700xxxx00000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BA4CB06C3487AE47C7644A8DFD9233E2BDD915CEEC7BD6BB31E4330477192B2131D3BA64A8068682AFD2A8F027B802B12
2021-02-11 17:50:43.567 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Disconnecting from mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:43.568 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNINITIALIZED(HANDLER_MISSING_ERROR) to OFFLINE(COMMUNICATION_ERROR)
2021-02-11 17:50:43.569 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-02-11 17:50:43.570 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:53.571 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:2af1d3ba53 at IP 192.168.0.134
2021-02-11 17:50:53.576 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:53.578 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:53.579 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:2af1d3ba53 at 192.168.0.134:6444
2021-02-11 17:50:53.589 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:53.590 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:2af1d3ba53 from UNINITIALIZED(HANDLER_MISSING_ERROR) to ONLINE
2021-02-11 17:50:53.592 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-02-11 17:50:53.597 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:2af1d3ba53 at 192.168.0.134
2021-02-11 17:50:53.600 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:2af1d3ba53 at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010B11323500xxxx00000000000000000000000000006B000A76E27EED2C3647E57D8602DF8BF1CA5B02D25A8CDB0C30BE971FDB12777A6D2FD0AA2DBAC5227E569B8730A9F5A0778A9DA1B3A6A854498C9BC281F830
2021-02-11 17:50:57.245 [DEBUG] [eaac.internal.handler.MideaACHandler] - MideaACHandler config for mideaac:ac:mideaac__192_168_0_134__xxxx__net_ac_8ae6 is org.openhab.binding.mideaac.internal.MideaACConfiguration@1685412
Now the channels are created, when sending the power ON command the following error was shown:
2021-02-11 17:52:17.086 [DEBUG] [eaac.internal.handler.MideaACHandler] - Handling channelUID power with command ON
2021-02-11 17:52:17.092 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.mideaac.internal.handler.MideaACHandler@16fd235': null
at org.openhab.binding.mideaac.internal.handler.CommandSet.fromResponse(CommandSet.java:25) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler.handlePower(MideaACHandler.java:144) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler.handleCommand(MideaACHandler.java:123) ~[?:?]```
Manual creation of Thing shows same connection error.
You created a different topic, guess this was not the intention? Perhaps due to replying per mail.
On topic, the shown logs are the fulls logs, from start of scanning until firing a command. Only the deviceID I changed to xxxx, since this code can be used to take over the unit via internet. The discovered deviceID is correct.
The unit works fine via the NetHome Cloud and Midea app, never tried the HomeAssistant integration. I do not have an HA setup running. I might be able to put something into docker, but do not have any experience with HA.
I think somewhere in the check of the device is something going wrong. The device is shown ONLINE for about 10 seconds, then a communication error is shown.
Set-up also a separate docker based setup, which shows the following logs:
2021-02-11 20:19:20.253 [DEBUG] [al.discovery.MideaACDiscoveryService] - Stop scan for Midea AC devices.
2021-02-11 20:19:20.254 [DEBUG] [al.discovery.MideaACDiscoveryService] - Start scan for Midea AC devices.
2021-02-11 20:19:20.254 [TRACE] [al.discovery.MideaACDiscoveryService] - Discovering: 255.255.255.255
2021-02-11 20:19:20.254 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 6445
2021-02-11 20:19:20.255 [TRACE] [al.discovery.MideaACDiscoveryService] - Broadcast discovery package sent to port: 20086
2021-02-11 20:19:25.254 [DEBUG] [al.discovery.MideaACDiscoveryService] - Stop scan for Midea AC devices.
2021-02-11 20:21:04.017 [DEBUG] [eaac.internal.handler.MideaACHandler] - MideaACHandler config for mideaac:ac:e2424fcf5e is org.openhab.binding.mideaac.internal.MideaACConfiguration@5385fb36
2021-02-11 20:21:04.017 [DEBUG] [eaac.internal.handler.MideaACHandler] - Configuration valid for mideaac:ac:e2424fcf5e
2021-02-11 20:21:04.022 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPAddress: 192.168.0.134
2021-02-11 20:21:04.022 [DEBUG] [eaac.internal.handler.MideaACHandler] - IPPort: 6444
2021-02-11 20:21:04.022 [DEBUG] [eaac.internal.handler.MideaACHandler] - ID: *xxxxxxxxxxx*
2021-02-11 20:21:04.023 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:e2424fcf5e at 192.168.0.134:6444
2021-02-11 20:21:04.028 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:04.029 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:e2424fcf5e from UNKNOWN(NONE) to ONLINE
2021-02-11 20:21:04.030 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:e2424fcf5e at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010B141504008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B0A8B7738ED91D6762986FAB07EDBD00EC26C0BFB0278A35978BC4BE27A65AA398739E6924BC3AFC87D7C1FEFB9429D26
2021-02-11 20:21:08.036 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Disconnecting from mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:08.037 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:e2424fcf5e from ONLINE(NONE) to OFFLINE
2021-02-11 20:21:08.037 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:e2424fcf5e from OFFLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2021-02-11 20:21:08.289 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Starting connection monitor job in 10 seconds for mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:18.290 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:e2424fcf5e at IP 192.168.0.134
2021-02-11 20:21:18.291 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:18.291 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check FAILED for mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:18.292 [TRACE] [ler.MideaACHandler$ConnectionManager] - Connecting to mideaac:ac:e2424fcf5e at 192.168.0.134:6444
2021-02-11 20:21:18.294 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:18.295 [DEBUG] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:e2424fcf5e from OFFLINE(COMMUNICATION_ERROR) to ONLINE
2021-02-11 20:21:18.295 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Cancelling connection monitor job for mideaac:ac:e2424fcf5e at 192.168.0.134
2021-02-11 20:21:18.299 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:e2424fcf5e at 192.168.0.134 bytes.length: 104, bytes: 5A5A011168002000000000000115010B141512008F7A0000001200000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B5E41B98D2C559357BF4D969E4E51128683EFFAE6AB2599D19AEB1AF38245FCA77D1F74F9A088FECCF4399A313D340D0A```
Here you also see the check if the device is online fails.
I can test things if you like, but are not a developer unfortunately. Will try to set up the HA integration.
Well if your DeviceId is properly obtained then ok.
Looking on the log it seems that IP and port is correct, as it is connecting to device (TCP connection) properly.
After connecting status request message is sent, but there is no answer and then device goes to OFFLINE.
Every Polling Time interval (default 10s.) connection is checked again.
So my conclusion is there is something different in protocol to device with your version 3, so currently created either request status message or any other message (like changin power) there is no response from device.
As wrote before: my binding is based on python script which is supported in HomeAssistant: if you can check it and it is working there, then I can fix it. If not further more complicated investigation would be needed.
Hello Jacek!
I insttaled latest jar. It found my unit. I added it as a thing and added all the channels. After disabeling an enabeling it starts but then goes to uninitialized.
First of all, @JacekDob (and who else might have helped) thank you so much for this binding.
I was about to try some scripts I’ve found for some basic iteration, when I realized you released this binding 2 days before.
Since I’m not a skilled developer, not going to promise I can help with development, but I’m happy to help with any required Q&A.
Let me start with my experience.
Initially I had some issues finding my AC machines. I had to set up on manually. It worked.
After that, I forced another scan and all devices have shown up. Since then everything seems to be working nicely.
FYI, I’m using 5x duct machines, model MTIU-12FNXD0. External splitter model M5O-42FN8-Q.
Then for connectivity I use the LCAC KIT WI-FI.
But then, after few minutes warning shows and stops reporting.
2021-03-07 16:36:45.752 [TRACE] [ler.MideaACHandler$ConnectionManager] - Performing connection check for mideaac:ac:mideaac__192_168_1_130__12094627919834__net_ac_5c3b at IP 192.168.1.130
2021-03-07 16:36:45.755 [TRACE] [ler.MideaACHandler$ConnectionManager] - Checking status of connection for mideaac:ac:mideaac__192_168_1_130__12094627919834__net_ac_5c3b at 192.168.1.130
2021-03-07 16:36:45.757 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Connection check OK for mideaac:ac:mideaac__192_168_1_130__12094627919834__net_ac_5c3b at 192.168.1.130
2021-03-07 16:36:45.759 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Requesting status update from mideaac:ac:mideaac__192_168_1_130__12094627919834__net_ac_5c3b at 192.168.1.130
2021-03-07 16:36:45.762 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Writing to mideaac:ac:mideaac__192_168_1_130__12094627919834__net_ac_5c3b at 192.168.1.130 bytes.length: 104, bytes: 5A5A011168002000000000000115020710242D00DA370000000B00000000000000000000000000006B000A76E27EED2C3647E57D8602DF8B0D913A99AC66BBC2C031875985FEA665A6BD5E96EA81A1E4D966D532E6557AEE06B0AF055C9D1214C27F82B5E7C202BF
2021-03-07 16:36:45.765 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response received length: 176
2021-03-07 16:36:45.767 [DEBUG] [ler.MideaACHandler$ConnectionManager] - Response bytes: 5A5A011158004400DE4901000000000000000000DA370000000B000000000000000000000300000033EA990CBC3A488F0BC352DD7544A352D841DE54A76FF90C8AEEF193574829990C0D4BC13B22C0D48E8FF1807D7312735A5A011158004400E04901000000000000000000DA370000000B000000000000000000000300000033EA990CBC3A488F0BC352DD7544A352D841DE54A76FF90C8AEEF193574829996AABDDC31AEC2777B319A86300ECAD00
2021-03-07 16:36:45.772 [WARN ] [g.mideaac.internal.security.Security] - AES decryption error: IllegalBlockSizeException: Input length must be multiple of 16 when decrypting with padded cipher
at org.openhab.binding.mideaac.internal.handler.Response.<init>(Response.java:26) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.sendCommand(MideaACHandler.java:567) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.requestStatus(MideaACHandler.java:530) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.checkConnection(MideaACHandler.java:716) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.lambda$0(MideaACHandler.java:476) ~[?:?]
And if I change an item or command AC with remote , then binding also stops working, until restart…