"A Schedule was met at" Keeps being sent

[bh56]

I have an ISY 994i/IR Pro.  Running v.4.8.0

I have a number of Open/Close Sensors 2843-222 v1.6.

I have a few programs that turn on at a specific time to monitor if my doors are opened/closed.

If

   From 11:00:00 PM

   To 7:00:00 AM (next day)

And Status 'Device Sensor' is On

Then

   Send notification

Else

 - No Actions

For these programs at the From time, I get the following message:

Front Entry - Close

A Schedule was met at 2020/09/09 11:03:00 PM.
----------------------------------------
     At: 2020/09/09 11:03:00 PM
Program: Front Entry - Close

Does anyone have any idea of what causes these to be generated?

 

[Michel Kohanim]

@bh56,

Whenever the status changes (from off to on) and it's within 11:00PM to 7:00AM (next day), you will get the notification.

With kind regards,
Michel

[MrBill]

@bh56 i suspect a different program than the one you posted generated that notification.  As @Michel Kohanim points out that program only sends when status changes off to on. 

 

Please check using the Find feature by right clicking 'My programs' to find all programs referencing that device.

[bh56]

Thanks @Michel Kohanim.  Michael, from 7-11(next day), i just arm the alert of any open or close event.  During these times, the doors have not been opened or closed.  When these events do occur, I get a different message, not the one I get at exactly the program is enabled. 

@MrBill, I was unable to use the Find function to find the device or program.  I've not used this before, but it does not seem to work.  Do I find the "Program" or Find the "Device"..  I tried changing the enable to be different for the Open and Close, as I was/am enabling them at the same time.  Maybe this was/is causing issues for the same device.  Will see tonight if this helps.

 

[kclenden]

17 hours ago, MrBill said:

As @Michel Kohanim points out that program only sends when status changes off to on. 

That's only 99.99% true. ? The program is triggered by three things:

• Time becomes 11:00PM
• Time becomes 7:00AM (next day)
• Sensor status changes from OFF to ON

When the program is triggered, the entire IF is evaluated.  So at 11:00PM if the sensor state is ON then the program will send even though the sensor status hasn't just changed from OFF to ON.  Other than that one instance, the program will only send if the status changes from OFF to ON.  Given that the OP's message indicates a time of 11:03:00PM, it's not likely that one exception is the cause of the message though.

8 hours ago, bh56 said:

Do I find the "Program" or Find the "Device"

There are only two ways your message was sent.  Either it was sent by the program you typed above, or it was sent by another program.  So I would use the "Raw Text" option and search for either "Send Notification", or if you use "Send Notification" in a lot of programs you could search for specifically named content (i.e. the "Name" shown in "Configuration->Emails/Notifications->Customizations").  Keep in mind that when you search using "Raw Text", capitalization matters.

Here are two screenshots of examples:

 

Edited September 11, 2020 by kclenden

[MrBill]

12 hours ago, bh56 said:

Thanks @Michel Kohanim.  Michael, from 7-11(next day), i just arm the alert of any open or close event.  During these times, the doors have not been opened or closed.  When these events do occur, I get a different message, not the one I get at exactly the program is enabled. 

@MrBill, I was unable to use the Find function to find the device or program.  I've not used this before, but it does not seem to work.  Do I find the "Program" or Find the "Device"..  I tried changing the enable to be different for the Open and Close, as I was/am enabling them at the same time.  Maybe this was/is causing issues for the same device.  Will see tonight if this helps.

 

I would use the Find function to find programs associated with the device in questions.

1) on the Programs tab right click whatever your top level folder is called and select "Find Replace"

2) in the popup window Device should already be selected, select your device in the second dropdown:

3) Click the Find button to be taken to the FIRST program using that device.  After reviewing that program, then click the FIND button again, to look for more programs that reference that device.  Continue to Press FIND after reviewing each program until you have cycled thru and are back the the FIRST program that Find found.

Alternatively you could search for something else, such as the specific notification.  Personally I'd use Device, but there may be multiple search terms you could utilize to find other programs.

I agree with @kclenden about the conditions that will trigger the program shown.  However your notification seems to indicate a program was triggered at 11:03 PM. 

I suppose it's also possible that you have other programs that enable/disable or other RUN a program that generates the notification which may mean it's most effective to use @kclenden's method of searching using Raw Text, but keep in mind your text must be exact, including case, i.e. "Send Notification" and "send notification" are not the same thing, you will need to use "Send Notification" exactly as it appears in programs.

[Michel Kohanim]

@kclenden,

THANK YOU THANK YOU!

With kind regards,
Michel

[bh56]

Yes, everyone.  @kclenden@MrBill @Michel Kohanim thank you so much for your help on this.

After some of your insight I'm thinking I'm using the Open/Close sensor close event incorrectly.  Maybe I should not be monitoring this event.
I'm thinking the "Schedule" trips, the open/close sensor is in a "closed" state, thus I get the close alert.  Maybe I should just be monitoring the "Open" event, as this is what I'm really looking for.  But was thinking at other times, I may want to know both about the "Open" and "Close".

I'll play around some more and do some more testing on this.

Thanks so much for all of your help with this.

[kclenden]

On 9/13/2020 at 11:54 AM, bh56 said:

I'm thinking the "Schedule" trips, the open/close sensor is in a "closed" state, thus I get the close alert.

Unless you mistyped the time of the alert, it seems like the alert came too late (2 minutes after "schedule" trips) for that to be the cause.

It sounds like your ultimate goal is to be alerted to an "event" that happens within a set time frame.  If that's the case, you probably want to monitor CONTROL instead of STATUS as changes in control are one-time events while status is an ongoing state.  So your program would look like:

If
   From 11:00:00 PM
   To 7:00:00 AM (next day)
And 'Device Sensor' is switched On
Then
   Send notification
Else
 - No Actions

Only one event can happen at a time, or at least that's how the ISY sees it, so now when the program is triggered by 11:00:00PM (an event) you can't also have a "switched On" event*.  That takes care of the one exception problem you had with "status".  Now the only event that can really trigger your notification will be "'Device Sensor' is switched On" and if that event doesn't fall within 11:00:00PM and 7:00:00am (next day) it won't send.

* While the above is true, you could still have a "switched On" event that just happens to be triggered at 11:00:00PM.  You still only have one event being triggered, but in this case it's the "switched On" and not 11:00:00PM.

Edited September 15, 2020 by kclenden