homebridge-winix-purifiers

[bcullman]

Link To GitHub Repo

https://github.com/regaw-leinad/homebridge-winix-purifiers

Link To NPM Package

https://www.npmjs.com/package/homebridge-winix-purifiers

Plugin Icon (Optional)

[github-actions]

The following pre-checks failed:

❌ Could not determine plugin name.

Comment /check to run checks again.

[bcullman]

/check

[github-actions]

The following pre-checks failed:

❌ Could not determine plugin name.

Comment /check to run checks again.

[bwp91]

Hi @bcullman

Just looking now to see why there are issues with the plugin name.

We would also normally want/expect the developer of a plugin to request verification.

Are they aware? In agreement?

[bwp91]

/check

[github-actions]

The following pre-checks failed:

❌ Could not determine plugin name.

Comment /check to run checks again.

[bwp91]

/check

[github-actions]

✅ Pre-checks completed successfully.

[bcullman]

Hi @bcullman

Just looking now to see why there are issues with the plugin name.

We would also normally want/expect the developer of a plugin to request verification.

Are they aware? In agreement?

hi @bwp91 -

This is my bad. I have not checked with the author, @regaw-leinad, I am simply an enthusiastic user of the plugin. I did take a moment to review the verification process, and it sorta seemed like this plugin would have passed straight out. When it didn't, I should have closed the PR, but I got distracted.

it does seem the pre-check is passing now. I will proceed however you choose.

[regaw-leinad]

Hi @bcullman and @bwp91 - im only just now seeing this - currently traveling. I appreciate you posting this here for verification. I remember I hadn't taken this step yet due to something i felt was missing from the requirements, but I can't quite remember off the top of my head (and while on mobile). I'll sit down and take a look when I get settled.

I'm on board for this as long as it's passing the requirements.

[github-actions]

• General
  • The plugin must be of type dynamic platform.
  • The plugin must not offer the same nor less functionality than that of any existing verified plugin.
• Repo
  • The plugin must be published to NPM and the source code available on a GitHub repository, with issues enabled.
  • A GitHub release should be created for every new version of your plugin, with release notes.
• Environment
  • The plugin must run on all supported LTS versions of Node.js, at the time of writing this is Node v18 and v20.
  • The plugin must successfully install and not start unless it is configured.
  • The plugin must not execute post-install scripts that modify the users' system in any way.
  • The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
• Codebase
  • The plugin must implement the Homebridge Plugin Settings GUI.
  • The plugin must not contain any analytics or calls that enable you to track the user.
  • If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.
  • The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.

---

---

Comment /check to run checks again.

[bwp91]

I'm happy to mark this plugin as verified. There are a couple of items that are technically not satisfied:

The plugin must be of type dynamic platform.

This was a new rule that I implemented to push new developers to creating platform-based plugins. Since this is an established plugin already, happy to waive the rule.

A GitHub release should be created for every new version of your plugin, with release notes.

Please do this in the future! The Homebridge UI displays release notes when a user updates the plugin, and these are pulled from GitHub, so this is the reasoning for this requirement.

@regaw-leinad if you have any questions about this please feel free to reach out 😀