My thermostat does not appear when I run the plug-in

tbrune0362 commented 5 years ago

Hi Adrian,

I have followed and double checked all steps provided (updated config.json) for a Google account but still cannot find my thermostat. Can you help me? I have spent several hours a day for the last week trying to get this to work. Thank you.

Thomas034 commented 5 years ago

Posto your config please

adriancable commented 5 years ago

First, check that the Thermostat is visible if you log into your Google Account with the Nest app. If not, then you have another problem.

If you do see the Thermostat, please send me your config.json, and also the output of: homebridge -D

You can email them to adrian.cable@gmail.com. Thanks!

tbrune0362 commented 5 years ago

The thermostat is visible in the Nest app. Followed up with a direct email.

d1g1talweb commented 5 years ago

I have the same issue, plugin installed, config file updated, i can see homebridge reaching out to nest and finding my devices upon restart. I just cant seem to see or add any nest accessories inside of Homekit...

HammerAce42 commented 5 years ago

I recently added a second Thermostat to my Nest account (haven't migrated to a Google account yet) and the new Thermostat does not show up despite restarting homebridge several times. The old devices still show up fine.

adriancable commented 5 years ago

@HammerAce42 - thanks for reaching out. Google is introducing a new API for Nest devices which it seems they are rolling out slowly. It looks like around 5%, or less, of thermostats in the field are connecting with the new API, and I am guessing that you are one of the (un)lucky ones.

The new API is completely different from the old API, and is based on Google protocol buffers rather than REST/JSON. It is rather hard to reverse-engineer but I have made some pretty good progress on doing so, and implementing the new API in homebridge-nest.

It isn't ready yet, but if you are interested in trying an early version to see if it works for you, and help me locate and resolve any issues before release, then please send me an email at adrian.cable@gmail.com and I'll get you going.

-Adrian

mattiacantalu commented 5 years ago

Hello @adriancable , here Mattia. Same issue for me; I've just merged (my bad) old Nest account to new Google one. All my Nest accessories don't work, event if I set up correctly the config.json with google data. I can reach you via email in order to test new integration 😉

adriancable commented 5 years ago

@mattiacantalu - please send me an email at adrian.cable@gmail.com and I'll get you the new code.

mattiacantalu commented 5 years ago

@adriancable email sent!

schramfamily commented 5 years ago

Hey @adriancable!

Thank you so much for all the work you put into this. I had it up and running on a homebridge I setup on my Mac, just to play. Now, after migrating to a Google Account and changing the code accordingly, I get syntax errors. *no syntax errors with the old "Nest" account though...

Can I send you my config and have you look at it real quick? I'm sure I have something in there that shouldn't be.

adriancable commented 5 years ago

Sure, send over the config.

schramfamily commented 5 years ago

Thank you so much!

It is attached. I took out the Google Authentication information. If I need to send it to you with the information in it let me know.

-Aaron

On Sep 20, 2019, at 11:02 AM, Adrian Cable notifications@github.com wrote:

Sure, send over the config.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrisjshull/homebridge-nest/issues/148?email_source=notifications&email_token=ANH637IEODUA6BHGFA3DAULQKTX23A5CNFSM4ISEA5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HFAOI#issuecomment-533614649, or mute the thread https://github.com/notifications/unsubscribe-auth/ANH637I6QLT25INDLAQ4MGTQKTX23ANCNFSM4ISEA5NA.

daveblademan commented 4 years ago

Hey Adrian, just converted over from a Nest to Google sign-in...all was working great in the old set up.. Now getting the following error:

[Nest] Error: You did not specify {'token'} or {'clientId','clientSecret','code'}, one set of which is required for the new API

I was configuring for "googleAuth"...

Is this the same issue as those above ??

Cheers

schramfamily commented 4 years ago

I was getting a syntax error when saving the code replacement.

-Aaron

Sent from my iPhone

On Oct 2, 2019, at 12:10 PM, daveblademan notifications@github.com wrote:

Hey Adrian, just converted over from a Nest to Google sign-in...all was working great in the old set up.. Now getting the following error:

[Nest] Error: You did not specify {'token'} or {'clientId','clientSecret','code'}, one set of which is required for the new API

I was configuring for "googleAuth"...

Is this the same issue as those above ??

Cheers

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

adriancable commented 4 years ago

@daveblademan - that message is from a very old version of the plug-in. Please update to the latest version, then you should be good.

@schramfamily - I don't understand the question. Can you elaborate? Thanks!

daveblademan commented 4 years ago

Thanks Adrian - thought I’d updated it all - will redo it - thanks.

mattiacantalu commented 4 years ago

@adriancable as I said via email the development branch you sent me works correctly on my freeNAS...

bassrock commented 4 years ago

I'm seeing the same issue, the nest shows up in the nest app but does not show up via homebridge nest. Even in the logs.

iron8130 commented 4 years ago

Same issue here too... The thermostat is not showing in the Home app. I am using a google account. I see my 1 Nest thermostat and my 4 Nest protects in the Nest app, but in Homekit, I see 4 Smoke/CO sensors and 1 "Home Occupied" switch.

adriancable commented 4 years ago

@iron8130 - send me an email at adrian.cable@gmail.com and I'll get you a test new version which should work for you.

nflute commented 4 years ago

I have the same problem after migrate to google account (Keep receiving non-stop emails from google "New Log-in to your Nest Account" and that force me to migrate google, wish I had read this first.)

When are you planing to release fix for those who migrated to google account?

adriancable commented 4 years ago

See here: https://support.google.com/googlenest/thread/17510832?hl=en

Need to see how that plays out. Right now it's difficult to fix on our side if Nest sends an email each time you log on.

nflute commented 4 years ago

Now the thermostats are not showing in home app anymore.

malizivko commented 4 years ago

Question, if you migrated your account from Nest to Google, is it all Nest products that are not working or just Thermostat?

I just got homebridge installed and I am trying to get it to work but I dont see any of my Nest items (Thermostat, Nest Protect, Temperature sensors, Doorbell)

dclowd9901 commented 4 years ago

Logs from homebridge -D

[11/29/2019, 2:51:00 PM] [Nest] Initializing Nest platform...
[11/29/2019, 2:51:00 PM] [Nest] Fetching Nest devices.
[11/29/2019, 2:51:00 PM] [Nest] Authenticating via Google.
[11/29/2019, 2:51:01 PM] Loading 0 accessories...

dgileadi commented 4 years ago

First-time setup here with Google authentication, and my newly purchased Nest Thermostat isn't showing up. From the logs:

[12/4/2019, 10:48:02 AM] Loaded plugin: homebridge-nest
[12/4/2019, 10:48:02 AM] Registering platform 'homebridge-nest.Nest'
[12/4/2019, 10:48:02 AM] ---
[12/4/2019, 10:48:02 AM] Loading 1 platforms...
[12/4/2019, 10:48:02 AM] [Nest] Initializing Nest platform...
[12/4/2019, 10:48:02 AM] [Nest] Fetching Nest devices.
[12/4/2019, 10:48:02 AM] [Nest] Authenticating via Google.
[12/4/2019, 10:48:02 AM] Loading 0 accessories...

joemulray commented 4 years ago

what are the chances that newly purchased nest devices are pointing to the new api? I am worried that I might myself in the same situation as @dgileadi

adriancable commented 4 years ago

@joemulray - I believe that for thermostats, the chance of them being on the new API is currently about 5%. I am not aware of any Protects or cameras being on the new API yet.

dclowd9901 commented 4 years ago

Is this just a matter of remapping the api? I may fork and do that for us unlucky ones.

mintakka commented 4 years ago

I think I’m in this unlucky new-api group also. If anyone develops a fix for this on another fork please let me know! 😊

dclowd9901 commented 4 years ago

This is proving to be quite tricky. Google uses gRPC and protobufs to transact. I’m just trying to get initial device info that’s given to the home.nest.com site, and it’s quite difficult to find how that information is fed to the front end.

joemulray commented 4 years ago

same boat 😢

[12/15/2019, 10:54:09 PM] [Nest] Initializing Nest platform...
[12/15/2019, 10:54:09 PM] [Nest] Fetching Nest devices.
[12/15/2019, 10:54:09 PM] [Nest] Authenticating via Google.
[12/15/2019, 10:54:09 PM] Loading 0 accessories..

promiseofcake commented 4 years ago

Question, so this does not work for newly added thermostats? I did a factory-reset of my old thermostat and seem to have lost access via the standard Nest API (non-Google Account). Or is the idea that it's still a roll of the dice if we move to a Google Account to re-gain access?

jjknudsen commented 4 years ago

I'm trying to get two newly installed thermostats up and running on an account that was migrated from a Nest account to a Google account. Tried to do some debugging myself, and the devices property is just an empty array. Is this the expected result if I've been migrated to the new API?

Let me know if there's anyway I can help debug or verify the new code. I'll go ahead and send an email to @adriancable to get access to the new code as well.

dclowd9901 commented 4 years ago

I believe this is what happens if you’ve been migrated. I saw this result as well.

You can try digging through the XHR calls on the home.nest.com page, but I had no luck, and I checked basically every call. I can see the call makeup of, say, changing the thermostat temp. It transmits via base64 protobuf, but I can’t tell how the page gets its initial devices list.

On Mon, Dec 23, 2019 at 3:31 PM Jeremy Knudsen notifications@github.com wrote:

I'm trying to get two newly installed thermostats up and running on an account that was migrated from a Nest account to a Google account. Tried to do some debugging myself, and the devices property is just an empty array. Is this the expected result if I've been migrated to the new API?

Let me know if there's anyway I can help debug or verify the new code. I'll go ahead and send an email to @adriancable https://github.com/adriancable to get access to the new code as well.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrisjshull/homebridge-nest/issues/148?email_source=notifications&email_token=AAKA2EW3AJ7XVEBKSRYF523Q2FC6LA5CNFSM4ISEA5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSD2UY#issuecomment-568606035, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKA2EQQLVHYSICDKOJNRPTQ2FC6LANCNFSM4ISEA5NA .

promiseofcake commented 4 years ago

I think so @JeremyKnudsen, new devices (whether on Google account or Nest account) seem to be communicating over a different endpoint and protocol.

joemulray commented 4 years ago

Is there a fork of this repository, or another development branch we can be working on this, a new refactor of the api?

dclowd9901 commented 4 years ago

I’ll create a fork today

On Tue, Dec 24, 2019 at 6:12 AM Joseph Mulray notifications@github.com wrote:

Is there a fork of this repository, or another development branch we can be working on this, a new refactor of the api

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrisjshull/homebridge-nest/issues/148?email_source=notifications&email_token=AAKA2ETLM6MU74X5KKDZ6YTQ2IKGDA5CNFSM4ISEA5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTIKWA#issuecomment-568755544, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKA2ESVGAHS3Y6YOHFQURTQ2IKGDANCNFSM4ISEA5NA .

dclowd9901 commented 4 years ago

https://github.com/dclowd9901/homebridge-nest

I have a friend who works at Nest, and verified that, internally, google calls their account system Gaia, so that might be a lead for digging through logs.

adriancable commented 4 years ago

No need to create a fork or recreate any work, implementation of the new API is already done (and yes it is complicated). I was waiting for Homebridge to update to HAP-NodeJS 0.5.x so I can support cameras, but in the mean time, you can all try it (without camera support).

Assuming you are using Homebridge on a Mac or Linux (otherwise adjust the paths):

cd /usr/local/lib/node_modules/homebridge-nest
wget https://sidewinder.starlinghome.io/beta/homebridge-nest-experimental24.tar.gz
sudo tar xvfz homebridge-nest-experimental24.tar.gz
sudo npm install

jjknudsen commented 4 years ago

Wow. This is fantastic. Lovely little early Christmas present. I followed the instructions and both my thermostats and all three of my temp sensors showed up and seem to work great.

dclowd9901 commented 4 years ago

Totally surprised and delighted. And I can’t wait to see the code to see what the solution was. This has been driving me nuts!

On Tue, Dec 24, 2019 at 6:55 PM Jeremy Knudsen notifications@github.com wrote:

Wow. This is fantastic. Lovely little early Christmas present. I followed the instructions and both my thermostats and all three of my temp sensors showed up and seem to work great.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrisjshull/homebridge-nest/issues/148?email_source=notifications&email_token=AAKA2ESHY75BZITWPY4HXNLQ2LDS7A5CNFSM4ISEA5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTZYPQ#issuecomment-568826942, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKA2EXQKE6VA5FJTWH7WMTQ2LDS7ANCNFSM4ISEA5NA .

adriancable commented 4 years ago

You're all welcome. Merry Christmas!

mintakka commented 4 years ago

Thank you!! Working perfectly again, Merry Christmas 😁

Radstake commented 4 years ago

homebridge-nest-experimental24.tar.gz detects nest
also send commands to nest
after x time, command / status from Nest not showing in homebrigde
I have e-nest with heatsink

Already greatly help by @adriancable, but does any one else has this issue?

Radstake commented 4 years ago

PS Some extra logging: Nest API call to subscribe to device settings updates returned an error: ENOTFOUND @adriancable

adriancable commented 4 years ago

@Radstake - ENOTFOUND is a DNS lookup error. Most likely cause is something is glitchy with your Internet connection (on your router, or on the device you are running homebridge).

Radstake commented 4 years ago

Thx, for your reaction. So what could be ‘glitchy’? Router and device are setup ok. Never had any DNS failures. Besides homebridge tons of external requests per hour, all error free. Could it be because it’s the setup with the heatsink? Deferent endpoint?

Hartelijke groet,

Erich Radstake

Op 26 dec. 2019 om 17:28 heeft Adrian Cable notifications@github.com het volgende geschreven:

@Radstake - ENOTFOUND is a DNS lookup error. Most likely cause is something is glitchy with your Internet connection (on your router, or on the device you are running homebridge).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

adriancable commented 4 years ago

@Radstake - I'm not sure - it could be a Nest issue. The Nest service was down in many parts of the world yesterday, and it seems people are continuing to have issues today:

https://downdetector.com/status/nest/

Radstake commented 4 years ago

Thx, I’ll have a look

Hartelijke groet,

Erich Radstake

Op 26 dec. 2019 om 18:32 heeft Adrian Cable notifications@github.com het volgende geschreven:

@Radstake - I'm not sure - it could be a Nest issue. The Nest service was down in many parts of the world yesterday, and it seems people are continuing to have issues today:

https://downdetector.com/status/nest/

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

chrisjshull / homebridge-nest

My thermostat does not appear when I run the plug-in #148