I’ve been modifying the Midea binding code provided to me by @justaoldman for personal use. My original goal was to increase the polling frequency from 10 seconds. This was to reduce local Wi-Fi traffic and align with the OH default rrd4j persistence strategy. While testing locally and some testing also by @justaoldman and @Davide_Cencini differences in device responses and capabilities were uncovered. IMO that is going to make it difficult for one binding to cover all the bases for Midea (and Midea clones) split ACs. So, I’m going to offer up my beta version as an alternative to the one above. If your device is working fine on the @zdanhauser binding, great, no reason to change.
Besides the polling process, if supported by the device and the response bytes are in the expected order, the swing, sleep and turbo switches can be set. These all work for me on my recent V3 device (April 2024). The response byte restriction has been relaxed to greater than 21, instead of exactly 25 as this is one difference uncovered between devices. Data is only currently only read by the binding from the first 20 bytes anyway.
The current version is on my OH-addons fork as a release here. I have only tested on OH4.1 and OH4.2 milestones up to 3. Also have only used NetHome as a cloud provider to get key and token.
If starting from scratch, place the jar in the addons folder and skip to 5. If coming from another version, I’d advise the following 1) Unlink items from the Midea device(s) and delete the things 2) remove the other jar from the addons folder and stop OH 3) use the karaf openhab-cli clean-cache and place the new jar in the addons folder 4) restart OH (this could take longer than normal with the clean-cache) 5) Do an inbox scan with the Midea binding for devices. 6) After accepting go to the UI page and add your cloud provider information and save 7) Ideally the device should pull the key and token (V3) and come online. Then relink your items to the channels.
I’m not an expert either with Java or OH (OH is a retirement hobby), but I’ll try my best to address any issues. Hopefully I won’t regret this 
. Please provide a debug log using the OH forum code fences icon “</>” and an explanation of what was going on.