Formally known as Nest_accfactory, this is a Homebridge plugin I have developed to allow Nest devices to be used with HomeKit including having support for HomeKit Secure Video on doorbells and camera devices

Building and maintaining this project takes time, effort, and resources. If you find it valuable, please consider sponsoring to support its development and future improvements. Your support makes a difference—thank you!

The following Nest devices are known to be supported by this Homebridge plugin:

• Nest Thermostats
• Nest Protects
• Nest Temperature Sensors
• Nest Cameras
• Nest Doorbells
• Nest Heat Links
• Nest × Yale Locks

Note: Google has discontinued support for 1st and 2nd generation Nest Thermostats as of October 25, 2025.
Based on this, these models are expected to stop functioning with this Homebridge plugin.

The accessory supports connection to Nest using a Nest account AND/OR a Google (migrated Nest account) account.

If you have a Nest Account, you’ll need to obtain an access token from the Nest web app.

1. Go to home.nest.com and click Sign in with Nest.
2. After logging in, open home.nest.com/session.
3. You’ll see a JSON string similar to:

   {"2fa_state":"enrolled","access_token":"XXX", ...}

4. Copy the value of access_token near the start (a long string beginning with b) and paste it into your Homebridge configuration.
   • Ignore any other access_token entries further down the string.

Note: Do not log out of home.nest.com, as this will invalidate your credentials.

Google Accounts require an "issueToken" and "cookie", which are unique to your account. You only need to do this once as long as you stay logged into your Google Account.

1. Open Safari in a Private Window
2. Enable the Develop Menu (Safari ▸ Settings ▸ Advanced ▸ check Show features for web developers)
3. Open Develop ▸ Show Web Inspector, then select the Network tab
4. Ensure Preserve Log is checked
5. In the filter box, type issueToken
6. Go to home.nest.com and click Sign in with Google
7. After login, click the iframerpc network request
8. In Headers, copy:
   • Summary ▸ URL this is your issueToken
   • Request ▸ Cookie: this is your cookie, which must include a key starting with SIDCC= (if SIDCC is missing, the cookie is incomplete and authentication will fail)
9. Enter both into your Homebridge configuration

Important: Tokens must be obtained using Safari. Other browsers (Chrome, Edge, Firefox, etc.) do not reliably generate valid or non-expiring issueToken and cookie values and will often result in authentication failures or token expiry.
If you did not use Safari, re-capture the tokens using Safari.

Note: Do not log out of home.nest.com, as this will invalidate your credentials.

When using the plugin configuration with homebridge-config-ui-x, the config.json will be updated/generated with the configuration options available via the web-form. Additional options can be specified in the config.json directly.

Sample config.json entries below

{
    "nest": {
        "access_token": "<nest access token>",
        "fieldTest": false
    },
    "google": {
        "issuetoken": "<google issue token>",
        "cookie": "<google cookie>",
        "fieldTest": false
    },
    "options": {
        "eveHistory": true,
        "weather": true,
        "elevation": 600,
        "hksv": false
    },
    "devices": [
        {
            "serialNumber": "XXXXXXXX",
            "exclude": false
        },
        {
            "serialNumber": "YYYYYYYY",
            "hksv": true
        }
    ],
    "platform": "NestAccfactory"
}

The following options are available in the config.json options object. These apply to all discovered devices and homes.

The following options are available on a per-device level in the config.json devices array. Each device is specified as a JSON object, and the device is identified using the "serialNumber" key with the value of its serial number (in uppercase).

The following options are available on a per-home level in the config.json homes array. Each home is specified as a JSON object, and the home is identified using the "name" key.

To support streaming and recording from cameras, an ffmpeg binary needs to be present. We have specific requirements, which are:

• version 6.0 or later
• compiled with:
  • libx264
  • libfdk-aac
  • libspeex
  • libopus

By default, we look in /usr/local/bin for an ffmpeg binary, however, you can specify a specific ffmpeg binary to use via the configuration option 'ffmpegPath'

A pre-compiled ffmpeg binary that meets these requirements is available from the ffmpeg-for-homebridge project and may be used as an alternative to building ffmpeg yourself.

This is a personal hobby project, provided "as-is," with no warranty whatsoever, express or implied, including but not limited to warranties of merchantability or fitness for a particular purpose. Building and running this project is done entirely at your own risk.

This plugin is only supported when used with official Homebridge installations.
Other platforms or forks such as HOOBS, Home Assistant, or similar derivatives are not officially supported and may not function as intended.

Please note that I am not affiliated with any companies, including but not limited to Google, Apple, or any other entities. The author of this project shall not be held liable for any damages or issues arising from its use.

If you encounter a problem, please raise an issue on the project's GitHub repository. Providing diagnostic details and being available to assist with followup testing is appreciated and helps ensure the issue can be resolved effectively.