We are talking about Anderson/MacShou’s solution with OSK-103 here right??
I’m not even sure that is still developed.
Fair change the OSK-103 got updates that are not in the repository of Anderson…
I can see there are still updates, but they all concern HA…
Makes sense, as his OSK won’t received any updates…
I too recommend to dump the OSK and get ESP 
(if you manage to sell it for a recent price, you can buy may ESP for it :P)
This thread is about Midea A/C units so I didn’t feel it was necessary to specify that level of detail but if it’s helpful I have no problems doing so. I installed the integration from HACS and then plugged the information into configuration.yaml and restarted HA. Not sure how to enabe debug for the midea integration.
Make: Midea
Model: MAW08V1QWT
Add’l Info: It has a built dongle that’s concealed behind the front panel. It’s just a USB dongle that with a sticker that says “smart kit intelligent” on the sticker and has a MAC address. I would imagine it’s just a WiFi dongle but no idea beyond that
This is the section I added to my configuration.yaml. I pulled the device ID by doing a Share from within the Midea app, pulled the data out of the QR code and then converted the string to text.
climate:
- platform: midea_ac
host: 192.168.29.111
id: 012345678901234
After adding this to my config and restarting HA I do see an entity was created but it says it’s unavailable.
Pretty sure the integrated wifi stick in your unit is the newer, hereby often referred 103 one, which is not supported by the HACS Midea AC integration.
Bummer. Is there a way to buy a different dongle that would allow me to control it from HA?
There are three options:
as @aceindy suggested, try the ESPHome solution linked above
there’s a fake cloud method described in detail here: https://github.com/WMP/midea-ac-py/tree/support-8370#install-fake-cloud-only-if-you-have-protocol-version-3
(untested): in theory if you can get a 102 dongle, it could work. But that’s something I never tried 
one could argue with the elegant word But yes, it’s a viable 4th option.
Elegant was used referring to much more usage cases in same room, not only HVAC 
But it is OK to correct my wording- hehee…
Best, JR
Thanks for the help @Lukacs_Attila & @Foxxy. I think all 4 of those options will likely exceed my current HA abilities.
Maybe I’ll revisit when I’ve gotten a bit better on the platform.
problem with ‘elegant’ IR is that it only 1 way communication.
In other words, you can order it to go on, but can’t verify if it is really on.
Also operating it with original remote will seriously confuse HA
@aceindy No, it would not confuse HA if you use the original remote, because in my cheme I’ve put IR receiving diode, which updates the state of the air conditioner to the right state. So if you use the original remote, HA will know what to do.
Nope, HA has to assume that everything worked. Without a back channel, that is directly connected to the sensor, it will always be an assumption. 
But nonetheless, why not using the simpler and possibly cheaper way to get to a biderectional solution. The ESPs and the parts for an ESP dongle are not even worth mentioning. In theory and using all ways to save money you will be under 10.-€ / $10 for a known working and actively developed dongle, that gives you the whole experience. 
Sure, first thing is to enable the debug log especially for this component. You do that by adding this to your configuration.yaml:
logger:
default: WARNING # or DEBUG or INFO
logs:
custom_components.midea_ac: debug
I hope this is the correct spelling for the component. Can’t test it, as I don’t have it running anymore (that’s why I recommend the ESPHome-based approach).
Other necessary infos would be the label of the A/C (Media is always the manufacturer, but labels the A/Cs with a lot different brands like OlimpiaSplendid, Mr.Cool, …) and the dongle you are using. All original dongles are either OSK-102 or OSK-103.
I just need to take a few pics to publish a small guide about how the ESPHome based approach is working (including buying instructions). As I said, it is the better approach towards your A/C as this component here in this thread will be discontinued rather sooner than later. My recommendation for you: wait for the guide and decide after you read it. I’m quite sure you will end up with the ESPHome based approach.
I was wondering what the status is on the Tutorial you said you were writing?
Thanks.
My soldering skill are limited to say the least, but I took a deep breath, ordered everything and I was able to make the thing work, so I can confirm: even with basic soldering skills (i.e. it’s ugly like hell :D) you can do the same.
Text is done, but pictures aren’t… But I’d say in the next three days it will be ready.
I’ve tested this option. I have 2 AC with OSK102 and the component work great. I also have 1 AC with OSK103 dongle and is unavailable in HA.
I have tried to switch one OSK102 with the OSK103 dongle and the AC started to work with HA.
My question is: what differences have the two dongle?
@paddy0174 can’t wait to read the guide
They use different protocols. That makes it necessary, that with the OSK-103 you need to setup a fake server in your LAN.
So when the guide will be released then I could easily connect my Midea AC with OSK103? Or I will have to but something? I don’t really know what is ESPHome? I read on the Internet but still my brain does not work hah. If it comes to the programming im good but I really fight with connecting accessories to HA
HI All,
Have anyone experienced such behaviour - i have OSK103 (version 3 protocol). Running HA in Docker. Trying to add the integration with fake midea cloud. Did everything as mentioned here - GitHub - WMP/midea-ac-py at support-8370, but i get this error:
2021-04-21 10:14:48 ERROR (MainThread) [homeassistant.components.climate] Error while setting up midea_ac platform for climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 199, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/midea_ac/climate.py", line 73, in async_setup_platform
device.authenticate(device_8370_only_ac_mac, device_8370_only_wifi_ssid, device_8370_only_wifi_pw)
File "/usr/local/lib/python3.8/site-packages/msmart/device.py", line 43, in authenticate
self._authenticate()
File "/usr/local/lib/python3.8/site-packages/msmart/device.py", line 46, in _authenticate
self._lan_service.authenticate(self._mac, self._wifi_ssid, self._wifi_pw)
File "/usr/local/lib/python3.8/site-packages/msmart/lan.py", line 68, in authenticate
self._authenticate()
File "/usr/local/lib/python3.8/site-packages/msmart/lan.py", line 80, in _authenticate
raise error
File "/usr/local/lib/python3.8/site-packages/msmart/lan.py", line 76, in _authenticate
tcp_key = self.security.tcp_key(response, self._key)
File "/usr/local/lib/python3.8/site-packages/msmart/security.py", line 90, in tcp_key
raise Exception('authentication failed')
Exception: authentication failed
My config is:
climate:
- platform: midea_ac
host: 192.168.0.43 (IP of AC)
id: **************** (id od AC)
8370_only_ac_mac: ********** (MAC of AC)
8370_only_wifi_ssid: *********** (SSID which AC is connected to)
8370_only_wifi_pw: ********** (password of SSID which AC is connected to)
Installed pip3.7 install git+https://github.com/kueblc/midea-msmart.git@support-8370 inside the docker container.
Created a Fake Midea Service on 192.168.0.44
Made an entry in local DNS server pointing module.appsmb.com to the ip Fake Midea Clud Service (192.168.0.44)
Changed the DNS entry on HA Docker Host pointing to local DNS Server.
I have exactly the same issue. Could it have something to do with the Python version? I’m using 3.9.4.
Just setup a Python 3.7.10 venv > same issue. So not the python version