Xathros

Your welcome. More sensors will require more variables. You might consider renaming the ones we have used already to reflect the sensor to which they belong and name additional ones according to their sensor as well. May I suggest: s.Secure_RoomTemp i.Secure_RoomAlertTmp i.Secure_RoomDelta i.SecureRoomSuspend You can rename the existing variables on the variables page and they will be updated throughout your programs automagically. I would also recommend creating folders for each sensor's set of programs to keep things organized and give you an easy way to enable/disable the programs for individual sensors. -Xathros

@Teken Modify NotificationSuspend as follows: If Then Wait 20 minutes $i.NotificationSuspend = 0 Run Program SecureRoomMonitor (IfPath) Else If the room temp is steady, the monitor program will not automatically retrigger even when above the threshold since it requires a change in temp value to trigger. The change above will force the notification to resend as long as the temp remains above the threshold. -Xathros

Correct. I have to do this with my CAI based temp probes as well. Everything is 10X actual. -Xathros

First, the program won't trigger until the temp value changes. Bump the value up one and see if it triggers. In my original posting my program said: $i.AlertDelta = $Secure_room - $i.AlertSentAt. This is not valid code in the ISY but is the intended goal. Doing this the ISY way: $i.AlertDelta is $Secure_Room sets AlertDelta to the current Secure_Room temp value. $i.AlertDelta -= $i.AlertSentAt subtracts i.AlertSentAt from i.AlertDelta leaving i.AlertDelta with the actual difference between the current Room temp and the temp when the last alert was sent. -Xathros

-Xathros

Yes Sir it was. I have just edited the whole thing to make it functional and syntactically correct. Note: I changed s.AlertSentAt to and integer i.AlertSentAt, Added a line to SecureRoomMonitor to set i.AlertSentAt and corrected the calculation section in the Else of SecureRoomMonitor Sorry for all the errors. Was rushing out the door when I posted that yesterday. -Xathros

Sorry. Use "is". I typed out those programs yesterday and I often make the mistake of substituting "=" for "is". -Xathros

Something like this should do it: Create an integer variable: i.NotificationSuspend and set it's value to 0 Create another integer variable: i.AlertSentAt and set it's value to 0 Create another integer variable: i.AlertDelta and set it's value to 0 Program: SecureRoomMonitor (Modify your program to something like this:) If $Secure_Room > 220 and $i.NotificationSuspend = 0 Then Send Notification $i.NotificationSuspend = 1 $i.AlertSentAt = $Secure_Room Run Program NotificationSuspend (ThenPath) Else $i.AlertDelta = $Secure_Room $i.AlertDelta -= $i.AlertSentAt Run Program OverrideSuspend (IfPath) Program: Notification Suspend If Then Wait 20 minutes $i.NotificationSuspend = 0 Else Modify the wait to meet your needs. And another program to monitor the rate change during the Suspend Period: Program: OverrideSuspend if $i.AlertDelta >= 50 Then $i.NotificatiopnSuspend = 0 Run Program SecureRoomMonitor (IfPath) Else In this configuration, if the temp increases another 5 deg during the 20 minute notification suspend time, the suspend is overridden, an alert sent and the alert suspend restarted. This will happen everytime the temp increases 5deg above the temp at the previous alert. Otherwise, the alert will continue once every 20 mins until the temp drops below 22C. Adjust as necessary. Hope this helps. -Xathros EDITED to correct program logic and Syntax

When customizing the notification, Select Variables, then the variable name from the list. It will insert the above substitution variable in the notification. Alternatively, you could just type it in since we know the type and ID: 2 and 11 hence ${var.2.11} -Xathros

Easy: ${var.2.11} -Xathros

Now I see it! Its the Variable ID. As in: /rest/vars/set/<var-type>/<var-id>/<value> Sets a variable given by var-id var-type: 1 – Integer 2 – State So in this case, the alert was caused by a change in value of variable 2.11 <state.11> I modified my program to be driven by a state variable and tested by changing the variable value. Now I get "Value: 2.1" My State variable is ID#1 so that correlates to your perfectly. -Xathros

I recreated your custom notification on my test system and ran a test. The value I get in place of your "Value: 2.11" is the name of my device tree "Network: XathTest". In my test case, the program was sending an X10 command. It looks like {Alert.Details} is related to the most recent event to occur within the system. There are very few places in the ISY that support floating point values. Energy and Climate modules come to mind. You might look at the data available from those and see if you can spot a 2.11 somewhere. -Xathros

Sorry. I have no clue what the 2.11 means in this case. -Xathros

What does your custom notification definition look like? -Xathros

I pulled my system out when I moved and rebuilt/expanded at my new place. Ended up with a much more functional system the second time around. Could have fixed the first one by starting over but never felt it was worth doing until the move forced the issue. -Xathros

Glad I could be of assistance. -Xathros

Anytime! Always happy to help. -Xathros

Because the change in status of the light coming on when triggered would have canceled the timer if done in a single program. This method also takes care of a possible issue when the light is triggered On less thaan 2 minutes before Sunrise+30. -Xathros

What are you trying to accomplish? As far as I can tell, /rest/query/<node-id> does query the node just like the admin console. You can follow that with a /rest/status/<node-id> after a brief delay to get the result of the query. -Xathros

28 links is still a very small number. How many devices do you have? Any multinode devices like KPL's? Do the show plm links/count again as any insteon traffic arriving during the show will throw off the pointer and result in fewer or more than actual number of links. -Xathros

Then I would recommend restoring a recent backup and trying the restore PLM again per LeeG's suggestion. Try to make sure there is no Insteon traffic during the restore. -Xathros

Select Tools / Diagnostics / Show ISY Links Tabls. That should give you a popup list of devices to select. Pick a device. Are any links shown? Do you have a recent ISY backup? -Xathros

Gotcha! -Xathros

Doesn't the Elk have an internal battery backup? -Xathros

It is also my preference to have the PLM located at the panel along with my phase bridging access points. -Xathros