LeeG

Mikes What are you trying to accomplish with 'is responding'? Here is a simple test Program result. No command sent to device. It is looking at the information the ISY has about whether the device has responded to commands. IsResponding - [iD 0053][Parent 0001] If Status 'IOLinc I2CS-Sensor / IOLinc I2CS-Relay' is Responding Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' Fri 06/19/2015 06:02:15 AM : [ Time] 06:02:14 4(0) Fri 06/19/2015 06:02:15 AM : [X10-RSP ] 02 63 66 00 06 Fri 06/19/2015 06:02:15 AM : [ X10] A1 Fri 06/19/2015 06:02:15 AM : [ X10] A1/On (3) Fri 06/19/2015 06:02:16 AM : [X10-RSP ] 02 63 62 80 06 Fri 06/19/2015 06:02:17 AM : [X10-RX ] 02 52 66 00 Fri 06/19/2015 06:02:17 AM : [ X10] A1 If you want to know at that instant if the device 'is responding' send some command first. On, Off, Query, whatever. You lose the ability to know if the device reacted to the last action against the device.if you issue a command. Again, what are you trying to accomplish? EDIT: Example A Program sends a command to the I/O Linc Relay to Close the garage door. The garage door does not close. A question that might be asked, did the I/O Linc Relay receive the command to Close the door? The "If 'is responding' " answers that question. If 'is responding' always sent a command you could not use the 'is responding' to know if the Close door command reached the I/O Linc Relay. If what the I/O Linc Relay did last is not important a command such as 'Off' can be sent to the device followed by an 'is responding' check. .

Yes. The file shows a KPL that "is not responding". I removed power from the device last week for other tests.

No commands are sent to the device by that statement. A "not responding" device has a Red ! next to the device node. A "responding" device does not have the red !. The If Status 'xxxx' is/is not responding is checking for the Red ! indication.

If using Scene Off command the On Level does not matter. If using a Scene On command the On Level must be 0%.

I do not use Mobilinc. The operative point is to turn a Scene On/Off to affect multiple devices. I have read discussions about Mobilinc making an assumption that a Scene should be used rather than control an individual device but as I said, I do not use Mobilinc so do not know those details. Mobilinc has a forum category where you would likely get better Mobilinc specific questions answered.

Sure. Need to know how you are turning one of the Scene devices Off to know how best to turn the KPL button(s) Off without affecting all the Scene devices. Done by physically turning the device Off, with a Program action, another Scene, etc. Detail is most important.

If there are multiple devices involved do not turn On/Off individual device. Insteon does not propagate that individual device command to other devices in a Scene. If all Scene devices are expected to stay in sync turn the Scene On/Off, not an individual device.

Using Scenes in Insteon is basic. For all the reasons mentioned creating Scene results using Programs is a bad approach. You may have coupling issues, noise or signal suckers, to explain why Scenes do not work now but whatever the issues they can be solved. Start with one Scene, set up the KPL buttons involved, whatever Responders are used, etc. When that is working well move on to the next. ISY Scene xxxx KPL1 - button B - Controller KPL2 - button B - Controller Responder1 - maybe as Controller if it has a paddle or Responder Responder2 - Responder Verify that the 2 120v legs are coupled. Tap the Set button on PLM 4 times to start Beacon test. Check color of KPL status LED in each KPL tto see if in RF range of PLM and on same or opposite 120v leg.

Select Link Management | New INSTEON Device. Enter Insteon Address of I/O Linc, Name of choice, and Auto Discover. Click Ok There will be two nodes added, one for Sensor, one for Relay

Generally Parens are needed when the If has both Or and And statements. The Parens bracket a set of conditions, a group of Ors or a Group of Ands that then need to be Ored or Anded with something else. Without the Parens some of the Ored conditions operate without benefit of the time range. The Wiki has some examples that may be helpful.

Use a Program like this to monitor Heartbeat. This one turns On an X10 device, most folks prefer a Notification if Heartbeat fails. HeartBeat - [iD 0044][Parent 0001] If Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Dry / Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action') The ISY Log shows change of state. The Heartbeat will have the same state as long as it stays dry.

Also if the BuzzLinc should alert ONLY when door is Opened and NOT if door remains Open then use If Control If From Sunset To Sunrise (next day) And ( Control 'Door Sensors / Deck Door Sensor' is switched On Or Control 'Door Sensors / Kitchen Door Sensor' is switched On Or Control 'Door Sensors / Man Cave Door Sensor' is switched On ) Then Repeat 3 times Set 'BuzzLinc' On Set 'BuzzLinc' 2 (Beep Duration) Set 'BuzzLinc' Off Else Set 'BuzzLinc' Off

Need Parens so time range applies to all Sensors If From Sunset To Sunrise (next day) And ( Status 'Door Sensors / Deck Door Sensor' is On Or Status 'Door Sensors / Kitchen Door Sensor' is On Or Status 'Door Sensors / Man Cave Door Sensor' is On ) Then Repeat 3 times Set 'BuzzLinc' On Set 'BuzzLinc' 2 (Beep Duration) Set 'BuzzLinc' Off Else Set 'BuzzLinc' Off

Not possible to Disable Relay node alone. Both nodes would Disable. The only way I know to avoid this if relocating the PLM does not resolve is to change to a NO switch. That way both the Sensor and Relay would be Off during the 3AM Query. The extra Sensor message (which could also be an extra Relay message) would not produce a False Open indication.

The I/O Linc Sensor is On so the door should be closed. However, comm coming from the garage is a problem. This is the initial response from Sensor showing Sensor On. Sun 06/14/2015 03:56:48 PM : [iNST-SRX ] 02 50 2F.8D.28 2C.08.F8 27 00 01 (01) Sun 06/14/2015 03:56:48 PM : [std-Direct Ack] 2F.8D.28-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 06/14/2015 03:56:48 PM : [D2D EVENT ] Event [2F 8D 28 1] [sT] [255] uom=0 prec=-1 Sun 06/14/2015 03:56:48 PM : [ 2F 8D 28 1] ST 255 - Sensor (NODE 1) shows On However, after the physical Query of the Relay a second Sensor response is seen at the PLM. Because this response comes after the Query of the Relay but before the Relay Query response, NODE 2 (Relay) is marked On in error Sun 06/14/2015 03:56:48 PM : [iNST-TX-I1 ] 02 62 2F 8D 28 0F 19 00 - Query of Relay Sun 06/14/2015 03:56:48 PM : [iNST-ACK ] 02 62 2F.8D.28 0F 19 00 06 LTSREQ (LIGHT) Sun 06/14/2015 03:56:48 PM : [iNST-SRX ] 02 50 2F.8D.28 2C.08.F8 23 00 01 (01) - duplicate Sensor response Sun 06/14/2015 03:56:48 PM : [std-Direct Ack] 2F.8D.28-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 06/14/2015 03:56:48 PM : [D2D EVENT ] Event [2F 8D 28 2] [sT] [255] uom=0 prec=-1 Sun 06/14/2015 03:56:48 PM : [ 2F 8D 28 2] ST 255 This is the actual Relay Query response showing Relay is Off but it is ignored since the duplicate Sensor response was already applied to the Relay Query Sun 06/14/2015 03:56:49 PM : [iNST-SRX ] 02 50 2F.8D.28 2C.08.F8 27 00 00 (00) Sun 06/14/2015 03:56:49 PM : [std-Direct Ack] 2F.8D.28-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 This did not cause any action since the Relay is not connected and no Program is looking at Relay state. However, the Relay state is marked On and would cause issues if you had a Program monitoring the Relay. EDIT: it is these duplicate messages that caused the false door open

2 - Any scene communication (PLM to device, device to PLM) requires a link record in both devices. For a SwitchLinc to send command to PLM (ISY) when paddle is pressed requires a Controller link (starts with E2) in device and Responder link (starts with A2) in PLM. These links are created when device added to ISY. All Scene communication from PLM to device requires a Controller link (E2) in PLM and Responder link (A2) in device. These are created when Scenes are defined. 3 - No. 4 - No. Only consideration is information in ISY reflects current devices. A File | Restore ISY to an earlier backup that does not reflect current devices would create issues for any PLM or device restore. As long as ISY is current no concern for doing a Restore.

The system wide Query at power up queries each I/O Linc node (Sensor and Relay) twice. When the Sensor is Queried both nodes are queried as it requires separate Query commands to get the state of both nodes. Then the Relay node is Queried so both nodes are queried again. Same thing happens with FanLinc where a unique Query command must be sent to each FanLinc node. Need to see the result of a Tools | Diagnostics | Event Viewer at LEVEL 3 of a manual Query against Sensor node to know if door is actually open. You can post the result of the Event Trace for evaluation. Since Insteon is not controlling door movement (I/O Linc Relay not connected) what could be opening door as a result of a power outage? It is not likely a manual Query of Sensor would show a false Open state.

The 2413S PLM supports 992 link records. Run Tools | Diagnostics | Show PLM Links Table. Do it 3-4 times until the same total link number is repeated several times. Inbound messages affects the Next pointer so Show link count can be too high or too low if traffic is received. Also deleted links are counted so doing a File | Restore Modem (PLM) which eliminates deleted links may be useful.

All settings/options the ISY supports should be done with the Admin Console. This particular option cannot be set with the Admin Console so setting directly is the only choice.

Correct

The KeypadLinc (and SwitchLinc) Local On Level has two modes of operation. Going to the last On value is referred to as "Resume Bright". Refer to the KeypadLinc User Manual "Local On Level" for the information on using "Resume Bright" or using the defined Local On Level as an absolute.

You are running a 99i. That is both Discontinued and past End of Life. I cannot offer any suggestion on how to get the sliders to work. The Icon question was associated to the actual device definition for the I/O Linc and KPL. Was thinking an update may have been pending against one of the devices until the post showed using 99i. The Green LED being Off when door closed is correct.

As a side note, don't spend time evaluating the posted Relay Status. First, the Relay is a Responder Only. It does not report back to the ISY when the Relay turns Off. Second, regardless whether the Scene is sent an On or Off command, the I/O Linc MUST turn the Relay On to initiate any door movement, open or close. If the door moves the Relay was turned On regardless of the Scene command sent to the I/O Linc.

You have a Java issue. The Relay slider must stay at 0% On Level for the Scene name and Red button F as a Controller. Are there any additional Icons along side of Relay or KPL button F under Main device list? Click Help | About, what is displayed for Firmware? what is displayed for UI?

The Garage Door Scene, the Garage Door-Relay Responder slider should be 0% On Level. Set to 100% On Level you have seen commands issues against Garage Door Scene perform opposite to what you say you want. The Garage Door Scene lists the Garage Door-Relay as a Responder. That slider should be set to 0% On Level to have the Garage Door Scene On open the door. The image with Living Room Keypad - F in Red below Garage Door Scene was not posted. Click on Red Living Room Keypad - F and set Garage Door - Relay to 0% On Level. This is necessary for the On command from button F to open door.