Does virtual switch as trigger retain on test or only when turned on

I want to trigger an action if a virtual switch is “on” and during a scheduled time.
When the scheduled time comes and goes will the subsequent trigger “on” succeed or only if the virtual,switch is turned on during the scheduled time?

It appears that subsequent evaluations of the condition based on time passing fail. cease the switch trigger fails because it has not changed between condition evaluations??

Set up your scene as you would based on your desired schedule. then add a test for the switch in the Luup for the scene. it will run/cancel the scene based on the status of your switch.

Example:

– this script cancels the change of the thermostat to the overnight temperature if Vacation Mode is off (0)

local VacationStatus = luup.variable_get(“urn:upnp-org:serviceId:VSwitch1”, “Status”, 66)
if (VacationStatus == “0”) then
return false
end

If you have a condition:

CondName VirtualSwitch and Schedule

If CondName is already true (from the previous schedule) and a new Schedule happens, the CondName will not fire because it is already true.
If you want it to fire every time it evaluates to true then rename to: _CondName. The underscore as the first character changes the behavioir.

This behavior seems to be different than:

VSProperty(Status)
condition VSProperty == 1 and schedule ----- which does work even though status has not changed where tVS has not changed and it fails (I think)

so:
VSProperty == 1 succeeds
and
VSTriger and schedule fails

Results now ok!
Test set up as follows and it is working.
Condition: cTestOn tHome AND sTest — turns light on
Condition: cTestOff tHome AND NOT sTest — turns light off

I don’t know why it started to work - probably something I did with the schedule - not the on/off trigger.
Note - no “_” in condition name - I am still not clear on why that would change things.

Thanks