maziggy 82c90c6387 fix(mqtt): skip print-start fire on first RUNNING after Bambuddy startup (#1304) ...

Restarting Bambuddy mid-print misfired the plate-check + archive flow.
  The is_new_print guard treated _previous_gcode_state=None → RUNNING as
  a transition, but None just means we haven't seen any prior state yet —
  catch-up from a printer that was already running, not a fresh start.

  Add `_previous_gcode_state is not None` to the guard. _was_running still
  flips on unconditionally, so completion detection is unchanged. 3 tests
  that asserted the buggy behavior now seed an explicit prior state; new
  regression test pins the contract for the reporter's exact scenario.

2026-05-13 09:57:20 +02:00

..

app

fix(mqtt): skip print-start fire on first RUNNING after Bambuddy startup (#1304)

2026-05-13 09:57:20 +02:00

tests

fix(mqtt): skip print-start fire on first RUNNING after Bambuddy startup (#1304)

2026-05-13 09:57:20 +02:00

__init__.py

Added screenshots

2025-11-28 10:23:59 +01:00