When deleting a device, does the ISY actually delete the links from the PLM as well? I deleted a device and viewed the PLM link table and said device was gone. However, oddly (in my opinion), when I added the same device back, the PLM did not beep and go into linking mode. Is this intended behavior?

 

I'm not seeing any issues, but am curious for my own knowledge.

The ISY issues a command to have the link record deleted. It is up to the PLM to perform that action and I do not know what affect the deleted link record would have if/when the device is added back. The command to mark the link inactive is in Red

 

Wed 02/05/2014 07:13:54 PM : [1D 38 0 1 ] Link 1 : 0FF0 [620122800B010001] Saving [62..............]

Wed 02/05/2014 07:13:55 PM : [1D 38 0 1 ] Link 0 : 0FF8 [220022800BFF1F01] Saving [22..............]

Wed 02/05/2014 07:13:55 PM : [MNG-LNK-RSP ] 02 6F 80 E2 00 1D 38 00 01 20 40 06

Wed 02/05/2014 07:13:55 PM : [1D 38 0 1 ] Start : Removing device from ISY

Wed 02/05/2014 07:13:55 PM : [1D 38 0 1 ] Finish : Removing from ISY was Successful

Wed 02/05/2014 07:13:56 PM : [All ] Writing 0 bytes to devices

Based on the PLM link table after adding a new device post deletion, it does appear that it has marked the link correctly and allowed the new device to take over that slot in the database. I still just find it odd that it doesn't need to go back into linking mode if I re-add the deleted the device. When I re-add the deleted device, the PLM links exist, the device links exist and match the ISY links, so I'm sure everything would probably work without issue.

The reuse of the deleted record is what I expected. Was Start Linking or New INSTEON Device used to readd device after the delete? I have to make a run out of town this afternoon; will see what my PLM does once I know which approach was used to readd the device. Also what level firmware is in the PLM, Tools | Diagnostics | PLM Info/Status?

I've used New Insteon Device to add all of my devices.

 

PLM v9B

Have not forgotten this question. I just realized the device I was testing had already been in the test bed at some point in the past which explains why I was not seeing any difference between what I thought was first and subsequent adds. I have to switch to a device that has never been used before.

No problem, thanks.

The difference in PLM response is due to the fact that the device has a link back to the PLM the second time so there is no need to go through the linking sequence needed by an I2CS device. The first Query Insteon Engine response indicates the device is I2CS and does not have link to the PLM. The ISY generates the sequence that links the I2CS device back to the PLM. This is why the PLM beeps as it must be put into linking mode to generate the device link.

 

Sun 02/09/2014 01:45:57 PM : [1f 14 82 ] Added to list of devices to link to ISY

Sun 02/09/2014 01:45:57 PM : [iNST-TX-I1 ] 02 62 1F 14 82 0F 0D 00

Sun 02/09/2014 01:45:57 PM : [iNST-ACK ] 02 62 1F.14.82 0F 0D 00 06 (00)

Sun 02/09/2014 01:45:57 PM : [iNST-SRX ] 02 50 1F.14.82 22.80.0B AB 0D FF (FF)

Sun 02/09/2014 01:45:57 PM : [std-Direct Nack] 1F.14.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 02/09/2014 01:45:57 PM : [iNST-TX-I2CS] 02 62 1F 14 82 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Sun 02/09/2014 01:45:57 PM : [iNST-ACK ] 02 62 1F.14.82 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Sun 02/09/2014 01:45:57 PM : [iNST-SRX ] 02 50 1F.14.82 22.80.0B A3 0D FF (FF)

Sun 02/09/2014 01:45:57 PM : [std-Direct Nack] 1F.14.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Sun 02/09/2014 01:45:57 PM : [iNST-DUP ] Previous message ignored.

Sun 02/09/2014 01:45:58 PM : [iNST-SRX ] 02 50 1F.14.82 22.80.0B 2B 09 01 LNK-ON (01)

Sun 02/09/2014 01:45:58 PM : [std-Direct Ack] 1F.14.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 02/09/2014 01:45:58 PM : [LNK-BGN ] 02 64 01 00 06

Sun 02/09/2014 01:45:59 PM : [LNK-STAT ] 02 53 M(01) gid=00 1F.14.82 021E 41

Sun 02/09/2014 01:45:59 PM : [iNST-TX-I1 ] 02 62 1F 14 82 0F 0D 00

Sun 02/09/2014 01:45:59 PM : [LNK-END ] 02 65 06

Sun 02/09/2014 01:45:59 PM : [std MH ] Unexpected Ack imCmd=65 cmd1= 0x82

Sun 02/09/2014 01:45:59 PM : [iNST-ACK ] 02 62 1F.14.82 0F 0D 00 06 (00)

Sun 02/09/2014 01:45:59 PM : [iNST-SRX ] 02 50 1F.14.82 22.80.0B 2B 0D 02 (02)

Sun 02/09/2014 01:45:59 PM : [std-Direct Ack] 1F.14.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

At this point I deleted the device and added it again. This time the device reports it is I2CS and it has a link to the PLM, thus no need to go through the sequence to generate that link.

 

Sun 02/09/2014 01:47:51 PM : [1f 14 82 ] Added to list of devices to link to ISY

Sun 02/09/2014 01:47:51 PM : [iNST-TX-I1 ] 02 62 1F 14 82 0F 0D 00

Sun 02/09/2014 01:47:51 PM : [iNST-ACK ] 02 62 1F.14.82 0F 0D 00 06 (00)

Sun 02/09/2014 01:47:51 PM : [iNST-SRX ] 02 50 1F.14.82 22.80.0B 2B 0D 02 (02)

Sun 02/09/2014 01:47:51 PM : [std-Direct Ack] 1F.14.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 02/09/2014 01:47:51 PM : [iNST-TX-I1 ] 02 62 1F 14 82 0F 10 00

Sun 02/09/2014 01:47:51 PM : [iNST-ACK ] 02 62 1F.14.82 0F 10 00 06 ID-REQ (00)

Sun 02/09/2014 01:47:51 PM : [iNST-SRX ] 02 50 1F.14.82 22.80.0B 2B 10 00 ID-REQ (00)

Sun 02/09/2014 01:47:51 PM : [std-Direct Ack] 1F.14.82-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 02/09/2014 01:47:51 PM : [iNST-SRX ] 02 50 1F.14.82 02.1E.41 8B 01 00 (00)

Sun 02/09/2014 01:47:51 PM : [std-Broadcast] 1F.14.82-->02.1E.41, Max Hops=3, Hops Left=2

Sun 02/09/2014 01:47:51 PM : [1F 14 82 0 ] Calibrating engine version

Thanks for the diligence and info - makes sense. I assume if I factory reset said device, it would have to go into linking mode again.

That would be correct. The factory reset would clear the device link database which makes the attempt after the reset look like the first.