Reduction In Number Of Programs?

[smokegrub]

I have 4 hidden door sensors and 1 triggerlinc to monitor our doors. 

Each device has these 2 programs:

If open, notify with custom message identifying the door

If low battery, notify with custom message identifying the door

This a total of 10 programs.

Is there a way to program this setup to reduce the number of programs. I am assuming there might be a way with variables, but I have never used this asset and don’t know where to begin.

 

I have the same situation with 9 leak sensors so this is an area ripe for improvement, if possible.

[elvisimprsntr]

Do you need to know every time a door is opened? If these are frequently used doors, all the notifications would drive me nuts.

 

Also consider your actions based on low battery. For example, I wait for my first smoke to start chirping, then replace the 9v batteries in all the smokes, since I know the others will chirp soon.

[oberkc]

Nothing is jumping out at me as far as ideas to reduce number of programs. My only thoughts are to put all these into a program folder for organizational purposes only.

[smokegrub]

Do you need to know every time a door is opened? If these are frequently used doors, all the notifications would drive me nuts.

 

Also consider your actions based on low battery. For example, I wait for my first smoke to start chirping, then replace the 9v batteries in all the smokes, since I know the others will chirp soon.

Reporting is controlled by a program that is enabled 5 minutes after a KPL button is pressed allowing us to leave the house w/o triggering a notification. We use MobiLinc to turn off reporting remotely if need be. Thus we only get notifications when we want them.

[smokegrub]

Nothing is jumping out at me as far as ideas to reduce number of programs. My only thoughts are to put all these into a program folder for organizational purposes only.

I have done that.

 

Thanks.

[andyf0]

You can combine all your door sensors into a program using 'OR' for each sensor to trigger the program. If any of them open send a custom message using a substitution variable ${sys.node.#.name} to identify which device caused the trigger. You can do the same for a low battery message.

 

So 2 programs.

[oberkc]

Substitution variables. Not something I have ever used or needed, but I may try one out. I understand the "#" represents the address of the device that causes a program to run, correct?

 

Thanks for the tip!

[LeeG]

Yes, that is the function of #

 

Here is the Wiki link to email variables

 

http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables

[smokegrub]

Spot on, Andy.

[smokegrub]

Andy, I am obviously doing something wrong. Would you be so kind as to draft example programs to handle two devices: House (37.D9.45 and Garage (38.D10.46)?

You can combine all your door sensors into a program using 'OR' for each sensor to trigger the program. If any of them open send a custom message using a substitution variable ${sys.node.#.name} to identify which device caused the trigger. You can do the same for a low battery message.

 

So 2 programs.