Verification Request: homebridge-dibby-wemo

[K0rb3nD4ll4S]

Plugin Name

homebridge-dibby-wemo

Link To GitHub Repo

https://github.com/K0rb3nD4ll4S/dibby-wemo-manager/tree/main/packages/homebridge-plugin

Plugin Icon (Optional)

npm package: https://www.npmjs.com/package/homebridge-dibby-wemo
GitHub repository: https://github.com/K0rb3nD4ll4S/dibby-wemo-manager/tree/main/packages/homebridge-plugin
Plugin author: SRS IT

---

Differentiation from existing verified Wemo plugin

There is an existing verified plugin (@homebridge-plugins/homebridge-wemo) for basic Wemo device bridging. homebridge-dibby-wemo is differentiated by its built-in DWM scheduling engine — a full local automation system not present in any other verified Wemo plugin:

• Schedule rules — turn devices on/off at fixed times or sunrise/sunset on selected days
• Countdown rules — auto turn off/on after N minutes of being in a trigger state
• Always On — health-monitored enforcement; corrects any off-state within 10 seconds
• Away Mode — randomised on/off simulation within a time window
• Trigger rules — IFTTT-style: when device A changes state, control device B
• Multi-device rules — one rule can target multiple devices simultaneously

All scheduling runs entirely within Homebridge — no cloud, no external service, no Belkin account required.

---

Verification checklist

• Offers unique functionality not duplicated by existing verified plugins (full DWM scheduling engine)
• Published to npm: https://www.npmjs.com/package/homebridge-dibby-wemo
• Source on GitHub with issues enabled: https://github.com/K0rb3nD4ll4S/dibby-wemo-manager
• GitHub releases with release notes: https://github.com/K0rb3nD4ll4S/dibby-wemo-manager/releases
• Registered as a dynamic platform (api.registerPlatform)
• Implements Homebridge Plugin Settings GUI (customUi: true, full 5-tab custom UI)
• Runs on Node.js v18 and v20 (no native deps — uses sql.js WASM for SQLite)
• No special TTY or non-standard startup parameters
• No user tracking or analytics
• All files written to Homebridge storage directory (~/.homebridge/dibby-wemo.json)
• config.schema.json present and valid
• No unhandled promise rejections — all async paths have try/catch

---

Custom UI tabs

1. Devices — discovered Wemo devices with on/off toggle and firmware info
2. DWM Rules — full CRUD rules engine with live scheduler status bar
3. Device Rules — native Wemo firmware rules via FetchRules/StoreRules
4. Settings — location config for sunrise/sunset scheduling
5. Help — built-in documentation

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

No response

[github-actions]

🔴 Failed Checks

• GitHub Repo: version mismatch - NPM has v1.0.1 but GitHub package.json has v2.0.1

🟢 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: '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 20
• 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 1.11.4
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• 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: the pluginType is set to 'platform'
• Config Schema JSON: contains a name schema property
• Dependencies: homebridge was not installed as a dependency
• Dependencies: hap-nodejs was not installed as a dependency
• Security: no known vulnerabilities in dependencies
• Security: code patterns flagged for manual review
• Security: no privilege escalation attempts detected
• 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 v1.0.1 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

• Please action these failures and then comment /check to run the checks again.
• If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.
• Remember this is an automatic script: if you think something has been marked as a failure in error, let us know with a reply.
• Feel free to ask any questions you have by replying to this issue.

[K0rb3nD4ll4S]

/check

[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: '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 20
• 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 1.11.4
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v2.0.1) matches NPM version (v2.0.1)
• 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: the pluginType is set to 'platform'
• Config Schema JSON: contains a name schema property
• Dependencies: homebridge was not installed as a dependency
• Dependencies: hap-nodejs was not installed as a dependency
• Security: no known vulnerabilities in dependencies
• Security: code patterns flagged for manual review
• 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: full config - plugin should start with comprehensive configuration
• Runtime: network resilience - plugin should handle network failures without crashing
• 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.1 of the plugin.
• Link to the run workflow: visit →.
• External HTTP requests detected:
  • 📡 http://192.168.1.100:49153/setup.xml
    Methods: GET | Count: 3 | Scenarios: full config, network resilience
  • 📡 http://192.168.1.100:49153/upnp/control/basicevent1
    Methods: GET, POST | Count: 3 | Scenarios: full config, network resilience

📋 Next Steps

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

[bwp91]

Hi @K0rb3nD4ll4S

I wanted to see if you would be interested in becoming a maintainer of the existing verified wemo plugin, and whether you would want to integrate this functionality into that? And then make any updates to that plugin as and when you wanted.

I will always try to recommend there being one, 'super' plugin per brand, rather than multiple (and therefore give you the chance, if you wanted).

Let me know your thoughts 🙂

[K0rb3nD4ll4S]

That sounds like an interesting question. Who is maintaining the plugin now?K0rb1nD4ll4sOn Apr 3, 2026, at 8:31 AM, Ben ***@***.***> wrote:bwp91 left a comment (homebridge/plugins#988) Hi @K0rb3nD4ll4S I wanted to see if you would be interested in becoming a maintainer of the existing verified wemo plugin, and whether you would want to integrate this functionality into that? And then make any updates to that plugin as and when you wanted. I will always try to recommend there being one, 'super' plugin per brand, rather than multiple (and therefore give you the chance, if you wanted). Let me know your thoughts 🙂 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[bwp91]

So I have been the maintainer for the last few years, but don't have much time for it anymore. I will do the bare-minimum now like updating the dependencies once in a while. And there is no one else!

[K0rb3nD4ll4S]

Can we decommission the old and keep the new? I have a strong tie to “Dibby” being in the name. Let me know your thoughts.