v2.0.33 — Critical desktop-launch fix + green_bg icon + README refresh
⚠️ Critical desktop-launch fix — upgrade from v2.0.30 / v2.0.31
Every desktop installer published since v2.0.30 (Windows, macOS, Linux) had a latent build-pipeline bug that caused the main process to crash silently on startup. The .exe ran (three Electron processes visible in Task Manager) but the window never appeared because BrowserWindow's ready-to-show event never fired.
Root cause
apps/desktop/electron.vite.config.js's rollupOptions.input map listed core/sun and core/types as explicit entries — but omitted core/paths. Five main-process files do a runtime require('./core/paths') (ipc/homekit.ipc.js, ipc/rules.ipc.js, scheduler-standalone.js, service-manager.js, service-manager-sync.js). Without an explicit input the tree-shaker dropped the module entirely, and the first IPC-handler load died with:
[main] unhandledRejection: Error: Cannot find module '../core/paths'
Fix (single line)
'core/paths': resolve(__dirname, 'src/main/core/paths.js'),Verified end-to-end: npm run dev produces a window titled "Dibby Wemo Manager" with a valid MainWindowHandle; locally-built Dibby Wemo Manager Setup 2.0.33.exe installs and launches on Windows 11 with no further intervention.
Icon — switched to the green_bg variant
The previously-used 7G_dark_flat variant only fills 42 % of its canvas (small bright badge centred on transparent / dark padding). The green_bg variant fills 100 % — same artwork, on the lime-green background that matches the "wemo" wordmark already inside the badge. Optical weight now matches every other Windows desktop icon (WinRAR, Git Bash, etc.).
Every sized PNG (16, 24, 32, 48, 64, 72, 96, 128, 144, 192, 256, 512, 1024) and the multi-resolution icon.ico (16 / 24 / 32 / 48 / 64 / 128 / 256 layers) were regenerated from the 1024 × 1024 green_bg master via Pillow LANCZOS and distributed to all 10 icon paths.
CI improvements
build-win.ymlnow auto-triggers on everyv*.*.*tag push.- CI downloads matching Node 20 LTS Windows x64 to
apps/desktop/resources/node.exeso the headless service ships with real Node for HomeKit chacha20-poly1305. - PowerShell step strips
build.win.signtoolOptionsfrompackage.jsonin CI so unsigned builds succeed; locally-built releases sign normally with the SRS IT cert.
README — Quick Start updated
- Filenames bumped from
2.0.19→2.0.33across every download example. - New "24/7 always-on host options" subsection covers Synology Docker +
.spk, generic Linux Docker, Homebridge, and Home Assistant.
Affected packages
All monorepo packages bumped to 2.0.33 in unified versioning. Desktop fix in installers only; homebridge-dibby-wemo@2.0.33 / node-red-contrib-dibby-wemo@2.0.33 get the version bump + new icon.
2.0.32 was burned on npm during pre-release testing (unpublished within the 24 h cooldown), so the same code is re-tagged here as v2.0.33.
Upgrade
- Desktop (Windows / macOS / Linux): important — upgrade from v2.0.30 / v2.0.31 to v2.0.33 to actually see the app window.
- Synology Container Manager / Docker: Stop → Build → Start (pulls
:latest). - Synology
.spk: download the new.spkfor your arch → Package Center → Manual Install. - Homebridge:
npm install -g homebridge-dibby-wemo@2.0.33. - Node-RED:
npm install -g node-red-contrib-dibby-wemo@2.0.33. - HACS: ⋮ → Reload data → Dibby Wemo → ⋮ → Redownload → 2.0.33 → restart HA.