LeeG

" I have done it in the same place I always" I am noting that the update that is failing is to change the PLM address in the RemoteLinc so the PLM is different from when the RemoteLinc was last successfully updated.

Since the PLM address is being changed things are not exactly the same. Was the old PLM a 2412? Being near another Dual Band device can also be an issue. Add some distance between RemoteLinc and Dual Band device.

Try another set of batteries.

That is a RemoteLinc that is either too close to a Dual Band device (odd but true for a RemoteLinc) or it is not in linking mode. The first command issued gets no response from device. The command is tried three times (each fails to get a response) so the update remains queued. It looks like the PLM has been replaced as the "to" device address is being changed.

If that is a RemoteLinc (not RemoteLinc2) it may need some additional distance from Dual Band Device. There is no error if the updates do not complete, just the 1011 Icon. An Event Trace at LEVEL 3 will show what is happening. Be sure the RemoteLinc is in linking mode before starting next update.

The PLM is the Controller of the Scene when the Scene is used in a Program.

Battery powered devices can be added to ISY one way. Put one device into manual linking mode with Set button. Use New INSTEON Device, entering Insteon address and Name of choice. use default Auto Discover and Remove existing links. If that does not work then likely comm issue (be sure Insteon address is correct). Battery device could be out of range of Dual Band device. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Perform steps above to add device. Post the event trace. What ISY Firmware and UI is being used ( Help | About)? What type PLM and how old?

Motion Sensor and RemoteLinc2 are battery devices that sleep. Necessary to put "one" battery device into manual linking mode, add that device to ISY. When addition is complete take device out of linking mode before putting next battery into linking mode.

barrygordon Thanks for that information. As Xathros (thanks) just noted I was asking for information on something Insteon can do that the ISY does not support. What you describe is how Insteon works (not able to globally change responder on levels across the Scene), not something the ISY does not support. Not trying to start a discussion, I was pretty certain the ISY was not a limiting factor. This requires a discussion with the Insteon manufacturer (SmartLabs/Smarthome) to see if they are willing/able to add that capability. They may be limited by the SD command structures associated with Scene On.

barrygordon "The fact that scenes cannot be dimmed is an ISY design issue." Can you expand on that. What Insteon function at the Scene level does the ISY not support.

MWareman "Question. If you dim from 100% to 90% with a ramp rate of 3 minutes, will it take 3 mins to get to 90%?" No. The Ramp Rate is from Full Off to Full On. From the User Guide..... Definition: Ramp rate is the time it takes OutletLinc Dimmer to go from Full-off to Full-on (& vice versa) That is consistent across the Insteon dimmers. EDIT: the ramp time from 100% to 90% would be 10% of 3 minute Ramp Rate. 180 x .10 = 18 seconds to go from 100% to 90%

CSharron I found one of the 2472D devices would not turn On or Off. It would respond to Fast On and Fast Off which sounds like it was simply using a very slow ramp rate but that was not the case. I finally double tapped the Set button and the OutletLinc responded as it should. Try a Set button double tap on the OutletLinc that appears not to be working at all. Now the OutletLinc takes a full 8 minutes to go from Full Off to Full On.with a Scene On. EDIT: right click on OutletLinc (not Scene) and select Query. It will show the OutletLinc Current State value moving up or down at the 8 minute ramp rate when OutletLinc is reacting to Scene On or Scene Off command.

What does the OutletLinc actually do?

Once a Program is triggered and a clause selected the clause will execute from beginning to end without interruption, unless there is a Wait or Repeat in the executing clause. The example will double count in the Else clause when moving from On to Off Status when the Off paddle is tapped. That is why use of the Else clause is not a good idea in this case except for some general Action that is not bothered by entering the Else clause multiple times. So this could be dangerous If Control '33.95.41.1' is switched Off And Status '33.95.41.1' is Off Then variable -=1 more lines Else variable += 1 more lines

CSharron Being invoked from a Program, the Set Scene 'SceneOutletLinc' On will have the PLM as Controller. Need to set the OutletLinc Responder Ramp rate at bottom right side when the Scene name is selected.

larryllix See post #4. The Program is triggered when the Off paddle is tapped (by If Control). The Program is triggered again when Status changes (by If Status). Certainly should ISY change how Programs are triggered it could break existing Programs. I think the idea of ISY changing any existing functional characteristic of most anything would break something.

The RF devices do send 2 Group Broadcast On messages. The second message is ignored by ISY. Wed 11/18/2015 03:32:53 PM : Setting Time From NTP Wed 11/18/2015 03:32:58 PM : [iNST-SRX ] 02 50 14.C1.C7 00.00.01 CB 11 01 LTONRR (01) - first Group Broadcast message Wed 11/18/2015 03:32:58 PM : [std-Group ] 14.C1.C7-->Group=1, Max Hops=3, Hops Left=2 Wed 11/18/2015 03:32:58 PM : [D2D EVENT ] Event [14 C1 C7 1] [DON] [1] uom=0 prec=-1 Wed 11/18/2015 03:32:58 PM : [ 14 C1 C7 1] DON 1 Wed 11/18/2015 03:32:58 PM : [D2D-CMP 0075] CTL [14 C1 C7 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 11/18/2015 03:32:58 PM : [D2D EVENT ] Event [14 C1 C7 1] [sT] [255] uom=0 prec=-1 Wed 11/18/2015 03:32:58 PM : [ 14 C1 C7 1] ST 255 Wed 11/18/2015 03:32:58 PM : [iNST-SRX ] 02 50 14.C1.C7 00.00.01 CB 11 01 LTONRR (01) - second Group Broadcast message - ignored Wed 11/18/2015 03:32:58 PM : [std-Group ] 14.C1.C7-->Group=1, Max Hops=3, Hops Left=2 Wed 11/18/2015 03:32:58 PM : [INST-DUP ] Previous message ignored.

Xathros Try using New INSTEON Device. I used that with most of my devices including FanLincs where Set button access is not necessary.

rleidy Hope that was helpful. .The Event Trace is usually good at showing actual activity. Please post back if additional questions.

SwitchLincControlStatus - [iD 0088][Parent 0001] If Control '33.95.41.1' is switched Off And Status '33.95.41.1' is Off Then Set 'SwitchLinc Relay' On Else Set 'SwitchLinc Relay' Off First press of Off paddle. If is false so Else runs. (If Control is True but Status is On so IF Status False) "If that is accurate, then what happens when the lagging status is finally updated from ON to OFF. Does that trigger the program a second time? If not, why not?" The eventual change of Status to Off does trigger Program again. If is still False so Else runs again.. Wed 11/18/2015 09:33:14 AM : [iNST-SRX ] 02 50 33.95.41 00.00.01 CB 13 00 LTOFFRR(00) Wed 11/18/2015 09:33:14 AM : [std-Group ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2 Wed 11/18/2015 09:33:14 AM : [D2D EVENT ] Event [33 95 41 1] [DOF] [0] uom=0 prec=-1 Wed 11/18/2015 09:33:14 AM : [ 33 95 41 1] DOF 0 Wed 11/18/2015 09:33:14 AM : [D2D-CMP 009A] CTL [33 95 41 1] DOF op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Wed 11/18/2015 09:33:14 AM : [D2D-CMP 0094] CTL [33 95 41 1] DOF op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Wed 11/18/2015 09:33:14 AM : [D2D-CMP 0088] CTL [33 95 41 1] DOF op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 11/18/2015 09:33:14 AM : [iNST-SRX ] 02 50 33.95.41 22.80.0B 40 13 01 LTOFFRR(01) Wed 11/18/2015 09:33:14 AM : [std-Cleanup ] 33.95.41-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Wed 11/18/2015 09:33:14 AM : [iNST-DUP ] Previous message ignored. Wed 11/18/2015 09:33:14 AM : [iNST-SRX ] 02 50 33.95.41 13.01.01 CB 06 00 (00) Wed 11/18/2015 09:33:14 AM : [std-Group ] 33.95.41-->13.01.01, Max Hops=3, Hops Left=2 Wed 11/18/2015 09:33:14 AM : [iNST-INFO ] Previous message ignored. Wed 11/18/2015 09:33:15 AM : [iNST-TX-I1 ] 02 62 16 90 AB 0F 13 00 Wed 11/18/2015 09:33:15 AM : [D2D EVENT ] Event [33 95 41 1] [sT] [0] uom=0 prec=-1 Wed 11/18/2015 09:33:15 AM : [ 33 95 41 1] ST 0 Wed 11/18/2015 09:33:15 AM : [iNST-ACK ] 02 62 16.90.AB 0F 13 00 06 LTOFFRR(00) Wed 11/18/2015 09:33:15 AM : [D2D-CMP 0088] STS [33 95 41 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 11/18/2015 09:33:15 AM : [iNST-SRX ] 02 50 16.90.AB 22.80.0B 2B 13 00 LTOFFRR(00) Wed 11/18/2015 09:33:15 AM : [std-Direct Ack] 16.90.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 11/18/2015 09:33:15 AM : [iNST-TX-I1 ] 02 62 16 90 AB 0F 13 00 Wed 11/18/2015 09:33:15 AM : [iNST-ACK ] 02 62 16.90.AB 0F 13 00 06 LTOFFRR(00) Wed 11/18/2015 09:33:16 AM : [iNST-SRX ] 02 50 16.90.AB 22.80.0B 2B 13 00 LTOFFRR(00) Wed 11/18/2015 09:33:16 AM : [std-Direct Ack] 16.90.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Second press of Off paddle. If is True so Then runs. Wed 11/18/2015 09:36:13 AM : [iNST-SRX ] 02 50 33.95.41 00.00.01 CB 13 00 LTOFFRR(00) Wed 11/18/2015 09:36:13 AM : [std-Group ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2 Wed 11/18/2015 09:36:14 AM : [D2D EVENT ] Event [33 95 41 1] [DOF] [0] uom=0 prec=-1 Wed 11/18/2015 09:36:14 AM : [ 33 95 41 1] DOF 0 Wed 11/18/2015 09:36:14 AM : [D2D-CMP 009A] CTL [33 95 41 1] DOF op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Wed 11/18/2015 09:36:14 AM : [D2D-CMP 0094] CTL [33 95 41 1] DOF op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Wed 11/18/2015 09:36:14 AM : [D2D-CMP 0088] CTL [33 95 41 1] DOF op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 11/18/2015 09:36:14 AM : [iNST-SRX ] 02 50 33.95.41 13.01.01 CB 06 00 (00) Wed 11/18/2015 09:36:14 AM : [std-Group ] 33.95.41-->13.01.01, Max Hops=3, Hops Left=2 Wed 11/18/2015 09:36:14 AM : [iNST-INFO ] Previous message ignored. Wed 11/18/2015 09:36:14 AM : [iNST-TX-I1 ] 02 62 16 90 AB 0F 11 FF Wed 11/18/2015 09:36:14 AM : [iNST-ACK ] 02 62 16.90.AB 0F 11 FF 06 LTONRR (FF) Wed 11/18/2015 09:36:15 AM : [iNST-SRX ] 02 50 16.90.AB 22.80.0B 2B 11 FF LTONRR (FF) Wed 11/18/2015 09:36:15 AM : [std-Direct Ack] 16.90.AB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 11/18/2015 09:36:15 AM : [D2D EVENT ] Event [16 90 AB 1] [sT] [255] uom=0 prec=-1 Wed 11/18/2015 09:36:15 AM : [ 16 90 AB 1] ST 255 Wed 11/18/2015 09:36:15 AM : [D2D-CMP 0066] STS [16 90 AB 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Wed 11/18/2015 09:36:15 AM : [D2D-CMP 0065] STS [16 90 AB 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Wed 11/18/2015 09:36:15 AM : [D2D-CMP 002C] STS [16 90 AB 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true

When you post the Program are there other Programs that are triggered at the same time, something that would not happen when manually driving the Then.

Suggest posting your Program. Here is an example Motion - [iD 0045][Parent 0001] If Control 'MotionSensor2-Sensor' is switched On And From 10:00:00AM To 11:00:00AM (same day) Then Set 'SwitchLinc Relay' On Wait 20 minutes Set 'SwitchLinc Relay' Off Else Set 'SwitchLinc Relay' Off

NightOps The Trigger Reverse option reverses the Sensor On/Off status messages when the Sensor changes state (something you are already aware of). What many are not familiar with is the Query message state is NOT reversed by Trigger Reverse. The 3 AM Query done by the ISY each morning causes the I/O Linc Sensor state in the ISY to change to the actual state of the Sensor. Probably does not bother KPL button state if Sensor is linked as Controller to KPL button. However, any ISY Program that uses Sensor state will see the Sensor change state in the ISY (from Query result) around 3 AM even though Sensor did not physically changed state. The best solution (as already posted) is to use a new magnetic switch that does not require the use of Trigger Reverse. That eliminates the 3 AM Query driven change of Sensor state.

I suspect most who understand Insteon and link tables debug from the display popup and post the displayed image.

The "Show Device Links Table" and "Show ISY Links Table" have a Save button on the displayed link table. The Save function writes XML file.