v2.0.18 — Embedded HomeKit Bridge + Day-of-Week Fix + Service UX
What's New in v2.0.18
All monorepo packages bumped to 2.0.18 in unified versioning.
🏠 Embedded HomeKit Bridge (headless)
Dibby now ships its own HomeKit Accessory Protocol bridge using hap-nodejs, running inside the DibbyWemoScheduler background service. Pair Dibby once with Apple Home and every Wemo on your network appears as a HomeKit Switch — including older Wemos with no native HomeKit firmware, and newer ones whose setup-code sticker has been lost.
Because the bridge runs in the always-on service, it stays alive after you close the desktop app and across reboots. No need to keep the desktop GUI open.
To enable: Settings → 🏠 HomeKit Bridge → Install DibbyWemoScheduler service → Yes to UAC. Scan the QR with iOS Home, done.
Falls back gracefully to in-app bridge mode when the service isn't installed (good for testing without committing to install).
🐛 Day-of-week off-by-one fix for Belkin-app-created rules
Rules created in the official Belkin WeMo phone app showed up in Dibby with every day shifted +1 (Friday → Saturday). Root cause: Belkin firmware uses Sun=1..Sat=7, Dibby uses Mon=1..Sun=7. Translated at every Wemo-device I/O boundary across the desktop, Homebridge plugin, Node-RED, and Home Assistant integration. Also handles bundle DayIDs (0=Daily, 8=Weekdays, 9=Weekends) which were previously silently dropped.
⚙ Service Install / Start / Stop / Uninstall
The HomeKit Bridge panel in Settings now has the full service-management surface inline:
| Service state | Buttons shown |
|---|---|
| Not installed | ⚙ Install DibbyWemoScheduler service |
| Installed, stopped | ▶ Start service · 🗑 Uninstall service |
| Installed, running | ■ Stop service · 🗑 Uninstall service |
The Uninstall button shows a confirm dialog explaining that bridge pairing data, deployed node-windows, and the bundled node.exe will be removed (devices and DWM rules are preserved).
Standalone cleanup tool at tools/uninstall-service.bat (self-elevating PowerShell wrapper) for stuck-state recovery.
📦 Service install works from BOTH portable AND installer
Each service install copies all needed files to C:\ProgramData\DibbyWemoManager\ so service config references stable paths regardless of where Dibby itself lives:
scheduler-standalone.jsnode-windows/package + full transitive dep tree (xml, yargs, yargs-parser, cliui, …)node.exe(~91 MB) — bundled because Electron's BoringSSL doesn't exposechacha20-poly1305in a hap-nodejs–compatible way
NSIS installer's customInit hook stops + cleans previous install before file copy → upgrade installs work without manual uninstall.
🏠 HomeKit setup-code QR for native-HK Wemos
Per-device Info tab now shows a scannable X-HM:// QR alongside the existing setup code text. If you lose the physical sticker, Dibby remembers and shows it.
⏱ Countdown rule — state-based, not transition-based
The DWM Countdown rule fires the timer whenever the device is in the trigger state, regardless of how it got there. Previously the timer only started on a transition INTO the trigger state — so if the device was already ON when the scheduler started, the auto-OFF countdown would never run until someone manually toggled it off and back on.
⚠ UX honesty: Wemo firmware schedulers no longer fire rules autonomously
After Belkin shut down their cloud (2024), the on-device autonomous scheduler in Wemo firmware no longer wakes up to fire scheduled rules. We did the full reverse-engineering loop and confirmed this is universal across Socket and LightSwitch firmware revisions; the firmware was designed around a cloud-pushed nudge over TLS to api.xbcs.net which no longer exists, and the device pins certificates so we can't fake the nudge. The honest answer is rules must be fired by an external scheduler — Dibby's service does this for you.
Clear in-app warnings now appear in the rule editor and rules list when Wemo firmware rules exist but no scheduler is running.
Install
| Platform | Command / Action |
|---|---|
| Windows desktop | Download Dibby Wemo Manager Setup 2.0.18.exe below |
| Windows portable | Download Dibby Wemo Manager 2.0.18.exe (no install — extracts to TEMP, but still installs the service to ProgramData) |
| Homebridge | npm install -g homebridge-dibby-wemo |
| HOOBS | Plugins tab → search homebridge-dibby-wemo → Install |
| Home Assistant | HACS → Custom repositories → add this repo as Integration |
| Node-RED | npm install node-red-contrib-dibby-wemo (from ~/.node-red) |
Recommended setup for users without an always-on PC
- Raspberry Pi 4 (~$35) running Dibby's Linux ARM64 build — boots up automatically, low power
- Existing Homebridge / HOOBS — install
homebridge-dibby-wemo - Existing Home Assistant — install via HACS
- Old Android phone on a charger — install Dibby Android app, foreground service runs in background
One always-on host is enough to fire rules + run the HomeKit bridge for an entire household.