Merge develop into main for v0.4.1 release

Author: Andy

README.md

@@ -81,7 +81,7 @@ Open Wemo consists of two parts that work together:
 | **Auto-Refresh** | Device states update automatically (configurable interval) |
 | **Timer Schedules** | Schedule devices to turn on or off at specific times, daily or per day of week |
 | **Standby Threshold** | Configure the power level at which Insight devices are considered in standby (via device config panel) |
-| **LED Mode** | Prevent Insight devices from auto-shutting off low-power devices like LED lights (via device config panel) |
+| **LED Mode** | Prevent Insight devices from auto-shutting off low-power devices like LED lights while keeping manual off behavior intact |
 | **QR Code Setup** | Scan a code to instantly set up the app on any phone |
 | **Cross-Platform** | Bridge runs on Windows, macOS, and Linux |
 | **No Cloud Required** | Everything stays on your local network — private by design |
@@ -254,7 +254,7 @@ For Insight devices, you can adjust power monitoring settings:
 
 This is useful if your device draws a small amount of power when "off" (like a TV in standby mode) and you want to fine-tune when it shows as "Standby" vs. "Off".
 
-- **LED Mode** — toggle to keep low-power devices (like LED lights) from being automatically shut off by the Insight's standby detection. The bridge sends a periodic heartbeat to prevent the firmware timeout. This respects manual off commands — if you turn the device off, the keep-alive pauses.
+- **LED Mode** — toggle to keep low-power devices (like LED lights) from being automatically shut off by the Insight firmware. While enabled, Open Wemo keeps the device in normal "On" mode, hides the standby-threshold control, and only applies protection after you turn the device on yourself. If you turn the device off, it stays off.
 
 ### Header Actions
 
@@ -356,7 +356,7 @@ chmod +x ~/.cache/node-systray/*/tray_linux_release
 
 - **Give it time**: Insight devices average power over time; readings stabilize after a few minutes
 - **Standby mode**: Very low power (< 1 watt) shows as "Standby" state
-- **Adjust standby threshold**: Tap the gear icon on the device card to customize the wattage at which the device is considered "Standby"
+- **Adjust standby threshold**: Tap the gear icon on the device card to customize the wattage at which the device is considered "Standby" when LED Mode is off
 - **Device firmware**: Older WeMo firmware may report slightly different formats
 
 ---
@@ -571,7 +571,7 @@ A: Nope! Just install the bridge and it will automatically discover your existin
 A: Yes! Tap the timer icon on any device card to create schedules. Set a time, choose on or off, and select which days of the week. Timers run on the bridge, so they're reliable and consistent as long as the bridge is running.
 
 **Q: What is the standby threshold?**  
-A: For Insight devices, the standby threshold is the power level (in watts) below which the device shows as "Standby" instead of "Off". This is useful for devices that draw a small amount of power when turned off (like TVs or chargers). You can adjust it by tapping the gear icon on an Insight device card. The range is 0-50 watts.
+A: For Insight devices, the standby threshold is the power level (in watts) below which the device shows as "Standby" instead of "Off". This is useful for devices that draw a small amount of power when turned off (like TVs or chargers). You can adjust it by tapping the gear icon on an Insight device card when LED Mode is off. The range is 0-50 watts.
 
 **Q: My Insight device keeps turning off my LED light. What can I do?**  
-A: Enable "LED Mode" in the device's configuration panel (tap the gear icon). This sends a periodic heartbeat to prevent the Insight's firmware from auto-shutting off low-power devices that draw too little power for the sensor to detect. LED Mode respects manual off commands — if you turn the device off yourself, it stays off.
+A: Enable "LED Mode" in the device's configuration panel (tap the gear icon). Open Wemo lowers the Insight auto-off threshold, keeps the device reporting as "On" instead of "Standby," and sends a periodic keep-alive only after you turn the device on yourself. If you turn the device off yourself, it stays off.

docs/API.md

@@ -709,7 +709,7 @@ Gets the keep-alive (LED Mode) status for a device.
 PUT /api/devices/:id/keepalive
 ```
 
-Enables or disables keep-alive (LED Mode) for a device. When enabled, the bridge sends a periodic heartbeat to prevent the Insight firmware from auto-shutting off low-power devices.
+Enables or disables keep-alive (LED Mode) for a device. When enabled, Open Wemo also adjusts the Insight auto-off and display thresholds so low-power loads stay in normal "On" mode instead of falling into standby behavior. The keep-alive only protects devices after the user has turned them on; enabling LED Mode does not turn an intentionally off device back on.
 
 **Request Body:**
 ```json

docs/RELEASING.md

@@ -0,0 +1,209 @@
+# Release Process
+
+This checklist is the release runbook for Open Wemo.
+
+The current repo workflow is:
+
+- day-to-day work lands on `develop`
+- release candidates are merged to `main`
+- CI runs on `main` / `master`
+- a pushed tag matching `v*.*.*` triggers the GitHub release workflow
+- GitHub release notes are generated from commit subjects between the previous tag and the new tag
+
+## Release Checklist
+
+### 1. Stabilize the release branch
+
+- [ ] Start from `develop`
+- [ ] Pull the latest branch state
+- [ ] Confirm the working tree is clean
+- [ ] Review the commits that will go into the release
+- [ ] Clean up noisy commit history before release if needed (squash fixups, avoid vague subjects, make commit titles user-facing)
+
+```bash
+git checkout develop
+git pull origin develop
+git status
+git log --oneline origin/main..HEAD
+```
+
+Notes:
+
+- The release workflow uses commit subjects to build the GitHub release notes, so commit titles matter.
+- Good subjects: `Fix LED Mode reviving devices that are intentionally off`
+- Bad subjects: `wip`, `fix stuff`, `debug`, `try again`
+
+### 2. Update release-facing docs
+
+- [ ] Update `README.md` for any user-visible changes
+- [ ] Update API docs if endpoints or payloads changed (`docs/API.md`)
+- [ ] Update protocol or architecture docs if behavior changed significantly
+- [ ] Make sure contributor workflow is still accurate if the process changed (`CONTRIBUTING.md`)
+
+For the current release, specifically verify the docs cover:
+
+- LED Mode behavior
+- standby threshold behavior
+- any changed expectations for Insight devices
+
+### 3. Bump versions consistently
+
+- [ ] Choose the correct semver bump
+- [ ] Update version in root package
+- [ ] Update version in bridge package
+- [ ] Update version in web package
+- [ ] Re-check for any hard-coded version references that should match the release
+
+Files to update:
+
+- `package.json`
+- `packages/bridge/package.json`
+- `packages/web/package.json`
+
+Versioning guide:
+
+- patch: bug fixes, no breaking changes
+- minor: new features, backward-compatible
+- major: breaking changes
+
+### 4. Run the full validation pass
+
+- [ ] Install dependencies if needed
+- [ ] Run typecheck
+- [ ] Run lint
+- [ ] Run tests
+- [ ] Run at least a Linux release build locally
+- [ ] Prefer running all platform builds before tagging if practical
+
+```bash
+bun install
+bun run typecheck
+bun run lint
+bun test
+bun run build:linux
+# optional but recommended before release
+bun run build:all
+```
+
+### 5. Do release-candidate smoke testing
+
+- [ ] Launch the local build you intend to ship
+- [ ] Verify the app starts cleanly
+- [ ] Verify the most important changed behaviors manually
+- [ ] Verify no obvious regressions in core flows
+
+Suggested smoke-test areas:
+
+- device discovery
+- device on/off control
+- Insight status reporting
+- LED Mode toggle behavior
+- standby threshold behavior
+- timer flow if related code changed
+
+### 6. Prepare the final release commit set
+
+- [ ] Commit doc updates, version bumps, and release-prep changes
+- [ ] Make sure the final commit set is understandable when read as release notes
+- [ ] Push the final `develop` branch state
+
+```bash
+git add .
+git commit -m "Prepare vX.Y.Z release"
+git push origin develop
+```
+
+### 7. Merge to the release branch
+
+- [ ] Merge `develop` into `main`
+- [ ] Push `main`
+- [ ] Wait for CI on `main` to pass before tagging
+
+```bash
+git checkout main
+git pull origin main
+git merge develop --no-ff -m "Merge develop for vX.Y.Z"
+git push origin main
+```
+
+Current CI behavior from `.github/workflows/ci.yml`:
+
+- lint/typecheck job
+- test job
+- Linux build verification job
+
+### 8. Create and push the release tag
+
+- [ ] Create an annotated semver tag
+- [ ] Push the tag
+- [ ] Confirm the release workflow starts
+
+```bash
+git tag -a vX.Y.Z -m "Release vX.Y.Z"
+git push origin vX.Y.Z
+```
+
+Current release trigger from `.github/workflows/release.yml`:
+
+- push tags matching `v*.*.*`
+
+### 9. Verify the GitHub release output
+
+- [ ] Confirm the GitHub release was created
+- [ ] Confirm all expected binaries are attached
+- [ ] Confirm the release body reads well
+- [ ] Edit the release text manually if the generated notes need cleanup or grouping
+
+Expected artifacts:
+
+- Windows: `open-wemo-*-win.exe`
+- macOS ARM: `open-wemo-*-mac`
+- macOS Intel: `open-wemo-*-mac-intel`
+- Linux: `open-wemo-*-linux`
+
+Release note source:
+
+- generated from `git log PREV_TAG..HEAD --pretty=format:"- %s" --no-merges`
+
+### 10. Post-release follow-through
+
+- [ ] Smoke-test one downloaded release artifact from GitHub
+- [ ] Confirm the version shown in shipped binaries matches the tag
+- [ ] Open follow-up issues for anything intentionally deferred
+- [ ] Sync your local branches back to the normal development flow
+
+```bash
+git checkout develop
+git pull origin develop
+```
+
+## Quick Command Checklist
+
+```bash
+git checkout develop
+git pull origin develop
+git status
+git log --oneline origin/main..HEAD
+
+bun install
+bun run typecheck
+bun run lint
+bun test
+bun run build:linux
+
+git checkout main
+git pull origin main
+git merge develop --no-ff -m "Merge develop for vX.Y.Z"
+git push origin main
+
+git tag -a vX.Y.Z -m "Release vX.Y.Z"
+git push origin vX.Y.Z
+```
+
+## Repo-Specific Reminders
+
+- Keep commit subjects clean because they become release notes.
+- Bump all three package versions together.
+- Do not tag before CI passes on `main`.
+- If the release includes user-visible behavior changes, update `README.md` in the same release.
+- If the release includes protocol or API behavior changes, update the corresponding files in `docs/` before tagging.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-wemo",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "private": true,
   "description": "Open-source solution for controlling Belkin WeMo smart home devices",
   "workspaces": ["packages/*"],

packages/bridge/assets/generate-icons.ts

@@ -54,7 +54,7 @@ const iconPng = renderSvgToPng(svgContent, 32);
 const iconIco = createIco(iconPng, 32, 32);
 
 // Create error icon (red background instead of dark blue)
-const errorSvgContent = svgContent.replace('#1a1a2e', '#7f1d1d').replace('#4ade80', '#fca5a5');
+const errorSvgContent = svgContent.replace("#1a1a2e", "#7f1d1d").replace("#4ade80", "#fca5a5");
 const iconErrorPng = renderSvgToPng(errorSvgContent, 32);
 const iconErrorIco = createIco(iconErrorPng, 32, 32);
 

packages/bridge/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-wemo/bridge",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "private": true,
   "description": "Desktop tray app + REST API server for Open Wemo",
   "type": "module",

packages/bridge/src/install.ts

@@ -86,7 +86,7 @@ export function isInstalledLocation(): boolean {
   console.log(`[Install] Expected installed path: ${installedExePath}`);
 
   // Check if current path matches the installed exe path exactly, or is within install directory
-  const isInstalled = currentPath === installedExePath || currentPath.startsWith(installDir + "/");
+  const isInstalled = currentPath === installedExePath || currentPath.startsWith(`${installDir}/`);
 
   console.log(`[Install] Is installed location: ${isInstalled}`);
 

packages/bridge/src/server/routes/devices.ts

@@ -481,6 +481,34 @@ deviceRoutes.put("/:id/keepalive", async (c) => {
 
   setKeepAliveEnabled(device.id, body.enabled);
 
+  if (device.deviceType === "Insight") {
+    try {
+      const client = await getInsightClient(device);
+      const autoThresholdWatts = body.enabled ? 0 : 8;
+      const displayThresholdMilliwatts = body.enabled ? 1 : 8000;
+      await Promise.all([
+        client.setAutoPowerThreshold(autoThresholdWatts),
+        client.setPowerThreshold(displayThresholdMilliwatts),
+      ]);
+
+      if (body.enabled) {
+        const state = await client.getBinaryState();
+        if (state === 0 || state === 8) {
+          markManualOff(device.id);
+        }
+      }
+
+      console.log(
+        `[KeepAlive] Set auto threshold to ${autoThresholdWatts}W, display threshold to ${displayThresholdMilliwatts}mW for "${device.name}"`
+      );
+    } catch (error) {
+      console.error(
+        `[KeepAlive] Failed to set power thresholds for "${device.name}":`,
+        error instanceof Error ? error.message : error
+      );
+    }
+  }
+
   return c.json({
     id: device.id,
     enabled: body.enabled,

packages/bridge/src/server/static.ts

@@ -113,41 +113,6 @@ function getWebDir(): string {
   return devPath;
 }
 
-/**
- * Recursively reads all files from a directory (development mode).
- */
-function readFilesRecursively(dir: string, basePath = ""): void {
-  if (!existsSync(dir)) {
-    console.warn(`[Static] Directory not found: ${dir}`);
-    return;
-  }
-
-  const entries = readdirSync(dir);
-
-  for (const entry of entries) {
-    const fullPath = join(dir, entry);
-    const relativePath = basePath ? `${basePath}/${entry}` : entry;
-    const stat = statSync(fullPath);
-
-    if (stat.isDirectory()) {
-      readFilesRecursively(fullPath, relativePath);
-    } else if (stat.isFile()) {
-      try {
-        // Use Bun.file for reading - works with both filesystem and embedded paths
-        const file = Bun.file(fullPath);
-        const content = new Uint8Array(file.stream() as unknown as ArrayBuffer);
-        const mimeType = getMimeType(entry);
-        fileCache.set(`/${relativePath}`, {
-          content,
-          mimeType,
-        });
-      } catch (error) {
-        console.warn(`[Static] Failed to read file: ${relativePath}`, error);
-      }
-    }
-  }
-}
-
 /**
  * Loads embedded files (production/compiled mode).
  * Uses Bun.file() which works with both filesystem and $bunfs/ paths.

packages/bridge/src/tray/index.ts

@@ -5,7 +5,7 @@
  * Uses systray2 for cross-platform support.
  */
 
-import { chmodSync, existsSync, readdirSync, readFileSync } from "node:fs";
+import { chmodSync, existsSync, readFileSync, readdirSync } from "node:fs";
 import { homedir, platform } from "node:os";
 import { join } from "node:path";