HI Jacek,
So I was able to install a new module OSK105 but it appears to be the same as the OSK103 using the new version 3 midea protocol as @Eranl mentioned I also stood up the fake server python as the links he mentioned require to isolate the unit from the internet app as the readme on those sites indicate that this is a one user at a time connection approach as I understood it from the huge year long blog over on HA site…
So good part is your latest package will correctly discover these modules and add them in to openhab show on line then as soon as it polls the unit it errors attempting to retrieve the status. enabling the debug log for the binding returns this and repeats as the binding error handling seems to recover correctly and try again. status to online then unknown then offline.
2021-07-21 20:04:39.699 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_1_178__30786325767627__net_ac_0a4c at 192.168.1.178
2021-07-21 20:04:39.699 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-07-21 20:04:42.865 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-07-21 20:04:43.709 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-07-21 20:04:43.966 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler MideaACHandler tried updating the thing status although the handler was already disposed.
2021-07-21 20:04:53.971 [INFO ] [ler.MideaACHandler$ConnectionManager] - Connected to mideaac:ac:mideaac__192_168_1_178__30786325767627__net_ac_0a4c at 192.168.1.178
after enabling the python script to substitute the cloud with the repeater and adding the dns and taking away internet I can see it start responding on port 443 back to the fake server and it does stop the OSK103 from going into a reboot every 8 seconds and the 600 seconds of Lan is verified.
We can see the module conversation in the trace then we see the module do a udp broadcast and the entire conversation starts over.
The network trace shows it doing a syn ack and fin
as below
So looking through all the remaining scripts that are using it would appear the reason it is not actually allowing a status retrieval is the new module is expecting credentials to be passed to it
apparently when you set up the module through the app to allow it to connect to the wifi it uses your OSK103 modules MAC address and wifi ssid as the user name and the wifi password as the user password
based on the example below from that git site @Eranl listed so perhaps if we added a class to handle that logon it may not be to horrible to go on from there.
# first take device’s ip and id
# pip3 install msmart; midea-discover
device = ac(‘YOUR_AC_IP’, YOUR_AC_ID)
# If the device is using protocol 3 (aka 8370), you must authenticate with your
# WiFi network’s credentials for local control
device.authenticate(‘YOUR_AC_MAC’, ‘YOUR_WIFI_SSID’, ‘YOUR_WIFI_PW’)
# Refresh the object with the actual state by querying it
device.refresh()
Anyway hope this helps
and as always test harness was clean fresh install of openhab 3.1.0(stable) only other binding was NTP and of course this time a OSK103(5) USB module
sorry for such a long post but wanted to offer as much content to this as possible.