Request these two enhancements to integrated mode manager:
Abilty to exclude switching to a mode based if a trigger is true
Ability to force use of an alternative schedule if a trigger is true
Probably simpler if implemented as additional inputs following the simple UI model vs expanding it into an OR or AND NOT type moment - things like that are probably better be done in rule machine etc but both these scenarios are likely easy entry-level mode moments.
Sample Use case 1:
Manually set "Vacation" switch means we skip "wakeup mode" entirely to avoid hot water recirculator, bathroom floor radiant heat, and morning music from turning on at 6am.
Sample Use case 2:
Holiday app toggles (or user manually sets "day off" ) holiday switch so you can sleep in. In this case, you want to say presence of this switch being "on" means use Alternative Schedule for mode evaluation (eg, weekend 10am switch to day)
Thus what you really may be looking at is a Mode Scheduler type of application that allows you to provide alternate Mode sequences and triggers. Could be a fun exercise…
Agreed. There are lot of ways I can accomplish this, I was just suggesting that with the addition of a couple bool evaluations, the simple easy-to-manage mode stuff will likely avoid just about everyone from having to do a LOT of complex rules to implement modes in another app, or the need to write a full fledged schedule app for what's otherwise a pretty solid way of managing modes in all the scenarios I could think of. There's already a Holiday plugin, and there may be other actions (who knows, weather station integration?) that could provide something with a conditional bool evaluation or a "use the alternative schedule" evaluation.
(I did have very similar things written in rule machine, but it was pretty complex, and but for 2 enhancement requests, I essentially ripped out all the rule code in leu of the new manager)
