CStickney

Thanks. I agree that manual DHCP is a work around. My concern is less about conflict and more about predictability. I went the PolicyPro route vs just running this on server-based *nix instance to minimize external dependencies.

Initially, I'd say it was a case of experimental necessity. Following the initial install instructions, the steps are listed to use ISY Finder. My home automation network is on a separate subnet from my user devices so nothing is discovered as the discovery process appears to be a broadcast level poll. Nothing in the "First Steps" section of initial setup documentation mentions the URL format to manually add an instance, e.g., https://{ip}:8443/desc This info is, of course, contained in the "troubleshooting" section well below, but separated by several next step topics that a user would not natively scroll past as they haven't been successful with step 1. So experimenting, a browser to the DHCP IP brings up PG2. The default user/pass works, so this appears to a first time user to be a viable option. Further, PG2 appears to be the only graphical mechanism (at least that I can see in 5.4.3) to set the polisy pro to use a static IP addr. So a user that subscribes to a philosophy that service class devices should be statically defined, PC2 still seems relevant and required?

Thanks for the response, Geddy. Yep. Portal account created. UUID is added to my inventory list and license is associated to it. The "dot" is present, but blank. I've rebooted the IoP with and without the admin console active. Also rebooted the hardware appliance multiple times with no change in condition. I will open a case for that. Sorry. Let me elaborate. The only place I can change the IP of the polisy appliance is through what I understand to be the PG2 interface ( ip:443/polisyconf) which is easy enough and straight forward, sans the (deprecated) statements about PG2. The only other place I see that mentions the IP of the actual device is the admin console, but no configuration is allowable. I understand from your explanation that this is intentional. Only that it's confusing when admin console shows the correct IP and mask but shows all 0's for the gateway configuration which had me 2nd guessing if the system was functioning correctly.

New to the ISY ecosystem. Starting fresh with polisy pro. current version: ISY 5.4.3, polygot 3.0.56 on BSD 13.0p11 I'm able to get the device configured and accessible via admin console, pg2, and pg3. I'm unable to apply the portal license. I've registered the UUID on the portal. Help | Manage Modules | ISY Portal (21075) | Yes. Spinning wheel, closed dialog box, never actually connects. Along this process, a few observations. I'm unsure if these are nuisance or symptomatic to my issues with portal registration? Changing from DHCP to static - the only graphical mechanism I see for this is via the deprecated PG2, Settings | Policy Configuration. I see no equivalent function in PG3. Also, I observe (but cannot modify) the IP settings in admin console, with the exception that the DefGW is listed as 0.0.0.0. PG2 and netstat -r shows the configured GW. I presume this is an interface bug in admin console? I have successfully added my ISY UUID to the portal. I've seen in documentation and on the portal ( ISY | Select Tool | Information | ISY Portal Access Troubleshooting) that I will need to authorize the portal access from ISY via Admin Console | Configuration | Portal Tab ... No such "portal" tab exists in my admin console (LAN nor Cloud). Any suggestions or pointers on what I'm missing?