Exten Posted March 3, 2013 Posted March 3, 2013 Here's the error screenshots. Can't add the brown SSQTXE-110 control. I've tried under 3 different firmwares, all of them recent, last 3 versions I believe. Is there anything else I can post to help troubleshoot?
LeeG Posted March 3, 2013 Posted March 3, 2013 Have the Event Viewer set to LEVEL 3. Level 1 shows results only, not the actual commands issued and responses. Not useful for analyzing actual device communication. A guess is the device is not responding as expected to the query to determine link database start location. Was the default Auto Discover used rather than selecting a specific device type? What is the latest ISY firmware that was tried? Was the UI confirmed with Help | About to be at the same level as the ISY firmware?
Exten Posted March 3, 2013 Author Posted March 3, 2013 Have the Event Viewer set to LEVEL 3. Level 1 shows results only, not the actual commands issued and responses. Not useful for analyzing actual device communication. A guess is the device is not responding as expected to the query to determine link database start location. Was the default Auto Discover used rather than selecting a specific device type? I just tried again using both auto discover and nmanually setting it to Broan SMSC110. What is the latest ISY firmware that was tried? Was the UI confirmed with Help | About to be at the same level as the ISY firmware? Attached. I'm on the road today so I'll check in in a couple days. Thanks for helping Lee.
LeeG Posted March 3, 2013 Posted March 3, 2013 Thanks for the additional data. The ISY is at 3.3.10 which is the latest Official release. The Insteon device is not identifying itself. The ISY tried three times and the device failed to indicate device type each time. This is a trace of a pretty old ICON device which is what this device looks like it is built on (single status LED at paddle pivot point). The message in Blue is missing from the posted trace. Sun 03/03/2013 10:49:25 AM : [iNST-TX-I1 ] 02 62 04 56 50 0F 10 00 Sun 03/03/2013 10:49:25 AM : [iNST-ACK ] 02 62 04.56.50 0F 10 00 06 ID-REQ (00) Sun 03/03/2013 10:49:25 AM : [iNST-SRX ] 02 50 04.56.50 19.70.06 2B 10 00 ID-REQ (00) Sun 03/03/2013 10:49:25 AM : [std-Direct Ack] 04.56.50-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 03/03/2013 10:49:25 AM : [iNST-SRX ] 02 50 04.56.50 02.0B.28 8B 01 00 (00) If not already tried use Start Linking and then press the Insteon device Set button. This should also generate a message that identifies the device type. If that does not work then back to New INSTEON Device and select the Broan Device Type. I think that is what the initial trace covered but it was at Level 1. I suspect that is going to show a different command is not working as other devices do but a LEVEL 3 trace is needed to confirm that.
Exten Posted May 19, 2013 Author Posted May 19, 2013 Okay...I'm back. Now using 4.0.4RC1 (latest) ...problem still exists. Set logging to level 3. Started linking mode at device. Device seems to go into flashing light mode - I think it's looking to link as it should be... Selected Start Linking from ISY menu..... Log says....Start Insteon Device Linking Mode.....in middle of screenshot. Any other info I can provide? Broan control seems to sputter and buzz at appropriate times - seems to react to ISY probings just fine (if I am reading it's reactions properly....) But ISY doesn't like the information that is being put out by the control?
Michel Kohanim Posted May 19, 2013 Posted May 19, 2013 Hi Exten, It seems that the PLM didn't even link to 1F.54.9F ... it's not even listed. I think we may have to talk to SmartHome; perhaps this device can only link to other BROAN devices? Can you link it to one of your INSTEON devices? With kind regards, Michel
arw01 Posted May 19, 2013 Posted May 19, 2013 Maybe you posted the wrong section of the trace? The one above shows the 1f.54. one the one below never shows it.
LeeG Posted May 19, 2013 Posted May 19, 2013 Started linking mode at device. Device seems to go into flashing light mode - I think it's looking to link as it should be... Selected Start Linking from ISY menu..... The sequence is wrong. Click Start Linking first which puts the PLM into a mode where it is looking for Set button press message from the device. Putting the device into linking mode before clicking Start Linking means the PLM is not listening for the message from the device.
Exten Posted May 20, 2013 Author Posted May 20, 2013 Okay...corrected the order. It seems to pop right up and successfully identify a device is out there. Comes right back immediately thinking it's a v.52 device. Then I click finish and then it doesn't like something...
LeeG Posted May 20, 2013 Posted May 20, 2013 Click Help | About what is shown for Firmware? what is shown for UI? Actually much progress is being made. The device identified itself and the ISY started the device add process. The trace indicates it is a very old I1 device. I added an I1 device to 4.0.4 successfully which brings up the possibility the UI (Admin Console) is not at 4.0.4.
Exten Posted May 21, 2013 Author Posted May 21, 2013 Just for grins a cleaner screenshot.... Yo Michael - I could try and link with something else - what would be the best device to use? Doesn't make sense that it would be listed as a valid device when manually linking devices if it will only link to it's Broan Bretheren. I guess 2 or more will play Fans Gone Wild or sumthin. But I have no use of that and I'm not inclined to buy a 2nd one. Right now I have that fan operating just fine on an appliance link on a timed cycle and ISY program control so mebbe I'm better off without it. How many times have I seen crusty old firmware purported to be the latest and greatest thing in an industry that is kind of behind the curve when it comes to technology? But I would have it working if possible.....so all ideas welcome.
LeeG Posted May 21, 2013 Posted May 21, 2013 With the Admin Console at the correct level I am out of ideas. I suggest discussing with UDI as it is not obvious what the ISY does not like about the Broan device. Here is the beginning of adding an old I1 ICON which looks much like what the Broan presents. ' Tue 05/21/2013 12:18:47 AM : Start Insteon Device Linking Mode Tue 05/21/2013 12:18:47 AM : [LNK-BGN ] 02 64 01 00 06 Tue 05/21/2013 12:18:56 AM : [LNK-STAT ] 02 53 M(01) gid=00 04.56.50 020B 28 Tue 05/21/2013 12:18:56 AM : [04.56.50 00] Linked device type=02.0B fw=28 Tue 05/21/2013 12:18:56 AM : [4 56 50 0 ] Added to list of devices to link to ISY Tue 05/21/2013 12:18:56 AM : [LNK-BGN ] 02 64 01 00 06 Tue 05/21/2013 12:19:02 AM : Stop Insteon Device Linking Mode, Final processing to follow Tue 05/21/2013 12:19:02 AM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Tue 05/21/2013 12:19:02 AM : [iNST-TX-I1 ] 02 62 04 56 50 0F 0D 00 Tue 05/21/2013 12:19:02 AM : [iNST-ACK ] 02 62 04.56.50 0F 0D 00 06 (00) Tue 05/21/2013 12:19:03 AM : [iNST-SRX ] 02 50 04.56.50 22.80.0B 2B 0D 00 (00) Tue 05/21/2013 12:19:03 AM : [std-Direct Ack] 04.56.50-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 05/21/2013 12:19:03 AM : [4 56 50 0 ] Calibrating engine version Tue 05/21/2013 12:19:03 AM : [4 56 50 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0000) Tue 05/21/2013 12:19:03 AM : [iNST-SRX ] 02 50 04.56.50 22.80.0B 23 0D 00 (00) Tue 05/21/2013 12:19:03 AM : [std-Direct Ack] 04.56.50-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 05/21/2013 12:19:03 AM : [iNST-DUP ] Previous message ignored. Tue 05/21/2013 12:19:03 AM : [4 56 50 1 ] Start : Adding device to ISY Tue 05/21/2013 12:19:03 AM : [4 56 50 1 ] Finish : Adding device to ISY was Successful
Michel Kohanim Posted May 21, 2013 Posted May 21, 2013 Hi Exten, I am with LeeG here! So, did it link to any other INSTEON device? It really does not matter to which device you link it to. We just want to validate that it's an INSTEON like device. The reason we have it in the list is because INSTEON has a list which we use but we have never actually tried it. We were told that it's like a SwitchLinc but that might not be the case. So, the main question is whether or not this is an actual INSTEON device and not a one off. With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.