You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /detail `name` field is user-mutable, so renaming a printer broke
model detection. `pid` is firmware-set and stable.
Also exposes Pid on FFMachineInfo. Bumps to 1.3.1.
Refs: GhostTypes/ff-5mp-hass#13
Copy file name to clipboardExpand all lines: CHANGELOG.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
## [1.3.1] - 2026-05-08
11
+
12
+
### Fixed
13
+
14
+
- Printer model detection (`IsPro`, `IsAD5X` on `FFMachineInfo`) now reads the firmware-set integer `pid` field on `/detail` instead of string-matching the user-mutable `name` field. Renaming an Adventurer 5M / 5M Pro / AD5X via the LCD or cloud no longer breaks model detection in downstream consumers (Electron UI, Web UI). Falls back to the legacy name+capability heuristic when `pid` is absent so older firmware still works. Reported in [ff-5mp-hass#13](https://github.com/GhostTypes/ff-5mp-hass/issues/13).
15
+
16
+
### Added
17
+
18
+
-`FFMachineInfo.Pid: number | undefined` — the raw firmware PID exposed for consumers that want to do their own model-class gating. Known modern HTTP-capable PIDs: `35` (Adventurer 5M), `36` (5M Pro), `38` (AD5X).
19
+
20
+
### Changed
21
+
22
+
- Corrected misleading JSDoc on `FFPrinterDetail.pid` (was "Process ID, possibly related to the current print job"; it is in fact the firmware-set Product ID).
/** Firmware-set Product ID identifying the printer model (e.g. 35=Adventurer 5M, 36=5M Pro, 38=AD5X). Undefined on firmware that doesn't report it. */
240
+
Pid?: number;
239
241
/** Indicates if the printer model is a "Pro" version. */
0 commit comments