Xiaomi Home Integration for Home Assistant

Original Article ↗ Hacker News Discussion ↗

Xiaomi has released an official Home Assistant integration, prompting enthusiasm from users who can now tie more of the company’s devices into their smart homes, but also concern that it relies heavily on Xiaomi’s cloud rather than local control. Many Home Assistant users emphasize a preference for local-only ecosystems built on Zigbee, Z-Wave, or Wi‑Fi devices with open firmware, citing past examples where cloud-dependent products were crippled or enshittified by vendors. The thread broadens into practical advice on starting with Home Assistant, trade-offs between different protocols and hardware, and alternatives like Valetudo or ratgdo for keeping automation reliable, private, and independent of proprietary platforms.

Home Assistant–Xiaomi Integration

  • New Xiaomi integration connects devices via Xiaomi’s cloud using OAuth; tokens and device metadata are stored in Home Assistant config in clear text, so local config security is important.
  • Some argue this isn’t “true” integration because it still requires Xiaomi’s cloud and account; it’s seen more as an official cloud bridge than a local API.
  • Partial local control exists but depends on Xiaomi “central hub gateway” functionality, which is region‑restricted and unclear for many users.

Local vs Cloud Control

  • Strong preference from many for devices that work fully offline (local control, no vendor servers).
  • Users categorize devices as: (1) need internet to work, (2) need internet only for setup, (3) fully local. Many aim for category 3 wherever possible.
  • Multiple examples of cloud shutdowns (e.g., Feit, Sylvania) turning “smart” devices into bricks or reduced functionality.

Device Ecosystems: Zigbee, Z‑Wave, Wi‑Fi

  • Zigbee and Z‑Wave widely recommended for reliability, local control, and avoiding vendor lock‑in; Zigbee2MQTT is praised for broad device support.
  • Some report Zigbee problems (non‑compliant devices, noisy thermostats, mesh complexity) and prefer Wi‑Fi + ESPHome/Tasmota (e.g., Shelly, Sonoff) for mains‑powered devices.
  • Concern about Wi‑Fi: firmware quality, phoning home, OTA updates, and 2.4GHz congestion; mitigated via VLANs and firewalls.

Garage Doors and Closed APIs

  • myQ/LiftMaster/Chamberlain criticized for closing APIs and adding subscriptions; many recommend alternatives like ratgdo, OpenGarage, Konnected, Shelly relays, or DIY ESP32 + relay solutions.
  • Debate over DIY complexity vs. ease of past cloud integrations and cost of professional installation.

Experiences with Home Assistant

  • Widely praised as powerful, polished, and central to many smart homes; large integration ecosystem and companion apps (HomeKit/Google Home bridging).
  • Also described as complex, programmer‑oriented, and not “set and forget”; issues include upgrades breaking configs, database corruption, and entropy over time.
  • Some keep HA usage minimal: only automations (no dashboards), only where vendor apps fall short.

Privacy, Security, and Vendors

  • Skepticism toward Xiaomi and Chinese IoT vendors due to ads, potential tracking, and CCP associations, but others point out similar “enshittification” by Western companies (Windows, TVs, Amazon).
  • Strong cultural norm in the thread: prefer local, open solutions (Zigbee, Z‑Wave, Tasmota, Valetudo) and avoid cloud lock‑in where possible.