bmercier Posted November 28, 2011 Share Posted November 28, 2011 Hi, I believe I found a bug in the triggering of programs using an Elk zone input. When I test a zone for "Violated", the program gets triggered when the zone changes from "Violated" to "Normal", as opposed to "Normal" to "Violated". Example: If Elk Zone 'Entree' is Violated Then .... The following program will run the "Then" only when the door gets closed (returning to Normal, or Closed). When I look at the Elk tab, the zone gets violated when the door is opened, as it should be. I'm using 3.1.13. Thanks, Benoit. Link to comment Share on other sites More sharing options...
Chris Jahn Posted November 28, 2011 Share Posted November 28, 2011 Hi Benoit, If the status of that zone changes at all then then program will run either the then or else path depending on whether the if condition evaluates to true or false. For example, when the zone goes to Violated, it will run the Then path, when it goes back to Normal (or any status other than Violated), it will run the else path. Link to comment Share on other sites More sharing options...
bmercier Posted November 28, 2011 Author Share Posted November 28, 2011 Hi Chris, I apologize, You are absolutely right. It works perfectly. I should have done more testing. I had other conditions that messed it up. Thanks, Benoit. Link to comment Share on other sites More sharing options...
Chris Jahn Posted November 28, 2011 Share Posted November 28, 2011 Hi Benoit, No problem at all, we welcome all feedback and questions. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.