Jump to content

Workaround to Link a 2432-2 Mini Remote


Recommended Posts

Hardware

I just received four 2432-2 Mini Remotes marked with the following:

Mini Remote
Model: 2342-2
FCC ID: SBP23422
IC: 5202A-23422
v1.5s 1441

I am using an ISY994i/IR PRO (1110) with firmware v.4.2.18.

 

Problem

The procedure in the wiki does not work correctly.  Specifically, regardless of whether you select 4-scene keypad or 8-scene keypad, after linking, the ISY always regards the Mini Remote as being in 8-scene mode (you can see this from the radio buttons in the admin console), and the Mini Remote is always configured to be in 8-scene toggle mode (you can tell this from the button flash pattern in the manual).  

 

Workaround

To get the Mini Remote link and in 4-scene mode or 8-scene non-toggle mode.  Do the following:

  • Perform a factory reset of the Mini Remote
  • Link the Mini Remote with the ISY as per the wiki procedure.  
  • Both the ISY and Mini Remote should now be in 8-scene toggle mode.
  • Change the radio button to 4-scene or 8-scene non-toggle mode in the ISY admin console.  Click "Yes" to proceed.  Ignore all the errors and warnings.
  • The ISY admin console should now show the mode you selected.
  • Manually change the Mini Remote to the same toggle mode you just selected in the ISY by following the procedure in the manual.
  • The "current state" for the Mini Remote buttons in the ISY console should now update correctly in the ISY Admin Console when you press a button on the remote.

You should now be able to use the remote in your programs.

 

Alex

Link to comment
Share on other sites

Can you run Tools | Diagnostics | Event Viewer at LEVEL 3.

 

Put the Mini Remote into linking mode and change the mode to something different. Please post the event trace.

 

Beyond the message confirming the action and popup instructions for putting the Mini Remote into linking mode, there should be no errors.

 

EDIT: for the benefit of others who read this topic the Mini Remote has a 50' RF limit compared to a Keypad which has 150'. These are clear line of site distances. I suggest positioning the Mini Remote near the 2413 PLM when adding to ISY and doing Scene work containing the device.

Link to comment
Share on other sites

Hi Lee,

 

Here is the event log you asked for.  If this is, in fact, a problem of insteon communications during linking, then the ISY ought to report it as such in the same way as other communication errors.  In this case, though, during the linking operation the ISY admin console mentions no error and displays the device with no exclamation points:

 

PlbMKmV.png

 

Alex

Link to comment
Share on other sites

I was referring to the errors you mentioned in your post changing modes.

"Change the radio button to 4-scene or 8-scene non-toggle mode in the ISY admin console. Click "Yes" to proceed. Ignore all the errors and warnings."


Comm with the Mini Remote is at the extreme limit, Max Hops=3, Hops Left=0. Any interference will produce errors as there is no place to go with Hops Left=0 but failure.

Sat 03/07/2015 04:52:21 PM : [iNST-TX-I1 ] 02 62 2E EC 14 0F 0D 00

Sat 03/07/2015 04:52:21 PM : [iNST-ACK ] 02 62 2E.EC.14 0F 0D 00 06 (00)

Sat 03/07/2015 04:52:21 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 23 0D 02 (02)

Sat 03/07/2015 04:52:21 PM : [std-Direct Ack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Sat 03/07/2015 04:52:21 PM : [iNST-TX-I1 ] 02 62 2E EC 14 0F 10 00

Sat 03/07/2015 04:52:22 PM : [VAR 2 7 ] 11990

Sat 03/07/2015 04:52:22 PM : [iNST-ACK ] 02 62 2E.EC.14 0F 10 00 06 ID-REQ (00)

Sat 03/07/2015 04:52:22 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 23 10 00 ID-REQ (00)

Sat 03/07/2015 04:52:22 PM : [std-Direct Ack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Sat 03/07/2015 04:52:22 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 23 10 00 ID-REQ (00)

Sat 03/07/2015 04:52:22 PM : [std-Direct Ack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Sat 03/07/2015 04:52:22 PM : [iNST-SRX ] 02 50 2E.EC.14 00.12.37 83 02 15 (15)

Sat 03/07/2015 04:52:22 PM : [std-Broadcast] 2E.EC.14-->00.12.37, Max Hops=3, Hops Left=0

Link to comment
Share on other sites

Hi Lee,

Thanks for your help.  The number of hops indeed explains the errors I saw and ignored previously when attempting to change the Mini Remote to 4-scene from the admin console.  Moving the Mini Remote right beside the modem and then changing the radio button to 4-scene resulted in the ISY showing success without errors.  Here is the pastebin of that log.  All the "Hops Left" are 2 which is an improvement.

 

The problem remains, however, that the Mini Remote stays in 8-scene toggle mode and is not switched to the 4-scene mode shown in the admin console.  This is so despite the ostensibly error-free change of mode from the admin console.  So I still have to follow the procedure in my OP and manually change the Mini Remote to 4-scene mode.  

 

Alex

Link to comment
Share on other sites

The link records for the 8 button mode were deleted successfully .  However, the attempt to switch modes failed.  The 0xFD was hard to find the last time this error was posted.   I'll research this and post back when I find the cause of the FD.

 

Sat 03/07/2015 06:51:01 PM : [2E EC 14 1 ] Memory : Write dbAddr=0x1005 [0F] cmd1=0x20 cmd2=0x0F

Sat 03/07/2015 06:51:01 PM : [iNST-TX-I1 ] 02 62 2E EC 14 0F 20 0F

Sat 03/07/2015 06:51:01 PM : [iNST-ACK ] 02 62 2E.EC.14 0F 20 0F 06 (0F)

Sat 03/07/2015 06:51:02 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 AB 20 FD (FD)

Sat 03/07/2015 06:51:02 PM : [std-Direct Nack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sat 03/07/2015 06:51:02 PM : [2E EC 14 1 ] Memory : Write dbAddr=0x1004 [09] cmd1=0x20 cmd2=0x09

Sat 03/07/2015 06:51:02 PM : [iNST-TX-I1 ] 02 62 2E EC 14 0F 20 09

Sat 03/07/2015 06:51:02 PM : [iNST-ACK ] 02 62 2E.EC.14 0F 20 09 06 (09)

Sat 03/07/2015 06:51:02 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 AB 20 FD (FD)

Sat 03/07/2015 06:51:02 PM : [std-Direct Nack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sat 03/07/2015 06:51:02 PM : [VAR 2 7 ] 12702

Sat 03/07/2015 06:51:03 PM : [14 66 7C 1 ] Link 1 : 0FF0 [A2232A1E77014E16] Writing [..............16]

 
Link to comment
Share on other sites

The only description I have found for the Nack  value of 0xFD is bad checksum which makes no sense since these are Standard commads.

 

Sat 03/07/2015 06:51:01 PM : [2E EC 14 1 ] Memory : Write dbAddr=0x1005 [0F] cmd1=0x20 cmd2=0x0F
Sat 03/07/2015 06:51:01 PM : [iNST-TX-I1 ] 02 62 2E EC 14 0F 20 0F
Sat 03/07/2015 06:51:01 PM : [iNST-ACK ] 02 62 2E.EC.14 0F 20 0F 06 (0F)
Sat 03/07/2015 06:51:02 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 AB 20 FD (FD)
Sat 03/07/2015 06:51:02 PM : [std-Direct Nack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 03/07/2015 06:51:02 PM : [2E EC 14 1 ] Memory : Write dbAddr=0x1004 [09] cmd1=0x20 cmd2=0x09
Sat 03/07/2015 06:51:02 PM : [iNST-TX-I1 ] 02 62 2E EC 14 0F 20 09
Sat 03/07/2015 06:51:02 PM : [iNST-ACK ] 02 62 2E.EC.14 0F 20 09 06 (09)
Sat 03/07/2015 06:51:02 PM : [iNST-SRX ] 02 50 2E.EC.14 2A.1E.77 AB 20 FD (FD)
Sat 03/07/2015 06:51:02 PM : [std-Direct Nack] 2E.EC.14-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 

 

The same set of commands to my Mini Remotes work fine.

 

Sun 03/08/2015 09:28:34 PM : [1C 27 E3 1  ] Memory : Write dbAddr=0x1005 [0F] cmd1=0x20 cmd2=0x0F

Sun 03/08/2015 09:28:34 PM : [iNST-TX-I1  ] 02 62 1C 27 E3 0F 20 0F
Sun 03/08/2015 09:28:34 PM : [iNST-ACK    ] 02 62 1C.27.E3 0F 20 0F 06                 (0F)
Sun 03/08/2015 09:28:34 PM : [iNST-SRX    ] 02 50 1C.27.E3 22.80.0B 2B 20 0F           (0F)
Sun 03/08/2015 09:28:34 PM : [std-Direct Ack] 1C.27.E3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 03/08/2015 09:28:34 PM : [1C 27 E3 1  ] Memory : Write dbAddr=0x1004 [09] cmd1=0x20 cmd2=0x09
Sun 03/08/2015 09:28:34 PM : [iNST-TX-I1  ] 02 62 1C 27 E3 0F 20 09
Sun 03/08/2015 09:28:35 PM : [iNST-ACK    ] 02 62 1C.27.E3 0F 20 09 06                 (09)
Sun 03/08/2015 09:28:35 PM : [iNST-SRX    ] 02 50 1C.27.E3 22.80.0B 2B 20 09           (09)
Sun 03/08/2015 09:28:35 PM : [std-Direct Ack] 1C.27.E3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
The only difference I have found is your Mini Remote is v37 where mine are v36.  I will order some new Mini Remotes and see if something has changed the command requirements.
Link to comment
Share on other sites

Thanks for helping get to the bottom of this Lee,

My v.37 Mini Remotes came from aartech.ca's inventory two weeks ago.  I'm happy to test a fix at my end if you have one.  The best way to contact me is twitter @alx9r.

 

Thanks again,

 

Alex

Link to comment
Share on other sites

Thanks Alex for posting this, and thanks to Lee for looking into it! I was having the same problem. I changed a v.36 from 4 scene to 8 just fine, but I couldn't get the v.37 to convert thru the admin console, finally did it manually after reading this post.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...