Help: Unable to get Nest Manager 5.1.1 to Authorize Nest


(Rob DeMillo) #1

Hi @tonesto7 and everyone else -

Pretty much what it says on the tin. I’ve enabled the device handlers and SmartApps for the Nest Manager applications from @tonesto7 's github. I enabled OAUTH for Nest Manager (but not for NST Automations, as per the wiki). Everything seems fine, but when I click “ACCEPT” in the Nest Manager app on SmartThings to initiate automation with nest, I just get the “Oops! We encountered an error” on the Login To Nest page.

I did a live logging at that information is below. I’m stumped at this point - thanks for any help you can give.

  • Rob

9df4ac26-41df-460e-8007-fc8607513755 12:33:57 PM: info ||| Nest Manager | AuthToken not found: Directing to Login Page
e4975b6f-22d8-450f-b486-662eaa85e3ac 12:33:29 PM: debug getChildDevices(false), children=4
e4975b6f-22d8-450f-b486-662eaa85e3ac 12:33:29 PM: debug All selectors: []
e4975b6f-22d8-450f-b486-662eaa85e3ac 12:33:29 PM: info Body: [[product:[company:LIFX, name:LIFX A19, capabilities:[has_multizone:false, has_variable_color_temp:true, has_ir:false, has_color:true], identifier:lifx_a19], brightness:1, id:d073d5221619, location:[id:29cf1086614a02de186e26d285b906a0, name:My Home], color:[saturation:0, kelvin:3500, hue:0], connected:true, power:off, label:Dining room table, uuid:02ec76da-efed-46c5-b56e-cdcca025379a, last_seen:2017-06-11T19:33:29Z, group:[id:fa178fe6be9280a8a5581c9e4f822fcd, name:Kitchen], seconds_since_seen:0], [product:[company:LIFX, name:LIFX BR30, capabilities:[has_multizone:false, has_variable_color_temp:true, has_ir:false, has_color:true], identifier:lifx_br30], brightness:0.6999923704890516, id:d073d521c977, location:[id:29cf1086614a02de186e26d285b906a0, name:My Home], color:[saturation:0, kelvin:3500, hue:0], connected:true, power:off, label:Entryway Accent, uuid:02018a2c-757d-4136-8988-c79a08ae6902, last_seen:2017-06-11T19:33:29Z, group:[id:3ae317ec596067d9c64bc7e886dd420b, name:Entryway], seconds_since_seen:0], [product:[company:LIFX, name:LIFX A19, capabilities:[has_multizone:false, has_variable_color_temp:true, has_ir:false, has_color:true], identifier:lifx_a19], brightness:1, id:d073d522153a, location:[id:29cf1086614a02de186e26d285b906a0, name:My Home], color:[saturation:0, kelvin:3500, hue:0], connected:true, power:off, label:Bedroom Bathroom, uuid:02d09462-1d61-4d79-a4aa-b4f76e24c523, last_seen:2017-06-11T19:33:29Z, group:[id:fa178fe6be9280a8a5581c9e4f822fcd, name:Kitchen], seconds_since_seen:0], [product:[company:LIFX, name:LIFX A19, capabilities:[has_multizone:false, has_variable_color_temp:true, has_ir:false, has_color:true], identifier:lifx_a19], brightness:1, id:d073d521eda4, location:[id:29cf1086614a02de186e26d285b906a0, name:My Home], color:[saturation:0, kelvin:3500, hue:0], connected:true, power:off, label:Bedroom Window, uuid:0257b8ae-b218-4132-82c6-404e1e0b8f3f, last_seen:2017-06-11T19:33:29Z, group:[id:9741752f5863cf4200d96778035d048f, name:Master Bedroom], seconds_since_seen:0]]
e4975b6f-22d8-450f-b486-662eaa85e3ac 12:33:29 PM: info Status: 200
9df4ac26-41df-460e-8007-fc8607513755 12:33:03 PM: warn || Nest Manager | Missing: structData null
9df4ac26-41df-460e-8007-fc8607513755 12:32:57 PM: info ||| Nest Manager | AuthToken not found: Directing to Login Page
9df4ac26-41df-460e-8007-fc8607513755 12:32:57 PM: info ||| Nest Manager | appData.json File HAS Changed
c594ec63-017f-4838-b758-09dd6fa569e3 12:32:33 PM: trace getPhrases(), state.welcomeIssue = null


(Rob DeMillo) #2

OK - something happened and now I am getting a different response. When I select “ACCEPT” from the Nest authorization page, Nest returns with “Use this pincode to connect with Nest” followed by a 8 character pincode.

Still: help


#3

To add a little to this. I received a message in my Nest Mobile App earlier this afternoon. See screenshot

I am still running version 5.08 of NST Manager, so I dont think this issue has anything to do with being on 5.1

When authorizing now, I am also presented with this pincode, but there is no further prompting to insert that anywhere. Confirmed IDE logging is same as above posts. Nest Manager no longer appears in Works with Nest and my Thermostats and Protect are offline and unavailable in ST.


(Joe) #4

I also got the notice from Nest that a client has updated. I approved it, but I am not seeing a request for a pin anywhere. I am on nest manager 5.1.0


(jkp) #5

I received this too. I authorized but I was not presented with any pincode. My Nest Manager is still connected and working.

I do have 2FA enabled on my Nest Account as a side note. Also running 5.1 of NM.


#6

Just modified my Nest app for 2 Step verification and got email confirmation.

Went back into SmartThings and into Nest Manager to authorize. First I am presented with the verification key (received in text immediately), and then I am still presented with the following pin code being generated to use.

I suspect this has something to do with Nest specifically since I received that message shown in the earlier screenshot out of the blue.


(jkp) #7

I just received another notice in my Nest app. I ignored the request to authorize so will wait to see what happens.


(Rob DeMillo) #8

@keo we are on 5.1.1 - one more upgrade, you’ll probably see it.


(Rob DeMillo) #9

That’s what I am seeing @WB70 - thanks for confirming


(DavidM) #10

Hi Rob, I have also gotten this message “Oops! We encountered an error”. What did you do to resolve it?


(John) #11

I’m on 5.2.0 and have the sane problem with 2FA on and off, I tried both. @tonesto7


(Anthony S.) #12

Sorry guys i’ve been tied up with work and a new ST project. When you get the oops page it’s becasue our dev id’s are out of tokens. We are now asking new users to create there own dev account to make sure it doesn’t happen any more.

I apologize if the documentation is a big flakey.
http://thingsthataresmart.wiki/index.php?title=NST_Manager#Nest_Developer_Account


(Rob DeMillo) #13

Hi folks.

This happened to me a few months back, butbI literally did nothing to fix
it. I just downloaded the latest version from got hub and the issue
disappeared.


(Anthony S.) #14

It’s not surprising… There have been some platform oddities lately.


(lisa) #15

Thanks for replying to this message. I have a similar problem with the oops error. I have also created a developer account on Nest and copied in the clientid and clientsecret only to have the error before I even get to the works screen. I followed your documentation and checked it over several times but I am sure I have overlooked something. Any suggestions?


(Tim Weatherhead) #16

Hi Tony

Firstly Thanks for the app

I’ve installed Nest Manager v5 and in my “select location” it says you cant currently add this. I dont know why

Do I need to be at home. I’ve created this at work.

Any help greatly appreciated

Thanks Tim


(Brad Langhorst) #17

Sorry to bump this thread, but I’ve had a ton of issues with NST Manager and Google Home. I finally had to have SmartThings Support delete my NST Manager application so I could link Google Home with it. I linked Google Home and reinstalled NST Manager. I got my secrets by creating a Nest dev account per the wiki and entered those into the IDE. When I open the NST smartapp and enter my Nest credentials, I keep getting “Oops! We’ve encountered an error! Please try again.” Any ideas? I’m sure it has to do with the default oauth callback - when I click on the link https://graph.api.smartthings.com/oauth/callback, I get:

Oh No! Something Went Wrong!
Error
500: Internal Server Error
URI
/oauth/callback
Reference Id
e1a86ce5-724e-4770-82e2-bcb0a74d8078
Date
Fri Dec 15 02:56:38 UTC 2017

Is this an issue I need to address with ST Support? I only have Nest Protects and am wondering NST Manager is overkill and if I should look for another solution.


(jkp) #18

Best place to post your question is in the NST Manager thread…


(Brad Langhorst) #19

The problem was discussed in this thread, which is why I posted it here. I just opened a ticket with ST because there is something wrong with my oauth callback link. It will probably take them a week to fix it though…


(jkp) #20

tagging @WB70