I can get to the Polisy through the ISY portal web access but IoX doesn't find it. I'm running firmware 5.5.9. I can ping the Polisy and it responds. I just cleared the Java cache since I upgraded to 5.5.9 yesterday, although I am 90%+ sure that IoX has worked previously to this since the firmware update. Any other suggestions?

SOLVED: It appears the manual IP I had set on the Polisy got reset in the 5.5.9 update, because Polisy now shows DHCP and the IP address has changed, which is why IoX couldn't find it. Meanwhile, another device stole the (former) static IP. I guess I needed both a manual IP and a router reservation.

12 hours ago, landolfi said:

SOLVED: It appears the manual IP I had set on the Polisy got reset in the 5.5.9 update, because Polisy now shows DHCP and the IP address has changed, which is why IoX couldn't find it. Meanwhile, another device stole the (former) static IP. I guess I needed both a manual IP and a router reservation.

No, you should not have a manual IP address. The reason UD is forcing DHCP reservations is because the use of a manual IP was causing issues resulting in many service tickets.

DHCP reservation is the way to go.

Edited April 4, 20232 yr by DennisC
Corrected last line to DHCP "reservation".

1 hour ago, DennisC said:

DHCP is the way to go.

DHCP Reservation is the way to go.  DHCP alone is a random pool address.

On 4/4/2023 at 8:32 AM, DennisC said:

No, you should not have a manual IP address. The reason UD is forcing DHCP reservations is because the use of a manual IP was causing issues resulting in many service tickets.

DHCP reservation is the way to go.

I get that. But shouldn't that be documented somewhere if IoX can't find the ISY when its IP changes as appears to be the case? Otherwise a situation like mine occurs where the Polisy goes offline temporarily during a software update and another device takes its previously assigned IP. What I think we are saying is unless you plan to deal with IoX not finding the ISY when its IP changes, a router reservation is REQUIRED.

Edited April 5, 20232 yr by landolfi

50 minutes ago, landolfi said:

But shouldn't that be documented somewhere if IoX can't find the ISY when its IP changes as appears to be the case?

Like this: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy

or https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy

Now that you've got it working it might not be a "fair" test, but clear your Java again (selecting all 3 options). Then run start.jnlp to put the icon back on the desktop and run IoX Launcher. If it doesn't "Find" the IoX what happens if you hit "Refresh"?

Usually devices aren't randomly hopping IPs unless the router reboots or multiple devices come online at nearly the same time as you rebooted the Polisy. If something randomly took the IP during a reboot of the Polisy you might have other network issues. 

Either way, glad you got it sorted out easily. 

 

1 hour ago, Geddy said:

Like this: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy

or https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy

Usually devices aren't randomly hopping IPs unless the router reboots or multiple devices come online at nearly the same time as you rebooted the Polisy. If something randomly took the IP during a reboot of the Polisy you might have other network issues. 

Either way, glad you got it sorted out easily. 

 

Thanks. I did try both, but since my computer couldn't resolve the polisy host name using what it thought the IP was (i.e., the old IP for that host), it didn't work. I also tried what I usually do, IPaddress:3000 to try to get to PG3, which didn't work for the same reason. It was just a random event I guess with the second device grabbing the Polisy's IP. So all this is here in case it helps someone in the future.