Skip to content
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.

[Bug]: nest_token not working #541

Open
ralewis85 opened this issue Feb 28, 2023 · 5 comments
Open

[Bug]: nest_token not working #541

ralewis85 opened this issue Feb 28, 2023 · 5 comments
Labels
bug Something isn't working no-issue-activity This issue does not have recent activity

Comments

@ralewis85
Copy link

ralewis85 commented Feb 28, 2023

Describe the bug

I'm using both the Homebridge Nest and Homebridge Nest Cam plugins. The former works, while the latter is not, in homebridge. I am following this part of the guide https://github.com/Brandawg93/homebridge-nest-cam/wiki/Manual-Authentication

This is the same access_token that homebridge-nest uses if you want to grab from existing config

Debug Output

[2/27/2023, 10:40:49 PM] [Nest-cam] Initializing Nest-cam platform...
[2/27/2023, 10:40:50 PM] [Nest-cam] Nest authentication failed (code undefined).
[2/27/2023, 10:40:50 PM] [Nest-cam] Unable to retrieve access token.

Steps to reproduce

          {
            "nest_token": "<access token>",
            "options": {
                "ffmpegCodec": "libx264",
                "streamQuality": 3,
                "alertCheckRate": 10,
                "alertCooldownRate": 180,
                "alertTypes": [
                    "Motion",
                    "Sound",
                    "Person",
                    "Package Delivered",
                    "Package Retrieved",
                    "Face",
                    "Zone"
                ],
                "importantOnly": true,
                "motionDetection": false,
                "streamingSwitch": true,
                "chimeSwitch": false,
                "announcementsSwitch": false,
                "doorbellAlerts": false,
                "doorbellSwitch": false,
                "audioSwitch": true
            },
            "platform": "Nest-cam"
        }

In comparison I'm using the same access token in Homebridge Nest with the following config, and my thermostat works just fine.

        {
            "name": "Nest",
            "access_token": "<access token>",
            "platform": "Nest"
        }

Device Type

Docker Container

iOS Version

16

Camera Types

Nest Doorbell Wired

Bug Persistence

Consistently

Last Working Version

No response

@ralewis85 ralewis85 added the bug Something isn't working label Feb 28, 2023
@kennyknight
Copy link

kennyknight commented Mar 1, 2023

I am also having the same issue:

homebridge-nest-cam v7.5.4

[3/1/2023, 4:31:59 PM] [Nest-cam] Nest authentication failed (code undefined).
[3/1/2023, 4:31:59 PM] [Nest-cam] Unable to retrieve access token.

Config excerpt (token masked for security):

{
"nest_token": "g.0.eyJraWQiOiIyMzhiNTUxZmXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxAwqtcYlx1MDA5OVwiPcOAW1x1MDA4QVx1MDA4RjNcdTAwMEVjN0bDucOmPS5Xw6TDlVLDqcOVw4rDg1x1MDA4Q3toXHUwMDg5XHUwMDBFwrnDlUVcdTAwMTjCv1xmMcOUZcKgwrXDlF7CqsOtXHUwMDE3w51RXHUwMDA2w4hcdTAwOTEpw7dcdTAwOEE3w7NcdTAwMDVcL8KoOWfDsMK9U8ORwqbCr8OmwqvDly5cdTAwODXDkS3DmWbDmiFcdTAwOTPDgFx1MDAwNj7Dq8O0X8OnXHUwMDkzw7rCsWNcdTAwOTUzw5lOwrrDvTZcdTAwMDPDm09cdTAwMUPDjj4-eHNcdFx1MDA5RntcdTAwOTBcdTAwMUUnXHUwMDk2w6XDh1x1MDAxNStzbcO0XHUwMDEzwqx2w6xdXHRdw45cdTAwMDLCtFx1MDA5QWVuw4VjdlU2XHUwMDEwLcOsMVx1MDAxNktcdTAwMULCoiPDkcKuJcOEw7gobcO9XHUwMDlFfW9dw67Cp3dcdTAwOUZcXFx1MDA4OGArXHUwMDFFeFMkw47DoGRcdTAwOURVXHUwMDlGPlx1MDA4NVpcdTAwODnCp8OIXHUwMDgxTFx1MDAwQsONbVx1MDAxNMK8LWlgXHUwMDAzXHUwMDEww4tLXHUwMDBCUMOKw71jwrzCqFZON8KnXHUwMDg5VFx1MDA5QcOhY2RcZkUiLCJ1dG9rdCI6IkdPT0dMRV9PQVVUSCJ9.kP9ZGs8WvrrdRaoLsH66X3-DUa-Io9BFCnN6yGZMWI36E7NpbB3TLjaUbhxn7ByvBoP40dJiXjgrQSfcvwTvjBlW-p5uUmXnIqzfpLJeiecrCC8gfXqn5lcybhA5NY5kPlpRsNLavsZ9TfdpDE27TFDQGGXXePwysmKQZMDPwSEoyRYUwa-6v0FF1yum8dbgZTYJcnutuEJ9pi0c4dj5vstN0t3se7JuinexJHJ3NSfNiFcqzryitn8ATx0AUGP4rDaDeAE6B7G_mTN1Y298mBFfVQEhhnzyD9FJ-UfL6jveF2O8Qr9isCQBWmyQB0iQXx78e-uIkZJyLGMz-iyM5Q",
"options": {
"ffmpegCodec": "libx264",
"streamQuality": 3,
"alertCheckRate": 10,
"alertCooldownRate": 180,
"alertTypes": [
"Motion",
"Sound",
"Person",
"Package Delivered",
"Package Retrieved",
"Face",
"Zone"
],
"importantOnly": true,
"motionDetection": false,
"streamingSwitch": true,
"chimeSwitch": false,
"announcementsSwitch": false,
"doorbellAlerts": false,
"doorbellSwitch": false,
"audioSwitch": true
},
"platform": "Nest-cam"
}

Followed the directions in the wiki to the letter but cannot get it to authorize. Am running homebridge-nest v4.6.9 using google auth without issue.

@dpacker780
Copy link

Describe the bug

I'm using both the Homebridge Nest and Homebridge Nest Cam plugins. The former works, while the latter is not, in homebridge. I am following this part of the guide https://github.com/Brandawg93/homebridge-nest-cam/wiki/Manual-Authentication

This is the same access_token that homebridge-nest uses if you want to grab from existing config

Debug Output

[2/27/2023, 10:40:49 PM] [Nest-cam] Initializing Nest-cam platform... [2/27/2023, 10:40:50 PM] [Nest-cam] Nest authentication failed (code undefined). [2/27/2023, 10:40:50 PM] [Nest-cam] Unable to retrieve access token.

Steps to reproduce

          {
            "nest_token": "<access token>",
            "options": {
                "ffmpegCodec": "libx264",
                "streamQuality": 3,
                "alertCheckRate": 10,
                "alertCooldownRate": 180,
                "alertTypes": [
                    "Motion",
                    "Sound",
                    "Person",
                    "Package Delivered",
                    "Package Retrieved",
                    "Face",
                    "Zone"
                ],
                "importantOnly": true,
                "motionDetection": false,
                "streamingSwitch": true,
                "chimeSwitch": false,
                "announcementsSwitch": false,
                "doorbellAlerts": false,
                "doorbellSwitch": false,
                "audioSwitch": true
            },
            "platform": "Nest-cam"
        }

In comparison I'm using the same access token in Homebridge Nest with the following config, and my thermostat works just fine.

        {
            "name": "Nest",
            "access_token": "<access token>",
            "platform": "Nest"
        }

Device Type

Docker Container

iOS Version

16

Camera Types

Nest Doorbell Wired

Bug Persistence

Consistently

Last Working Version

No response

I just ran into the same problem. Since I run Homebridge-Nest for my Thermostat, I found there's actually a different way it has to be done now due to changes that Google has been making changes to the API. If you read the below link on how to connect to Nest it steps you through how to do it, requires a few more steps, but it woks.

https://github.com/chrisjshull/homebridge-nest#using-a-google-account

For Homebridge-nest-cam, I found just replacing the access token section with the settings in the above link bypassed the issue for both plugins. So you'll have something like this:

  {
        "platform": "Nest-cam",
        "options": {
            "ffmpegCodec": "libx264",
            "motionDetection": true,
            "streamingSwitch": true,
            "disableAudio": false
        },
        "googleAuth": {
            "issueToken": "<Your issue token>",
            "cookies": "<Your cookies>"
        }
    },

@github-actions
Copy link

github-actions bot commented Apr 8, 2023

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the no-issue-activity This issue does not have recent activity label Apr 8, 2023
@jradwan
Copy link

jradwan commented Apr 10, 2023

Same here. Is this related to the latest Google announcement that the Works With Nest program is being deprecated (along with Dropcams being de-supported)?

In the plug-in, it prompts me to "Click HERE to open the Nest login page." but when I click the link I get:

Access blocked: Nest’s request is invalid

You can’t sign in because Nest sent an invalid request. You can try again later, or contact the developer about this issue.
If you are a developer of Nest, see error details.
Error 400: invalid_request

Details:

Error 400: invalid_request
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob
[Related developer documentation](https://developers.google.com/identity/protocols/oauth2/resources/oob-migration)

edit: aargh, nevermind. I forgot about #516. Followed the instructions here and got my cameras working again.

@Radstake
Copy link

Quick addition. I could got it to work, but it seems google changed the request url parameters. They have added &include_granted_scopes=true after the home.nest.com . I could not get it to work with the extra scopes parameter. But leaving if out seemed to work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working no-issue-activity This issue does not have recent activity
Projects
None yet
Development

No branches or pull requests

5 participants