feat: add bulk editing support

.ai/task-manager/.init-metadata.json

@@ -0,0 +1,18 @@
+{
+    "version": "1.26.0",
+    "timestamp": "2026-02-01T01:26:14.673Z",
+    "files": {
+        "config/TASK_MANAGER.md": "ad37290f6f5bced23be611198f288f8c196452183aa139197085c3da73174b49",
+        "config/hooks/POST_ERROR_DETECTION.md": "ed4e1691880ea54ea43c318dc236c326ed81a3ce2785321a25e6db747a6e7e88",
+        "config/hooks/POST_PHASE.md": "d79fccfee4629ffc226db97f6f755c4dd068ee9c30f7d8bf98dfc55b104003c5",
+        "config/hooks/POST_PLAN.md": "4c9850cb6d11d74065b6c4a00137fe00540aeea7b44d9edbfc8211ff5ea34662",
+        "config/hooks/POST_TASK_GENERATION_ALL.md": "aa86468a634da40ae141670b960473bce10589190b0f9119bf07d64cd49a9a7b",
+        "config/hooks/PRE_PHASE.md": "efd9ad1ae9265ef36388cd5dfd9f96a45ae98f7f3d1a2eb5cc8caec01f4efb23",
+        "config/hooks/PRE_PLAN.md": "b8291630f12a1745e00b4a8079e9b7d8d5f7cd3c146df505b2fc8fa175dea1b9",
+        "config/hooks/PRE_TASK_ASSIGNMENT.md": "94735720070a6084560cc89708deb1e123f8c8b24c9ed8ffbb95886423d4b9f7",
+        "config/templates/BLUEPRINT_TEMPLATE.md": "f67488cd05a2fcdbf8a58a863d1315cde4f77a3b42d7e752374feb31620e8063",
+        "config/templates/EXECUTION_SUMMARY_TEMPLATE.md": "9023bd2f6e39169068fd8684254679c82bc76ddbde3d2881eadd76c107f083c2",
+        "config/templates/PLAN_TEMPLATE.md": "c506f6f9394bc4b75e4ccc9fafcef244219bb255a9efd7b95852e8f21123728b",
+        "config/templates/TASK_TEMPLATE.md": "e0fa4d9bde7d9ab9edcf4f32785011c7125424f5199a0994c5900ef0352c4e02"
+    }
+}

.ai/task-manager/README.md

@@ -0,0 +1,7 @@
+# AI Task Manager
+
+This directory contains AI-assisted task management files for this project.
+
+Managed by the [AI Task Manager](https://www.github.com/e0ipso/ai-task-manager) project.
+
+**Documentation**: https://mateuaguilo.com/ai-task-manager

.ai/task-manager/archive/01--bulk-device-settings/plan-01--bulk-device-settings.md

@@ -0,0 +1,295 @@
+---
+id: 1
+summary: "Add bulk management of common expose settings across multiple selected devices"
+created: 2026-01-31
+---
+
+# Plan: Bulk Device Settings Management
+
+## Original Work Order
+
+> Add a new feature to enable bulk management of common settings across multiple devices. For example, a user should be able to check off devices, and then set a setting like the power-on behaviour after a power loss. The settings available should be based off of common exposes definitions, and not specific models so the same value can be set across varying models of devices.
+
+## Plan Clarifications
+
+| Question | Answer |
+|----------|--------|
+| Where should the bulk settings UI be accessible from? | Devices page for selection, then navigate to a dedicated Bulk Settings page for editing |
+| Which types of settings should be available? | Expose features only (power_on_behavior, sensitivity, LED indicators, etc.) |
+| How should common settings be determined? | Exact match by feature name AND type - features must share the same name and same type/value constraints |
+| How should current values be displayed? | Query each device for current value; if all match, show that as default; if values differ, show no default with a note indicating variance |
+
+## Executive Summary
+
+This plan introduces a bulk device settings feature that allows users to select multiple devices from the Devices page and navigate to a dedicated page where they can modify common expose settings across all selected devices simultaneously.
+
+The approach leverages existing patterns in the codebase: TanStack React Table's row selection (already used in ReportingPage and BindingsPage), the established Feature component system for rendering expose controls, and the Promise.allSettled pattern for batch WebSocket operations. By computing the intersection of expose features with matching names and types, users only see settings that can be safely applied to all selected devices.
+
+This feature addresses a common pain point for users with many similar devices (e.g., multiple smart plugs or switches) who currently must configure each device individually.
+
+## Context
+
+### Current State vs Target State
+
+| Current State | Target State | Why? |
+|---------------|--------------|------|
+| Users configure device settings one at a time | Users can select multiple devices and configure common settings in bulk | Reduces repetitive work for users with many similar devices |
+| Devices page has no selection mechanism | Devices page has row selection with checkboxes | Enables multi-device operations |
+| No dedicated bulk settings page exists | New Bulk Settings page shows common exposes for selected devices | Provides focused UI for bulk configuration with adequate screen space |
+| Each device setting change is a separate action | Bulk changes are applied to all selected devices in parallel | Improves efficiency and user experience |
+| No visibility into current values across devices | Settings show common value as default or indicate variance | Prevents accidental overwrites; provides context before changes |
+
+### Background
+
+The codebase already has established patterns for bulk operations:
+
+- **ReportingPage** and **BindingsPage** implement row selection with TanStack React Table and batch actions using `Promise.allSettled()`
+- **Feature components** (`src/components/features/*.tsx`) render individual expose controls and are reusable
+- **WebSocket API** supports setting device values via `{ieee_address}/set` endpoint with transaction tracking
+- **Expose definitions** contain `name`, `type`, `access`, and value constraints that can be compared for compatibility
+
+The strict matching requirement (same name AND type/constraints) ensures that when a user sets a value, it will be valid for all selected devices. For example, if two devices both have `power_on_behavior` but with different enum values, they would not appear as a common setting.
+
+## Architectural Approach
+
+```mermaid
+flowchart LR
+    subgraph DevicesPage["Devices Page"]
+        A[Device Table] --> B[Row Selection]
+        B --> C["Bulk Settings Button"]
+    end
+
+    subgraph Navigation
+        C --> D[Store Selected Devices]
+        D --> E[Navigate to /bulk-settings]
+    end
+
+    subgraph BulkSettingsPage["Bulk Settings Page"]
+        E --> F[Load Selected Devices]
+        F --> G[Compute Common Exposes]
+        G --> H[Render Feature Controls]
+        H --> I[User Changes Setting]
+        I --> J[Apply to All Devices]
+    end
+
+    subgraph WebSocket
+        J --> K["Promise.allSettled()"]
+        K --> L["{ieee}/set for each device"]
+        L --> M[Show Results Toast]
+    end
+```
+
+### Device Selection on Devices Page
+
+**Objective**: Enable users to select multiple devices for bulk operations without disrupting the existing page functionality.
+
+The Devices page table will be enhanced with row selection capabilities using the existing `useTable` hook's `rowSelection` support. A checkbox column will be added as the first column. When devices are selected, a contextual toolbar appears with a "Bulk Settings" button. Clicking this button stores the selected device identifiers and navigates to the dedicated bulk settings page.
+
+Selected devices will be stored in the Zustand store to persist across navigation. Only the IEEE addresses need to be stored since full device data can be retrieved from the existing `devices` state.
+
+### Common Expose Computation
+
+**Objective**: Determine which expose features are common across all selected devices with compatible types and constraints.
+
+The system will iterate through all selected devices' expose definitions and compute the intersection. For a feature to be considered "common":
+
+1. All selected devices must have a feature with the exact same `name`
+2. All features must have the same `type` (binary, enum, numeric, etc.)
+3. For enum types: all devices must have the exact same set of allowed values
+4. For numeric types: ranges must be compatible (intersection of min/max)
+5. The feature must have SET access (`access & 0b010`)
+
+Features will be grouped by category (if available) or presented in a flat list. Each common feature shows how many devices it applies to (should be 100% for strict matching).
+
+### Bulk Settings Page
+
+**Objective**: Provide a dedicated interface for viewing and modifying common settings across selected devices.
+
+The page will display:
+- A summary header showing the count and list of selected devices
+- A list of common expose features rendered using existing Feature components
+- An apply mechanism for each setting (or batch apply for multiple changes)
+
+The existing Feature components (`Binary`, `Enum`, `Numeric`, etc.) will be reused with a modified `onChange` handler that applies to all selected devices. The page will show which devices will be affected and provide feedback on the operation results.
+
+### Current Value Detection
+
+**Objective**: Show intelligent defaults based on current device states, with clear indication when values differ.
+
+When the Bulk Settings page loads, the system will query the current state of each selected device for each common expose feature. The display logic:
+
+1. **Uniform values**: If all selected devices have the same current value for a setting, pre-populate the control with that value as the default
+2. **Mixed values**: If values differ across devices, show the control with no value selected and display a subtle note (e.g., "Current setting varies across selected devices")
+3. **Unknown values**: If some devices don't have a current state available, treat as mixed/unknown
+
+```mermaid
+flowchart TD
+    A[Load Bulk Settings Page] --> B[For each common expose]
+    B --> C[Query deviceStates for each selected device]
+    C --> D{All values identical?}
+    D -->|Yes| E[Set control default to common value]
+    D -->|No| F[Leave control empty]
+    F --> G[Show variance indicator note]
+```
+
+This approach ensures users understand the current state before making changes and avoids accidentally overwriting intentionally different configurations.
+
+### Batch WebSocket Operations
+
+**Objective**: Apply setting changes to all selected devices efficiently with proper error handling.
+
+When a user changes a setting value, the system will:
+1. Construct the payload for each selected device
+2. Send all requests in parallel using `Promise.allSettled()`
+3. Collect results (fulfilled/rejected) for each device
+4. Display a summary toast showing success count and any failures
+5. Update local state to reflect changes
+
+This follows the established pattern in `ReportingPage.tsx` where batch operations are already implemented.
+
+```mermaid
+sequenceDiagram
+    participant User
+    participant BulkSettingsPage
+    participant WebSocketManager
+    participant Z2M as Zigbee2MQTT
+
+    User->>BulkSettingsPage: Change power_on_behavior to "on"
+    BulkSettingsPage->>BulkSettingsPage: Build payloads for all devices
+
+    par For each device
+        BulkSettingsPage->>WebSocketManager: sendMessage(device1/set, {power_on_behavior: "on"})
+        BulkSettingsPage->>WebSocketManager: sendMessage(device2/set, {power_on_behavior: "on"})
+        BulkSettingsPage->>WebSocketManager: sendMessage(device3/set, {power_on_behavior: "on"})
+    end
+
+    WebSocketManager->>Z2M: WebSocket messages
+    Z2M-->>WebSocketManager: Responses
+    WebSocketManager-->>BulkSettingsPage: Promise.allSettled results
+    BulkSettingsPage->>User: Toast: "3/3 devices updated successfully"
+```
+
+### State Management
+
+**Objective**: Manage selected devices across page navigation and coordinate with existing store patterns.
+
+A new slice will be added to the Zustand store to track bulk operation state:
+- `bulkSelectedDevices`: Array of IEEE addresses (per source index for multi-instance support)
+- Actions to set/clear selection
+
+The selection state will be cleared after successful bulk operations or when the user navigates away from the bulk settings flow.
+
+## Risk Considerations and Mitigation Strategies
+
+<details>
+<summary>Technical Risks</summary>
+
+- **Feature compatibility edge cases**: Some features may have the same name but subtly different behaviors across device models
+    - **Mitigation**: Strict type and constraint matching; show device count affected by each setting
+
+- **Large batch operations**: Applying changes to many devices simultaneously could overwhelm the WebSocket connection
+    - **Mitigation**: Use existing transaction-based API with proper timeout handling; consider chunking for very large selections (50+ devices)
+
+</details>
+
+<details>
+<summary>Implementation Risks</summary>
+
+- **Multi-instance complexity**: The application supports multiple Zigbee2MQTT instances; bulk operations must respect source boundaries
+    - **Mitigation**: Store selections per `sourceIdx`; only allow bulk operations within a single source
+
+- **State synchronization**: Device state may change while user is on bulk settings page
+    - **Mitigation**: Subscribe to device state updates; show stale data warnings if device definitions change
+
+</details>
+
+## Success Criteria
+
+### Primary Success Criteria
+
+1. Users can select multiple devices on the Devices page using checkboxes
+2. Users can navigate to a Bulk Settings page showing only common expose features
+3. Settings with uniform values across devices show that value as the default; settings with mixed values show no default with a variance indicator
+4. Changing a setting applies the value to all selected devices via WebSocket
+5. Users receive clear feedback on which devices were updated successfully
+
+## Resource Requirements
+
+### Development Skills
+
+- front-end javascript
+- front-end css and html
+
+### Technical Infrastructure
+
+- javascript
+- typescript
+- vite
+- tailwind
+- react
+
+## Integration Strategy
+
+- this project is a front end built on the websocket API of zigbee2mqtt.
+
+## Task Dependency Graph
+
+```mermaid
+graph TD
+    1[Task 1: Store Slice] --> 2[Task 2: Row Selection]
+    1 --> 4[Task 4: Bulk Settings Page]
+    3[Task 3: Common Expose Logic] --> 4
+    4 --> 5[Task 5: Batch Apply]
+    5 --> 6[Task 6: Integration Tests]
+```
+
+## Execution Blueprint
+
+**Validation Gates:**
+- Reference: `/config/hooks/POST_PHASE.md`
+
+### ✅ Phase 1: Foundation
+**Parallel Tasks:**
+- ✔️ Task 1: Add bulk selection store slice
+- ✔️ Task 3: Implement common expose computation logic
+
+### ✅ Phase 2: UI Integration
+**Parallel Tasks:**
+- ✔️ Task 2: Add device row selection to Devices page (depends on: 1)
+- ✔️ Task 4: Create Bulk Settings page (depends on: 1, 3)
+
+### ✅ Phase 3: Feature Completion
+**Parallel Tasks:**
+- ✔️ Task 5: Implement batch apply with feedback (depends on: 4)
+
+### ✅ Phase 4: Quality Assurance
+**Parallel Tasks:**
+- ✔️ Task 6: Add integration tests for bulk settings flow (depends on: 5)
+
+### Execution Summary
+- Total Phases: 4
+- Total Tasks: 6
+- Maximum Parallelism: 2 tasks (in Phases 1 and 2)
+- Critical Path Length: 4 phases (1 → 4 → 5 → 6)
+
+## Execution Summary
+
+**Status**: ✅ Completed Successfully
+**Completed Date**: 2026-01-31
+
+### Results
+Successfully implemented bulk device settings management feature:
+- **Store Slice**: Added `bulkSelectedDevices` state with multi-instance (sourceIdx) support
+- **Device Selection**: Added row selection checkboxes to Devices page with contextual toolbar
+- **Common Exposes**: Implemented `computeCommonExposes` utility with strict type/value matching
+- **Bulk Settings Page**: Created dedicated page at `/bulk-settings/:sourceIdx` with value status indicators
+- **Batch Apply**: Implemented parallel WebSocket operations with toast feedback
+- **Testing**: 18 tests covering core business logic
+
+### Noteworthy Events
+- Tests for `computeCommonExposes` were created during Task 3 (core logic) rather than Task 6 (testing phase), which is appropriate for the implementation flow
+- Used expandable daisyUI collapse components for feature controls to keep the UI clean while allowing editing
+
+### Recommendations
+- Consider adding chunking for very large selections (50+ devices) to prevent WebSocket overload
+- May want to add a "Select All" shortcut for common device patterns in future iterations

.ai/task-manager/archive/01--bulk-device-settings/tasks/01--add-bulk-selection-store-slice.md

@@ -0,0 +1,72 @@
+---
+id: 1
+group: "state-management"
+dependencies: []
+status: "completed"
+created: "2026-01-31"
+skills:
+  - typescript
+  - zustand
+---
+# Add Bulk Selection Store Slice
+
+## Objective
+Add a new slice to the Zustand store to track selected devices for bulk operations, following existing store patterns and supporting multi-instance (sourceIdx).
+
+## Skills Required
+- TypeScript for type definitions
+- Zustand for state management patterns
+
+## Acceptance Criteria
+- [ ] New `bulkSelectedDevices` state added to store (Map keyed by sourceIdx to array of IEEE addresses)
+- [ ] `setBulkSelectedDevices(sourceIdx, ieeeAddresses[])` action implemented
+- [ ] `clearBulkSelectedDevices(sourceIdx?)` action implemented
+- [ ] Types exported for use in components
+- [ ] Follows existing store slice patterns in the codebase
+
+Use your internal Todo tool to track these and keep on track.
+
+## Technical Requirements
+- Store file: `src/store.ts`
+- State shape: `bulkSelectedDevices: Map<number, string[]>` (sourceIdx → IEEE addresses)
+- Must support multi-instance pattern (sourceIdx) used throughout the codebase
+
+## Input Dependencies
+None - this is the foundation task.
+
+## Output Artifacts
+- Extended store with bulk selection state and actions
+- Type definitions for bulk selection state
+
+## Implementation Notes
+
+<details>
+<summary>Detailed Implementation Guide</summary>
+
+1. **Open `src/store.ts`** and locate the existing state interface and store creation.
+
+2. **Add new state property** to the store state interface:
+   ```typescript
+   bulkSelectedDevices: Map<number, string[]>;
+   ```
+
+3. **Add actions** to the store:
+   ```typescript
+   setBulkSelectedDevices: (sourceIdx: number, ieeeAddresses: string[]) => void;
+   clearBulkSelectedDevices: (sourceIdx?: number) => void;
+   ```
+
+4. **Initialize the state** in the store creation:
+   ```typescript
+   bulkSelectedDevices: new Map(),
+   ```
+
+5. **Implement the actions**:
+   - `setBulkSelectedDevices`: Create a new Map, copy existing entries, set the new entry for the given sourceIdx
+   - `clearBulkSelectedDevices`: If sourceIdx provided, delete that entry; otherwise create new empty Map
+
+6. **Pattern reference**: Look at how other Map-based state is handled in the store (e.g., `deviceStates`).
+
+7. **Export selectors** if the codebase uses selector patterns for store access.
+
+</details>