starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #307] [Bug]: Archive Duplication Issue #190

New issue

Closed

opened 2026-05-06 12:27:01 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:27:01 +02:00

Owner

Originally created by @jjjonesjr33 on GitHub (Feb 9, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/307

Originally assigned to: @maziggy on GitHub.

Bug Description

When reconnecting or restarting Bambuddy while a printer is actively printing, the same project is automatically archived again, resulting in duplicate archive entries.

Expected Behavior

The archive process should avoid creating duplicates. While the system does correctly label them as duplicates, they are still being created unnecessarily.

Steps to Reproduce

Rebooting the software while a file is actively printing triggers this behavior.

Printer Model

H2C

Bambuddy Version

v0.1.8.1

Printer Firmware Version

01.01.03.00

Installation Method

Docker

Operating System

Other

Relevant Logs / Support Package

file:///C:/Users/jjjon/Downloads/bambuddy-support-20260208-223050.zip

Screenshots

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode

Originally created by @jjjonesjr33 on GitHub (Feb 9, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/307 Originally assigned to: @maziggy on GitHub. ### Bug Description When reconnecting or restarting Bambuddy while a printer is actively printing, the same project is automatically archived again, resulting in duplicate archive entries. ### Expected Behavior The archive process should avoid creating duplicates. While the system does correctly label them as duplicates, they are still being created unnecessarily. ### Steps to Reproduce Rebooting the software while a file is actively printing triggers this behavior. ### Printer Model H2C ### Bambuddy Version v0.1.8.1 ### Printer Firmware Version 01.01.03.00 ### Installation Method Docker ### Operating System Other ### Relevant Logs / Support Package ```shell file:///C:/Users/jjjon/Downloads/bambuddy-support-20260208-223050.zip ``` ### Screenshots <img width="1152" height="635" alt="Image" src="https://github.com/user-attachments/assets/b7779c83-7140-4fb0-a156-ae255195f5f9" /> ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode

BreizhHardware

2026-05-06 12:27:01 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:27:02 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 9, 2026):

Thanks for reporting! The H2C isn't officially supported yet, so there may be differences in how its firmware broadcasts print state over MQTT that cause duplicate archive triggers.

There is duplicate detection logic in place that prevents this on supported printers (A1, P1S, X1C) — it checks for existing archives on restart and reuses them. The fact that duplicates are correctly labeled shows the detection is working, but the prevention step may not be catching the H2C's specific state transitions.

I'll start looking into H2C support today. In the meantime, you can safely delete the duplicate entries from the archive.

@maziggy commented on GitHub (Feb 9, 2026): Thanks for reporting! The H2C isn't officially supported yet, so there may be differences in how its firmware broadcasts print state over MQTT that cause duplicate archive triggers. There is duplicate detection logic in place that prevents this on supported printers (A1, P1S, X1C) — it checks for existing archives on restart and reuses them. The fact that duplicates are correctly labeled shows the detection is working, but the prevention step may not be catching the H2C's specific state transitions. I'll start looking into H2C support today. In the meantime, you can safely delete the duplicate entries from the archive.

BreizhHardware commented

2026-05-06 12:27:02 +02:00

Author

Owner

@leisegang commented on GitHub (Mar 19, 2026):

The duplicates are also couted as many times as there are duplicates.
In my installation i se that if i start a print at 1900 and it is finished at 0200 the next day it is archived 2 times. and filament is added twice leaving cost tracking and filament tracking not correct.

@leisegang commented on GitHub (Mar 19, 2026): The duplicates are also couted as many times as there are duplicates. In my installation i se that if i start a print at 1900 and it is finished at 0200 the next day it is archived 2 times. and filament is added twice leaving cost tracking and filament tracking not correct.

BreizhHardware commented

2026-05-06 12:27:02 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 19, 2026):

Need more details. Please open a new issue and upload a support package.

@maziggy commented on GitHub (Mar 19, 2026): Need more details. Please open a new issue and upload a support package.

BreizhHardware referenced this issue

2026-05-06 12:34:08 +02:00

[PR #191] [MERGED] Fix Spoolman sync for transparent/natural filament spools #950

BreizhHardware referenced this issue

2026-05-06 12:34:11 +02:00

[PR #203] [MERGED] v0.1.6 final #957