I have a scene that runs a 4 hour timer. If the scene triggers again before the 4 hours are up, does ewelink create a new scene or overwrite the existing scene. I have a rain sensor and I want to delay opening a blind until 4 hours after the rain has stopped but it needs to be 4 hours after the last time it rained, not the first time..
First of all, we don’t know what the rain sensor actually is. That’s crucial, because different devices report rainfall in different ways:
- some only send a pulse like “rain detected,”
- others maintain a binary state “rain/no rain,”
- still others provide analog values (humidity, conductivity).
Without this information, it’s impossible to say for sure how the eWeLink scene will behave, right?
We also don’t know whether your scenes run in the cloud or, for example, on iHost, because that changes the situation. So if you want advice, enlighten us a bit more 
Scenes in eWeLink start a timer every time they are triggered. If another trigger occurs within those 4 hours, the system does not overwrite the previous timer but launches a new one. As a result, you can end up with several parallel countdowns.
You want to countdown from the last rainfall. That requires logic that resets the timer with each new event. In plain eWeLink this is difficult, because there is no built‑in “restart” mechanism for timers. Basically there’s no go for such an automation.
Practical solutions:
- In eWeLink you could try a condition like “if no rain signal appears for 4h,” but the platform’s logic is limited.
- In Home Assistant or Node‑RED it’s straightforward: an automation with delay: 4h and mode: restart ensures the countdown always starts from the last event.
Hi. Well, the rain sensor is simply a modified sonoff door sensor, so OPEN means No Rain and CLOSED means rain. I have a third party device that simply places a loop on the sensor when it’s wet to change state. I use the change of state to run a scene - all cloud based.
When the rain stops, then the third party device removes the loop and the door sensor changes to OPEN. Of course, it may rain again in ten minutes so it’ll be CLOSED again.
Every time it CLOSES, the auto scene will run. So my question is if rain stops and starts several times before the scene’s 4 hour delay timer reaches the end, does the scene end 4 hours after the first CLOSE or 4 hours after the last CLOSE.
Your setup works correctly as a simple binary sensor, but eWeLink scenes do not reset the timer, because each event creates a new instance. This means the blind may open 4 hours after the first rainfall, even if it has rained several more times since.
In plain eWeLink you won’t achieve the effect of 4 hours after the last rainfall. The platform has no mechanism to reset the timer on a subsequent event. If you want the counter to always start from the last rainfall, you need logic that cancels the previous countdown and starts a new one. You can’t do this in eWeLink. If you care about the last rainfall logic, you need a more flexible platform (HA, Node‑RED, iHost), where the timer can be restarted.
In short, it’s not possible with eWeLink automation aka scene.
write 3 scenes: (scene 1) if no rain detects then wait for 4 hours + open the blinds.
(Scene 2) İf rain detects then close the blinds + disable scene 1
(Scene 3) If no rain detects then enable scene 1
I use this scenes combination to control a light with motion sensor. It works perfectly. (When sensor detects motion it trigers light and after 2 minutes light goes off, but İf there’s a motion detected in 2 minutes period it continues to light up.so in short 2 minutes period starts with the last detection)
Thanks. I’ve set it up and I am now waiting for it to rain!!!
Your trick with three scenes looks clever, but it only looks that way. In eWeLink there is no real “disable/enable” for a scene - they always run. What you’ve built is just a workaround with conditions, which will inevitably break down and get confused when states switch quickly. In practice, it’s not a very smart or particularly inventive solution, because it doesn’t provide any guarantee of reliability with a 4‑hour timer.
You’re right! My combination works perfectly but sometimes it failures. So as you said, there’s no guarantee..
In my case it’s controlling a blind, so it if stays out or comes in inadvertently it’s not a big deal. I had wondered whether to use a Zigbee mini switch (which I’m only using as a Zigbee network relay) to be the logic of ON and OFF.
A Zigbee end device, such as a Zigbee mini switch (that also may act as a router), is not responsible for any control logic. At most, it handles simple ON/OFF logic, and that’s it. A Zigbee router or switch is not a logic controller. Control logic always resides on the controller side (the coordinator + the automation system). The logic that decides whether something should turn on or off is implemented by platforms such as eWeLink, Cube on iHost, or Home Assistant with Zigbee2MQTT or ZHA.
This is not about lecturing, but about naming things according to reality