Verification Request: homebridge-cmd4-advantageair (reinstatement)

Open
#1,338 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
documentation

Research direction

Start by reading the verification requirements and the linked cleanup commit to understand how archived repositories lost verified status. The issue asks whether this plugin can be reinstated or needs a new assessment; the decision depends on the requirements and the plugin’s stated storage and functionality limitations. Done means providing a clear eligibility decision to the maintainer.

Written by the indexing model from the issue text.

Description

awaiting-changes request-verification
Plugin Name

homebridge-cmd4-advantageair

Link To GitHub Repo

https://github.com/mitch7391/homebridge-advantageair/tree/v3-maintenance

Plugin Icon (Optional)

No response

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟠 No (please explain in the more information box at the end)

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.

🟠 No (please explain in the more information box at the end)

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

🟢 Yes

More Information

Hi Homebridge team!

I'm the maintainer of homebridge-cmd4-advantageair, which was previously Homebridge Verified.

I noticed its verification was removed on 11 July 2025, as part of a cleanup of archived repositories:

https://github.com/homebridge/plugins/commit/91ad74cfa60ca936ba1eb3b01fa7713eb07d0c9c

The repository was archived after my twins were born, but I've since unarchived it and resumed active development and maintenance.

I'm currently developing a separate native v4 replacement (homebridge-advantageair), which has reached Beta 3. The original v3 plugin remains available for existing users during the transition.

Would it be possible to reinstate the original plugin's verification now that the repository is active again?

I understand the verification requirements may have changed, and I intend to apply separately for the separate native v4 plugin once it reaches stable.

Regarding the "No" responses above, I recognise that the legacy Cmd4-based implementation may not meet every current verification requirement, particularly around temporary file storage. This is among many architectural limitations being addressed by the native v4 rewrite. I also recognise that other verified plugins verified after mine, including homebridge-myplace and homebridge-myplaceiq, offer overlapping Advantage Air functionality. My original Cmd4-based implementation takes a different approach, with its own configuration and accessory options.

As this is a request to reinstate previously granted verification rather than a new plugin application, I wanted to clarify whether that overlap would affect eligibility for reinstatement.

As this plugin was previously verified and was removed during the archived-repository cleanup, I'm primarily seeking clarification on whether its original status can be reinstated during the transition, or whether a new verification assessment would be required.

Thanks for your consideration!

Cheers,
Mitch (@mitch7391)

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.