ISY triggering program when status isnt true?

[RichTJ99]

Hi,

 

I have a pretty simple program that sends an email when the door is opened. For some reason, at random, the ISY triggers my basement program. The ISY says the status for the device is on. If you look at the ISY, the ISY says the device is off, but the program just keeps running for no apparent reason.

 

While I was away on vaction, I started getting emails that the basement door was opened. I turned on the lights, logged into the cameras & I know the door was not opened. I also can see the ISY says the door is closed yet the program just keeps running & sending the recurring emails.

 

I thought this was a triggerlinc issue & I swapped out a triggerlinc with a new one I bought. What could it be that is doing it with two different triggerlincs with the same program.

 

BTW, none of my other triggerlinc programs do this, just the basement.

 

Thanks,

Rich

If
       Control 'Door: Basement Door Open' is switched On
   And Control 'Door: Basement Door Open' is not switched Off

Then
       Repeat Every  2 minutes and 30 seconds
          Send Notification to All

Else
  - No Actions - (To add one, press 'Action')

[Michel Kohanim]

Hi Rich,

 

The first question I have is: do you really want ISY to send you en email every 2.5 minutes as long as the door is open?

 

Have you checked the event viewer to see if you actually get DOF when the door is closed? Please note that Control and Status are too different things. ISY status for a device is NOT equal to whether or not a control was issued. I think, in this case, you might want to use Status instead of control.

 

With kind regards,

Michel

[RichTJ99]

Michel,

 

I did change the program to status instead of control as you mentioned.

 

Right now, the status is closed if i look on the ISY yet the program is running.

 

I agree that 2.5 minutes is not the right time, but I cant figure why this keeps triggering.

 

It seems once it starts, it doesnt stop.

 

I know if I walk down & open & shut the door it will turn off.

 

Any ideas why the ISY status is closed but the program is still running?

 

Thanks,

Rich

 

 

If
       Status  'Door: Basement Door Open' is On
   And Status  'Door: Basement Door Open' is not Off

Then
       Repeat Every  2 minutes and 30 seconds
          Send Notification to All

Else
  - No Actions - (To add one, press 'Action')

[Michel Kohanim]

Hi Rich,

 

I am getting a little confused as well!

 

I do not think you would need the "is not off" condition at all. In short, the program continues to run till the status changes from on to something else. You would need the "is not off" if you used control since a control does not have a status. But, since you are using status, the condition is evaluated based on the status of the device.

 

With kind regards,

Michel

Michel,

 

I did change the program to status instead of control as you mentioned.

 

Right now, the status is closed if i look on the ISY yet the program is running.

 

I agree that 2.5 minutes is not the right time, but I cant figure why this keeps triggering.

 

It seems once it starts, it doesnt stop.

 

I know if I walk down & open & shut the door it will turn off.

 

Any ideas why the ISY status is closed but the program is still running?

 

Thanks,

Rich

 

 

If
       Status  'Door: Basement Door Open' is On
   And Status  'Door: Basement Door Open' is not Off

Then
       Repeat Every  2 minutes and 30 seconds
          Send Notification to All

Else
  - No Actions - (To add one, press 'Action')

[RichTJ99]

Michel,

 

I had changed the script to your recommendation:

 

If
       Status  'Door: Basement Door Open' is On

Then
       Repeat Every  2 minutes and 30 seconds
          Send Notification to All

Else
  - No Actions - (To add one, press 'Action')

 

This seems very basic in terms of what we are stating it should do. For some reason it seems to randomly trigger. I wouldnt care about one random message.

 

The issue I have is that the ISY says the status is off, yet the program is still running.

 

How is it possible if the ISY gets a "on" command but the ISY sees the status is off, then how should the program be running? Is there a way to make the ISY "refresh" its status?

 

It seems to me that the ISY says "I have been triggered" & because the status doesnt ever actually change, it doesnt think to go look to see if the status has changed.

 

Any ideas on what else I can do? I have swapped the device out & the old device in a different location is working fine with no accidental triggers.

 

The only common item for the basement program is I am using the same DS10A wire leads. I guess I can swap those out too but theres not really much to those things.

 

Thanks,

Rich

[Michel Kohanim]

Hi Rich,

 

This is quite strange. If ISY thinks the status is Off then the program should stop running.

 

Would you please kind enough to schedule a tech support call? This way, we can see what's going on and don't have to go back and forth on forum.

 

With kind regards,

Michel

[TJF1960]

Hello Rich,

 

Was this problem resolved, and if so what was found.

 

Thanks in advance,

 

Tim

[RichTJ99]

Unfortunately, no it is still doing it. Is actually happening right now.

 

Door: Basement Door Open is currently "off" however the script is running a "then".

 

Now one thing to keep in mind is that I have multiple triggerlincs in my house all running a copy of this script (though they are named slightly different), none of hte other triggerlincs have this issue.

 

I believe the false running has to do with a faulty magnetic reed switch which i borrowed from an X10 DS10a. If I swap out the triggerlincs I get similar behavior.

 

At some point when I am not so lazy I will swap out the switch & see how it goes.

 

THe only question I have is if the ISY sees that the door is "off" why is it running the program still. I can only guess that because the status doesnt change, the ISY isnt checking to see if the status is off, its just checking for a change.

 

Thanks for asking & any suggestions are welcome.

 

THanks,

Rich

[TJF1960]

Hi Rich,

 

One thing you could try is to just disconnect the wires to the triggerlinc and short the terminals (or leave them disconnected depending on whether the contact type is N.O. or N.C.) for a day to see if the status problems continue.

 

Also, have you checked the log to see if the triggerlinc shows up at around the time the first email is sent?

 

Tim