Jump to content

RemoteLink 2 2444 Support?


Guest edilks

Recommended Posts

I installed 3.1.10 beta which is supposed to include support for the RemoteLinc 2.

 

When installing using 'Link a RemoteLink" I don't see a dropdown specifically for the RemoteLink 2, only the model 2440. I have a RemoteLinc 2, model 2444A2 (8 button). How do I install it?

Link to comment

Brian, I don't see the 2444 in the dropdown list, all I see is the "[00.05] (2440) RemoteLinc" entry. Can you tell me what list entry I should be selecting (or seeing)? Am I not seeing a newer list due to a cache issue?

Link to comment

edilks

 

Check Help | About to insure 3.1.10 is installed. Clear the Java cache and be sure to use the URL that invokes the 3.1.10 level of the Admin Console. The RemoteLinc2 entries are very near the top of the Device Type pulldown list if running 3.1.10 Admin Console. If they are not in the list the 3.1.10 Admin Console is not being invoked or the Java cache was not cleared.

 

Lee

Link to comment

Much better. Thanks.

Misunderstood I had to clear the java cache on installation. Thought it was not required for the released version I was upgrading from.

 

Remote works as expected. Good except for the problem with the button mis-organization which I read about in another topic.

Link to comment

Hi! I am trying to get my iIISY99 to see my remotelinc 2 and I followed the above steps but cannot find the remotelinc 2 in the device type pulldown list. Help-about tells me I am using the administrative console version 3.1.11, and I just updated Java to version 6, update 29. I have tried clearing the Java's cache, restarting my computer, but no luck...the remotelinc 2 device does not show up in the device pulldown list.

 

 

What am I doing wrong...??

Link to comment

The Help | About is the firmware level of the ISY, not the Admin Console. If the RemoteLinc 2 device types are not near the top of the Device Type pulldown list it is not the Admin Console for 3.1.10. Clear the Java cache and be sure to use the URL that invokes 3.1.10 Admin Console.

Link to comment

stef2

 

There is another possibility. 3.1.10 must be installed before installing 3.1.11. If 3.1.11 was installed without going to 3.1.10 first the 3.1.10 Admin Console will not be on the ISY as 3.1.11 is a fix to the ISY image only, there is no UI in the 3.1.11 install.

 

Lee

Link to comment

I just installed my first RemoteLinc 2. The strange thing is the numbering of the buttons is right to left then top to bottom (almost like the put the board in backwards). Not what I'd expect. Instead of:

 

A=1

B=2

C=3

D=4

etc.

 

What it has is:

A=2

B=1

C=4

D=3

etc.

 

Anyone else seeing this? It does seem work and I'll rename them anyway but it just took me by surprise.

Link to comment
stef2

 

There is another possibility. 3.1.10 must be installed before installing 3.1.11. If 3.1.11 was installed without going to 3.1.10 first the 3.1.10 Admin Console will not be on the ISY as 3.1.11 is a fix to the ISY image only, there is no UI in the 3.1.11 install.

 

Lee

 

No dice for me. I installed 3.1.11 from 3.1.9 before reading this post (note the url in the 3.1.10 beta post is pointing to 3.1.11). I reverted back to 3.1.9 and upgraded to 3.1.10 then 3.1.11 clearing the java cache each time. I'm not sure what this means:

"and be sure to use the URL that invokes 3.1.10 Admin Console."

but I'm opening the admin console by going to the local URL (http://192.168.0...) and hitting the admin console link in the upper right of the main navbar of the ajax UI.

Link to comment

timmay

 

By no dice you meam the RemoteLinc2 device types are not shown in the Device Type pulldown near the top (entries 5,6,7)?

 

Suggest installing 3.1.10 and invoking the Admin Console. Check Help | About to verify it indicates 3.1.10 is the ISY firmware and the Device Types pulldown shows the RemoteLinc2 device types near the top of the list.

 

Only when that has been achieved installed the ISY image only 3.1.11 download. This download does not include the Admin Console, it is only a fix for the ISY code itself.

 

Lee

Link to comment

I have a number of RL2 #2444A3 switches that will not be recognized by ISY.

 

ISY99i v. 3.1.10

 

Set RL2 with blinking green LED

ISY:

Add new device

Enter address, name and find 2444A3 in dropdown.

Starts to process and I get the following error message

 

Any help would be appreciated

post-929-140474154269_thumb.jpg

Link to comment

I have a number of RL2 #2444A3 switches that will not be recognized by ISY.

 

ISY99i v. 3.1.10

 

Set RL2 with blinking green LED

ISY:

Add new device

Enter address, name and find 2444A3 in dropdown.

Starts to process and I get the following error message

 

Any help would be appreciated

post-929-140474154269_thumb.jpg

Link to comment
For sure the Admin Console code running is not 3.1.10. For some reason Java is pulling an old version from the cache. There have been some posts that indicate a reboot is sometime required on Mac to clear the cache.

 

You can try pulling the Admin Console from the UDI site with the following URL.

 

http://www.universal-devices.com/99i/3.1.10/admin.jnlp

 

Sweet, that did the trick!

Note I'm on Win7, but I didn't try a reboot yet. Possibly a bug related to the AJAX UI? Thanks a ton.

 

I had a socket failure message and failed on the first link attempt (it was in link mode so I'm not sure what the problem was), but issued a rewrite and it worked.

Link to comment
awzulich

 

That normally indicates the RL2 is not in range of a Dual Band Device. Try moving it closer to an Access Point or Dual Band PLM.

 

Lee

 

Lee

 

I have no dual band devices, but the RL2 is within 15 feet of three #2443 access points. Are the new dual band devices necessary for these to work?

Link to comment

An Access Point should work with the RL2. Temporarily move an Access Point to the same circuit as the ISY PLM and position the RL2 within a few feet of the relocated Access Point. Repeat the New INSTEON Device process.

 

If that is not successful run Tools | Diagnostics | Event Viewer with Device communications events selected. Run through the New INSTEON Device process and post the event log.

Link to comment

Brian and Lee -

 

The RL2s are indeed 2444A3

 

An Access Point should work with the RL2. Temporarily move an Access Point to the same circuit as the ISY PLM and position the RL2 within a few feet of the relocated Access Point. Repeat the New INSTEON Device process.

 

If that is not successful run Tools | Diagnostics | Event Viewer with Device communications events selected. Run through the New INSTEON Device process and post the event log.

 

Ran it again with the access point adjacent to the ISY PLM.

 

Once again failed. Here is the log as requested:

 

 

Fri 11/11/2011 09:12:23 PM : Setting Time From NTP

Fri 11/11/2011 09:12:30 PM : Setting Time From NTP

Fri 11/11/2011 09:12:38 PM : Setting Time From NTP

Fri 11/11/2011 09:12:45 PM : Setting Time From NTP

Fri 11/11/2011 09:12:53 PM : Setting Time From NTP

Fri 11/11/2011 09:13:00 PM : Setting Time From NTP

Fri 11/11/2011 09:13:04 PM : ---- Initializing the linked devices ----

Fri 11/11/2011 09:13:04 PM : ---- All Linked Devices are now initialized ----

Fri 11/11/2011 09:13:04 PM : ---- Add remaining devices ----

Fri 11/11/2011 09:13:04 PM : [ 1C 24 A 1] Writing High Water Mark at Link 0

Fri 11/11/2011 09:13:04 PM : [1C 24 A 1 ] Using engine version i2

Fri 11/11/2011 09:13:04 PM : [iNST-ACK ] 02 62 1C.24.0A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Fri 11/11/2011 09:13:07 PM : Setting Time From NTP

Fri 11/11/2011 09:13:09 PM : [iNST-ACK ] 02 62 1C.24.0A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Fri 11/11/2011 09:13:15 PM : Setting Time From NTP

Fri 11/11/2011 09:13:17 PM : [iNST-ACK ] 02 62 1C.24.0A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Fri 11/11/2011 09:13:21 PM : [ 1C 24 A 1] ** Not added ** Remove Device Links failed

Fri 11/11/2011 09:13:21 PM : ---- All Remaining Device Added ----

Fri 11/11/2011 09:13:21 PM : [All ] Writing 0 bytes to devices

Fri 11/11/2011 09:13:22 PM : Setting Time From NTP

Fri 11/11/2011 09:13:30 PM : Setting Time From NTP

Fri 11/11/2011 09:13:37 PM : Setting Time From NTP

 

BTW, I tried this with three RL2s .. no joy

 

Thanks for your help

Link to comment

The RL2 is not responding to the commands sent from the ISY. RF communication is not under application control (ISY in this case). All RF communication is autonomous and automatic. The lack of response from the RL2 can be caused by any of the following

 

the Access Point not working

the Access Point is not coupled to the ISY PLM phase

the RL2 is not in linking mode

the RL2 is out of range of the Access Point

the RL2 is not working

something is interfering with RF communication - this can be eliminated as a cause if other RF devices are working.

 

EDIT: these are actually Access Points and not SignaLincs with the black external antenna

Link to comment

FYI - for those that have observed the odd button numbering of the RemoteLinc2, the device does in fact use a different Button to Group number assignment from any other multiple button device. For all other multiple button devices the first button uses Group 1, second button uses Group 2, third button uses Group 3, and so on. For some reason an RL2 button A uses Group 2 and button B uses Group 1. Just the opposite of what one would expect. This was noted in an earlier post. That is why the ISY nodes appear to be numbered wrong when in fact it is the RL2 that is reversed for each group of horizontal buttons.

 

Not likely SmartLabs will ever change this as it would create an incompatibility between new and old

Link to comment

Archived

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


×
×
  • Create New...