Nest credentials with google account #100
Comments
|
If you migrated your Nest account to a Google account, you need to provide an issue_token and cookie to the Nest class constructor, instead of a username & password. |
|
thanks..I updated that! Now, I am seeing the following: |
|
Line 895 mentioned in first warning: https://github.com/gboudreau/nest-api/blob/master/nest.class.php#L895 It seems no devices are listed in the response from the server. Try to add a line, after line 1004: [1004] $this->last_status = $status;
[1005] var_dump($status); die();This will show you the complete response from the Nest server, which, I guess, would contain no devices. Maybe inspecting this response will show you part of the solution... Maybe you have multiple homes, and the nest.class.php is using the wrong one..? |
|
thanks.. I double checked my $issue_token & $cookies again and I get the same error. |
|
You can send it here: https://www.pommepause.com/contact/ |
|
super - were you able to see what i sent? |
|
The Nest API returns no devices for the account you used. It has one structure (home/location), but no devices in that location. |
|
hmmm... I did follow the steps in the readme with the same results.
Can I please confirm the formatting of the cookies? I see
"1P_JAR=2019-11-30-22;
OCAK=....."
should I delete spaces after the semicolon?
…On Sat, Nov 30, 2019 at 5:02 PM Guillaume Boudreau ***@***.***> wrote:
The Nest API returns no devices for the account you used. It has one
structure (home/location), but no devices in that location.
I suggest you follow again the steps listed in the README, to get the
proper cookies and issue_token values for the Google Account that is used
to access your Nest devices.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#100?email_source=notifications&email_token=ADXS3J7TGTK5VEAJ4NPIHP3QWLPGFA5CNFSM4JSW5HA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQU2JA#issuecomment-560024868>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXS3J5VLMQJP4UIXHA4TR3QWLPGFANCNFSM4JSW5HAQ>
.
|
|
Are you logged in more than one Google account? I had the same problem and needed to use incognito so it was only the one account |
|
yes, I used incognito mode to pull the information.
…On Sat, Nov 30, 2019 at 6:03 PM bauzer714 ***@***.***> wrote:
Are you logged in more than one Google account? I had the same problem and
needed to use incognito so it was only the one account
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#100?email_source=notifications&email_token=ADXS3J2SLRU7CYWY6M2ZN4DQWLWMLA5CNFSM4JSW5HA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQVU5Y#issuecomment-560028279>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXS3J4XG76OPILQXS2A5DTQWLWMLANCNFSM4JSW5HAQ>
.
|
|
@k-rock I'm not sure if you ever worked this out. I had the same issue after someone inadvertently converted the nest account to a google account this morning. In my case, my google account then had to be added to the family and was not the primary account. When I used my account to set this up, I got the same messages as you and it did not list any devices. When I used the main google account, it seems to work fine. |
Yesterday I had a new issue where the google server was returning 403 errors on the transport URL. I generated new token and cookie and was able to get past this issue, but still not working correctly. Currently having an issue where no devices are showing up, but it allows me to login without the 403 server errors. I just generated a new token and cookie using Chrome incognito mode but still nothing. Results in a blank list: The energy usage dump: Results in this: Where None of this is making any sense to me and was all working fine before yesterday. Since I am no longer getting any error messages, and everything looks good on the Nest website and iOS app, not sure what would be the next step here. |
|
Any chance you're seeing this issue? |
I don't know. I migrated Nest to Google over a year ago and basically this was all working until yesterday's 403 errors, which after a new token/cookie turned into no more errors but a missing thermostat. I'm seeing the thermostat on the website and in the app. It's only when using this API that it is not seen. Not getting any server errors or PHP errors. What I don't understand is if this API is simulating calls from the app or website (which are showing a device), then why is no device being returned to this API? |
|
@sparky672 - because Nest and Google change things and we have to react. Please recall this is a free open-source unofficial API and we're trying to help you. Can you help us, help you? We've seen an increase of how devices are being accessed on the web site. Can you confirm which of the below URL formats you see when you access it on the website? "I’m back to accessing my thermostat at https://home.nest.com/thermostat/{serial_number} rather than https://home.nest.com/thermostat/DEVICE_{some_identifier_not_serial_number}, " |
I fully recognize that you're only trying to help and greatly appreciate it. I apologize if my tone came across differently than that... I am genuinely confused about how this works, and not trying to provoke.
|
|
As suspected. You're one of the ones that Nest decided to make an unsolicited update for: Workaround is here: #115 (comment) Other ones: I've been patiently waiting for this to affect me so I can see if a code fix can be put in place. Until then or another developer is impacted the temporary fix is our best path. |
THANK YOU ... now I know I have no choice but to do this reset. According to a commenter, I'm going to lose my history... this is not ideal and was hoping it wasn't the case. |
|
Here is what I did to finally resolve the issue...
It's working again! Notes:
|
|
Although I am completely satisfied that I am able to retrieve my history data, Do not need device data, so it's just an FYI... Result: |
I can confirm that this workaround still works as of July 2021. |
|
Confirming this works as of September 2, 2021. |
|
It only worked for me for a week or so, then it quit working. At this point, it's not worth trying to troubleshoot. |
|
That's disappointing. I looked into the new APIs a bit, and it looks like Google has made it more difficult to reverse engineer. If mine reverts again I may take another look and check out some of the other projects. |
|
FWIW: Mine still seems to be working. |
I am trying to run a php script that references this api.
when I try to run this, i get an error:
sudo /usr/bin/php update_nest_target_humidity.php
PHP Fatal error: Uncaught InvalidArgumentException: Nest credentials were not provided. in /home/homeassistant/.homeassistant/nest.class.php:120
Stack trace:
#0 /home/homeassistant/.homeassistant/update_nest_target_humidity.php(16): Nest->__construct()
#1 {main}
thrown in /home/homeassistant/.homeassistant/nest.class.php on line 120
The text was updated successfully, but these errors were encountered: