LeeG

The image did not attach. Be sure to click Attach after image selected. The Admin Console has not changed much as far as the overall look. Click Help | About, what is displayed for Firmware, what is displayed for UI?

Several of my battery devices send multiple Group Broadcast On messages. Do not know why they do, perhaps SmartLabs felt battery communication would need assistance since the device cannot monitor power line for conflicting message activity. This is from a motion sensor. Thu 11/27/2014 06:11:18 PM : [iNST-SRX ] 02 50 14.99.51 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 06:11:18 PM : [std-Group ] 14.99.51-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:11:18 PM : [D2D EVENT ] Event [14 99 51 1] [DON] [1] uom=0 prec=-1 Thu 11/27/2014 06:11:18 PM : [ 14 99 51 1] DON 1 Thu 11/27/2014 06:11:18 PM : [D2D-CMP 006B] CTL [14 99 51 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 06:11:18 PM : [D2D-CMP 0045] CTL [14 99 51 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 06:11:18 PM : [D2D EVENT ] Event [14 99 51 1] [sT] [255] uom=0 prec=-1 Thu 11/27/2014 06:11:18 PM : [ 14 99 51 1] ST 255 Thu 11/27/2014 06:11:18 PM : [VAR 2 7 ] 1 Thu 11/27/2014 06:11:18 PM : [iNST-SRX ] 02 50 14.99.51 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 06:11:18 PM : [std-Group ] 14.99.51-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:11:18 PM : [iNST-DUP ] Previous message ignored. Thu 11/27/2014 06:11:18 PM : [iNST-SRX ] 02 50 14.99.51 11.00.01 CB 06 00 (00) Thu 11/27/2014 06:11:18 PM : [std-Group ] 14.99.51-->11.00.01, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:11:18 PM : [iNST-INFO ] Previous message ignored. Thu 11/27/2014 06:11:18 PM : [iNST-SRX ] 02 50 14.99.51 11.00.01 CB 06 00 (00) Thu 11/27/2014 06:11:18 PM : [std-Group ] 14.99.51-->11.00.01, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:11:18 PM : [iNST-INFO ] Previous message ignored. This is from a TriggerLinc Thu 11/27/2014 06:11:53 PM : [iNST-SRX ] 02 50 11.B6.BC 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 06:11:53 PM : [std-Group ] 11.B6.BC-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:11:53 PM : [D2D EVENT ] Event [11 B6 BC 1] [DON] [1] uom=0 prec=-1 Thu 11/27/2014 06:11:53 PM : [ 11 B6 BC 1] DON 1 Thu 11/27/2014 06:11:53 PM : [D2D-CMP 004F] CTL [11 B6 BC 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 06:11:53 PM : [D2D EVENT ] Event [11 B6 BC 1] [sT] [255] uom=0 prec=-1 Thu 11/27/2014 06:11:53 PM : [ 11 B6 BC 1] ST 255 Thu 11/27/2014 06:11:53 PM : [D2D-CMP 003D] STS [11 B6 BC 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Thu 11/27/2014 06:11:54 PM : [iNST-SRX ] 02 50 11.B6.BC 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 06:11:54 PM : [std-Group ] 11.B6.BC-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:11:54 PM : [iNST-DUP ] Previous message ignored. Thu 11/27/2014 06:11:54 PM : [iNST-SRX ] 02 50 11.B6.BC 22.80.0B 41 11 01 LTONRR (01) Thu 11/27/2014 06:11:54 PM : [std-Cleanup ] 11.B6.BC-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Thu 11/27/2014 06:11:54 PM : [iNST-DUP ] Previous message ignored. From another TriggerLinc Thu 11/27/2014 06:12:20 PM : [iNST-SRX ] 02 50 11.B8.2D 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 06:12:20 PM : [std-Group ] 11.B8.2D-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:12:20 PM : [D2D EVENT ] Event [11 B8 2D 1] [DON] [1] uom=0 prec=-1 Thu 11/27/2014 06:12:20 PM : [ 11 B8 2D 1] DON 1 Thu 11/27/2014 06:12:20 PM : [D2D-CMP 0061] CTL [11 B8 2D 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 06:12:20 PM : [D2D EVENT ] Event [11 B8 2D 1] [sT] [255] uom=0 prec=-1 Thu 11/27/2014 06:12:20 PM : [ 11 B8 2D 1] ST 255 Thu 11/27/2014 06:12:20 PM : [iNST-SRX ] 02 50 11.B8.2D 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 06:12:20 PM : [std-Group ] 11.B8.2D-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 06:12:20 PM : [iNST-DUP ] Previous message ignored. Thu 11/27/2014 06:12:21 PM : [iNST-SRX ] 02 50 11.B8.2D 22.80.0B 41 11 01 LTONRR (01) Thu 11/27/2014 06:12:21 PM : [std-Cleanup ] 11.B8.2D-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Thu 11/27/2014 06:12:21 PM : [iNST-DUP ] Previous message ignored.

Thanks for the trace, there are two On messages. However, my TriggerLincs do the same thing. Suggest adding a Wait 1 second at the beginning of the Then clause. Thu 11/27/2014 11:42:29 AM : [iNST-SRX ] 02 50 14.8A.FD 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 11:42:29 AM : [std-Group ] 14.8A.FD-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 11:42:29 AM : [D2D EVENT ] Event [14 8A FD 1] [DON] [1] uom=0 prec=-1 Thu 11/27/2014 11:42:29 AM : [ 14 8A FD 1] DON 1 Thu 11/27/2014 11:42:29 AM : [D2D-CMP 000B] CTL [14 8A FD 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 11:42:29 AM : [D2D-CMP 0009] CTL [14 8A FD 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 11:42:29 AM : [D2D EVENT ] Event [14 8A FD 1] [sT] [255] uom=0 prec=-1 Thu 11/27/2014 11:42:29 AM : [ 14 8A FD 1] ST 255 Thu 11/27/2014 11:42:29 AM : [iNST-SRX ] 02 50 14.8A.FD 00.00.01 CB 11 01 LTONRR (01) Thu 11/27/2014 11:42:29 AM : [std-Group ] 14.8A.FD-->Group=1, Max Hops=3, Hops Left=2 Thu 11/27/2014 11:42:30 AM : [D2D EVENT ] Event [14 8A FD 1] [DON] [1] uom=0 prec=-1 Thu 11/27/2014 11:42:30 AM : [ 14 8A FD 1] DON 1 Thu 11/27/2014 11:42:30 AM : [D2D-CMP 000B] CTL [14 8A FD 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 11/27/2014 11:42:30 AM : [D2D-CMP 0009] CTL [14 8A FD 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Go through the door Open/Close sequence and post the event trace. It sounds like the TriggerLinc is sending two On messages which can be related to how the magnet interacts with the TriggerLinc.

I have a 99i running a group of older devices. I use the 4.2.18 Admin Console, too long ago to know if I had to install another certificate. The 3.3.10 firmware does not support several of the newer Insteon devices (such as the latest KPLs) so its usefulness is limited.

When the new PLM was connected to the ISY and the PLM and then the ISY powered up, was a File | Restore Modem (PLM) issued? There is a step by step procedure in the Wiki for replacing a PLM.

Check Tools | Diagnostics | PLM Info/Status. What is the PLM firmware? Some users have seen this with PLM v9B firmware.

Thanks for posting back, good to know that helped.

Take a look at the KeypadLinc User Guide (around page 10-12, depends on KPL level). The Local On Level has two modes of operation. One is "Resume Bright" where the KPL turns On to the previous Local On Level when turned Off. The other mode is "Fixed Bright" where the KPL tuns On to the defined Local On Level. These modes have to be set using the instructions in the KeypadLinc User Guide.

"but the staus of each f the sensors is blank. Also, I never get any information about battery statuses." Do not know what "f the sensors is blank" means. The Low Battery node turns On when the battery is Low, otherwise the node is blank. If you want the Low Bat node to show Off, put the Hidden Door Sensor into manual linking mode. Right click the Low Bat node and select Query. Assuming the battery is Ok the Low Bat node will indicate Off. Be sure to take the Hidden Door Sensor out of linking mode so something unknown is not linked by mistake.

Sorry, I did not understand the issue. Use If Control 'ezsnsrf node' is switched On which triggers the Program when the node turns On. The Program is not affected when the node turns Off. The ISY Wait will timeout so the statements after the Wait execute. Nothing drives the Else clause

Nothing in the ISY affects the timer established in the EZSnsRF for that Dakota Alert device. If you have a spare PLM the free Simplehomenet Utility Suite can be used to change the timer in the EZSnsRF. Can change codes for the Dakota Alert device and add it to the EZSnsRF as another device and not set the timer.

Note that the 2412N SmartLinc port is a LAN (Internet) connection. The port on a 2413S is for a Serial port. Not sure what that did to the ISY Serial port.

Go to the other post for answer.

Enabling Program does not cause that Program to Run. What is in "Driveway Alerts Lights"? EDIT: I see the attachment. You need to Run that Program. Enabling does not cause the Program to execute.

The 2412N does not work with the ISY. Is that the correct number?

Post the Programs again and the event log at LEVEL 3 showing EZSnsRF activation.

The Programs are not overriding each other. While in the 15 minute Wait the first Program is not doing anything. Look for other reason such as turning Off devices causes the first Program to be triggered turning Island back On.

Device 2A.20.84 InlineLinc has very poor communication with the PLM. Many of the commands are working at the extreme edge or not getting a response from the device at all. Max Hops=3 ,Hops Left=0 is as bad as comm can be and still work. Sáb 11/22/2014 05:27:31 AM : [iNST-SRX ] 02 50 2A.20.84 2F.B9.B6 23 0D 02 (02) Sáb 11/22/2014 05:27:31 AM : [std-Direct Ack] 2A.20.84-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sáb 11/22/2014 05:27:32 AM : [iNST-SRX ] 02 50 2A.20.84 01.32.41 83 01 73 (73) Sáb 11/22/2014 05:27:32 AM : [std-Broadcast] 2A.20.84-->01.32.41, Max Hops=3, Hops Left=0 These commands got no response from device (no 02 50 ...... response) Sáb 11/22/2014 05:27:32 AM : [iNST-TX-I2CS] 02 62 2A 20 84 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sáb 11/22/2014 05:27:32 AM : [iNST-ACK ] 02 62 2A.20.84 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sáb 11/22/2014 05:27:41 AM : [iNST-TX-I2CS] 02 62 2A 20 84 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sáb 11/22/2014 05:27:41 AM : [iNST-ACK ] 02 62 2A.20.84 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sáb 11/22/2014 05:27:50 AM : [iNST-TX-I2CS] 02 62 2A 20 84 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sáb 11/22/2014 05:27:50 AM : [iNST-ACK ] 02 62 2A.20.84 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sáb 11/22/2014 05:27:54 AM : [2A 20 84 0 ] Failed to add device, reason 9

Being that two RF only devices have comm issues look into the Dual Band device(s) the thermostats would communicate through to get to the PLM. Are any other devices, particularly RF only devices, experiencing comm issues? Perhaps something happened to one of the devices used to couple the 120v legs was unplugged or turned Off. The first three commands sent to the thermostat failed to get any response from thermostat Fri 11/21/2014 07:14:25 PM : [iNST-TX-I1 ] 02 62 29 25 E2 0F 0D 00 Fri 11/21/2014 07:14:25 PM : [iNST-ACK ] 02 62 29.25.E2 0F 0D 00 06 (00) Fri 11/21/2014 07:14:34 PM : [iNST-TX-I1 ] 02 62 29 25 E2 0F 0D 00 Fri 11/21/2014 07:14:34 PM : [iNST-ACK ] 02 62 29.25.E2 0F 0D 00 06 (00) Fri 11/21/2014 07:14:43 PM : [iNST-TX-I1 ] 02 62 29 25 E2 0F 0D 00 Fri 11/21/2014 07:14:43 PM : [iNST-ACK ] 02 62 29.25.E2 0F 0D 00 06 (00) Fri 11/21/2014 07:14:47 PM : [29 25 E2 0 ] Failed to add device, reason 3

There are many aspects to an ISY Scene that have to be changed when using Adjust Scene. That statement changes one value (On Level or Ramp Rate) in a single link record. It usually takes many Adjust Scene statements to change all On Levels for example. ISY Scene xxxx Motion Sensor - Sensor as Controller SwitchLinc as Controller LampLinc as Controller There are several "Insteon" Scenes associated with the above ISY Scene. The PLM is a Controller with the SwitchLinc as Responder The PLM is a Controller with the LampLinc as Responder The Motion Sensor - Sensor is a Controller with the SwitchLinc as Responder The Motion Sensor - Sensor is a Controller with the LampLinc as Responder The SwitchLinc is a Controller with the LampLinc as Responder The LampLinc is a Controller with the SwitchLinc as Responder That is 6 "Insteon" Scenes, each of which must be changed with a separate Adjust Scene statement to keep all the Controllers doing the same thing with all the Responders at the same On Level. If Ramp Rate is changed then 6 more Adjust Scene statements are needed to make the Ramp Rate changes. Coding an ISY Scene is pretty simple. Many folks do not understand just how many "Insteon" Scenes are involved with that single ISY Scene and how many Adjust Scene statements are necessary to alter the Responder values.

There is a procedure in the Wiki for installing a new PLM. Simply connecting to the new PLM is not enough. All link records that have the old PLM Insteon address have to be updated. Here is the link to the Wiki ..... http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29

Can you post a link to some examples. It sounds more like a finger check than a functional reason. It would set the program status to False

Yes. This statement "http://192.168.2.2/REST/programs/0026/" running this Program If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send X10 'A1/On (3)' Else Send X10 'B1/On (3)' <programs> <program id="0026" parentId="0001" status="false" folder="false" enabled="false" runAtStartup="false" running="idle"> <name>Beep</name> <lastRunTime>2014/11/20 10:17:22 PM</lastRunTime> <lastFinishTime>2014/11/20 10:17:22 PM</lastFinishTime> </program> </programs> Adding runThen to "http://192.168.2.2/REST/programs/0026/runThen/" <RestResponse succeeded="true"> <status>200</status> </RestResponse> The event log, first with a False Status when first REST statement without runThen followed by the same Program with False Status with runThen Thu 11/20/2014 10:17:20 PM : [ Time] 22:17:22 2(0) Thu 11/20/2014 10:17:20 PM : [X10-RSP ] 02 63 E6 00 06 Thu 11/20/2014 10:17:20 PM : [ X10] B1 Thu 11/20/2014 10:17:20 PM : [ X10] B1/On (3) Thu 11/20/2014 10:17:21 PM : [X10-RSP ] 02 63 E2 80 06 Thu 11/20/2014 10:17:22 PM : [X10-RX ] 02 52 E6 00 Thu 11/20/2014 10:17:22 PM : [ X10] B1 Thu 11/20/2014 10:22:36 PM : [ Time] 22:22:38 2(0) Thu 11/20/2014 10:22:36 PM : [X10-RSP ] 02 63 66 00 06 Thu 11/20/2014 10:22:36 PM : [ X10] A1 Thu 11/20/2014 10:22:36 PM : [ X10] A1/On (3) Thu 11/20/2014 10:22:37 PM : [X10-RSP ] 02 63 62 80 06 Thu 11/20/2014 10:22:37 PM : [X10-RX ] 02 52 66 00 Thu 11/20/2014 10:22:37 PM : [ X10] A1

Can insure Status is True by adding statement to If that will always be True. If $Sxxx is $Sxxx Then EDIT: ran some tests and confirmed the runThen does run the Then even if the current Status is False when the command is issued http://192.168.2.2/REST/programs/0026/runThen/ More convinced the REST command being issued has a problem of some sort causing the If clause to execute