Xiaomi MIoT

… `requiresMiCloud: true` does. Does it mean all communication between homebridge and the device is going through the micloud? If so does anything else such as Xiaomi SmartHome Hub Gateway overrides this requirement as they are advertised for "local automation"?

Excerpt saved from GitHub on 2026-10-22.

… Standing Fan 2S) 🔵[MiCloud] zhimi.fan.za5 (Smartmi Standing Fan 3) zhimi.fan.fa1 (Mijia DC Circulating Fan) zhimi.fan.fb1 (Mi Smart Air Circulator Fan) dmaker.fan.1c (Mi Smart Standing Fan 1C) dmaker.fan.p8 (Mi Smart Standing Fan 1C CN) dmaker.fan.p9 (Mi Smart Tower Fan) dmaker.fan.p10 (Mi Smart Standing Fan 2) dmaker.fan.p11 (Mi Smart Standing Fan Pro) dmaker.fan.p15 (Mi Smart Standing Fan Pro EU) dmaker.fan.p5 (Mi Smart Fan 1X) 🔵[MiCloud] dmaker.fan.p18 (Mi Smart Fan 2) air.fan.ca23ad9 (AIRMATE CA23-AD9 Air Circulation Fan) zhimi.fan.v3 (Smartmi Standing Fan V3) 🔵[MiCloud] zhimi.fan.sa1 (Mi …

Excerpt saved from GitHub on 2026-10-22.

… Please specify the `micloud` property in the `config.json` Devices marked as 🔴[BLE Mesh] and 🟡[Zigbee] require a connection over a Gateway or Hub. Fan zhimi.fan.za4 (Smartmi Standing Fan 2S) 🔵[MiCloud] zhimi.fan.za5 (Smartmi Standing Fan 3) zhimi.fan.fa1 (Mijia DC Circulating Fan) zhimi.fan.fb1 (Mi Smart Air Circulator Fan) dmaker.fan.1c (Mi Smart Standing Fan 1C) dmaker.fan.p8 (Mi Smart Standing Fan 1C CN) dmaker.fan.p9 (Mi Smart Tower Fan) dmaker.fan.p10 (Mi Smart Standing Fan 2) dmaker.fan.p11 (Mi Smart Standing Fan Pro) dmaker.fan.p15 (Mi Smart Standing Fan Pro EU) dmaker.fan.p5 (Mi Smart …

Excerpt saved from GitHub on 2026-10-22.

… Please specify the `micloud` property in the `config.json` Devices marked as 🔴[BLE Mesh] and 🟡[Zigbee] require a connection over a Gateway or Hub. Fan zhimi.fan.za4 (Smartmi Standing Fan 2S) 🔵[MiCloud] zhimi.fan.za5 (Smartmi Standing Fan 3) zhimi.fan.fa1 (Mijia DC Circulating Fan) zhimi.fan.fb1 (Mi Smart Air Circulator Fan) dmaker.fan.1c (Mi Smart Standing Fan 1C) dmaker.fan.p8 (Mi Smart Standing Fan 1C CN) dmaker.fan.p9 (Mi Smart Tower Fan) dmaker.fan.p10 (Mi Smart Standing Fan 2) dmaker.fan.p11 (Mi Smart Standing Fan Pro) dmaker.fan.p15 (Mi Smart Standing Fan Pro EU) dmaker.fan.p5 (Mi Smart …

Excerpt saved from GitHub on 2026-10-22.

… work correctly so you should always try adding it to the plugin! Devices marked as 🔵[MiCloud] require a MiCloud connection. Please specify the `micloud` property in the `config.json` Devices marked as 🔴[BLE Mesh] and 🟡[Zigbee] require a connection over a Gateway or Hub. Fan zhimi.fan.za4 (Smartmi Standing Fan 2S) 🔵[MiCloud] zhimi.fan.za5 (Smartmi Standing Fan 3) zhimi.fan.fa1 (Mijia DC Circulating Fan) zhimi.fan.fb1 (Mi Smart Air Circulator Fan) dmaker.fan.1c (Mi Smart Standing Fan 1C) dmaker.fan.p8 (Mi Smart Standing Fan 1C CN) dmaker.fan.p9 (Mi Smart Tower Fan) dmaker.fan.p10 (Mi Smart …

Excerpt saved from GitHub on 2026-10-22.

NOTICE: This PR was completely vibe coded Since my Smart Kettle Pro 2 does not work correctly, I have decided to add support for it.

Excerpt saved from GitHub on 2026-10-22.

I just installed Homebridge on jailbroken iPhone SE and inserted homebridge-miot v1.3.1 plugin. https://preview.redd.it/3n32ur5yc1u91.jpg?width=1576&format=pjpg&auto=webp&s=15f77e97b077a12dc5b27ff767a8542f1877d5ca \- Tested two Xiaomi Mi Smart LED Bulb Essential (White and Color) and it works !!!!

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.

I just got this robot. The miot command set is almost identical to dreame.vacuum.p2008. Everything seems to work. I also wanted room cleaning functionality. I have added a room_clean action for the vacuum which calls the cleaning command with the appropriate parameters to initiate targeted cleaning. The custom action definition for room cleaning in the homebridge config has to be something like: { "action": "room_clean", "name": "Clean Kitchen", "params": [ 18, "{\"selects\": [[4,1,1,2,1]]}" ] } The first parameter of 18 is passed to piid 1 and indicates room cleaning (19 would be area …

Excerpt saved from GitHub on 2026-10-22.

Hi, I was trying to support the smart speaker, and currently not finished yet, I faced some trouble. From logs I didn't see anything wrong, but the accessory not appeared. Could you please help review the code to see if the code style & format is correct and maybe anything I was missing to do? This is a famous smart speaker in China named "小爱音箱Pro / Mi AI Speaker Pro". Spec: https://home.miot-spec.com/spec/xiaomi.wifispeaker.lx06 Edit: accessory appeared as 'Not responding'.

Excerpt saved from GitHub on 2026-10-22.

Thanks! Looks good.

Excerpt saved from GitHub on 2026-10-22.

added support for yeelink color 1 light, tested on my own lights

Excerpt saved from GitHub on 2026-10-22.

… connection. Please specify the `micloud` property in the `config.json` Devices marked as 🔴[BLE Mesh] and 🟡[Zigbee] require a connection over a Gateway or Hub. Fan zhimi.fan.za4 (Smartmi Standing Fan 2S) 🔵[MiCloud] zhimi.fan.za5 (Smartmi Standing Fan 3) zhimi.fan.fa1 (Mijia DC Circulating Fan) zhimi.fan.fb1 (Mi Smart Air Circulator Fan) dmaker.fan.1c (Mi Smart Standing Fan 1C) dmaker.fan.p8 (Mi Smart Standing Fan 1C CN) dmaker.fan.p9 (Mi Smart Tower Fan) dmaker.fan.p10 (Mi Smart Standing Fan 2) dmaker.fan.p11 (Mi Smart Standing Fan Pro) dmaker.fan.p15 (Mi Smart Standing Fan Pro EU) …

Excerpt saved from GitHub on 2026-10-22.

Related to #357 . However after I add this js file and restart homebridge, `switch3:on` still not pulled automatically. (If I manually add it into property monitor, it works.) I see these two property actually have the same name, both are `switch:on`, the last one was renamed to `switch3:on` by plugin (I guess). Maybe that's the reason?

Excerpt saved from GitHub on 2026-10-22.

What changed Remove the unsupported `indicator-light` service and property from `cuco.plug.cp1`. Why The CP1 device does not support `siid=3`. Including it in property polling caused the complete polling batch to fail, eventually stopping polling and breaking local control. [code] Validation `node --check` passed. `git diff --check` passed. Deployed to Homebridge on my local instance. Initial property fetch returned `switch:on` successfully. Subsequent polling completed without failures. Manual local control was verified successfully.

Excerpt saved from GitHub on 2026-10-22.

… in the SIID / PIID for oven status so the current state is correctly reflected. Requires MiCloud. Fixes minor spelling typo. Toggling / controlling the microwave oven unfortunately still does not work, however.

Excerpt saved from GitHub on 2026-10-22.

Selecting a room in Apple Home on `roidmi.vacuum.v60` currently reaches the generic `vacuum:start-room-sweep` action with a string room ID and fails with MIOT code `-4006`. The same robot supports room cleaning through the vendor `sweep:start-sweep` action (SIID 14, AIID 1). Route Matter vacuum-only room cleaning for this model through area mode `2`, passing a JSON payload with the configured `mapId` and numeric `segmentId` array. Validate that all selected rooms have valid IDs and share a map before sending the command. Unsupported mopping modes fail explicitly. Other models and …

Excerpt saved from GitHub on 2026-10-22.

… great library and also for the incredibly Miot spec metadata fetcher. Regarding the fan speed fallback logic: The logic in `homebridge-miot/lib/modules/airpurifier/AirPurifierDevice.js` determines whether percentage-based fan speed control can be enabled by checking if any of the following properties are defined as ranged integers: `air-purifier-favorite:fan-level` `motor-speed:favorite-level` `custom-service:favorite-level` `custom-service:favorite-speed` The property air-purifier:fan-level is not considered for this check because it uses a fixed three-value list (e.g., 0 = Level 1, 1 = …

Excerpt saved from GitHub on 2026-10-22.

[37m[5/27/2021, 12:18:51 AM] ^[[39m^[[36m[miot]^[[39m [Luftfilter Xiaomi] Did not specified. Got did: 361081581 from device! ^[[37m[5/27/2021, 12:18:51 AM] ^[[39m^[[36m[miot]^[[39m [Luftfilter Xiaomi] Doing device specific setup ^[[37m[5/27/2021, 12:18:51 AM] ^[[39m^[[36m[miot]^[[39m [Luftfilter Xiaomi] Doing initial properties fetch ^[[37m[5/27/2021, 12:18:51 AM] ^[[39m^[[36m[miot]^[[39m [Luftfilter Xiaomi] Device setup finished! Device ready, you can now control your device! ^[[37m[5/27/2021, 12:18:52 AM] ^[[39m^[[36m[miot]^[[39m [Luftfilter Xiaomi] Filter life level: 96%. ^[[37m[5/27/2021, …

Excerpt saved from GitHub on 2026-10-22.

PS: The `zhimi.airpurifier.v3` product name is not v3, it's just first version of Xiaomi Mi Air Purifier. However there's a known issue for this device: fan level polling failed. If anyone knows how to solve it, please have a try. `Error while parsing response from device for property air-purifier:fan-level. Response: {"did":"686324","siid":2,"piid":2,"code":-704220043,"exe_time":0}`

Excerpt saved from GitHub on 2026-10-22.

Hi @merdok I based on our design I have added support for Xiaomi PM 2.5 Monitor (zhimi.airmonitor.v1). I thought it could work without Mi Cloud connection but unfortunately it can not. I have it running for couple hours and everything seems to be ok. Kindly accept my PR

Excerpt saved from GitHub on 2026-10-22.

This model works only with Miot plugin

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.

So all my devices work well with homekit except my robot vacuum dreame d9 max i use miot plugin, which finds device itself, dreametech app to controll it, and get following message: \[DreameBot D9 Max\] The device with deviceId 661057964 is not online! Device must be online for proper synchronization! Device is on and on charging station at that time ​ ​

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.

Device model DREAME L10s Pro Ultra Heat Model info: dreame. vacuum.r2338a Device name DREAME L10s Pro Ultra Heat Does the device require a MiCloud connection? No Anything special about the device? Not Working Switch, All other functions are not displayed LOG Homebridge: [5/9/2024, 3:13:07 AM] [homebridge-miot] Restarting child bridge... [5/9/2024, 3:13:07 AM] Got SIGTERM, shutting down child bridge process... [5/9/2024, 3:13:12 AM] [homebridge-miot] Child bridge process ended [5/9/2024, 3:13:12 AM] [homebridge-miot] Process Ended. Code: 143, Signal: null [5/9/2024, 3:13:19 AM] …

Excerpt saved from GitHub on 2026-10-22.

Added support for Qingping Air Monitor Pro v1

Excerpt saved from GitHub on 2026-10-22.

Draft as I have to test it properly

Excerpt saved from GitHub on 2026-10-22.

… update. Do you think it is better to set the current temperature to the target temperature in that case then set it to 0 degree? I was wondering how the air conditioner works if it cannot read the current temperature. I mean in that case it has no relation to how much it should heat...

Excerpt saved from GitHub on 2026-10-22.

Adds device classes for two Xiaomi fans that currently fall back to generic handling. dmaker.fan.p39 (Xiaomi Smart Tower Fan) Power, fan level 1–4 (`fan:fan-level`) and stepless speed (`fan:speed-level`) Modes: Straight Wind / Natural Wind / Sleep Horizontal swing plus angle (30/60/90/120/150) Manual move left/right (`fan:motor-control`, write-only) Off delay (`fan:off-delay-time`, minutes), LED (`fan:brightness`), buzzer (`fan:alarm`), child lock xiaomi.fan.p85 (Mijia Smart Standing Fan Pro Slim) Power, fan level 1–4, stepless speed (`dm-service:fan-level`) Modes: Straight Wind / Natural …

Excerpt saved from GitHub on 2026-10-22.

Device model Living Room Xiaomi Smart Speaker xiaomi.wifispeaker.l05g 6b4f316b556150307270383556797959 561346725 192.168.1.41 tw Living Room AC miir.aircondition.ir02 ir.1622213879634477056 tw Device name Living Room Xiaomi Smart Speaker (IR Control) Created from app air conditioner remote I have Speaker with IR Remote control. Successfully added this custom IR remote to homebridge, looks like it's supported and recognized as air conditioner, but doesn't work and does't response. Here's config, i used IP and token of speaker and model and id of created remote. `{ "name": "Living Room AC …

Excerpt saved from GitHub on 2026-10-22.

Just following the suggestion to open a PR. However, when I restart with the file in place locally, none of the switches seem to have their names populated correctly. Not sure what's up with that.

Excerpt saved from GitHub on 2026-10-22.

Adds device classes for two Xiaomi fans that currently fall back to generic handling. dmaker.fan.p39 (Xiaomi Smart Tower Fan) Power, fan level 1–4 (`fan:fan-level`) and stepless speed (`fan:speed-level`) Modes: Straight Wind / Natural Wind / Sleep Horizontal swing plus angle (30/60/90/120/150) Manual move left/right (`fan:motor-control`, write-only) Off delay (`fan:off-delay-time`, minutes), LED (`fan:brightness`), buzzer (`fan:alarm`), child lock xiaomi.fan.p85 (Mijia Smart Standing Fan Pro Slim) Power, fan level 1–4, stepless speed (`dm-service:fan-level`) Modes: Straight Wind / Natural …

Excerpt saved from GitHub on 2026-10-22.

Thanks for the contribution, @claudiomadureira! 🙏 The `ijai.vacuum.v18` (Xiaomi Robot Vacuum S20) device definition has been merged into `main` in commit b23f2d0. I landed the device file directly (rather than via the merge button) because the branch had drifted quite a bit, the version bumps targeted 1.8.8 while `main` is already at 1.9.1, and there were conflicts in CHANGELOG/package.json. The device file itself was merged verbatim, with a fresh changelog entry and a supported-devices listing (marked as MiCloud-only). Closing this as merged-by-content. If you get a chance to confirm it …

Excerpt saved from GitHub on 2026-10-22.

Here is Mi Motion Activated Night Light 2 https://www.merdok.org/miotspec/?model=yeelink.light.nl1 And there's Mi Motion Sensor https://www.merdok.org/miotspec/?model=lumi.sensor_motion.v2 Both of them have events "motion-sensor:motion-detected" So Mi Motion Sensor is displayed in room page: Is it possible to display here Mi Motion Activated Night Light 2 as well ?

Excerpt saved from GitHub on 2026-10-22.