Bumbershoot Posted January 10, 2022 Posted January 10, 2022 Hi @Jimbo. Upon installing and starting the PG3 version of this nodeserver, there was nothing to prompt me to get an authorization token as there was in the PG2 version. Unfortunately, the token I got for the PG2 version doesn't appear to be valid for the PG3 version. Maybe I'm missing something, but it's not entirely apparent what that would be. Thanks!
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 That's strange, it worked for me and I tested that part a lot. Can you PM me the log file? You are living on the edge moving to PG3 before the NS release announcement 1
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 1 hour ago, Jimbo said: That's strange, it worked for me and I tested that part a lot. Can you PM me the log file? You are living on the edge moving to PG3 before the NS release announcement PM sent. I wanna support the developers, and I don't mind a few cuts and bruises.
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 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. 1
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 5 minutes ago, Jimbo said: Please delete the NS and I'll try to get a fix out today. Will do, thanks!
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 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.
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 (edited) 15 minutes ago, Jimbo said: 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. Hmmm.... Already on 3.0.36. [admin@polisy ~]$ sudo pkg info pg3 pg3-3.0.36 Name : pg3 Version : 3.0.36 Installed on : Fri Dec 31 18:26:57 2021 PST Origin : misc/pg3 Architecture : FreeBSD:13:* Prefix : /usr/local Categories : misc Licenses : MIT Maintainer : andrey@xkinghome.net WWW : https://github.com/UniversalDevicesInc/polyglot-v2 Comment : Polyglot v3 for UDI Polisy Annotations : repo_type : binary repository : udi Flat size : 59.6MiB Description : Polyglot v2 server for Universal Devices ISY994 version 5.x.x WWW: https://github.com/UniversalDevicesInc/polyglot-v2 Edited January 10, 2022 by Bumbershoot
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 The log showed older version, check the PG UI to see what it shows.You need to restart after updatingsudo service pg3 restartSent from my Pixel 6 Pro using Tapatalk
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 Okay, I restarted PG3 and reinstalled the nodeserver, but something's goofy here. The log says it's 3.0.31 2022-01-10 14:20:09,409 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.31 Starting... and the UI says it 3.0.36. I'm going to reboot my Polisy.
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 @Jimbo, a reboot of the Polisy has corrected the problem. I got the appropriate dialogue this time, and now have a token. 1
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 Ok crap, sorry, my bad. That's the pyton interface version, which is the latest. Sorry.
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 1 minute ago, Bumbershoot said: @Jimbo, a reboot of the Polisy has corrected the problem. I got the appropriate dialogue this time, and now have a token. Awesome! Thanks.
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 Hi @Jimbo, I'm seeing an issue with temperature with tag type 13. Reporting actual Celsius when it should be in Fahrenheit. See screenshots...
Jimbo.Automates Posted January 10, 2022 Posted January 10, 2022 Hi @Jimbo, I'm seeing an issue with temperature with tag type 13. Reporting actual Celsius when it should be in Fahrenheit. See screenshots... Are you on ISY994 or ISY on Polisy? I'll look at mine when I get home tonight, I'm still on ISY994Sent from my Pixel 6 Pro using Tapatalk
Bumbershoot Posted January 10, 2022 Author Posted January 10, 2022 5 minutes ago, Jimbo said: 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 This is PG3 with ISY on the Polisy, v 5.30. On polyglot v2 on the ISY994 the value is correct. 1
Bumbershoot Posted January 11, 2022 Author Posted January 11, 2022 49 minutes ago, Jimbo said: Are you on ISY994 or ISY on Polisy? I'll look at mine when I get home tonight, I'm still on ISY994 Hi @Jimbo, you can disregard the temperature issue. It has corrected itself!
Jimbo.Automates Posted January 11, 2022 Posted January 11, 2022 Oh that's strange, but good.Sent from my Pixel 6 Pro using Tapatalk
garybixler Posted January 11, 2022 Posted January 11, 2022 @JimboHi I tried adding wireless tags to pg3 but I can't get past the error. ERROR: Unable to authorize, no client id returned in Node Server Data. Check Log for ERROR I finally did the reboot as suggested above but still can't get past the error and no nodes get loaded. I reused the code from the PG2 install. Thanks Gary
Jimbo.Automates Posted January 11, 2022 Posted January 11, 2022 @JimboHi I tried adding wireless tags to pg3 but I can't get past the error. ERROR: Unable to authorize, no client id returned in Node Server Data. Check Log for ERROR I finally did the reboot as suggested above but still can't get past the error and no nodes get loaded. I reused the code from the PG2 install. Thanks Gary I don't think you can reuse the code. Delete it and restart and reauthorize. Sent from my Pixel 6 Pro using Tapatalk
garybixler Posted January 11, 2022 Posted January 11, 2022 Unfortunately it won't ask for any reauthorization.
Jimbo.Automates Posted January 11, 2022 Posted January 11, 2022 Ok,.PM me the log.Sent from my Pixel 6 Pro using Tapatalk
garybixler Posted January 11, 2022 Posted January 11, 2022 I can't get back on PG2 either. Saw this error on their website. Maybe something wrong on their end. Got code 4c55714a-6e06-408f-af11-14b6b1b5d86f, asking for access token ERROR: Unable to get access token from code, see log I'll give it try tomorrow and send the logs if it still doesn't work. Nothing pressing. Thanks Gary
garybixler Posted January 11, 2022 Posted January 11, 2022 Comparing logs from PG2 and PG3 is looks like maybe PG3 doesn't have a gateway address for the wireless tag NS. Can't bring up polisy settings in PG3 to check.
Jimbo.Automates Posted January 11, 2022 Posted January 11, 2022 2 hours ago, garybixler said: Comparing logs from PG2 and PG3 is looks like maybe PG3 doesn't have a gateway address for the wireless tag NS. Can't bring up polisy settings in PG3 to check. 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' 1
Jimbo.Automates Posted January 12, 2022 Posted January 12, 2022 I've found the issues but haven't completely fixed. Latest 3.0.3 is better, but still needs some work.
Recommended Posts