Hi,
is there any way I can get S2 to associate with it’s own S1 ?
I have 4 landings, with two switches on each landing. Lets say I’m on landing 2. When I press S1 (up) I want landing 2,3,4 lights to turn on, when I press S2 (down) I want landing 2,1,0 lights to turn on.
Also I need to somehow enable double click to turn on/off all lights, but looking at parameter 6 there is not an option for double click to turn ‘off’, only ‘on’.
Any direction you guys might have would (as always) be greatly appreciated.
I doubt that it is possible to have a multi-channel device associate with itself at the Z-Wave level let alone persuading Vera to configure it. If you decide to try it, be aware that you may have to exclude and re-include the device to remove failed association attempts.
I would implement the logic in scenes or PLEG. There will be a small delay before the lights respond to the switches but you should be able to program whatever sequences you want.
I recognize the double-click of an FGS221 switch in a PLTS device using the condition: LightOn and (LightOff; LightOn < 10) where LightOn is a trigger for the switch turning on and LightOff is a trigger for the light turning off.
Hey Rex,
thanks for the reply, I’ll give it a try. I’m guessing I need to basically remove all current S2 associations and use PLTS (I love it) instead. Or do you mean to use S2 association to control all the other lights and PLTS to turn on S1?
Well that choice is up to you. The advantage of retaining associations is that they are virtually instant in operation - and will still function if Vera is offline. The downsides are that they can be a pain to manage and they lack flexibility. If you can implement some of your logic with associations, you may as well do so.
PLTS is a good choice for a simple timer - like put on lights for x time then turn off. More complex logic is going to require PLEG.
[quote=“RexBeckett, post:4, topic:177595”]Well that choice is up to you. The advantage of retaining associations is that they are virtually instant in operation - and will still function if Vera is offline. The downsides are that they can be a pain to manage and they lack flexibility. If you can implement some of your logic with associations, you may as well do so.
PLTS is a good choice for a simple timer - like put on lights for x time then turn off. More complex logic is going to require PLEG.[/quote]
can you or someone be kind enough to give a specific example of PLTS to start me off; say turn lights on Monday and Wednesday 20 minutes after sunset (random on between the 2 days) but only at night (using Day Or Night plugin). then turn off say at 11 pm. just too complicated for my brain but i consider my self very good in following instructions. thanks in advance.
Conditions DoOn ItsNight AND MWEvening DoOff ItsNight AND Not MWEvening
Actions DoOn Turn On Light X DoOff Turn Off Light x[/quote]
Thank you. i tested it for couple of days and made some modification and lights turn on/off on schedule. i have about 11 “away from home” scenes to turn on/off/dim 11 lights at different times and days. now i can consolidate them in 1 PLEG and clean up my dashboard clutter.
however, i am not sure how to do this: i have 1 scene that turns dimmable light at 70%; after 3 minutes turn off, after 20 minutes turn it back on at 100%; after about 30 minutes, dim to 50%, after 1 hour turn it off etc, etc. i wonder if you can give me an example of how to do this in PLEG (or PLTS). i don’t have a clear view of when to use PLEG/PLTS. thanks for your help.
PLEG actions can include delays. This would a way to handle short intervals - like on for three minutes then off. For longer delays, you can create a self-triggered timer and start it with an action Start Timer then have a condition that is fired by the timer ending.
PLTS is good where an accurate time interval is required but the logic is fairly simple. I use it for timing extract fans and security lights. When you need multiple time intervals and more complex logic, PLEG is generally the better choice.
[quote=“RexBeckett, post:8, topic:177595”]PLEG actions can include delays. This would a way to handle short intervals - like on for three minutes then off. For longer delays, you can create a self-triggered timer and start it with an action Start Timer then have a condition that is fired by the timer ending.
PLTS is good where an accurate time interval is required but the logic is fairly simple. I use it for timing extract fans and security lights. When you need multiple time intervals and more complex logic, PLEG is generally the better choice.[/quote]
Just one more question for clarrification and i really appreciate your patience. When you say self-triggered timer and Start Timer, do you mean using the Count Down Timer plugin?
No, I’m talking about PLEG. You can create a PLEG schedule with Start Type:Self Trigger, Stop Type:Interval and Every: set to your required duration. This type of schedule does not start automatically.
You can start the timer from a PLEG action using the Advanced tab to select your PLEG device and the action Start Timer for your named schedule. You would do this at the point you want the delay to start - say when you turn a light on.
You can detect when the timer has completed by including the term NOTname-of-your-schedule in condition statements along with other terms as required.
[quote=“RexBeckett, post:10, topic:177595”]No, I’m talking about PLEG. You can create a PLEG schedule with Start Type:Self Trigger, Stop Type:Interval and Every: set to your required duration. This type of schedule does not start automatically.
You can start the timer from a PLEG action using the Advanced tab to select your PLEG device and the action Start Timer for your named schedule. You would do this at the point you want the delay to start - say when you turn a light on.
You can detect when the timer has completed by including the term NOTname-of-your-schedule in condition statements along with other terms as required.[/quote]
i sincerely apologize for being so stupid with this pleg thing because i really dont know what i am doing. i waited for a week to see if i can figure out my mistake but to no avail. the LAMP turns on/off as scheduled. but my WALL ESCONCES are not doing anything. is the “self triggered” and “start timer” supposed to turn the lights on/off daily? i understand the esconces lights are not on any day schedule. attaching my PLEG status. thanks
Sorry, @waltzer11, but your capture doesn’t show the whole of the PLEG status report. Try printing it to a PDF and attaching that.
From what is there, it doesn’t look as though the timer was ever started. If you can attached the whole report I should be able see whether there is a problem with your actions.
[quote=“RexBeckett, post:12, topic:177595”]Sorry, @waltzer11, but your capture doesn’t show the whole of the PLEG status report. Try printing it to a PDF and attaching that.
From what is there, it doesn’t look as though the timer was ever started. If you can attached the whole report I should be able see whether there is a problem with your actions.[/quote]
sorry about that. here is a pdf attachment. thanks for your time. i want the wall esconces to turn on at say 70% (dimmable), after 15 minutes dim to about 15% after 30 minutes turn off. then after 45 turn on again at full 100% to have a “live-in look” if we go away. if you will be kind enough to give me a sample of this sequence, then i can follow and do the other lights. thanks.
Now I understand what you want to achieve, I will suggest a different approach.
I also wanted to have a realistic simulation of normal domestic activity when I am out. I solved it by creating a simple timer plugin that can be used from within PLEG to sequence lights, radios and blinds. The timer can use absolute, relative or randomized times as required. I did this before RTS added the self-triggered timer to PLEG. The key feature of my LogicTimer plugin is a settable Flag variable that can be used to enable each condition statement in the sequence. I believe it is possible to do this with PLEG alone but the logic required to steer the sequence will be more complex.
Take a look at LogicTimer. There is an example in the thread that shows how it may be used to orchestrate a lighting sequence.
If you do want to continue with PLEG’s Self-Triggered timer, there are a couple of problems with your current setup:
You need to move the action that starts EsconsesTimer to the condition LampOn otherwise it will never be started.
The way you have your delayed actions set for EsconsesOn and EsconsesOff, you are not getting any real benefit from using EsconsesTimer. You could do it all with delayed actions triggered by LampOn.
You will have problems with the condition EsconsesOff. It will fire whenever it becomes night and, after the delay, turn off the lights. You would need to add a term signifying that it is in automatic mode. This could be the state of your Home/Away switch or a term that is true only when EsconsesTimer has just ended. For example:
Conditions ETimerEnded Not EsconsesTimer EsconsesOff ItsNight AND (ETimerEnded; NOW < 1:00)
[quote=“RexBeckett, post:14, topic:177595”]Now I understand what you want to achieve, I will suggest a different approach.
I also wanted to have a realistic simulation of normal domestic activity when I am out. I solved it by creating a simple timer plugin that can be used from within PLEG to sequence lights, radios and blinds. The timer can use absolute, relative or randomized times as required. I did this before RTS added the self-triggered timer to PLEG. The key feature of my LogicTimer plugin is a settable Flag variable that can be used to enable each condition statement in the sequence. I believe it is possible to do this with PLEG alone but the logic required to steer the sequence will be more complex.
Take a look at LogicTimer. There is an example in the thread that shows how it may be used to orchestrate a lighting sequence.
If you do want to continue with PLEG’s Self-Triggered timer, there are a couple of problems with your current setup:
You need to move the action that starts EsconsesTimer to the condition LampOn otherwise it will never be started.
The way you have your delayed actions set for EsconsesOn and EsconsesOff, you are not getting any real benefit from using EsconsesTimer. You could do it all with delayed actions triggered by LampOn.
You will have problems with the condition EsconsesOff. It will fire whenever it becomes night and, after the delay, turn off the lights. You would need to add a term signifying that it is in automatic mode. This could be the state of your Home/Away switch or a term that is true only when EsconsesTimer has just ended. For example:
Conditions ETimerEnded Not EsconsesTimer EsconsesOff ItsNight AND (ETimerEnded; NOW < 1:00)[/quote]
thanks. just for clarification, i am testing this PLEG with 2 lights; “lamp shade” and “wall esconces”. i have 2 wall esconces sharing 1 GE dimmable switch. thanks for your input. i will see what i can do to implement your suggestions and let you know.
[quote=“RexBeckett, post:14, topic:177595”]Now I understand what you want to achieve, I will suggest a different approach.
I also wanted to have a realistic simulation of normal domestic activity when I am out. I solved it by creating a simple timer plugin that can be used from within PLEG to sequence lights, radios and blinds. The timer can use absolute, relative or randomized times as required. I did this before RTS added the self-triggered timer to PLEG. The key feature of my LogicTimer plugin is a settable Flag variable that can be used to enable each condition statement in the sequence. I believe it is possible to do this with PLEG alone but the logic required to steer the sequence will be more complex.
Take a look at LogicTimer. There is an example in the thread that shows how it may be used to orchestrate a lighting sequence.
If you do want to continue with PLEG’s Self-Triggered timer, there are a couple of problems with your current setup:
You need to move the action that starts EsconsesTimer to the condition LampOn otherwise it will never be started.
The way you have your delayed actions set for EsconsesOn and EsconsesOff, you are not getting any real benefit from using EsconsesTimer. You could do it all with delayed actions triggered by LampOn.
You will have problems with the condition EsconsesOff. It will fire whenever it becomes night and, after the delay, turn off the lights. You would need to add a term signifying that it is in automatic mode. This could be the state of your Home/Away switch or a term that is true only when EsconsesTimer has just ended. For example:
Conditions ETimerEnded Not EsconsesTimer EsconsesOff ItsNight AND (ETimerEnded; NOW < 1:00)[/quote]
i created a logic timer device and called it “lighting timer”. just to clarify, there are no buttons in the device (see attached). i will try to test it with your examples.
Best Home Automation shopping experience. Shop at Ezlo!