LeeG

sfroach It can be a slow process. Pick a few Insteon messages from a trace and analyze the contents. It is easier today to start because SmartLabs has released so much information that was confidential not to long ago. If you run into something that looks important but don't understand, post and I will try to answer. Thanks Brian, they are all good references.

Teken's point about studying the insteondetails.pdf document is a great point. Much of what is seen in the LEVEL 3 trace is Insteon specifics which the Wiki nor the ISY User Guide will never teach. First, the ISY cannot send/receive Insteon directly so all Insteon activity is physically to or from the PLM. It may be from a device going through the PLM to the ISY but always physically to or from PLM. It would have been better to post the event trace as a .txt file so i could include individual lines in this post. What does '[iNST-TX-I1]' mean? Is that ISY Transmitting or it the PLM? This is a Insteon message from the ISY to the PLM to be sent over the Insteon network. TX-I1 is sending an I1 message. It starts with 02 62 which indicates an a outbound message. What does INST-ACK mean? Is that a device acknowledging receipt or is it the PLM? This is the PLM ACKing the previous. It is a mirror image of the line above with an 0x06 added to the end indicating the outbound message has a good structure. A 0x15 on the end would indicate a bad message structure. What does D2D Event mean? Is that a device reporting a Status change? I don't know what D2D actually stands for. It is describing the PLM ACK above. Whats uom=0, prec=-1 mean? uom - Unit of Measure (I think - means more to UDI than us) prec - Precision (I think - means more to UDI than us) What's D2D-CMP 0013 mean? It will require a post of your Program to explain. Looks like an evaluation of the If but need Program to be sure. Really need to understand Insteon details to appreciate the information in the Insteon messages. An Insteon message that starts with 02 6x is outbound to the PLM or device. An Insteon message that starts with 02 5x is inbound from device.

If the Motion Sensor is a Controller of a Scene the Motion Sensor cannot be stopped by the ISY Disable. Insteon has no concept of enabling/disabling a Scene by issuing an ISY Enable/Disable of the Controller. The Motion Sensor can be marked Disabled but this has NO affect on the Motion Sensor controlling the Scene.

apostolakist is correct, a Set Scene 'xxxxx' On (and turning Scene On with Admin Console) does not receive ACKs from the Responders. The ISY issues a single Group Broadcast message for the Scene number which has all Responders reacting at the same time. The change in Responder device Status is what the ISY expects to happen from the Scene execution. Same result from a device turning a Scene On (button/paddle press On). Although the Controller device does receive ACKs from the Responders the only thing the PLM/ISY knows is the Scene was turned On. The ISY sets the Scene Responder Status to what the Scene should do rather than knowing what actually happened.

There should be a Fade Stop after the Fade Down. Hardware always sends that command when a button/paddle/toggle is released after starting a Fade Up or Fade Down. Some devices will not react well if they do not see the Fade Stop. Entry for 15 - [iD 0004][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'Entry Light' Fast On Wait 15 minutes Set Scene 'Entry Light' Fade Down Wait 5 seconds Set Scene 'Entry Light" Fade Stop Else - No Actions - (To add one, press 'Action')

Duplicate post. See other post for answer.

The Scene that is used to turn the downstairs lights Off, add the two switches as Responders. Insteon allows a device to be a Controller in one Scene only. When a Controller, as below, a device is assumed to also be a Responder. The "entry light" Scene cross links the two devices. Scene "entry light" 30.BA.D4 - Red Controller 33.B6.A8 - Red Controller Scene "downstairs lights" 30.BA.D4 - Responder 33.B6.A8 - Responder other Responders

Mikes Most of what is in the event trace can be understood by reading the insteondetails.pdf document that is accessed at insteon.com. Some information in that document discusses details about how Insteon works which may be interesting to some but the good stuff covers Insteon message structure and flow in detail. Also SmartLabs has released what was confidential in the past, details on device specific information under the Developer section. Some of the information in that LEVEL 3 trace is added by UDI. The Blue is the actual inbound message from device. The other information is the UDI identification of some of the data in the message; Group, Max Hops, Hops Left, that is helpful to know without having to analyze the actual message. Wed 06/24/2015 04:10:20 AM : [iNST-SRX ] 02 50 1C.FD.D5 00.00.01 CB 13 00 LTOFFRR(00) Wed 06/24/2015 04:10:20 AM : [std-Group ] 1C.FD.D5-->Group=1, Max Hops=3, Hops Left=2 It just takes time to dig out all the useful information. i've been using Insteon for some ten years. There is information that has not been necessary to understand to know what is happening. New things which SmartLabs is adding all the time which they consider confidential and do not discuss with us normal users. The release of the Developer Notes was a major advance in what SmartLabs was willing to pass on to users.

The reason for needing two Programs is the fact that the light being tested in the If section changes Status by the Then clause. The change in light Status from Off to On causes Program to be triggered again. The If now evaluates to False which drives the Else clause which changes light Status again when a single Program. When two programs the Program is triggered again and the If is False which drives the Else. However, with two Programs the Else does not do anything so the light remains On. The IR code was Pressed once so the IR code does not cause another Program trigger. It is the change in light Status that causes the retrigger.

hurnik To have the three Leak Sensor nodes in a Group, right click on one of the nodes and select Group Devices. It brings the three nodes together. Click the node with the +,sign to expand. Also note that there is a limit to the size of the node names. Using a long node name could prevent room for the - Dry, - Heartbeat, - Wet nodes. - Dry node is On when Leak Sensor is Dry - Wet node is On when Leak Sensor is Wet - Heartbeat node receives On or Off command at the approx 24 hour period to know Leak Sensor is communicating. The Leak Sensor 2 nodes have the Group Devices function used. The Leak Sensor has not had the Group Devices used so the three nodes are not grouped together. Two of the Leak Sensor nodes are toward the bottom of the image

sfroach Note that a Scene On and Scene Off command sends a single Insteon command and there are NO ACKs associated with the Insteon activity. It is assumed the devices received the command and turned On or Off. It is common for a low voltage transformer to generate enough interference when On that the Off command is not recognized. Suggest using a simple incandescent bulb to run a test of On and Off without the transformers. If that does not work reliably then there is a general comm issue to the OutletLinc. If the incandescent bulb is reliable then the transformers are the issue. Try powering a single transformer from FilterLinc to see if things improve.

"Immediately the kitchenB fires that says if its off, turn it on. seems like a loop. " Besides the Program names discussed not matching the examples posted, kitchenB is describing Kitchen #2B?; the "seems like a loop" is discussing a Program that sounds like something you did not design? If you are using examples someone else authored please provide the functional details you want to implement. With that information a Program or Programs can be suggested to provide that function.

The Scene turning Off cannot cause Kitchen #1 to trigger. That leaves either another Program being triggered or the Scene contains 'Kitchen / Kitchen Cabinets'. 'Kitchen / Kitchen Cabinets' turning Off will trigger Kitchen #2B

If Control is a trigger ONLY when the device is manually operated. That is a major characteristic of If Control. Turning the device On/Off with a Scene is not manual operation of the device and therefore does not trigger the Program. If Status triggers when a device is operated by a Scene, as a Responder to another device (which is a Scene), and when device is operated manually. Use the If variation that satisfies the requirements of the situation.

I put this simple test Program together that has an If 'is responding' for an I/O Linc Sensor. This Program does not trigger when Sensor is switched On or Off. Notice no X10 traffic as Sensor is cycled Off, then On. AAA3 - [iD 0043][Parent 0001] If Status 'IOLinc I2CS-Sensor' is Responding Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' Wed 06/24/2015 04:10:20 AM : [iNST-SRX ] 02 50 1C.FD.D5 00.00.01 CB 13 00 LTOFFRR(00) Wed 06/24/2015 04:10:20 AM : [std-Group ] 1C.FD.D5-->Group=1, Max Hops=3, Hops Left=2 Wed 06/24/2015 04:10:20 AM : [D2D EVENT ] Event [1C FD D5 1] [DOF] [0] uom=0 prec=-1 Wed 06/24/2015 04:10:20 AM : [ 1C FD D5 1] DOF 0 Wed 06/24/2015 04:10:20 AM : [D2D EVENT ] Event [1C FD D5 1] [sT] [0] uom=0 prec=-1 Wed 06/24/2015 04:10:20 AM : [ 1C FD D5 1] ST 0 Wed 06/24/2015 04:10:20 AM : [D2D-CMP 0079] STS [1C FD D5 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Wed 06/24/2015 04:10:20 AM : [iNST-SRX ] 02 50 1C.FD.D5 13.00.01 CB 06 00 (00) Wed 06/24/2015 04:10:20 AM : [std-Group ] 1C.FD.D5-->13.00.01, Max Hops=3, Hops Left=2 Wed 06/24/2015 04:10:20 AM : [iNST-INFO ] Previous message ignored. Wed 06/24/2015 04:10:26 AM : [iNST-SRX ] 02 50 1C.FD.D5 00.00.01 CB 11 00 LTONRR (00) Wed 06/24/2015 04:10:26 AM : [std-Group ] 1C.FD.D5-->Group=1, Max Hops=3, Hops Left=2 Wed 06/24/2015 04:10:26 AM : [D2D EVENT ] Event [1C FD D5 1] [DON] [0] uom=0 prec=-1 Wed 06/24/2015 04:10:26 AM : [ 1C FD D5 1] DON 0 Wed 06/24/2015 04:10:26 AM : [D2D EVENT ] Event [1C FD D5 1] [sT] [255] uom=0 prec=-1 Wed 06/24/2015 04:10:26 AM : [ 1C FD D5 1] ST 255 Wed 06/24/2015 04:10:26 AM : [D2D-CMP 0079] STS [1C FD D5 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Wed 06/24/2015 04:10:27 AM : [iNST-SRX ] 02 50 1C.FD.D5 11.00.01 CB 06 00 (00) Wed 06/24/2015 04:10:27 AM : [std-Group ] 1C.FD.D5-->11.00.01, Max Hops=3, Hops Left=2 Wed 06/24/2015 04:10:27 AM : [iNST-INFO ] Previous message ignored. When the 'is responding' is changed to On the Program does trigger. AAA3 - [iD 0043][Parent 0001] If Status 'IOLinc I2CS-Sensor' is On Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' Wed 06/24/2015 04:13:37 AM : [iNST-SRX ] 02 50 1C.FD.D5 00.00.01 CB 13 00 LTOFFRR(00) Wed 06/24/2015 04:13:37 AM : [std-Group ] 1C.FD.D5-->Group=1, Max Hops=3, Hops Left=2 Wed 06/24/2015 04:13:37 AM : [D2D EVENT ] Event [1C FD D5 1] [DOF] [0] uom=0 prec=-1 Wed 06/24/2015 04:13:37 AM : [ 1C FD D5 1] DOF 0 Wed 06/24/2015 04:13:37 AM : [D2D EVENT ] Event [1C FD D5 1] [sT] [0] uom=0 prec=-1 Wed 06/24/2015 04:13:37 AM : [ 1C FD D5 1] ST 0 Wed 06/24/2015 04:13:37 AM : [D2D-CMP 0079] STS [1C FD D5 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Wed 06/24/2015 04:13:37 AM : [D2D-CMP 0043] STS [1C FD D5 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Wed 06/24/2015 04:13:37 AM : [ X10] A1 Wed 06/24/2015 04:13:37 AM : [X10-RSP ] 02 63 66 00 06 Wed 06/24/2015 04:13:37 AM : [ X10] A1/Off (11) Wed 06/24/2015 04:13:38 AM : [X10-RSP ] 02 63 63 80 06 Wed 06/24/2015 04:13:38 AM : [X10-RX ] 02 52 66 00 Wed 06/24/2015 04:13:38 AM : [ X10] A1 Your situation does not reproduce. There are other Programs involved or the Program described is not functional.

Something must be driving the 'is responding' Program as it does not run on its own initiative. Perhaps the thermostat is battery powered so that it changes to 'is not responding' to save battery life. Just a wild guess. Need more information to explain the operation.

The State variable changing value ($Vacation is 1) would trigger the Program while in a Wait. The evaluation would be False driving the Else clause.

The Wait (and Repeat) statement allows the Program to be triggered during the Wait (or Repeat). An 'If Time' has no False side trigger so the Waits will not cause the Else to run.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Set the time to a value 5 minutes in the future. Post the event trace when Program is triggered. The conditions described should be impossible. The Then works when directly Run but skips statements when the Program is triggered. There is more to this than is being documented. EDIT: look for another program that is invoking 'Morning lights' or the If itself is running 'Morning lights'

The ISY sent an Extended command three times to write a link record. The ToggleLinc failed to respond to any of the three command attempts. This usually means a comm issue. With a history of using the ToggleLinc to power LEDs it could mean an issue with the device itself. Put the ToggleLinc on an extension cord and power it at the PLM plug point. If the commands work the device is fine and there is a comm problem.

Is $Vacation an Integer or State variable?

Forgot to put this in my last post. Time range works the same for a Program and a Folder.

It should be a State variable. integer variables do not trigger Programs or Folders. I would not spend time analyzing what happens when the Folder has an Integer variable as the only condition. When it is a State variable that is False then analyze what happens with an Elk Zone trigger.

State variable is used in a Folder when the only condition. The Folder will turn True (has Green bar) when Folder condition is True. That does not happen with an Integer variable. Folder being True does not force a Program to trigger, only allows the Program condition(s) to trigger Program when they occur.

That would be the case where you want to monitor if something is possible (power available to a device). Something like Query or Off or On would be fine as you are not trying to analyze an issue with that particular device.