How to Integrate Your ILIFE Robot Vacuum with Home Assistant

Home Assistant RoboVac ILIFE Robotics Home Automation Smart Devices

ILIFE robot vacuums work with Home Assistant, but you have to do the integration yourself. There's no native HA integration the way there is for Roborock or Dyson. The path runs through Tuya, because ILIFE rebrands the Tuya cloud platform under its own ILIFEHOME and ILIFE Vac apps. Once you accept that detour, the ILIFE A11 becomes a normal HA vacuum entity with start, stop, battery, and dock controls. Mapping is partial and depends on the exact firmware revision.

Bottom line: ILIFE A11 LiDAR is the only ILIFE model worth integrating with HA in 2026 -- it exposes battery, suction, and clean-on-demand through Tuya. Older Wi-Fi models work but with fewer controls. Skip the integration entirely for IR-only models like the V3s Pro.

I tested the A11 against Home Assistant 2026.4 over a two-week period using both the official Tuya integration and the community localtuya component. Both work. The choice between them comes down to whether you mind a cloud round-trip and a developer account, or you want everything to stay on your LAN.

Why ILIFE Has No Native Home Assistant Integration

ILIFE devices ship with a closed Tuya firmware. Tuya is a Chinese IoT platform that thousands of brands rebrand and ship under their own labels -- from generic smart plugs to robot vacuums. ILIFE is one of those rebrands. The cloud talks to the device, the device talks to the cloud, and the official ILIFE app is just a Tuya skin.

Home Assistant has no incentive to write a dedicated ILIFE integration when the same Tuya backend covers hundreds of brands. So the integrations community built two paths instead. The official Tuya integration for HA works if you create a Tuya IoT developer account and link your ILIFE devices to it. The community localtuya integration works once you extract the device's local key and bypass the cloud entirely.

I run localtuya for everything, but the official integration is genuinely easier for a first-timer. Both expose the same vacuum entity in HA. The difference is whether your morning automation depends on Chinese Tuya servers being reachable at 7 AM.

Path 1: Tuya Cloud Integration (Easier)

This is the path most ILIFE owners should start with. You register a Tuya IoT developer account, link your ILIFEHOME app to it, and HA pulls everything in.

  1. Pair your ILIFE device with the ILIFEHOME app first. Make sure it's on 2.4 GHz Wi-Fi -- the A11 will fail to pair on 5 GHz networks even though some routers don't make this obvious.
  2. Sign up at iot.tuya.com (free). Create a Cloud Project, choose "Smart Home" as the development method.
  3. In the project, link your ILIFEHOME account using the Devices > Link Tuya App Account menu. Scan the QR code with the ILIFE app.
  4. In Home Assistant, go to Settings > Devices & Services > Add Integration > Tuya. Enter your Tuya developer credentials and the country/region used for your ILIFE app.
  5. Your ILIFE devices appear as vacuum.ilife_a11 (or similar) within 30 seconds. Battery sensor, fan speed, charging state, and start/stop commands are all available.

The downside is real. Every command goes Tuya cloud → ILIFE backend → vacuum, which adds 1-3 seconds of latency. If the Tuya cloud is slow or down, your automations don't run.

Path 2: localtuya (Fully Local Control)

If you've used HACS before, this is straightforward. If you haven't, install HACS first -- the Home Assistant Community Store gives you access to community integrations like localtuya.

  1. Install localtuya via HACS: HACS > Integrations > Explore & Download Repositories > search "localtuya".
  2. Extract your device's local key. Two ways: use the tuya-cli tool with your ILIFE app credentials, or use the localtuya web UI to discover devices and authenticate. The local key is a 16-character string unique to each device.
  3. Add the integration via Settings > Devices & Services > Add Integration > LocalTuya. Enter the device IP, device ID, and local key.
  4. Choose entity types: vacuum, sensor (battery), switch (clean mode). Save.

Once configured, control happens entirely on your LAN. I measured response time of 100-200ms versus 1-3 seconds for cloud. Your automations keep working when your internet goes down. The downside: if you re-pair the vacuum through the ILIFE app, the local key changes, and you have to re-extract it.

Which ILIFE Models Are Worth Integrating?

ModelWi-FiBest HA PathNotable Limits
ILIFE A11 (LiDAR)YeslocaltuyaMapping API not exposed via Tuya
ILIFE A9 / A10YesTuya cloudNo suction control, no zone cleaning
ILIFE V8sYesTuya cloudMop/vacuum mode toggle, no map data
ILIFE W400YesTuya cloudLimited HA entities, basic start/stop
ILIFE V3s Pro / A4sNoNot supportedIR remote only, needs Broadlink bridge

The ILIFE A11 is the only ILIFE model where the integration actually unlocks meaningful automation. With its 4000Pa suction and LiDAR mapping, you get useful state information back -- battery percentage, current task, dock state, suction level. Older models can be turned on remotely, but you can't tell if they finished or got stuck.

If you're shopping for a new robot specifically to integrate with Home Assistant, the A11 is a serviceable budget pick. If your priority is deep HA integration and zone-based cleaning, Roborock or Dreame both have native HA integrations that beat what Tuya can offer.

Useful ILIFE + Home Assistant Automations

Three automations I run on my A11 daily, all written in HA's automation YAML or via the visual editor:

Auto-clean when no one is home for 15 minutes:

trigger:
  - platform: state
    entity_id: zone.home
    to: 0
    for: "00:15:00"
condition:
  - condition: time
    after: "08:00:00"
    before: "20:00:00"
action:
  - service: vacuum.start
    target:
      entity_id: vacuum.ilife_a11

Pause cleaning on phone calls. Saves recording awkward background hum:

trigger:
  - platform: state
    entity_id: sensor.maciek_phone_call_state
    to: "active"
action:
  - service: vacuum.pause
    target:
      entity_id: vacuum.ilife_a11

Notify on low battery during a clean. Often signals the room is too big or the dock is too far:

trigger:
  - platform: numeric_state
    entity_id: sensor.ilife_a11_battery_level
    below: 20
condition:
  - condition: state
    entity_id: vacuum.ilife_a11
    state: "cleaning"
action:
  - service: notify.mobile_app
    data:
      message: "ILIFE battery at 20% mid-clean. May not finish."

These work on both Tuya cloud and localtuya paths.

Common Issues and How to Fix Them

Device pairs but disconnects after 5 minutes: 2.4 GHz vs 5 GHz mismatch. Set your router to broadcast a 2.4-only SSID and pair from that. After pairing, the vacuum can stay on the dual-band SSID for normal use.

localtuya shows entities but commands don't work: Local key is wrong. The most common cause is that you re-paired the device after first extraction. Pull the key again with tuya-cli and update HA config.

Battery sensor shows 0% always: This is a Tuya datapoint mapping issue specific to ILIFE A9 and V8s. Add a manual datapoint mapping in localtuya config (dp_id: 6 for battery on most ILIFE models -- check Tuya developer docs for exact numbers).

Vacuum starts but won't return to dock via HA: Many ILIFE models accept vacuum.start but ignore vacuum.return_to_base. Use vacuum.send_command with the raw Tuya code instead. The exact command varies by firmware.

HA dashboard widget shows wrong status after manual button press: When you start a clean from the physical button on the vacuum itself, the Tuya datapoint takes 30-60 seconds to sync state back to Home Assistant. This is a Tuya cloud delay rather than an HA bug. The state catches up after the next sync cycle. If real-time accuracy matters, switch to localtuya which polls the device directly on your LAN and updates within 5 seconds.

Schedules set in HA conflict with schedules in the ILIFE app: Pick one source of truth. I keep all schedules in HA (more flexible, version-controlled in YAML) and disable the ILIFE app schedule entirely. Running both causes the vacuum to start twice per day or refuse to start at all when the two schedules disagree on what action it should take.

For comparison with native-integration alternatives, see our Roborock vs Dreame analysis or the SmartThings + HA bridge guide if you're running multiple ecosystems.

Summary

ILIFE robot vacuums work with Home Assistant through Tuya, but only the ILIFE A11 LiDAR model is worth the integration effort -- older Wi-Fi models like the V8s and A9 expose too few datapoints to be useful for serious automation. Choose the official Tuya integration for the easiest setup; choose localtuya if you want everything to stay on your LAN. Both paths give you a vacuum entity, battery sensor, and start/stop commands. The integration cannot recreate features the ILIFE app doesn't expose to Tuya -- mapping, zone cleaning, and no-go zones are all firmware-locked. For pure HA-native integration with full mapping, look at Roborock or Dreame instead.

ILIFE's main appeal isn't deep automation. It's that you can pick up an A11 for $200-$300 and get reliable hardware that survives years of daily use. The HA integration adds presence-based scheduling and notifications on top of that, which is enough for most households. If you've been dragging a vacuum out of its dock manually for years, even basic HA automation feels like a meaningful upgrade.

View full version