I deleted the debug log, recompiled, and updated the downloadable JAR.
I’m experiencing that same issue as described by atyec89 even have two AC’s where both are having these issues.
Had these issues already in the OpenHAB 3 version, but somehow since the Openhab 4.1 and Smarthome transforming their platform the communication seems more bugged than before.
In some cases the devices responds well, but in other cases the device starts acting up, not reacting anymore and throws a lot of errors regarding the length of the data and the communication being lost due to a broken pipe:
That is with the V3 USB
To be exact, my AC’s have a:
Nethome Plus
EU-OSK103
These dongles have an imprint in the casing that says Smart kit
Dongle version 3, firmware version 3.0.8. I forgot to mention in my previous post, that, what is interesting, I was able to get it working with below version from @justaoldman.
Hovewer it is not stable.
After your comment I’ve also tried this binding and it does indeed seem more reactive to input. I see the occasional broken pipe message, but both my AC’s now can be properly controlled via OpenHAB.
Hi, I am sorry you are having problems but considering it was only to test with and confirm your device could connect and receive commands and also confirm that token and key work…
That is why it says pure rough for debug only!! @zdanhauser 's version is what you should be using for any continuous use. What I provided was just a test package and even I only use it to try and add/puzzle out some additional functions and quirks so it was never meant to be used long term.
I have removed it from my replies on blog to prevent further confusion. as well as pulled the jar off github the source files are still there if someone else wants to review the code or even stand up their own environment and compile their custom version to test with…
@justaoldman Hi! No problem, I was aware of it. I just wanted to highlight, that binding with my device could work, which means, that from my side probably settings were done properly.
I didn’t planned to use it continuously, but for debug purpose it was fine. Therefore thank you!
Many thanks for the new version of this binding.
I have used the old one, but since I updated to OH 4.x the old binding was not working.
Now I tried to use the new version from @zdanhauser, but after putting the .jar-file into openhabs addon directory i recognized a hugh load of the CPU that wont end.
So I took a look at the DEBUG logging of the mideaac binding and saw a flush of this message:
08:16:38.985 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554728 time(s)
08:16:38.985 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554729 time(s)
08:16:38.985 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554730 time(s)
08:16:38.985 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554731 time(s)
08:16:38.986 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554732 time(s)
08:16:38.986 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554733 time(s)
08:16:38.985 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 290660881 time(s)
08:16:39.008 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 290660882 time(s)
08:16:39.007 [INFO ] [dler.MideaACHandler$ConnectionManager] - Socket connection exception Socket closed. Try reconnection 293554734 time(s)
What I have still tried to fix it:
- Restart of the VM
- Restart of the openhab service
- Installation of a new midea thing
The binding is working so far. I’am able to control my air conditioner with the thing of the binding. And it seems more responsive as in the older version.
But the exception above increased the CPU usage from 2-4% up to 20-25%…
Has anybody an idea what I am doning wrong or whats the fault?
Hi all,
is just for air conditioners or support/will support also midea water heaters?
Hi,
This binding looks for a device type of AC so no I do not think the current version will work with a water heater.
1 Like
I also have the same problem, OH4 and binding 4.1.0. Furthermore, the air conditioners do not respond to commands. The thing is online, also throws interruptions every now and then, then goes crazy with that message and you have to restart OH. Has anyone managed to make it work?
I haven’t experienced the mentioned error, however, there were other TCP-related errors. (In case of weak WiFi connection, when the TCP connection encountered an error, the connection was not automatically restored.) I uploaded an updated JAR file that fixed these issues. Give it a try, it solved the errors for me.
2 Likes
Many thanks for your effort!
It seems better now. I’ll have an eye on it, but for the moment it’s working fine.
I’m still grappling with the issue of null/empty/wrong device responses. I’ve just compiled a version that appears to have significantly reduced these errors. Give it a try, but make sure to backup the previous plugin first.
updated, but I still get this message:
Response data is not 25 long!
and the association does not send commands
I am really sorry about that 
did not give it up, still working on it.
Hi, I’ve just discovered a logical issue in the code related to the order of method calls and have fixed it. Please give it a try. As demonstrated in the attached video capture, the plugin can now handle and survive null responses, and it will be online with the next poll. It can also survive a simulated access point problem.
Hello! Thanks for the work and for sharing! But unfortunetelly none of your last releases can solve my issue. Once I try to power on or off the device, getting an error “Device not responding with its status. Last response was null”
2024-04-21 19:29:58.532 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from OFFLINE (CONFIGURATION_ERROR): Token and Key missing in configuration. to ONLINE
2024-04-21 19:29:58.532 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from ONLINE to OFFLINE (CONFIGURATION_ERROR): Token and Key missing in configuration.
2024-04-21 19:29:58.535 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from OFFLINE (CONFIGURATION_ERROR): Token and Key missing in configuration. to UNKNOWN
2024-04-21 19:29:58.522 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-21 19:29:58.524 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-21 19:29:58.525 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d at 192.168.10.100
2024-04-21 19:29:58.527 [WARN ] [ler.MideaACHandler$ConnectionManager] - Device mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d@192.168.10.100 cannot authenticate, token and key missing
2024-04-21 19:30:24.860 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from UNKNOWN to ONLINE
2024-04-21 19:30:24.856 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-21 19:30:24.857 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-21 19:30:24.857 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d at 192.168.10.100
2024-04-21 19:30:35.866 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from ONLINE to UNKNOWN
2024-04-21 19:30:35.864 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
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:996) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.requestStatus(MideaACHandler.java:962) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.checkConnection(MideaACHandler.java:1253) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.lambda$0(MideaACHandler.java:712) ~[?:?]
2024-04-21 19:31:05.092 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from UNKNOWN to ONLINE
2024-04-21 19:31:05.088 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-21 19:31:05.089 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-21 19:31:05.089 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d at 192.168.10.100
2024-04-21 19:31:16.095 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from ONLINE to UNKNOWN
2024-04-21 19:31:16.093 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
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:996) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.requestStatus(MideaACHandler.java:962) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.checkConnection(MideaACHandler.java:1253) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.lambda$0(MideaACHandler.java:712) ~[?:?]
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:996) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.sendCommandAndMonitor(MideaACHandler.java:968) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.requestStatus(MideaACHandler.java:960) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler.handleCommand(MideaACHandler.java:220) ~[?:?]
2024-04-21 19:31:40.625 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'MideaAC_1_Power' received command ON
2024-04-21 19:31:40.627 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'MideaAC_1_Power' predicted to become NULL
2024-04-21 19:31:40.885 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null
2024-04-21 19:31:40.634 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d from UNKNOWN(NONE) to OFFLINE(COMMUNICATION_ERROR)
2024-04-21 19:33:20.397 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null to ONLINE
2024-04-21 19:33:20.393 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-21 19:33:20.394 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-21 19:33:20.395 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d at 192.168.10.100
2024-04-21 19:33:26.846 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'MideaAC_1_Power' received command ON
2024-04-21 19:33:26.848 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'MideaAC_1_Power' predicted to become ON
2024-04-21 19:33:26.852 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'MideaAC_1_Power' changed from NULL to ON
2024-04-21 19:33:27.101 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null
2024-04-21 19:33:26.850 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d from ONLINE(NONE) to OFFLINE(COMMUNICATION_ERROR)
2024-04-21 19:33:31.399 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null to ONLINE
2024-04-21 19:33:31.407 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from ONLINE to UNKNOWN (CONFIGURATION_PENDING): Configuration missing, discovery needed. Discovering...
2024-04-21 19:33:31.443 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from UNKNOWN (CONFIGURATION_PENDING): Configuration missing, discovery needed. Discovering... to ONLINE
2024-04-21 19:33:31.399 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-21 19:33:31.401 [WARN ] [eaac.internal.handler.MideaACHandler] - Configuration invalid for mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d
2024-04-21 19:33:31.401 [WARN ] [eaac.internal.handler.MideaACHandler] - Discovery needed, thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' is discovering....
2024-04-21 19:33:31.431 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-21 19:33:31.432 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-21 19:33:31.433 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d at 192.168.10.100
2024-04-21 19:33:42.437 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from ONLINE to UNKNOWN
2024-04-21 19:33:42.435 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-21 19:33:45.860 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'MideaAC_1_Power' received command OFF
2024-04-21 19:33:45.861 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'MideaAC_1_Power' predicted to become ON
2024-04-21 19:33:46.120 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null
2024-04-21 19:33:45.868 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_10_100__-137438953354539__net_ac_b20d from UNKNOWN(NONE) to OFFLINE(COMMUNICATION_ERROR)
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:996) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.requestStatus(MideaACHandler.java:962) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.checkConnection(MideaACHandler.java:1253) ~[?:?]
at org.openhab.binding.mideaac.internal.handler.MideaACHandler$ConnectionManager.lambda$0(MideaACHandler.java:712) ~[?:?]
updated. I also rebooted without binding, cleared the cache and inserted the new binding. I keep getting the same error: Response data is not 25 long!
and the item power does not respond and takes the binding offline. Could it be a bad token? I use this procedure: msmart-ng · PyPI
I also noticed that they often change IP addresses (but I think it’s a DHCP issue, which can be resolved by the router, it doesn’t worry me)
For more information, my version of OH is 4.1.2
I attach screenshots of the log
This does not tell me too much. What does this command say? “openhab-cli showlogs”
2024-04-23 15:25:59.878 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a from ONLINE(NONE) to OFFLINE class="highlight commError">(COMMUNICATION_ERROR)
2024-04-23 15:25:59.871 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'MideaAC__192_168_1_119__31885837312891__net_ac_D41A_Power' received command ON
2024-04-23 15:25:59.873 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'MideaAC__192_168_1_119__31885837312891__net_ac_D41A_Power' predicted to become ON
2024-04-23 15:25:59.875 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'MideaAC__192_168_1_119__31885837312891__net_ac_D41A_Power' changed from OFF to ON
2024-04-23 15:26:00.130 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null
2024-04-23 15:26:10.184 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-23 15:26:10.183 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status. Last response was null to ONLINE
2024-04-23 15:26:12.380 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-23 15:26:25.186 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-23 15:26:27.383 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
this is thepart of the log when I use the On/off option, below if I do nothing:
2024-04-23 15:27:37.939 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-23 15:27:37.940 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-23 15:27:37.941 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_1_154__31885837320281__net_ac_8de0 at 192.168.1.154
2024-04-23 15:27:37.643 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_154__31885837320281__net_ac_8de0' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.Response bytes is null. to UNKNOWN
2024-04-23 15:27:37.895 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_154__31885837320281__net_ac_8de0' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Broken pipe [sendCommand SocketException]
2024-04-23 15:27:37.943 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_154__31885837320281__net_ac_8de0' changed from OFFLINE (COMMUNICATION_ERROR): Broken pipe [sendCommand SocketException] to ONLINE
2024-04-23 15:27:48.944 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-23 15:27:50.447 [INFO ] [eaac.internal.handler.MideaACHandler] - Changing status of mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a from OFFLINE class="highlight commError">(COMMUNICATION_ERROR) to OFFLINE class="highlight commError">(COMMUNICATION_ERROR)
2024-04-23 15:27:50.448 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a' changed from OFFLINE (COMMUNICATION_ERROR): Device not responding with its status.Response bytes is null. to UNKNOWN
2024-04-23 15:27:50.752 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 1 time(s)
2024-04-23 15:27:50.752 [INFO ] [ler.MideaACHandler$ConnectionManager] - Socket connection exception already connected. Try reconnection 2 time(s)
2024-04-23 15:27:50.753 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a at 192.168.1.119
2024-04-23 15:27:50.700 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Broken pipe [sendCommand SocketException]
2024-04-23 15:27:50.755 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'mideaac:ac:mideaac__192_168_1_119__31885837312891__net_ac_d41a' changed from OFFLINE (COMMUNICATION_ERROR): Broken pipe [sendCommand SocketException] to ONLINE
2024-04-23 15:28:01.755 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!
2024-04-23 15:28:03.946 [ERROR] [ler.MideaACHandler$ConnectionManager] - Response data is not 25 long!```
I extracted the two main parts, also because it would be a continuous loop