To be more specific: The “off timer” (minutes) is a bit hidden in a weird location within the SmartLights app.
Just create a new routine within the SmartLights app, select the switch you want to control, and then trigger based on “POWER ALLOWANCE.” (I think it’s the LAST choice, at the bottom of the screen/page?..)
Within POWER ALLOWANCE, you can actually set it to trigger based on “MINUTES” the device has been on/operating.
As mentioned above, this is somewhat of an “always” approach. e.g. ALWAYS turn off the front porch lights after they have been on for 10 minutes. Note: The minimum duration is ONE minute. (I wish they allowed fractions of a minute, so we could use .5 minutes to create a 30-second rule. But, it only supports whole numbers.)
So, if you want to CONDITIONALLY have this rule/routine run, then you need to create a second (virtual) switch via the IDE website interface (aka a “Simulated Switch.”) Then, you point your ALWAYS-OFF script at this “simulated switch” – instead of pointing it at the REAL/PRIMARY switch.
Example: You have four Phillips Hue bulbs in a ceiling fan in your dining room. You name the bulbs: CF1, CF2, CF3, CF4. You then create your PRIMARY simulated-switch named “dining room light” to control all four of these bulbs concurrently. So, when you turn ON the “dining room light” – all four of these bulbs come on together. (Ditto for turning them off as a “team,” too.)
Let’s say you want to create a routine that turns these lights ONE when you come home?
Typically: You would just create a routine that would see your presence-sensor-fob “arrive,” and therefore turn “on” the “dining room lights.” (Sounds straight-forward… but… wait for it…)
But, what if you then want these lights to automatically turn OFF 2 minutes later?
You would THINK that you would just create another routine, that would turn OFF these lights when POWER ALLOWANCE exceeds 2 minutes – right? (Sorry, that’s the wrong answer.)
Because when you sit down to eat dinner, and turn on the “dining room light” – it would then shut-off automatically 2 minutes later.
So, what you do INSTEAD is this:
After creating the primary switch, you then create a SECONDARY simulated-switch, too (and point it at the same four bulbs = CF1, CF2, CF3, CF4.) You now have TWO simulated-switches, that can control this team of lights.
Let’s name this SECONDARY switch “DR-Bulbs” (DR = Dining Room.)
You then create your presence-sensor routine to turn on the “DR-Bulbs” switch (instead of the switched named “dining room lights” switch.)
Similarly, you create your POWER ALLOWANCE “off” routine to point to DR-Bulbs switch, too.
So, if/when you control the lights via the “dining room lights” switch – they will remain on, until they are manually turned off.
Whereas, when you control the same lights via the switch named “DR-Bulbs” – they will always turn off 2 minutes after they are turned on.
I leverage these same “secondary switches” and delays for all kinds of other events. e.g. spoken “welcome home” events with my Samsung speakers. If you trigger based on the presence sensor, then the “welcome home” message plays too early (as you are still approaching your front door.) By adding a 1-minute delay/pause routine, the speaker says “welcome home” once I am indeed inside the house.
I hope this level of detail helps. Again, it’s a little hidden in the POWER ALLOWANCE field. Within it, you will find the option for “minutes.”