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?
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.
I blocked all the devices on the MikroTik; at least now they won’t arbitrarily open the gates at the houses.
Really?! How come?
Curious! Last night happen the same to me. My garage door open without any action from users or automation 
My dog got hit by a car, and my child runs out into the street whenever the door opens on its own.
But if the gate is opening by itself, shouldn’t the first question be why?
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.
I have completely prevented the gate from opening accidentally, 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.
I’ve already checked that, and there’s nothing anywhere. Support doesn’t work here, so there’s no point in reporting anything.
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.
I am very surprised and annoyed. Which Sonoff device are you using?
All devices