ISY inaccessible, not sure what to do

[DirkR]

Hi All,

 

after rewiring my network (at the strong insistence of wife about the number of cables in the office...) I have not been able to access my ISY. I can start the admin console (from http://isy.universal-devices.com/99i/),but it doesn't find the ISY. How does it try to find it? If it tries broadcast that probably won't work, because there are two routers in the mix. Is there a way to give it the IP address directly? I can't seem to find any option to do that.

 

I can acess the ISY through its IP address, but if I just to go http://<isy'>http://<isy IP>/ I get "/WEB/udajax.htm not found" (could be caused by a botched upgrade, I'm running on Linux and have never been able to make that work). If I try to get the admin console from there ("http://<isy ip>/admin") I get a Java error about a missing manifest.

 

What else can I do? Any hints welcome!

 

Thanks

 

  Dirk 

[jerlands]

Sounds to me like you had assigned ISY a static IP and you've changed a router in the path?

If so you can telnet to ISY, change the IP to DHCP then reserve the address in the router, or... go back to the original config and change it to DHCP

 

From 99i user guide...

 

  Connecting to the ISY Shell Using the Serial Port

1. Connect one end of a serial null modem cable (included with PRO version) to ISY's Port B, and connect the other end to the serial connector (or USB to serial adapter) on the computer.

2. Start a terminal program (such as Windows HyperTerminal) and configurefor 115200bps, 8N1, Xon/Xoff, and for the appropriate COM port.

    3. Type a few characters until prompted for Username: and enter admin (lower case) followed by <ENTER>. When prompted for Password: enter admin (lower case) followed by <ENTER> (Figure 9A).

    The ISY  Shell is displayed (Figure 9B)

 

 

Jon...

[DirkR]

Hi Jon,

 

thanks for the quick response!

 

Sounds to me like you had assigned ISY a static IP and you've changed a router in the path?

If so you can telnet to ISY, change the IP to DHCP then reserve the address in the router, or... go back to the original config and change it to DHCP

 

From 99i user guide...

 

  Connecting to the ISY Shell Using the Serial Port

1. Connect one end of a serial null modem cable (included with PRO version) to ISY's Port B, and connect the other end to the serial connector (or USB to serial adapter) on the computer.

2. Start a terminal program (such as Windows HyperTerminal) and configurefor 115200bps, 8N1, Xon/Xoff, and for the appropriate COM port.

    3. Type a few characters until prompted for Username: and enter admin (lower case) followed by <ENTER>. When prompted for Password: enter admin (lower case) followed by <ENTER> (Figure 9A).

    The ISY  Shell is displayed (Figure 9B)

 

 

Jon...

 

No, it has always been on DHCP and still is. It just used to be that the computer was connected to the same router as the ISY, but now it is PC -> Router1 -> Router2 -> ISY, and the admin console doesn't seem to find it any more (Login is greyed out).

 

To my big surprise my computer actually does have a serial port and I do still have the cable that came with the ISY. But it's female on the serial side, so I can't plug it in. I haven't used a serial gender changers in 15+ years (and I was hoping never again having to do it...), so I need to dig deep to see if I can still find one.

 

In any case, I can telnet into the system and get to the shell.  I'm just not sure how that helps me, as I don't seem to be able to do anything major in there.

 

So the question remains: how can I tell the admin console where to find my ISY?

 

Thanks!

 

  Dirk

[jerlands]

First.. you can use USB to connect ISY to your PC in order to Telnet but doesn't seem you need to.

 

I think the problem is the added router has changed the IP address of ISY (and possibly you've reserved an address for ISY in the one connecting to the Internet?)

 

You probably can find ISY on the first router (with it's software) then find it on the second router with the new IP?

 

Once you know the address of ISY on the router you both share then you'd simply place that address into the ISY Finder URL followed by desc i.e. http://192.168.0.21/desc

 

 

Jon...

[KMan]

Sounds to me that both routers are acting as DHCP servers, and your ISY is ending up on a network that isn't reachable from the router that your PC is connected to. In addition, some other device is at the IP address that you think your ISY is at.

 

You should be able to log into both routers and find out what IP your ISY is actually at (look for "attached devices" or something similar. While in there, you might try turning off the DHCP server on one of the routers if both have it turned on.

[DirkR]

Hi All,

 

thanks for the quick responses! I really like this community.

 

@KMan You're right, both of them work as DHCP servers, and the ISY is on a different network. But that network is reachable (I can telnet into the ISY, and I can access the web interface, it's just broken), so I think that's ok.

 

My problem is that I don't see any way to manually enter the IP address/URL of the ISY. I don't seem to get the ISY finder window. When I start the admin console I only get the empty console window with Logon greyed out. I pushed every button there was in it, but none of them do anything (not really surprising as it's not connected). I did clear the Java cache, but it didn't seem to make a difference. I'm getting my console from http://isy.universal-devices.com/99i/, the one from my actual ISY doesn't pass the Java security (missing manifest).

 

Is there  a way to force the ISY finder window to open? If not, is there a way to update the firmware from the shell, or in general without the admin console running?

 

Thanks!

 

  Dirk

[mwester]

Unless you are an expert in networking and have configured both routers "just so", your network is fundamentally broken.  It may seem that all you need to do is fix the ISY connectivity, but given what you've described, there's a lot of other stuff that just isn't going to work - things that aren't going to be reachable from other things.

 

Replace Router 2 with a network switch.  That may not fix your ISY problem, but at least it will ensure that your network is a single logical network, with every device able to see every other device, with every DHCP device able to get an address in the same range from the same authoritative source and with no conflicts.

[jerlands]

 

 I'm getting my console from http://isy.universal-devices.com/99i/, the one from my actual ISY doesn't pass the Java security (missing manifest).

 

What firmware do you have?  I think you need to download the application (.jnlp) rather than use the applet (clear java cache before install.)

 

 

 

Jon

[KMan]

Unless you are an expert in networking and have configured both routers "just so", your network is fundamentally broken.  It may seem that all you need to do is fix the ISY connectivity, but given what you've described, there's a lot of other stuff that just isn't going to work - things that aren't going to be reachable from other things.

 

Replace Router 2 with a network switch.  That may not fix your ISY problem, but at least it will ensure that your network is a single logical network, with every device able to see every other device, with every DHCP device able to get an address in the same range from the same authoritative source and with no conflicts.

Listen to him. You don't want to be running two DHCP servers, unless you know what you are doing.

 

Post the make and model of the new router that you added. It can likely be set in a mode that it will act like a switch and not a router (including turning DHCP off). Unfortunately, it is not always obvious how to do this, since they try to make them plug and play for the normal use (which is one router on the network).

[DirkR]

@jerlands: That was a good link! The jnlp is just a little metafile, not the actual app, so that didn't help. But the linked article mentioned the Java exception table. Adding my ISY IP to that allowed me to start the console from the IP address, which worked as it didn't need to find it using broadcast or something like that.

 

@KMan: The router is a T-Mobile rebranded Asus AC-1900. I couldn't see any obvious options that would turn it into a switch, it really wants to be a router and given that it handles Wifi and other things it probably has to. Anyway, that problem is solved (see above), so for now I'll keep my two DHCPs.

 

Thanks for your help! 

 

Now I need to figure out how to upgrade the firmware from Linux. But that's a different thread...

[jerlands]

Glad to hear you're connected again   I'm confused though -->> The jnlp is just a little metafile, not the actual app <<-- the .jnlp is the standalone java UI application not dependent like the applet on browser security and resources?

 

 

Jon...

[DirkR]

No, the jnlp is just a tiny text file that tells java where to find the actual program (the codebase at the top and all the <jar...> lines). Here it is, in it's entirety, for 4.3.26:

<?xml version="1.0" encoding="utf-8"?><jnlp spec="1.0+" codebase="http://isy.universal-devices.com/994i/4.3.26" href="admin.jnlp">
<information>
<title>ISY994 Administrative Console</title>
<vendor>Universal Devices, Inc.</vendor>
<description>Configuration Utility for ISY</description>
<homepage href="http://www.universal-devices.com"/>
<description kind="short">ISY Admin Console</description>
<shortcut online="true"><desktop/><menu submenu="ISY994 Series"/></shortcut>
<icon href="udlogo.png" kind="splash"/>
<icon href="isy.jpg" />
<offline-allowed/> 
</information>
<security><all-permissions/></security>
<update check="background" policy="always"/>
<resources>
<jar href="insteon.jar" download="eager"/>
<jar href="ce.jar" download="lazy"/>
<jar href="chart.jar" download="lazy"/>
<jar href="fp.jar" download="lazy"/>
<jar href="RXTX.jar" download="lazy"/>
<j2se version="1.7+" href="http://java.sun.com/products/autodl/j2se"/>
</resources>
<application-desc main-class="com.universaldevices.client.ui.UDClientApplet">
<argument>urn:udi-com:device:X_Insteon_Lighting_Device:1</argument>
</application-desc></jnlp>

So it doesn't depend on the browser in any way, but it is not everything that's needed to run the console either, it just points at it. If you're really curious, the full spec for jnlp is here.

 

Yours

 

  Dirk