benchlab-pytools 3.2.1__tar.gz → 3.3.1__tar.gz

{benchlab_pytools-3.2.1 → benchlab_pytools-3.3.1}/CHANGELOG.md

@@ -4,6 +4,43 @@ All notable changes to BENCHLAB PyTools are documented here. Format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows
 [SemVer](https://semver.org/).
 
+## [3.3.1] - 2026-10-17
+
+### Fixed
+- Packaging: `benchlab-pytools[flash]` was missing `pydantic` and
+  `requests` (`flash_manager` imports `config_manager` -> `config.schema`
+  -> `pydantic`; `--source service_http` needs `requests`), so a clean
+  `[flash]`-only install crashed with `ModuleNotFoundError` on first use.
+  The launcher also reported `ModuleNotFoundError` as "Flash tool module
+  not available in this build" regardless of cause; it now prints the
+  real missing module and the install command. (#90)
+- `check_bootloader_supported()` only gated BENCHLAB1 firmware against
+  the CMD_BOOTLOADER version floor; a BENCHLAB2 unit on firmware below
+  `0x05` (which predates CMD_BOOTLOADER on BL2, per the firmware repo's
+  protocol contract freeze history) passed the check and then hit a 5s
+  timeout in `enter_dfu_mode()` instead of being told up front to use a
+  physical BOOT0/jumper bootloader entry. (#94)
+
+## [3.3.0] - 2026-10-01
+
+### Added
+- Firmware flash tool (`-flash`, `benchlab.flash`): flashes new firmware
+  onto BENCHLAB1/2 devices (STM32F303RB) over USB DFU, commanding the
+  running firmware to jump into ST's factory ROM bootloader and talking to
+  it via a pure-Python `pyusb` client (no external flashing binary
+  required). Supports `.bin` (primary), `.hex`, and `.elf` images, and
+  `direct`/`named_pipe`/`service_http` sources for the initial CDC-side
+  bootloader jump. Falls back to a guided manual BOOT0 entry for firmware
+  too old to support the CDC bootloader command. (#84)
+- `HttpConfigClient` (`service_http` source) now implements fan/RGB/
+  calibration read-write (`read_fan_config`/`write_fan_config`,
+  `read_rgb_config`/`write_rgb_config`, `read_calibration`/
+  `write_calibration`), via a new translation layer
+  (`benchlab.config.http_dto`) between the BL_Service HTTP API's DTO JSON
+  shapes and this repo's existing config-dict convention. Handles BL2's
+  wider calibration wire struct correctly. `config_tool.py` (`-config`)
+  gained `--source service_http` CLI support to match. (#86)
+
 ## [3.2.1] - 2026-10-01
 
 ### Fixed
@@ -173,6 +210,8 @@ export, MQTT publisher, VU dials, WigiDash, and config import/export tools,
 sharing a common data-source layer (direct serial, FastAPI, MQTT, named
 pipe, service HTTP, service WebSocket).
 
+[3.3.1]: https://github.com/BenchLab-io/benchlab-pytools/compare/v3.3.0...v3.3.1
+[3.3.0]: https://github.com/BenchLab-io/benchlab-pytools/compare/v3.2.1...v3.3.0
 [3.2.1]: https://github.com/BenchLab-io/benchlab-pytools/compare/v3.2.0...v3.2.1
 [3.2.0]: https://github.com/BenchLab-io/benchlab-pytools/compare/v3.1.0...v3.2.0
 [3.1.0]: https://github.com/BenchLab-io/benchlab-pytools/compare/v3.0.4...v3.1.0

{benchlab_pytools-3.2.1 → benchlab_pytools-3.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: benchlab-pytools
-Version: 3.2.1
+Version: 3.3.1
 Summary: Python control suite for BENCHLAB telemetry devices
 Project-URL: Homepage, https://benchlab.io/
 Project-URL: Repository, https://github.com/BenchLab-io/benchlab-pytools
@@ -24,16 +24,18 @@ Classifier: Topic :: System :: Monitoring
 Requires-Python: >=3.10
 Requires-Dist: benchlab-pycore>=0.8.0
 Requires-Dist: packaging<26.0,>=23.0
+Requires-Dist: pydantic>=2.0.0
 Requires-Dist: python-dotenv<2.0,>=1.2.2
 Requires-Dist: pywin32>=306; platform_system == 'Windows'
+Requires-Dist: requests>=2.33.1
 Requires-Dist: textual<9.0,>=0.60
 Requires-Dist: windows-curses>=2.4.1; platform_system == 'Windows'
 Provides-Extra: all
 Requires-Dist: amqtt<0.13.0,>=0.12.0; extra == 'all'
-Requires-Dist: benchlab-pycore>=0.8.0; extra == 'all'
 Requires-Dist: blessed>=1.20.0; extra == 'all'
 Requires-Dist: dearpygui>=2.1.1; extra == 'all'
 Requires-Dist: fastapi==0.111.1; extra == 'all'
+Requires-Dist: intelhex>=2.3.0; extra == 'all'
 Requires-Dist: libusb-package>=1.0.26.1; (sys_platform == 'win32') and extra == 'all'
 Requires-Dist: matplotlib>=3.10.7; extra == 'all'
 Requires-Dist: numpy; extra == 'all'
@@ -41,49 +43,53 @@ Requires-Dist: numpy>=2.2.0; extra == 'all'
 Requires-Dist: paho-mqtt<3.0,>=2.0; extra == 'all'
 Requires-Dist: pillow>=10.0.0; extra == 'all'
 Requires-Dist: pillow>=11.3.0; extra == 'all'
-Requires-Dist: pydantic>=2.0.0; extra == 'all'
+Requires-Dist: pyelftools>=0.31; extra == 'all'
 Requires-Dist: pyserial>=3.5; extra == 'all'
 Requires-Dist: python-dotenv==1.2.2; extra == 'all'
 Requires-Dist: pyusb>=1.3.1; extra == 'all'
 Requires-Dist: pyyaml<7.0,>=6.0; extra == 'all'
 Requires-Dist: pyyaml>=6.0; extra == 'all'
-Requires-Dist: requests>=2.31.0; extra == 'all'
-Requires-Dist: requests>=2.33.1; extra == 'all'
 Requires-Dist: ruamel-yaml; extra == 'all'
 Requires-Dist: tornado; extra == 'all'
+Requires-Dist: tqdm>=4.66; extra == 'all'
 Requires-Dist: uvicorn[standard]==0.24.0; extra == 'all'
 Requires-Dist: websockets<16.0,>=13.0; extra == 'all'
 Provides-Extra: csv-log
-Requires-Dist: benchlab-pycore>=0.8.0; extra == 'csv-log'
 Requires-Dist: pyserial>=3.5; extra == 'csv-log'
+Provides-Extra: flash
+Requires-Dist: intelhex>=2.3.0; extra == 'flash'
+Requires-Dist: libusb-package>=1.0.26.1; (sys_platform == 'win32') and extra == 'flash'
+Requires-Dist: pyelftools>=0.31; extra == 'flash'
+Requires-Dist: pyserial>=3.5; extra == 'flash'
+Requires-Dist: pyusb>=1.3.1; extra == 'flash'
+Requires-Dist: tqdm>=4.66; extra == 'flash'
 Provides-Extra: graph
 Requires-Dist: dearpygui>=2.1.1; extra == 'graph'
 Requires-Dist: pyserial>=3.5; extra == 'graph'
 Provides-Extra: hwinfo
 Requires-Dist: pyserial>=3.5; extra == 'hwinfo'
+Provides-Extra: link
+Requires-Dist: paho-mqtt<3.0,>=2.0; extra == 'link'
+Requires-Dist: pyserial>=3.5; extra == 'link'
 Provides-Extra: mqtt
 Requires-Dist: amqtt<0.13.0,>=0.12.0; extra == 'mqtt'
 Requires-Dist: paho-mqtt<3.0,>=2.0; extra == 'mqtt'
 Requires-Dist: pyyaml<7.0,>=6.0; extra == 'mqtt'
 Provides-Extra: restapi
 Requires-Dist: fastapi==0.111.1; extra == 'restapi'
-Requires-Dist: pydantic>=2.0.0; extra == 'restapi'
 Requires-Dist: pyserial>=3.5; extra == 'restapi'
 Requires-Dist: python-dotenv==1.2.2; extra == 'restapi'
 Requires-Dist: uvicorn[standard]==0.24.0; extra == 'restapi'
 Provides-Extra: service-ws
 Requires-Dist: websockets<16.0,>=13.0; extra == 'service-ws'
 Provides-Extra: tui
-Requires-Dist: pydantic>=2.0.0; extra == 'tui'
 Requires-Dist: pyserial>=3.5; extra == 'tui'
-Requires-Dist: requests>=2.33.1; extra == 'tui'
 Provides-Extra: vu
 Requires-Dist: blessed>=1.20.0; extra == 'vu'
 Requires-Dist: numpy; extra == 'vu'
 Requires-Dist: pillow>=10.0.0; extra == 'vu'
 Requires-Dist: pyserial>=3.5; extra == 'vu'
 Requires-Dist: pyyaml>=6.0; extra == 'vu'
-Requires-Dist: requests>=2.31.0; extra == 'vu'
 Requires-Dist: ruamel-yaml; extra == 'vu'
 Requires-Dist: tornado; extra == 'vu'
 Provides-Extra: wigidash
@@ -109,6 +115,7 @@ BENCHLAB PyTools is the Python-based control suite for BENCHLAB telemetry device
 - **VU Dials** — analog-style VU meter dial display and configuration
 - **WigiDash** — telemetry/graph display on a G.SKILL WigiDash panel
 - **Config Tool** — import/export device configuration (fan curves, RGB, etc.) via JSON
+- **Flash Tool** — flash new firmware onto BENCHLAB1/2 devices over USB DFU
 
 All tools share a common data-source layer, so the same telemetry can be read directly from a device, through a FastAPI server, over MQTT, or via the Windows BENCHLAB service — locally or remotely — without changing the consumer tool.
 
@@ -176,8 +183,25 @@ python -m benchlab -vu          # VU analog dials
 python -m benchlab -vuconfig    # VU dial configuration UI
 python -m benchlab -wigidash    # WigiDash display
 python -m benchlab -config ...  # Device configuration import/export
+python -m benchlab -flash ...   # Firmware flash tool (STM32 ROM DFU)
 ```
 
+The flash tool needs its extra: `pip install "benchlab-pytools[flash]"`. It takes a firmware
+image with `--file` and does not download one; releases live in
+[BENCHLAB-FW](https://github.com/BenchLab-io/BENCHLAB-FW/releases). Start with `--list` to see what
+is connected, and `--verify-only` to check an image against a device without erasing or writing:
+
+```bash
+python -m benchlab -flash --list
+python -m benchlab -flash --file benchlab2-fw07-v0.7.2.bin --verify-only
+```
+
+**On Windows, flashing needs a one-time driver step.** In DFU mode the board enumerates as
+ST's ROM bootloader (VID `0483`, PID `DF11`), which does not bind to a driver libusb can use,
+so the tool cannot see a device that is plugged in and sitting in its bootloader. Bind WinUSB
+to it with [Zadig](https://zadig.akeo.ie/) first -- see
+[Windows: USB driver setup](benchlab/flash/README.md#windows-usb-driver-setup-zadig).
+
 Running with no flags is equivalent to launching the interactive menu.
 
 ### Data Sources
@@ -218,7 +242,7 @@ Common connection flags:
 -i, --interval SECONDS     Refresh interval (default: 1.0)
 ```
 
-When a source needs a background service (`fastapi`, `mqtt`), the launcher starts and health-checks it automatically, and tears it down on exit. Not every tool supports every source — the config tool, for example, only supports `direct` and `named_pipe`. See each tool's README for specifics.
+When a source needs a background service (`fastapi`, `mqtt`), the launcher starts and health-checks it automatically, and tears it down on exit. Not every tool supports every source — the config and flash tools, for example, only support `direct`, `named_pipe`, and `service_http`. See each tool's README for specifics.
 
 ### Launch Profiles
 
@@ -259,6 +283,7 @@ Each consumer tool lives in its own subpackage under `benchlab/` with its own RE
 - [Core](benchlab/core/README.md) — shared internals (data sources, process management, discovery)
 - [CSV Logger](benchlab/csv_log/README.md)
 - [FastAPI Server](benchlab/restapi/readme.md)
+- [Flash Tool](benchlab/flash/README.md) — firmware flashing over USB DFU
 - [Graph](benchlab/graph/README.md)
 - [HWiNFO Export](benchlab/hwinfo/README.md)
 - [Link](benchlab/link/README.md) — publish telemetry to BENCHLAB cloud

{benchlab_pytools-3.2.1 → benchlab_pytools-3.3.1}/README.md

@@ -12,6 +12,7 @@ BENCHLAB PyTools is the Python-based control suite for BENCHLAB telemetry device
 - **VU Dials** — analog-style VU meter dial display and configuration
 - **WigiDash** — telemetry/graph display on a G.SKILL WigiDash panel
 - **Config Tool** — import/export device configuration (fan curves, RGB, etc.) via JSON
+- **Flash Tool** — flash new firmware onto BENCHLAB1/2 devices over USB DFU
 
 All tools share a common data-source layer, so the same telemetry can be read directly from a device, through a FastAPI server, over MQTT, or via the Windows BENCHLAB service — locally or remotely — without changing the consumer tool.
 
@@ -79,8 +80,25 @@ python -m benchlab -vu          # VU analog dials
 python -m benchlab -vuconfig    # VU dial configuration UI
 python -m benchlab -wigidash    # WigiDash display
 python -m benchlab -config ...  # Device configuration import/export
+python -m benchlab -flash ...   # Firmware flash tool (STM32 ROM DFU)
 ```
 
+The flash tool needs its extra: `pip install "benchlab-pytools[flash]"`. It takes a firmware
+image with `--file` and does not download one; releases live in
+[BENCHLAB-FW](https://github.com/BenchLab-io/BENCHLAB-FW/releases). Start with `--list` to see what
+is connected, and `--verify-only` to check an image against a device without erasing or writing:
+
+```bash
+python -m benchlab -flash --list
+python -m benchlab -flash --file benchlab2-fw07-v0.7.2.bin --verify-only
+```
+
+**On Windows, flashing needs a one-time driver step.** In DFU mode the board enumerates as
+ST's ROM bootloader (VID `0483`, PID `DF11`), which does not bind to a driver libusb can use,
+so the tool cannot see a device that is plugged in and sitting in its bootloader. Bind WinUSB
+to it with [Zadig](https://zadig.akeo.ie/) first -- see
+[Windows: USB driver setup](benchlab/flash/README.md#windows-usb-driver-setup-zadig).
+
 Running with no flags is equivalent to launching the interactive menu.
 
 ### Data Sources
@@ -121,7 +139,7 @@ Common connection flags:
 -i, --interval SECONDS     Refresh interval (default: 1.0)
 ```
 
-When a source needs a background service (`fastapi`, `mqtt`), the launcher starts and health-checks it automatically, and tears it down on exit. Not every tool supports every source — the config tool, for example, only supports `direct` and `named_pipe`. See each tool's README for specifics.
+When a source needs a background service (`fastapi`, `mqtt`), the launcher starts and health-checks it automatically, and tears it down on exit. Not every tool supports every source — the config and flash tools, for example, only support `direct`, `named_pipe`, and `service_http`. See each tool's README for specifics.
 
 ### Launch Profiles
 
@@ -162,6 +180,7 @@ Each consumer tool lives in its own subpackage under `benchlab/` with its own RE
 - [Core](benchlab/core/README.md) — shared internals (data sources, process management, discovery)
 - [CSV Logger](benchlab/csv_log/README.md)
 - [FastAPI Server](benchlab/restapi/readme.md)
+- [Flash Tool](benchlab/flash/README.md) — firmware flashing over USB DFU
 - [Graph](benchlab/graph/README.md)
 - [HWiNFO Export](benchlab/hwinfo/README.md)
 - [Link](benchlab/link/README.md) — publish telemetry to BENCHLAB cloud

{benchlab_pytools-3.2.1 → benchlab_pytools-3.3.1}/benchlab/__init__.py

@@ -2,4 +2,4 @@
 BENCHLAB Telemetry Package
 """
 
-__version__ = "3.2.1"
+__version__ = "3.3.1"

{benchlab_pytools-3.2.1 → benchlab_pytools-3.3.1}/benchlab/config/README.md

@@ -1,12 +1,12 @@
 # BENCHLAB Device Configuration Tool
 
-A command-line tool for importing and exporting BENCHLAB device configuration via JSON files. Supports both direct serial (pycore) and Windows named pipe (BL_Service) data sources.
+A command-line tool for importing and exporting BENCHLAB device configuration via JSON files. Supports direct serial (pycore), Windows named pipe (BL_Service), and the BL_Service HTTP API as data sources.
 
 ## Features
 
 - **Export Configuration**: Read current device settings and save to JSON
 - **Import Configuration**: Apply JSON configuration to devices
-- **Multi-Source Support**: Works with both direct serial and named pipe connections
+- **Multi-Source Support**: Works with direct serial, named pipe, and HTTP connections
 - **Interactive Mode**: Simple interface for loading JSON configs
 - **Validation**: Schema validation with detailed error messages
 - **Batch Operations**: Configure multiple devices from a single JSON file
@@ -29,6 +29,11 @@ For named pipe support (Windows only), you need:
 pip install pywin32
 ```
 
+For `service_http` support (talking to a running BL_Service instance over HTTP, any platform), you need:
+```bash
+pip install requests
+```
+
 ## Usage
 
 ### Interactive Mode
@@ -55,6 +60,11 @@ python -m benchlab -config --list
 
 # List devices via named pipe (Windows only)
 python -m benchlab -config --list --source named_pipe
+
+# List devices via the BL_Service HTTP API
+python -m benchlab -config --list --source service_http
+python -m benchlab -config --list --source service_http \
+    --service-url http://localhost:8585 --service-token secret
 ```
 
 #### Export Configuration
@@ -68,6 +78,9 @@ python -m benchlab -config --export my_config.json --device COM4
 
 # Export via named pipe
 python -m benchlab -config --export my_config.json --source named_pipe
+
+# Export via the BL_Service HTTP API
+python -m benchlab -config --export my_config.json --source service_http
 ```
 
 #### Import Configuration
@@ -88,6 +101,9 @@ python -m benchlab -config --import my_config.json --yes
 
 # Import via named pipe
 python -m benchlab -config --import my_config.json --source named_pipe
+
+# Import via the BL_Service HTTP API
+python -m benchlab -config --import my_config.json --source service_http
 ```
 
 ## JSON Configuration Format
@@ -120,6 +136,7 @@ python -m benchlab -config --import my_config.json --source named_pipe
 - **`port`**: Match by serial port (e.g., "COM4" - not portable)
 - **`productId`**: Match by product ID (0x10 or 0x11)
 - **`pipeName`**: Match by named pipe name (named_pipe source only)
+- **`guid`** is also required when using `service_http`, since the service addresses devices by their UID rather than a port or pipe name.
 
 **Note:** When exporting, the tool automatically uses `guid` selector with the device UID for portability. This allows you to export configuration on one system and import it on another, and the tool will find the same device regardless of which COM port it's connected to.
 
@@ -235,6 +252,25 @@ Uses the Windows BL_Service named pipe interface for communication.
 - Requires BL_Service to be running
 - Requires pywin32 library
 
+### Service HTTP (BL_Service HTTP API)
+
+Talks to a running BL_Service instance over its HTTP API (`--service-url`,
+default `http://localhost:8585`). Fan, RGB, and calibration read/write go
+through a translation layer (`benchlab/config/http_dto.py`) between the
+service's DTO JSON shapes and this tool's own config format — see that
+module if you're integrating against the HTTP API directly rather than
+through this tool.
+
+**Advantages:**
+- Cross-platform (the service itself may run anywhere reachable over HTTP)
+- Multiple tools can access the device simultaneously
+- No direct serial port management
+
+**Limitations:**
+- Requires BL_Service to be running and reachable
+- Requires the `requests` library
+- Device selector must use `guid` (the service addresses devices by UID, not port/pipe name)
+
 ## Configuration Profiles
 
 ### Profile IDs
@@ -276,6 +312,11 @@ Use `--dry-run` to preview exactly what would change on the device (connects and
 - Check Windows service status
 - Verify device is connected to service
 
+**Service HTTP:**
+- Ensure BL_Service is running and reachable at `--service-url`
+- Check `--service-token` if the service has token auth enabled
+- Verify the device UID is correct (use `--list` to see available UIDs)
+
 ### Import Fails
 
 - Use `--dry-run` to validate JSON syntax
@@ -316,12 +357,14 @@ manager.import_config('input.json', dry_run=False)
 ```
 
 For lower-level access (used internally by `ConfigManager`), `create_config_client()`
-returns a `ConfigClient` with `read_calibration()`/`write_calibration()`,
+returns a `ConfigClient` with `read_fan_config()`/`write_fan_config()`,
+`read_rgb_config()`/`write_rgb_config()`, `read_calibration()`/`write_calibration()`,
 `save_config()`/`load_config()`/`reset_config()`, and (BL2 firmware 7+ only)
 `factory_cal_unlock()`, which temporarily lifts write-protection on the factory
-calibration slot. There is no CLI/JSON-config surface for `factory_cal_unlock()` —
-it's a niche factory-calibration tool, not a user-facing config option, and a
-successful call resets the device immediately:
+calibration slot. All three sources (`direct`, `named_pipe`, `service_http`)
+implement the full interface. There is no CLI/JSON-config surface for
+`factory_cal_unlock()` — it's a niche factory-calibration tool, not a
+user-facing config option, and a successful call resets the device immediately:
 
 ```python
 from benchlab.config.config_client import create_config_client

{benchlab_pytools-3.2.1 → benchlab_pytools-3.3.1}/benchlab/config/config_client.py

@@ -10,6 +10,12 @@ import logging
 from abc import ABC, abstractmethod
 from typing import Optional, Dict, Any
 
+from .http_dto import (
+    fan_dto_to_dict, fan_dict_to_dto,
+    rgb_dto_to_dict, rgb_dict_to_dto,
+    calibration_dto_to_dict, calibration_dict_to_dto,
+)
+
 logger = logging.getLogger("benchlab.config.client")
 
 DISCOVERY_PIPE_NAME = "BenchlabDiscovery"
@@ -160,6 +166,18 @@ class ConfigClient(ABC):
         """
         pass
 
+    @abstractmethod
+    def enter_bootloader(self) -> bool:
+        """Jump the device into its USB DFU bootloader.
+
+        Disruptive: the device stops responding as a sensor/CDC device
+        immediately after this succeeds, and re-enumerates as USB DFU
+        (VID 0x0483 / PID 0xDF11). Callers must close this connection and
+        take over the device directly over USB from there -- see
+        benchlab.flash.flash_manager.
+        """
+        pass
+
     @abstractmethod
     def close(self):
         """Close connection and cleanup resources."""
@@ -473,6 +491,16 @@ class DirectConfigClient(ConfigClient):
             return False
         return factory_cal_unlock(self.ser)
 
+    def enter_bootloader(self) -> bool:
+        """Jump the device into its USB DFU bootloader.
+
+        Disruptive: the device stops responding over CDC immediately after
+        this succeeds. Mirrors enter_bootloader()'s own caveat in pycore --
+        the actual jump happens on the firmware's next 100ms task tick.
+        """
+        from benchlab_pycore.core.config_io import enter_bootloader
+        return enter_bootloader(self.ser)
+
     def close(self):
         """Close serial connection."""
         if self.ser and self.ser.is_open:
@@ -657,18 +685,218 @@ class NamedPipeConfigClient(ConfigClient):
         result = self._send_command("SendFactoryCalUnlock", payload="benchlab")
         return result and result.get('success', False)
 
+    def enter_bootloader(self) -> bool:
+        """Jump the device into its USB DFU bootloader.
+
+        Disruptive: the device stops responding over CDC immediately after
+        this succeeds, and the C# service marks it DISCONNECTED (it does
+        not treat this as a device error). Mirrors the service's own
+        SendBootloader pipe command and its HTTP equivalent
+        (POST /device/{uid}/bootloader).
+        """
+        result = self._send_command("SendBootloader")
+        return result and result.get('success', False)
+
     def close(self):
         """Close pipe connection."""
         self._close_pipe()
         logger.info(f"Closed named pipe connection to {self.pipe_name}")
 
 
-def create_config_client(source: str, identifier: str) -> ConfigClient:
+class HttpConfigClient(ConfigClient):
+    """Configuration client using the C# BenchLab service's HTTP API.
+
+    Implements device info, name, save/load config, fan/RGB/calibration
+    read-write, and the disruptive reset/bootloader/factory-cal-unlock
+    commands. Fan/RGB/calibration routes (GET/PUT /device/{uid}/fan,
+    /rgb/{profile}, /calibration) use DTOs with a different, more
+    structured shape than this repo's raw ctypes-struct-dict convention
+    (DirectConfigClient/NamedPipeConfigClient) -- see benchlab.config.
+    http_dto for the translation layer between the two. reset_config has
+    no HTTP equivalent at all (by design: the service only exposes
+    save/load actions, since no firmware contract defines a config-reset
+    opcode -- RESET power-cycles the whole device instead).
+    """
+
+    DEFAULT_URL = "http://localhost:8585"
+
+    def __init__(self, uid: str, base_url: str = DEFAULT_URL,
+                 token: Optional[str] = None, timeout: float = 5.0):
+        """Initialize an HTTP client scoped to one device.
+
+        Args:
+            uid: Device UID (used in /device/{uid}/... routes).
+            base_url: Base URL of the C# BenchLab service.
+            token: Optional X-Benchlab-Token value (only needed when the
+                service has token auth configured -- required on every
+                request except GET /health).
+            timeout: HTTP request timeout in seconds.
+        """
+        import requests
+
+        self.uid = uid
+        self.base_url = base_url.rstrip("/")
+        self.timeout = timeout
+        self._session = requests.Session()
+        if token:
+            self._session.headers["X-Benchlab-Token"] = token
+
+    def _get(self, path: str) -> Optional[Dict[str, Any]]:
+        try:
+            resp = self._session.get(
+                f"{self.base_url}{path}", timeout=self.timeout)
+            if resp.status_code == 200:
+                return resp.json()
+            logger.warning(
+                "GET %s -> %s: %s", path, resp.status_code, resp.text)
+            return None
+        except Exception as e:
+            logger.error(f"GET {path} failed: {e}")
+            return None
+
+    def _post(self, path: str, json_body=None) -> bool:
+        try:
+            resp = self._session.post(
+                f"{self.base_url}{path}", json=json_body,
+                timeout=self.timeout)
+            if resp.status_code in (200, 204):
+                return True
+            logger.warning(
+                "POST %s -> %s: %s", path, resp.status_code, resp.text)
+            return False
+        except Exception as e:
+            logger.error(f"POST {path} failed: {e}")
+            return False
+
+    def _put(self, path: str, json_body=None) -> bool:
+        try:
+            resp = self._session.put(
+                f"{self.base_url}{path}", json=json_body,
+                timeout=self.timeout)
+            if resp.status_code in (200, 204):
+                return True
+            logger.warning(
+                "PUT %s -> %s: %s", path, resp.status_code, resp.text)
+            return False
+        except Exception as e:
+            logger.error(f"PUT {path} failed: {e}")
+            return False
+
+    def get_device_info(self) -> Optional[Dict[str, Any]]:
+        """Get device information from GET /device/{uid}/info."""
+        return self._get(f"/device/{self.uid}/info")
+
+    def read_device_name(self) -> Optional[str]:
+        info = self.get_device_info()
+        return info.get('deviceName') if info else None
+
+    def write_device_name(self, name: str) -> bool:
+        """Write device friendly name via PUT /device/{uid}/name."""
+        return self._put(f"/device/{self.uid}/name", {"name": name})
+
+    def read_fan_config(self, profile_id: int,
+                        fan_id: int) -> Optional[Dict[str, Any]]:
+        """Read fan config via GET /device/{uid}/fan/{profile}/{fan}."""
+        dto = self._get(f"/device/{self.uid}/fan/{profile_id}/{fan_id}")
+        return fan_dto_to_dict(dto) if dto is not None else None
+
+    def write_fan_config(self, profile_id: int, fan_id: int,
+                         config: Dict[str, Any]) -> bool:
+        """Write fan config via PUT /device/{uid}/fan/{profile}/{fan}."""
+        return self._put(
+            f"/device/{self.uid}/fan/{profile_id}/{fan_id}",
+            fan_dict_to_dto(config))
+
+    def read_rgb_config(self, profile_id: int) -> Optional[Dict[str, Any]]:
+        """Read RGB config via GET /device/{uid}/rgb/{profile}."""
+        dto = self._get(f"/device/{self.uid}/rgb/{profile_id}")
+        return rgb_dto_to_dict(dto) if dto is not None else None
+
+    def write_rgb_config(self, profile_id: int,
+                         config: Dict[str, Any]) -> bool:
+        """Write RGB config via PUT /device/{uid}/rgb/{profile}."""
+        return self._put(
+            f"/device/{self.uid}/rgb/{profile_id}", rgb_dict_to_dto(config))
+
+    def read_calibration(self) -> Optional[Dict[str, Any]]:
+        """Read calibration via GET /device/{uid}/calibration.
+
+        Works for both BENCHLAB Original and BL2 -- the service resolves
+        the connected device's variant server-side and returns a
+        CalibrationDto with array lengths matching that variant.
+        """
+        dto = self._get(f"/device/{self.uid}/calibration")
+        return calibration_dto_to_dict(dto) if dto is not None else None
+
+    def write_calibration(self, calibration: Dict[str, Any]) -> bool:
+        """Write calibration via PUT /device/{uid}/calibration.
+
+        No read-before-write: the server validates the submitted array
+        lengths (Vin/Ts/TsB/power arrays) against the connected device's
+        own variant and rejects a mismatch with a 400 (surfaced here as a
+        logged warning and a False return). Callers are expected to pass
+        a dict shaped like read_calibration()'s own output. The submitted
+        Crc is ignored -- the server always recomputes it before writing.
+        """
+        return self._put(
+            f"/device/{self.uid}/calibration",
+            calibration_dict_to_dto(calibration))
+
+    def save_config(self) -> bool:
+        """Save configuration to device flash via
+        POST /device/{uid}/config/save."""
+        return self._post(f"/device/{self.uid}/config/save")
+
+    def load_config(self) -> bool:
+        """Reload configuration from device flash via
+        POST /device/{uid}/config/load."""
+        return self._post(f"/device/{self.uid}/config/load")
+
+    def reset_config(self) -> bool:
+        raise NotImplementedError(
+            "HttpConfigClient does not support config reset -- the C# "
+            "service has no HTTP route for it, by design: no firmware "
+            "contract defines a config-reset opcode (use the device's "
+            "RESET command / POST /device/{uid}/reset to power-cycle "
+            "instead, which is not equivalent)")
+
+    def factory_cal_unlock(self) -> bool:
+        """Temporarily lift write-protection on BL2's factory calibration
+        slot via POST /device/{uid}/factory-cal-unlock.
+
+        Disruptive: a successful call resets the device immediately -- the
+        service marks it DISCONNECTED until it re-enumerates.
+        """
+        return self._post(
+            f"/device/{self.uid}/factory-cal-unlock",
+            json_body={"passphrase": "benchlab"})
+
+    def enter_bootloader(self) -> bool:
+        """Jump the device into its USB DFU bootloader via
+        POST /device/{uid}/bootloader.
+
+        Disruptive: the device stops responding over CDC immediately after
+        this succeeds, and the C# service marks it DISCONNECTED (it does
+        not treat this as a device error).
+        """
+        return self._post(f"/device/{self.uid}/bootloader")
+
+    def close(self):
+        """Close the HTTP session."""
+        self._session.close()
+
+
+def create_config_client(
+        source: str, identifier: str, base_url: Optional[str] = None,
+        token: Optional[str] = None) -> ConfigClient:
     """Factory function to create appropriate config client.
 
     Args:
-        source: 'direct' or 'named_pipe'
-        identifier: Port name for direct, pipe name for named_pipe
+        source: 'direct', 'named_pipe', or 'service_http'
+        identifier: Port name for direct, pipe name for named_pipe, device
+            UID for service_http
+        base_url: Service base URL (service_http only)
+        token: Optional X-Benchlab-Token (service_http only)
 
     Returns:
         ConfigClient instance
@@ -681,5 +909,12 @@ def create_config_client(source: str, identifier: str) -> ConfigClient:
         return DirectConfigClient(identifier)
     elif source == 'named_pipe':
         return NamedPipeConfigClient(identifier)
+    elif source == 'service_http':
+        kwargs = {}
+        if base_url:
+            kwargs['base_url'] = base_url
+        if token:
+            kwargs['token'] = token
+        return HttpConfigClient(identifier, **kwargs)
     else:
         raise ValueError(f"Invalid source type: {source}")