Well the situation you described is exactly why it’s complicated to implement the two-level grouping feature. What happens if a group is supposed to run but then a user also want to manually operate one zone in the group? It’s non-trivial to clearly define the logic. Say zones 1, 2, 3 are in parallel group P1, what if P1 is currently running (i.e. all of zones 1, 2, 3 must be running) while the user also wants to stop zone 1 individually? Should that be allowed? Which should take priority? Also, if P1 is running and the user manually starts zone 1 again for a different period of time, what should zone 1’s duration be? Without a clearly defined logic, the firmware will not have predictable behavior. I don’t think any one implementation can meet all users’ need. I’ve seen a lot of different requests for scheduler features, some of them conflict with each other. So I am afraid one firmware can’t fit everyone’s need. But the project is open-source so you can always modify the firmware in any way you want to fit your need.