Google Home migration?? #95

sparky672 · 2019-10-15T17:34:33Z

Google is pushing hard to get me to migrate my Nest account over to Google Home. Before I do that, can anyone tell me if doing such would break my access to this API?

Thank you!

gboudreau · 2019-10-15T17:41:40Z

Yes, it will (break your API access). Don't do it unless you find a working alternative that can work with the Google API, if there is such a thing (didn't look).

sparky672 · 2019-10-15T17:51:27Z

UGH!!!! Thank you! Stupid Google forced me to migrate grandma's Nest account to Google Home in order to update/add/delete family members (for Nest Protect notifications). Now I cannot add myself back into grandma's house without migrating my own Nest account over Google Home, which apparently is going to break this thing for my own house's thermostat.

I wrote a complex application that uses your API code to dump the thermostat data into my online database to track my tank's fuel oil level, graphs, average daily fuel consumption, etc. I really depend on this system since Nest does not have a usage counter built into it anyplace. My circa 1990 Honeywell actually had a resettable hourly usage meter built into it, so Nest takes a huge step backwards in this area.

This system I wrote keeps me from having to dip a stick into the oil tank like a caveman. Thanks Google for effing everything up so badly!

doctorkb · 2019-10-15T18:02:58Z

@sparky672 - I totally agree. The moment Google forces me to switch the account is the moment I head to Costco for the Ecobee 4.

sparky672 · 2019-10-15T18:05:15Z

I like the Nest. Not that I'm opposed to switching... but the amount of time I have invested into my custom data acquisition application is ridiculous. Does Ecobee have a similar API where I can get usage data?

sparky672 · 2019-10-15T18:47:44Z

@gboudreau, I thought your PHP class was accessing the same Nest API server as the Nest App so I'm confused about how this can be broken. Is it a matter of the user account? Once the user account is migrated to Google Home, then the API will reject access to that account, while somehow the Nest App is still able to connect?

doctorkb · 2019-10-15T18:50:49Z

@sparky672 > I like the Nest. Not that I'm opposed to switching... but the amount of time I have invested into my custom data acquisition application is ridiculous. Does Ecobee have a similar API where I can get usage data?

I don't mind the Nest. I do mind that my data is being held hostage.

It looks like Ecobee's API is much more supported: https://www.ecobee.com/home/developer/api/introduction/index.shtml

WRT authentication, I'm betting the Google account authentication uses the Google federated login, not the direct authentication.

sparky672 · 2019-10-16T17:19:35Z

Over in the Homebridge Nest project, they've developed a procedure to get and use the Google token, and login to the API.

And the part that gets the connection is here.

I cannot test this out since I have not migrated my Nest account. My grandmother's account was migrated but she only has Nest Protects. Is there anyone here who already migrated their Nest account to Google, who would be willing to experiment with getting this Nest API project working with the Google tokens?

cagivacode · 2019-10-16T18:25:54Z

I am in the same boat.....and have not migrated my nest account.

I have been recording multi zones and calculating oil usage with great success. Even ran a special "smart" script last year that adapted to outside conditions and saved 100 gallons over the season.

The homeassistant nest project is also stuck.....they all rushed to open API accounts before the cut off.

I am not switching units...so I keep looking for a solution.

sparky672 · 2019-10-16T18:32:34Z

Even ran a special "smart" script last year that adapted to outside conditions and saved 100 gallons over the season.

I've just been gathering and displaying usage data and calculating levels. Also wrote a script that tries to predict a refill date based on past usage. Never tried controlling it or gathering outside temperatures. I thought about trying to gather outside temps to display next to usage but didn't seem super useful.

What did your script do and how did it save your fuel usage?

cagivacode · 2019-10-16T19:07:03Z

Well...I have hydronic heating / oil /multi zone and live in the mid-atlantic which has variable temps in winter.

At first nest saved because it does vary "pre heat" times based on learning of the hydronic system.

After looking at my graphs, I realized that on a regular basis the heat was fighting the lowest temps of the day and not running during the highest temps. So the script does a little "heat banking" during the peak temps of the day (even when no one is home) and does a little deferment during the coldest.

Not real complicated....just heat bank if outside is above a certain temp / defer heating if outside is very cold and normal schedule the rest of the time. Just taking advantage of the non linear nature of heat loss based on the temperature gradient.

In operation it was not real noticeable....occasionally a little warmer / colder in the middle of the night than expected (which mirrored the outside climate).

sparky672 · 2019-10-16T19:10:44Z

Interesting. I have hydronic system too. But I also have variable rate electric, which is basically hourly pricing based on the wholesale market. When electricity is cheap at night, I would crank up the electric heaters and save oil.

I thought about tying my application into that but never finished figuring out how to get the hourly electric rates.

Sal-Tepedino · 2019-10-31T15:48:15Z

I've migrated my account and it broke access.

The badnest project (https://github.com/USA-RedDragon/badnest) managed to get google logins working.
I'd be more than happy to test out google account logins with this project.

sparky672 · 2019-10-31T15:53:39Z

I've migrated my account and it broke access.

The badnest project (https://github.com/USA-RedDragon/badnest) managed to get google logins working.
I'd be more than happy to test out google account logins with this project.

Yes, please!

Sal-Tepedino · 2019-10-31T15:56:30Z

The question is if Guillaume is even interested in modifying the code to fix it, at this point.

sparky672 · 2019-10-31T15:57:45Z

The question is if Guillaume is even interested in modifying the code to fix it, at this point.

Even if not, we can possibly modify it ourselves.

Sal-Tepedino · 2019-10-31T16:00:09Z

True, but I'm more of a bash developer (being a SysAdmin) than a php developer. If you wanna have a crack at it, I'll test it out.

gboudreau · 2019-10-31T16:44:01Z

I just checked the code of badnest; the implementation of how to use a Google account is pretty hackish. Expected, until Google releases better API access (early 2020 for enterprises; maybe later for individuals, if ever).

I could try to implement this, but to do so, I would need to migrate my Nest account to a Google account; not sure I want to do that until I'm sure I can make it work...

If someone who already migrated could provide me with their "issue_token", "cookie" and "api_key", per badnest's instructions, I could try to implement it using those values. (Of note: those values become unusable as soon as you logout from the Nest website, in the browser window that you used to get them. So I would suggest using a regular browser window, not an Incognito one, to get those values, in order to be able to Logout from this session, once I'm done.)

bauzer714 · 2019-10-31T16:47:23Z

Don't post these values publicly though. Please contact @gboudreau through a different medium if you're willing to do so.

Sal-Tepedino · 2019-10-31T17:07:49Z

Isn't there a more 'correct' way to get a google authentication token to your account than this way? Wouldn't that method break any time you close the browser you used to get the token? That wouldn't be good for any sort of long-standing system, right?

sparky672 · 2019-10-31T17:13:11Z

Isn't there a more 'correct' way to get a google authentication token to your account than this way?

No. That's the point. This is not officially sanctioned by Google. You're tricking the API into thinking you're getting access via the Nest app.

Wouldn't that method break any time you close the browser you used to get the token? That wouldn't be good for any sort of long-standing system, right?

My understanding is that you're good for as long as you don't log out of your account. My main browser on my primary computer never asks me to log back into Google... I open Gmail.com and there it is - no login prompt... unless of course I click the "logout" or "switch accounts".

I also maintain other Google accounts for clients so I'm guessing if I log into those with a different browser, I wouldn't be disturbing my own Google log in.

Sal-Tepedino · 2019-10-31T17:21:56Z

Well, yes, I get the 'unofficial-ness' of accessing nest this way, but I'm talking just standard Google auth tokens. Surely there's some application-level way to obtain them that actually IS official, seeing as it's needed for all the other Google application stuff... right? Using the Nest page as the fake API is the unofficial bit. The Google auth token should be well established since it's been around for a while... right? (Please note: I'm claiming no knowledge of how this stuff actually works. Just asking questions that I don't know the answers to)

gboudreau · 2019-10-31T17:30:03Z

When you login on the Nest website, Google uses your session (OCAK cookie) to know which Google account you are logged in as. Using this info, it can then check if you already granted the Nest website access to your Google account. If not, it prompts. If you already granted access, it will use your OCAK cookie (along with some other tidbits) to get a short-lived access token to use the internal Nest API.

Since we, as developers, cannot ask to get access to the internal Nest API from Google, we need to 'steal' the info that the Nest website has been able to get from Google, and use those secrets ourselves to connect to the Nest API, and ourselves get the same short-lived access token that the Nest website is able to get.
This process requires the issue_token, cookie and api_key values.

The process might be simplified somewhat, but we can't use the usual Google API methods of getting an access token; Google are not allowing that.

sparky672 · 2019-10-31T17:33:15Z

Well, yes, I get the 'unofficial-ness' of accessing nest this way, but I'm talking just standard Google auth tokens. Surely there's some application-level way to obtain them that actually IS official, seeing as it's needed for all the other Google application stuff... right? Using the Nest page as the fake API is the unofficial bit. The Google auth token should be well established since it's been around for a while... right? (Please note: I'm claiming no knowledge of how this stuff actually works. Just asking questions that I don't know the answers to)

I'm not sure either. However, since Google is not yet giving anyone API access to Nest data, I doubt anything official they provide could work. Edit: what Guillaume just said ^^^

As a side note, the whole Google thing is still such a totally convoluted mess (cluster-f***):

No support for Nest Protects in the Google Home app despite being forced to manage the Nest Home via the Google app. Forced to use Nest app for Nest Protects despite no way to manage "home" via this app.
Family users are being shown in the Nest app with no way to delete them. Just a message to use the Google Home app to add/remove family members. And yet, these same family members are NOT showing up in the Google Home app. In other words, there are a couple family user names in limbo. No access, cannot remove from Nest app, and yet also not showing up in Google Home app. < oh well, moot point once Google shuts down Nest app.

gboudreau · 2019-10-31T17:37:12Z

I pushed some kind of test code in the dev/google-account branch.
Maybe try that; see test.php on how to test it.
Really not sure my old implementation, which uses the {transport_url}/v3/mobile URL, would work with the info we can get with a Google account...

Sending a post to https://home.nest.com/api/0.1/user/{$this->userid}/app_launch seems to return many URLs; maybe one we need is in there.
Old code also needs a 'user', which I didn't find in basnest code... Not sure it's available in the response of app_launch or not...

gboudreau · 2019-10-31T18:05:26Z

Seems to be working! :)
Try this code, people with migrated Google account:
https://github.com/gboudreau/nest-api/blob/dev/google-account/nest.class.php

This shows you how to instantiate the class, to provide the new information: 26ac4de#diff-93bc3c03503d8768cf7cc1e39ce16fcb

Follow the instructions here to get the required values: https://github.com/USA-RedDragon/badnest#example-configurationyaml---when-you-are-using-the-google-auth-login

Make sure, for the cookie value, to provide all the cookies on one line:

$cookie = 'GoogleAccountsLocale_session=en; GALX=... ; SIDCC=...';

@Sal-Tepedino : maybe now would be a good time to logout, and re-login, in your browser!
Thanks for providing the required detail to work on this.

sparky672 · 2019-10-31T18:10:42Z

Follow the instructions here to get the required values: https://github.com/USA-RedDragon/badnest#example-configurationyaml---when-you-are-using-the-google-auth-login

Instructions copy & pasted here:

The values of "issue_token", "cookie" and "api_key" are specific to your Google Account. To get them, follow these steps (only needs to be done once, as long as you stay logged into your Google Account).

Open a Chrome browser tab in Incognito Mode (or clear your cache).
Open Developer Tools (View/Developer/Developer Tools).
Click on 'Network' tab. Make sure 'Preserve Log' is checked.
In the 'Filter' box, enter issueToken
Go to home.nest.com, and click 'Sign in with Google'. Log into your account.
One network call (beginning with iframerpc) will appear in the Dev Tools window. Click on it.
In the Headers tab, under General, copy the entire Request URL (beginning with https://accounts.google.com, ending with nest.com). This is your $issue_token
In the 'Filter' box, enter oauth2/iframe
Several network calls will appear in the Dev Tools window. Click on the last iframe call.
In the Headers tab, under Request Headers, copy the entire cookie (beginning OCAK=... - include the whole string which is several lines long and has many field/value pairs - do not include the cookie: name). This is your $cookie; make sure all of it is on a single line.
~~In the 'Filter' box, enter issue_jwt~~

~~Click on the last issue_jwt call~~

~~In the Headers tab, under Request Headers, copy the entire x-goog-api-key (do not include the x-goog-api-key: name). This is your $api_key~~

gboudreau · 2019-10-31T18:25:17Z

Pretty sure the $api_key would be the same for everyone: AIzaSyAd...sZE4
(I think this is an API key that was created by the Nest website developers, and will be the same for everyone, until they change it on their side.)
Can you confirm yours is like that?

gboudreau · 2019-10-31T18:26:32Z

Similarly, only the login_hint will be unique in $issue_token :

https://accounts.google.com/o/oauth2/iframerpc?action=issueToken&response_type=token%20id_token&login_hint=UNIQUE_VALUE_HERE&client_id=733249279899-44tchle2kaa9afr5v9ov7jbuojfr9lrq.apps.googleusercontent.com&origin=https%3A%2F%2Fhome.nest.com&scope=openid%20profile%20email%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fnest-account&ss_domain=https%3A%2F%2Fhome.nest.com

gboudreau · 2019-10-31T18:28:58Z

Of note: you'll get this, if the cookie ever becomes invalid (because you logged out, or timed out):

$ php test.php
Error: Response to login request doesn't contain required access token. Response: '(object) array(
   'error' => 'USER_LOGGED_OUT',
   'detail' => 'No active session found.',
)'
$

sparky672 · 2019-10-31T18:42:40Z

Pretty sure the $api_key would be the same for everyone: AIzaSyAd...sZE4
(I think this is an API key that was created by the Nest website developers, and will be the same for everyone, until they change it on their side.)
Can you confirm yours is like that?

I logged into my grandmother's converted Nest account and cannot find x-goog-api-key. Maybe because she only has Nest Protects?

sparky672 · 2019-11-02T16:31:15Z

Apparently breaking the issue_token does not throw a UnexpectedValueException, but rather a RuntimeException.

Here is what I ended up with. Not really sure if/how this can be cleaned up or if it's comprehensive enough.

try {
    $nest = new Nest(NULL, NULL, $issue_token, $cookies);
    // Execute all Nest-related code here: $nest->...()
    $energy_report = $nest->getEnergyLatest();
} catch (UnexpectedValueException $ex) {  // Happens when the issue_token or cookie is not working, for whatever reason
    $error_message = "Unexpected Value Exception: ";
} catch (RuntimeException $ex) {  // Probably a temporary server-error
    $error_message = "Runtime Exception: ";
} catch (Exception $ex) {   // Other errors; should not happen if it worked in the past
    $error_message = "Other Exception: ";
} finally {
    if (! is_null($ex)) {
        $error = $error_message . $ex->getMessage();
        $message = $error . "\n";
        // send email
        $subject	= "Nest Data Dump Failure"; 
        $email		= "*******@gmail.com";
        $headers 	= "From: ***@*****.com\r\n";
        $headers 	.= "Content-type: text/plain; charset=utf-8\r\n";
        mail($email, $subject, $message, $headers);
        die($error . "<br/><br/>");
    }
}

Seems to be working.

bauzer714 · 2019-11-13T21:41:53Z

@gboudreau - can we close this issue?

sparky672 · 2019-11-13T21:44:54Z

Yes... everything seems to be working great! The API is staying logged in and my application has been collecting data as normal. Thank you!

sparky672 · 2019-12-14T15:14:35Z

Everything was working fine until today:

Runtime Exception: Error: Received empty response from request to https://accounts.google.com/o/oauth2/iframerpc?action=issueToken&response_type=token%20id_token&login_hint=xxxx&client_id=xxxx-xxxxxx.apps.googleusercontent.com&origin=https%3A%2F%2Fhome.nest.com&scope=openid%20profile%20email%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fnest-account&ss_domain=https%3A%2F%2Fhome.nest.com.

I x'd out the personal info above. I went to Chrome and followed the whole procedure again to regenerate the token and cookie, but I'm getting the same error.

bauzer714 · 2019-12-14T15:17:54Z

#105

gboudreau · 2019-12-14T15:21:18Z

This issue should be resolved by 8c2dd5c
(published on composer as v1.2.4)

sparky672 · 2019-12-14T15:25:25Z

Yes! Thank you!

sparky672 · 2021-01-23T17:18:36Z

Everything stopped working today. I don't know what's going on since I'm seeing no PHP errors and nothing being reported back from the API.

bauzer714 · 2021-01-23T17:22:29Z

My tokens occasionally need to be renewed, if you haven't done that in awhile.

My thermostat and protects are showing online and getting data, but getEnergyLatest is returning false due to a 500 error. It's broken in the Nest app though as well.

Sal-Tepedino · 2021-01-23T17:30:11Z

I've had one of my thermostats change it's ID on the nest web page to 'DEVICE_#########' (in the URL) instead of the serial number. The other one is still the serial number. I can't query the 'DEVICE_' one at all. Doesn't even show up when I do a blank $nest->getDeviceInfo(); Perhaps related to your issue?

…

On Sat, Jan 23, 2021 at 12:22 PM bauzer714 ***@***.***> wrote: My tokens occasionally need to be renewed, if you haven't done that in awhile. My thermostat and protects are showing online and getting data, but getEnergyLatest is returning false due to a 500 error. It's broken in the Nest app though as well. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AELMMQO5TFHBLNGBAQMLZ6DS3MAWDANCNFSM4JA7YR3Q> .

sparky672 · 2021-01-23T17:36:54Z

My tokens occasionally need to be renewed, if you haven't done that in awhile.

I just tried that and it's not working. I was able to get the new tokens but the result is the same. When following the instructions to use an incognito window, I am now getting a "cookies are blocked" message when attempted to log into my Nest account. This was not an issue when I got the token last.

sparky672 · 2021-01-23T19:21:19Z

What's weird is that I have my program written to catch this. If there is something wrong with the token, it would display this error message. Been working over a year and I can test it by deleting the token parameter.

However, as of this morning, I am getting absolutely nothing now.

try {
		$nest = new Nest(NULL, NULL, $issue_token, $cookies);  // new Nest object
		// Execute all Nest-related code here: $nest->...()
		$energy_report = $nest->getEnergyLatest();  // get the energy report from Nest API
	} catch (UnexpectedValueException $ex) {  // Happens when the issue_token or cookie is not working, for whatever reason
		$error_message = "Unexpected Value Exception: ";
	} catch (RuntimeException $ex) {  // Probably a temporary server-error
		$error_message = "Runtime Exception: ";
	} catch (Exception $ex) {  // Other errors; should not happen if it worked in the past
		$error_message = "Other Exception: ";
	} finally {  // always runs
		if (! is_null($ex)) { // send out messages only if there is an exception
			$error = $error_message . $ex->getMessage();
			$message = $error . "\n" . $footer;
			mail($email, $subject, $message, $headers);
			die($error . "<br/><br/>");
		}
	}

It's blowing right through this code without showing an error message. I just tested it again by putting in a dummy token and get Unexpected Value Exception: Response to login request doesn't contain required access token. Response: null. Then I put in the correct token and I'm getting nothing... the response is empty or blank as far as I can tell.

sparky672 · 2021-01-23T19:26:39Z

I've had one of my thermostats change it's ID on the nest web page to 'DEVICE_#########' (in the URL) instead of the serial number. The other one is still the serial number. I can't query the 'DEVICE_' one at all. Doesn't even show up when I do a blank $nest->getDeviceInfo(); Perhaps related to your issue?
…

I'm not using my device ID at all. I'm just trying to get my data...

    $nest = new Nest(NULL, NULL, $issue_token, $cookies);  // new Nest object
    $energy_report = $nest->getEnergyLatest();

bauzer714 · 2021-01-23T19:32:45Z

The issue is that getEnergyLatest is getting 500 errors from Google and thus you're getting "false" returned. It's not you. The app and the website both tell me I have no data for me after 6+ years. Similar reports across Reddit of missing history data.

There is a gap where there is no exception thrown. It's a weird case that I'll look into adding some resiliency to once the functionality is restored.

cagivacode · 2021-01-23T19:34:09Z

I had the same thing today...it is not a token issue since I still get current temp data.

the energy data is the specific issue (even on the nest app itself).....

and bauzer714 just typed faster than I did...

sparky672 · 2021-01-23T19:34:54Z

The issue is that getEnergyLatest is getting 500 errors from Google and thus you're getting "false" returned. It's not you. The app and the website both tell me I have no data for me after 6+ years. Similar reports across Reddit of missing history data.

ok THANK YOU! I missed your previous response.

There is a gap where there is no exception thrown. It's a weird case that I'll look into adding some resiliency to once the functionality is restored.

Thank you!

bauzer714 · 2021-01-24T00:01:10Z

Pr submitted. #134

bauzer714 · 2021-01-25T19:04:47Z

Nest has fixed the endpoint. I now see data.

Estimated fix time 1740 UTC.

sparky672 · 2021-01-25T19:21:44Z

Nest has fixed the endpoint. I now see data.

Estimated fix time 1740 UTC.

Working here too now.

The time it was fixed coincides with my Facebook conversation with Google Nest. I'm not taking any credit since they clearly have no clue... but was funny that it started working between these comments.

Me: Lisa, same here since Friday and if you log out and back in, it wipes it all out and says "check back tomorrow for history". The underlying issue here is that it's not you - it's everyone. The Google Nest server is returning a 500 error when the history data is requested. Hope they fix it soon.

Google Nest: Thanks for bringing this up, John. What type of thermostat do you have (Nest Thermostat E, Nest Learning Thermostat or the new Nest Thermostat)? Here's how to find out:

Me: I have a Nest Learning Thermostat 3rd gen. I also have two eyeballs and can see all the online reports just like Lisa's and mine.... and the "500 internal server error" coming back from your API when the history data is requested. Why are you not yet acknowledging this this as a widespread issue?

Google Nest: We'd like to isolate what's happening, John. Could you try restarting your thermostat to refresh it's connection? Also, try uninstalling and reinstalling the Nest app. Let us know how it goes.

Me: I did not do a restart or reinstall. The history has been missing and messed up since last Friday, but just now it looks like you guys finally fixed it. Thank you.

sparky672 · 2021-02-23T15:03:43Z

Stopped working today with a 403 error:

Runtime Exception: Error: HTTP 403 from request to https://czfe54-front01-iad01.transport.home.nest.com/v5/subscribe. JSON error: -

Still have access via app and website. Just no access via this API.

Anyone else?

bauzer714 · 2021-02-23T15:16:05Z

Mine is still working. Timezone is EST.

sparky672 · 2021-02-23T16:16:40Z

Mine is still working. Timezone is EST.

When I put the URL from the error message directly into a browser, I am getting a 400 error...

I'm in the CST time zone.

bauzer714 · 2021-02-23T16:24:05Z

Looks like you're assigned a different transport url. From browser you can see the transport URL that you should be using by filtering for "session" in the network tab in chrome. I can't call if this value is cached or not, but you could try clearing it.

sparky672 · 2021-02-23T16:30:17Z

Looks like you're assigned a different transport url. From browser you can see the transport URL that you should be using by filtering for "session" in the network tab in chrome. I can't call if this value is cached or not, but you could try clearing it.

Are you saying get a new token and cookie? Because this URL and error message are coming from the API, and I have no control over the URL being used or do anything with a cache. It was working fine before today.

I will redo token & cookie now.

bauzer714 · 2021-02-23T16:34:20Z

That wasn't the intention. Your browser is working, I'd confirm which transport URL the web is using. If it's not the one the API is using, then clear the temp cache of your web server to force the API class to newly login. I'm speculating a bit here, it's been awhile since I've had to look into this part.

sparky672 · 2021-02-23T18:11:18Z

I went back a third time and regenerated another new token and cookie.

Now I am getting no errors, but the history dump is completely blank. $nest->getEnergyLatest()

Last 10 days energy report: 
{ 
"keys": [ 
"energy_latest.06AAxxxxxxxxxxx" 
] 
}

06AAxxxxxxxxxxx is the serial number for my Nest Protect

sparky672 · 2021-02-23T18:23:03Z

This code is showing no thermostats.

echo "Devices list (thermostats):\n";
$devices_serials = $nest->getDevices();
jlog($devices_serials);

It's coming back completely blank...

Devices list (thermostats): ----------

sparky672 · 2021-02-25T16:32:21Z

Just wanted to clean up this thread a bit...

I had the same issue as described here: #115 (comment)

Here is what I did to resolve the issue:

Delete/remove the thermostat from account via app.
Did the Reset -> "Reset WWN Connection" from the thermostat's settings menu.
Re-add the thermostat to the account using the QR code and the iOS app.

Energy dump seems to be working. It's show previous 10 days, with only the most recent day (same day as reset) coming up missing. Will edit this when the history resumes.

Notes:

The "Reset" menu on the thermostat no longer shows a "Reset WWN Connection" option.
My history data seemed to be intact. I lost no prior history data, but the day that I did this reset is completely missing from the energy dump. History data collection afterwards is also working fine. The one day is missing from online, app, and the API.
$nest->getDevices() is still not working for some reason.

sparky672 closed this as completed Nov 13, 2019

sparky672 reopened this Jan 23, 2021

Google Home migration?? #95

Google Home migration?? #95

Comments

sparky672 commented Oct 15, 2019

gboudreau commented Oct 15, 2019

sparky672 commented Oct 15, 2019 • edited Loading

doctorkb commented Oct 15, 2019

sparky672 commented Oct 15, 2019

sparky672 commented Oct 15, 2019

doctorkb commented Oct 15, 2019

sparky672 commented Oct 16, 2019 • edited Loading

cagivacode commented Oct 16, 2019

sparky672 commented Oct 16, 2019 • edited Loading

cagivacode commented Oct 16, 2019

sparky672 commented Oct 16, 2019

Sal-Tepedino commented Oct 31, 2019

sparky672 commented Oct 31, 2019

Sal-Tepedino commented Oct 31, 2019

sparky672 commented Oct 31, 2019 • edited Loading

Sal-Tepedino commented Oct 31, 2019

gboudreau commented Oct 31, 2019 • edited Loading

bauzer714 commented Oct 31, 2019

Sal-Tepedino commented Oct 31, 2019

sparky672 commented Oct 31, 2019 • edited Loading

Sal-Tepedino commented Oct 31, 2019

gboudreau commented Oct 31, 2019

sparky672 commented Oct 31, 2019

gboudreau commented Oct 31, 2019

gboudreau commented Oct 31, 2019 • edited Loading

sparky672 commented Oct 31, 2019 • edited Loading

gboudreau commented Oct 31, 2019

gboudreau commented Oct 31, 2019

gboudreau commented Oct 31, 2019

sparky672 commented Oct 31, 2019 • edited Loading

sparky672 commented Nov 2, 2019 • edited Loading

bauzer714 commented Nov 13, 2019

sparky672 commented Nov 13, 2019

sparky672 commented Dec 14, 2019

bauzer714 commented Dec 14, 2019

gboudreau commented Dec 14, 2019

sparky672 commented Dec 14, 2019

sparky672 commented Jan 23, 2021

bauzer714 commented Jan 23, 2021

Sal-Tepedino commented Jan 23, 2021 via email

sparky672 commented Jan 23, 2021

sparky672 commented Jan 23, 2021 • edited Loading

sparky672 commented Jan 23, 2021

bauzer714 commented Jan 23, 2021

cagivacode commented Jan 23, 2021

sparky672 commented Jan 23, 2021

bauzer714 commented Jan 24, 2021

bauzer714 commented Jan 25, 2021

sparky672 commented Jan 25, 2021 • edited Loading

sparky672 commented Feb 23, 2021

bauzer714 commented Feb 23, 2021

sparky672 commented Feb 23, 2021 • edited Loading

bauzer714 commented Feb 23, 2021 • edited Loading

sparky672 commented Feb 23, 2021 • edited Loading

bauzer714 commented Feb 23, 2021

sparky672 commented Feb 23, 2021 • edited Loading

sparky672 commented Feb 23, 2021 • edited Loading

sparky672 commented Feb 25, 2021 • edited Loading

sparky672 commented Oct 15, 2019 •

edited

Loading

sparky672 commented Oct 16, 2019 •

edited

Loading

sparky672 commented Oct 16, 2019 •

edited

Loading

sparky672 commented Oct 31, 2019 •

edited

Loading

gboudreau commented Oct 31, 2019 •

edited

Loading

sparky672 commented Oct 31, 2019 •

edited

Loading

gboudreau commented Oct 31, 2019 •

edited

Loading

sparky672 commented Oct 31, 2019 •

edited

Loading

sparky672 commented Oct 31, 2019 •

edited

Loading

sparky672 commented Nov 2, 2019 •

edited

Loading

sparky672 commented Jan 23, 2021 •

edited

Loading

sparky672 commented Jan 25, 2021 •

edited

Loading

sparky672 commented Feb 23, 2021 •

edited

Loading

bauzer714 commented Feb 23, 2021 •

edited

Loading

sparky672 commented Feb 23, 2021 •

edited

Loading

sparky672 commented Feb 23, 2021 •

edited

Loading

sparky672 commented Feb 23, 2021 •

edited

Loading

sparky672 commented Feb 25, 2021 •

edited

Loading