I have a suggestion for the heat boost feature. Is there a way, at least for Flex Daily users, for there to be also a choice in heat/cool rules between increasing/decreasing run times for Fixed users and adjustment of crop coefficient, such as percentage increase/decrease, for flex daily users. I find this to be more robust for this premium rachio feature.
Edit: Just to add more info onto why I suggest this to add to the original post. For how it is right now, if you increase the runtime during heat waves for flex daily users (through “boosting”), you are just going to push the next run date further down. Same goes for reducing runtime during cool spells, it will move the next run date closer. That being said, you are getting contradicting behaviors on this feature for flex daily users. One is reducing frequency when you may want to increase frequency and one is increasing frequency when you want to reduce frequency when you try to “boost” this by runtimes. For fixed, the behavior works as intended but not for flex daily, as discussed, the opposite. But to replicate the intended behavior for flex daily a good parameter that you can adjust is the Crop Coefficient.