Verification Request: homebridge-nest-climate-cntrl

Aperta
#1,346 24 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
nodejs, typescript
Ambito
devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
371
Fork
26
Merge medio
1h
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di homebridge/plugins

Tutte le issue di homebridge/plugins

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.