Olimpia Splendid Dolceclima Air Pro 14 HP WiFi — working local control via midea_ac_lan (Midea Smart Kit protocol)

Share your Projects! Custom Integrations
1

Posting this in case it saves someone else the digging — I got a Olimpia Splendid Dolceclima Air Pro 14 HP WiFi (EU version, 14000 BTU/h, 420 m³ portable AC) working with local, cloud-free control in Home Assistant.

There’s an existing thread about this exact model (Olimpia Splendid DOLCECLIMA Air Pro 14 HP wifi dongle esp home) where @aceindy speculated it might use an OSK-103/OSK-105 module and therefore work with the Midea ecosystem — but as far as I can tell nobody had confirmed it hands-on yet. Can now confirm: yes, it works.

Device fingerprint

  • Model: Olimpia Splendid Dolceclima Air Pro 14 HP WiFi
  • Vendor app: OS Comfort (com.olimpia.ac) — Olimpia Splendid’s official app, used for initial pairing/registration.
  • Confirmed: TCP port 6444 open on the unit, and it responds to a standard Midea “Smart Kit” auth/discovery handshake — i.e. this is a Midea-manufactured WiFi module under the hood, like it is in a lot of other rebranded AC brands (Comfee, Toshiba, Carrier, Electrolux, and apparently other Olimpia Splendid lines too — the master list of known-working Midea-protocol models already lists an Olimpia Splendid Nexya S4E (2019), and there’s a separate report of the Olimpia Splendid Aryal S1 working with the Midea SLWF-01pro ESPHome dongle).

Heads-up for anyone else with an Olimpia Splendid AC searching for an integration: don’t confuse this with ha-olimpia-splendid-unico — that’s a great project, but it’s for a completely different Olimpia Splendid product line (the “Unico” monobloc units with a B1015 WiFi board), using its own custom BLE + TCP protocol. It explicitly does not apply to the Air Pro / Dolceclima line, and that’s by design — different hardware, different protocol.

What worked

  1. Installed midea_ac_lan via HACS (this is the actively maintained HA custom component for the Midea Smart Kit protocol, config-flow based).
  2. Paired/registered the device first via the official OS Comfort app and confirmed it worked there. (I haven’t tested whether this step is strictly necessary for midea_ac_lan to pick it up, or whether it would also work provisioning a factory-fresh unit directly — if anyone’s tried skipping this, curious to hear.)
  3. In the midea_ac_lan config flow, I used the automatic-discovery mode but entered the device’s static IP directly (rather than relying on broadcast auto-discovery finding it). Not sure if plain auto-discovery (no IP entry) would also work — plausible, since it’s UDP broadcast on the same subnet, but untested.
  4. On the “cloud account” step, none of the built-in cloud provider options authenticated using my real OS Comfort account credentials. What did work was picking the flow’s “no username / password” (anonymous) option. That matched what I saw independently when testing with the msmart-ng CLI tool’s discover command — it authenticated successfully against the unit using its own built-in default/anonymous credentials, no account needed.
  5. Result: full climate entity in Home Assistant — power, mode, and target temperature control all working.

So in the end, no custom code, forks, or reverse-engineering was needed at all — the existing midea_ac_lan integration already handles this device out of the box, you just need to pick the anonymous/no-login option on the account step instead of trying to authenticate with your real Olimpia account.

Open questions (if anyone can confirm)

  • Does plain auto-discovery (no manual IP) find the unit too?
  • Is pairing via the official app a hard prerequisite, or can midea_ac_lan provision a brand-new unit from scratch?
  • Does this hold for other Dolceclima/Air Pro capacities (9HP/10HP/12HP), or just the 14HP?
1 Like