bpwwer

I don't have an Ambient station or account so I'd need access to your data to test and debug. It sounds like something could be wrong in the profile files created for your data. It should log what it is creating for the node definitions if you enable debug level logging. So first do that and send me the log.

@TechmanThat would imply that PG3 is not able to connect to whatever ISY is configured as the current ISY. The PG3 log should provide more info on why it's not connecting. Typically, it fails to connect if the username or password is wrong in ISYs->edit current ISY configuration. But it could also be the IP address or port number that is wrong. I just added this feature and it seemed to accurately detect if the ISY was connected or not in my testing, but there could also be a bug and it's giving a false reading.

Did you restart the admin console? You always have to restart the admin console after installing a node server or the admin console won't know how to display the nodes created by the node server.

It was released when I posted. If it isn't showing up in the store yet, refresh the store listing.

Is it really this message: "Portal Access Token Expired. Refreshing..." ? If so, that's not an error, it's a warning. The token is only good for about 1 hour and then it needs to be refreshed (or you need to re-login to the Portal). PG3 attempts to refresh it automatically when it detects that it expired. So unless it fails to refresh, it's behaving as intended.

I'm not sure what you're asking. It looks like the new ISY launcher crashes/fails when it tries to load a list of devices saved with the old ISY launcher. However, if you can look at the contents of the previously saved file, it does have all the name/URL strings in it so that could be helpful when re-adding.

Done in version 2.0.1

So, I hit OK. I can't tell if it updated my ISY launcher shortcut or not (btw, I'm running on a Linux desktop, not Windows). But the finder didn't show any of my devices and load wouldn't load an old saved list either. I had to re-add everything and re-save. It seems to be working mostly the same as before now that I've re-added everything.

I haven't heard anything about IoX launcher. But I just got this when I tried to run ISY Launcher from my desktop

No, it didn't hurt anything to have run it before the package was available. It's there now, but it took a while to build so there may be a lot of other packages that are also updated.

The packaging script failed to finish and I can't get into the system now to restart it. Normally, it just takes a couple of minutes to package it so I make the forum update after I started the packaging script..

I get the same thing. I'm not the developer of this node server. I don't believe it is being maintained any longer so if Google changed something that breaks it, then it will probably need to be removed from the store.

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.