Everything posted by Jimbo.Automates
-
PG3 Kasa TP-Link Node Server 3.0.7
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.
-
affiliate link
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.
- Elk Readme
-
PG3 ELK Nodeserver 3.0.13
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.
-
PG3 HarmonyHub Node Server 3.0.9
Version 3.02 released see Release Notes
-
PG3 HarmonyHub Node Server 3.0.9
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.
-
PG3 CAO Wireless Tag Nodeserver 3.0.4
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.
-
oauth2 token for PG3 version
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.
-
oauth2 token for PG3 version
Spoke with @bpaauwe and we think this is actually a bug in PG3 which should be fixed in the next release.
-
oauth2 token for PG3 version
I've found the issues but haven't completely fixed. Latest 3.0.3 is better, but still needs some work.
-
PG3 on Polisy
@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.
-
Custom Configuration Parameters missing
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.
-
ISY on Polisy v5.3.0 (IoP) - OUTDATED
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.
-
oauth2 token for PG3 version
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'
-
Custom Configuration Parameters missing
Version 3.0.4 released. The issue is fixed.
-
Custom Configuration Parameters missing
Yes, I understand people jumping on PG3, just have to know with no official announcements of a supported release that you will likely have issues. Personally I was going to wait and announce mine once I get all converted, 9 down 2 to go... Then worry about supporting everyone. There is a issue with FlumeWater, I currently can't use it in production since it doesn't work with my new water meter, so its not as well tested as the others. Thanks for the log, I'll try to get a fix out soon.
-
oauth2 token for PG3 version
Ok,.PM me the log. Sent from my Pixel 6 Pro using Tapatalk
-
oauth2 token for PG3 version
I don't think you can reuse the code. Delete it and restart and reauthorize. Sent from my Pixel 6 Pro using Tapatalk
-
oauth2 token for PG3 version
Oh that's strange, but good. Sent from my Pixel 6 Pro using Tapatalk
-
oauth2 token for PG3 version
Are you on ISY994 or ISY on Polisy? I'll look at mine when I get home tonight, I'm still on ISY994 Sent from my Pixel 6 Pro using Tapatalk
-
oauth2 token for PG3 version
Awesome! Thanks.
-
oauth2 token for PG3 version
Ok crap, sorry, my bad. That's the pyton interface version, which is the latest. Sorry.
-
oauth2 token for PG3 version
The log showed older version, check the PG UI to see what it shows. You need to restart after updating sudo service pg3 restart Sent from my Pixel 6 Pro using Tapatalk
-
oauth2 token for PG3 version
Actually I was mistaken. Looks like your PG3 version is 3.0.31 please delete the NS and upgrade PG3 to to 3.0.36 and try again.
-
oauth2 token for PG3 version
Thanks, as long as that's understood Thanks for the log, there is a bug due to a feature added that was not yet supported on PG, and now that it is I see it wasn't implemented correctly. Please delete the NS and I'll try to get a fix out today.