bpwwer

There are a couple of non-errors that can cause that error message. If you haven't purchased any node servers yet, the list is empty and it reports that message. It may also report that message if your portal login token has expired, in that case it will refresh the token but it doesn't get the new token until after it's tried to get the list of purchased node servers. A Sync Purchases should work to get the list. It tried to re-direct you to the portal but it looks like something blocked it. That would be something on your end (AV software, maybe pop-up blocker). The flash is the browser trying to open a new tab/window to go to the portal purchase URL, but then something shut it down immediately.

Most likely it is because the query to Ambient Weather returned an error instead of data (or no data). They aren't known for their reliability. It looks like the AC hasn't read the profile files. If it hasn't read the profile files, it doesn't know how to layout the data so it uses whatever the last node viewed's layout. The main layout should have a lot more values. Restarting the AC will cause it to re-read the profile files. If that doesn't help, re-send the profile files using the Upload Profile button on the PG3 node details page and then restart the AC again after that.

@Bumbershoot I think the problem is that you changed the wrong credentials in PG3. You said: The username/password on the Profile tab are the credentials that the UI will use to talk with the PG3 server side and aren't related to the ISY at all. That exist to allow you to restrict who can run the PG3 UI. The ISY credentials are under the ISYs menu by selecting the Edit Current ISY option. That shows the ISY IP Address, port, username, and password. The username/password here needs to match what you set the IOP username/password to. @jkrausDeleting the ISY and re-adding could cause problems with existing node server installations. That probably causes it to recreate security tokens so it ends up looking like a new ISY. I don't believe I've had to delete an ISY and re-add it, at least not in a very long time so I'd have to dig through the code to see what that really does internally.

That certainly seems legit. Monitor the PG3 log after the update. There should be a lot of 401 errors before you change it in PG3, but they should stop almost immediately after changing it.

I just tested it myself and everything worked exactly like I expected. Changed password on admin account using AC Restarted AC to verify that I had to use the new password PG3 was reporting lots of 401 (authentication failed errors) which is to be expected since it is still using the old password. ISY -> edit current ISY, change password to new password and hit save PG3 stops reporting errors and starts communicating properly with ISY. All the node servers have continued to operate without any issues throughout this. I'm not sure what @Michel Kohanimmeant, but the only reason to delete and reinstall a node server would be if you changed to a different ISY. The node server doesn't know the ISY username or password so changing that will not effect the node server. (in general, there are some node servers that communicate directly with the ISY, those may need to restarted to get the new username/password) There may be something else going on with this that I'm not aware of so I can't say for sure that an uninstall/re-install wasn't required, but just changing the ISY password does not require node servers to be uninstalled/re-installed. @BumbershootIt sounds like there was something wrong with the credentials you entered in PG3. Possibly not even your fault. I seem to remember there being certain restrictions on what could be entered for the ISY password so that maybe what you actually typed wasn't what it ended up being set to. An example of this would be if the ISY limited the length of the password to 8 characters. The AC knows this limit so it always truncates what you type to 8 characters. PG3 doesn't so it would send the longer version and fail to authenticate.

If the password was changed on the ISY and PG3 was not updated with the new password, PG3 will report the errors in it's log (probably lots and lots of 401 (failed to authenticate) errors. You should just be able to update the ISY account info in PG3 under ISY -> Edit Current ISY. If that didn't work, it's a bug. There shouldn't be any need to restart anything let along delete and re-install.

That's been the main goal of PG3. A lot of the node servers for PG2 seem to have been developed but then abandoned since the time it takes to maintain them can quickly become larger than the initial development time. The expectation is that by being compensated for the effort, they'll be more likely to continue maintaining and supporting their node servers. At some point, the default configuration on a Polisy will switch to PG3 being installed and PG2 not being installed by default. Eventually, PG2 may be removed, but that will be a while. Since PG2 is an open source project, how long it remains viable to run on something other than an Polisy will be up to the "community".

In general, the PG3 and/or the node server log will provide information to help understand what is happening.

You'd want to do it from PG2. The PG2 delete will delete the configuration in PG2 and delete the configuration and nodes on the ISY. The delete on the AC will only delete the configuration from the ISY.

You're welcome. There actually is an issue entered to restore individual node servers from PG2. Right now, resources to work PG3 features is limited. A feature like that is a convenience for the initial migration and will likely never be used after that. So it's hard to justify spending resources on something like that.

Wake-On-Lan node server now in the PG3 node server store.

No, it's probably not an ISY thing, I must still have something wrong in the profile files or you don't have the most recent profile files loaded in the AC. Here's what I see on mine: Try the "Upload Profile" button on the PG3 node details page and then restart the AC.

No, the restore is kind of an all or nothing. As part of the restore, it changes the configuration on the ISY to point back to the PG3 version. If you then delete the PG3 version, it will delete the node server from both PG3 and the ISY. The PG2 version will no longer work. Possibly you could then delete the PG2 version and re-install the PG2 . If you just want to partially move to PG3, I'd recommend not trying to use the restore from PG2 backup and just delete the node server from PG2, install the PG3 version in the same slot, re-configure and fix anything that broke. That's the cleanest way and you can concentrate on making sure each one works correctly before moving on to the next.

There was a typo in one of the OpenWeatherMap files. I've fixed so the latest version 3.1.3 should show connected/disconnected

In general you can't. But since the migration process is not great, it's not impossible to end up in that situration. You should be fine restoring from a PG2 backup. Just make sure you either delete the node servers from PG2 before doing the restore. The PG3 restore from PG2 backup can't clean up what's on PG2 after the restore.

There have been changes to the way node servers work since this node server was ported. The node server is not responsible for that status value, PG3 is. I've updated the node server so it should work correctly with the latest PG3 design.

It is slot dependent. So if there is a PG2 node server in slot that you are allowed to install and you have a different node server in PG3 slot 2. The restore will overwrite the existing node server in PG3. However, if there isn't any slot "overlap" between what's in the PG2 backup and what's currently installed on PG3, then none of the existing PG3 node servers would be effected.

Added this to the issues list for the node server so I've captured the request.

Try version 2.0.4, I made some changes that I think should fix that.

Seems like that used to work. I wonder if a new version of Python is now more strict about that sort of thing.

Have you installed PG3? I don't believe it is being installed by default yet so you have to manually install it using the instructions in the release announcements for PG3 before you can use it.

No command sent by the ISY to a node is synchronous. In this case, the ISY sends the backup command to the node server node. It does not wait for any response. The node server then queries every lighting type node for it's status. It does this one-by-one. How long it takes to complete will depend on how many devices you have and what else the ISY is busy doing. Polling is not used. It only does the queries when asked and same for the restore.

you can send it directly via a PM here. Ideally, just download the PG3 log and attach that to PM. Also, before you do that, can you verify what version of PG3 your are running?

I did the port of this node server from PG2 to PG3 so it's possible I broke something when I did the port. I don't use Google Calendars so I'm not sure I can thoroughly test it myself. I have no issues installing it. The error "Node server object missing uuid" is not in any of the PG3 code. It also doesn't make any sense because object names can't have spaces so there isn't any objects in PG3 named "Node server". I don't doubt that you're getting an error, but with that information I'm not able to do anything to debug it. PG3 logs showing when you try to install it would help.

I'm wondering what a node server for WOL would look like... Configuration could be via custom parameters: [host] : [mac address] [host2] : [mac address2] I would assume the goal would be to have a program action that sends the WOL packet to one of the configured devices. So would this create a node for each host and that node would have one command to send the WOL packet? Or would a single node with a dynamic parameter list for a send command be better? A node per host would be easier to implement, but that brings up the question @Michel Kohanim, what is the node limit for IOP? It could be a pretty simple node server, so what's it worth?