fix: /status usually reports offline even though printing works #2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The web UI's
/statusendpoint (CONFIG?/BATTERY? over the shared RFCOMM socket) intermittently or persistently reports the printer as offline, while print jobs on the same link succeed. Observed behavior on the P21 at 09:E2:D5:44:88:8A:0x00byte); a second attempt works.b'\x00'toCONFIG?), then recovers after a disconnect/reconnect or a pause._with_linkgives up after 3 empty-reply retries, which is not enough when the printer needs a longer settle.Fix direction: treat a stray short/garbage reply as "retry" (not just empty), increase settle/retry budget for queries, and consider closing the RFCOMM socket between query bursts so the link re-initializes cleanly. The status poll is already at 15 min cadence — the goal is that when it does fire, it succeeds.
Reported 2026-10-18 during web UI development (branch
webui).