erniekraut Posted March 6, 2015 Share Posted March 6, 2015 I have replaced my Smartlabs 2414 USB PowerLinc V2 and "InHomeFre" Windows PC software with my new ISY-994i and cannot get my Smartlabs RemoteLinc #2440 to link with my ISY-994i. I have put new batteries into the RemoteLinc and placed the RemoteLinc near the AccessPoint for each of the two legs of power in my house and also near a dual-band LampLinc. The RemoteLinc DOES still control the Insteon devices originally linked - one scene of four devices and three individual devices. The RemoteLinc controls these devices at all locations in my house. When I enter the data in the "Link a RemoteLinc" window, put my RemoteLinc into linking mode by pressing the first button (Scene A) for 10 seconds until the LED blinks and then click on the "OK" button in the "Link a Remotelinc" window, I end up getting a message "The following devices could not be added: OA.38.OE (2440) RemoteLinc v.00 - cannot determine Insteon Engine" The label inside the battery compartment of my Remote Linc reads 1208 Rev1.0 0A.38.0E Is there some way I can link my remote or must I buy some type of new remote control and throw away my operational RemoteLinc? Thanks in advance - I'm really puzzled. Ernie Link to comment
LeeG Posted March 6, 2015 Share Posted March 6, 2015 To add the RemoteLinc to the ISY press DIM/BRIGHT buttons until RemoteLinc LED blinks. Use New INSTEON Device or click Link a RemoteLinc which takes you to the New INSTEON Device popup. Enter the Insteon address of RemoteLinc and Name of your choice. Have the RemoteLinc near the 2413 PLM when Ok is clicked. Link to comment
erniekraut Posted March 7, 2015 Author Share Posted March 7, 2015 Thank you, Lee. I tried your suggestion and I'm still getting the "cannot determine Insteon Engine" message. I'm wondering if it is so old that the 2440 Ver 1.0 firmware is not supported. Link to comment
stusviews Posted March 7, 2015 Share Posted March 7, 2015 A few of us have been having difficulty with RemoteLincs. Search for 2440 Link to comment
LeeG Posted March 7, 2015 Share Posted March 7, 2015 erniekraut What ISY firmware is being used, Help | About, Firmware and UI levels? Run Tools | Diagnostics | Event Viewer at LEVEL 3. After putting RemoteLinc into linking mode with DIM/BRIGHT buttons, use New INSTEON Device to add RemoteLinc. Position RemoteLinc near 2413 PLM and be sure the RemoteLinc has new batteries. Post the event trace. There is an Icon on the bottom right side of Event Viewer popup for Copy to Clipboard. Then Paste event trace. Link to comment
LeeG Posted March 7, 2015 Share Posted March 7, 2015 erniekraut I do not think there is an issue with the RemoteLinc as a particular device. Being that it is an older generation device it uses the older 1 byte commands. This means that some 250+ Insteon messages must flow successfully to add the RemoteLinc. There are many Insteon networks that cannot handle that volume of load. In addition the RemoteLinc is RF only so that means more than 250 Insteon RF messages must flow successfully. That requires a good Insteon network. I've added my RemoteLinc to the ISY several times using 4.2.23 with no problems. I have a good Insteon network because I have worked hard to achieve that. There are some folks who do not appreciate the amount of Insteon work that is needed to both add a RemoteLinc and define Scenes using the RemoteLinc buttons. They blame the RemoteLinc or the ISY for what is an Insteon network issue. The event trace will show the nature of the problem. Link to comment
hart2hart Posted March 7, 2015 Share Posted March 7, 2015 They are very finicky. I worked several hours to find that holding remotelinc in my hand at specific angle to access point made it add and update 100%. The process involved putting it into link mode., adding device with event viewer turned on at level 3, holding and rotating RL very slowly about 5 feet from AP and watching event viewer for messages to start flowing. Not very high tech but it works. I have couple very early generation RL and they work fine with latest ISY FW. Link to comment
blueman2 Posted March 20, 2015 Share Posted March 20, 2015 Exact same issue here. I had to replace my PLM and now I cannot communicate to my Remotelinc 2440. I deleted it, re-added it, and it adds along with all 6 buttons, but it continues to show the '010101' icon and gives failure message on trying to write. Exact same message as I have read in several other posts on the 2440. I have added and removed it 4 times, done factory reset 4 times. Used all different ways to add (2440, auto). Tried restore with no joy as well. Using a new 2413S V2 PLM with 9E firmeware, and 4.2.28 on my ISY and java. Link to comment
blueman2 Posted March 20, 2015 Share Posted March 20, 2015 OK, I finally got it to write and it now works. The trick, as people have mentioned, is location. I had the remotelinc in the same room as the new PLM I just installed. When I moved the remotelinc across the house away from the PLM, it worked just fine. Apparently, this new PLM (2413S) has a bad radio. Same issue with other remotes that are used anywhere near this PLM. I think I may need to return it. Link to comment
jckinneman Posted May 11, 2015 Share Posted May 11, 2015 Working with support I did the move it closer to PLM and keep trying steps to no avail. I came across this posting and when I moved it over 40 feet away it programmed immediately. The remote appears to work OK while near the PLM once it has been programmed. Link to comment
Teken Posted May 11, 2015 Share Posted May 11, 2015 Working with support I did the move it closer to PLM and keep trying steps to no avail. I came across this posting and when I moved it over 40 feet away it programmed immediately. The remote appears to work OK while near the PLM once it has been programmed. Based on all the forum replies this hardware 2 PLM appears to have a stronger RF output. Which must be impacting the reception portion. Standing RF waves are obviously at play here because if you're further than the PLM this indicates over powering the receiver and not the transmission. Ideals are peaceful - History is violent Link to comment
dstanley Posted June 4, 2015 Share Posted June 4, 2015 I am still having issues trying to write updates to one of these older RemoteLincs. the unit works and does what it is supposed to do but a change of an associated KPL has it wanting to have updates written to it. Attached is my log of the attempt to to write these updates ... I don't know how to read this. Dwight ISY-Events-Log.v4.3.1__Wed 2015.06.03 09.25.24 PM.txt Link to comment
LeeG Posted June 4, 2015 Share Posted June 4, 2015 The RemoteLinc is not responding to some commands. The ISY will try three times and if all fail the update stops. The line marked in Red got no response from RemoreLinc. I have not seen this locally with my RemoteLinc but some users have indicated a better experience with the old RemoteLinc when it is further away from Dual Band device. Seems like the signal strength can overload a Dual Band device when updates are done with the RemoteLinc near a Dual Band device. Wed 06/03/2015 09:24:01 PM : [11 C3 68 1 ] Link 0 : 0FF8 [E20130E715010001] Writing [E20130E715010001] Wed 06/03/2015 09:24:01 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:01 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:01 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 28 0F SET-MSB(0F) Wed 06/03/2015 09:24:01 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:01 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 2B F8 Wed 06/03/2015 09:24:01 PM : [iNST-ACK ] 02 62 11.C3.68 0F 2B F8 06 PEEK (F8) Wed 06/03/2015 09:24:03 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 2B E2 PEEK (E2) Wed 06/03/2015 09:24:03 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:03 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:03 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:12 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:12 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:21 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:21 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:24 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 28 0F SET-MSB(0F) Wed 06/03/2015 09:24:24 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:24 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 2B F9 Wed 06/03/2015 09:24:24 PM : [iNST-ACK ] 02 62 11.C3.68 0F 2B F9 06 PEEK (F9) Wed 06/03/2015 09:24:26 PM : [iNST-SRX ] 02 50 11.C3.68 2F.BA.01 2F 2B 01 PEEK (01) Wed 06/03/2015 09:24:26 PM : [std-Direct Ack] 11.C3.68-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 06/03/2015 09:24:26 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:26 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:35 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:35 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:44 PM : [iNST-TX-I1 ] 02 62 11 C3 68 0F 28 0F Wed 06/03/2015 09:24:44 PM : [iNST-ACK ] 02 62 11.C3.68 0F 28 0F 06 SET-MSB(0F) Wed 06/03/2015 09:24:48 PM : [11 C3 68 1 ] Link 0 : 0FF8 [E20130E715010001] *Failed Writing [E20130E715010001] Link to comment
Brian H Posted June 4, 2015 Share Posted June 4, 2015 I also had issues with a V2.1 9E firmware. The 2440 would not be found if next to the PLM. If I moved it far away it was. Then I tried it again far away but with no other Dual Band Devices powered up. Again no access. My thoughts are the latest PLM or firmware. Can use a power line signal to another Dual Band Device for the 2440 but not its own RF processing. Also could be overloaded by the RF signal as other have thought. Link to comment
grossmd Posted October 30, 2016 Share Posted October 30, 2016 Hey guys, I realize this is an old post but came upon this same problem tonight after replacing PLM and moving remote away worked instantly. Thanks! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.