LeeG

Image is of Scene with Relay On Level set to 0% On Level. The Scene On command Opens the door, the Scene Off command Closes the door. If there are additional Red Controllers of the Scene, click on each Red Controller below the Scene name. Set the I/O Linc Relay to 0% On Level to have an On command from the Controller open the door and an Off command close door. Each Controller must have the Relay with 0% On Level for the On and Off commands do the same thing as sending Scene name On and Off commands.

Click on Scene name that has I/O Linc Relay as Responder. Set the Scene Relay On Level to 0%.

Black to GND Either Red to S if Sensor should be On when door open or Green to S if Sensor should be On when door closed Tape unused Red or Green wire. Com and NO go to door opener

What problem are you having with a KPL?

Don't think so. The load control button is Queried with a Standard/Direct command to obtain local load information. This is followed by a single Extended command that returns all the Secondary KPL button On/Off states as a bit map. This Direct message pulls local load information. Tue 06/09/2015 06:23:01 PM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 19 00 Tue 06/09/2015 06:23:01 PM : [iNST-ACK ] 02 62 1B.57.F8 0F 19 00 06 LTSREQ (LIGHT) Tue 06/09/2015 06:23:01 PM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 00 00 (00) Tue 06/09/2015 06:23:01 PM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 06/09/2015 06:23:01 PM : [D2D EVENT ] Event [1B 57 F8 1] [sT] [0] uom=0 prec=-1 Tue 06/09/2015 06:23:01 PM : [ 1B 57 F8 1] ST 0 Tue 06/09/2015 06:23:01 PM : [D2D EVENT ] Event [1B 57 F8 1] [OL] [51] uom=0 prec=-1 Tue 06/09/2015 06:23:01 PM : [ 1B 57 F8 1] OL 51 Tue 06/09/2015 06:23:01 PM : [D2D EVENT ] Event [1B 57 F8 1] [RR] [31] uom=0 prec=-1 Tue 06/09/2015 06:23:01 PM : [ 1B 57 F8 1] RR 31 This single Extended message pulls all Secondary button information. Tue 06/09/2015 06:23:01 PM : [iNST-TX-I2 ] 02 62 1B 57 F8 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Tue 06/09/2015 06:23:01 PM : [iNST-ACK ] 02 62 1B.57.F8 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Tue 06/09/2015 06:23:02 PM : [iNST-SRX ] 02 50 1B.57.F8 22.80.0B 2B 2E 00 (00) Tue 06/09/2015 06:23:02 PM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 06/09/2015 06:23:02 PM : [iNST-ERX ] 02 51 1B 57 F8 22 80 0B 11 2E 00 01 01 00 00 20 20 1F 33 43 02 00 00 12 00 Tue 06/09/2015 06:23:02 PM : [Ext-Direct ] 1B.57.F8-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Hard to see how these messages could be confused.

Not with different devices. The Query response has the device Insteon address so physical device confusion is not possible. Only which node in the same physical device can be an issue because the Query response does not contain the node Group number. There was a FanLinc issue a few days ago for the same reason (wrong node Status changed). First time I had seen a situation where the FanLinc Query results triggered a Program because of the change in Fan Status because Light Status was applied to Fan node.

"If I goto the device itself Garage Door, and hit and On command, it will open. If I hit On again on the device itself, it will close the door. " This is normal operation for a Direct command. Only Scenes are affected/controlled by Momentary mode command rules. "When I goto the scene Garage Door Relay in the ISY and send an On command, it shows each device is turned On. But the Garage Door does not open." The I/O Linc Relay will either only Open the door with an On command or only Close the door with an On command when using Momentary C mode in combination with the Sensor Status. Suggest Open the garage door and send a Scene On command to see if I/O Linc relay is configured to Close door with On command.

The I/O Linc has two nodes, Sensor and Relay, each node must be queried individually. In this case the Sensor will report On with the door closed and of course the Relay will report Off. There are cases traced and posted where a Query response will be late arriving at the PLM such that the Relay Off Query response is applied to the Sensor Query. The Query response does not indicate which node it applies to. This can result in a Program being run because the door Status looks Open when the door is actually closed. Although it best to try and resolve the late message some users have found it easier to change magnetic switch such that the door Status is Off when door is closed. This way both Sensor and Relay report Off at 3AM so a late Query response does not produce unwanted action at 3AM. An event trace at 3AM when something unexpected occurs is needed to know what actually happened.

apostolakisl The comm issue may be other than no response to Query although the trace of Trigger Reverse does show a no response to the Extended command. The 3AM Query is a short Standard command and most likely is a delay in getting one of the Query responses back which can falsely indicate "door open" when it is actually closed. The trace does show Hops Left=0 messages so it is difficult to know without an actual trace at 3AM of a failure.

There is no dependency on a "direct link" for this example to work. The OP did not discuss how he should turn the Fan On. Fan could be a member of a Scene, could be the Responder to a Controller Only device such as RemoteLinc2 (Mini Remote), etc. Hopefully the OP will post back if there is a question on turning Fan On. Certainly worthy noting though.

That is a great point. I copied my hardware v1.B Heartbeat Program from another Program doing the same processing. It does not matter that a Heartbeat Off message will not occur. HeartbeatOCS3 - [iD 0090][Parent 0001] If Control 'OpenClose3-Opened / OpenClose3-Heartbeat' is switched On Or Control 'OpenClose3-Opened / OpenClose3-Heartbeat' is switched Off - does not occur at hardware v1.B Then Wait 25 hours Send X10 'A11/On (3)' Else - No Actions - (To add one, press 'Action')

The Heartbeat On occurred at 23 hours 51 minutes. Working well. I think for those who are using both Opened and Closed nodes at hardware v1.9 and earlier will be expecting that capability to continue with v1.B hardware.

I assume H is set to non-toggle Off mode so it is not illuminated. In non-toggle Off mode the button generates an off command when pressed.

Each time Motion Sensor senses motion the Wait starts over, waiting for 1 hour. When no motion for 1 hour wait completes and Fan is turned Off. If Control 'Motion Sensor - Sensor' is switched On Then Wait 1 hour Set 'FanLinc - Fan' Off Else

That may indicate a coupling problem as the AC is likely drawing 240v which would couple while AC is On.

I would check the Green LEDs. Comm to I/O Linc is varied. Some response has Hops Left=2, some have Hops Left=0. Mon 06/08/2015 08:20:03 PM : [iNST-TX-I1 ] 02 62 1A E8 CB 0F 11 FF Mon 06/08/2015 08:20:03 PM : [iNST-ACK ] 02 62 1A.E8.CB 0F 11 FF 06 LTONRR (FF) Mon 06/08/2015 08:20:03 PM : [All ] Writing 1 bytes to devices Mon 06/08/2015 08:20:03 PM : [iNST-TX-I2CS] 02 62 23 D2 F1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Mon 06/08/2015 08:20:03 PM : [iNST-SRX ] 02 50 1A.E8.CB 24.1C.B3 2B 11 FF LTONRR (FF) Mon 06/08/2015 08:20:03 PM : [std-Direct Ack] 1A.E8.CB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/08/2015 08:20:03 PM : [D2D EVENT ] Event [1A E8 CB 1] [sT] [255] uom=0 prec=-1 Mon 06/08/2015 08:20:03 PM : [ 1A E8 CB 1] ST 255 Mon 06/08/2015 08:20:03 PM : [iNST-ACK ] 02 62 23.D2.F1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Mon 06/08/2015 08:20:04 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 2B 2F 00 (00) Mon 06/08/2015 08:20:04 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/08/2015 08:20:04 PM : [iNST-ERX ] 02 51 23 D2 F1 24 1C B3 11 2F 00 01 01 0F FF 20 A2 00 24 1C B3 FF 1F 01 ED Mon 06/08/2015 08:20:04 PM : [Ext-Direct ] 23.D2.F1-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Mon 06/08/2015 08:20:04 PM : [23 D2 F1 1 ] Memory : Write dbAddr=0x4006 [0E] cmd1=0x20 cmd2=0x0E Mon 06/08/2015 08:20:04 PM : [iNST-TX-I2CS] 02 62 23 D2 F1 1F 20 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 06/08/2015 08:20:04 PM : [iNST-ACK ] 02 62 23.D2.F1 1F 20 0E 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (0E) Mon 06/08/2015 08:20:05 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 2B 20 0E (0E) Mon 06/08/2015 08:20:05 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/08/2015 08:20:05 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 23 20 0E (0E) Mon 06/08/2015 08:20:05 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Mon 06/08/2015 08:20:05 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 23 20 0E (0E) Mon 06/08/2015 08:20:05 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Mon 06/08/2015 08:20:13 PM : [iNST-TX-I1 ] 02 62 33 F1 0F 0F 11 FF Mon 06/08/2015 08:20:13 PM : [iNST-ACK ] 02 62 33.F1.0F 0F 11 FF 06 LTONRR (FF) Mon 06/08/2015 08:20:14 PM : [iNST-SRX ] 02 50 33.F1.0F 24.1C.B3 27 11 FF LTONRR (FF) Mon 06/08/2015 08:20:14 PM : [std-Direct Ack] 33.F1.0F-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Mon 06/08/2015 08:20:14 PM : [D2D EVENT ] Event [33 F1 F 1] [sT] [255] uom=0 prec=-1 Mon 06/08/2015 08:20:14 PM : [ 33 F1 F 1] ST 255 Mon 06/08/2015 08:20:18 PM : [All ] Writing 1 bytes to devices Mon 06/08/2015 08:20:18 PM : [iNST-TX-I2CS] 02 62 23 D2 F1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Mon 06/08/2015 08:20:18 PM : [iNST-ACK ] 02 62 23.D2.F1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Mon 06/08/2015 08:20:19 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 27 2F 00 (00) Mon 06/08/2015 08:20:19 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Mon 06/08/2015 08:20:19 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 23 2F 00 (00) Mon 06/08/2015 08:20:19 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Mon 06/08/2015 08:20:20 PM : [iNST-ERX ] 02 51 23 D2 F1 24 1C B3 11 2F 00 01 01 0F FF 20 A2 00 24 1C B3 FF 1F 01 ED Mon 06/08/2015 08:20:20 PM : [Ext-Direct ] 23.D2.F1-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Mon 06/08/2015 08:20:20 PM : [23 D2 F1 1 ] Memory : Write dbAddr=0x4006 [0F] cmd1=0x20 cmd2=0x0F Following command to turn Trigger Reverse Off got no Response. Mon 06/08/2015 08:20:20 PM : [iNST-TX-I2CS] 02 62 23 D2 F1 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 Mon 06/08/2015 08:20:20 PM : [iNST-ACK ] 02 62 23.D2.F1 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (0F) Mon 06/08/2015 08:20:23 PM : [iNST-TX-I1 ] 02 62 00 00 19 CF 11 00 Mon 06/08/2015 08:20:23 PM : [iNST-ACK ] 02 62 00.00.19 CF 11 00 06 LTONRR (00) Mon 06/08/2015 08:20:23 PM : [Ext MH ] Unexpected Ack imCmd=62 cmd1=LTONRR 0x11 Retry of command gets multiple responses Mon 06/08/2015 08:20:28 PM : [iNST-TX-I2CS] 02 62 23 D2 F1 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 Mon 06/08/2015 08:20:28 PM : [iNST-ACK ] 02 62 23.D2.F1 1F 20 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (0F) Mon 06/08/2015 08:20:28 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 2B 20 0F (0F) Mon 06/08/2015 08:20:28 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 06/08/2015 08:20:28 PM : [iNST-SRX ] 02 50 23.D2.F1 24.1C.B3 23 20 0F (0F) Mon 06/08/2015 08:20:28 PM : [std-Direct Ack] 23.D2.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Mon 06/08/2015 08:20:33 PM : [iNST-TX-I1 ] 02 62 23 FE FE 0F 11 FF Mon 06/08/2015 08:20:33 PM : [iNST-ACK ] 02 62 23.FE.FE 0F 11 FF 06 LTONRR (FF) Mon 06/08/2015 08:20:33 PM : [iNST-SRX ] 02 50 23.FE.FE 24.1C.B3 27 11 FF LTONRR (FF) Mon 06/08/2015 08:20:33 PM : [std-Direct Ack] 23.FE.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Mon 06/08/2015 08:20:33 PM : [D2D EVENT ] Event [23 FE FE 1] [sT] [255] uom=0 prec=-1 Mon 06/08/2015 08:20:33 PM : [ 23 FE FE 1] ST 255 I would expect retry to have worked and Trigger Reverse would be Off. Green LEDs should confirm.

That makes things more difficult to analyze. Put the PLM into Beacon made and see if all 5 Dual Band devices hear the PLM and note which ones are same 120v leg as PLM and which are on opposite 120v leg. What type thermostat?

They communicate over RF only. Check the Dual Band device the thermostat uses talks to the PLM.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Click on the I/O Linc Options button, set Trigger Reverse and click Done. Click I/O Linc Options button again, uncheck Trigger Reverse and click Done. Post event trace. Assuming using the same type magnetic switch, either the Options update was not successful before or the magnetic switch is not working correctly. Is the Green LED On on both I/O Lincs when door closed.

The Energy Display is not supported by the ISY so there is no ISY limit regarding those. The iMeter Solo has no dependencies on other devices so 1, 2, 3, 4, 5,... etc iMeter Solo devices should work okay. EDIT: I have 1 iMeter Solo installed under 3.3.1. It has no dependencies on other ISY known devices and works well.

The next Heartbeat On message came approx 23 hours 50 minutes after last Heartbeat message. I had done some testing with the magnet position and pressed the Set button a few times during that testing. This last Heartbeat message came nominally 24 hours after last Heartbeat message generated with Set button. It had an On command even though Open Close Sensor was now Open. Want to see one more Heartbeat message but feel certain it will be 24 hours (23 hours 50 minutes) after this last Heartbeat On message. This is so much better than dropping Heartbeat message at hardware v1.B.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device to add EZFlora and post event trace. I just added an EZFlora to 4.3.1. Don't think there were any changes added to 4.3.1 in this area. Also click Help | About and verify UI is 4.2.30.

I'll post what happens tomorrow evening as that will be a more normal 24 hour period. It adds as a 2421 TriggerLinc. Firmware is v.43 Closed node does not populate. The documentation for the v1.B indicates the Closed node is now controlled/activated by software since the Jumper no longer exists. This will require some new function by the ISY.

The v1.B Open Close Sensor sent Heartbeat On message, Group 4, On command. Sat 06/06/2015 07:25:00 PM : [ Time] 19:25:00 1(0) Sat 06/06/2015 07:29:36 PM : [ Time] 19:29:39 1(0) Sat 06/06/2015 07:39:36 PM : [ Time] 19:39:39 1(0) Sat 06/06/2015 07:40:35 PM : [ Time] 19:40:38 1(0) Sat 06/06/2015 07:50:35 PM : [ Time] 19:50:38 1(0) Sat 06/06/2015 07:53:03 PM : [iNST-SRX ] 02 50 36.ED.98 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 07:53:03 PM : [std-Group ] 36.ED.98-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 07:53:03 PM : [D2D EVENT ] Event [36 ED 98 4] [DON] [4] uom=0 prec=-1 Sat 06/06/2015 07:53:03 PM : [ 36 ED 98 4] DON 4 Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 07:53:04 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 22.80.0B 41 11 04 LTONRR (04) Sat 06/06/2015 07:53:04 PM : [std-Cleanup ] 36.ED.98-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Sat 06/06/2015 07:53:04 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 11.01.04 CB 06 00 (00) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->11.01.04, Max Hops=3, Hops Left=2 Sat 06/06/2015 07:53:04 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 11.01.04 C3 06 00 (00) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->11.01.04, Max Hops=3, Hops Left=0 Sat 06/06/2015 07:53:04 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 07:53:04 PM : [iNST-SRX ] 02 50 36.ED.98 11.01.04 C3 06 00 (00) Sat 06/06/2015 07:53:04 PM : [std-Group ] 36.ED.98-->11.01.04, Max Hops=3, Hops Left=0 Sat 06/06/2015 07:53:04 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 07:55:35 PM : [ Time] 19:55:39 1(0) Sat 06/06/2015 07:59:59 PM : [ Time] 20:00:00 1(0) Sat 06/06/2015 08:09:59 PM : [ Time] 20:09:59 1(0) Sat 06/06/2015 08:12:47 PM : [iNST-SRX ] 02 50 2C.71.C2 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 08:12:47 PM : [std-Group ] 2C.71.C2-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:47 PM : [D2D EVENT ] Event [2C 71 C2 4] [DON] [4] uom=0 prec=-1 Sat 06/06/2015 08:12:47 PM : [ 2C 71 C2 4] DON 4 Sat 06/06/2015 08:12:47 PM : [iNST-SRX ] 02 50 2C.71.C2 00.00.04 CB 11 04 LTONRR (04) Sat 06/06/2015 08:12:47 PM : [std-Group ] 2C.71.C2-->Group=4, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:47 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 08:12:47 PM : [iNST-SRX ] 02 50 2C.71.C2 22.80.0B 41 11 04 LTONRR (04) Sat 06/06/2015 08:12:47 PM : [std-Cleanup ] 2C.71.C2-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Sat 06/06/2015 08:12:47 PM : [iNST-DUP ] Previous message ignored. Sat 06/06/2015 08:12:48 PM : [iNST-SRX ] 02 50 2C.71.C2 11.01.04 CB 06 00 (00) Sat 06/06/2015 08:12:48 PM : [std-Group ] 2C.71.C2-->11.01.04, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:48 PM : [iNST-INFO ] Previous message ignored. Sat 06/06/2015 08:12:48 PM : [iNST-SRX ] 02 50 2C.71.C2 11.01.04 CB 06 00 (00) Sat 06/06/2015 08:12:48 PM : [std-Group ] 2C.71.C2-->11.01.04, Max Hops=3, Hops Left=2 Sat 06/06/2015 08:12:48 PM : [iNST-INFO ] Previous message ignored.

I did get a Heartbeat when I installed the v1.B, with an On command even though the Open Close Sensor was closed. May have been when I pressed the Set button as it was powered for only a few minutes. Sending an On command seemed consistent with what had been posted. It will be another 5 hours +/- before getting the 24 hour Heartbeat message. The Open Close Sensor is near a Dual Band device so I am expecting to see the heartbeat message if the device generates one. Program is HeartbeatOCS3