I am using Integrated Mode Manager on my C8 Pro hub, running the latest update.
In trying to figure out why my hub did not go into Vacation mode as expected, I discovered that the rule under the hood is set up as:
Set mode to Vacation unless Away. That doesnt show up on the main interface. And I think it explains why my expected mode change didn’t happen, because the hub mode would have been Away when the trigger for Vacation occurred.
(1) What’s going on here? Why is “unless Away” being forced into the rule under the hood? Is this expected behavior?
(2) How can I revise this so that Vacation mode can be triggered even from Away mode?
That is the expected behavior. Away mode is special and overrides any other mode. The hub tracks the ‘shadow mode’, which is the mode it would return to if not away.
You could try reversing the exit condition on your away mode… it should exit away when everyone departs the 50 mile presence, not when someone arrives in the 50 mile presence.
Everyone leaves household –> Away mode –>. Everyone leaves 50 mile –> Exit away mode, trigger vacation mode.
In vacation mode –> Someone enters the 50 mile zone, nothing happens. Someone enters the household presence zone, Home mode should activate.
This may create a race condition though where it either doesn't work or doesn't work reliably.
You might be better off setting the vacation mode through Rule Machine so you can account for that, or handle all mode changes through rule machine. Or just use the 50 mile presence directly in whatever rules are affected by vacation mode.
I have a virtual presence sensor called “guest presence”. I don't have a hub mode named guest… only times of the day day/sunset/night etc) plus Away. My automations use both mode and guest presence as conditions where needed.
