If I remember correctly, group FE is a special Indigo PowerLinc group that is sometimes used to get a remote module out of linking mode. You can either just ignore that link, or manually delete it if you want.

Try first opening the Interface Options dialog (in the Prefs dialog) and press the button to Clear Links button. Then shut down the Indigo Server, manually delete the XML links (looks like you are deleting the correct structures), and relaunch Indigo then ReSync the PowerLinc links (via Interface Options). I think the problem is that the links are both in the PowerLinc and Indigo's database, and you need to clear them both or they get re-synced back into existence.

Matt,

Extract from my database file - 1290060 is the binary of the controller I am presently using, are the others older ones I've had in the past?

<PowerLincAddressList type="vector">
<Address type="string">392669</Address>
<Address type="string">1290060</Address>
<Address type="string">791635521</Address>
</PowerLincAddressList>
<PowerLincAddressActive type="string">1290060</PowerLincAddressActive>

Yes. Indigo tracks them so that it can automatically rewrite remote links with the new PowerLinc address when it encounters an old address. This makes swapping out an old PowerLinc easier since Indigo will automatically fix the links in the remote modules so they aren't stale (pointing to an unused PowerLinc).

Matt,

I'm back to my old problem in using an EZX10RF, I use the Simplehomenet Utility to write links in the EZ and then to the PLM. My problem is if I do a sync with Indigo then since the links are not in the Indigo database they get removed from the PLM as the syncing appears to write over the PLM with only what is in the Indigo database.

So I was wondering if it'spossible to manually write the links in the Database file so would they would be written to the PLM after a sync? If so if I sent you the 6 lincs as written in the PLM would you be able to show me the format to write them into the Indigo Database?

thanks,

bob

P.S. Thanks for your note regarding the EasyDaq relays showing up as devices.

Did the clean up links provision Matt mentioned a couple of posts ago ever get implemented? If not, is it still on todo list?

I don't know, I was of the understanding it wasn't considered necessary althought I still do it. When I do a read of the links I see lots of crap so I remove it manually.

bob wrote:My problem is if I do a sync with Indigo then since the links are not in the Indigo database they get removed from the PLM as the syncing appears to write over the PLM with only what is in the Indigo database.

I don't believe it should do that. Try the following:

1) Open the Interface Options dialog from the Prefs dialog.

2) Press the Sync Links button.

3) Use the SimpleHomeNet utility to add the PowerLinc links you want to the EZX10RF.

4) Connect the PowerLinc back up to Indigo, and press the Read Links button (again from the Interface Options dialog)

5) Next, press the Sync Links button.

6) Lastly, copy/paste the Event Log showing the results of step #2, #4, and #5.

Matt,

After I clean up the Indigo database file I reset the PLM to get rid of the old and unused links and then write to a clean PLM. This obviously removes all existing links in the PLM so after resyncing I have to manually add the EZX10RF links back to the PLM. If I had a template to add my EZX10RF links to the Indigo database file, they would get written to the PLM when I did a sync. Since you are not going to add linking for the EZX10RF in 5, I thought this work around would work just as well for me.

Follow my steps above and let me know what it shows (step #6).

Also, after you have done step #5 open the Link Editor dialog in Indigo for the PowerLinc. Are the links there? If so, are they marked as persistent? If not, then mark them as persistent.

Matt,

OK I followed your instructions and the links I created with the Simplehomenet Utility are preserved. From this exercise I see that if I do Sync Links, the Links from the PowerLinc are written to the Database file so if I have links I don't want in the Powerlinc they are re-written to the database file even if I have removed them from the Datebase file. So I have to delete them from the Powerlinc using the utility and also delete the same ones from the Database file, then I end up with the same links in both after a sync.

The only thing is that the EZX10RF links are not shown in the Link Editor dialog in Indigo for the PowerLinc.

The EZX10RF links are:

Code: Select all

PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 02, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 03, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 04, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 05, data 00 00 FF

Here is the result of the sync and the read;

Code: Select all

 PowerLinc           Linking - batch sync started
  PowerLinc           Linking - syncing PowerLinc links (address 13.AF.4C)
  PowerLinc           Linking - comparing local and powerlinc links
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D2.0D, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 0F.80.D8, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.CE.D1, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.B7.50, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.B7.16, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.CF.B3, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 04.D2.1F, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.28.A7, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D3.A7, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 19.80.54, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D0.42, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D2.00, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.17.23, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 0F.80.98, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 13.55.38, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 13.55.4C, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.32.0B, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 13.56.D1, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 05.9D.9B, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 18.76.23, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 19.80.65, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.35.52, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.7A.2E, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 04.D8.6F, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.CD.86, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 02, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 03, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 04, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 05, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.32.19, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D1.8E, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 16.84.59, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 0E.9F.88, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 1B.7E.C6, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.D2.0D, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 0F.80.D8, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.CE.D1, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.B7.50, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.B7.16, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.CF.B3, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 04.D2.1F, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 08.28.A7, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.D3.A7, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 19.80.54, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.D0.42, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.D2.00, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 14.17.23, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 13.55.38, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 13.55.4C, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 14.32.0B, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 13.56.D1, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 05.9D.9B, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 18.76.23, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 19.80.65, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 14.35.52, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.7A.2E, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 04.D8.6F, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.CD.86, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 08.9B.59, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 14.32.19, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 07.D1.8E, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 16.84.59, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 0E.9F.88, flags 03, group 01
  PowerLinc           Linking - . .  match: remote link is identical to persistent link 1B.7E.C6, flags 03, group 01
  PowerLinc           Linking - compare complete
  PowerLinc           Linking - sync complete
  PowerLinc           Linking - batch sync complete
  PowerLinc           Linking - PowerLinc links updated

PowerLinc           Linking - reading powerlinc internal links
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D2.0D, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 0F.80.D8, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.CE.D1, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.B7.50, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.B7.16, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.CF.B3, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 04.D2.1F, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.28.A7, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D3.A7, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 19.80.54, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D0.42, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D2.00, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.17.23, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 0F.80.98, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 13.55.38, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 13.55.4C, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.32.0B, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 13.56.D1, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 05.9D.9B, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 18.76.23, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 19.80.65, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.35.52, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.7A.2E, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 04.D8.6F, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.CD.86, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 02, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 03, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 04, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 08.9B.59, flags 03, group 05, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 14.32.19, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 07.D1.8E, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 16.84.59, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 0E.9F.88, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - . . . read: INSTEON plc link to controller 1B.7E.C6, flags 03, group 01, data 00 00 FF
  PowerLinc           Linking - read complete



Frankly, I've very confused as to what you are trying to do here. What exactly are the links for?

Can you tell me why a device would have 4 links when it is not linked to any other device like this example?

Thanks

<InsteonLinksGroup type="dict">
<DeviceAddress type="string">1267409</DeviceAddress>
<InsteonLinks type="vector">
<Link type="dict">
<MemoryLoc type="string">4088</MemoryLoc>
<ObjVers type="string">4</ObjVers>
<Status type="string">1</Status>
<Type2 type="string">0</Type2>
</Link>
<Link type="dict">
<MemoryLoc type="string">4080</MemoryLoc>
<ObjVers type="string">4</ObjVers>
<Status type="string">1</Status>
<Type2 type="string">0</Type2>
</Link>
<Link type="dict">
<MemoryLoc type="string">4072</MemoryLoc>
<ObjVers type="string">4</ObjVers>
<Status type="string">1</Status>
<Type2 type="string">0</Type2>
</Link>
<Link type="dict">
<MemoryLoc type="string">4064</MemoryLoc>
<ObjVers type="string">4</ObjVers>
<Status type="string">1</Status>
<Type2 type="string">0</Type2>
</Link>
</InsteonLinks>
<LinkInsertLocation type="string">4056</LinkInsertLocation>
<ObjVers type="string">2</ObjVers>
</InsteonLinksGroup>

I'll give it a try, but first please answer my question above in detail.

Exactly what are the links for, and what are you trying to accomplish with all of the XML manual link editing/etc.? The more detail, the better.

Actually the fiddling in the Database is not related to the EZX10RF

Originally I wanted the Powerlinc as a responder to each link I created in the EZX10RF. I did this with the Simplehomenet Utility. Using your steps above I now have that working OK, as I didn't realize that syncing the PowerLinc writes it's links to the Database, I thought it worked only the other way around.

The reason I am fiddling around with the Database is because my most unreliable and troublesome device is the Insteon Motion Detector. For example all of a sudden one MD started to flash the red LED (not a battery issue, a missing link issue) when I open the Database I see the structure the same for 3 of the MD's but the fourth one has a different structure. I delete all its structure and re-install the MD and it's OK.

Also when I get something strange happening I can usually see the cause in the Databse, for example I had a problem where whenever the EZX10RF was used it turned on a light in the house. I traced it and I found a link in the EZX10RF to the light (I never created these links but they somehow appear sometimes in various devices). I removed this link from the EZ then removed it from the Database. I suppose I could remove the link from the EZX10RF then do a sync to remove it but having to collect all the motion detectors and open them up to press the button for syncing is a pain.

Also I find that, with similar devices, that one has one link in it's Database structure and the other has several (like in my last post). I am fiddling to see if I remove them if it makes any difference and to basically understand the Database structure. Maybe this is because if the device is reinstalled/synced it writes a new link instead of writing over the old one?

I have 5 now but haven't installed it until I get everything cleaned up in 4.
regards - bob

Type2 having a value of 0:

Code: Select all

               <Type2 type="string">0</Type2>

Means it is an empty link. Likely a link that was erased. You should totally ignore it, but don't delete it because when Indigo wants to add a future link it will find the empty link and knows its address so that it can write the new link to its address.