Geddy

FYI - The site appears to be working now.

@tjkintz if you go here - https://forum.universal-devices.com/forum/339-current-release-announcements/ Click on "Follow" and then select "A notification and an email when new content is posted" you'll get an email (and forum notification alert) that something has been updated. This covers PG3, IoP, UD Mobile - any Universal Devices release that gets posted there. Perhaps future Polyglot development can somehow push a notification within the system that an update is available, but right now the easiest way is to follow the forums and get the alerts. Polisy is in active development so there are regular updates ongoing. The current problem with automatic updates is that things might break if the unit updates without the user knowing it. It's completely different than thinking about a Router that might just update some internal security setting. This is a slightly higher complex system.

@Ross - According to the release for PG3 v 3.0.63 IoP was running once installed. So as @MrBill says you've probably had it running. It's fine to run without adding anything to it (that's how mine is currently). Are you comfortable with SSH access to the Polisy? If so you should check out the wiki link I posted above and let us know what you get for the OS version result. I also think it should be current enough. (sudo uname -a) Are you on Windows or macOS? If on Windows and running ISY Launcher method you can probably just refresh your ISY Finder window to find the IoP process. That information is also seen in the wiki linked above. If it doesn't load on refresh try adding it manually as described -> https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can't_Find_Polisy Since it's a new(ish) hard drive with 3.0.63 installed I think it's safe bet that IoP is running and you should be able to access the "Update Packages" button as @MrBill shows above. I think with the level of development around the Polisy keeping it updated is key. Otherwise, there appears a higher risk of issues by just letting it sit and churn. It's a living system that the developers have been making requests to help themselves, but also just overall making the whole system operate better (for all the users) as more, and more node servers are being developed.

@SSamuels is it possible the other two node servers are installed/managed by PG2 and not PG3 node servers? Or are you certain they're all PG3 node servers? If they were installed in the PG2 side they cannot be managed in PG3 and will show up this way. Otherwise, since you've done the restart of PG3 try to restart each node server individually? Can you see the logs of either to see if you notice any errors? Or look at the main PG3 log to see if any errors are seen to lead you toward resolution.

@Illusion probably something @bpwwer or @Michel Kohanim could better explain. However, my "simple" way of looking at it is: Polisy = Device = Reboot Polyglot = Service = Restart IoP = Service = Restart (although this doesn't appear to work when given the command from PG3 interface) I'm not clear why there's an option to "reboot ISY", but it might have been to reboot an ISY994 that the Polisy could talk to. I don't think it works. Something with trying to restart or reboot ISY (either IoP or ISY994) from the PG3 web UI doesn't work and just flashes an error in the lower right of the screen. IMO best way to reboot the IoP is through admin console. Same way as done previously with the ISY994.

@Goose66 This is the closest thing I've seen to what you're looking for... There was an older post for in the "geek batch" area:

Bummer...seems like UDI's site might be having issues. That's something @Michel Kohanim will need to review. Try emailing as @MrBill says, but I think there might have been some recent changes to the ticket platform since @Michel Kohanim removed the email method from his signature. But should still work to get something started. If you read the information in the wiki it will give you the commands to use via SSH login. Please note the default SSH login are admin/admin for user/pass. If you're not comfortable with logging in via SSH please wait for support to work on your ticket to assist with the process.

@Ross since your issue is more with upgrading PG3 than the issue being discussed where you originally posted it, I split it out so you could get more help for this specific issue. Since you're on an older version of PG3 at this point you need to open a support ticket to get the options for your specific device. Please review this information in the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_OS_Versions_Below_13 Submit a Ticket: https://www.universal-devices.com/my-tickets

Have you tried adding the other items mentioned in the configuration as "Custom Configuration Parameters"? Since in the read me it says "User Provided" I wondered if the whole parameter has to be added. https://github.com/simplextech/pg3_docs/tree/main/ST-Inventory#user-provided I don't use this Node Server so can't help with the setup. And think @simplextech commented that they only get notifications from PMs, so perhaps send a PM to them referencing this topic.

Nice work @Panda88! The new area to discuss YoLink can be found here: https://forum.universal-devices.com/forum/395-yolink/

@Illusion since you went the new hard drive approach I would suggest opening a support ticket to ask this specific question before proceeding. Since it warns you that you could brick your system you don't want to mess up what you just got updated. So better safe than sorry at this point just to confirm the steps to update from where you are currently. Submit a Ticket: https://www.universal-devices.com/my-tickets

@someguy PG3 current version is 3.1.12 - release announcement here: What Techman gave you is Firmware for ISY on Polisy. You can find all current release information here - https://forum.universal-devices.com/forum/339-current-release-announcements/

Apparently "computer people" alphabetize capitalizations different than normal humans. Same reason some of the other node servers that are in all caps get put before others. That's "computers" for you. Are you running ISY994 or IoP? Your screen shot above is showing the ISY is at 5.3.3. ISY994 current version is 5.3.4 IoP current version is 5.4.4 I don't think that makes a difference for what you're experiencing, but is just another update needed somewhere.

@apostolakisl what version of PG3 are you running? Are you on 3.1.x? If on an older version (like 3.0.x) then there's apparently something not allowing it to show the actual version of node server you're running. It's only going to show the last version that is supported by your version of PG3. I saw @bpwwer mention this somewhere. It was a change in the PG3 3.1.x update and would break the older versions if handled differently. So make sure PG3 is updated and it might fix your issues with other node servers you say you're having the issue with. If you're current then it could be the other developers have not updated where the version numbers are since the 3.1.x update in PG3 purchasing process.

@kaplansa not noticed any issues with it and this is one node server I have run in PG3 for a while. Take a look at the logs to see if you can see any errors coming when you try to operate something. Have you made sure you have an IP reservation for the Hue bridge in your router? Or else setup the bridge IP as noted in the settings (and mentioned in this post). Just knowing what kind of errors are seen in the log will help with further troubleshooting.

@TVC15 There have been a lot of posts about this through the years. Info about the power supply can be found in the wiki - https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Quick search of the forums found this topic:

@Illusion moved your post above into this thread as it appears to be your same issue. Please review replies above. @Chris McKean did you get help from your support ticket? What resolved your problem? Please update here so it might help others.

@Illusion make sure your ISY Portal is an active subscription. Can you log into my.isy.io and confirm your license for ISY Portal is current? Once you confirm the access license is still current then it should work. Make sure you're using your ISY Portal email and password (same credentials used to log into my.isy.io). Also while in the ISY Portal make sure the setting for "My Preferred ISY" points to your active ISY (either ISY944 or IoP) Just double check the information needed to use ISY Portal with Mobilinc (Pro or HD) can be found in the UDI Wiki - https://wiki.universal-devices.com/index.php?title=ISY_Portal_MobiLinc_Configuration

Take a look at this recent post...doubt the ultimate issue will resolve your issue (was GFCI outlet), but perhaps the information from @Brian H might help.

@Illusion I'm not sure what you're doing (or not doing) at this point. But I might suggest you read the Polisy User Guide to help in some ways: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Any node servers you install with PG2 can only be managed by PG2 and will show up as "unmanaged" in PG3. And vise-versa. PG2 can only point to one ISY. PG3 (I believe) can point to multiple ISY. So, are you working with a Polisy and trying to send node servers to an (external) ISY994? Or are you on a Polisy and trying to send node servers to ISY on Polisy? If you want to delete Node Servers you need to access the dashboard that installed them and uninstall and delete from there. PG2 is a two step process. PG3, I think, is a more simple solutions, but haven't gone through the process in a while to give you step-by-step. If your Polisy is "old" and you're waiting for a new drive then I wouldn't do anything with it now until you get the new drive. You're going to cause more problems than good at this point by randomly trying to flip between two entirely different systems.

@Illusion sounds like @bpwwer would need to step in to answer your questions. Or others that use this node server. Not sure what would cause it not to work through switches unless they changed subdomains somewhere along the route.

@CPrince "Find/Replace" is only found on the Programs tab when you right click on a program. You can search for devices from that screen.

@Illusion Have you installed any other PG3 node servers? Do they show up in the ISY? Sounds like you might not have the PG3 pointing to the ISY process correctly. Are you running ISY994 or ISY on Polisy? Make sure you've added the ISY to the PG3 dashboard - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs If you do have other NS installed and appearing in ISY then perhaps PG3 needs to restart. Make sure you've also closed admin console and re-opened for new NS to be loaded to the admin console.

@Blackbird There have been lots of questions/comments on this subject through the years. Either searching the forums with the search bar at the top of the page might find the posts or using Google Site Search will find you several comments. What @kzboray states is the typical answer for the issue. Surge protectors or UPS devices tend to filter the traffic for larger system installs. While it "might" work sometimes it could be problematic. Best practice has always been to suggest plugging directly into the wall. I had a whole home surge protector installed (about the time I started installing Insteon), but also use point of service surge protection for high value equipment. However, the PLM is plugged directly to the wall outlet. Think of it like a Powerline Wi-Fi extender. Those have to be plugged directly into the outlet to propagate the network signal to other parts of the house.

It's more than likely Java related. How long have you been an ISY user? It's likely a very old cache still in the system somehow, but Java 6 would have been very old (2006~2011). But I searched for macOS and Java 6 and it seems that it's more recent (stupid macOS+java!). So it seems to be a Java related cache. You should remove the old cache. See if there's anything else in that directory. Also, reading some of these tips from Java might be helpful: https://www.java.com/en/download/help/java_mac.html You might also want to look at this for removing cache after Java was removed: https://www.java.com/en/download/help/deployment_cache.html But again, you appear to have multiple installs of Java. Maybe you need them for something. If not, I'd remove them and just use the standard release. If you need them...it might be advisable to setup another account on the Mac that doesn't have all those java versions installed and only use THAT account to run basic Java and access admin console. I guess this brings me back to your first post...are you having issues now? Your last statement really is a loaded statement... If it's working now...why wouldn't it work "down the road"? I mean, sure, macOS sucks for some people and makes things unbearable...but I think if it's working for you now, and you've got that much "junk" (java installs) working against you...what makes you think it wouldn't work in the future? Do you have that little faith in Apple that their macOS will go funky? I mean...it's Apple. It's just supposed to work, right? (Sorry...a tiny anti-macOS rant there...it's silly how users have such different experiences and abilities with macOS+java+ISY. Don't get me wrong...I am 100% in the iOS/iPadOS world, but macOS (issues) baffle my mind.)