riceman Posted June 6, 2007 Posted June 6, 2007 I'm an Ocelot user and am desperately trying to find equivalent (or near-equivalent) functionality with an Insteon-based system. Ocelot provides great flexibility with regard to conditionals... Specifically, I need to be able to set up a trigger that only fires based on a time of day (e.g. if my motion sensor detects movement between 11PM and 6AM, then trigger some action--turn on lights, etc., but do nothing during other times of day) Another thing I do with the Ocelot is to set a variable based on an input from a motion sensor--if movement is detected during any given day, one lighting schedule executes, but if no motion is detected, a different (away from home) lighting schedule executes (based on checking the value of the variable I am setting... I know these are somewhat specific applications, but it seems like triggers based on time would have a broad application... Is there any plans to provide this kind of functionality? Thanks, Dave
Michel Kohanim Posted June 6, 2007 Posted June 6, 2007 I'm an Ocelot user and am desperately trying to find equivalent (or near-equivalent) functionality with an Insteon-based system. Ocelot provides great flexibility with regard to conditionals... Specifically, I need to be able to set up a trigger that only fires based on a time of day (e.g. if my motion sensor detects movement between 11PM and 6AM, then trigger some action--turn on lights, etc., but do nothing during other times of day) Another thing I do with the Ocelot is to set a variable based on an input from a motion sensor--if movement is detected during any given day, one lighting schedule executes, but if no motion is detected, a different (away from home) lighting schedule executes (based on checking the value of the variable I am setting... I know these are somewhat specific applications, but it seems like triggers based on time would have a broad application... Is there any plans to provide this kind of functionality? Thanks, Dave Dave, Most of what you are looking for will be in our releases 2.2 (06.20). At the moment, ISY has no notion of variables nor do we have any plans (yet) to support them. ISY triggers are based on the permissible states of devices and anything outside of that is not currently supported. For your second scenario, I don't see a need for variable since: a. If your motion detector is an Insteon Device b. It has states associated with it: i.e. motion detected or idle therefore, your trigger will be based on the state of the motion detector device and the time of day Do you have any other scenarios where the variables used cannot be categorized as device states? With regards
Recommended Posts
Archived
This topic is now archived and is closed to further replies.