You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-mac-wakeonlan is a dynamic platform plugin that exposes each Mac as a HomeKit switch and wakes it with Wake-on-LAN. It is published on npm with provenance (GitHub Actions, Trusted Publishing), has a GitHub release with notes for each version, a config.schema.json for the Homebridge UI, an MIT license and a README in English and Italian.
I know homebridge-wol (verified) also does Wake-on-LAN. The main differences are:
It is a dynamic platform plugin (devices are managed as platform accessories) instead of a static accessory plugin.
Real status can be checked by ping or by a TCP port (statusPort), for Macs whose firewall drops ping.
Magic packets go to the broadcast address of every local interface plus unicast to the Mac, which helps on networks with several subnets or VLANs.
Without an IP, the switch works as a pulse instead of showing a wrong state.
Optional sleepCommand to put the Mac to sleep from the Home app.
The plugin does not write files, does not make network calls other than the magic packets, ping and TCP checks to the configured Mac, and contains no analytics. It only runs sleepCommand if the user sets it in the config.
Activity
github-actions commentedon Nov 13, 2026
🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin'keywordsdeclare the supported transports ('supports-hap'and/or'supports-matter')'preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 2.5.0typepropertypropertiesfor object typepluginAliaspluginAliasmatches the platform/accessory registered in codepluginTypeis set to'platform'nameschema propertyhomebridgeis not declared as a runtime/peer/bundled dependencyhap-nodejsis not declared as a runtime/peer/bundled dependencyℹ️ Check Details
v0.0.3of the plugin.📋 Next Steps
All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.
DavideFarina2010 commentedon Nov 17, 2026
/check
github-actions commentedon Nov 17, 2026
🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin'keywordsdeclare the supported transports ('supports-hap'and/or'supports-matter')'preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 2.5.0typepropertypropertiesfor object typepluginAliaspluginAliasmatches the platform/accessory registered in codepluginTypeis set to'platform'nameschema propertyhomebridgeis not declared as a runtime/peer/bundled dependencyhap-nodejsis not declared as a runtime/peer/bundled dependencyℹ️ Check Details
v0.0.3of the plugin.📋 Next Steps
All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.