goldband Posted April 8, 2013 Share Posted April 8, 2013 I have an ISY99i with 6 dual band dimmers and a few dual band switches. I am now trying to add a Mini Remote Insteon 2342-2. When I put the admin console in link mode and enable the setup button (green flashing) on keypad, nothing is recognized. If I use 'New Insteon Device' process and enter the ID, there is no popup for this device. If I leave the setting to audtodiscover I get ' cant determine insteon engine' error. I am very near ISY device and one working dualand switch. Also, if I follow the manual setup procedure, I can get the device to control one of the dimmers, but It never appears in the ISY admin console lists. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 9, 2013 Share Posted April 9, 2013 Hi goldband, Please follow the instructions here: http://wiki.universal-devices.com/index ... emoteLinc2 With kind regards, Michel Link to comment Share on other sites More sharing options...
churbin Posted April 28, 2013 Share Posted April 28, 2013 Trying to link a 2342-2 not a 2444A2. I believe that this is an older model. I have easily linked multiple 2444A2 and 2444A3 remotes. I have tried multiple times to link via 1. "Link Remotelink2" 2. "New Insteon Device" on auto detect 3. "New Insteon Device" selecting "Remotelink 4 Scene and 8 Scene 2444A2" from the dropdown 4. "Link Remotelink" 5. Start linking Start Linking doesnt see it. In all other cases i get the following error: "The following devices could not be added (device address and type) Cannot determine Insteon engine I am very close to the PLM and various dual band devices. What next? Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 28, 2013 Share Posted April 28, 2013 Hi churbin, ISY cannot communicate with your RL. Did you make sure that your RL was in programming mode before doing Link Management | Link a RemoteLinc2? With kind regards, Michel Link to comment Share on other sites More sharing options...
churbin Posted April 28, 2013 Share Posted April 28, 2013 yes definitly in program mode for all tests. linking all the other remotes sitting in the same spot worked fine Link to comment Share on other sites More sharing options...
Michel Kohanim Posted April 28, 2013 Share Posted April 28, 2013 Hi chrubin, The only thing I can recommend is to factory reset the device and make sure it has good battery. Otherwise, I think it's a defective RL. With kind regards, Michel Link to comment Share on other sites More sharing options...
GuitarBuilder Posted May 4, 2013 Share Posted May 4, 2013 I just got a 2342 Mini Remote as well and it has the exact same problem. Hard to believe they would both be defective. Link to comment Share on other sites More sharing options...
GuitarBuilder Posted May 4, 2013 Share Posted May 4, 2013 Update: I was able to link up the Mini Remote with individual ApplianceLincs quite easily; the remote controls the responders without any issues. The ISY however continues to refuse to link with the Mini Remote. It is definitely an ISY issue. Link to comment Share on other sites More sharing options...
LeeG Posted May 4, 2013 Share Posted May 4, 2013 Do not assume an ISY issue. The command sequence for an application to generate the links is different than set button linking. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Put the RemoteLinc2 into linking mode with its Set button and use New INSTEON Device to add the RL2. Post the event trace. The Insteon Mesh network may not be handling the commands an application must use. Link to comment Share on other sites More sharing options...
LeeG Posted May 4, 2013 Share Posted May 4, 2013 GuitarBuilder Perhaps some background will help. The newest I2CS RemoteLinc2 must be able to Set button link with the oldest I1 devices that were sold back in 2005/2006. That compatibility has been maintained forever. However, applications (like ISY) handle the newest I2CS devices with Extended commands which do not even exist in an I1 device. In fact I1 devices do not even repeat Extended messages so Insteon Mesh network can work very differently when doing Set button links versus being processed by an Application. SmartLabs has chosen to drop completely the single byte data management commands used by Applications so frequently in the past. You may not have any I1 devices so this extreme situation may not apply but the Insteon Mesh network does not always have the same reliability with Set button linking versus an Application. Also the PLM plug point is often subject to interference because of what else is powered from the same circuit. It is necessary to understand why the RemoteLinc2 cannot be added to the ISY. Could be a communication problem, could be something new in the latest I2CS RemoteLinc2. An Event Viewer trace is important in determining the actual problem you are having. Link to comment Share on other sites More sharing options...
GuitarBuilder Posted May 6, 2013 Share Posted May 6, 2013 Hi Lee, Thanks for your help; I don't know how relevant this is, but I'm not concerned about a RemoteLinc 2. As far as I can tell, the 2342 is a different animal altogether. Link to comment Share on other sites More sharing options...
LeeG Posted May 6, 2013 Share Posted May 6, 2013 The 2342-xxx Mini Remote was called a RemoteLinc2 when it was first released. There is an 8 Scene, 4 Scene and single Scene model. Like the 2843-xxxx Open/Close Sensor was called a TriggerLinc when first released. Not sure why Smarthome is renaming these products but they are the same products regardless of what Smarthome is calling them today. Perhaps they have decided to get away from so many products being labeled xxxxxxLinc. Sorry if my using the original names has caused any confusion. Link to comment Share on other sites More sharing options...
Brian H Posted May 6, 2013 Share Posted May 6, 2013 The same base part number can then have a different -suffix number for the modules with different RF frequencies or AC power requirements. Used in other countries. RemotrLinc2 UK doesn't sound as good. Link to comment Share on other sites More sharing options...
GuitarBuilder Posted May 9, 2013 Share Posted May 9, 2013 GuitarBuilder Perhaps some background will help. The newest I2CS RemoteLinc2 must be able to Set button link with the oldest I1 devices that were sold back in 2005/2006. That compatibility has been maintained forever. However, applications (like ISY) handle the newest I2CS devices with Extended commands which do not even exist in an I1 device. In fact I1 devices do not even repeat Extended messages so Insteon Mesh network can work very differently when doing Set button links versus being processed by an Application. SmartLabs has chosen to drop completely the single byte data management commands used by Applications so frequently in the past. You may not have any I1 devices so this extreme situation may not apply but the Insteon Mesh network does not always have the same reliability with Set button linking versus an Application. Also the PLM plug point is often subject to interference because of what else is powered from the same circuit. It is necessary to understand why the RemoteLinc2 cannot be added to the ISY. Could be a communication problem, could be something new in the latest I2CS RemoteLinc2. An Event Viewer trace is important in determining the actual problem you are having. Well here's the trace - does that help? What's Reason 3? I get the exact same error message - Cannot Determine Insteon Engine. Direct communications with responders is perfect. Link to comment Share on other sites More sharing options...
LeeG Posted May 9, 2013 Share Posted May 9, 2013 GuitarBuilder Insteon address 1C.4E.02 was sent a command three times (02 62 outbound messages) with no response (no 02 5x inbound message) from the device on any of the three attempts. When an RF battery device does not respond it can be not in manual linking mode so it is asleep not in RF range of a Dual Band device not the correct Insteon address defective device but this is very low on probability list. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted May 9, 2013 Share Posted May 9, 2013 GuitarBuilder, How old/new is the PLM? With kind regards, Michel Link to comment Share on other sites More sharing options...
Buzzhazz Posted December 19, 2013 Share Posted December 19, 2013 The 2342-xxx Mini Remote was called a RemoteLinc2 when it was first released. There is an 8 Scene, 4 Scene and single Scene model. Like the 2843-xxxx Open/Close Sensor was called a TriggerLinc when first released. Not sure why Smarthome is renaming these products but they are the same products regardless of what Smarthome is calling them today. Perhaps they have decided to get away from so many products being labeled xxxxxxLinc. Sorry if my using the original names has caused any confusion. Hi Lee (et al), I'm not a frequent poster because my system is pretty darn reliable, but I am having a heck of a time getting my mini-remote to be recognized by ISY-994. I can link it to a responder manually, but not through the ISY. I have carefully followed all instructions and have performed several factory resets to no avail. My Level 3 event log is attached, and any help would be appreciated. FWIW, I am a woodworker and I have my dust collector controlled by a SwitchLinc switch. The SwitchLinc actually closes a relay which then powers the 2HP dust collector. I want the mini-remote to act as a controller do I can control my dust collector from whatever woodworking machine I happen to be at. I suppose I could just manually link it and be done with it, but I like to understand why things are not working. FYI my firmware is v.4.0.5. Thanks. ISY-Events-Log.v4.0.5__Thu 2013.12.19 10.30.37 AM.txt Link to comment Share on other sites More sharing options...
LeeG Posted December 19, 2013 Share Posted December 19, 2013 The Mini-Remote is not responding to a command as needed. See the Red trace entry below is missing from the posted trace. Thu 12/19/2013 01:16:37 PM : [iNST-TX-I1 ] 02 62 1C 2D 53 0F 0D 00 Thu 12/19/2013 01:16:37 PM : [iNST-ACK ] 02 62 1C.2D.53 0F 0D 00 06 (00) Thu 12/19/2013 01:16:37 PM : [iNST-SRX ] 02 50 1C.2D.53 22.80.0B 27 0D 01 (01) Thu 12/19/2013 01:16:37 PM : [std-Direct Ack] 1C.2D.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 12/19/2013 01:16:37 PM : [iNST-TX-I1 ] 02 62 1C 2D 53 0F 10 00 Thu 12/19/2013 01:16:38 PM : [iNST-ACK ] 02 62 1C.2D.53 0F 10 00 06 ID-REQ (00) Thu 12/19/2013 01:16:38 PM : [iNST-SRX ] 02 50 1C.2D.53 22.80.0B 2B 10 00 ID-REQ (00) Thu 12/19/2013 01:16:38 PM : [std-Direct Ack] 1C.2D.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 12/19/2013 01:16:38 PM : [iNST-SRX ] 02 50 1C.2D.53 00.10.36 8B 02 01 (01) Thu 12/19/2013 01:16:38 PM : [std-Broadcast] 1C.2D.53-->00.10.36, Max Hops=3, Hops Left=2 Thu 12/19/2013 01:16:38 PM : [1C 2D 53 0 ] Calibrating engine version The ISY issued the command 3 times and failed to get the required response in the posted trace. Without that response the ISY does not know it is a Mini-Remote. Link to comment Share on other sites More sharing options...
Buzzhazz Posted December 19, 2013 Share Posted December 19, 2013 The Mini-Remote is not responding to a command as needed. See the Red trace entry below is missing from the posted trace. Thu 12/19/2013 01:16:37 PM : [iNST-TX-I1 ] 02 62 1C 2D 53 0F 0D 00 Thu 12/19/2013 01:16:37 PM : [iNST-ACK ] 02 62 1C.2D.53 0F 0D 00 06 (00) Thu 12/19/2013 01:16:37 PM : [iNST-SRX ] 02 50 1C.2D.53 22.80.0B 27 0D 01 (01) Thu 12/19/2013 01:16:37 PM : [std-Direct Ack] 1C.2D.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 12/19/2013 01:16:37 PM : [iNST-TX-I1 ] 02 62 1C 2D 53 0F 10 00 Thu 12/19/2013 01:16:38 PM : [iNST-ACK ] 02 62 1C.2D.53 0F 10 00 06 ID-REQ (00) Thu 12/19/2013 01:16:38 PM : [iNST-SRX ] 02 50 1C.2D.53 22.80.0B 2B 10 00 ID-REQ (00) Thu 12/19/2013 01:16:38 PM : [std-Direct Ack] 1C.2D.53-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 12/19/2013 01:16:38 PM : [iNST-SRX ] 02 50 1C.2D.53 00.10.36 8B 02 01 (01) Thu 12/19/2013 01:16:38 PM : [std-Broadcast] 1C.2D.53-->00.10.36, Max Hops=3, Hops Left=2 Thu 12/19/2013 01:16:38 PM : [1C 2D 53 0 ] Calibrating engine version The ISY issued the command 3 times and failed to get the required response in the posted trace. Without that response the ISY does not know it is a Mini-Remote. Without understanding the codes, I suspected as much. Any thoughts on getting it to work or do you suspect it is just defective out of the box. As I wrote earlier, it works fine in manual linking, and I have good comm between the ISY and the dozens of other devices I have installed. Link to comment Share on other sites More sharing options...
LeeG Posted December 19, 2013 Share Posted December 19, 2013 Set button linking is connecting one of the buttons as a Controller to a Responder. The Responder is not aware of what the Controller actually is. Adding to the ISY requires knowledge of device specifics such as how many buttons, etc. The missing Broadcast message has that information. What type PLM (2412 or 2413) and what is the firmware level (Tools | Diagnostics | PLM Info/Status)? Link to comment Share on other sites More sharing options...
Buzzhazz Posted December 19, 2013 Share Posted December 19, 2013 Set button linking is connecting one of the buttons as a Controller to a Responder. The Responder is not aware of what the Controller actually is. Adding to the ISY requires knowledge of device specifics such as how many buttons, etc. The missing Broadcast message has that information. What type PLM (2412 or 2413) and what is the firmware level (Tools | Diagnostics | PLM Info/Status)? I have the 2413 and it shows 19.75.b9 v98/Connected. On a side observation, when I factory reset the mini remote in accordance with the manual, I get the proper beeps and LEDs indicating a successful reset, but the remote still controls the responder (which I linked manually). I though a reset would eliminate links. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 19, 2013 Share Posted December 19, 2013 Hi buzzhazzard, I might have some bad news for you: we had another customer with the same exact issue with Leak Sensors and it turned out to be the PLM (v98). Are you certain your PLM is v98 and not v9B? With kind regards, Michel Link to comment Share on other sites More sharing options...
Brian H Posted December 19, 2013 Share Posted December 19, 2013 The link you manually added is still in the responders Link Database and that maybe why you got those results. I have an old original RemoteLinc. If I factory reset it. The All On and All Off buttons still control the devices that where on the individual buttons. Only the individual buttons the factory reset removed. Stopped controlling the devices. Link to comment Share on other sites More sharing options...
Buzzhazz Posted December 19, 2013 Share Posted December 19, 2013 Hi buzzhazzard, I might have some bad news for you: we had another customer with the same exact issue with Leak Sensors and it turned out to be the PLM (v98). Are you certain your PLM is v98 and not v9B? With kind regards, Michel Hi Michel It's v98. I will probably just live with it as i can't imagine having to ever control wy workshop dust collector with the ISY. Everything else is working fine and I have had no problems linking other devices. As I wrote before, I just like to understand how things work and why sometimes they wont. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 20, 2013 Share Posted December 20, 2013 Hi buzzhazard, I do agree with your decision. With kind regards, Michel Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.