i have a Scene called “comming home” and another one “going out”
it simple does disarm, and turn some lights on in the driveway (if night)
however if i do manually or with other triggers/scenes/luup do the same actions this does also set the scene to be active.
also the other way arround.
is there a way to actually keep a Scene to be active “triggered” even if it does nothing anymore ?
the reason is to check then on the scene status (if possible) with other code later on
and it also looks really nice on the HomeWave app as well to see that i’m home … (or even not)
the “good thing” on its become inactive is that i can just push it again if someone else comes without the luxury having it triggered via vehicle tracking (guest) but that does not really happen much anyway.
Not quite sure about your description of scene status… Normally they just run and finish.
For the type of status flag you’re talking about, I capture the state with a virtual switch set by a scene which gets triggered by some event or other… Not sure if that’s clear or not? Works just fine with HomeWave.
yeah guess my strange way of explaining things made it not really more easy 
example:
scene A does turn on Light1 and Light2
if i execute the scene the light1 and light2 change status to active and so does the scene.
so i have 3 active items … so good so far
if i now manually turn off light1
light1 AND sceneA become inactive (which makes sense)
but now i can not check on the status of the scenea which was triggered by another method.
you mean instead of punch the scene directly triggering a virtual switch instead ?
and the switch hit the scene if change ? (actually while iam writing this it makes already more sense to me) 
ill try that
I kind of have the same question but mine has an immediate and a delay action in the scene.
Can someone answer this…
I have a scene that has multiple triggers. For example…turning on a light…
The scene has an immediate action to turn on the light, then a delayed action to turn the light back off after say 5 minutes.
My question is…if the scene is triggered by trigger#1, and after 2 minutes, Trigger#2 re-triggers the same scene…does the scene start a second instance of the scene and therefore have a second simutaneous timer running and after the delay, and have the lights turn off 2 times.
For example…
If I trigger sensor#1 at 10:00am, then 2 minutes later I trigger sensor#1 again, or sensor#2 at 10:02am, I know I would get the action of light on at both 10:00 and 10:02 but do I get the action light off at 10:05am, 10:07 or both 10:05 and 10:07am?
Hopefully I haven’t confused you all:)
Terry
Terry, what you describe is exactly what happens, dumb though that may be. A veritable marketplace of replacements that don’t suffer from this shortcoming have sprung up to fill the void. You could search for these terms to find them. Program Logic Timer; Smart Switch plugin; Countdown Timer plugin.
nullx8, scene “active” status is dodgy at best, broken by design at worst. Most of us stop relying on it pretty early.
The trouble stems from the expectation that after a scene runs, there is some vestigial “memory” of it having done so. In reality there isn’t: once the scene has started, its actions are queued and the scene ends. There are some rudimentary settings that mark the scene with a binary “active” veneer; these you have probably already found, and found to be inadequate.
The workaround, like is often the case in Veraland, is to roll your own state, using a variable container or virtual switch, as has already been recommended.
futzle,
I’ve been having some troubles with this tuff…I’ll admit. I thought I was a good programmer before, but I question that now (:.
I was using a few PLEG timers and they were great…saved a lot of efforts for lazy guys like me But I added a forth one and suddenly, everything broke down. Nothing was responding…even scenes and triggers that once were working great. I attributed it to no cpu resources left and was pretty disappointed. Maybe I was creating it with my potentially unneccesary actions. Like for example…If a door is opened, then turn on a light, then after 5 minutes turn the light off. But what if…someone turned that same light on before they opened the door? What if they turned it on and never openned the door? I was forced to add the manual lighton to the trigger so that after 5 minutes the light would still go off when the person never actually opened the door. When I place the LightOn as a trigger to the scene that actually turns the light on, does the scene run twice, and create 2 instances of itself, and depending on how many things are going on, and how many times someone opens and closes the door, cause the system to be bogged down.
I was thinking of maybe setting a system variable to recognize a scene was running and when the same scene runs, it could just check the system variable and kill itself if the variable is already set? does that work?
Terry
Your previous post to nullx8 kind of gives me the answer I was looking for…I’ll retry the PLEG and Timer. Or use a Variable container…I’ve got a bunch of those working and they seem pretty stable. I’ll check my scenes state somehow. I see even more advantages to the PLEG, because it has the restart function. If I just try and check to see if a scene is running and abort…the PLEG works even better because it could actually restart the time on a retrigger. I like it…I will perservere…lol.
Thanks again,
Terry
@tvipond
You may run out of memory if you add too many plugins … but it’s very unlikely that you will run out of CPU cycles unless you put things in some sort of infinite loop.
Also the PL timer is referred to as PLTS If you add a bunch of these you may be running out of memory … How many devices (Z-Wave and Plugins) do you have ? Do you have a Vera Lite or a Vera 3 ? Do you have a memory stick installed for Log Files ? Otherwise logs eat up memory.
A single PLEG device (not a PLTS) can handle timer actions for a number of independent lights. I recommend the PLTS only if you need UI (User Interface) control of the timing cycle, and PLEG otherwise.
If you want a bunch of virtual switches to keep various states, and you are worried about memory usage, you could try my MultiSwitch plugin. With this, you get eight switches in one device. See: Here.