It doesn’t work that way. Your Scene 2 doesn’t continuously monitor anything. Scenes do not monitor. There are simple automations of the “if-then” type. In your example, it goes like this: if lamps change from off to on, then wait 20 min. There’s no next step defined. This scene waits 20 min. and do nothing else. On the “Komplet foto” screenshot the situation is different, because the next step is defined. It means that after 20 min. the lamps go to “off” state. No other conditions are set. The scene is executed despite of anything else. If you switch the lamps off manually, the scene will go on anyway. When you switch the lamps off and on again during the 20 min period, another instance of your Scene 2 is fired.
As pointed out before, scenes in the eWeLink cloud platform are simple automations that are not capable of performing complex scenarios, including monitoring. That’s why you need to turn to something else if you want to achieve your goal. Getting angry and grumbling won’t help or change anything. This is how it was conceived.
To put it simply, the creation of complex automations (scenes) requires precision to achieve the desired results. The way in which the implementation of the next steps takes place is also a difficulty, especially when the states are to be monitored. What is supposed to happen when conditions change? Is the automation to be continued, restarted, queued?
