LeeG

Only PLM comm can have the retry count adjusted. A Scene link between a MS and Responder will always generate at least one Group Cleanup Direct message. If ACKed that would be the end of the Group Cleanup Direct messages. If not ACKed the Responder would receive another Group Cleanup Direct message. These are messages that have been used forever which makes me think they are not responsible for a 20 second delay in traffic.

Sorry, I do not understand the two conditions. Every Insteon device sending an On/Off command sends a Group Broadcast message and a Group Cleanup Direct message. Insteon has worked this way from the beginning 2005. The Group Cleanup Direct message is normally ignored. Wed 10/01/2014 10:48:13 AM : [iNST-SRX ] 02 50 1C.FD.D5 00.00.01 CB 13 00 LTOFFRR(00) Wed 10/01/2014 10:48:13 AM : [std-Group ] 1C.FD.D5-->Group=1, Max Hops=3, Hops Left=2 Wed 10/01/2014 10:48:13 AM : [D2D EVENT ] Event [1C FD D5 1] [DOF] [0] uom=0 prec=-1 Wed 10/01/2014 10:48:13 AM : [ 1C FD D5 1] DOF 0 Wed 10/01/2014 10:48:13 AM : [D2D EVENT ] Event [1C FD D5 1] [sT] [0] uom=0 prec=-1 Wed 10/01/2014 10:48:13 AM : [ 1C FD D5 1] ST 0 Wed 10/01/2014 10:48:13 AM : [iNST-SRX ] 02 50 1C.FD.D5 22.80.0B 41 13 01 LTOFFRR(01) Wed 10/01/2014 10:48:13 AM : [std-Cleanup ] 1C.FD.D5-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Wed 10/01/2014 10:48:13 AM : [iNST-DUP ] Previous message ignored. Wed 10/01/2014 10:48:13 AM : [iNST-SRX ] 02 50 1C.FD.D5 13.01.01 CB 06 00 (00) Wed 10/01/2014 10:48:13 AM : [std-Group ] 1C.FD.D5-->13.01.01, Max Hops=3, Hops Left=2 Wed 10/01/2014 10:48:13 AM : [iNST-INFO ] Previous message ignored. The Group Cleanup Direct was not ignored in your situation because a Fast On, Scene On and Fast Off were issued by the Program delaying the Group Cleanup Message to the point where it looks like another On scenario. For I2CS devices the retry count can be set. This is for the IO Linc I used in my trace. I think rather than adding a Wait or changing the retry count your Program could be split into two sections. The first Then invokes Program 2 which does a Disable of Program 1 so the command activity generated by Program 2 will not allow the delayed Group Cleanup Direct from triggering Program 1.

If Err is only blinking LED power off the unit and check the SD card to be sure it is seated correctly. if Mem and Err blinking the ISY cannot connect to the Ethernet network.

Normal device Insteon Scene traffic starts with of a Group Broadcast message (in Red) that all linked responders normally see and react to. This message has no responder Insteon address (as there could be many responders) so no responder can ACK this message. Knowing this message is not ACKed a device then sends a Group Cleanup Direct message (in Blue) to each responder, one at a time. This message is ACKed so if an ACK is not received it is repeated a few times expecting an ACK on one of the retries. Normally the ISY ignores the Group Cleanup Direct messages. In this case the Program that is triggered by the initial Group Broadcast immediately puts Insteon traffic on the network so the Group Cleanup Direct message is received very late. In an Insteon Scene world this would normally mean the Group Broadcast was not received so the Group Cleanup Direct takes its place (as is designed by SmartLabs) and triggers the Program. Normal solution is to Wait 1 or 2 seconds in the Program before sending Insteon traffic. In the latest I2CS world devices can be told how many retries to perform. Setting the retry count to 0 suppresses all the Group Cleanup Direct messages so a second Program trigger is prevented because there is no Group Cleanup Direct message. Only I2CS devices have this control over retries. Tue 09/30/2014 04:21:45 PM : [iNST-SRX ] 02 50 28.40.E7 00.00.01 C7 11 01 LTONRR (01) Tue 09/30/2014 04:21:45 PM : [Std-Group ] 28.40.E7-->Group=1, Max Hops=3, Hops Left=1 Tue 09/30/2014 04:21:45 PM : [D2D EVENT ] Event [28 40 E7 1] [DON] [1] uom=0 prec=-1 Tue 09/30/2014 04:21:45 PM : [ 28 40 E7 1] DON 1 Tue 09/30/2014 04:21:45 PM : [D2D-CMP 0080] CTL [28 40 E7 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:45 PM : [D2D-CMP 007D] CTL [28 40 E7 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:45 PM : [D2D-CMP 006E] CTL [28 40 E7 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:45 PM : [D2D-CMP 009D] CTL [28 40 E7 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:45 PM : [D2D-CMP 0009] CTL [28 40 E7 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:46 PM : [iNST-TX-I1 ] 02 62 26 D2 CE 0F 12 00 Tue 09/30/2014 04:21:46 PM : [iNST-TX-I1 ] 02 62 00 00 12 CF 11 00 Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [iNST-ACK ] 02 62 26.D2.CE 0F 12 00 06 LTON-F (00) Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [ Time] 16:22:02 0(0) Tue 09/30/2014 04:21:46 PM : [iNST-SRX ] 02 50 26.D2.CE 2A.1C.95 23 12 00 LTON-F (00) Tue 09/30/2014 04:21:46 PM : [std-Direct Ack] 26.D2.CE-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 09/30/2014 04:21:46 PM : [iNST-ACK ] 02 62 00.00.12 CF 11 00 06 LTONRR (00) Tue 09/30/2014 04:21:47 PM : [iNST-TX-I1 ] 02 62 26 D2 CE 0F 14 00 Tue 09/30/2014 04:21:47 PM : [D2D EVENT ] Event [26 D2 CE 1] [sT] [255] uom=0 prec=-1 Tue 09/30/2014 04:21:47 PM : [ 26 D2 CE 1] ST 255 Tue 09/30/2014 04:21:47 PM : [iNST-SRX ] 02 50 28.40.E7 2A.1C.95 41 11 01 LTONRR (01) Tue 09/30/2014 04:21:47 PM : [Std-Cleanup ] 28.40.E7-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 09/30/2014 04:21:47 PM : [iNST-ACK ] 02 62 26.D2.CE 0F 14 00 06 LTOFF-F(00) Tue 09/30/2014 04:21:47 PM : [D2D EVENT ] Event [28 40 E7 1] [DON] [0] uom=0 prec=-1 Tue 09/30/2014 04:21:47 PM : [ 28 40 E7 1] DON 0 Tue 09/30/2014 04:21:47 PM : [D2D-CMP 0080] CTL [28 40 E7 1] DON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:47 PM : [D2D-CMP 007D] CTL [28 40 E7 1] DON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:47 PM : [D2D-CMP 006E] CTL [28 40 E7 1] DON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:47 PM : [D2D-CMP 009D] CTL [28 40 E7 1] DON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Tue 09/30/2014 04:21:47 PM : [D2D-CMP 0009] CTL [28 40 E7 1] DON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true

sanders2222 I ran a few tests this morning on the results of deleting a device. Programs reflected the deleted device after restarting the Admin Console. Before the restart If From Sunset To Sunrise (next day) And From Sunset For 2 hours Then Set 'IO Linc I2CS-Relay' On Else - No Actions - (To add one, press 'Action') After the restart If From Sunset To Sunrise (next day) And From Sunset For 2 hours Then Set <Not Specified> On Else - No Actions - (To add one, press 'Action')

dstanley Thank you for the kind words. The ISY community is the best I have had the pleasure to work with. Great group of folks. The UDI folks are none better. Their products are excellent and the level of support could not be better.

The IRLincR handles many more codes than the credit card remote generates. Check the Specs and the User Guide on the Smarthome site. There could be huge number of nodes required if generated when the IRLincR is added to the ISY.

The ISY places the parens in the correct location. Was the Program change Saved?

Good to hear it is working. I think if the Admin Console was closed and started again the Program references would have been marked as 'not available' or something to that affect. I don't think programs reflect a deleted device without restarting the Admin Console

Program 1 has a coding problem If From Sunset To Sunrise (next day) And Control 'Triggerlinc' is switched On And ( Status 'Island (Kitchen ICON)' is Off Or Status 'Island (Mudroom Door ICON)' is Off ) Then Run Program 'Mud Room Lightup - 2' (Else Path) Without the parens the Ored Status check is NOT anded with the TriggerLinc action

Red circle with line indicates program is disabled. For Program 2 what is all red?

The motion sensor did not respond to the three commands sent to it. There are three pairs of 02 62 ...... outbound messages with no 02 50 ..... response. Only thing to try is a Factory Reset of the motion sensor. If that does not work the motion sensor likely defective. The access point may have failed but I'm more inclined to think motion sensor issue.

The Red LED on the mortion sensor will blink when in linking mode. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Run the New INSTEON Device again and post the trace.

Having to replace the battery should not have lost the links to the PLM. To add the Motion Sensor to the ISY it cannot already be defined to the ISY. Use New INSTEON Device (as you have been). Before clicking Ok on the popup put the motion sensor into linking mode with a single press and hold of Motion Sensor Set button for 4-5 seconds. Then click Ok. That message indicates the motion sensor either was not in linking mode before or is not in range of a Dual Band device. Also check device address is correct. Those labels can be easily misread.

I assume the Set Scene 'Island' On is changing the Status of 'Island (Mudroom Door ICON)'. As soon as the Status changes the Program is triggered again with a False result that drives the Else clause. The Then clause is terminated because of the Wait and change in Island Status.

If From 7:30:00PM To 9:30:00PM (same day) Then Also the Program is triggered True only at exactly 7:30PM and triggered False only at exactly 9:30PM. To test change the Program to a From time that is a few minutes past current time. At the From time the Program will run the Then. Set the To time to something a few minutes after the From time so the Else leg can be tested.

If From 10:30:00PM To 5:30:00AM (next day) Then

That message is usually the result of not having comm with the device. Since it is not a Dual Band device it could be on the opposite 120v leg as the PLM and there is a coupling problem. What is being used to couple the twe 120v legs? If using Access Points (now called Range Extenders) do they indicate good RF comm and on opposite 120v legs?

"Basically what I want is a scene where the motion sensor is the controller for the light and turns it on, but only allow that to happen on a certain schedule. Is that possible" It seems the question has changed. From the initial post it is not possible to have the motion sensor as Controller and only operate the Scene some of the time. Insteon has no means of having the motion sensor the Controller and have that work on a schedule. A Program can be triggered by the motion sensor within a schedule and have the Program turn the devices On with a Scene. There will be approx 1 second delay in having both lights turn On which is the cost to invoke a Program. The Program can react to the lights already being On as well as operate the light Scene only during certain times. The suggestion to set the On Level to zero will prevent the lights from turning On but will also turn the lights Off if the lights had been turned on manually.

A Scene does not have a means of adding a schedule. A Program is required.

Running the ISY with manual links is not a good idea.

Thanks Brian. I was not aware that linking was even possible until Stu raised the question. I found the same results you did.

"Is there a way to do that using an ISY?" No. "If not, then is there any problem with manually linking that button pair?" The expected versus actual link tables will not match making a Restore Device impossible for both the RemoteLinc and any manually linked device. Also it will be necessary to analyze the link tables to see what devices are affected be those buttons.

Assuming the PLM is a 2413 that is the Dual Band device to use. Use New INSTEON Device. Enter the Insteon address of one of the devices, Name of your choice, and Auto Discover. Put the device into manual linking mode. Click Ok on New INSTEON Device. With the device near the 2413 PLM comm should not be a problem.

paulbates There are no Wait or Repeat statements in that Program. The Then clause will run all the statements. The issue that started this topic was a Wait that allows the change in if Conditions to terminate the clause. When no Wait or Repeat is used the clause runs all the statements.