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.

remko2000 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...

Is there someone who can share his/heres json file? I'm struggling with the right structure of my json with the info of my my nest with googleAuth. I used to work with the old client ID, clienttoken, etc. but now I'm migrated to google I also want my nest to show up in my homebridge/homekit again on my raspberry. I've already the right info of my googleauth like issuetoken, cookies, api. but how do I process this in my Json. Where do I put:

"googleAuth": { "issueToken": "xxx", "cookies": "xxx", "apiKey": "xxxxx"

into my json?

jjknudsen commented 4 years ago

Your log suggests you're authenticating just fine. I'm guessing it's the same issue I faced with the new API. Have you followed the suggestions in this comment above to test the fixes for the new API?

remko2000 commented 4 years ago

I try but: ' https://sidewinder.starlinghome.io/beta/homebridge-nest-experimental24.tar.gz' leaves my an error on my raspberry (No such file or directory).

Can someone help me with the right pads for install on a raspberry?

changochulo commented 4 years ago

You rock. This fixed the issue for me. My nest thermostat is now showing up in Homekit. Thanks!

reedickulus commented 4 years ago

Can you please provide guidance on how to do this if I am using HOOBS on Raspberry Pi? I tried following the guide for "manual plugin" install in HOOBS, but it did not work.

apabari commented 4 years ago

Hi @adriancable , thanks for this post. I upgraded to a Gen3 Thermostat the other day, and was wracking my brain trying to figure out why it wasn't showing up on Homebridge anymore. Thanks again for this fix.

I noticed that my Nest Camera is now showing up too, but it says "No Response". Is this to be expected, because this is still a test / experimental branch?

Thanks !

adriancable commented 4 years ago

Nest Camera support will need to wait for an update to Homebridge/HAP-NodeJS. You can read the details in the Homebridge issues list on Github if you’re interested.

From: apabari notifications@github.com Reply to: chrisjshull/homebridge-nest reply@reply.github.com Date: Monday, December 30, 2019 at 9:33 PM To: chrisjshull/homebridge-nest homebridge-nest@noreply.github.com Cc: Adrian Cable adrian.cable@gmail.com, Mention mention@noreply.github.com Subject: Re: [chrisjshull/homebridge-nest] Thermostat not showing in HomeKit (Google Account) (#148)

Hi @adriancable , thanks for this post. I upgraded to a Gen3 Thermostat the other day, and was wracking my brain trying to figure out why it wasn't showing up on Homebridge anymore. Thanks again for this fix.

I noticed that my Nest Camera is now showing up too, but it says "No Response". Is this to be expected, because this is still a test / experimental branch?

Thanks !

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

remko2000 commented 4 years ago

I've deinstalled my old nestplugin 3.5 en installed this one on my raspberry (download the image on my mac, unzipped it it and filezilla'ed into the right folder into my raspberry and then installed it with: sudo npm install). After that I updated Json and my thermostate and my smokesensors show up. Very glad it works and Adrian; many thx for your good work! Awesome plugin.

jjknudsen commented 4 years ago

What error are you getting? The download link is still valid. Make sure you are running the proper command to download.

wget https://sidewinder.starlinghome.io/beta/homebridge-nest-experimental24.tar.gz

reedickulus commented 4 years ago

Can you please place the most recent update with the implementation of the new API in the Hoobs repository? Thank you so much.

rtgoodwin commented 4 years ago

This fixed it for me as well, and not on a Google account. (Curse you Gsuite!).

reedickulus commented 4 years ago

Can you run npm pack on the project and upload the .tgz file?

tman15bp commented 4 years ago

Please can you explain how to install this in more detail as it is not working for me I am on Mac

ghost commented 4 years ago

Make sure you have wget installed. I used

brew install wget

then run the rest of the commands

ghost commented 4 years ago

@adriancable Thank you so much for posting the experimental update, greatly appreciated! Ditched my ecobee and got a Nest today after finding your plugin. Sooooo glad to be back on Nest, phew.

You're a lifesaver!

jamezpowell commented 4 years ago

I have tried everything above and I still cannot get my Nest devices to show up. I am using a Nest account, not Google. I see int he logs on startup that it logs into Nest, queries for devices, and then says loading 0 devices. I have 2 cameras and a thermostat that show fine in my Nest app. I am also having an issue where restarting the hoobs service causes "[Nest] Auth failed: rate limit exceeded. Please try again in 60 minutes"

I don't have 2FA on. I used to be able to do this using the tokens and all from Nest, but I recently updated (completely reformatted and started over) everything with homebridge as I was running an old instance and wanted to go the hoobs route.

[Homebridge] [1/27/2020, 6:01:55 PM] [NeatoVacuumRobot] Initializing NeatoVacuumRobot platform... [Homebridge] [1/27/2020, 6:01:55 PM] [NeatoVacuumRobot] Refresh is set to: auto [Homebridge] [1/27/2020, 6:01:55 PM] [Home] Initializing MyQ2 platform... [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Initializing Alarmdotcom platform... [Homebridge] [1/27/2020, 6:01:55 PM] [Nest] Initializing Nest platform... [Homebridge] [1/27/2020, 6:01:55 PM] [Nest] Fetching Nest devices. [Homebridge] [1/27/2020, 6:01:55 PM] Loading 0 accessories... [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Panel (95059875-127) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Back Den Door (95059875-4) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Back Laundry Door (95059875-2) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Back Middle Bedroom Window (95059875-12) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Dining Window (95059875-6) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Front Bedroom Window (95059875-9) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Front Door (95059875-3) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Garage Door (95059875-1) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Garage Window 1 (95059875-13) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Garage Window 2 (95059875-14) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Kitchen Window (95059875-5) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Master Bathroom Window (95059875-11) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Master Bedroom Window (95059875-10) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Middle Bedroom Window (95059875-8) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Office Window (95059875-7) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Loaded from cache: Smoke (95059875-15) [Homebridge] HAP Warning: Characteristic 00000079-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000080-0000-1000-8000-0026BB765291. Adding anyway. [Homebridge] INFO: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded! [Homebridge] GOOD: Refreshing All Device Data | Source: (First Launch) [Homebridge] [1/27/2020, 6:01:55 PM] [Security System] Logging into Alarm.com as jamezpowell [Homebridge] [1/27/2020, 6:01:55 PM] API launched [Homebridge] [1/27/2020, 6:01:55 PM] [Nest] Auth failed: rate limit exceeded. Please try again in 60 minutes [Homebridge] [1/27/2020, 6:01:55 PM] [Nest] Unable to connect to Nest service. [Homebridge] [1/27/2020, 6:01:56 PM] [Home] Initializing platform accessory 'Garage Door Opener (ID: 83397179)'... [Homebridge] INFO: INFO: Your plugin version is up-to-date [Homebridge] NOTICE: Sending Plugin Status to SmartThings | UpdateAvailable: false [Homebridge] NOTICE: Temperature Unit is Now: (F) [Homebridge] NOTICE: Updating Global Values | HubIP: 192.168.1.33 | UseLocal: true [Homebridge] WARN: Devices to Remove: (0) [] [Homebridge] INFO: Devices to Update: (30) [Homebridge] GOOD: Devices to Create: (0) [] [Homebridge] ALERT: Total Initialization Time: (1 seconds) [Homebridge] NOTICE: Unknown Capabilities: [] [Homebridge] INFO: SmartThings DeviceCache Size: (30) [Homebridge] INFO: WebServer Initiated... [Homebridge] INFO: Sending StartDirect Request to SmartThings | SendToLocalHub: (true)

adriancable commented 4 years ago

See #195 - you will probably need to authenticate via access token, as shown in the README. Good luck!

jamezpowell commented 4 years ago

Thank you for the help. I just decided to go ahead and migrate to Google since I found a workaround for my only IFTTT action that required WWN. It’s all up and running now with the google account.

kjustie commented 4 years ago

I have 2 Nest thermostats, 1 of which is no longer showing in Home app, though it does show in the Nest app and web site; it does not appear in Homebridge log when "fetching nest devices." At the beginning of Jan. this thermostat was off the wall (wiring problem) long enough that its battery died and it had to be reconfigured from scratch and re-added to my Nest account like a new device. Is that why it's not appearing in Home, and if so what do I need to do to get it back? Or some other problem? (This thermostat previously appeared in Home; the period it was offline was also a period when NO Nest devices were visible in Home. I just today switched to token authentication (still Nest account), which brought everything back EXCEPT this one thermostat.) thanks

AFN40 commented 4 years ago

Same here. Except my Nest that disappeared has not been recently reconfigured. Additionally, I've always used Google Authentication for access. The other Nest thermostat E works perfectly fine.

kjustie commented 4 years ago

...worth mentioning that my Nest that does NOT work is an E, in contrast to AFN40's E that does work; my working Nest is not an E. So E vs. not-an-E is not the issue, nor is recent reconfig, nor is authentication method since AFN40 is using Google and I'm using Nest (token).

fletchto99 commented 4 years ago

Any chance the experimental version can be cut into a beta release on NPM? I use a docker container called hombridge_gui which re-installs the plugin from the NPM version when restarted causing this to get reset quite often. Thanks 🎉

jessedufrene commented 4 years ago

@AFN40 @kjustie i'm in pretty much the same boat, my nest E stopped working a few weeks ago, it just disappeared from my home app. but a comment from earlier in this issue fixed my problem, quoted below

I'm running on a RPi, so the only thing i had to change to make it work with my setup is the first command. i exclude /local from the path and run as root, as so: cd /usr/local/lib/node_modules/homebridge-nest

and a few notes in case the extra troubleshooting info may be helpful to others or the devs, I have a Nest E (and no other nest products), i've been using the google auth token thing since shortly after it was first supported. it's worked for many months, one day a few months ago it deauthed, i believe i recall it spamming some message every minute or so in the log, and the accessory in the home app would show as not responding. after reauthing, it worked for a few more months until just recently when the accessory just disappeared completely and i started having the issue discussed here. the log didnt spam anything, and when the nest initialized, the log would only show "initializing nest platform" then "fetching nest devices" and move on to the other modules, not saying anything related to the nest anymore. i tried reauthing, updating, and readding the homebridge to home, all to no avail, until i did those quoted instructions, and now everything works fine again

kjustie commented 4 years ago

gamewin1 -- thank you! The steps you outlined worked perfectly (except that I had to substitute "curl -O" for the wget command; running on Mac / High Sierra). Nest E reappeared upon restart and is working normally now.

remko2000 commented 4 years ago

I've got also a problem with this plug in: after installed this plugin (npm homebridge-nest 3.5.1) through Homebridge Config UI X all my google devices (protects, thermostat) appear and works OK but homebridge gets unstable and after about a day all my accessoires (also my domoticz-accessoires) disappear. After re-adding I have to assign everything to a room again. A lot of work. Is this the same problem?

Is this method of installation (npm) incorrect and do I have to follow these steps (after unstalling 3.5.1)?

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

Do this solve the problem of instability?

fletchto99 commented 4 years ago

Hey @adriancable I've forked this repo and added the experimental code in https://github.com/fletchto99/homebridge-nest

I've pubished this to npm under homebridge-nest-fletchto99. If/when you publish a new release with the official version I'll happily remove my fork and published package. I've done this so that I'm able to pull in the latest version automatically into a docker container I use for homebridge.

For other folks manually installing the package please note you can use npm install homebridge-nest-fletchto99 to have the experimental changes. Please note that this fork will likely go away in the future in favor of the official repo.

AFN40 commented 4 years ago

Thanks gamewin1!! Worked perfectly.

maydaydarkhorse commented 4 years ago

I have successfully installed @fletchto99 's fork and now have my thermostat back in Homekit. Any chance someone could help me with the necessary steps to get ffmpeg installed so my cameras will work? All the instructions say on his fork is "install ffmpeg" but for the life of me I can't find any instructions... (yes, I am a noob to all this - any help would be greatly appreciated!)

adriancable commented 4 years ago

Closing now 4.4.0 is released.

bkalai321 commented 4 years ago

cd /usr/local/lib/node_modules/homebridge-nest had to create homebridge-nest with sudo mkdir homebridge-nest wget https://sidewinder.starlinghome.io/beta/homebridge-nest-experimental24.tar.gz needed to use sudo sudo tar xvfz homebridge-nest-experimental24.tar.gz sudo npm install

this solution rocks all I had to do afterward is add my access code to the config.json and all my nests product showed in accessories as well as home app Thanks @adriancable for this

bkalai321 commented 4 years ago

The https://sidewinder.starlinghome.io/beta/homebridge-nest-experimental24.tar.gz site is not available any longer

adriancable commented 4 years ago

It has no purpose. It is an old old beta which eventually became 4.4.0, which itself is out of date compared with the current published version, and has a lot of bugs (hence the ‘experimental’ in the title). There are no circumstances when you would use it over the current published version in github.

@bkalai321 - please just use the current released version on Github. Your thermostat will be there, and everything will work great.

chrisjshull / homebridge-nest

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