LeeG

Both Programs will execute. However, the order in which they run is not controllable. If the order of execution is important have Program X invoke Program Y rather than both being triggered by Motion Sensor Multiple Programs can be triggered by any Sensor or Switch using "If Control" The If condition is not lost because a Program has been triggered.

ctviggen Keep in mind that this time the PLM is "not new" because the ISY is already aware of new PLM Insteon address. It may be necessary to run File | Restore Devices after the PLM replacement process. Also remember that battery powered devices will have to be updated, one device at a time with the individual Device Restore.

n4bos The problem is result of the Program taking longer than 1 minute per iteration the way it is coded.. The If counts to 60. The Then takes 1 minute + (Wait 1 minute + time to run the remainder of Then). The amount of time taken can be more accurate if the Wait is for a longer time, say Wait 1 hour but this depends on what you are trying to accomplish with timer.

Where are you using a button number? In the various Program clauses or a Scene the KPL button name is used.

I pressed the button. I've tried 3.3.10 on a 99i. It does not show button number on the normal UI display of any of the buttons.

I don't remember that. I suspect you are thinking about some other product.

The Event Trace shows button number. Thu 06/02/2016 12:24:01 PM : [iNST-SRX ] 02 50 1B.57.F8 00.00.06 CB 13 00 LTOFFRR(00) Thu 06/02/2016 12:24:01 PM : [std-Group ] 1B.57.F8-->Group=6, Max Hops=3, Hops Left=2 Thu 06/02/2016 12:24:01 PM : [D2D EVENT ] Event [1B 57 F8 6] [DOF] [0] uom=0 prec=-1 Thu 06/02/2016 12:24:01 PM : [ 1B 57 F8 6] DOF 0 Thu 06/02/2016 12:24:01 PM : [D2D EVENT ] Event [1B 57 F8 6] [sT] [0] uom=0 prec=-1 Thu 06/02/2016 12:24:01 PM : [ 1B 57 F8 6] ST 0 Thu 06/02/2016 12:24:01 PM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 41 13 06 LTOFFRR(06) Thu 06/02/2016 12:24:01 PM : [std-Cleanup ] 1B.57.F8-->ISY/PLM Group=6, Max Hops=1, Hops Left=0 Thu 06/02/2016 12:24:01 PM : [iNST-DUP ] Previous message ignored.

Krusty66 The Adjust Scene function is changing the Responder On Level for Light1 and Light2. This value resides in the Responder (Light1 and Light2) so no Controller changes are made. If the ISY is trying to change the Mini Remote that is the result of some other pending update unrelated to the Adjust Scene function. EDIT: example of an Adjust Scene statement. Only the Responder is changed. Tue 05/31/2016 03:31:47 PM : [ Time] 15:31:57 4(0) Tue 05/31/2016 03:31:47 PM : [13 8 1B 1 ] Link 2 : 0FE8 [A29222800BFF1F01] Saving [..........FF....] Tue 05/31/2016 03:31:48 PM : [All ] Writing 1 bytes to devices Tue 05/31/2016 03:31:48 PM : [13 8 1B 1 ] Link 2 : 0FE8 [A29222800BFF1F01] Writing [..........FF....] Tue 05/31/2016 03:31:48 PM : [iNST-TX-I1 ] 02 62 13 08 1B 0F 28 0F Tue 05/31/2016 03:31:48 PM : [iNST-ACK ] 02 62 13.08.1B 0F 28 0F 06 SET-MSB(0F) Tue 05/31/2016 03:31:48 PM : [iNST-SRX ] 02 50 13.08.1B 22.80.0B 2B 28 0F SET-MSB(0F) Tue 05/31/2016 03:31:48 PM : [std-Direct Ack] 13.08.1B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 05/31/2016 03:31:48 PM : [iNST-TX-I1 ] 02 62 13 08 1B 0F 2B ED Tue 05/31/2016 03:31:48 PM : [iNST-ACK ] 02 62 13.08.1B 0F 2B ED 06 PEEK (ED) Tue 05/31/2016 03:31:49 PM : [iNST-SRX ] 02 50 13.08.1B 22.80.0B 2B 2B 00 PEEK (00) Tue 05/31/2016 03:31:49 PM : [std-Direct Ack] 13.08.1B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 05/31/2016 03:31:49 PM : [iNST-TX-I1 ] 02 62 13 08 1B 0F 29 FF Tue 05/31/2016 03:31:49 PM : [iNST-ACK ] 02 62 13.08.1B 0F 29 FF 06 POKE (FF) Tue 05/31/2016 03:31:49 PM : [iNST-SRX ] 02 50 13.08.1B 22.80.0B 2B 29 FF POKE (FF) Tue 05/31/2016 03:31:49 PM : [std-Direct Ack] 13.08.1B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

"Questions - There seems to be three options Non-Toggle On, Non Toggle Off, Toggle. What is the difference between the three? I assume toggle means pressing a button changes the state of the button from on to off or off to on." Yes "Does Non Toggle On mean it sends an on command every time you press the button and the non toggle off sends the off command every time you press the button? " Yes "When this button is set as a controller in a scene does any action trigger the scene?" Yes "So if I am in Toggle mode and I go from on to off or off to on, does that trigger the scene?" Yes "If I am in Non Toggle Off mode and I press the button and it sends an off signal, does that also trigger the scene?" Yes "How are the LED Backlights controlled?" Add the KPL button as a responder in a Scene. Turn Scene On/Off to turn KPL backight On/Off "It seems that in toggle mode, when going from off to on, the backlight turns on. When going from on to off, the backlight goes off. Correct? " Yes "I assumed adding a button as a responder in a scene is what allows me to control the key backlight."" Yes "Maybe this is only in Non Toggle Mode." Turning backlight ON/Off has nothing to do toggle/non-toggle mode "Mutually Exclusive - " Never use this function. Everything should be done with Scenes.

Device 3D.AC.3D has a link record with the Scene number. Look at the link records in 3D.AC.3D as it responded to the Scene Off even though not in the Scene definition that the ISY is aware of. Mon 05/30/2016 10:59:20 AM : [GRP-RX ] 02 61 1E 13 00 06 Mon 05/30/2016 10:59:20 AM : [iNST-SRX ] 02 50 3D.AC.3D 3D.C7.22 65 13 1E LTOFFRR(1E) Mon 05/30/2016 10:59:20 AM : [std-Cleanup Ack] 3D.AC.3D-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Mon 05/30/2016 10:59:20 AM : [iNST-SRX ] 02 50 0F.50.98 3D.C7.22 61 13 1E LTOFFRR(1E) Mon 05/30/2016 10:59:20 AM : [std-Cleanup Ack] 0F.50.98-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Mon 05/30/2016 10:59:21 AM : [CLEAN-UP-RPT] 02 58 06 Mon 05/30/2016 10:59:21 AM : [iNST-SRX ] 02 50 3B.91.A9 3D.C7.22 61 13 1E LTOFFRR(1E) Mon 05/30/2016 10:59:21 AM : [std-Cleanup Ack] 3B.91.A9-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 <html><font color="red">----- Downstairs - Entry - Vent-30 Test Results -----</font></html> <html><font color="red">[succeeded]</font> Downstairs - Vent - E -30min (F 50 98 5)</html> <html><font color="red">[succeeded]</font> Downstairs - Entry - Vent (3B 91 A9 6)</html> <html><font color="red">----- Downstairs - Entry - Vent-30 Test Results -----</font></html>

Make sure Save Changes was done. Is the UI (Admin Console) also at 4.5.0? Post Program.

There is no adjustment for Heartbeat frequency. Simple enough to find out how often Heartbeat occurs. Write a simple Program that sends a message for each Heartbeat. AAA1 - [iD 0042][Parent 0001][Not Enabled] If Control 'OpenClose3-Opened / OpenClose3-Heartbeat' is switched On Or Control 'OpenClose3-Opened / OpenClose3-Heartbeat' is switched Off Then send text/email/etc Else - No Actions - (To add one, press 'Action') It is very unlikely Heartbeat is the issue.

What type battery is being used?

That is an interesting configuration. I have 6-7 Insteon devices in a detached garage that is more than 300' of cable from main house (I buried that cable) plus the interior wiring inside garage. I have no problem controlling those devices from the house and none are Dual Band. The devices were installed before there was Dual Band beyond the old SignaLincs. I have no experience going through a meter but I suspect having Dual Band devices on both 120v legs and on both sides of the meter would help with comm reliability. I have many Dual Band devices driven by my test ISY. Perhaps there other Insteon folks that have multiple meters who can pass on their experience.

The fact that Insteon devices exist that are not known to the PLM likely means the Insteon messages are coming from one or more of those devices not defined to the ISY. The Insteon address(es) are not in the PLM link list but the PLM sees the messages and searches the link table for a match. Not shown because the Insteon address is not known to the PLM but it breaks the GET-NEXT process. Suggest you leave things alone unless you can stop all Insteon activity. I publish my Insteon addresses all the time. Not hard to discover what they are if someone really wants to know.

Is the PLM link record count always 40? How many Insteon devices are installed and what types.

That is not the number of links required by the PLM. The Show ISY Links reflects what is written in the device, not the PLM. Here is a link displayed by Show ISY Links Table for an ICON switch. 1 : 0FF0 : E2 01 22.80.0B FF 1F 01 It is a Controller link pointing to the PLM. The link record required in the PLM was created when the device was added to the ISY. Nothing new is required in the PLM. Here are the Show ISY Links for an I2CS Motion Sensor that is in a Scene, No PLM link records are required for this device beyond what was created when Motion Sensor added to ISY, even though it is a Controller in an ISY Scene. 0 : 0FF8 : E2 01 22.80.0B 01 00 01 1 : 0FF0 : E2 02 22.80.0B 01 00 02 2 : 0FE8 : E2 03 22.80.0B 01 00 03 3 : 0FE0 : E2 01 13.08.1B 01 00 01 4 : 0FD8 : E2 01 14.41.95 01 00 01 5 : 0FD0 : 00 00 00.00.00 00 00 00 I think your concern over the 17xx count is not an issue. The Show ISY Links do indicated links are required in other devices but not the PLM. Of course there are ISY Scenes that add to the PLM count but Show ISY Links does itself not mean much.

Don't know what "ISY links" means. The PLM links start with all the devices defined to the ISY. An 8 button KPL has 9 link records, for example. One link for each button so a button press is sent to the PLM/ISY plus one additional needed for I2CS and other things. Then come the link records required for the Scenes you define. The number depends, of course, on the number of devices. Are the devices Controller only, Responder only, or both.

The 2413S holds 992 link records. The initial 256 decimal bytes are control information. I can see the unexpected Insteon traffic in the Event Viewer (running 4.4.6). I triggered a motion sensor and lost more than 50 PLM link records displayed. The same Insteon traffic can produce false high counts. If the PLM link record that matches the Insteon traffic has already been displayed by Show, all the link records past the motion sensor link will be displayed again. I've seen folks report 1500 PLM link records displayed even though that is physically impossible for a 2413S. The Show PLM Links Table uses "Thu 05/26/2016 05:59:55 PM : [GET-NEXT-LNK-RSP] 02 6A 06". Normally the last record accessed is from the Show. However, Get-Next-LNK reads the next record, even if the last PLM link record accessed was due to an inbound Insteon traffic. So, either the PLM link record count will be too low or too high if inbound traffic. Thu 05/26/2016 05:59:54 PM : [GET-LNK-RSP ] 02 69 06 Thu 05/26/2016 05:59:54 PM : [LNK-DATA ] 02 57 A2 09 01 DB B6 07 07 FF Thu 05/26/2016 05:59:55 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 05/26/2016 05:59:55 PM : [LNK-DATA ] 02 57 A2 0A 01 DB B6 07 07 FF Thu 05/26/2016 05:59:55 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 05/26/2016 05:59:55 PM : [LNK-DATA ] 02 57 A2 0B 01 DB B6 07 07 FF Thu 05/26/2016 05:59:56 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 05/26/2016 05:59:56 PM : [LNK-DATA ] 02 57 A2 0C 01 DB B6 07 07 FF Thu 05/26/2016 05:59:56 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 05/26/2016 05:59:56 PM : [LNK-DATA ] 02 57 A2 0D 01 DB B6 07 07 FF Thu 05/26/2016 05:59:56 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 CB 11 01 LTONRR (01) - motion sensor Thu 05/26/2016 05:59:56 PM : [std-Group ] 13.F2.57-->Group=1, Max Hops=3, Hops Left=2 Thu 05/26/2016 05:59:56 PM : [D2D EVENT ] Event [13 F2 57 1] [DON] [1] uom=0 prec=-1 Thu 05/26/2016 05:59:56 PM : [ 13 F2 57 1] DON 1 Thu 05/26/2016 05:59:56 PM : [D2D-CMP 006D] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 05/26/2016 05:59:56 PM : [D2D-CMP 0068] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 05/26/2016 05:59:56 PM : [D2D-CMP 0067] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 05/26/2016 05:59:57 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 CB 11 01 LTONRR (01) Thu 05/26/2016 05:59:57 PM : [std-Group ] 13.F2.57-->Group=1, Max Hops=3, Hops Left=2 Thu 05/26/2016 05:59:57 PM : [iNST-DUP ] Previous message ignored. Thu 05/26/2016 05:59:57 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 05/26/2016 05:59:57 PM : [LNK-DATA ] 02 57 A2 02 13 F2 57 10 01 34 Thu 05/26/2016 05:59:57 PM : [iNST-TX-I1 ] 02 62 00 00 91 CF 13 00 Thu 05/26/2016 05:59:57 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Usually PLM links go up because of testing. Scenes are changed and rewritten. It is common for PLM link counts to go down after doing a Restore Modem (PLM) because the now deleted Scene records are not written by a Restore Modem (PLM). Once you determine what is causing the Insteon traffic so a good Show PLM Links Table is obtained (should be run 3-4 times to insure count is good), do a Restore Modem (PLM) followed by another Show PLM Links Table (show done a few times to insure new count is correct). Now you know your starting point. May not be necessary to do anything at this point. If link records still need to be reduced, combining Scenes, eliminating Scenes, eliminating devices in Scenes, are some of the actions that can be done. It is very rare to reach the PLM max when the PLM has been cleaned up with a Restore Modem (PLM).

bmf Are the Insteon devices mounted in metal boxes? Is the 2474 installed between other devices in the same box?

The Show PLM Links Table will be incorrect if any Insteon activity reaches the PLM during the Show. Motion Sensor activity, thermostat humidity, Insteon switches, anything that matches a PLM link record. The next PLM record read will be the one following the unexpected Insteon message. The 02 6A 15 indicates the last active record has been read but many PLM link records can be skipped if an Insteon activity reaches the PLM.

That means either a defective device or something in the area of the 2 wire SwitchLinc is interfering with RF.

Also since that is a 2 wire dimmer, it needs to be connected to an "incandescent bulbs only". Also there must be an RF capable device available to receive comm from 2474.

There is bad comm to device. The Standard commands have a Max Hops=3, Hops Left=0 which is as bad as it can get and still work. The Extended command got no response from device on any of the three attempts. What devices are used to couple the 2 120v legs? Thu 05/26/2016 07:10:56 AM : [3d e7 22 ] Added to list of devices to link to ISY Thu 05/26/2016 07:10:56 AM : [iNST-TX-I1 ] 02 62 3D E7 22 0F 0D 00 Thu 05/26/2016 07:10:56 AM : [iNST-ACK ] 02 62 3D.E7.22 0F 0D 00 06 (00) Thu 05/26/2016 07:10:57 AM : [iNST-SRX ] 02 50 3D.E7.22 39.00.97 23 0D 02 (02) Thu 05/26/2016 07:10:57 AM : [std-Direct Ack] 3D.E7.22-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Thu 05/26/2016 07:10:57 AM : [iNST-TX-I1 ] 02 62 3D E7 22 0F 10 00 Thu 05/26/2016 07:10:57 AM : [iNST-ACK ] 02 62 3D.E7.22 0F 10 00 06 ID-REQ (00) Thu 05/26/2016 07:11:06 AM : [iNST-TX-I1 ] 02 62 3D E7 22 0F 10 00 Thu 05/26/2016 07:11:06 AM : [iNST-ACK ] 02 62 3D.E7.22 0F 10 00 06 ID-REQ (00) Thu 05/26/2016 07:11:07 AM : [iNST-SRX ] 02 50 3D.E7.22 39.00.97 23 10 00 ID-REQ (00) Thu 05/26/2016 07:11:07 AM : [std-Direct Ack] 3D.E7.22-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Thu 05/26/2016 07:11:07 AM : [iNST-SRX ] 02 50 3D.E7.22 01.24.42 83 01 65 (65) Thu 05/26/2016 07:11:07 AM : [std-Broadcast] 3D.E7.22-->01.24.42, Max Hops=3, Hops Left=0 Thu 05/26/2016 07:11:07 AM : [3D E7 22 0 ] Calibrating engine version Thu 05/26/2016 07:11:07 AM : [iNST-TX-I2CS] 02 62 3D E7 22 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 05/26/2016 07:11:07 AM : [iNST-ACK ] 02 62 3D.E7.22 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 05/26/2016 07:11:16 AM : [iNST-TX-I2CS] 02 62 3D E7 22 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 05/26/2016 07:11:16 AM : [iNST-ACK ] 02 62 3D.E7.22 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 05/26/2016 07:11:25 AM : [iNST-TX-I2CS] 02 62 3D E7 22 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 05/26/2016 07:11:25 AM : [iNST-ACK ] 02 62 3D.E7.22 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 05/26/2016 07:11:29 AM : [3D E7 22 0 ] Failed to add device, reason 9 Thu 05/26/2016 07:11:29 AM : [All ] Writing 0 bytes to devices

Could try a Factory Reset of KPL followed by a Restore device. Have you checked the wiring? A wire nut could have come lose.