maziggy 1234f0830a fix(mqtt): don't let K-profile responses clobber the nozzle size (#2663) ...

Fetching K-profiles probes every nozzle size in turn (extrusion_cali_get
for 0.2/0.4/0.6/0.8mm), and each response echoes the requested diameter at
the top level. _process_message passed every "print" message -- including
these responses -- to _update_state, which treats a top-level
nozzle_diameter as the installed hardware. So the last size probed (0.8)
overwrote the real nozzle in memory; a genuine status push corrected it and
the next K-profile fetch broke it again, which is why it flickered between
0.8, empty and the correct 0.4. Since 1.2.5 the #1899 mismatch guard then
refused to dispatch, failing prints with a bogus "printer has 0.8mm".

Handle extrusion_cali_get responses only via the K-profile parser and skip
_update_state for them, mirroring the existing get_accessories guard. The
nozzle size now comes solely from the real status push. In-memory only --
affected printers self-correct on the next push after updating.

2026-07-27 09:15:34 +02:00

..

app

fix(mqtt): don't let K-profile responses clobber the nozzle size (#2663)

2026-07-27 09:15:34 +02:00

tests

fix(mqtt): don't let K-profile responses clobber the nozzle size (#2663)

2026-07-27 09:15:34 +02:00

__init__.py

…