starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #736] [Bug]: Print completed Notification stopped working #491

New issue

Closed

opened 2026-05-07 00:10:49 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

2026-05-07 00:10:49 +02:00

Owner

Originally created by @piatho on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/736

Originally assigned to: @maziggy on GitHub.

Bug Description

The notification for completed prints seems to not trigger. I am getting notifications for everything incl percentage completed 25%, 50% and 75% but the final print completed does not come although activated.

The notification also does not appear in the notification log

I am using NTFY as notification broker.

I am on v0.2.2 using docker container

Expected Behavior

Notification for prints completed would be expected if as in my case the toggle is et to active for "print completed"

Steps to Reproduce

Activate NTFY
Setup "Print completed" notification
Wait for a print to complete

Printer Model

P1S

Bambuddy Version

0.2.2

Printer Firmware Version

01.09.01.00

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

No response

Screenshots

No response

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
My printer has Developer Mode enabled

Originally created by @piatho on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/736 Originally assigned to: @maziggy on GitHub. ### Bug Description The notification for completed prints seems to not trigger. I am getting notifications for everything incl percentage completed 25%, 50% and 75% but the final print completed does not come although activated. The notification also does not appear in the notification log I am using NTFY as notification broker. I am on v0.2.2 using docker container ### Expected Behavior Notification for prints completed would be expected if as in my case the toggle is et to active for "print completed" <img width="674" height="210" alt="Image" src="https://github.com/user-attachments/assets/d0daa7e1-0a8d-420e-a7e1-f477288dd615" /> ### Steps to Reproduce Activate NTFY Setup "Print completed" notification Wait for a print to complete ### Printer Model P1S ### Bambuddy Version 0.2.2 ### Printer Firmware Version 01.09.01.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package _No response_ ### Screenshots _No response_ ### 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 - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:10:49 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:10:50 +02:00

Author

Owner

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

Thanks for reporting this — I was able to confirm the issue.

The print complete notification was chained behind the finish photo capture with no timeout. If the camera connection stalled after the print finished, the notification would silently never send — while progress notifications (25/50/75%) worked fine because they use a completely different code path.

This is now fixed and available in branch dev, next release or daily build.

If you still see the issue after updating, please enable debug logging during print finishes and upload the logs.

@maziggy commented on GitHub (Mar 17, 2026): Thanks for reporting this — I was able to confirm the issue. The print complete notification was chained behind the finish photo capture with no timeout. If the camera connection stalled after the print finished, the notification would silently never send — while progress notifications (25/50/75%) worked fine because they use a completely different code path. This is now fixed and available in branch dev, next release or daily build. If you still see the issue after updating, please enable debug logging during print finishes and upload the logs.

BreizhHardware commented

2026-05-07 00:10:51 +02:00

Author

Owner

@stringham commented on GitHub (Mar 18, 2026):

I noticed that the print completed notification did not send if "Auto-archive completed prints" is not checked on the printer. Perhaps this is a different issue.

@stringham commented on GitHub (Mar 18, 2026): I noticed that the print completed notification did not send if "Auto-archive completed prints" is not checked on the printer. Perhaps this is a different issue.

BreizhHardware commented

2026-05-07 00:10:51 +02:00

Author

Owner

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

Cannot reproduce. Please open a new issue and attach a support package.

@maziggy commented on GitHub (Mar 19, 2026): Cannot reproduce. Please open a new issue and attach a support package.

BreizhHardware commented

2026-05-07 00:10:51 +02:00

Author

Owner

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

@stringham , @maziggy I can confirm this. If i switch on "Auto-archive completed prints" my complete print notification is send. Since i am still on v 0.2.2, commit [dbe8696] github.com/maziggy/bambuddy@dbe86968b0) seems to be not the reason it works with "Auto-archive completed prints" and not without it

@piatho commented on GitHub (Mar 19, 2026): @stringham , @maziggy I can confirm this. If i switch on "Auto-archive completed prints" my complete print notification is send. Since i am still on v 0.2.2, commit [dbe8696] https://github.com/maziggy/bambuddy/commit/dbe86968b00218e65f38b35432118e095a053375) seems to be not the reason it works with "Auto-archive completed prints" and not without it

BreizhHardware commented

2026-05-07 00:10:51 +02:00

Author

Owner

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

See my last comment.

@maziggy commented on GitHub (Mar 19, 2026): See my last comment.

BreizhHardware referenced this issue

2026-05-07 00:15:45 +02:00

[PR #491] [CLOSED] Feature/184 #1058