KPL, IOlinc, and other communication errors

[backinthelab]

Previously posted in the Updates section....

 

- KPL buttons on one of three KPL's have stopped responding to other Insteon devices, but respond to Elk. UPDATE: After attempting an restore, writing updates, then finally removing the KPL entirely, pulling the air gap, I cannot bring the device back in. While trying to add it via the Admin console I get a "Node not added - failed removing links" error (-200000/-9).

- Scene on levels and ramp rates will not take when scene is selected. I'm getting "Error: Request Failed" when attempting to adjust. They don't save when I return to the scene.

- Communication issue with garage door IOLinc, status "ON" does not change unless I force a query, however "OFF" changes when it's activated.

- A new one! Motion sensor links are not updating. I've re-written links while it was in linking mode, however, it still turns on devices it used to be controlling. I've updated these devices but the issue remains.

- Another new one! A Switchlinc that controls a fan immediately switches Off when turned on manually. If I turn on via Admin Console, it stays on.

 

LeeG's response with my comments in blue:

Lets go through these a few at a time.

 

The I/O Linc Sensor changing from OFF to ON but not ON to OFF is odd. Does your configuration run with the I/O Linc Trigger Reverse option set? No, Trigger Reverse isn't checkedIs the actual I/O Linc Sensor (green LED on front of I/O Linc) On or Off when door is closed? LED is illuminated when both sensor and activation status is Off.

 

The Scene On Level/Ramp Rate change causing "Error: Request Failed", would you please expand on how the Scene values are being changed. Through the Admin Console, with the Adjust Scene Program function, etc. Run Tools | Diagnostics | Event Viewer with Device communications events selected (important), attempt the Scene changes (however done) and post the Event Log.

Here's the event log, I went back a couple of events earlier, as it appears odd...

Sat 08/13/2011 08:27:17 PM : [iNST-SRX    ] 02 50 0A.59.61 12.9F.9A 23 11 FF    LTONRR (FF)
Sat 08/13/2011 08:27:17 PM : [standard-Direct Ack][0A.59.61-->ISY/PLM Group=0] Max Hops=3, Hops Left=0
Sat 08/13/2011 08:27:17 PM : [   A 59 61 1]       ST 255
Sat 08/13/2011 08:27:17 PM : [iNST-ACK    ] 02 62 00.00.25 CF 11 00 06          LTONRR (00)
Sat 08/13/2011 08:27:17 PM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTONRR 0x11
Sat 08/13/2011 08:27:22 PM : [iNST-ACK    ] 02 62 11.A9.02 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)
Sat 08/13/2011 08:27:31 PM : [iNST-ACK    ] 02 62 11.A9.02 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)
Sat 08/13/2011 08:27:33 PM : [iNST-ACK    ] 02 62 00.00.18 CF 13 00 06          LTOFFRR(00)
Sat 08/13/2011 08:27:33 PM : [Ext. Msg. Handler] Unexpected Ack imCmd=62 cmd1=LTOFFRR 0x13
Sat 08/13/2011 08:27:33 PM : [11 A9 2 1   ] Link    0 : 0FF8 [E201129F9AFF1F01] *Failed Writing [E201129F9AFF1F01]
Sat 08/13/2011 08:27:33 PM : [All         ] Writing 0 bytes to devices

 

Lee and anyone else on the forum, thank you in advance for ANY help you might be able to provide. This is some weird stuff that I've never seen before! I'm contemplating a factory reset of everything and spending my Sunday rebuilding, unless I can avoid that mess.

[LeeG]

The ISY is using Extended commands to update the Scene information. That is somewhat unusual for most devices. What type of device and firmware level is the device that is having the Scene information updated.

 

Also, check Link Management | Advanced Options and make sure the Automatic option is selected.

[backinthelab]

It does this with any device when adjusted from within a scene. In that instance, it was a Switchlinc. It's now lost communication with a motion sensor and a triggerlinc. Nonetheless, I did confirm that the automatic mode was set in Advanced Options.

[LeeG]

Sorry, I am not able to provide any direction with the information provided.

[backinthelab]

Is there any info I can provide that might help me to avoid a master reset of the whole system? If not, does anyone have a method to ease the pain, particularly in relation to programs? Is there a way I can export a list of current programs to reference when rebuilding? I have a few more device on their way and would rather have a stabile platform to add them to. So, if wiping the ISY and PLM is my best bet, I'll roll up the sleeves and do it.

[backinthelab]

Problem solved*! I hope I'm not posting this prematurely, however, I'm making headway without wiping out the entire system. I've successfully re-added the KPL that has been problematic and it's now responding and controlling how it's supposed to (like it was before). I still have a bit to go, but here are the steps I took to get to this point:

 

1. Cleared my Java cache and restarted the jnlp app.

2. Disabled all programs that had anything to do with the KPL, motion sensors, and triggerlincs.

3. Disabled all motion sensors and triggerlincs.

4. Ran "Restore Devices"

5. Tried to use "Add New Insteon Device" option with the KPL's address. It failed, so I used the "Start Linking" option and put the KPL in linking mode. This worked.

6. Enabled KPL programs and added to appropriate scenes.

 

Now, I have no idea how to translate the event logs so I can only go by operating results. So far so good. My next step is to enable the sensors one-by-one to see if we have a bad apple in here somewhere.

 

Out of the issues posted above, some remain due to the fact that I have not yet updated the ISY firmware. Those that aren't going to be cured by the update include:

 

- Garage IOLinc refusing to update status to OFF

- Scene adjustments still not working. I just verified this by trying to adjust the ramp rate on scene containing two Switchlinc Dimmers. I now get a "Failed initializing node - continuing" (-200000/-7) and "Could not open file" (/log/a.log).

 

So, down to a couple of problems, but progress is GOOD!

[backinthelab]

Tried another scene with the event viewer running. This scene contains a KPL v.29, Lamplinc v.37, and (2) Switchlinc Dimmers v.37. I clicked "Apply Changes to All Devices", then moved the ramp rate. Here's what the Event Viewer had to say:

 

Mon 08/15/2011 07:13:51 PM : [7 F3 1A 1   ] Link   13 : 0F90 [A214129F9AFF1F01] Saving  [............1F..]
Mon 08/15/2011 07:13:52 PM : [All         ] Writing 1 bytes to devices
Mon 08/15/2011 07:13:52 PM : [7 F3 1A 1   ] Using engine version i1 for 'Family Room'
Mon 08/15/2011 07:13:52 PM : [7 F3 1A 1   ] Link   13 : 0F90 [A214129F9AFF1F01] Writing [............1F..]
Mon 08/15/2011 07:13:52 PM : [iNST-ACK    ] 02 62 07.F3.1A 0F 28 0F 06          SET-MSB(0F)
Mon 08/15/2011 07:13:52 PM : [iNST-SRX    ] 02 50 07.F3.1A 12.9F.9A 2B 28 0F    SET-MSB(0F)
Mon 08/15/2011 07:13:52 PM : [standard-Direct Ack][07.F3.1A-->ISY/PLM Group=0] Max Hops=3, Hops Left=2
Mon 08/15/2011 07:13:52 PM : [iNST-ACK    ] 02 62 07.F3.1A 0F 2B 96 06          PEEK   (96)
Mon 08/15/2011 07:13:52 PM : [iNST-SRX    ] 02 50 07.F3.1A 12.9F.9A 2B 2B 1F    PEEK   (1F)
Mon 08/15/2011 07:13:52 PM : [standard-Direct Ack][07.F3.1A-->ISY/PLM Group=0] Max Hops=3, Hops Left=2
Mon 08/15/2011 07:13:53 PM : [All         ] Writing 0 bytes to devices
Mon 08/15/2011 07:13:53 PM : [All         ] Writing 0 bytes to devices
Mon 08/15/2011 07:13:53 PM : [All         ] Writing 0 bytes to devices

 

Anybody know what's going on here?

[LeeG]

Device 07.F3.1A had its responder link record for Scene 14 Ramp Rate set to 1F which is the fastest ramp rate. The ISY changes only those devices where a Ramp Rate applies (KPL Secondary buttons do not Ramp so they are not updated) and where it believes the existing Ramp Rate is different than the new value.