Verification Request: homebridge-nest-climate-cntrl
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
Plugin Name
homebridge-nest-climate-cntrl
Link To GitHub Repo
https://github.com/pponce/homebridge-nest-climate-cntrl
Plugin Icon (Optional)
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from homebridge/plugins
-
awaiting-final-review request-icon
Difficulty 1/5 Under an hour Newbie friendliness 70/100
homebridge/plugins#1376 · 1 comment ·
-
awaiting-final-review request-verification
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
homebridge/plugins#1331 · 2 comments ·
-
awaiting-final-review request-verification
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
homebridge/plugins#1288 · 1 comment ·
-
awaiting-changes request-icon
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
homebridge/plugins#1222 · 8 comments ·
-
awaiting-final-review request-verification
Difficulty 4/5 3-5 days Newbie friendliness 35/100
homebridge/plugins#1374 · 2 comments ·
All issues in homebridge/plugins
Similar issues
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: testing bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
snapotter-hq/SnapOtter#5099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EveryInc/compound-engineering-plugin#2091 ·
Maintainers usually reply within 1 day