@pierre-gilles, I am creating a specific topic to avoid cluttering the post Parlons de Gladys V4 which is already quite full and continues to fill up.
When I create a scene to turn on the pond pump at a certain time, then wait 8 hours to turn it off, no other scene works alongside it. So is this a bug, or is this normal behavior? So I wonder what is the point of Wait? If I want to automatically turn off the staircase light after 3 minutes, will no other scene be able to be launched during this time?
At 00:00 every day I retrieve the state via a Get device value of various lights (for the moment) and then use the Only continue if function. I wanted (all this for testing since I would then have to integrate motion detectors) that if at least one light is on, send a \nTurn Off the Lights to all the lights. If I use the equal to 1 operator, it doesn’t work. I have to use the greater than or equal to 1 operator which works. Is it because in the database the value of the light state is 1.00 and not 1?
All this of course took place at the same time as the REX test.
For information, with each attempt I paste message sends to be sure of the steps that pass or not. So on point 1, the first message does not even pass. This indicates to me that no other scene can be launched while a scene is in wait. I have to restart Gladys to regain the use of other scenes.
@pierre-gilles, so this morning we got confirmation that the pump was indeed stopped 5 hours later, which shows that the scene was still ongoing. And in the process, all the scenarios I had tried to launch after the pump scenario were launched (turning off the staircase lighting 3 minutes after it was turned on - even though it wasn’t and hasn’t been turned on since 00:50 - turning off the lighting in the garage area - even though no lighting was on anymore).
This means that the scenario was indeed played and kept the actions to be performed in memory, but it did not execute the actions, they were just queued.
That’s an interesting side effect I didn’t think people would set up scenarios that would last so long, there is indeed a queue for scenario execution with a concurrency of 1 ^^ I’ll change the concurrency:
Very interesting! I’ve created a task, I need to investigate before I can answer you, right now I don’t know
Perfect, I’ll test it tonight and let you know tomorrow
Ok!! Super!! Thanks in advance ^^ Have you tried repeating the experience? Just to make sure it’s not just on my side!! Which would be annoying because I’ve tested several things ^^
Edit: Well, I did it now after all ^^ It works perfectly, at least for 2 scenes at the same time. We’ll need to take the time to test with more.
I didn’t think people would set up scenarios that would last so long, there is indeed a queue for scenario execution with a concurrency of 1 ^^ I’ll change the concurrency:
