mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #554] [Bug]: Maintenance breaks after updating total print time (v0.2.1) #362
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#362
Loading…
Add table
Add a link
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?
Originally created by @Percy2Live on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/554
Originally assigned to: @maziggy on GitHub.
Bug Description
In v0.2.1 the Maintenance section becomes unusable after modifying the printer’s total print time.
Initial state:
Fresh database
Printer added successfully (P1S)
Custom maintenance entries can be created
Maintenance page works as expected
After changing the printer’s total print time (e.g. setting it to 2300h):
Maintenance page shows: “No printer configured”
Printer is still present in the printers table, but shows no maintenance anymore
Reproduces consistently
Deleting and recreating the database does not prevent the issue
Expected Behavior
Maintenance should work as intended
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.2.1
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
bambuddy-support-20260228-141614.zip
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 28, 2026):
Good catch, thanks! Fixed in branch 0.2.2b1.
@Percy2Live commented on GitHub (Feb 28, 2026):
Great to hear that. I'm obviously better at searching bugs than coding^^
Are you aware that in this state the backup functionality is also not working?
@Percy2Live commented on GitHub (Mar 1, 2026):
Can confirm this works now in 0.2.2b1.
Also solved the backup problem