bpwwer

There isn't any restriction on how many slots a node server can be installed in. Whether or not multiple copies of the node can run on the Polisy is defined by the node server, not PG3. Each ISY/IoP can have up to 100 node servers installed and again, there isn't any restrictions on duplicate node servers on different ISY/IoP devices. If you have both an i994 ISY and IoP connected to PG3, you can as many as 200 node servers installed. Node servers (or the hardware they talk to) may have restrictions on the number of connections they support but PG3 doesn't know or care about that. I don't know about ST-Inventory specifically to know if it supports running multiple copies or not.

They don't mean anything. It's comparing the node server configuration it gets from the ISY with what it thinks it should be and reports differences it finds. This comparison really only works if you have one ISY/IoP enabled, otherwise it gets a bit confused.

None of those are the station id. The ST-00012345 is a device ID (tempest device) when you log into your account via the web app, the station is part of the URL. For example, mine shows tempestwx.com/station/4697/ <-- the 4697 is my station ID Or from the status screen on either the mobile app or web app

That likely no longer works. With the initial versions of PG3, it would work in some specific cases where the PG2 node server and the PG3 node server were mostly compatible and you had a license or didn't need a license for the PG3 version. Over time, the PG2 and PG3 versions have become less compatible and now you need a license to install any node server on PG3. If none of the node servers showed up in PG3, that means that none of them met the criteria needed to install the PG3 version.

The station's units are the first thing it tries to get from the server. Either 1) the station id you entered is wrong 2) the api key is wrong 3) your station doesn't have any devices associated with it (maybe, not sure if this would have station units or not).

The (re)install button is a brand new feature of 3.1.13 and it appears that there are some bugs that still need to be worked out. Please go to the Node Server Store and select the iAquaLink node server. In the detail purchase page, it should show an install button there and that button should allow you to install using your existing license. However, before you do that, please verify that PG3 is really able to communicate with the ISY. If it is, then you've tripped one of PG3's features that tries to prevent accidental node server removal. If PG3 has node servers listed in it's database for an ISY, and it queries the ISY and gets back that no node servers are installed, it doesn't really know if there are no node servers as maybe you reset the ISY and are restoring it from backup. So it basically does nothing. As soon as you add a node server to the ISY, PG3 will then realize that the list coming from the ISY is valid and will clean up any slots in it's database that don't match what's on the ISY.

PG3 can't do anything to make the node server pause for 5+ minutes, that would have to be in the node server code. Given that pause is about 5 minutes and the short poll is 5 minutes, I'd guess the node server is waiting for something that happens in in the short poll handler.

That appears to be a node server issue not a PG3 issue.

It trying to connect to an IoP at 192.168.1.50:8080 but is failing because the username or password is incorrect. Please verify the username and password is configured properly in PG3 by going to ISYs -> Edit Current ISY

The (re)install button on that screen is a brand new feature I just added so it may not be behaving as it should. What I think has happened is that you purchased the beta version and have a license for the beta version. But the production version of the node server was not added as an update to the beta version so it can't use the beta license. PG3 isn't handling this case very well and in some cases it seems to think it can use the license for the production version and in other cases it thinks it can't. Thus, confusing us all. Because of the way the licensing system is implemented, it's very difficult for node server developers (and even me as the PG3 developer) to test code related to licensing. I don't think this specific case can be recreated without purposely adding some fake node servers into the beta/production stores. If you do end up re-purchasing the production version, then work with @Panda88and @Michel Kohanimto get a refund on the beta version.

Thanks for this comment and for the screen shots above. Polyglot (PG2) did have a mechanism to check if an update was available and the install it if it was. Because of changes in in PG3, it wasn't possible to use that same mechanism. I do think about this occasionally and agree that it would be nice for either PG3 or the AC (or both) to notify you when an update is available and provide the option to apply the update. A lot of effort to date has been spent working on each component to try and make them usable and stable but the integration of the components into a consistent whole is still lacking. Some of this is happening for the eisy release with the goal to make the overall experience much better. What helps us a lot is to get clear and detailed feedback (like what you provided above) so thanks again.

I believe the current official method to update is to open the admin console connected to the IoP instance on the Polisy and use the upgrade packages button there. The IoP software on Polisy is becoming the defacto management interface for the Polisy.

The PG3 log in and the ssh login are completely different. The ssh default is user=admin password=admin I don't understand what you mean. The only restriction when installing a node server is to use a slot that doesn't already have a node server installed. If a slot has a node server installed in it, you can't install another node server to the same slot.

Can you paste what you see in the purchases list?

The instructions for upgrading PG3 are posted with every release announcement: If something isn't clear about that, please let me know what you think would make it better. We're still trying to figure out why you're having issues upgrading YoLink. The node server store has been evolving over time as developers have asked for additional options for node server purchases. This has caused some confusion for both users and developers. What appears to have happened is that the production version of YoLink was entered as a new node server instead of an update to the beta version. What that means in this case, is that PG3 thinks you have YoLink(beta) installed in slot 1 so it can't install YoLink(production) there. It also looks like you have a license for YoLinkI(beta) but not a license for YoLink(production).

Version 3.0.63 of PG3 will no longer receive updates to node servers automatically. You need to update

The PG3 log should show why it's failing to upgrade. We need to see what's in the log after you stop and restart the node server.

Can you check if a copy of the node server is already running? Based on the line in the log that says it's already connected, I suspect that you have a copy running so it won't allow you to start another. Since you're expecting to run two copies, when the one installed on IoP is not running you should only have one active, if you have two, then you probably have a stuck/hung copy occupying slot one and can't start another copy

No, PG3 knows nothing of z-wave so it just backs up the installed node servers.

The point I was trying to make, was that when you do "update packages", it updates all packages that have an update available, not just PG3. Since there is zero interaction between PG3 and Z-Wave, it is far more likely that some other package update caused the problem than it is that the PG3 package update cause the problem. I understand that you did the updates specifically to get the new version of PG3 so that it appears that the PG3 update is a factor in the issue with z-wave. But until we really know what caused your issue, we shouldn't be attributing blame to any one component.

To be clear, "update packages" applies all pending updates, not just PG3. Those errors are coming from IoP and I believe there was also a recent update to IoP.

You should submit a ticket. Unfortunately with the current "upgrade packages" you get all pending updates, not just PG3. It's highly unlikely that upgrading PG3 would effect z-wave. But it is very possible that some other update would.

The uptime display in the footer isn't very useful. There are really two separate components to PG3; the server side running on Polisy and the UI running on your browser. The UI will pull the current uptime for the server when you first log in and then it continues to increment that. It isn't constantly polling the server to see what the server uptime is. If you restart the server, it doesn't restart the UI and the UI simply continues along, incrementing the uptime. That should probably be fixed at some point to periodically check the server and update the uptime, but things like that are pretty low on the priority list.

This issues is fixed in version 3.1.12, see the release announcement for the list of fixes in this version. It is available now.

Hello all, We are very happy to introduce PG3 v3.1.17 which is a minor update to work with Node version 19.5 To upgrade PG3: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you will need to restart PG3. From PG3 select System-> Restart Polyglot 3. Once PG3 has restarted, reload /refresh the browser page. Changelog for 3.1.17 - Update to run with Node version 19.5 Changelog for 3.1.16 (December 9, 2022) - Change IoX discovery process so that it only looks for the IoX on Polisy/eisy - Remove "Running on Polisy" from footer (can only run on Polisy/eisy) - Make node server verification errors more verbose - Add log info for starting udi_interface module install - Add log info for IoX UUID query - Check for updates of PG3. If a new version is available you'll see a notice in the footer - Set autocomplete in login screen for username and password - Fix the re-install process from the Purchases page. It now shows the available install options and makes you choose instead of guessing - Move account management to System menu (use to be Settings -> Profile) - Move backup/restore option from Settings menu to System menu and remove Settings menu - nodeExists shouldn't fail if it can't get node status - Fix store name / module name conflict - Fix updateStores() to work if network is down - Don't update node name to 'undefined' during initial node verification Changelog for 3.1.15 - Ignore multiple clicks of start/restart button - [internal] Change checkDrivers to nodeExits - Allow addnode to rename a node. - Update the purchase option ID if missing. - Update PG3 database with node names from ISY. - [internal] Clean up error reporting in getNode. - Add text to typed parameters delete buttons. - [internal] Include name in renamenode results. - [developer] Fix submit for new node servers - Clean up log messages - Rework store change / version change detection code - Trap error when clearing notices (node server auto update bug) Changelog for 3.1.14 - Remove "Reboot ISY" option from menus. It doesn't work and isn't needed here. - Add some color to the footer badges. Makes it more obvious when things are connected/disconnected - Use isy enable field for connection status. Display the connection status to the current ISY in the footer. - Purchased list improvements: show store(s) that node server is available in, better detect which option user has license for. - Trap error if IoP service is not running and report error. PG3 requires that IoP be running and using the default port of 8080. If it is unable to detect the IoP, it will fail to run. Changelog for 3.1.13 - Add a (re)install button to the purchased node server listing so you don't have navigate back to the store to install - Force the use of SSL for node server to PG3 communication - Convert error messages to info/debug when inserting new node servers to store - Remove version column from node server lists. Now that we support having multiple versions available a single version makes no sense - 3.1.12 broke the notification of new node server versions available, it is now fixed. Changelog for 3.1.12 - Node server configuration error message improvements - Don't overwrite custom parameters when re-installing a node server. - Remove 'Software Management' section from settings, it wasn't being used. - Clear notices when a node server is updated. - Unicode characters in date/time string would cause backup and log downloads to fail. - Get Polisy ID from IoP instead of using current network adapter mac address. Support Thread: