Verification Request: homebridge-kdk-airy

[eric-vader]

Plugin Name

homebridge-kdk-airy

Link To GitHub Repo

https://github.com/eric-vader/homebridge-kdk-airy

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

I have run this plugin on my own KDK fans since August 2023 (first version: https://github.com/eric-vader/homebridge-kdk-airy-archive, on npm as 1.1.0 since October 2024), before homebridge-kdk-plugin was published in July 2026. Version 2 is a rewrite for Homebridge 2, now released for general availability as open source under GPL-3.0.

Compared with the verified homebridge-kdk-plugin:

• Fans are identified by HASHGUID rather than IP address. No fan addresses are configured, and a fan that changes address is found again by rediscovery.
• A settings page in the Homebridge UI searches the network and lists the fans for naming and per-fan options.
• Adaptive Lighting on the light.
• Swing Mode can control the 1/f Yuragi fluctuation or the reverse direction, or be hidden.
• Night mode is a hidden switch, so it is not part of "turn everything on".
• Fans that stop answering show as No Response and are rediscovered.
• The command sound (off, beep or melody) is configurable.
• Writes are coalesced and retried, with a configurable minimum gap between requests. Writes that change nothing are not sent.
• Models without a light get no light services.
• Tests run the plugin end to end against a UDP fan simulator.

It does not support Homebridge 1.x. Targets Homebridge 2, on Node 22.22.3 or newer.

[github-actions]

🟢 Passed Checks

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• Package JSON: keywords exist and contain 'homebridge-plugin'
• Package JSON: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
• Package JSON: 'preinstall' in scripts is not present
• Package JSON: 'install' in scripts is not present
• Package JSON: 'postinstall' in scripts is not present
• Package JSON: engines.node property is compatible with Node 22
• Package JSON: engines.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 2.4.0
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v2.0.2) matches NPM version (v2.0.2)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains valid JSON Schema
• Config Schema JSON: schema has valid type property
• Config Schema JSON: schema has valid properties for object type
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: pluginAlias matches the platform/accessory registered in code
• Config Schema JSON: the pluginType is set to 'platform'
• Config Schema JSON: contains a name schema property
• Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
• Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
• Security: no known vulnerabilities in dependencies
• Security: no unsafe code patterns detected
• Security: no privilege escalation attempts detected
• Runtime: homebridge installed successfully
• Runtime: no config - homebridge should start without plugin configuration and plugin should not load
• Runtime: platform only - plugin should start with just platform property
• Runtime: minimal required - plugin should start with minimal required configuration
• Runtime: full config - plugin should start with comprehensive configuration
• Runtime: plugin shuts down cleanly within 12s of SIGTERM
• Runtime: plugin restarts cleanly without port conflicts
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

ℹ️ Check Details

• These checks were run against v2.0.2 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.