Jimbo.Automates

OK, found the issues, should really be fixed in 3.0.11. It's actually common code in all my nodeservers so now I need to fix them all. It doesn't occur all the time, only if the ISY is slow to add a new node, which happens...

Thanks for the Log, it just seems PG3 stops, no idea why. I'm discussing with @bpwwer to see if we can figure it out.

Never use the "add all nodes from the admin console" that's not meant for Polyglot... It looks like you also have the issue with multiple copies of the NS running, that's not supposed to happen but seems to be happing to many... Easiest fix is to reboot Polisy, or log in with a terminal and kill the processes. I or @bpwwer or @Michel Kohanim can provide the commands if you need them.

@tmorse305 That sounds correct to me, everything should install. But, shutdown PG2 first. If there are issues we will need help from @bpwwer since I have never done that before.

Yes, and that's a bummer, hopefully that'll be fixed soon. I'll look at the NS log you posted. Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 Notification Nodeserver 3.0.3 is released. See the README for more information, including information on moving from PG2. The Release Notes are also available.

First issue is setting shortPoll is broken, it's done differently in PG3 and guess I never tested that, so just set it in the PG UI. Second issue is strange, seems things just stop... Can you download the main PG3 log and send that to me? I'll try to clear out my inbox again.

Shortpoll shouldn't matter because the tags are no poll'ed the changes are pushed to the NS by the tag manager.

@mbking If you shutdown the PG2 NS and install on PG3 it should just work. The NS only has one identifier so Harmony doesn't care that it moved to a different IP address, it will automatically be seen. Just make sure to change the default port number when you install on PG3 along with setting the other params, then restart. All the same devices will be available since that info is contained on the ISY. However, if you don't copy the config file as mentioned in the doc then the ID's may change so you may have to edit the buttons in the Harmony app. If you leave the PG2 NS in place it will automatically startup if/when PG2 is restarted which will create a conflict, so best to delete it from PG2.

The Polyglot Version 3 Nodeserver for CAO Wireless Tags version 3.0.10 is released. If you are going to buy a Tag Manager or any Tags, please use my affiliate link: https://goo.gl/rXAGk9 See the README for more information, including information on moving from PG2. The Release Notes are also available.

Everything should be fixed with 3.0.10, there was a udi_interface issue and a silly bug created during PG3 conversion.

The issues with PG3 deleting configuration data has been fixed make sure you are running 3.0.38. But be aware if you are on a version before that and upgrade your node addresses may change.

Yes, should be good with PG3 3.0.38 Good to hear about ELK. I did the ISY On Polisy migration and UD Mobile using PG3 ELK NS is super fast now Yes, I think text to Keypads and Speech are highest priority.

Mine was doing the same and Michel asked for logs but it stopped doing it after I turned off the write updates to wireless devices. I have a lot of wireless devices to update one at a time... Sent from my Pixel 6 Pro using Tapatalk

There is an issue with the UDI interface, I'm working with Bob to fix it. Sent from my Pixel 6 Pro using Tapatalk

PG3 3.0.38 and NS 3.0.8 should resolve these issues.

The Polyglot Version 3 Nodeserver for CAO Wireless Tags is released. It should now work as long as you have PG3 3.0.38 or newer. If you are going to buy a Tag Manager or any Tags, please use my affiliate link: https://goo.gl/rXAGk9 See the README for more information, including information on moving from PG2. The Release Notes are also available.

This should be fixed in 3.0.8.

I'm having similar weirdness, it was working fine on my dev environment when installed locally and I wasn't able to install and test from the store until today. Sent from my Pixel 6 Pro using Tapatalk

Looks like you may have the same issue I did, restarting PG3 did not stop the running NS so now 2 copies are running. Simpleist fix is to just reboot Polisy, but if you don't want to do that I can send you commands to kill the existing ones. I had multiple copies of all my NS's running...

I was not able to do the Portal migration because my IoP didn't have Portal even though it showed up at my.isy.io , so I added the trial license for Portal thru my.isy.io, then updated modules in the AC and accepted it in the Portal tab, then the Portal was working and I could do the migration.

There is no way to Migrate PG3 from ISY to ISY On Polisy. I decided to do this migration today and most of my time has been deleting everything on PG3 and reinstalling after pointing to Polisy. Just a warning that if you are moving to PG3 it would be best to migrate to ISY On Polisy first. The PG2 backup and restore on PG3 should work, but I have no experience with it since I moved one at a time originally.

I assume the payment will happen when the 1 month trial period ends? @Michel Kohanim can confirm?

@Javi Can you comment if it's possible to keep our UD Mobile setup including Favorites when moving from ISY to ISY On Polisy? If swap the IP address of ISY and Polisy during the conversion, and change the Portal setting in UD Mobile will it work? Sorry if this has been discussed somewhere else, but would be nice to see it included in the OP.

The Polyglot Version 3 Node server for Ecobee is released. See the README for more information, including information on moving from PG2 The Release Notes are also available.