CStickney Posted May 24, 2022 Posted May 24, 2022 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?
Geddy Posted May 24, 2022 Posted May 24, 2022 1 hour ago, CStickney said: I've registered the UUID on the portal. Does this mean you created an account at my.isy.io and setup the portal from there? When you login does the UUID show and is there a red dot next to the UUID? If you haven't gone to the Portal site you need to go there. Sign up for a 30 day trial. Add the UUID and it should send a signal to the ISY on Polisy that will need to be approved. 1 hour ago, CStickney said: No such "portal" tab exists in my admin console (LAN nor Cloud). The IoP needs to reboot. In the PG3 interface you should have an option under "System" to "Reboot ISY". This will reboot that system. Give it a few minutes to complete (I believe PG3 gives you alerts to the process). Make sure you are not actively in Admin Console when you reboot the IoP service. Once it reboots you should now have a tab for portal approval. If after reboot you still do not have a portal tab please open a support ticket to get assistance with the proper steps to achieve this. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com You lose me on the discussion you're having about DHCP and Static. Currently ISY on Polisy does not allow to edit the IP for the IoP service. This is because there are some relationships between IoP and PG2/PG3 that require the ISY service to be at a known IP address (basically). Make sure that you have read the Wiki for the Polisy User Guide for more information and setup guidance. 1
CStickney Posted June 10, 2022 Author Posted June 10, 2022 (edited) Thanks for the response, Geddy. On 5/23/2022 at 10:11 PM, Geddy said: Does this mean you created an account at my.isy.io and setup the portal from there? When you login does the UUID show and is there a red dot next to the UUID? If you haven't gone to the Portal site you need to go there. Sign up for a 30 day trial. Add the UUID and it should send a signal to the ISY on Polisy that will need to be approved. Yep. Portal account created. UUID is added to my inventory list and license is associated to it. The "dot" is present, but blank. On 5/23/2022 at 10:11 PM, Geddy said: The IoP needs to reboot. In the PG3 interface you should have an option under "System" to "Reboot ISY". This will reboot that system. Give it a few minutes to complete (I believe PG3 gives you alerts to the process). Make sure you are not actively in Admin Console when you reboot the IoP service. Once it reboots you should now have a tab for portal approval. 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. On 5/23/2022 at 10:11 PM, Geddy said: You lose me on the discussion you're having about DHCP and Static. Currently ISY on Polisy does not allow to edit the IP for the IoP service. This is because there are some relationships between IoP and PG2/PG3 that require the ISY service to be at a known IP address (basically). 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. Edited June 10, 2022 by CStickney
Geddy Posted June 10, 2022 Posted June 10, 2022 8 hours ago, CStickney said: I will open a case for that. Yes, you should open a support ticket. If Portal isn't showing a request on ISY on Polisy then support might need to reset the request. I also didn't think that the IoP was able to change the DHCP setting. It shoudln't be set to static on the device (as you're showing) because that needed to be managed by the Polisy. You will need to have Support review that as well. Is there a reason you're trying to setup PG2? Since you are starting fresh with the Polisy I would suggest not setting anything up in PG2 and only use PG3 and IoP settings. To setup the IoP in PG3 follow the steps in the Wiki portion found here - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_.28PG3.29_Dashboard But, wait until you have a support ticket to confirm the steps based on what you're showing above. 1
CStickney Posted June 11, 2022 Author Posted June 11, 2022 On 6/10/2022 at 7:22 AM, Geddy said: Is there a reason you're trying to setup PG2? Since you are starting fresh with the Polisy I would suggest not setting anything up in PG2 and only use PG3 and IoP settings. 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?
tazman Posted June 11, 2022 Posted June 11, 2022 @CStickneyyou should set ISY to DHCP then reserve the IP in your router that way the router knows what it is handing out and there should never be a conflict. 2
CStickney Posted June 11, 2022 Author Posted June 11, 2022 29 minutes ago, tazman said: @CStickneyyou should set ISY to DHCP then reserve the IP in your router that way the router knows what it is handing out and there should never be a conflict. 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.
Recommended Posts