# Leave Sonoff wifi devices from Cloud? **URL:** \ **Category:** Ideas & Suggestion\ **Created:** [September 14, 2026, 9:59am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170 "2026-09-14T09:59:45Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 14, 2026, 9:59am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/1 "2026-09-14T09:59:45Z")
Is it possible to remove all Sonoff Wi-Fi devices from the eWeLink Cloud and connect them to Home Assistant so that they have no connection to the eWeLink Cloud whatsoever? ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 14, 2026, 10:23am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/2 "2026-09-14T10:23:45Z")
> [@Jojkoba](#): > > have no connection to the eWeLink Cloud whatsoever Yes, but only by replacing the original firmware with custom firmware such as ESPHome or Tasmota. With the original eWeLink firmware, there is no Home Assistant or SonoffLAN setting that completely disables the device’s cloud connection. SonoffLAN provides local control, but the device can still communicate with eWeLink Cloud. Its “cloud disabled” option only disables cloud access for the integration, not for the device itself. I bet that you already know that you can also block Internet access at the router level, but that’s a network-level workaround. ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 14, 2026, 10:35am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/3 "2026-09-14T10:35:14Z")
I blocked all the devices on the MikroTik; at least now they won’t arbitrarily open the gates at the houses. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 14, 2026, 10:47am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/4 "2026-09-14T10:47:00Z")
> [@Jojkoba](#): > > arbitrarily open the gates Really?! How come? ---
**Author:** ![NelsonSilva](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/nelsonsilva/32/7064_2.png) [@NelsonSilva](https://forum.ewelink.cc/u/NelsonSilva)\ **Post date:** [September 14, 2026, 11:58am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/5 "2026-09-14T11:58:44Z")
Curious! Last night happen the same to me. My garage door open without any action from users or automation 🫣 ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 14, 2026, 1:22pm UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/6 "2026-09-14T13:22:33Z")
My dog got hit by a car, and my child runs out into the street whenever the door opens on its own. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 14, 2026, 3:08pm UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/7 "2026-09-14T15:08:58Z")
> [@Jojkoba](#): > > the door opens on its own. But if the gate is opening by itself, shouldn’t the first question be why? ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 15, 2026, 5:04am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/8 "2026-09-15T05:04:50Z")
The commands always come via the eWeLink cloud. When I checked the logs, I found only these entries: ![Screenshot_20260915-070408_eWeLink](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/d/de7c996bb8b596230f7a1a7ba70eabf65c035d4e.png) There wasn’t a single log entry for the other devices. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 15, 2026, 5:32am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/9 "2026-09-15T05:32:11Z")
> [@Jojkoba](#): > > The commands always come via the eWeLink cloud The log is interesting. It shows an ON command associated with the eWeLink account, followed one second later by the Inching action switching the device OFF. However, the Inching entry doesn’t necessarily mean that a separate scene sent the OFF command. As you know, inching can also be handled internally by the device firmware. So the interesting part is really the repeated ON commands coming from the eWeLink account. It would be useful to determine what is triggering those commands. ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 15, 2026, 6:18am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/10 "2026-09-15T06:18:42Z")
I have completely prevented the gate from opening accidentally, but the problem persists. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 15, 2026, 7:04am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/11 "2026-09-15T07:04:26Z")
> [@Jojkoba](#): > > but the problem persists In that case, it would be interesting to find out what is generating the ON commands. Since the logs show them coming through the eWeLink cloud, perhaps the next step is to check whether they coincide with any scene, automation, app activity or another connected client. ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 15, 2026, 7:56am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/12 "2026-09-15T07:56:44Z")
I’ve already checked that, and there’s nothing anywhere. Support doesn’t work here, so there’s no point in reporting anything. ---
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [September 15, 2026, 11:26am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/13 "2026-09-15T11:26:54Z")
> [@Jojkoba](#): > > Support doesn’t work here Unfortunately! It’s a pity that eWeLink hasn’t looked into this, because only they can really investigate or rule out what might be happening on the backend. I’ve encountered similar cases a few times myself, but in every case it eventually turned out to be something that had been overlooked. Hopefully someone from eWeLink will come across this thread and take a look. If you’ve really ruled everything else out, perhaps there is some stale data left on the server, or possibly a bug in the server-side software. ---
**Author:** ![popadak.peter](https://avatars.discourse-cdn.com/v4/letter/p/46a35a/32.png) [@popadak.peter](https://forum.ewelink.cc/u/popadak.peter)\ **Post date:** [September 16, 2026, 10:10am UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/14 "2026-09-16T10:10:09Z")
I am very surprised and annoyed. Which Sonoff device are you using? ---
**Author:** ![Jojkoba](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jojkoba/32/8490_2.png) [@Jojkoba](https://forum.ewelink.cc/u/Jojkoba)\ **Post date:** [September 16, 2026, 4:39pm UTC](https://forum.ewelink.cc/t/leave-sonoff-wifi-devices-from-cloud/209170/15 "2026-09-16T16:39:23Z")
All devices