mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #497] [Bug]: Print Bed Cooled Notification stopped working #315
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
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-maziggy-1#315
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 @hollycroftlabs on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/497
Originally assigned to: @maziggy on GitHub.
Bug Description
The notification for "Print Bed Cooled" never triggers. This used to work after it was implemented but seems broken currently.
Expected Behavior
I get a notification when the print bed cools to below my set temperature.
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.2.1b2
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 23, 2026):
Good catch. Thanks for reporting.
Fixed in branch 0.2.1b3.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!
@hollycroftlabs commented on GitHub (Feb 24, 2026):
Hi, sorry to say this is still not working in 0.2.1b3
Notification doesn't seem to trigger
@maziggy commented on GitHub (Feb 24, 2026):
Are you really sure you're running 0.2.1b3? Upload a support package please (https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging)
@hollycroftlabs commented on GitHub (Feb 24, 2026):
Yup. Ill wait for my next print to finish and get close to the right temp before hitting debug
@hollycroftlabs commented on GitHub (Feb 24, 2026):
Hi, managed to get some debug logs. Printer dropped below 35 degrees at about 14:14
bambuddy-support-20260224-141512.zip
@maziggy commented on GitHub (Feb 24, 2026):
Bambuddy cannot connect to your printer via FTP. I would bet, developer mode is not enabled on your printers.
@hollycroftlabs commented on GitHub (Feb 24, 2026):
Just checked and all 3 printers have developer mode on
@maziggy commented on GitHub (Feb 26, 2026):
The support package logs show that Bambuddy cannot establish FTP connections to your printer(s):
WARNING [bambu_ftp] FTP SSL error connecting to [IP]: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol WARNING [bambu_ftp] FTP connection failed to [IP]: [Errno 104] Connection reset by peer
These errors are a strong indicator that Developer Mode is not fully enabled on the printer(s). Could you please double-check:
Note that toggling these settings off and on will generate a new access code that needs to be updated in Bambuddy.
The bed cooled notification itself relies on MQTT (not FTP), but if your printer connections are unstable, the temperature monitor may silently time out before the notification can fire.
The fix in 0.2.1b3 was for a different scenario (notifications not triggering for prints started from BambuStudio/touchscreen). Your issue appears to be connection-related.
@hollycroftlabs commented on GitHub (Feb 26, 2026):
Evening,
Jus checked all 3 printers:
toggling developer mode made no difference to the access codes.
As for the issue, most of my prints come from either the Queue or direct from the file manager.
@maziggy commented on GitHub (Feb 27, 2026):
Very curious....
Please use branch 0.2.1 and send me a new support package.
git checkout 0.2.1 && git pull && docker compose down && docker compose up --build -d
@hollycroftlabs commented on GitHub (Mar 10, 2026):
Apologies for not getting around to this sooner. Im now running on 0.2.3b1 and im still getting no notifications when print bed reaches the temp in the settings (35)
For infor, this print was started from the file manager in Bambuddy. Based on previous discussions I have also turned developer mode off, lan mode off, then both back on and regenerated an access code for each printer.
Interestingly, the access code changed from a numeric only to hex values.
bambuddy-support-20260310-125453.zip
@maziggy commented on GitHub (Mar 11, 2026):
I looked through your support package logs and found that every single bed cooldown monitor across all 3 of your printers timed out after exactly 30 minutes. The monitor started correctly but never detected the temperature dropping below threshold. Unfortunately the debug logs didn't cover an active cooldown window, so I couldn't see what temperature values the monitor was actually reading.
I've added detailed debug logging to the bed cooldown polling loop in the next build. Each poll will now log the actual bed temperature value vs threshold, which will tell us whether the temperature is stale, missing, or something else entirely.
Could you help collect new logs?
The new log lines will look like:
[BED-COOL] Printer 1: bed=55.0°C, threshold=35°C
or if the temperature is missing:
[BED-COOL] Printer 1: bed temp is None (keys: [...], state: FINISH)
That will tell us exactly what's going on. Thanks!
@hollycroftlabs commented on GitHub (Mar 17, 2026):
This seems to be working in the latest branch. I have tried printing from Bambu Studio and from File manaer and I am getting the notifications.
Thanks
@maziggy commented on GitHub (Mar 17, 2026):
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!