matapan Posted September 13, 2011 Posted September 13, 2011 Using ISY 99 with 2.8.16 firmware, a Keypadlinc Relay dual band device I added came up in the Admin Console as an unsupported device. Probably not surprising if the Keypadlinc came out after the ISY firmware was released. The device responds to basic on / off commands, but does not respond to scene commands. Is this device supported in the current beta firmware?
LeeG Posted September 13, 2011 Posted September 13, 2011 matapan According to the release notes the 2487S support was added at 3.1.3 Lee
bsobel Posted January 13, 2012 Posted January 13, 2012 I just updated to 3.1.16 and the 2487S is still being detected as an 'unknown device' yet the forums say this was added earlier in the 3.1.x line. I cleared my java cache and the install went fine, any ideas why the device is unknown again?
LeeG Posted January 13, 2012 Posted January 13, 2012 bsobel Check Help | About and be sure the Firmware line and the UI line both say 3.1.16. If the UI line does not say 3.1.16 or the UI line is not there at all (should be line immediately below Firmware line) check the URL being used to invoke the Admin Console and clear Java cache again. Sounds like the wrong level Admin Console is being used. Lee
matapan Posted January 13, 2012 Author Posted January 13, 2012 Have you tried deleting the dual band Keypadlinc from the My Lighting list, then adding it back after the ISY firmware upgrade?
MexicanRadio Posted December 1, 2012 Posted December 1, 2012 I'm having problems with a new (as in only days old) 6-button dual-band Keypadlinc switch (2487S), also. Keypadlinc is marked: v6.9 1246 When first installed, with ISY software on ver. 3.2.6, it was correctly added, showing all 6 buttons. However, not long later, when I was working on programming the ISY to use newly added devices, the ISY suddenly complained it couldn't communicate with the Keypadlinc. I had already successfully added a couple of programs to use the Keypadlinc by then. The device has never been detected correctly since. Now, whenever I try to add the Keypadlinc, whether I use Start Linking or New Insteon Device the Keypadlinc always comes up as an Unsupported device: 2.44 In fact, you can see the device type switch from the selected 2487S Keypadlinc to Unsupported device almost immediately when using the New Insteon Device method. So far I have tried: Updating software from 3.2.6 to 3.3.4 (including clearing the Java cache before re-attempting any addition of the Keypadlinc) Factory reset on the Keypadlinc Reviewing all devices for spurious links to the Keypadlinc and ensuring that none remain Unplugging and re-plugging the PLM Rebooting the ISY via software Unplugging and replugging the ISY I've tested RF communications (4 taps method) using another device plugged in on another circuit. The keypadlinc was the initiator and it works fine, with the second device indicating that it is communicating and on the opposite phase. So my assumption here is that I have RF comms as backup to the line comms. On the very same circuit (i.e. same breaker) is also an OutletLinc (2473SWH) (bought and installed at the same time as the Keypadlinc) which works just fine, so my assumption is that communication on that circuit with the PLM/ISY is normal. Nothing has helped so far, the device always comes up as unsupported. So... failed Keypadlinc? Or is this a bug in 3.3.4 which I understand is Beta (although a release candidate) and I should go back to 3.2.6, if possible, and try again. Or is there something I am missing and I am doing it wrong?
LeeG Posted December 1, 2012 Posted December 1, 2012 If you go back to 3.2.6 be sure to restore a good 3.2.6 backup as the 3.3.x images made changes to the configuration information which is not backward compatible. In the past a specific Device Type selection would be used. Since this is an I2CS device that may not be possible any more.
MexicanRadio Posted December 1, 2012 Posted December 1, 2012 Gave the alternate device a try. No luck. Still goes to unsupported device. I guess I'll try moving it, so I can see if it's just something with the circuit it's on. Is it possible to test an Insteon device with no load attached?
LeeG Posted December 1, 2012 Posted December 1, 2012 A load connection with the Red wire is not a requirement. Devices in a 3,4,5 way configuration, only one normally is connected to a load. Cap the Red wire. I use an Appliance cord to test new wired devices before installing them. Allows them to be plugged near the PLM to insure they work before installing. That way if they work at the PLM and not at the final location it normally means a comm. issue.
MexicanRadio Posted December 2, 2012 Posted December 2, 2012 Well, this doesn't look promising. Same wrong results when the Keypadlinc is plugged via a test cable into the very same outlet as the PLM. There's an error that occurs at line 14 when trying to add the device. Could this be the problem? See the log below: Sat 12/01/2012 16:41:49 : [20 42 4F ] Added to list of devices to link to ISY Sat 12/01/2012 16:41:49 : [iNST-TX-I1 ] 02 62 20 42 4F 0F 0D 00 Sat 12/01/2012 16:41:49 : [iNST-ACK ] 02 62 20.42.4F 0F 0D 00 06 (00) Sat 12/01/2012 16:41:50 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 AB 0D FF (FF) Sat 12/01/2012 16:41:50 : [std-Direct Nack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:50 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Sat 12/01/2012 16:41:50 : [iNST-ACK ] 02 62 20.42.4F 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Sat 12/01/2012 16:41:50 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 09 01 LNK-ON (01) Sat 12/01/2012 16:41:50 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:50 : [LNK-BGN ] 02 64 01 00 06 Sat 12/01/2012 16:41:51 : [LNK-STAT ] 02 53 M(01) gid=00 20.42.4F 022C 41 Sat 12/01/2012 16:41:51 : [iNST-TX-I1 ] 02 62 20 42 4F 0F 0D 00 Sat 12/01/2012 16:41:51 : [LNK-END ] 02 65 06 Sat 12/01/2012 16:41:51 : [std MH ] Unexpected Ack imCmd=65 cmd1=IOCTL 0x4F Sat 12/01/2012 16:41:52 : [iNST-ACK ] 02 62 20.42.4F 0F 0D 00 06 (00) Sat 12/01/2012 16:41:52 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 0D 02 (02) Sat 12/01/2012 16:41:52 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:56 : [iNST-TX-I1 ] 02 62 20 42 4F 0F 0D 00 Sat 12/01/2012 16:41:56 : [iNST-ACK ] 02 62 20.42.4F 0F 0D 00 06 (00) Sat 12/01/2012 16:41:56 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 0D 02 (02) Sat 12/01/2012 16:41:56 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:56 : [iNST-TX-I1 ] 02 62 20 42 4F 0F 10 00 Sat 12/01/2012 16:41:56 : [iNST-ACK ] 02 62 20.42.4F 0F 10 00 06 ID-REQ (00) Sat 12/01/2012 16:41:57 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 10 00 ID-REQ (00) Sat 12/01/2012 16:41:57 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:57 : [iNST-SRX ] 02 50 20.42.4F 02.2C.41 8B 01 00 (00) Sat 12/01/2012 16:41:57 : [std-Broadcast] 20.42.4F-->02.2C.41, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:57 : [20 42 4F 0 ] Calibrating engine version Sat 12/01/2012 16:41:57 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 12/01/2012 16:41:57 : [iNST-ACK ] 02 62 20.42.4F 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 12/01/2012 16:41:58 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2F 00 (00) Sat 12/01/2012 16:41:58 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:58 : [iNST-ERX ] 02 51 20 42 4F 1C FA 98 11 2F 00 00 01 0F FF 00 AA 00 1C FA 98 FF 1C 01 4E Sat 12/01/2012 16:41:58 : [Ext-Direct ] 20.42.4F-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/01/2012 16:41:58 : [20 42 4F 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Sat 12/01/2012 16:41:58 : [20 42 4F 1 ] Start : Adding device to ISY Sat 12/01/2012 16:41:58 : [20 42 4F 1 ] Finish : Adding device to ISY was Successful Sat 12/01/2012 16:41:58 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Sat 12/01/2012 16:41:58 : [iNST-ACK ] 02 62 20.42.4F 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Sat 12/01/2012 16:41:59 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2E 00 (00) Sat 12/01/2012 16:41:59 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:41:59 : [iNST-ERX ] 02 51 20 42 4F 1C FA 98 11 2E 00 01 01 00 00 20 20 1C FE 3F 00 03 00 00 00 Sat 12/01/2012 16:41:59 : [Ext-Direct ] 20.42.4F-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/01/2012 16:41:59 : [ 20 42 4F 1] OL 255 Sat 12/01/2012 16:41:59 : [ 20 42 4F 1] RR 28 Sat 12/01/2012 16:41:59 : [iNST-TX-I1 ] 02 62 20 42 4F 0F 19 00 Sat 12/01/2012 16:41:59 : [iNST-ACK ] 02 62 20.42.4F 0F 19 00 06 LTSREQ (LIGHT) Sat 12/01/2012 16:42:00 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 01 FF (FF) Sat 12/01/2012 16:42:00 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:42:00 : [ 20 42 4F 1] ST 255 Sat 12/01/2012 16:42:00 : [ 20 42 4F 1] OL 255 Sat 12/01/2012 16:42:00 : [ 20 42 4F 1] RR 28 Sat 12/01/2012 16:42:00 : [20 42 4F 0 ] Successfully added device Sat 12/01/2012 16:42:00 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2F 00 00 02 0F FF 08 A2 00 1C FA 98 FF 1F 01 4A Sat 12/01/2012 16:42:00 : [iNST-ACK ] 02 62 20.42.4F 1F 2F 00 00 02 0F FF 08 A2 00 1C FA 98 FF 1F 01 4A 06 (00) Sat 12/01/2012 16:42:00 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2F 00 (00) Sat 12/01/2012 16:42:00 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:42:01 : [MNG-LNK-RSP ] 02 6F 40 E2 00 20 42 4F 02 2C 41 06 Sat 12/01/2012 16:42:01 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Sat 12/01/2012 16:42:01 : [iNST-ACK ] 02 62 20.42.4F 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Sat 12/01/2012 16:42:01 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2F 00 (00) Sat 12/01/2012 16:42:01 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:42:01 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Sat 12/01/2012 16:42:01 : [iNST-ACK ] 02 62 20.42.4F 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Sat 12/01/2012 16:42:02 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2F 00 (00) Sat 12/01/2012 16:42:02 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:42:02 : [iNST-ERX ] 02 51 20 42 4F 1C FA 98 11 2F 00 00 01 0F EF 20 00 00 00 00 00 00 00 00 B2 Sat 12/01/2012 16:42:02 : [Ext-Direct ] 20.42.4F-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/01/2012 16:42:02 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Sat 12/01/2012 16:42:02 : [iNST-ACK ] 02 62 20.42.4F 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Sat 12/01/2012 16:42:03 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2F 00 (00) Sat 12/01/2012 16:42:03 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/01/2012 16:42:03 : [iNST-ERX ] 02 51 20 42 4F 1C FA 98 11 2F 00 00 01 0F EF 20 00 00 00 00 00 00 00 00 B2 Sat 12/01/2012 16:42:03 : [Ext-Direct ] 20.42.4F-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/01/2012 16:42:03 : [iNST-TX-I2CS] 02 62 20 42 4F 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Sat 12/01/2012 16:42:03 : [iNST-ACK ] 02 62 20.42.4F 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Sat 12/01/2012 16:42:04 : [iNST-SRX ] 02 50 20.42.4F 1C.FA.98 2B 2F 00 (00) Sat 12/01/2012 16:42:04 : [std-Direct Ack] 20.42.4F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
LeeG Posted December 2, 2012 Posted December 2, 2012 Looks like either go back to 3.2.6 or wait for some future ISY release.
MexicanRadio Posted December 2, 2012 Posted December 2, 2012 Yep, and thanks for your help! Unless that error indicates a device malfunction, I'm betting those are gonna be my only choices. I'll see if anyone else has any ideas over the next couple of days. Maybe I'll order an earlier version, not dual-band, to try for this particular location. Eventually I need more than one anyway.
LeeG Posted December 2, 2012 Posted December 2, 2012 The event trace looks fine as far as physical errors are concerned. The message indicating an error is simply the PLM coming out of linking mode after establishing the necessary I2CS authorization link. Happens with all I2CS devices. Two link records were written successfully which is not correct for a KeypadLinc but that is due to the fact that the ISY does not have the 02.44 cat/subcat values in the list of supported devices. Physical communication with the KeypadLinc is very good (Hops Left=2). Just need an ISY release that has the 02.44 cat/subcat so the ISY knows it is a KeypadLinc.
MexicanRadio Posted December 2, 2012 Posted December 2, 2012 Physical communication with the KeypadLinc is very good (Hops Left=2). Just need an ISY release that has the 02.44 cat/subcat so the ISY knows it is a KeypadLinc. OK, I get it, and that lets me know what I needed, that it's just a software issue, not a hardware problem. So, I'll just reinstall and then wait for an update, which I'm sure will be coming, given UDI's usual great support.
Vyrolan Posted December 2, 2012 Posted December 2, 2012 If you go back to 3.2.6 be sure to restore a good 3.2.6 backup as the 3.3.x images made changes to the configuration information which is not backward compatible. Looks like either go back to 3.2.6 or wait for some future ISY release. I'm guessing unlike LeeG they don't read these forums on the weekend? I don't have a 3.2.6 to go back to. =( My ISY came with 3.1.X on it and first thing I did before adding any devices or anything was upgrade to 3.3.4. =( I guess I'm lucky it's the primary in my 3-way since even as unsupported device it can be added as a responder to my scene in ISY.
golfleep Posted December 2, 2012 Posted December 2, 2012 I'm having the same problem as the OP trying to add a dual band relay KPL, and am running 3.3.4. I can successfully add the device, but it comes up as an unsupported device. While it responds, I have no access to the scene buttons via the ISY/My lighting. I also posted in the 3.3.4 thread. Glad to know a few other people have had the same issue, hopefully it can get resolved soon!
Recommended Posts