bpwwer

The restore from PG2 backup does just that. It takes whatever is in the PG2 backup file and attempts to restore it to PG3. It is an extension of the normal backup/restore process but has the various limitations in that the exact same node server must exist for PG3. If the node server isn't available for PG3, that slot will be ignored. Otherwise the slot on PG3 will be overwritten to match the PG2 slot as close as possible.

Yes. You should also be able to just enter multiple station ID's in the configuration and you'll get nodes for all the devices associated with those station. The PG3 version is different from the PG2 version in configuration and the nodes that it creates.

The settings menu -> select profile enter new user id and new password and hit save.

Is this for a Tempest? I wasn't creating a value for battery voltage as part of the node definition. I added it to version 3.0.11

It doesn't have any node values for those items.

Not all node servers offer a trial. I don't know why WeatherFlow doesn't (it should, I just haven't gotten around to enabling it).

We've tried to communicate all along that one of the big changes for PG3 was designing things so third party developers could get compensated for the work creating node servers. As to why PG3 is free, I suspect it's for the same reason the ISY software is free, but that's something @Michel Kohanimwould have to answer. I do understand the pain of migrating. I haven't put much effort into mitigating that yet as PG3 is still being developed and I've been working to get a lot of basic functionality and bugs resolved. Documentation and tools to ease migration have been low on the priority list.

That implies that you already used the trial at one point. Check the Purchases menu on PG3 to see what node servers you've purchased/trial'ed. If it's not showing up there as a TRIAL then either something is wrong or @glarsenremoved the trial option. The documentation link is incorrect for the node server, that's something @glarsenwill have to correct.

Do you get the same error if you invoke the command from the admin console? If so, then it's not a UD Mobile issue for sure. It sounds like more of a PG3 or ISY on Polisy issue. Just to cover everything, have you restarted the ISY after installing the node server? There are known issues with node values with UOM 25 where not everything is fully configured until ISY is rebooted. This doesn't sound like any of those issues, but just to be sure.

One of the reasons PG2 is being deprecated is because of support issues, or lack there of. The main developer of PG2 has stopped supporting it, many of the node servers are currently unsupported because the developers don't have the time to support them for free. PG2 and most of the node servers have an open source license and the source code for them is readily available so if anyone wants to maintain and support them, they are free to do so. It is just the support from UDI that will be going away eventually. UDI has no control over the individual pricing of node servers. Developers are just starting to figure out what that should look like. I'm a bit surprised that most prices are as low as they are. There are other Home Automation environments were similar components start at about $30 and most are more. Sorry this came out a bit defensive, I wasn't trying to be. Just wanted to address some of your concerns which are always welcome.

Didn't know about that link so no, there is not one for PG3 yet.

More information is needed to really understand what is happening. When the ISY starts (after a reboot) it doesn't query the nodes for updated status. So it may simply be waiting for the next update to happen. Depending on the node server, that could be a while. What other nodes servers, besides ecobee are you running? Are there any errors showing up in the PG2 or PG3 log while you've waited for the ISY to get status updates?

The PG3 folder holds the database, the installed node servers, and the log files. PG3 itself is in a different location, /var/polyglot/node_modules which is where the program and all the library modules it needs are installed. In most cases, it's the database that causes the issues. Because of the database engine being used (sqlite3), some changes require removing, recreating, and then restoring the content of a table. If this process fails, there isn't a good way to try and recover. I've made it a more robust in the current version and changes are rare (only two or three in the past 40 releases). The process does backup the database before it attempts to make changes, so even in this case, recovery simply meant replacing the corrupted database with the backup and restarting using the new version. But to answer your question, yes backing up everything and restoring it would work.

For a restore from PG2 to work the PG3 node server must have the same name. If the name is different, it won't work as there is no way to map an old name to a new name. Also, you must have a valid license for the PG3 version. That means that from the node server store listing, the node server must show that you can "Install" it. The restore process won't try to purchase the node server. And lastly, it will carry over the custom parameters from PG2 to PG3, but as @Goose66said, many PG3 version may use different custom parameters, in which case you'd have to reconfigure the PG3 version after the restore.

Deleting and re-installing should always work. However, if you have a number of node servers already installed and working you should be able to recover using the instructions in the post for 3.0.40. @dwengrovitzI made a mistake in the original post and have just updated it. Try the revised instructions and see if that brings them back.

Both fixed in 3.0.10

Verson 3.0.9 was just released that adds some error handling so it shouldn't crash anymore. I'm guessing from the log that the temperature value isn't getting set (or set correctly) which comes from an AIR, not the SKY.

Thanks, yes I saw it, but haven't had time to look into it.

The current process is to stop and restart the node server. When a node server is started, it will check the local version against the version currently listed in the store, if they differ, it will do an install before starting. Eventually this will change and there will be a manual "update button" available to invoke updates in addition to the automatic updating we have today. The current plan is to allow bug fixes to automatically update, but all other types of updates would require the user to invoke the update at their convenience.

It's in the store now. It's not well tested so let me know if there are issues.

Yes, there are plans. It is actually written for PG3 but not tested.

I haven't tried that either. I did test by backing up my PG2 and using that to restore to PG3, but a lot of my node servers didn't have PG3 versions and I didn't have licenses for other. For the few that were left, it did seem to create them correctly in PG3. Keep in mind that PG3 is still considered ALPHA. There are missing features and most definitely bugs that still need to be addressed.

Yes, you can change the user name and password used in PG3 from the settings/profile menu.

I'm assuming those had trial licenses and that you were trying to convert them to perpetual licenses? Did you try refreshing the list after? Does it still say they are trial in the "order id" column?

The current version of the node server will display on the node server store page. You can compare that with the version listed in the node server details. After a restart of the node server (not PG3) they should match. I'm showing the current version of the Harmony Hub node server is 3.0.3 so it looks like you have the most recent. I believe @Jimbowas referring to the version of PG3. Versions prior to 3.0.38 of PG3 had problems updating node servers.