- This topic has 5 replies, 2 voices, and was last updated 11 months, 2 weeks ago by
.
-
Posts
-
I have a basic OS with 6 zones configured, I have them configured as :
1 : A
2 : B
3 : C
4 : A
5 : B
6 : CMy intention is to not let more than 3 run at the same time even if they all get start commands at the same time. Usually the OS will handle this on its own, but only when you have a program created and is running. I just discovered that if I send start commands to all 6 stations they will run and ignore the groupings. Just wanted to see if this is expected or if I’m doing something wrong, or if anyone has suggestions on how to achieve this functionality?
Attachments:
Sequential groups are observed whether you start a zone manually or automatically by a program. Please be specific about how you started the commands to all 6 stations: did you start each zone one by one, or did you start a run-once program? According to your screenshot, no matter which way you start zones 1, 4, 7, 8 should run in sequence (i.e. no two of them should start at the same time), zones 2 and 5 should run in sequence, and same with zones 3 and 6. However, zones 1 2, 3 can run together since they are in different groups.
OK Well that is how I hoped it would work, and actually it has been working that if we have them as just regular scheduled programs, but for some reason only the API start commands are doing this on our devices.
I started them one by one, by issuing the start station command in this format:
http://192.168.1.100:80/cm?pw=a1b2c3d4e5f6789…&sid=0&en=1&t=300
I uploaded another screenshot of them all running after the start commands.
Attachments:
Do you use a script to issue the command? If so, my guess is that you were issuing all commands at once? That could be the cause because the scheduler needs at least 1 second to schedule the current station into the queue. If you send all commands at once, it may not have time to schedule existing stations into the queue, therefore it’s not able to obey the sequential group constraints.
Generally if you want to start multiple zones at the same time, you should use the Run-Once /cr command, which allows you to schedule many zones together.
Thank you for the help!
Okay that makes perfect sense! I’m building a custom scheduler overlay that currently is managing the schedule and executing station start commands manually. I’ve been thinking about trying the program feature and creating programs and instead letting OS do most of the work, I just really like having this specific front end UI for how we do things here.
Would you recommend I simply space out my script actions a bit to allow them to queue, or is it better to create programs?
You can space our script commands by at least 1 second apart. Or, if you want to schedule several zones at the same time, use the Run-Once (/cr) command as I described. Run-Once doesn’t create a program, it’s just a separate API that allows you to easily schedule many zones at once. For example, if you want to run all 24 zones, each 2 minutes, you can use the Run-Once to schedule all in one command, instead of sending 24 separate commands.
- You must be logged in to reply to this topic.