eWeLink–SmartThings Integration Overview
eWeLink is a popular cloud-based smart home platform (primarily for SONOFF and SmartWise devices), while SmartThings is Samsung’s smart home ecosystem. Many users want to link these two systems so they can control their eWeLink devices from the SmartThings app and set up automation between platforms. Below is a detailed overview of the integration options, including both official (native) and unofficial methods. We'll also cover step-by-step setup instructions, working features and limitations, community-supported solutions, and recommended configurations and best practices.
Official Integration: Linking an eWeLink Account with SmartThings
The official integration between the two platforms became available in late 2020. It allows users to link their eWeLink account with SmartThings via the Samsung SmartThings mobile app. This enables SmartThings to access your devices stored in the eWeLink cloud, so you can view and control them from the SmartThings interface. This is a cloud-to-cloud integration, meaning it requires an internet connection, but is easy to set up and doesn't require additional hardware.
Supported device types: Primarily smart plugs and switches are officially supported, though more device types are being added over time. For example, lamps/light sources and certain Zigbee sensors can also be integrated — in the latter case, often through direct Zigbee pairing (see below).
Note: Some specialized devices (e.g. Wi-Fi sensors, thermostats, energy monitors) have limited support or are not visible at all through the official SmartThings integration. For example, the Sonoff TH16 temperature-sensing switch can be controlled via SmartThings, but temperature and humidity readings are not displayed in the SmartThings interface.
Setting Up the Official Integration (Step by Step)
To create the native integration between eWeLink and SmartThings, follow these steps in the SmartThings mobile app:
In the SmartThings app, when adding devices, go to the “Add device” menu, select “By brand”, then choose the eWeLink brand. SmartThings will then offer to install the eWeLink integration.
Install and log in to the SmartThings app: Make sure you have the latest version installed and that you're logged in with your Samsung account.
Add device by brand: On the main screen of the SmartThings app, tap the
+symbol (Add device), then choose Device. From the list of manufacturers, find and tap eWeLink.Select device type: After selecting eWeLink, you’ll see various categories — e.g., Lighting, Outlet, Switch/Dimmer, Motion Sensor, Open/Closed Sensor. Choose the category matching your device (e.g., for a Sonoff Basic or Mini relay module, select Switch/Dimmer).
Activate eWeLink Smart Home skill: After choosing the category, SmartThings will offer to add the eWeLink Smart Home integration. Select the location and room in SmartThings where the devices will be placed (e.g., Home / Living Room).
Log in to your eWeLink account: SmartThings will redirect you to a secure eWeLink login page. Choose your region/country, enter your eWeLink email (or phone number) and password, and log in. It is crucial to select the correct region (e.g., “Europe” or “Asia”), because your eWeLink devices are stored on regional servers — if you select the wrong region, the integration won’t find your devices.
Link accounts: After logging in, grant SmartThings access to your eWeLink devices. A connection will be established between the two clouds (account linking). Wait a few seconds for a “Linking successful” confirmation.
Import devices: After successful linking, SmartThings will automatically import supported devices from your eWeLink account. You don’t need to add each one manually — all compatible devices will appear in SmartThings under the specified location and room. For example, if you had three Sonoff switches in the eWeLink app, they will now appear in SmartThings and be controllable.
Once your accounts are linked, your eWeLink devices will show up in the SmartThings "My Home" dashboard and can be controlled immediately. Devices appear as individual tiles (e.g., “Light” or the device name) and can be toggled on/off as usual.
Tip: It's a good idea to check each imported device individually and, if needed, rename them or assign them to specific rooms in SmartThings so they are easy to identify.
Direct Pairing of Zigbee Devices
If you have eWeLink / SONOFF devices using the Zigbee protocol (e.g., SNZB-02 temperature sensor, SNZB-03 motion sensor, Zigbee smart plug, etc.), you can pair them directly with your SmartThings hub.
In this case, SmartThings communicates with the device using its own Zigbee radio, not through the eWeLink cloud.
Pairing process: In the SmartThings app, tap the + symbol, select Device, then choose Scan Nearby (or By brand > eWeLink > the appropriate Zigbee device type). Put the device into pairing mode (e.g., press and hold the button until the LED starts flashing). SmartThings will detect and add the device.
Note: Many Sonoff Zigbee sensors and switches work instantly with SmartThings. However, for some devices, you may need to install a custom driver (Edge driver) if the default SmartThings software does not recognize the model. Sonoff has officially published SmartThings Edge drivers for several of its Zigbee devices (e.g., motion and contact sensors), which can be found on the SmartThings Driver portal.
Advantages of direct pairing: Zigbee devices added this way run locally within SmartThings, so automation routines can still function even without an internet connection. However, such devices will not sync with the eWeLink app (SmartThings takes full control over them).
Official Integration: Features, Functions, and Limitations
Control: Imported devices can be controlled directly from the SmartThings app (on/off toggling, dimming if supported). Commands are sent over the internet to the eWeLink cloud and from there to the device — according to user feedback, the control remains fast and nearly real-time.
Status synchronization: The integration supports two-way status sync for ON/OFF states. If you toggle a device physically or via the eWeLink app, the state is updated in SmartThings within a few seconds. This is important so that SmartThings routines (automations) can reliably react to changes.
Multi-channel device handling: Multi-gang devices (e.g., Sonoff 2-gang or 3-gang wall switches) appear in SmartThings as separate switches for each channel. According to users, a 3-gang Sonoff switch is imported as three separate controllable switches in SmartThings. This allows targeted automation for each button (channel).
Missing or limited functions: Certain advanced features are not available in SmartThings. As mentioned earlier, sensor readings (temperature, humidity, brightness, power consumption, etc.) are not transferred through the official eWeLink integration — SmartThings only sees the switch function. For example, the Sonoff TH16 will appear as a switch, but its temperature data is not visible in SmartThings. Likewise, power meters may not display wattage, or it cannot be used as a routine condition. The community has found workarounds for some of these limitations (see below).
Cloud dependency: Since the integration of Wi-Fi devices is entirely cloud-based, an internet connection is always required for control and status reporting. If eWeLink services or the internet go down, devices will appear offline in SmartThings, and commands will not be executed. For mission-critical devices, fallback options (e.g., physical switches or local automation) should be considered.
Registration and region limitations: The official integration is available to everyone at no additional cost, but a valid eWeLink account is required. It is crucial to select the correct region when logging into SmartThings — the same region where your eWeLink account is registered. For example, if your Sonoff devices are on the European server, you must choose the Europe region during linking.
Matter device support: Some newer Sonoff devices are Matter-compatible, allowing SmartThings to detect them directly without using eWeLink (Matter bridging). When adding a Matter-compatible device to SmartThings in Matter mode, it should work immediately.
Unofficial Integration Methods
If the official SmartThings–eWeLink integration doesn’t meet your needs (e.g., because a specific device isn’t supported or you want local control), there are several unofficial ways to bridge the gap between the two platforms. These methods typically use intermediary services or platforms to relay commands. Below are the most common alternatives, along with their pros and cons.
IFTTT Integration
IFTTT (If This Then That) is a cloud-based automation service that both eWeLink and SmartThings officially support. With IFTTT, you can create applets (small automations) that connect events in eWeLink to actions in SmartThings — or the other way around. For example: “If an eWeLink smart switch turns on, then turn on a SmartThings device” or “If a SmartThings routine runs, then turn off an eWeLink device,” and so on.
How it works: eWeLink has its own IFTTT channel (eWeLink Smart Home), just like SmartThings. To set up the integration, you first need to link both accounts to IFTTT. This is similar to how other services are linked in IFTTT: log in to both your eWeLink and SmartThings accounts within IFTTT and authorize access. (In SmartThings, this appears as an IFTTT app within the SmartThings app once linked, indicating that the connection is active.)
Requirement – eWeLink Advanced Plan: It’s important to note that the eWeLink–IFTTT integration is only available with the eWeLink Advanced Plan subscription — which costs about $10/year. So, if you want to automate via IFTTT, be prepared for a small subscription fee on the eWeLink side. (IFTTT itself has a free tier, but limits you to 5 applets per month.)
Creating an IFTTT Applet: After linking your accounts on IFTTT, you can create your first applet. Applets consist of a trigger (IF) and an action (THEN). Example:
IF (eWeLink device turns on) ➔ THEN (turn on SmartThings device).
Available triggers and actions:
On the eWeLink side: device on/off status, sensor alerts, etc.
On the SmartThings side: toggling a virtual switch (see below) or real device — and vice versa.
Using virtual devices: Since SmartThings often requires a virtual switch to receive or trigger IFTTT actions, it's recommended to create virtual devices in SmartThings (e.g., a virtual switch named “EWeLink Lamp V”). These virtual switches act as a bridge: IFTTT toggles them, and SmartThings routines relay that to the actual devices.
Example of two-way sync:
Applet 1:
Trigger: eWeLink device turns ON ➔ Action: SmartThings virtual switch turns ON
(So if you manually turn on the lamp in the eWeLink app, the virtual copy in SmartThings also switches to ON.)Applet 2:
Trigger: SmartThings virtual switch turns ON ➔ Action: eWeLink device turns ON
(So if you toggle the switch in SmartThings, whether via routine or manually, the real device responds.)
You’ll need to create separate applets for turning off the devices (or use toggle commands, but separate ON/OFF applets are more reliable). This ensures that device states remain synchronized across platforms.
Note: The eWeLink IFTTT channel reportedly supports two-way syncing, but this depends on whether the specific device sends status triggers.
Pros and Cons
Advantages:
Integrates with many other services, enabling complex automations (e.g., weather, calendar, email triggers).
Once set up, it runs "in the background" with no need for manual control.
Disadvantages:
Being cloud-based, it introduces latency — typically 1–2 seconds per applet, but occasionally up to 5–10 seconds.
Requires an eWeLink Advanced subscription, and optionally IFTTT Pro if you need more than 5 applets.
Troubleshooting is harder (minimal logs), and it doesn’t work offline.
IFTTT Integration Summary – Pros and Cons
Method | Pros | Cons |
IFTTT (Cloud) | – Simple to set up (no coding required) | – Requires eWeLink subscription for IFTTT |
| – Works with many services (flexibility) | – Latency and cloud dependency (usually 1–5 sec delay) |
| – Two-way sync is possible (with virtual devices) | – Slightly more complex setup (virtual switches, many applets) |
Alexa or Google Home Routine Integration
If you don’t want to use IFTTT (or prefer to avoid subscription fees), a good alternative is leveraging the integration capabilities of voice assistant platforms like Amazon Alexa or Google Assistant. Both eWeLink and SmartThings are compatible with Alexa and Google systems — once devices are added to both platforms, the assistants can bridge them together.
Using Alexa routines:
In the Amazon Alexa app, you can create routines that perform actions when certain events (triggers) occur. Since both eWeLink and SmartThings devices are visible in Alexa (via their respective skills), you can configure cross-platform actions.
For example:
“If the Philips Hue motion sensor in SmartThings detects motion, then Alexa turns on the eWeLink Sonoff light.”
You would set up the routine like this in Alexa:
When: Hue motion detected
Action: Turn on Sonoff light (recognized through the eWeLink skill)
It also works the other way:
“If an eWeLink device turns on, start a SmartThings scene.”
However, in this case, a workaround might be needed, since Alexa routines can only use certain types of triggers (like sensors or Alexa Guard events), not every device state.
Virtual switches and Alexa:
If a SmartThings device’s state isn’t available as a direct trigger in Alexa, you can use a Simulated Alexa Switch — a special type of virtual device in SmartThings that behaves like both a switch and a sensor. Alexa recognizes it and can use its state change as a trigger in routines.
This method, developed by the SmartThings community, is useful when you want SmartThings to indirectly control eWeLink devices via Alexa.
Example:
A SmartThings routine turns on the Simulated Alexa Switch ➔
Alexa detects this state change and runs a routine that turns on an eWeLink light.
Thus, SmartThings indirectly controls the eWeLink device via Alexa.
Google Home Integration:
A similar concept can be used with Google Home, though Google’s automation capabilities are less flexible. The Automations feature in the Google Home app is still limited, and not all device states can be used as conditions.
However, on a basic level, you can add both eWeLink and SmartThings devices to Google Assistant and control one platform’s devices using voice commands. Some smart home systems (like Home Assistant integrated with Google) can even simulate triggers for Google routines — but this can be considered a "hacky" solution.
Pros and Cons
Advantages:
No extra fees required for eWeLink integration — both platforms are natively supported (even free eWeLink accounts work with Alexa/Google).
Alexa routines can handle fairly complex logic (timing, some conditions).
Response time is generally fast (similar to IFTTT, ~1–2 seconds delay).
Disadvantages:
Adds another “cloud component,” which can reduce reliability.
Alexa’s interface is in English, and virtual devices may require some experimentation.
Not all sensor data is accessible: for instance, Alexa can detect Hue motion but not its light level (lux), so routines may run inappropriately (e.g., turning on lights during the day).
In SmartThings, you could build smarter automations based on sensor values, but inserting Alexa in the chain may eliminate that potential.
Overall, this is a creative workaround if other solutions are unavailable or unsuitable.
Home Assistant as a Bridge
Home Assistant (HA) is an open-source, locally hosted smart home hub that supports a wide range of integrations — including eWeLink devices. If you have a Home Assistant server (e.g., running on a Raspberry Pi or NAS), you can use it as an intermediary layer to connect eWeLink and SmartThings. There are several ways to achieve this:
SonoffLAN integration:
The Home Assistant community maintains a popular integration called SonoffLAN (developed by AlexxIT), which allows many eWeLink devices to be controlled directly over the local network (LAN), bypassing the cloud.
To use this, the devices must be on the same network and support “LAN mode.”
With SonoffLAN, Home Assistant can control the devices and retrieve their status quickly and without the internet.
For devices that don’t support LAN mode, SonoffLAN can use the eWeLink cloud API instead (requires providing eWeLink credentials in HA), but still allows centralized control.
Home Assistant ↔ SmartThings connection:
Home Assistant also offers an official SmartThings integration, which allows SmartThings hub devices (Zigbee/Z-Wave devices, virtual switches, etc.) to be imported into HA.
This creates a two-way connection — HA displays the SmartThings devices as if they were native, and toggling them in HA reflects in ST, and vice versa. The integration requires a SmartThings token to be set up in HA.
Automations in Home Assistant:
Once devices from both platforms appear in Home Assistant, you can create automations that link them.
Examples:
If an eWeLink motion sensor is triggered, Home Assistant turns on a SmartThings Z-Wave siren.
If a SmartThings smart lock is unlocked, HA sends a command to a Sonoff relay.
The possibilities are virtually endless, as Home Assistant offers highly flexible logic and broad automation support.
MQTT bridge and custom firmware:
An advanced method involves flashing Sonoff devices with custom firmware (like Tasmota or ESPHome) and integrating them with HA via MQTT protocol, then linking HA to SmartThings using an MQTT bridge.
This method is more complex and typically unnecessary for most users, as the previously described solutions are sufficient.
Pros and Cons:
Advantages:
High flexibility and full local control — you manage everything in one place.
Reduces reliance on cloud services by running most operations locally.
Broad automation capabilities and strong community support.
Disadvantages:
Technically complex: requires a continuously running server, setting up HA, installing integrations, and sometimes writing YAML code for automations.
Recommended for advanced users or those already using Home Assistant and looking to expand functionality.
That said, the SonoffLAN integration is actively maintained by the community and continuously updated to support new eWeLink devices.
Node-RED and Other Custom Solutions
Node-RED is a visual programming tool that allows you to link different systems via flows (graphical logic diagrams). There are ready-made Node-RED packages for eWeLink integration — for example, the node-red-contrib-ewelink nodes — that let you control eWeLink devices through API calls, without modifying the original firmware.
Similarly, SmartThings can also be controlled from Node-RED using its REST API, either via a SmartThings-specific node package or HTTP requests. This allows you to write custom logic: for example, Node-RED monitors a webhook for an eWeLink device status change, and when triggered, it calls the SmartThings API to update a device’s state. This is very flexible, but requires some programming mindset and skills.
Industrial applications / custom integrations:
Like Node-RED, Zapier can also be used — it’s similar to IFTTT but aimed more at business integrations. By using webhooks and eWeLink’s Advanced Plan API keys, you can build automation flows between eWeLink and SmartThings.
You can even write custom scripts (e.g., in Python using the PyEwelink library) that interact with both platforms’ APIs.
However, these are quite niche use cases; for most home users, the earlier-mentioned platforms are more than sufficient.
eWeLink Webhooks and API:
As part of the eWeLink Advanced Plan, webhook support and REST API access are available.
This means you can set up webhook URL calls for specific events (e.g., eWeLink Scenes), or develop your own application using the eWeLink API.
These features can also be used in Node-RED or similar systems — for example, a SmartThings routine or Node-RED flow could call the URL of an eWeLink Scene, triggering actions in the eWeLink ecosystem.
These advanced integration options are beyond what most users will need, but it’s good to know that they exist.
Firmware Replacement (Tasmota/ESPHome) and Direct Integration
Finally, it’s worth discussing the option of removing devices from the eWeLink ecosystem and integrating them into SmartThings using open solutions. Some Sonoff Wi-Fi devices can be flashed with alternative firmware — the two most common are Tasmota and ESPHome. Once flashed, the device is no longer an eWeLink device, but can instead be controlled locally via MQTT or HTTP.
Tasmota integration with SmartThings:
Tasmota is an open-source firmware for ESP8266/ESP32 devices, offering a web interface and extensive integration options.
Previously, a SmartThings community-developed solution called “Tasmota (Connect)” (SmartApp + DTH bundle) allowed direct control of Tasmota-flashed Sonoff devices from SmartThings.
However, this method became obsolete with the discontinuation of the Groovy-based SmartThings platform in 2022. Since then, SmartThings Edge drivers have emerged for Tasmota devices, along with MQTT bridge solutions, allowing integration of Tasmota-controlled switches with SmartThings to some extent.
This setup requires an intermediary MQTT broker and an Edge driver that translates MQTT messages into SmartThings device events.
Important: Flashing firmware is an advanced task, may void the warranty, and carries some risk — it’s only recommended if you fully understand the process and absolutely need local integration.
ESPHome and SmartThings (via Matter):
Devices flashed with ESPHome firmware can now be integrated into SmartThings using the Matter protocol (as of 2023).
If a Sonoff device is reprogrammed with ESPHome and Matter support is enabled, SmartThings may be able to natively detect it as a Matter device.
This method is still relatively new and experimental, but shows promise: in the future, firmware that supports Matter could become a universal bridge between ecosystems.
Community Solutions and Plugins
Within the SmartThings and eWeLink integration ecosystem, smart home communities have developed a number of useful unofficial tools and guides. These are often open-source projects maintained by hobby developers that make integration easier and more flexible.
Home Assistant – SonoffLAN integration:
As mentioned earlier, the Home Assistant community maintains a SonoffLAN integration that is extremely popular.
Its developer actively updates it whenever eWeLink introduces new devices or protocol changes.
The project is hosted on GitHub and is well-supported, making it a reliable choice if you use Home Assistant to manage your eWeLink devices.
Node-RED – eWeLink nodes:
Several eWeLink-related packages have appeared in the Node-RED community.
The node-red-contrib-ewelink package was once popular, but users reported that it stopped working properly due to API changes (returns 403 errors).
As a replacement, a newer package using OAuth2 called node-red-ewelink-v2-oauth has emerged, which uses the official eWeLink API key for access.
This newer version is reportedly more stable, and the developer is actively tracking changes from eWeLink.
Additionally, eWeLink offers an official Node-RED plugin as part of their CUBE system, showing that Node-RED is a supported integration path.
SmartThings community solutions:
The SmartThings user community has also been active in this area.
Even before the official integration was released, there were custom Device Handlers and SmartApps designed to integrate eWeLink devices (mostly Sonoff).
For example, Eric Meyer (erocm123) developed a package for integrating Tasmota-flashed Sonoff devices with SmartThings, including support for displaying sensor values like temperature.
After the Groovy platform shutdown, these old solutions stopped working, but the new Edge architecture brought new community efforts.
For instance, Mariano Colmenarejo released an Edge driver that supports various Sonoff Zigbee devices, enabling local SmartThings integration for sensors not natively supported by ST.
These drivers can be installed via SmartThings Community Driver Channels.
OpenHAB, Hubitat, and others:
Though this guide focuses on SmartThings, it's worth mentioning that other smart home hubs also have community-driven support for eWeLink devices.
For example:
On Hubitat, a ported SonoffLAN app was available.
On openHAB, integration was achieved using MQTT and HTTP bindings.
These examples show that there is high demand for open eWeLink integration, and fortunately, the community supports it across multiple platforms.
Summary
Active, well-maintained community integrations are primarily available on open platforms like Home Assistant and Node-RED.
In the case of SmartThings, the importance of community tools has decreased somewhat due to the official integration and Matter support.
However, if no official solution exists for your device or use case, it’s worth checking community forums — chances are, someone has already developed a workaround or plugin for it.