Release 3.2.2 (Beta) Is Now Available

[ELA]

I performed a factory reset on the new I2CS Appliancelinc prior to a third attempt to Auto-Discover and this attempt went flawless. A forth attempt (just for test purposes) resulted in the ISY hanging once again. This might be due to operator error on my part?

 

Q1) I believe the best way to remove a device is to delete it from the ISY prior to factory resetting of the device, is that correct? This being to to remove all links on both ends?

Q2) If you factory reset a device first, then delete it from the ISY, does this fail to remove the links in the ISY -PLM?

 

I was surely seeing some strange behavior in the ISY and wonder if at least part of that was partial links not removed.

 

I was seeing the ISY lock-up and never time out (> 10 minutes) which seems very strange. I would expect it to time out no matter what, unless the code was hung. This appeared to be the case because I had to power reset it 2-3 times in this testing process to get it to stop presenting the "Initializing System Window".

 

The last time this happened I saw that it was hung attempting to work with an address shown on the screen that belonged to a MS(PIR) sensor ? The new Appliancelinc was not added to any scenes, and why would it hang up on the forth attempt but not the third? I then had a successful 5th auto-discover linking and am leaving it as is.

 

I am up and running fine now so no need to pursue this any further. I am just reporting this back in case is not all due to errors on my part.

 

I do have a new Switchlinc Dimmer (V5.6, suspected I2CS) to install on Sunday so I will see how that one goes. That will be a replacement of an existing older switchlinc dimmer (non I2CS).

[LeeG]

Without an event trace it is only speculation but it sounds like the ApplianceLinc does not respond to the PLM when it entered linking mode (the second time). The ISY issued the PLM command and is waiting for the 0253 command response that never comes. Not sure if this is a planned part of I2CS security or not. Would have thought the PLM would timeout eventually. I'll try a few times with the I2CS FanLinc. The I2CS motion sensor I have is not a good candidate to test this sequence since the MS it manually put into linking mode. I have a new ApplianceLinc ordered so that should allow a second test point for the ApplianceLinc.

[ELA]

Thanks for your help LeeG,

I had kept a log of one of the failed attempts. One where it hung up "appearing to" attempt communicating with an MS (PIR)Sensor.

I reviewed the log to the best of my understanding and it appears that linking mode was established , The ISY tried to begin linking but that it did not happen.

A little while later the garage PIR sensor times out with an off command ( from a previous On 10 minutes earlier when I had tripped it ). I guess this is why its address appeared in the window?

 

Thu 04/05/2012 06:57:20 PM : ---- Initializing the linked devices ----

Thu 04/05/2012 06:57:20 PM : ---- All Linked Devices are now initialized ----

Thu 04/05/2012 06:57:20 PM : ---- Add remaining devices ----

Thu 04/05/2012 06:57:20 PM : [iNST-TX-I1  ] 02 62 1C F3 17 0F 0D 00

Thu 04/05/2012 06:57:20 PM : [iNST-ACK    ] 02 62 1C.F3.17 0F 0D 00 06                 (00)

Thu 04/05/2012 06:57:21 PM : [iNST-SRX    ] 02 50    1C.F3.17    1B.FD.23       2B 0D FF           (FF)

Thu 04/05/2012 06:57:21 PM : [standard-Direct Ack][1C.F3.17-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Thu 04/05/2012 06:57:21 PM : [iNST-TX-I2CS] 02 62 1C F3 17 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Thu 04/05/2012 06:57:21 PM : [iNST-ACK    ] 02 62 1C.F3.17 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Thu 04/05/2012 06:57:22 PM : [iNST-SRX    ] 02 50 1C.F3.17 1B.FD.23 2B 09 01    LNK-ON (01)

Thu 04/05/2012 06:57:22 PM : [standard-Direct Ack][1C.F3.17-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Thu 04/05/2012 06:57:22 PM : [LNK-BGN     ] 02 64 01 00 06 




//   Garage PIR sensor   , turning off

Thu 04/05/2012 06:58:16 PM : [iNST-SRX    ] 02 50    14.71.EE     00.00.02 CB 13 02    LTOFFRR(02)

Thu 04/05/2012 06:58:16 PM : [standard-Group][14.71.EE-->Group=2] Max Hops=3, Hops Left=2

Thu 04/05/2012 06:58:16 PM : [  14 71 EE 2]      DOF   2

Thu 04/05/2012 06:58:16 PM : [  14 71 EE 2]       ST   0

Thu 04/05/2012 06:58:16 PM : [iNST-SRX    ] 02 50 14.71.EE 00.00.02 CB 13 02    LTOFFRR(02)

Thu 04/05/2012 06:58:16 PM : [standard-Group][14.71.EE-->Group=2] Max Hops=3, Hops Left=2

Thu 04/05/2012 06:58:16 PM : [iNST-SRX    ] 02 50     14.71.EE        00.00.02 CB 13 02    LTOFFRR(02):  Process Message: Ignored

Thu 04/05/2012 06:58:16 PM : [standard-Group][14.71.EE-->Group=2] Max Hops=3, Hops Left=2

Thu 04/05/2012 06:58:17 PM : [iNST-SRX    ] 02 50    14.71.EE    1B.FD.23 41 13 02    LTOFFRR(02)

Thu 04/05/2012 06:58:17 PM : [standard-Cleanup][14.71.EE-->ISY/PLM Group=2] Max Hops=1, Hops Left=0

Thu 04/05/2012 06:58:17 PM : [iNST-SRX    ] 02 50   14.71.EE    1B.FD.23 41 13 02    LTOFFRR(02):  Process Message: Ignored

Thu 04/05/2012 06:58:17 PM : [standard-Cleanup][14.71.EE-->ISY/PLM Group=2] Max Hops=1, Hops Left=0

[LeeG]

This looks like the same as one of the previous traces. 1C.F3.17 was put into linking mode and responded with an ACK. The PLM was put into linking mode which should have generated an exchange with the ApplianceLinc where the Insteon address, cat/subcat and firmware should have been sent from the ApplianceLinc to the PLM which would have resulted in an 02 53 response.

 

The PLM is not hung as it presented an message from 14.71.EE.

 

I’ll repeat the same sequence on my ApplianceLinc when it gets here Monday. Should have been here Saturday but either it was late getting to FedEx or the holiday has delayed delivery until Monday.

 

The sequence works correctly after the factory reset so I would think this is an ApplianceLinc issue.

 

Thu 04/05/2012 06:57:21 PM : [iNST-ACK ] 02 62 1C.F3.17 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Thu 04/05/2012 06:57:22 PM : [iNST-SRX ] 02 50 1C.F3.17 1B.FD.23 2B 09 01 LNK-ON (01)

 

Thu 04/05/2012 06:57:22 PM : [standard-Direct Ack][1C.F3.17-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 04/05/2012 06:57:22 PM : [LNK-BGN ] 02 64 01 00 06

 

 

 

 

// Garage PIR sensor , turning off

 

Thu 04/05/2012 06:58:16 PM : [iNST-SRX ] 02 50 14.71.EE 00.00.02 CB 13 02 LTOFFRR(02)

[ELA]

Installed a new Switchlinc (hardware R5.6, V40 firmware) under ISY V3.2.2 that went flawless using auto-discover. Unfortunately I forgot to save the log when ISY Rebooted after doing a "replace operation".

Later using the Query Engine the new device showed a "01" or i2 device. Did not appear to be I2CS.