This is interesting to me because I like to view the FarmBot as this 24/7 gardener that doesn’t complain about their bad back and horrible working hours. Why couldn’t Farm Events be pushed back indefinitely (or… max 24 hours, which would indicate your schedule is too full)?
The reason I’m asking is because I’m struggling getting my head around Nested sequences and Plant Groups and their intended usage.
If Regimens are designed to string Sequences together to form the basis of plant-care for a type of plant, it makes sense to keep these garden-agnostic. Meaning that a Regimen doesn’t know about the plants in your garden at all.
Example
I’m planning on growing 30 radishes in my garden. But I don’t want to harvest all 30 at the same time. So I’m making groups of 3 radishes, meaning I’ll end up having 10 groups.
Each group is assigned the same Radish Regimen, but using Farm Events, the start date for each group is staggered. But they all use the same set of sequences to be cared for.
Radish like lots of water. My Regimen dictates they are watered daily. But since all groups are using the same Regimen, they will all be watered at the same time in the Farm Events.
I get the feeling once I get to the point where 3 or 4 groups are “active” at the same time, FarmBot will struggle caring for my radishes after group 3, simply because their triggers are going to be dropped.
I don’t want to create a Radish (copy 1) Regimen just to be able to manually offset the watering time on each day. I think that goes against the design intent of Regimens. But I think something needs to change in order to prevent many events that happen to get scheduled at the same time to become dropped.