If the virtual switch condition is true at 08:00 a.m. So the routine is triggered even though the sensor condition was already true before 08:00 a.m.
One , hopefully last , question about this automation
This is another room in the same house. It works the same as the one above with one exception. Notice that the action on one of the automations shows only changing the temperature of the AC and the other one shows “turn on “ and then change the temperature. Subtle difference but possibly important. If the guests turn the ac off and then happened to lie down and be still for 30 minutes, I don’t want the automation to turn the ac back on. Apparently Smartthigs changed something in the program and I am no longer allowed to change the temperature without the “turn on” function as well. I am using Cielo Breeze Plus remotes to control the mini split and they work great. Any idea how to work around this program. I tried Smartthings support but they are useless. They just keep asking the same questions over and over and half the time they are off topic when they do answer. Boy, I miss WebCore
Oh, I guess I forgot to mention this. I wrote another automation that turns the virtual switch off at 7:00 p.m. and another automation that turns it ON at 8:01 a.m. so the trigger will actually turn on within the precondition window and basically disables the automation during the night hours. I don’t want anything changing during normal sleeping hours because the mini splits make noise every time they receive a signal even if it doesn’t change any settings. I guess I should have mentioned the other automation in the beginning. I just didn’t realize the relevance . Thanks for all your help on this. I will let you know how it turns out.
If you press turn on again when it is checked, it will be unchecked.
At least on android it works like this
If you want that at 08:00 a.m. the condition is true then you have to power on the virtual switch at 07:30 am. or you have to remove the switch being on for 30 minutes