Jimbo.Automates

I didn't imply anyone had an issue with paying just saying that I specify a trial period which allows you to try it out for a while to make sure it's what you want.

Also, anyone how had previously donated to me, there are a couple of you, please let me know when you purchase and I will ask @Michel Kohanim to refund you.

I specify a trial period, usually one month for all of my NS's. I think it shows you that when you click on Purchase.

You must be logged into the Portal. there is a button above all that. Also, because of the issue already mentioned below, I would advise not installing it until PG3 is fixed. There is currently an issue with PG3, it will delete the configuration data that is saved on disk during restart. So please try to avoid restarting polyglot until the next version of PG3. Also, make sure you have read and understood the Moving From PG2 section if you are moving from PG2.

Ya, there's a lot of stuff in that file, including some ping'ing which does fail, then running: curl -s https://pkg.isy.io/script/update121.sh | sudo bash cat /usr/local/etc/udx.d/static/update13.sh | sudo bash and a lot of other stuff, then finally the PG2 log at the end. Which only shows a date of 2021-6-24 so nothing recent. Not sure why PG2 would not be starting up and writing to the log. Does sudo service polyglot status say that it's running?

It's weird that the polyglot log was old, try: sudo service polyglot restart less /var/polyglot/log/debug.log and see what you can see in the log.

The MyQ log shows an SSL error, maybe @Goose66 can help debug? The weird thing is the polyglot.log is old, the last line is: 2021-6-24 08:18:39 [polyglot] info: Caught SIGTERM/SIGINT Shutting down.

Please don't install this yet, found an issue with configuration from my development environment is included in the release. Will fix tomorrow. Sent from my Pixel 6 Pro using Tapatalk

Great! You shouldn't have to reboot, sometimes it takes PG3 a while, like maybe 10 minutes at the most before it sees the slot open. But once PG2 didn't actually clear the slot and I had to delete manually in the AC Sent from my Pixel 6 Pro using Tapatalk

The HueEmulator Polyglot Version 3 Node Server is released. IMPORTANT: There was an issue with PG3 where it deleted the configuration data on restart so device ids could change, which has been fixed. Make sure your PG2 and PG3 are the versions mentioned in the README See the README for more information, including information on moving from PG2. The Release Notes are also available. I had planned to move this to use PyISY 3.x during the conversion, but there are conflicts because PG3 uses PyISY 2.x so we need to convert all that user it at the same time. We will work on this in the future.

The Polyglot Version 3 Node Server for Kasa TP-Link is released. See the README for more information, including information on moving from PG2. The Release Notes are also available.

Thanks, once you hit that link they remember so if you purchase from the same machine they will know. The link goes to https://store.wirelesstag.net which now defaults to the news feed, so if you click on "Indoor" link near the the top you will see their products.

Thanks, fixed it.

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

Version 3.02 released see Release Notes

The Polyglot Version 3 Nodeserver for Harmony Hubs Version 3.0.0 is released. IMPORTANT: There was an issue with PG3 where it deleted the configuration data on restart so device ids could change, which has been fixed. Make sure your PG3 is the versions mentioned in the README See the README for more information, including information on moving from PG2. The Release Notes are also available.

The Polyglot Version 3 Nodeserver for CAO Wireless Tags 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.

Released 3.0.4 which should work better, but it still can fail due to an issue with PG3 that will hopefully be fixed soon.

Spoke with @bpaauwe and we think this is actually a bug in PG3 which should be fixed in the next release.

I've found the issues but haven't completely fixed. Latest 3.0.3 is better, but still needs some work.

@dbwarner5 Moving the Ecobee to PG3 is next on my list, but it's a pretty complicated NS so it may take a while. My intent would be to keep the node addresses the same so programs will still work as expected if you put it in the same slot. However, I have found that even if the node address are the same you have to update/save the program sometimes for it to function. The only exception for all my NS's is that the Controller Node Status is now three states instead of two, now the status are Disconnected, Connected and Failed, instead of just True and False. so any programs referencing it must be edited and updated, even though the program shows the correct status, you still have to update and save. Although possibly just rebooting the ISY would fix them as well, but I'm not sure about that.

Hey @stevehoyt thanks, glad it's working now. Yes, once things settle down we can discuss enhancements or a custom version if necessary. You can start an issue here https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues which is where I look for ongoing issues since they can get lost in the forums.

Thanks @dbwarner5 Appreciate the feedback. @einstein.42 is no longer involved, PG3 is now owned by @bpwwer who has done a ton of work to get it this far and close to production.

From the log you sent, the issue is caused by a bug in the NS related to updates to latest PG3 which I thought was working in the NS but I'll have to take a look later. 2022-01-11 06:51:44,388 Thread-3 udi_interface ERROR udi_interface:write: handler_nsdata() missing 1 required positional argument: 'data'

Version 3.0.4 released. The issue is fixed.