New router, ISY not shown in router client list, can't connect to admin console

[smorgasbord]

OK, so I have a new router. I think what's going on is that the new router's address range is 192.168.50.XX whereas the old router's address range is 192.168.1.XX.  I don't see the ISY in the router's client list (short list since it's ethernet cabled), and I can't connect to the ISY admin console. I tried resetting my Java cache, too.

Rebooting the ISY doesn't help. If I unplug the ethernet cable to the ISY, the Memory and Error lights blink, which is to be expected for no ethernet, so it does see ethernet, the router just doesn't allow it to connect. I'm using DHCP on the router and do not have any manually assigned addresses.

My only thought at this point is that perhaps I gave my ISY a static IP (because I had a bookmark for http://192.168.1.200/WEB/INDEX.HTM) and now my router isn't allowing 192.168.1XX addresses. So my two options are:

1) Change the router to use 192.168.1 instead of 192.168.50 for its LAN address range

2) Reset the ISY to factory defaults (if in fact it's using a manual static IP)

The ISY is functioning fine, btw, as my programs are all running and I've verified that inputs run programs and cause the right things to happen with my Insteon devices. 

So, are those two items what I should try, and in that order, or should I check/do something else first?

thanks!

 

 

Edited July 5 by smorgasbord
Added detail on what to do next

[hart2hart]

192.168.1.xxx is very/most common for Class C addresses. Depending on how you assign addresses(DHCP or Static) in your network., I’d tend to go back to it to make sure 192.168.50.x has not broken something else you haven’t even noticed yet.

[tmorse305]

 

7 hours ago, smorgasbord said:

If I unplug the ethernet cable to the ISY, the Memory and Error lights blink, which is to be expected for no ethernet, so it does see ethernet

Do you use the UD portal?  If so go to the Portal and see if the portal can see your isy.  If so then your isy is getting an IP address from somewhere.  If not then you're probably right about the static IP assignment.  Option 1 seems easier to do, just change it to 192.168.1.x long enough to login in to isy and change it to DHCP.  Then you can switch it back to  192.168.50.x if you want.

Edited July 5 by tmorse305

[smorgasbord]

4 hours ago, hart2hart said:

I’d tend to go back to it to make sure 192.168.50.x has not broken something else you haven’t even noticed yet.

This the first and so far only thing I've noticed wrong. Since I changed the SSIDs I'm using, I had to reconnect all of my wireless devices anyway, and the few wired ones are all working. The ISY is the only thing so far I can tell hasn't re-connected.

1 hour ago, tmorse305 said:

 

Do you use the UD portal?  If so go to the Portal and see if the portal can see your isy.  If so then your isy is getting an IP address from somewhere.  If not then you're probably right about the static IP assignment.  Option 1 seems easier to do, just change it to 192.168.1.x long enough to login in to isy and change it to DHCP.  Then you can switch it back to  192.168.50.x if you want.

The portal doesn't work either, as expected when not seeing the ISY in the router's client/device list. It's good to know the ISY will function and make Insteon devices using powerline/wireless do their things, and that internet is only/mostly for talking to the ISY.

Edited July 5 by smorgasbord

[Geddy]

@smorgasbord This clearly sounds like you had a Static IP set at the device level. This was once the suggested option for ISY994 devices, but over the last many years UD has encouraged people to remove that setting and handle DHCP reservation at the router level. 

Since your local DHCP table changed from 192.168.50.x to 192.168.1.x and your ISY994 is not connected then clearly the IP was set to only join at the 50.x range of IP addresses.

As @hart2hart suggests changing the DHCP table back to 192.168.50.x would be the best bet. 

I would suggest this to be a temporary change and only to get the ISY994 back on the network.

If you still had your old router you could even handle it that way and directly connect a computer/laptop to the old router and then connect the ISY994 to the old router and connect that way and remove the Static IP setting on the configuration tab then unplug the ISY994 (both power and network), connect the network to the new router and power it back up. It should then connect because the IP address would be assigned by the router.

THEN, you could reserve an IP address from your router so the ISY994 would always connect at that IP address should you lose network or power to the ISY994.

Here's the other option from the wiki: 

https://wiki.universal-devices.com/Main_Page#Changed_ISP/Router_-_Can_no_longer_access_ISY

Sounds like you completely changed the network settings if you're also changing SSIDs for wireless devices. Always fun times! 

[smorgasbord]

OK, so I reconfigured my router to use the 192.168.1 IP pool instead of 192.168.50 IP pool and sure enough, the ISY showed up after reboot!

Now I should probably remove the static IP setup in the ISY and do it only in the router, for when I upgrade my router again - last time was over a dozen years ago so no complaints on that.

Of course, my portal lease is up, and it's now $44/year. A new eisy is $255, but considering I'm using it for my now also discontinued Insteon devices I don't have much incentive to upgrade. If eisy would support the YoLink set of devices, I'd be all over it in a heartbeat.

[Geddy]

29 minutes ago, smorgasbord said:

Of course, my portal lease is up, and it's now $44/year. A new eisy is $255, but considering I'm using it for my now also discontinued Insteon devices I don't have much incentive to upgrade. If eisy would support the YoLink set of devices, I'd be all over it in a heartbeat.

Glad you got it sorted out. Sounds like you're a "set it and forget it"  kind of user. There has been communication from UD over the last couple of years about the upgrade process and most recently a message about the increase in the portal license (post on UD website). 

And what do you mean "discontinued Insteon Devices"? There might be a few things that Insteon has quit supplying, but most common devices are still available from Insteon and even new devices have been introduced in the last year (note that only the current eisy will "fully" support the newer Insteon devices). 

Furthermore, the eisy DOES support Yolink devices (with the use of a plugin). Many people here use YoLink devices reliably in the eisy.

Guess you should take some time to review the forums and UD site to really learn about the products. Many longtime users were "all over it" when the Polisy was released and more when the eisy was released. The reliability of the ISY994 is outstanding and a fine machine that doesn't need much in the way of upgrading. So if it works for you it's fine to do what you need it to do. If you're wanting to open your home to more control using a UD device as your home automation controller than eisy is the best (only) option currently available. 

Again, glad you got the device back online. Hope you changed it to not be static IP!

[Brian H]

By chance. Are you talking about the older power line only devices? Like  2456S3 appliancelinc.

I use them my self.

 

[smorgasbord]

I admit I haven't been paying any attention to ISY stuff for over a year now.

When SmartHome went under, it seemed that Insteon might be in trouble and there was some effort in trying to get Insteon devices going again. That's about the time I started adding YoLink devices - I started with the water sensing devices since my well water tanks are located 600' feet from my house and the LoRa range they offer was nice. I ended up with some thermostats, open/close sensors and relays, and a few other things as well.

At that time (a year or two?) I checked the forums here and there wasn't anything I found on YoLink, and it didn't seem like that was going to happen. It's great that it did! If you've got a pointer for me to start looking at, that'd be great, and if EISY can control my YoLink and Insteon devices with programming logic, I'll certainly get on-board and migrate.

[Geddy]

3 hours ago, smorgasbord said:

If you've got a pointer for me to start looking at, that'd be great

Look here: https://forum.universal-devices.com/forum/395-yolink/

and here: https://github.com/Panda88CO/udi-yolink/blob/main/README.md

and read the UD wiki eisy User Guide: https://wiki.universal-devices.com/Eisy:User_Guide

These links should give you the basics for what can be done. If you’ve gone beyond Yolink be sure to look around the PG3 forum area for all the other plugins that are available with the eisy (and Polisy). Note that there are free and paid plugins.

To see the full list of available plugins check here: 

https://polyglot.universal-devices.com/