Cannot add Mini Remote (2342-2)

[FredT]

I have seen other posts about difficulties adding this device. It seem the solutions others worked out don't for me.

 

I have recently purchased an ISY-994i to replace my 99, specifically because of this problem. I have also upgraded the 994's firmware to V4.1.1.

 

I've attempted to add it as a RemoteLinc2 and generic Insteon device to no avail. Every attempt results in the dreaded "Cannot determine Insteon Engine" and the following is shown in the Event Viewer:

Fri 02/07/2014 11:44:22 AM : [26 88 6C ] Added to list of devices to link to ISY

Fri 02/07/2014 11:44:44 AM : [26 88 6C 0 ] Failed to add device, reason 3

Fri 02/07/2014 11:44:44 AM : [All ] Writing 0 bytes to devices

 

I've set the remote to factory defaults.

 

The particular Mini Remote is: 2342-2 v1.4 1337.

 

Help!!

 

...Fred

[LeeG]

Was the Mini Remote put into linking mode before adding to the ISY and is the Mini Remote close to a Dual Band device?

 

EDIT: put the event viewer into LEVEL 3 to see the actual commands issued and what the response if any is.

[FredT]

Was the Mini Remote put into linking mode before adding to the ISY

If you mean just prior, no. If you mean ever, then less; it is linked to some switches now.

 

 

is the Mini Remote close to a Dual Band device?

Yes, it works fine controlling the linked switches.

 

 

put the event viewer into LEVEL 3 to see the actual commands issued and what the response if any is.

Fri 02/07/2014 01:20:08 PM : [26 88 6c ] Added to list of devices to link to ISY

Fri 02/07/2014 01:20:08 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00

Fri 02/07/2014 01:20:08 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00)

Fri 02/07/2014 01:20:17 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00

Fri 02/07/2014 01:20:17 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00)

Fri 02/07/2014 01:20:25 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00

Fri 02/07/2014 01:20:25 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00)

Fri 02/07/2014 01:20:29 PM : [26 88 6C 0 ] Failed to add device, reason 3

Fri 02/07/2014 01:20:29 PM : [All ] Writing 0 bytes to devices

[LeeG]

The Mini Remote like all battery devices has to be put into linking mode with its Set button just before doing the add to the ISY. Otherwise the device is asleep (turned RF Off to conserve battery) and cannot receive commands.

 

The event trace is showing device 26.88.6C did not respond to the three attempts to send it a command. This is what happens if the battery device is not put into linking mode.

[FredT]

The Mini Remote like all battery devices has to be put into linking mode with its Set button just before doing the add to the ISY. Otherwise the device is asleep (turned RF Off to conserve battery) and cannot receive commands.

 

The event trace is showing device 26.88.6C did not respond to the three attempts to send it a command. This is what happens if the battery device is not put into linking mode.

By "linking mode", I assume you mean holding the link button until the LED flashes green as I did when I linked it to the wall switches.

 

Just tried that but sadly the same result:

 

Fri 02/07/2014 02:11:12 PM : [26 88 6C ] Added to list of devices to link to ISY

Fri 02/07/2014 02:11:12 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00

Fri 02/07/2014 02:11:12 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00)

Fri 02/07/2014 02:11:20 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00

Fri 02/07/2014 02:11:21 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00)

Fri 02/07/2014 02:11:29 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00

Fri 02/07/2014 02:11:29 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00)

Fri 02/07/2014 02:11:33 PM : [26 88 6C 0 ] Failed to add device, reason 3

Fri 02/07/2014 02:11:33 PM : [All ] Writing 0 bytes to devices

 

Do I need to do anything to the PLM?

[LeeG]

Nothing but putting the Mini Remote into linking mode before adding it to the ISY (using Set button as you described). With it in linking mode the next area would be is it near a Dual Band device that has good communication with the PLM.

[LeeG]

Also double check the .88. are eights and not B's.

[FredT]

I thought all I needed to do was to wake the RemoteLinc by toggling one of its switches just prior to linking with the ISY.

 

My PLM is dual mode and I am doing the linking attempts in the same room, about 10 ft. from the PLM. I tried again from about 5 ft. and again at about 2 ft. Still same.

 

I know I have the correct address because I can check it using the UDI admin console by display the link tables of devices (switches) that I have linked to it.

 

I have another, much older RemoteLinc 2 (V1.1) that I had already linked to the ISY years ago. It works fine when used at the same location.

[LeeG]

"I thought all I needed to do was to wake the RemoteLinc by toggling one of its switches just prior to linking with the ISY. "

 

All battery devices have to be put into linking mode with their Set button before the ISY (or any app) can communicate with it. Otherwise the device is asleep and cannot receive commands.

[FredT]

"I thought all I needed to do was to wake the RemoteLinc by toggling one of its switches just prior to linking with the ISY. "

 

All battery devices have to be put into linking mode with their Set button before the ISY (or any app) can communicate with it. Otherwise the device is asleep and cannot receive commands.

Yes, I've been doing as you say. Just wasn't aware it was necessary.

 

But sorry to say, still does not work even when I place the Mini within 2 feet of the dual band PLM.

 

Although the two remotes I own look identical, the older remote is a RemoteLinc2 Model 2444A2 v1.1 and works as expected with the ISY. The new remote is a Mini Remote Model 2342-2 v1.4 and is being very stubborn with the ISY. Is there any significants to this difference?

[Brian H]

LeeG;

 

If the latest shipping products data we Developer Group members got is correct.

 

Smartlabs changed the Sub Cat ID for the 2342-222 8 Scene, 2342-232 4 Scene and 2342-242 RemotrLinc2s and I don't see those latest Sub Cat IDs in the drop down list. Would that contribute to the problems?

 

I believe the Sub Cats where changed. As I now see International RF frequency one also listed with their own unique Sub Cat IDs.

[LeeG]

Brian, thanks for the data. It could be an issue later but now the device is not responding to the first command which is asking for the Insteon Engine. Even old devices respond to this command with an I1 indicator. This Mini Remote is not sending any response as though it did not receive the command to begin with. This is what the beginning of the trace should look like...

 

Sat 02/08/2014 01:31:36 PM : [1c 27 e3 ] Added to list of devices to link to ISY

Sat 02/08/2014 01:31:36 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 0D 00

Sat 02/08/2014 01:31:36 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 0D 00 06 (00)

Sat 02/08/2014 01:31:36 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 27 0D 01 (01)

Sat 02/08/2014 01:31:36 PM : [std-Direct Ack] 1C.27.E3-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

The Blue message above is the device response that is missing from the OP device

 

Sat 02/08/2014 01:31:36 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 10 00

Sat 02/08/2014 01:31:36 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 10 00 06 ID-REQ (00)

Sat 02/08/2014 01:31:37 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 2B 10 00 ID-REQ (00)

Sat 02/08/2014 01:31:37 PM : [std-Direct Ack] 1C.27.E3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sat 02/08/2014 01:31:37 PM : [iNST-SRX ] 02 50 1C.27.E3 00.12.36 87 02 01 (01)

Sat 02/08/2014 01:31:37 PM : [std-Broadcast] 1C.27.E3-->00.12.36, Max Hops=3, Hops Left=1

 

If the Mini Remote had responded to the first command it would be asked what type of device it is. This is where the cat/subcat/firmware is returned and could be an issue. This is an 8 button Mini Remote with a cat=00 subcat=12

[FredT]

LeeG:

 

Still doesn't work. What next?

 

My problem doesn't seem to be too different than that reported by goldband in April 2013 GuitarBuilder in May and buzzhazard in December in this thread:

viewtopic.php?f=28&t=11233&hilit=2342

 

It seems they gave up without a resolution. I think my problem is not unique to me. I'm not sure whether this is an UDI or SmartLabs issue. But, as a customer of both, I'd be annoyed if the two companies couldn't come together with a solution. Can't be that hard.

 

...Fred

[LeeG]

The device must respond to the Insteon Engine query. It is the first command issued by the ISY with the returned data being critical to knowing what the device requires. An I2CS device has very different requirements than an I2 device and the Insteon Engine Query is the command that provides that data. The device does not respond either because the command did not reach the device or the device response did not reach the PLM (if a response was sent). If using a Dual Band PLM (2413) try moving the Mini Remote near the PLM. Can also try a Factory Reset of the Mini Remote.

[FredT]

Finally got it to work.

 

Moving the remote closer to the PLM did not help, I had tried that many times before. Same for the factory reset.

 

Then I got the idea to move it closer to some other dual band devices. First near a back of three recently purchased SwitchLincs that are on another AC phase, only five feet from the PLM but on the other side of a common wall. Still no joy.

 

Then I thought to try something on the same AC phase as the PLM. I tried a brand new on/off module that I had purchased for the Christmas tree, but hadn't used. Plugged it in, set the remote to linking mode, and put it down about five feet from the module. Presto, the ISY was able to link to it.

 

Once linked, the on/off module is not needed. The ISY sees button presses on the remote and can respond with complex commands as I had wanted.

 

I'm guessing that for some reason the remote was having problems seeing the engine query. Could be a weak receiver on the remote or some interference or a combination. The ISY has absolutely no problem sense key presses on the remote in any room in my house. So what the communication problem was, it was asymmetrical.

 

...Fred

[Brian H]

Thanks for the updated information.

Though quite a strange set of circumstances.