brucesprague Posted August 7, 2007 Posted August 7, 2007 Is there anyway to create a trigger or something to turn a device off after a set time? For example, I would like to turn my bathroom lights OFF after 60 minutes (SwitchLinc dimmer) AFTER someone turns the lights ON. thanks, Bruce
Michel Kohanim Posted August 8, 2007 Posted August 8, 2007 Hi Bruce, You have finally caught up to what everyone else has been requesting: scheduling triggers and triggering schedules. Unfortunately, it has taken us a lot longer than expected to "redesign" and implement this feature. But, rest assured that it will be in our next "major" release. With regards, Is there anyway to create a trigger or something to turn a device off after a set time? For example, I would like to turn my bathroom lights OFF after 60 minutes (SwitchLinc dimmer) AFTER someone turns the lights ON.thanks, Bruce
brucesprague Posted August 8, 2007 Author Posted August 8, 2007 Michel....if there is a way....you will figure it out. thanks, Bruce
Michel Kohanim Posted August 8, 2007 Posted August 8, 2007 Bruce, Thanks so very much for your vote of confidence. With kind regards, Michel Michel....if there is a way....you will figure it out.thanks, Bruce
GPG Posted August 9, 2007 Posted August 9, 2007 Michel, I have been trying to come up with a way to do this in the mean time, because I would like to test if a device is on or off at a particular time. Do you think the following could be a temporary work around? I dedicate an unused Lamplinc to serve a my variable storage. If it is on, I am in the valid test period, and if it is off, then I am outside the test period. I then use two schedules to control the range of the test period. For example, schedule 1 turns the LL on at 8:00am and schedule 2 turns the LL off at 8:10am. I can then create a trigger to test if a device is on during a specified time frame by using the conditions: If device is on and LL is on Last night I set up something like this to trigger an email notification and it seemed to work. I did add a trigger to query the device a few minutes before, just to make sure the status was updated. I am going to test the false condition next. I just wanted to pass this by you, to see if this made sense and ask whether you had any other suggestions. Also, what do you think of the use of the LL as a crude way of implementing a true/false variable? Thanks, George
Michel Kohanim Posted August 9, 2007 Posted August 9, 2007 GPG, Wow, this is a brilliant work-around for ISY's current limitations. Wow again! Thanks so very much for your feedback, With kind regards, Michel Michel, I have been trying to come up with a way to do this in the mean time, because I would like to test if a device is on or off at a particular time. Do you think the following could be a temporary work around? I dedicate an unused Lamplinc to serve a my variable storage. If it is on, I am in the valid test period, and if it is off, then I am outside the test period. I then use two schedules to control the range of the test period. For example, schedule 1 turns the LL on at 8:00am and schedule 2 turns the LL off at 8:10am. I can then create a trigger to test if a device is on during a specified time frame by using the conditions: If device is on and LL is on Last night I set up something like this to trigger an email notification and it seemed to work. I did add a trigger to query the device a few minutes before, just to make sure the status was updated. I am going to test the false condition next. I just wanted to pass this by you, to see if this made sense and ask whether you had any other suggestions. Also, what do you think of the use of the LL as a crude way of implementing a true/false variable? Thanks, George
C Martin Posted August 10, 2007 Posted August 10, 2007 Michel, this is a good reason for being able to create a Virtual Device. It wold be an Insteon Device that has a virtual address and can be uesd to create such triggers. Just a thought.... Clarence
C Martin Posted August 10, 2007 Posted August 10, 2007 theses devices could have address ranges that would not be valid. i.e. VV.01.01, VV.01.02 These addresses would be invalid for anything but Virual Devices. The VV would indicate a virtual device.
Mark Sanctuary Posted August 10, 2007 Posted August 10, 2007 I think the ISY is event driven so virtual devices would just be another event in the loop. But would virtural devices be needed after the new timer system is completed?
C Martin Posted August 10, 2007 Posted August 10, 2007 Mark, I'm not sure... I remember having virtual X10 devices in Homeseer and using them. It might be the same as just using a timer or scheduled event. How about time delays between devices in the Scenes?
Michel Kohanim Posted August 10, 2007 Posted August 10, 2007 C Martin, Very interesting idea ... I think - I am not sure yet - our new trigger functionality would eliminate the need for virtual triggers (variables) especially for sequences and timed events. I will let you know if otherwise. Thanks so very much for the idea/feedback, With regards, Michel Mark,I'm not sure... I remember having virtual X10 devices in Homeseer and using them. It might be the same as just using a timer or scheduled event. How about time delays between devices in the Scenes?
Recommended Posts