bpwwer

It's a bug in the latest version of PG3.

I get this when I try to launch AC via cloud: java.io.FileNotFoundException: https://isy.universal-devices.com/iox/5.4.4/admin.jnlp

I'm still working on getting the update available notifications working but I'm getting close, I think. However, the auto update on restart should have worked. If you can, can you check the PG3 log and see if you can find where it tried (and I assume failed)? I'd like to know why it failed.

PG3 version 3.0.36 was probably an alpha release, none of the current information is probably valid for that version. Try the "Upgrade Packages" from the admin console again. For really out of date systems, it can take two attempts to get everything updated properly. Also note that it can take a while to update. 10+ minutes is not unreasonable. After the update is complete, you may have to reboot the polisy (use the reboot button in the admin console). If that doesn't clear things up you'll probably have to submit a ticket.

It's certainly possible they reduced the number of calls that can be made for the free plan. It currently says: 500 calls / per day 25 calls / per hour 3 calls / per second Which really means can't call it more than about once every 3 minutes or short poll needs to be 180 or larger.

When adding support for additional types of purchase options, the format of the entries in the node server store has changed. The latest version of PG3 can still install node servers entries that are in the old store format, but it can't detect the version change for node servers installed using old format. I'm working to make the detection a bit better. So node server store entries will need to transition from the old format to the new format and node server installations will need to be updated as well before the new version detection will work. However, the automatic update on restart should be able to detect the version update and automatically update on restart.

All the HTTP request to the WeatherBit servers are coming back with no response. The node server is probably not configured correctly.

Or if you're already running 3.1.12+, this might be bug in PG3.

A just releases a new version (2.0.7) that should fix the issue. The problem was that @jkosharek's station is reporting battery data that I had not seen before and the data parser ended up generating two battery drivers with the same name in the node. The ISY doesn't like that and the node was not really valid, hence it wasn't able to display it properly in the admin console.

What shows up in the log files for the node servers?

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