Verification Request: homebridge-nuki-mqtt-events

Open
#1,332 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
documentation

Research direction

Read the verification request and follow its repository link to inspect the homebridge-nuki-mqtt-events plugin. Check how it exposes Nuki keypad and fingerprint events as HomeKit triggers and supports the Nuki lock over Matter, then compare those details with the verification criteria in this repository. Done means the request has enough information to determine whether the plugin meets the stated criteria.

Written by the indexing model from the issue text.

Description

awaiting-final-review request-verification
Plugin Name

homebridge-nuki-mqtt-events

Link To GitHub Repo

https://github.com/orenasher/homebridge-nuki-mqtt-events

Plugin Icon (Optional)

No response

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

Exposes Nuki keypad/fingerprint events (who unlocked) as HomeKit triggers via Nuki's built-in MQTT, and the Nuki lock over Matter.

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.