homebridge / homebridge/plugins
Verification Request: homebridge-navilink
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 369
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Plugin Name
homebridge-navilink
Link To GitHub Repo
https://github.com/tbaur/homebridge-navilink
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
Dynamic platform for Navien appliances through the NaviLink cloud. HomeKit tiles for hot water and space-heating setpoints, power, recirculation, a fault contact, and temperature probes. State arrives over MQTT; the poll is a backstop. There is no other verified NaviLink or Navien plugin.
Settings GUI signs in and lists only the accessories the gateway reports. Bad config disables the platform and leaves cached accessories registered. Nothing is written outside the Homebridge storage path. No analytics.
Confirmed on an NCB-240E. Other families use the same cloud interface.
Contributor 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.
Research direction
Review the verification checklist and the linked homebridge-navilink repository, starting with the plugin configuration and the behavior described in the request. Confirm installation, configuration, storage, error handling, and functionality claims; done means the verification request is approved or a specific unmet requirement is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100