ISY Link table corrupted - how to edit?

[dburtis2]

Version 2.8.16 (Win 7 x64 with Chrome browser, all via wired local network) - I have tried twice to replace an old KPL with a new one and I have found the ISY link table for one of the lamplincs controlled by the KPL still has the old KPL address (even after an ISY restore between the two attempts). (By the way, that is not the only device with old KPL address - just an easy one to work with). I tried saving ISY link table for that device, editing the offending addresses (in Dreamweaver) to point to the already discovered new KPL, and loading it back to ISY. However, when I restored the lamplinc, ISY deleted the four links with the old KPL address and the new KPL address then wrote the ISY-changed (shortened) link table to the device.

 

1. Why doesn't my external edit work? (it showed up ok - with proper hex address - in the ISY link window until I did the restore device)

2. Is there another way to edit a bad ISY link short of a complete system rebuild? (Is there a bug in Load/Save for the link windows)?

 

I also looked for some way of reading and writing files from the telnet interface (but can only list them and can't tell which file has the links in any case).

 

Help, so far I've spent two days on this problem (a lot of that time searching through the manual, Wiki, and forum -- no mention of Load and Save for the link display windows). What can I do to solve this?

 

(Other than this frustration, I love ISY 99. It is much much better than Houselinc which I've been using for the past 4 years. Now if only I could bring up admin window on iPad...)

 

Don Burtis

[LeeG]

Did you issue the Replace xxx with …. against the old KeypadLinc node or the new KeypadLinc node. It sounds like the Replace was done against the wrong node.

[dburtis2]

Did you issue the Replace xxx with …. against the old KeypadLinc node or the new KeypadLinc node. It sounds like the Replace was done against the wrong node.

 

No, I did replace it using the "replace xxxx with..." after moving the old KPL out of the folder it was in. I'm certain I selected the correct device because ISY won't let you select the same device for replacement (and the wrong addresses in the links were from the old KPL).

 

I should have added a little more detail. The only way I could get the lamplinc to work with the new KPL was to take it out of the scenes and put it back in. Tedious for all the devices linked to the KPL, but that worked - however it did not remove the link with the old KPL address. This morning I discovered I could take advantage of the undocumented editing done by ISY when it restores a device. Sure enough, restoring the lamplinc (after getting it linked properly to the KPL via removal/reinsertion to each KPL scene) removed the links that contained the old KPL address.

 

I wish I had known that yesterday morning - I would have realized that doing a "whole house" restore would clean up any left-over old addresses. (Still not understanding why that would be necessary).

 

I also discovered this morning that a recent power outage may have be one (the only?) cause of some of the replacement issue. I discovered on old KPL had stopped responding (and had no LEDs lit). I did a reset (by error in timing it turned out to be a factory reset) and (because it was a factory reset) did a device restore. Seeing that triggered my memory about an entry I read on this forum about access points locking up from a power outage, so I interrupted power on each access point to reset it.

 

I'd still like to know why the save-edit-load didn't work on the ISY link table for the device. Sounds like either a bug or a misunderstood (and apparently undocumented) feature. If load doesn't change the internal ISY link table, why does it exist on the ISY link screen?

 

Don Burtis

[LeeG]

Issuing a Replace xxxx with against the old KeypadLinc should have resulted in all the affected link records being updated and the new KeypadLinc definition being removed. There may have been Green Icons next to some of the nodes indicating pending updates because communication problems existed for the reasons you described.

 

I'm not familiar with Load/Save as the ISY is very good at managing link records. You are the only person I can remember trying to manually change link records. Restore Device and/or Restore Modem (PLM) normally resolve link record problems. I'll see what I can determine through some testing on this end.

[dburtis2]

Issuing a Replace xxxx with against the old KeypadLinc should have resulted in all the affected link records being updated and the new KeypadLinc definition being removed. There may have been Green Icons next to some of the nodes indicating pending updates because communication problems existed for the reasons you described.

 

I'm not familiar with Load/Save as the ISY is very good at managing link records. You are the only person I can remember trying to manually change link records. Restore Device and/or Restore Modem (PLM) normally resolve link record problems. I'll see what I can determine through some testing on this end.

 

Thanks for your prompt reply. I was careful to let all of the writing (green icons) complete before attempting to look at the link tables. I agree ISY does a great job managing the links, but with any product that relies on conditions beyond its control (namely good communications with the devices), some errors can and will find their way in. It seemed to me that it would be logical to just change (or remove) a bad link address instead of resorting to other, more drastic and time-consuming, measures.

 

In my case, I have about 75 Insteon devices and starting over from scratch is a daunting prospect. I'd be more inclined to consider that if ISY produced a nice report that could be used as a script to walk me through a "re-do". The html ("Generate Topology") is a good start, but it doesn't contain the ramp rates and levels for scenes, and doesn't contain the programs. Don't misinterpret my comments - I think the product is great (but could be improved with better documentation -- again: why is there a "load" button on the link displays and what is it supposed to do?).

 

Don Burtis

[Michel Kohanim]

Mr. Burtis,

 

ISY keeps a running tab of where it stopped during any operation and that's the reason for green 01010 icons (pending operations).

 

Updating link records in ISY manually might cause your system to crash.

 

With kind regards,

Michel

[fitzpatri8]

I didn't see Lee recommend you start over from scratch, just to restore the link tables of the PLM and the affected device.

 

There's never a need to just 'accept' poor signals with Insteon gear--the ISY includes a scene test feature to help you identify specifically where signals are challenged, then you can choose which path you take. You likely have one or more poor wiring connections (which you'd want to resolve anyway to avoid arcing and a potential fire hazard), other lighting gear or appliances bleeding noise onto the power line, or electronics or surge suppressors that are swallowing up enough of the signals passing by that equipment downstream can't hear the signals. You can temporarily disconnect noisy or signal-absorbing devices while editing device link tables, you can permanently isolate obnoxious equipment with readily-available noise filters, and you can boost signals on far-flung circuits in a large home by adding another dual-band LampLinc, SwitchLinc or Access Point. Both inline and module-style filters are available, and the older x10-style filters are remarkably inexpensive when purchased in bulk.