Verification Request: homebridge-nest-climate-cntrl

Open
#1,346 24 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
nodejs, typescript
Domain
devtools

Research direction

This is a plugin verification review, not a code change. Start with the checklist in the issue body and the linked repository, https://github.com/pponce/homebridge-nest-climate-cntrl, and check each claim against its README and source. Read the five existing comments first, since the review may already be in progress. Done means each checklist item has a recorded verdict or an open question for the maintainers.

Written by the indexing model from the issue text.

Description

awaiting-final-review request-verification
Plugin Name

homebridge-nest-climate-cntrl

Link To GitHub Repo

https://github.com/pponce/homebridge-nest-climate-cntrl

Plugin Icon (Optional)
Image
The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟢 Yes

The plugin successfully installs and does not start unless it is configured.

🟢 Yes

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

🟢 Yes

The plugin does not contain any analytics or calls that enable you to track the user.

🟢 Yes

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

🟢 Yes

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

🟢 Yes

More Information

Nest Climate Cntrl (homebridge-nest-climate-cntrl) is an independently maintained, climate-focused fork of Nest Accfactory, with substantial additional functionality and a distinct supported device scope.

The plugin focuses on temperature, heating, room airflow and presence-based automation. It does not provide camera, doorbell or floodlight-camera accessories, video streaming or HomeKit Secure Video.

Its added capabilities include:

  • Climate temperature rules: use individual readings or equal averages from Nest and non-Nest temperature sensors exposed through Homebridge. Rules make bounded heating-target adjustments to achieve a desired room temperature.
  • Room fan rules: coordinate Homebridge fans with room temperatures or Nest heating/cooling activity, with fixed or temperature-based speeds and priorities for overlapping rules.
  • Expanded Home/Away definitions: combine Nest Home/Away with other Homebridge motion and occupancy sensors to expose a separate combined occupancy accessory.
  • Redesigned configuration interface: visual rule editors, sensor discovery, execution status, pause/resume controls, settings and contextual help inside Homebridge.
  • Standalone web dashboard: configure climate rules and adjust thermostat or desired room temperatures directly from thermostat cards.
  • Manual-change policies: keep sensor groups active when users adjust temperature, or optionally pause the rule. An optional per-thermostat setting displays the climate group’s reading and desired temperature in Apple Home.
    In addition:
    -Legacy Google authentication: keeps support for compatible existing refresh tokens. If you already have a working legacy token, you can continue using it; this plugin cannot issue a new one.
    -Eco switches: optional Apple Home switches to enter and leave Eco mode.
    -HVAC fan timers: configurable default duration and optional 15-, 30- and 60-minute action switches. These operate the blower connected to Nest.

The project has its own package name, platform identity, maintenance and support. It retains clear credit to Nest Accfactory and its contributors for the underlying Nest/Google integrations and shared HomeKit foundation.

Dominant language
TypeScript
Stars
371
Forks
26
Avg merge
1h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from homebridge/plugins

All issues in homebridge/plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.