|
Post by atekind on Nov 8, 2011 11:00:20 GMT -5
Hey Guys and Girls, i have done a search to no avail, but im interested in how you are setting up your vacation modes?
On homeworks I simply need to select the affected loads and then program three seperate functions: record, play, stop this would then watch and playback your home use with randomization.
It appears in Ra2 that i need to make a timeclock event as an "away" type, and then make an "away" button to engage it but in order to properly simulate a "lived in home i assume i would need to make several different timeclock events that turn on and off different lights at different times and make them all "away" type?
for example:
"Away timeclock #1" - at sunrise - lighting load "a" 90%, lighting load "b" 90% "Away timeclock #2" - at noon - lighting load "a" 0%, lighting load "b" 0%, lighting load "c" 90%, lighting load "d" 90% "Away timeclock #3" - at sunset - lighting load "c" 0%, lighting load "d" 0%, lighting load "e" 90%, lighting load "f" 90% "Away timeclock #4" - at midnight - lighting load "e" 0%, lighting load "f" 0%
then set up a button as "away" that the client can manually engage when they leave on vacation?
Any thoughts are appreciated guys!
|
|
|
Post by hanshi on Nov 8, 2011 11:29:29 GMT -5
Sounds to me like you get the idea. In RA2 you basically need to script out the day as seen when the system is in Away Mode.
|
|
|
Post by atekind on Nov 8, 2011 16:50:25 GMT -5
man thats a bit cumbersome hey?
|
|
|
Post by bradkas on Nov 8, 2011 19:04:16 GMT -5
The problem is, with only one time clock mode active at a time, all your 'normal' events need to be part of your 'away' mode. This will also cause them to be randomized whether you want to or not.
|
|
|
Post by atekind on Nov 8, 2011 23:25:48 GMT -5
Hold on then, I dont have to remake them, i just check the "away" box on all of my "normal" timeclock events as well right
|
|
|
Post by bradkas on Nov 9, 2011 9:42:36 GMT -5
Yes.
|
|
|
Post by Atekind1 on Dec 1, 2011 22:17:39 GMT -5
So with only one mode active at once i guess i need to stagger things hey? for example if i wanted 2 different things to happen at sunset i would need to set up event 1 to start 1 minute before sunset and event 2 to happen 1 minute after sunset?
|
|
|
Post by bradkas on Dec 2, 2011 0:13:31 GMT -5
Well, it's only one time clock mode active at once, not time clock event. So within a time clock, events can be scheduled to happen at the same time, but you cannot enable multiple time clocks to be active simultaneously.
Hopefully that makes sense, it's a very limited and silly implementation.
|
|
|
Post by atekind on Dec 2, 2011 7:20:56 GMT -5
So if my time clock event takes 45 seconds to complete due to fading and delays, then the events need to be at least 46 seconds apart?
Eg.
"Timeclock #1" - at sunrise - lighting load "a" 90%, lighting load "b" 90%, 45 second fade "Timeclock #2" - 46 seconds after sunrise - lighting load "c" 90%, lighting load "d" 90%, 30 second fade "Timeclock #3" - 77 seconds after sunrise - lighting load "e" 90%, lighting load "f" 90%, 30 second fade
|
|
|
Post by maguire on Dec 2, 2011 11:08:53 GMT -5
The timeclock programming event tab has "to the minute" accuracy, you cannot drill down to seconds.
You do not have to wait for one event to complete to start another
Example
Sunrise: Turn Landscape Lighting OFF, fade of 10 minutes Sunrise + 1 minute: Turn Hallway Lights On, Fade of 2 seconds.
|
|
|
Post by flash on May 1, 2012 13:54:23 GMT -5
Well, it's only one time clock mode active at once, not time clock event. So within a time clock, events can be scheduled to happen at the same time, but you cannot enable multiple time clocks to be active simultaneously. Hopefully that makes sense, it's a very limited and silly implementation.
|
|
|
Post by flash on May 1, 2012 13:54:35 GMT -5
Well, it's only one time clock mode active at once, not time clock event. So within a time clock, events can be scheduled to happen at the same time, but you cannot enable multiple time clocks to be active simultaneously. Hopefully that makes sense, it's a very limited and silly implementation.
|
|
|
Post by schalliol on May 26, 2012 23:48:34 GMT -5
Just to re-post an item someone else mentioned which I think is a bug, or at least a design flaw. Your normal event should NOT be randomized in an away mode. It's silly if you use dusk/dawn every single day and then when you're away you use dusk/dawn + & - 30 minutes. I really hope Lutron fixes this.
|
|
|
Post by bradkas on May 27, 2012 17:12:55 GMT -5
Yes, it could be as simple as a check box within the Away Time Clock mode were you define randomized or not. This box would only appear within the settings of an Away mode event to avoid confusion.
|
|
|
Post by maguire on May 30, 2012 16:14:47 GMT -5
TOTALLY AGREE Brad.
|
|