bpwwer

Looks like a bug in the unit of measure for PG3. It is reporting inches/day but saying mm/day. PG2 is reporting mm/day. .119 inches/day == 3.03 mm/day Will be fixed in the next version.

@macjeffThank you for all the detailed feedback. I can address some of now, and some of this on the list and will be address as time permits. Yes, agreed. As I posted somewhere else (earlier in this thread maybe), the migration process has not been worked on at all. The current PG3 releases have been mainly focus on allowing node server developers to port their node servers and not on all the features needed by normal users. This is good feedback. I'm not sure why installing would be slower, but I haven't tried to compare. I didn't think PG3 was doing anything differently from PG2 when installing a node server. But I can understand if the node server startup/initialization is slower. We've made changes to try and improve the process to make it more reliable and part of that is that there are now cases where some processes wait for others to complete so they can't corrupt each other which was a problem with PG2. This is supposed to be handled by the ISY software so it was removed from PG3. This wasn't a requirement for the Polyglot framework. It has been discussed but there isn't a clear path forward on how this can be implemented within the current framework. This is not likely to be something that will be in the initial release of PG3 if ever. There are some known issues with the store/portal authentication process. In order to access purchase information and make purchases, you need to be authenticated with the Portal. When you authenticate with the Portal the authentication is valid for about 1 hour and that authentication info is only held in memory for security reasons. There is a method to refresh the authentication automatically, which PG3 will do, but in most cases now, the refresh happens after it attempts to access the purchase info so that first attempt fails (which is why you see the message about failed to get purchase info). A refresh or resync after that should succeed. This will be improved, but right now, since it doesn't really effect functionality, it is lower priority.

Everything is being or will be looked at. It just takes time. I'm splitting my time between answering questions, resolving bugs and adding features to PG3. I appreciate all the the folks that are trying to migrate to PG3 as it helps immensely in finding existing issues, but it also means it's going to take some time to look into and resolve them all.

Ok, I understand. This is related to a bug in the ISY where the work-around is run a query. BTW, node server status is no longer true or false in PG3. It's connected, disconnected, and failed although I don't think most node server handle this correctly yet.

That's a known bug in PG3. The browser gets confused and needs a refresh/reload to show the correct data.

Most don't support query because the data is being polled at timed intervals, not by a manual query.

I'm sorry that there are so many issues with migrating from PG2 to PG3, but PG3 is not yet complete and there has been zero development effort to create a migration process at this point. A node server slot on the ISY can only be managed by one Polyglot and if something changes in the configuration of that slot, it can result in Polyglot thinking something else is managing it (i.e. marking it unmanaged). The process should work something like this: backup node servers with PG2. Results in a pg2_node_server_backup_file Stop PG2, PG2 is no longer going to manage the node servers. Restore the pg2_node_server_backup_file using PG3. PG3 will update the slots on the ISY to change management of those slots from PG2 to PG3. Review and possibly restart the node servers on PG3 This is how the process should work, but it may be broken/buggy at this point as it is untested. There is not yet any provision for migrating a single node server or maintaining a mix of PG2 and PG3 node servers. Because only one Polyglot can manage a slot and there isn't any way to migrate a single node server, the only current method is to delete the node server from PG2 (losing all nodes and programming). And then install/configure the node server on PG3 (and recreate any programming).

It only updates the forecast data every 5 minutes by default. Did you give it 5 minutes to pull data the first time?

What do you mean you used the NOAA code? WeatherFlow uses the WeatherFlow station ID to identify the station you want to use for forecast data.

The PG3 version of Climacell should create the same nodes and node values as the PG2 version.

No, there's no conversion and no upgrade. The PG3 node server is a different node server. I wasn't happy with the design choices I used in PG2 so I used PG3 as an opportunity to re-write it.

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.