mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-10-18 11:56:01 +02:00
maziggy
115d6fe627
Archive reprints and library-file prints built the MQTT project_file command with hardcoded project_id="0", subtask_id="0", task_id="0". Printers key per-job state (including gcode_start_time) on those IDs, so reprints looked like continuations of the same job and third-party MQTT observers (OctoEverywhere) reported compounding durations across repeat replays — a 40 min job reprinted from archive showed ~1h40m, and a second reprint of the same file showed ~4h. BambuStudio mints fresh IDs per submission; bambu_mqtt.start_print() now does the same using an epoch-millisecond timestamp for all three fields. md5 is deliberately left empty to avoid activating firmware md5-validation against a digest we can't compute without re-reading the upload. Added 6 regression tests in TestStartPrintUniqueIdentityFields covering non-zero IDs, md5 stays empty, uniqueness across successive submissions, numeric-string format, and blast-radius guard on unrelated payload fields. Updated CHANGELOG.