ulrick65 Posted October 8, 2017 Posted October 8, 2017 I have 4.6.2 of both the firmware and UI. I have many older model switchlinks and keypads links (several versions from 2008/2009 time frame) all working fine. I purchased a couple leak sensors, and they linked up and work fine. I just bought a few brand new 2477D's and 2334-232 keypadlincs because I wanted to see if I could use these to get rid of the access point bricks I have around the house (I also have the Signalinc in the panel, but I seem to do better with the access points...in fact I have no communications at all...everything works without a hitch). Now on to my problem: I can't get any of the new dual band devices to connect. I have an extension cord that I use for linking and testing and I can link many devices without a problem...but I try one of these and ISY does not "see" them when I press and hold the set button. I have tried also manual linking, but it tells me it can't figure out the device. I have factory reset them all, no go. I assume I am linking correctly (same as the old ones...hold in the set button for 3 to 5 seconds). The switchlinc is Rev 8.2 1817 The keypadlinc is Rev 8.8 1317 I can't believe I have a bunch of defective devices...so what am I doing wrong with these new fangled things? They beep at me, flash the lights, etc. but I can't seem to find anywhere to tell me what the beeps mean. When I factory reset, I get that one...I get the long beep..it stops..I let go of the button and it reboots fine. On the switchlinc, I put ISY in link mode, press the set button in after a couple seconds it beeps once...then the green light starts flashing but ISY doesn't "see" anything. I am well in range of the access points, if that matters...I even brought a new leak sensor to the same spot and linked it no problem (RF only as you know). UPDATE: I have now tried 5 different units (3 switchlincs, 2 keypadlincs and a 2477S on/off Switch)...none of them link. I looked at event viewer and I don't see anything coming from any of these, even when I do the on/off buttons...nothing in event viewer. I am beginning to wonder if whatever "language" these new units talk in my old 2412S v63 doesn't speak the lingo...anyone have an idea if that might be the case? Any help would be appreciated... Thanks.
larryllix Posted October 8, 2017 Posted October 8, 2017 Only battery devices need to be put in linking mode. The rest require to not be in linking mode.
ulrick65 Posted October 8, 2017 Author Posted October 8, 2017 Only battery devices need to be put in linking mode. The rest require to not be in linking mode. I am not sure what you mean? I put ISY into Linking Mode (I get the popup) and then I press the set button on the device for 3 to 5 seconds and ISY recognizes it and pops it up in another window "to be added" and then I click finish. That how I have always linked devices...is there something different I need to do with these new ones? Thanks
Brian H Posted October 8, 2017 Posted October 8, 2017 The way most of us use. Link Management. New Insteon Device Input the six digit Insteon ID from the label on the module. {ex. AC.B3.35} Give it a name. Use the Auto Discover method. With this method. Only battery operated module have to be taken out of their power saving mode. With the Set Button.
stusviews Posted October 8, 2017 Posted October 8, 2017 There are three methods for adding devices to the ISY. Except for a few devices, it really doesn't matter which method you use. Sometimes, one method will work whereas another won't. In that case, try a different way. But mostly when a device won't add it's because of a mismatch between the UI and firmware. Check that first.
ulrick65 Posted October 8, 2017 Author Posted October 8, 2017 Thanks for the replies. I use both methods as well in the past but with this being a complete new install, I have been using the "start linking" method for everything now. I tried the "New Insteon Device" method, both without pressing the set button and with pressing the set button...I get the same result, no joy. I ordered a new PLM as mine is a 2412S (I have another thread where Michel answered and the conversation kind of went that way about this issue here). I will see how the new PLM works, but I am still unclear on why the 2412S wont "see" anything from the new Dual Band devices. I assumed the PL protocol, etc. was the same... Anyway, I ordered a new one. If anyone can explain why the 2412S doesn't work I would love to learn. Thanks.
stusviews Posted October 8, 2017 Posted October 8, 2017 Are both the UI and firmware identical? If something is keeping the old PLM from recognizing the devices, then that same something will prevent the new PLM from recognizing the same devices.
Brian H Posted October 8, 2017 Posted October 8, 2017 The newer Insteon Module now use the I2CS {I2 with check sum} communications protocol. I have not seen anything on the 2412S not handling it. It does have a slower processor and memory. Doubt it but maybe a speed thing or Link Database Size. Real old hardware was 417 Links later >2000. You could always run the Event Viewer in Level 3 and see what the messages between the module and the PLM are doing.
ulrick65 Posted October 9, 2017 Author Posted October 9, 2017 Are both the UI and firmware identical? If something is keeping the old PLM from recognizing the devices, then that same something will prevent the new PLM from recognizing the same devices. Yes, 4.6.2 and both identical. The newer Insteon Module now use the I2CS {I2 with check sum} communications protocol. I have not seen anything on the 2412S not handling it. It does have a slower processor and memory. Doubt it but maybe a speed thing or Link Database Size. Real old hardware was 417 Links later >2000. You could always run the Event Viewer in Level 3 and see what the messages between the module and the PLM are doing. I have run the Event Viewer level 3. It never shows anything from any of the new devices I have purchased (2 keypadlincs, 2 switchlinc dimmers and I also tried a 2477S on/off switch), I am using a cord, plugged directly into the PLM. I have dozens of other switches and no issues. I have disconnected the new one, connected an older switchlinc dimmer to the exact same cord and all the traffic shows up in ISY (as well as all the traffic in my house) but no matter what, none of these new switches even make an entry in the event log level 3. I even connected two of them at the same time, linked them both together manually with the set buttons and they link and then control eachother, turn on the load, etc. That is why I figured the 2412S was the culprit...not sure what else it could be. I have over 20 devices installed in the house now, from switchlincs to keypadlinc to micro dimmers and leak sensors and everything works flawlessly. So either I got a box full of bad mixed devices (3 different models) or something is not compatible with the 2412S. Weird thing for sure... Anyone actually have new devices (dual band) running with a 2412S? Thanks.
ulrick65 Posted October 12, 2017 Author Posted October 12, 2017 I wanted to update the thread with my findings. Upgrading to the new PLM worked like a charm. The upgrade process went smoothly and all devices are now working properly. I guess that confirms that the 2412s was not compatible with the new switches. Also, I did notice a performance improvement in the network...definitely a lot faster updating links, creating scenes, etc. Thanks for all the help.
f11 Posted December 3, 2017 Posted December 3, 2017 Eric, I find I may be in the same situation you were, right down to using an aging 2412s PLM to talk to both "old" and "new" insteon devices. One of my old RemoteLinc hand controllers is giving me grief after I had to reset it and relink to my ISY, whereas direct device-to-device linking works flawlessly. I assume you bought the "new" 2413S (Serial) PLM, but thought I'd ask anyway. Its been a couple months since you posted your solution - is everything still working well? Thanks for posting your experiences here - I'd have been lost in my problem without reading your observations !
ulrick65 Posted December 7, 2017 Author Posted December 7, 2017 Yes, upgrading solved it all. System is working perfectly now. I have devices from 2008 running alongside brand new ones and no issues. Thanks.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.