Verification Request: homebridge-lindy-classic8

Plugin Name

homebridge-lindy-classic8

Link To GitHub Repo

https://github.com/ikthezeus/homebridge-lindy-classic8

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

homebridge-lindy-classic8 is purpose-built for the Lindy IPower Switch Classic 8, model 32657.

I found no existing verified plugin targeting this Lindy/IPower Classic 8 hardware.

The plugin provides native, momentary HomeKit power-cycle controls for each of the PDU's eight outlets and an optional staggered Power Cycle Everything action. It uses the Classic8's own native OFF/ON operation, allowing a cycle to complete even if Homebridge or network infrastructure is itself being power-cycled.

Temporary PDU delay changes are protected by a recovery journal stored using Homebridge's own storage directory, and the original delay profile is restored and verified after native power cycles.

The plugin:

is a dynamic platform;
includes a custom Homebridge Settings UI;
declares supports-hap;
contains no analytics or user tracking;
has no preinstall/install/postinstall scripts;
requires no non-standard Homebridge startup options;
supports Homebridge 1.8+ and Homebridge 2.x;
is tested in CI on Node.js 22, 24 and 26;
has 16 automated tests plus syntax/package checks.

Version 0.1.9 was hardware-smoke-tested on a physical Lindy 32657 under Homebridge 2.4.0. A native cycle of outlet 3 ("Rack Fans") was accepted by the PDU, the outlet physically powered off and back on, the original ON/OFF delay profile was restored, and no recovery journal remained pending.

The exact hardware-tested npm tarball was subsequently downloaded from the public npm registry and verified byte-for-byte by SHA-256.

npm package:
https://www.npmjs.com/package/homebridge-lindy-classic8

GitHub release:
https://github.com/ikthezeus/homebridge-lindy-classic8/releases/tag/v0.1.9

🟢 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 (v0.1.9) matches NPM version (v0.1.9)
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 v0.1.9 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.

Navigation Menu

Repository navigation

Verification Request: homebridge-lindy-classic8 #1256

Plugin Name

Link To GitHub Repo

Plugin Icon (Optional)

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

The plugin successfully installs and does not start unless it is configured.

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

The plugin does 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 stores them inside the Homebridge storage directory.

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

More Information

🟢 Passed Checks

ℹ️ Check Details

📋 Next Steps

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Verification Request: homebridge-lindy-classic8 #1256

Description

Plugin Name

Link To GitHub Repo

Plugin Icon (Optional)

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

The plugin successfully installs and does not start unless it is configured.

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

The plugin does 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 stores them inside the Homebridge storage directory.

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

More Information

Activity

github-actions commented on Oct 6, 2026

🟢 Passed Checks

ℹ️ Check Details

📋 Next Steps

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions