bpwwer

I was wrong about the API change. I can't find anything wrong. However, the free plan limits are now pretty low and you do need to have the short poll, long poll and number of forecast days set to stay below those limits. If you try to get more than 7 days of forecast data with the free or hobbyist plans, the node server will fail to start as it will be sit there waiting for more data that it will never receive. This makes things a bit more difficult since the node server doesn't have any way to know what plan you have so it can't auto-adjust the parameters. I've updated the documentation and configuration help to reflect the latest limits.

Looks like they have a completely new API and the old one no longer works. Converting the node server to use the new API is not a simple task so it may be a few days before a new version is available.

Typically, once you exceed a daily limit it won't reset until the next day and all calls to the service will fail until then.

@Goose66No, I don't think that would help. However, the node server can be re-installed to get the new version. From the store or from the purchased list, select install and there should be an option to re-install it in the existing slot. This will install the latest version without removing any existing nodes or resetting the configuration parameters.

It is a bug in 3.1.14. There are a couple of different issues related to how it tries to determine if an update is available. To enable support for multiple versions of the same node server a number of things had to change both in the store entries and in PG3. It's having issues dealing with node server that were installed from old style store entries detecting updates that now have the new style store entries. I believe I have the issue above fixed and am working some of the other issues.

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.