The New eWeLink Smart Home Add-on for Home Assistant Is Now Available

Ideas & Suggestion
, ,
1

We’re happy to announce that the new eWeLink Smart Home Add-on for Home Assistant is now officially released. This is the add-on we previously previewed here:

The new add-on is designed to fully replace the legacy eWeLink Smart Home add-on, providing Home Assistant users with a more stable, standards-compliant, and long-term maintainable official integration .

:glowing_star:New Add-on, New Features

1. Native Home Assistant Integration

The new add-on focuses purely on device integration. It does not provide a separate device control UI . Devices are synced to Home Assistant via MQTT , and all control, automation, and configuration are handled directly within Home Assistant.

2. Richer, Standards-Compliant Entities

Compared to the legacy add-on, devices expose more entities and state information in Home Assistant, following platform standards
(e.g. power data, device status, signal strength, etc.).

3. LAN Control First

For devices that support both local and cloud control, LAN communication is prioritized , with cloud access used as a fallback when needed.

4. Broad Device Support

The current release supports a wide range of Wi-Fi and Zigbee devices , including switches, plugs, lights, power monitoring devices, and various sensors.
Device support will continue to expand in future releases.

:clipboard: Full supported device list.

:red_question_mark:Why a New Add-on?

The legacy eWeLink Smart Home add-on served the community well in the early days. However, as Home Assistant has evolved rapidly, some of its implementation approaches no longer align with current best practices, and maintaining and extending it has become increasingly difficult.

With this in mind, we redesigned the integration from the ground up. The goals of the new add-on are to:

  • Better align with Home Assistant’s native architecture and entity model
  • Provide richer and more accurate device entities
  • Support more existing and future eWeLink / SONOFF devices
  • Enable long-term maintenance and continuous updates

:sparkling_heart:Migration for Legacy Users

For users currently using the legacy eWeLink Smart Home add-on, we provide a guided data migration process :

  • Existing devices and entities can be migrated seamlessly
  • Home Assistant automations and configurations remain intact
  • Migration includes conflict detection and guided steps

The legacy add-on will no longer be maintained or updated, and users are encouraged to migrate to the new add-on.

:red_exclamation_mark:Important Behavior Changes

Please note the following changes in the new add-on:

  • :cross_mark: Home Assistant devices are no longer synced back to the eWeLink cloud
  • :repeat_button: The legacy and new add-ons cannot run simultaneously by default
  • :locked_with_key: Switching eWeLink accounts will make previously synced devices unavailable

These changes help ensure data consistency and long-term stability.

:rocket:Getting Started

You can install the eWeLink Smart Home add-on from the Home Assistant Add-on Store by adding the official repository.

:blue_book: Installation, migration, and usage guide:
https://github.com/iHost-Open-Source-Project/hassio-ihost-addon/blob/master/hassio-ihost-ewelink-smart-home/DOCS.md

1 Like
2

My first impressions are disappointing. You describe the add‑on as “native”, but in practice it’s just an MQTT bridge that pulls devices from the cloud and exposes them to Home Assistant via MQTT Discovery. It works reliably and follows HA standards, but it’s not a full integration on the level of ZHA, Z2M, ESPHome, or Shelly — everything still goes through an intermediate layer and depends on the cloud.

More importantly, the add‑on simply isn’t ready. It’s more of a “work in progress”, at best a beta version. Many devices aren’t supported (e.g., TRVZB). @MichaelLearnsToCode The MQTT payload is filtered significantly better than in the very similar mechanism known from the latest iterations of the MQTT→HA “integration” used by the NSPanel Pro, but the usefulness is just as limited and doesn’t bring anything particularly exciting.

Setting aside the confusion caused by the recent TRVZB firmware update, it’s still far from the practicality of the SonoffLAN add‑on from HACS. For now, I’ll keep an eye on it, but I definitely won’t be using it as a “production‑ready” solution, because it simply isn’t one.