LeeG

As soon as 'Closet Light' is set to 30% the Program is triggered again because of the Wait and change in Status 'Closet Light' is off. The If is now False so the Set Scene does not execute.

This links to the Wiki section on email variables http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Custom_Email_Substitution_Variables ${sys.node.11 22 AA 1.name} would use the name of the device node ${sys.node.11 22 AA 1.ST} would show device Status

Can you screen capture with the search argument entered but not yet clicked on Green search Icon.

Here is the first hit on "door sensors"

Try running File | Restore Modem (PLM) to rebuild PLM link database.

I just tried "door sensors" which found several hits including your post. Perhaps the Search is not set to Forums.

I found "head around" and "fuzzy math" just now. What is the search argument and what is being searched?

It is nodes and Scenes. Not nodes and Scenes and the number of nodes in Scenes.

I believe the number is devices and Scenes, not the the number of devices being used in Scenes.

Not sure how helpful this will be since it is a negative response. Installed 2 Hidden Door Sensors in April, no battery issues with supplied batteries. Are these in exterior doors where temp could be a factor?

Keep in mind that lack of new device support extends to KeypadLincs. If using KPLs and one fails the replacement KPLs cannot be used on a 99i.

The Heartbeat message On/Off state reflects the state of the Sensor when the Heartbeat message is sent. The Heartbeat message can be generated by tapping the Sensor Set button. Approx 15 seconds after sending test Sensor On/Off message from tapping Set button the Heartbeat message is sent. Works like the Leak Sensor does in this area. The Open Close Sensor has v.40 firmware and three nodes when added to ISY using 4.2.21 or 4.2.22

Hops Left=3 is new with the PLMs that have the firmware change to correct the All On scenario. More information to come on the total effects on Hops Left counts. The fact that the KPL LED did not turn On is odd unless it is set for non-toggle off mode.

The defective KPL can be physically removed and the new KPL installed. Add the new KPL to the ISY under a dummy name. Right click on old KPL primary node, select Replace 'old kpl name' with .... No Insteon commands will be sent to the old KPL address. When Replace is complete the Admin Console will be terminated. When the Admin Console is started the new KPL dummy name will no longer exist. The old defective KPL name will remain but now have Insteon address of new KPL. No changes to Programs or Scenes are required.

The Heartbeat node number is 4 ${sys.node.21 78 1F 4.name}: ${sys.node.21 78 1F 4.ST}

There are multiple problems. The following Program cannot change I/O Linc Sensor Status with a Set .... Off, at least from the actual I/O Linc perspective. If From 3:02:00AM To 3:04:30AM (same day) And Status 'Gate Loop-Sensor' is On Then Set 'Gate Loop-Sensor' Off Set 'Gate Loop-Relay' Off Send Notification to 'Aaron's iPhone Text' content 'Fence Wire Cut - Fix' Else - No Actions - (To add one, press 'Action') This Program cannot generate a True evaluation. The two time ranges do not overlap yet they are Anded together. The time ranges should be Or'ed, paren'ed then Anded with Sensor Status check. If ( From 12:00:00AM To 2:59:50AM (same day) Or From 3:05:00AM To 11:59:59PM (same day) ) And Status 'Gate Loop-Sensor' is On Then Send Notification to 'Aaron's iPhone Text' content 'Fence Wire Cut' Else - No Actions - (To add one, press 'Action')

See the KeypadLinc Owner's Manual page 17 Configuring for 6 or 8-Button Operation Changing to 6-Button Configuration 1) Replace the 8-button plate with the 6-button plate (see Changing to 6 or 8-Button Plate) 2) Gently pull the set button out as far is it will go 3) Wait 10 seconds 4) While simultaneously holding the On and Off buttons, carefully push the set button back in, flush with the trim frame 5) Continue holding the On and Off button until the keypad beeps Keypad is now in 6 button mode Changing to 8-Button Configuration 1) Replace the 6-button plate with the 8-button plate (see Changing to 6 or 8-Button Plate) 2) Gently pull the set button out as far is it will go 3) Wait 10 seconds 4) While simultaneously holding the On/Off (upper left-most) button and the H (bottom right-most) button, carefully push the set button back in, flush with the trim frame 5) Continue holding the On/Off (upper left-most) button and the H (bottom right-most) button until the keypad beeps Keypad is now in 8 button mode

The "Trigger Reverse" option applies to the I/O Linc Sensor only. Without Trigger Reverse being used, the I/O Linc Sensor is On when the switch (or wire in this case) is closed, Off when the switch or wire is open. The Trigger Reverse option reverses that. The Sensor is Off when the switch or wire is closed, On when the switch or wire is open. The problem with Trigger Reverse is that it does not reverse Query results. The 3AM Query will change the Sensor state because Query returns the True state of the Sensor, not the reversed state from Trigger Reverse. There is another problem with Query results. The I/O Linc will sometimes send multiple messages with the Query results. This causes the Relay state to be applied against the Sensor or the Sensor state applied against the Relay. In a garage door application using a switch that is Open when the door is closed solves the duplicate message issue because the Sensor and Relay are both Off at 3AM. Having the Event Trace running at LEVEL 3 during the 3 AM Query will identify which issue exists.

Anytime. Happy to help.

No. Requires two Ons. The If says "If Status ..... On" (device is On) And "If Control ....... is switched On" (device is turned On again) Combining the Anded conditions means the device is On from first On (Status On) and turned On again (If Control).

Both KPLs are being monitored by the two Programs in post 6. Neither Program in post 6 uses/needs anything in the Else clause. The first Program turns On Scene 3 (turns On both H buttons) when any of the 4 KPL buttons is turned On. The second Program turns Off both H buttons when all four KPL buttons are turned Off. Oops, i see the missing piece. If Control 'kpl1 H' is switched Off Or Control 'kpl2 H' is switched Off Then Set Scene 'Scene 1' Off Set Scene 'Scene 2' Off Else Assumption - Scene 3 is assigned to kpl1 H and kpl2 H For reference - setting Backlight level changes the button LED level for All buttons, not just button H Then Set 'Keypad 1 - H' On 15/Off 7 Set 'Keypad 2 - H' On 15/Off 7 Else Set 'Keypad 1 - H' On 0/Off 0 Set 'Keypad 2 - H' On 0/Off 0 The Adjust Scene changes the Responder On Level or Responder Ramp Rate of the Set device the next time the Scene is used. Does not turn On/Off the Set device. Then In Scene 'Scene 1' set 'InlineLink1' 0% In Scene 'Scene 2' set 'InlineLink2' 0%

That is what the two Programs in post 6 are doing, monitoring the Controller buttons.

It is normal for the ISY to write updates when changes are made. If something prevents all updates from being written (usually a comm issue) the update is queued and a Green Icon placed to the left of the node. Multiple nodes could have queued updates. When one device is told to update I think the ISY will try to finish anything queued. I have always used a Pro so not sure about this. There is no specific option to drive updates to All devices. Note that battery powered devices have to be updated one at a time. There is a new capability in 4.2.21 to update Motion Sensors under Program control which may work on other battery devices but this has to be determined.

If Control and if status have their own set of rules. If Control triggers the Program when the inbound command matches what is being looked for, On in this case. If Control does not trigger a Program when the device/button is turned On by something other than the device paddle/button being pressed On. If Status triggers a Program when the Current State changes to match the condition being checked for. If Status does not trigger a Program when Current State does not change states. Turning a device/button On twice in a row triggers the Program once when Current State changes to On. The Program(s) that are checking Responder Status of InlineLincs should be deleted. No need to monitor a Responder.

If Control and If Status are both triggers. Both can trigger a Program to Run If Control is looking at the commands flowing from the device. If Status is looking at Current State of the device.