It is easy to trigger on a mode change into a mode. However what about triggering when changing out of a mode. For example, I have a Cleaning Mode I use for when cleaning house. I have a series of different ways through buttons and virtual buttons to activate that mode. Once there, many other rules are paused to prevent various triggers from interrupting Cleaning. I do not believe it is efficient nor good programming to have to attach "resume" actions to every rule in my system. What I have right now is an action that is called by the "Cleaning Start" rule which pauses the important actions then a reciprocal action which resumes all those that are paused. That action has to be called by just about every other automation in the system. What would be better is a trigger that calls the resume action whenever the mode changes from Cleaning to just about anything else.
I'm trying to decide the most efficient and tidy way to achieve this and I am hoping the community has a known solution before reinventing the wheel. This seems like one of those trivial ones…