ejh Posted February 10, 2013 Share Posted February 10, 2013 I have done no manual linking. I did delete the second device and then add it back in to see how the records were entered in the PLM. Again they are E2 not A2. The PLM is a 2413S V1.6 purchased about 6 months ago. I do not know if the PLM firmware version should matter. Is there a way to safely edit the PLM records without messing up what the ISY thinks they should be? It seems strange both devices are consistently entered in the PLM as E2 when I add them telling the ISY to delete all records in the sensor device. I have deleted them twice each and they consistently show back up the same way. Thanks again Link to comment
LeeG Posted February 10, 2013 Share Posted February 10, 2013 What does Help | About show for Firmware and UI levels? What is being entered in the Device Type field when the Leak Sensor is added to the ISY? Note that the linked light not shutting Off is normal. The Leak Sensor only sends On commands. It does not send Off commands as the Leak Sensor changes from Wet to Dry to Wet. Take a look at the spec’s section of the Leak Sensor sales page. It documents the commands the Leak Sensor sends (On command only). Link to comment
ejh Posted February 11, 2013 Share Posted February 11, 2013 Both Firmware and UI are identical. Insteon_UD99 v3.3.10 (2013-01-17-01:38:06) ISY 99i/IR Pro Link to comment
ejh Posted February 11, 2013 Share Posted February 11, 2013 The sensor then as I understand it sends WET -On or DRY-On only which implies it's counterpart is in the Off state. Link to comment
LeeG Posted February 11, 2013 Share Posted February 11, 2013 The ISY sets the Dry node to Off when the Leak Sensor sends a Wet On message. The ISY sets the Wet node to Off when the Leak Sensor sends a Dry On message. The Leak Sensor does not send an Off command to the Dry node or the Wet node which is why a directly linked device does not turn Off. I suggest Deleting the Leak Sensor from the ISY. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device, enter the Insteon address of the Leak Sensor, Name of choice, Device Type set to default Auto Discover. BEFORE clicking Okay, press Leak Sensor Set button until Leak Sensor LED blinks continuously. Now click Okay on New INSTEON Device popup. Post the event trace when the add completes. That will show the PLM commands used to create the PLM link records. Link to comment
ejh Posted February 11, 2013 Share Posted February 11, 2013 Log from Leak sensor device add Sun 02/10/2013 07:39:52 PM : [21 7d d7 ] Added to list of devices to link to ISY Sun 02/10/2013 07:39:52 PM : [iNST-TX-I1 ] 02 62 21 7D D7 0F 0D 00 Sun 02/10/2013 07:39:52 PM : [iNST-ACK ] 02 62 21.7D.D7 0F 0D 00 06 (00) Sun 02/10/2013 07:39:52 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 0D 02 (02) Sun 02/10/2013 07:39:52 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:52 PM : [iNST-TX-I1 ] 02 62 21 7D D7 0F 10 00 Sun 02/10/2013 07:39:52 PM : [iNST-ACK ] 02 62 21.7D.D7 0F 10 00 06 ID-REQ (00) Sun 02/10/2013 07:39:53 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 10 00 ID-REQ (00) Sun 02/10/2013 07:39:53 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:53 PM : [iNST-SRX ] 02 50 21.7D.D7 10.08.3E 8B 02 00 (00) Sun 02/10/2013 07:39:53 PM : [std-Broadcast] 21.7D.D7-->10.08.3E, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:53 PM : [21 7D D7 0 ] Calibrating engine version Sun 02/10/2013 07:39:53 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sun 02/10/2013 07:39:53 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sun 02/10/2013 07:39:53 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:39:53 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:54 PM : [iNST-ERX ] 02 51 21 7D D7 1C FB 8D 11 2F 00 00 01 0F FF 01 E2 01 1C FB 8D FF 1F 01 1B Sun 02/10/2013 07:39:54 PM : [Ext-Direct ] 21.7D.D7-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sun 02/10/2013 07:39:54 PM : [21 7D D7 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Sun 02/10/2013 07:39:54 PM : [21 7D D7 1 ] Start : Adding device to ISY Sun 02/10/2013 07:39:54 PM : [21 7D D7 1 ] Finish : Adding device to ISY was Successful Sun 02/10/2013 07:39:54 PM : [21 7D D7 2 ] Start : Adding device to ISY Sun 02/10/2013 07:39:54 PM : [21 7D D7 2 ] Finish : Adding device to ISY was Successful Sun 02/10/2013 07:39:54 PM : [21 7D D7 0 ] Successfully added device Sun 02/10/2013 07:39:55 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 02 0F FF 08 E2 01 1C FB 8D FF 1F 01 13 Sun 02/10/2013 07:39:55 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 02 0F FF 08 E2 01 1C FB 8D FF 1F 01 13 06 (00) Sun 02/10/2013 07:39:55 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:39:55 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:55 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 21 7D D7 10 08 3E 15 Sun 02/10/2013 07:39:55 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 02 0F F7 08 E2 02 1C FB 8D FF 1F 02 19 Sun 02/10/2013 07:39:56 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 02 0F F7 08 E2 02 1C FB 8D FF 1F 02 19 06 (00) Sun 02/10/2013 07:39:56 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:39:56 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:56 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 21 7D D7 10 08 3E 15 Sun 02/10/2013 07:39:56 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Sun 02/10/2013 07:39:57 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Sun 02/10/2013 07:39:57 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:39:57 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:57 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Sun 02/10/2013 07:39:57 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Sun 02/10/2013 07:39:58 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:39:58 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:58 PM : [iNST-ERX ] 02 51 21 7D D7 1C FB 8D 11 2F 00 3C 01 0F E7 01 00 00 00 00 00 00 00 00 9D Sun 02/10/2013 07:39:58 PM : [Ext-Direct ] 21.7D.D7-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sun 02/10/2013 07:39:58 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Sun 02/10/2013 07:39:58 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Sun 02/10/2013 07:39:59 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:39:59 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 02/10/2013 07:39:59 PM : [iNST-ERX ] 02 51 21 7D D7 1C FB 8D 11 2F 00 00 01 0F E7 01 00 00 00 00 00 00 00 00 D9 Sun 02/10/2013 07:39:59 PM : [Ext-Direct ] 21.7D.D7-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sun 02/10/2013 07:39:59 PM : [iNST-TX-I2CS] 02 62 21 7D D7 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Sun 02/10/2013 07:39:59 PM : [iNST-ACK ] 02 62 21.7D.D7 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Sun 02/10/2013 07:40:00 PM : [iNST-SRX ] 02 50 21.7D.D7 1C.FB.8D 2B 2F 00 (00) Sun 02/10/2013 07:40:00 PM : [std-Direct Ack] 21.7D.D7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Link to comment
ejh Posted February 11, 2013 Share Posted February 11, 2013 Result Device Links Table 0 : 0FF8 : E2 01 1C.FB.8D FF 1F 01 1 : 0FF0 : E2 02 1C.FB.8D FF 1F 02 2 : 0FE8 : 00 00 00.00.00 00 00 00 ISY Links Table 0 : 0FF8 : E2 01 1C.FB.8D FF 1F 01 1 : 0FF0 : E2 02 1C.FB.8D FF 1F 02 2 : 0FE8 : 00 00 00.00.00 00 00 00 Link to comment
LeeG Posted February 11, 2013 Share Posted February 11, 2013 The ISY Links Table is simply the link records the ISY thinks should be in the Leak Sensor. They should and do match what is in the Leak Sensor. They are not the link records in the PLM. A Show PLM Links Table displays the link records in the PLM. The New INSTEON Device wrote Responder link records into the PLM. If the PLM does not have Responder link records it is likely full. I full PLM link database can usually be corrected with a Restore Modem (PLM) which compresses out any deleted and duplicate records. Sun 02/10/2013 07:39:55 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 21 7D D7 10 08 3E 15 Sun 02/10/2013 07:39:56 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 21 7D D7 10 08 3E 15 Link to comment
ejh Posted February 11, 2013 Share Posted February 11, 2013 That was it. Thank you very much. The PLM has a limitation of around 1000 links I thought. I have over 100 Insteon devices in the home. What happens if the link table outgrows the PLM. I do not believe you can add a second PLM. Link to comment
LeeG Posted February 11, 2013 Share Posted February 11, 2013 Correct. A second PLM cannot be added to the same ISY. If actually beyond the PLM capacity and not just full because of deleted and duplicate links in the PLM, some Scene management will open up additional free space. Multiple Scenes with nearly identical responders can be combined to reduce the number of Scenes. With a little ingenuity the number of PLM links can often be reduced. If the solution cannot be found there an additional ISY can be used, where devices are split between the ISYs. The challenge is to split the devices so there is no need to control a device from both ISYs. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.