Any Support for Midea A/C?

Hi! I have Royal Clima AC made by Midea and OSK103 Module.
And I can’t get token and K1.
Could you make a little more detailed instruction?

Fix this problem in the next version

Seems like i have the same issue, very unstable since latest update.
Mine is also a OSK-102 module.

try new version msmart==0.1.29

Hi I Tried new version, I will let you know if it stays stable, Thanks.

Already stable for >1 hr

I can’t seem to get anything from adb logcat when filtering for doKeyAgree. I can see com.midea is logging in the adroid device bridge, but nothing in regard to token and k1. I have a device with OSK103. Does anyone had a similar issue that they know how to resolve?

Hello everyone,
I’m a complete newbie at HA and i’m failing the process how to extract device ID from my two splitters with OSK101 USB sticks for setup HA support in LAN mode?

Every help is welcome

Hi,
did you understand how to get token and k1 code?
I have the same problem with OSK103 module.
Thanks!

Something odd happens when I add the climate block to the configuration. The configuration validation just keeps spinning and doesn’t produce a result. Have anyone else had this issue?

New version (0.1.31) of msmart can get token and k1 from Midea Cloud now, no longer need to use android app.

Can you explain how this works? How does the new version get the K1? Automatically or is there something we have to do?

get from midea cloud

Afters latest update unstable again :frowning:

not sure if you already found a solution for your toshiba ac units, but in case you got some time:
we are searching for testers GitHub - h4de5/home-assistant-toshiba_ac: Toshiba AC integration into home-assistant.io

Am I the only one with this issue? I’m getting these insane numbers, the “32° F” seems to be showing the outside temperature in C, but for some reason it says F. Also I’m pretty sure it’s supposed to show the indoor temperature. Changing the operating mode from cool to off doesn’t seem to do anything either, and I don’t know where 237,024 is coming from, but that number fluctuates a lot.

Does anyone know what I’m doing wrong? Maybe my A/C just doesn’t work with this integration properly.
image image

I’m sorry, can’t be of much help here, because I use the ESPHome component, not the one that is linked in my post. :slight_smile:

I moved over from MacZhou’s component to ESPHome over a year ago (I think) and am very happy since then. :slight_smile:

1 Like

Hello, I have two ACs (Snowair) with OSK103 - as soon as I run “midea-discover” on my Raspberry (same network as the AC units) it runs and runs and runs. It does not end from itself.
Running “midea-discover -d” gives me the two units but somehow there is no k1 and token given?
Maybe because my units are not supported? Any hints on how I can make it work?
in “Nethome Plus” and “Midea Air” app I can see and control my ACs.

Thanks in advance!

INFO:msmart.cli:Debug mode active
INFO:msmart.cli:msmart version: 0.1.35 Currently only supports ac devices.
INFO:msmart.cli:Sending Device Scan Broadcast...
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:msmart.scanner:Broadcast message sent: 0
DEBUG:msmart.scanner:Midea Local Data 192.168.179.34 837000b8200f04205a5a0111a8007a800000000000000000000000002e950300001d0000000000000000000000000000f095a4676f7968306f259c259cec1f0e7ea68da00601c5f2f7d7a54947ac8512b52066d490b980df4c9aa20fd6fb7c23a0114241202cedfdbc46c8790f2be0315783a31e9ce355210ba98272939855f51fca94541303884c52e880ddefc03190f31443d17c3aac03a7656614ae1dca44efd720a42fcc1ccf64af0686ed4e66fcb3dd745659c80864ac5abb618a2fd654
DEBUG:msmart.scanner:Decrypt Reply: 192.168.179.34 22b3a8c02c19000030303030303050303030303030305131353032444242343439454331303030300b6e65745f61635f394543310000000001000000040000000000ac00000000000000502dbb449ec1069fcd0300080103000000000000000000000000000000000000000000
DEBUG:msmart.scanner:Midea Local Data 192.168.179.32 837000b8200f04205a5a0111a8007a8000000000000000000000000031950300001d00000000000000000000000000002a9aed100480b992d4b3c59b475fd6cf50a422b6c42c7b1741091ea6efd9d2afd0ffacfbb615fea2481dad05bff57be1ce3abc0b65041c8d321323b0b2fc83c0452d344fb15d422e44b8feb0510c78ca1fca94541303884c52e880ddefc03190f31443d17c3aac03a7656614ae1dca44693e90365fdafa8ce4d72312c12b857a0975a3da6dd1330ad12c472a34534cd9
DEBUG:msmart.scanner:Decrypt Reply: 192.168.179.32 20b3a8c02c19000030303030303050303030303030305131463043394431314536443946303030300b6e65745f61635f364439460000000001000000040000000000ac00000000000000f0c9d11e6d9f069fcd0300080103000000000000000000000000000000000000000000
DEBUG:msmart.scanner:Socket timeout
1 Like

Alright after you said that, I decided to try the ESPHome method, and I am very happy with it so far. :slight_smile:
It’s been working flawlessly for a couple days now, and I recommend this method to everyone.
image

3 Likes