The rule engine in EWeLink is pretty primitive. I would suggest you expose all your ewelink devices to Smartthings and run automations from Smartthings app. Quick and Reliable.
In eWelink, it is not possible to select the same device in IF and THEN, but it can be bypassed by creating a manual scene to turn off the “Corredor” device, and then adding this manual scene to the delay …
Unfortunately, yes, it’s a limitation in eWelink and I don’t understand why, then I have to unnecessarily create manual scenes and bypass the limitation in various ways. I have tried others (BlitzWolf, LSC - same applications…), there you can select the same device for both IF and THEN. But again in favor of eWelink - they are trying to improve the application, I don’t even remember any major improvements for the aforementioned.
Single-channel switch type devices are not allowed to be used as trigger conditions and execute actions at the same time in a scene, which may be the logic to avoid the scene loop putting a huge strain on the server, let me think about it…
If I create a manual scene (MS) where the status of device A (Reverse) is to be changed and for this I create an automatic scene for example:
IF Device A state is On AND temperature <= 20
THEN
launch (MS)
it’s the same as what the automatic scene would do without the (MS) if it could be used:
IF device A status is On AND temperature =< 20
THEN
device A - Reverse
and there would be one less unnecessary manual scene and at the same time it would make the scenes clearer.
After just rolling it out (Reverse instead of just On and Off) I redid the automatic scenes with the RF states and then halved the number of them than needed before and got rid of all the supporting manual scenes as well.