Skip to main content

Mitsubishi Electric Kumo Cloud

Cloud control for Mitsubishi Electric ductless mini-split heat pumps (M-Series, Mr. Slim, residential City Multi) that have a Kumo Cloud Wi-Fi adapter (PAC-USWHS002-WF-2 or compatible) installed and onboarded.

This driver is the cloud path. The local-LAN PuREMOTE protocol on the indoor adapter is not used here — pick the cloud driver if your system already lives in the Kumo Cloud account; pick a local-LAN driver (when one exists) if you want zero-internet operation.

Prerequisites

  • Each indoor unit has a Kumo Cloud Wi-Fi adapter installed and provisioned.
  • All adapters appear in the Kumo Cloud mobile app under one account.
  • The GEM controller has outbound HTTPS to app-prod.kumocloud.com.

Setup

  1. Create a device of driver type mitsubishi_kumo_cloud.
  2. Enter the Kumo Cloud username (email) and password exactly as used in the mobile app. The password attribute is encrypted at rest.
  3. Optionally tune status_interval (default 60000 ms; minimum 30000 — the cloud rate-limits aggressive polling).
  4. Send the get_devices command on the device. The response is a list of indoor units with their serial and label.
  5. For each indoor unit you want to control, create a zone. Set zone.address to the indoor-unit serial (12 alphanumeric characters).

Attributes

Device

NameRequiredTypeDescription
usernameyesstringEmail used in the Kumo Cloud app.
passwordyesstring (secure)Password used in the Kumo Cloud app.
status_intervalnoint (ms)Poll cadence. Default 60000, minimum 30000.

Zone

zone.address is the indoor-unit serial. The driver writes these attributes per zone as it polls:

AttributeTypeNotes
statestringon / off summary.
modestringheat, cool, auto, dry, fan, or off.
temperaturefloatCurrent room temperature reported by the indoor unit.
heat_setpointfloatActive heat setpoint.
cool_setpointfloatActive cool setpoint.
fan_speedstringauto, quiet, low, medium, high, powerful.
vanestringauto, horizontal, midhorizontal, middle, midvertical, vertical, swing.

The attribute units (°F vs °C) follow whatever the unit was provisioned with in the Kumo Cloud app — the driver does not convert.

Commands

CommandArgsNotes
get_devicesDiscovery; lists the indoor units linked to the account.
onaddressPowers the indoor unit on. The unit decides its own mode.
offaddressPowers it off.
set_modeaddress, modeSets heat, cool, auto, dry, fan, or off.
set_temperatureaddress, temperatureSingle-setpoint convenience. In cool mode it writes sp_cool; in heat mode sp_heat; otherwise both.
set_heat_setpointaddress, temperatureHeat setpoint only.
set_cool_setpointaddress, temperatureCool setpoint only.
set_fan_speedaddress, fan_speedOne of auto / quiet / low / medium / high / powerful.
set_vaneaddress, vaneVertical vane direction.
get_statusaddressForce a one-shot status read.

Known limitations

  • This is the cloud path only. If the GEM host or the indoor unit loses internet, the driver cannot send commands.
  • The Kumo Cloud login response shape has shifted between app versions. The driver tolerates both the historical 3-element array and the newer object form, but a future cloud change may need a small update.
  • Setpoint changes in dry, fan, or off mode are silently dropped by the cloud. Always set a heat/cool/auto mode first.
  • Humidity, error codes, and the City Multi central-controller pages are not exposed.

Troubleshooting

  • mitsubishi kumo cloud login failed in the log — verify the email/password by signing into the Kumo Cloud mobile app first. The driver re-authenticates automatically on 401 / 403 responses.
  • mitsubishi kumo cloud devices found: 0 — the account contains no provisioned adapters, or the account-tree shape was unrecognized. Run get_devices and check the response.
  • Polling pauses in the log — Kumo Cloud will rate-limit polling under ~30 s. Raise status_interval.