LeeG

MustangChris04 The Range Extender was not much more than a guess. Unfortunately a Query response does not carry the node Group number so there is nothing in the Query response that allows knowing which node (Light or Fan) the response applies to. I know from experience that the 0xBF On Level applies to the Fan, along with not expecting to see the Light on at that level at 3AM. Evaluating two Query response messages separated by outbound messages is not the type of analysis the ISY could do to any given Query response by itself. This has to do with the PLM receiving multiple copies of the same message through different paths (with different Hops Left counts) and presenting both to the ISY as unique messages rather than understanding they are same message coming at different times. Fri 06/05/2015 03:00:48 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 27 00 00 (00) - Light Off response Fri 06/05/2015 03:00:48 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/05/2015 03:00:48 AM : [iNST-TX-I1 ] 02 62 23 10 66 0F 19 03 - Query of Fan Fri 06/05/2015 03:00:48 AM : [iNST-ACK ] 02 62 23.10.66 0F 19 03 06 LTSREQ (03) Fri 06/05/2015 03:00:48 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 23 00 00 (00) - duplicate Light Off response applied to Fan Query Fri 06/05/2015 03:00:48 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 It may be possible to avoid this network failure by slowing down Insteon traffic. I don't know and I'm very uncomfortable with the ISY getting into a practice of trying to compensate for every network problem that exists. Also note that these duplicate Query messages did NOT turn Off the Fan. Some Program logic decided to turn off Fan.

The Insteon network is generating extra Query response messages. The Query of the Light (which is Off) is generating an extra message that looks like the response to the following Fan Query. The Fan is set for Med speed but the duplicate Light Off response from Light makes it look like Fan is Off. Fri 06/05/2015 03:00:48 AM : [iNST-TX-I1 ] 02 62 23 10 66 0F 19 00 - Query of Light Fri 06/05/2015 03:00:48 AM : [iNST-ACK ] 02 62 23.10.66 0F 19 00 06 LTSREQ (LIGHT) Fri 06/05/2015 03:00:48 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 27 00 00 (00) - Light Off response Fri 06/05/2015 03:00:48 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/05/2015 03:00:48 AM : [iNST-TX-I1 ] 02 62 23 10 66 0F 19 03 - Query of Fan Fri 06/05/2015 03:00:48 AM : [iNST-ACK ] 02 62 23.10.66 0F 19 03 06 LTSREQ (03) Fri 06/05/2015 03:00:48 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 23 00 00 (00) - duplicate Light Off response applied to Fan Query Fri 06/05/2015 03:00:48 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/05/2015 03:00:48 AM : [iNST-TX-I1 ] 02 62 23 10 66 0F 19 00 Fri 06/05/2015 03:00:49 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 27 19 BF LTSREQ (BF) - actual Fan Med response Fri 06/05/2015 03:00:49 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/05/2015 03:00:49 AM : [iNST-ACK ] 02 62 23.10.66 0F 19 00 06 LTSREQ (LIGHT) Fri 06/05/2015 03:00:49 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 27 00 00 (00) Fri 06/05/2015 03:00:49 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 This Fan Query worked as expected, showing Med speed Fri 06/05/2015 03:00:49 AM : [iNST-TX-I1 ] 02 62 23 10 66 0F 19 03 Fri 06/05/2015 03:00:49 AM : [iNST-ACK ] 02 62 23.10.66 0F 19 03 06 LTSREQ (03) Fri 06/05/2015 03:00:50 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 27 19 BF LTSREQ (BF) Fri 06/05/2015 03:00:50 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/05/2015 03:00:50 AM : [iNST-TX-I1 ] 02 62 26 4B 2D 0F 19 00 Fri 06/05/2015 03:00:50 AM : [iNST-ACK ] 02 62 26.4B.2D 0F 19 00 06 LTSREQ (LIGHT) This is duplicate Fan Query response Fri 06/05/2015 03:00:50 AM : [iNST-SRX ] 02 50 23.10.66 2B.95.60 23 19 BF LTSREQ (BF) Fri 06/05/2015 03:00:50 AM : [std-Direct Ack] 23.10.66-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 You can try an addition Range Extender near FanLinc and/or deal with the duplicate response messages in the Programming.

My new V1.B hardware Open Close Sensor under test. Will update as test results obtained.

espann I know nothing about Mobilinc but the ability for ISY to Enable Internet Access is dependent on the Router being setup for UPnP. Only if the File | Enable Internet Access is successful will that option be replaced with a Disable Internet Access option. It sounds like the Router is not enabled for UPnP.

The RemoteLinc is not responding to some commands. The ISY will try three times and if all fail the update stops. The line marked in Red got no response from RemoreLinc. I have not seen this locally with my RemoteLinc but some users have indicated a better experience with the old RemoteLinc when it is further away from Dual Band device. Seems like the signal strength can overload a Dual Band device when updates are done with the RemoteLinc near a Dual Band device. Wed 06/03/2015 09:24:01 PM : [11 C3 68 1 ] Link 0 : 0FF8 [E20130E715010001] Writing [E20130E715010001] Wed 06/03/2015 09:24:01 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:01 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:01 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 28 0F SET-MSB(0F) Wed 06/03/2015 09:24:01 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:01 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 2B F8 Wed 06/03/2015 09:24:01 PM : [iNST-ACK ] 02 62 11.C3.68 0F 2B F8 06 PEEK (F8) Wed 06/03/2015 09:24:03 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 2B E2 PEEK (E2) Wed 06/03/2015 09:24:03 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:03 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:03 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:12 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:12 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:21 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:21 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:24 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 28 0F SET-MSB(0F) Wed 06/03/2015 09:24:24 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:24 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 2B F9 Wed 06/03/2015 09:24:24 PM : [iNST-ACK ] 02 62 11.C3.68 0F 2B F9 06 PEEK (F9) Wed 06/03/2015 09:24:26 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 2B 01 PEEK (01) Wed 06/03/2015 09:24:26 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:26 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:26 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:35 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:35 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:44 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:44 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:48 PM : [11 C3 68 1 ] Link 0 : 0FF8 [E20130E715010001] *Failed Writing [E20130E715010001]

My v1.9 Open Close Sensor Heartbeat tonight sent an ON command just like last night because I left the Open Close Sensor Open. Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.04 CB 11 04 LTONRR (04) - 0X11 On command from Heartbeat node Wed 06/03/2015 06:42:13 PM : [std-Group ] 31.C1.1D-->Group=4, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:13 PM : [D2D EVENT ] Event [31 C1 1D 4] [DON] [4] uom=0 prec=-1 Wed 06/03/2015 06:42:13 PM : [ 31 C1 1D 4] DON 4 Wed 06/03/2015 06:42:13 PM : [D2D-CMP 0071] CTL [31 C1 1D 4] DON op=1 Event(val=4 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.04 CB 11 04 LTONRR (04) Wed 06/03/2015 06:42:13 PM : [std-Group ] 31.C1.1D-->Group=4, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:13 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:42:13 PM : [iNST-SRX ] 02 50 31.C1.1D 22.80.0B 41 11 04 LTONRR (04) Wed 06/03/2015 06:42:13 PM : [std-Cleanup ] 31.C1.1D-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Wed 06/03/2015 06:42:13 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:42:14 PM : [iNST-SRX ] 02 50 31.C1.1D 11.01.04 CB 06 00 (00) Wed 06/03/2015 06:42:14 PM : [std-Group ] 31.C1.1D-->11.01.04, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:14 PM : [iNST-INFO ] Previous message ignored. Wed 06/03/2015 06:42:14 PM : [iNST-SRX ] 02 50 31.C1.1D 11.01.04 CB 06 00 (00) Wed 06/03/2015 06:42:14 PM : [std-Group ] 31.C1.1D-->11.01.04, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:42:14 PM : [iNST-INFO ] Previous message ignored. Wed 06/03/2015 06:52:13 PM : [ Time] 18:52:15 16(0) I set the Open Close Sensor to Closed after Heartbeat On message to test Heartbeat command sent tomorrow night. I'm expecting an Off command to match Open Close Sensor state Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.01 CB 13 01 LTOFFRR(01) Wed 06/03/2015 06:56:34 PM : [std-Group ] 31.C1.1D-->Group=1, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:56:34 PM : [D2D EVENT ] Event [31 C1 1D 1] [DOF] [1] uom=0 prec=-1 Wed 06/03/2015 06:56:34 PM : [ 31 C1 1D 1] DOF 1 Wed 06/03/2015 06:56:34 PM : [D2D EVENT ] Event [31 C1 1D 1] [sT] [0] uom=0 prec=-1 Wed 06/03/2015 06:56:34 PM : [ 31 C1 1D 1] ST 0 Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 00.00.01 CB 13 01 LTOFFRR(01) Wed 06/03/2015 06:56:34 PM : [std-Group ] 31.C1.1D-->Group=1, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:56:34 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 22.80.0B 41 13 01 LTOFFRR(01) Wed 06/03/2015 06:56:34 PM : [std-Cleanup ] 31.C1.1D-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Wed 06/03/2015 06:56:34 PM : [iNST-DUP ] Previous message ignored. Wed 06/03/2015 06:56:34 PM : [iNST-SRX ] 02 50 31.C1.1D 13.01.01 CB 06 00 (00) Wed 06/03/2015 06:56:34 PM : [std-Group ] 31.C1.1D-->13.01.01, Max Hops=3, Hops Left=2 Wed 06/03/2015 06:56:34 PM : [iNST-INFO ] Previous message ignored.

bipto The Heartbeat message is still there at v1.B according to what Smarthome told Techman. Of course this is not the same information UDI was told. I have 2 v1.B Open Close sensors coming from Smarthome. I'll run the same Heartbeat Program logic using one of the new Open Close Sensors and see what actually happens.

If the PLM is losing link records the ISY can turn the device On and Off (does not use link records) but can lose ability for device to send state change messages (when button or paddle pressed) back to the PLM. Same will happen if device loses link records. A Restore Device will restore device link database. A File | Restore Modem (PLM) will rebuild PLM link database.

Heartbeat On received at 06:51 PM. Will Leave Open Close Sensor Open to see what the v1.9 generates for command at Wed Heartbeat. The ISY Log will show the Heartbeat message status (On or Off) only if the value is different from the last Heartbeat Log entry. The ISY Log does not show repeated On or repeated Off commands.

steadler Sorry but the Jumper is not specific to the use of an external sensor. The Jumper being removed activates the 2nd node , Closed, which has nothing to do with whether the external sensor is used.

bipto Can you expand on what "hung" is. If the Open Close Sensor fails to send a Heartbeat within 25 hours the Program indicates a problem.

My Heartbeat Programs do not require the Heartbeat command to cycle between On and Off. If the Open Close Sensor remains in the same state the same Heartbeat command will be sent. The Heartbeat Program refreshes the 25 hour Wait regardless of Heartbeat command received. The Program checks for either command so it does not matter whether the Open Close Sensor is in the Open or Close state at Heartbeat time. EDIT: sorry larryllix, had not read your post when I responded to Techman. You had already covered the item.

The Heartbeat node at v1.9 sends an On or Off command based on the state of the Opened node (at least as I remember it). There are so many devices I have worked with a Heartbeat node I could be wrong. My v1.9 has not yet triggered my monitor Program. With it on a 24 hr cycle it could be several more hours. To monitor the Heartbeat node requires a Program. You can have the Open/Close Sensor reflect an Open condition, have a Heartbeat message, change the Open/Close Sensor to Close and the wait for the next heartbeat message. That is more work than I want to do. Looking at the Heartbeat Program information or have it send a message is much easier. I ordered 2 Open/Close Sensors last night (Eastern time). It should ship tonight (Tuesday) with 4 day travel time.

Techman I had this Program Disabled for some other tests. This is how I monitor Heartbeat at v1.9 hardware. I Enabled the Program but it may take 24 hours to confirm the v1.9 Heartbeat is functional. Of course you have v1.B hardware so this type Program is of no use based on Michel's last post. Multi Scene is simply linking a Scene to the Opened node and the Closed node. Something the ISY has always been able to do. Not sure how the Closed node is activated at v1.B without the physical Jumper. I've ordered 2 Open/Close Sensors which should give me a v1.B to test. HeartbeatOCS1 - [iD 0071][Parent 0001] If Control 'OpenClose1-Opened / OpenClose1-Heartbeat' is switched On Or Control 'OpenClose1-Opened / OpenClose1-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A11/On (3)' Else - No Actions - (To add one, press 'Action')

Michel answered the question in post #3. The light is not turned Off. The Program is terminated when the Folder turns False so the "Set 'light' Off is not executed.

Just found an additional User Manual added for 2843-222 that is specific to devices without the Jumper.

The 2843-222 Open/Close Sensor adds as a TriggerLinc. The Heartbeat node does not alternate On/Off. The state of the Heartbeat is based on the state of the Opened node when the Heartbeat happens. My 2843-222 devices are hardware v1.9 which has a Jumper inside that can be removed to activate the Closed node. Users have posted the v1.B hardware variant no longer has a removable Jumper to activate the Closed node.

There is no wrong connection possible to GND/S and the magnetic sensor. I would check the wires between the magnetic switch and the I/O Linc. With the Green LED On all the time with the wires connected there sounds like a short in the wiring. Could be a defective shorted magnetic switch but that is low on the list of possibilities. Disconnect the wires from the switch when the magnet is not near the switch. If The Green LED remains On there is a short in the wires. If the Green LED goes out when the wires are disconnected from switch and magnet is not near switch the switch has a problem.

As was posted earlier the Sensor (Green LED) is not affected by Latching/Momentary modes. These affect the Relay operation only. The Green LED does not turn On or Off as the door moves from close to open position? Whether the Green LED is On or Off when the door is closed depends on the type of magnetic switch being used. If using the magnetic switch that came with the garage kit the Green LED (Sensor) should be On when door is closed and turn Off as the magnet moves away from the magnetic switch as the door opens. If this is not what happens to the Green LED the magnetic switch is not connected to GND and Sensor or the switch is not mounted correctly or the switch is defective. As was suggested remove the switch connections to GND/S and short GND to S to see if Green LED turned On.

First, never change the I/O Linc options with the Set button. Always use the Options button on the I/O Linc node display using Admin Console. Click the Options button and the Query button on the Options popup to see what options are actually set. When you refer to "status" light are you referring to the Green LED next to the wire connections or the White LED next to the Set button.

Without details about the specifics it is difficult to suggest a solution. REST can turn On/Off a Scene which turns On/Off devices which can trigger a Program using "If Status".

Yes. First install 4.2.30 to get to latest Official release. Clear the Java cache and installed apps. Use 4.a to install 4.2.30 Admin Console and create Icon on Desktop to invoke Admin Console without needing Chrome.

There was likely a link record(s) missing in the KPL or the PLM. Insteon must find a Controller link (E2 xx aa.bb.cc ........) in the KPL for the specific button (xx) and with the PLM Insteon address (aa.bb.cc) for it to send a message to the PLM. The PLM must have a matching Responder link (A2 xx dd.ee.ff .......) that matches where (xx) is the KPL button number and dd.ee.ff is the KPL Insteon address. When "If Status" will trigger a Program then "If Control" should also unless there are other If statements that would be False when the On message is received. This combination does not work with "If Control" as the On message is not being received at exactly 7AM If Control 'kplbutton' is switched 100% And Time is 7:00:00AM That is why posting the real Program statements that have been Copy to Clipboard is so important.

Look at the PLM link table to see if Responder links (A2 .. . .. .. .. .. ..) for KPL and RemoteLinc2 are missing.

From the 4.2.30 announcement Important Notes - Due to a major SSLv3 vulnerability (POODLE), all SSLv3 functionality is disabled. On the 994i series, TLS1.1 is now the default protocol. On PRO series, you can choose up to TLS 1.2.