brians Posted March 19, 2022 Share Posted March 19, 2022 I get this error... api_key is not defined, must be running local version or there was an error retreiving it from PG3? Must fix or add custom param for local I was getting this error, and a couple others stating that was expired and must re-key. I deleted the app in my ecobee account, tried uninstalling and re-installing the Node server and all I get is this error now. Link to comment
Jimbo.Automates Posted March 19, 2022 Share Posted March 19, 2022 Please download log package and send it to me. Sounds like PG3 is not sending out the auth codes. I'll also try to reinstall on the dev box to see if that happens.Sent from my Pixel 6 Pro using Tapatalk Link to comment
brians Posted March 19, 2022 Author Share Posted March 19, 2022 @JimboAutomatesI noticed the log package contains pg3-current.log which has logins and passwords for all my PG3 nodes. debug.log looks ok, I will send you that for now until I look over other log to make sure. Link to comment
Jimbo.Automates Posted March 19, 2022 Share Posted March 19, 2022 Ok, I'll try to take a look at it later today.Sent from my Pixel 6 Pro using Tapatalk Link to comment
macjeff Posted March 19, 2022 Share Posted March 19, 2022 I have the same issue now. I tried rebooting. Do you want me to PM you my logs? Jeff api_key is not defined, must be running local version or there was an error retreiving it from PG3? Must fix or add custom param for local invalid_grant: The authorization grant, token or credentials are invalid, expired, revoked, do not match the redirection URI used in the authorization request, or was issued to another client. Token expired -160978.383796 seconds ago, so will have to re-auth... Link to comment
Jimbo.Automates Posted March 19, 2022 Share Posted March 19, 2022 This seems to be caused by a change to the PG3 store, I've pinged @bpwwerfor his advice. I'm out today and tonight and traveling tomorrow. Link to comment
Jimbo.Automates Posted March 20, 2022 Share Posted March 20, 2022 What version of PG3 are you guys on? @bpwwer says this may be due to 3.0.47 release which wasn't meant for everyone yet. It shouldn't be an issue with 3.0.46Sent from my Pixel 6 Pro using Tapatalk Link to comment
macjeff Posted March 20, 2022 Share Posted March 20, 2022 3.0.47 It came in about a day or so ago via sudo pkg upgrade. There was a bug in 3.0.46 with backup he was fixing so I was checking every night for an update. So I guess that broke it. Link to comment
brians Posted March 20, 2022 Author Share Posted March 20, 2022 Yes I have 3.0.47 also. Link to comment
Jimbo.Automates Posted March 20, 2022 Share Posted March 20, 2022 Well that's the problem, he didn't announce this version and currently there's no way to release test versions so you'll have to wait for a fix from himSent from my Pixel 6 Pro using Tapatalk Link to comment
Jimbo.Automates Posted March 20, 2022 Share Posted March 20, 2022 PG3 3.0.48 is now released which should fix this issue. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.