[GH-ISSUE #497 ] [Bug]: Print Bed Cooled Notification stopped working #313

Owner

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

setup print bed cooled notifications and set desired temperature
Print something
Wait 😀

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

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 @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 1. setup print bed cooled notifications and set desired temperature 2. Print something 3. Wait 😀 ### 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 ```shell ``` ### 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

BreizhHardware

closed this issue
added the
bug
label

BreizhHardware commented

Author

Owner

@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!

@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](https://github.com/bambuman/bambuddy) — it helps others discover the project!

BreizhHardware commented

Author

Owner

@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

@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

BreizhHardware commented

Author

Owner

@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)

@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)

BreizhHardware commented

Author

Owner

@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): Yup. Ill wait for my next print to finish and get close to the right temp before hitting debug <img width="255" height="130" alt="Image" src="https://github.com/user-attachments/assets/1733a4c5-4c1d-445c-9430-a4947c643277" />

BreizhHardware commented

bambuddy-support-20260224-141512.zip

Author

Owner

@hollycroftlabs commented on GitHub (Feb 24, 2026):

Hi, managed to get some debug logs. Printer dropped below 35 degrees at about 14:14

@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](https://github.com/user-attachments/files/25522031/bambuddy-support-20260224-141512.zip)

BreizhHardware commented

Author

Owner

@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.

2026-02-21 15:07:23,479 WARNING [backend.app.services.bambu_ftp] FTP SSL error connecting to [IP]: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1032)
2026-02-21 16:14:29,783 WARNING [backend.app.services.bambu_ftp] FTP connection failed to [IP]: [Errno 104] Connection reset by peer (type: ConnectionResetError)
2026-02-21 16:15:33,879 WARNING [backend.app.services.bambu_ftp] FTP connection failed to [IP]: [Errno 104] Connection reset by peer (type: ConnectionResetError)

@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. >2026-02-21 15:07:23,479 WARNING [backend.app.services.bambu_ftp] FTP SSL error connecting to [IP]: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1032) >2026-02-21 16:14:29,783 WARNING [backend.app.services.bambu_ftp] FTP connection failed to [IP]: [Errno 104] Connection reset by peer (type: ConnectionResetError) >2026-02-21 16:15:33,879 WARNING [backend.app.services.bambu_ftp] FTP connection failed to [IP]: [Errno 104] Connection reset by peer (type: ConnectionResetError)

BreizhHardware commented

Author

Owner

@hollycroftlabs commented on GitHub (Feb 24, 2026):

Just checked and all 3 printers have developer mode on

@hollycroftlabs commented on GitHub (Feb 24, 2026): Just checked and all 3 printers have developer mode on

BreizhHardware commented

Author

Owner

@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:

LAN Only Mode is ON
Developer Mode is ON (this option only appears after LAN Only Mode is enabled)
The Access Code in Bambuddy matches the one shown on the printer

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.

@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: 1. LAN Only Mode is ON 2. Developer Mode is ON (this option only appears after LAN Only Mode is enabled) 3. The Access Code in Bambuddy matches the one shown on the printer 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.

BreizhHardware commented

Author

Owner

@hollycroftlabs commented on GitHub (Feb 26, 2026):

Evening,

Jus checked all 3 printers:

LAN mode ON
Developer mode ON
Access codes correct

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.

@hollycroftlabs commented on GitHub (Feb 26, 2026): Evening, Jus checked all 3 printers: 1. LAN mode ON 2. Developer mode ON 3. Access codes correct 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.

BreizhHardware commented

Author

Owner

@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

@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

BreizhHardware commented

bambuddy-support-20260310-125453.zip

Author

Owner

@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.

@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](https://github.com/user-attachments/files/25870291/bambuddy-support-20260310-125453.zip)

BreizhHardware commented

Author

Owner

@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?

Update your docker image -> git pull && git checkout 0.2.2b3 && git pull && docker compose down && docker compose up --build -d
Before starting a print, enable debug logging in Settings → Support → Debug Logging
Let a print complete and wait for the bed cooldown to either succeed or time out (~30 min)
Download a support package and attach it here

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!

@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? 1. Update your docker image -> git pull && git checkout 0.2.2b3 && git pull && docker compose down && docker compose up --build -d 2. Before starting a print, enable debug logging in Settings → Support → Debug Logging 3. Let a print complete and wait for the bed cooldown to either succeed or time out (~30 min) 4. Download a support package and attach it here 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!

BreizhHardware commented

Author

Owner

@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

@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

BreizhHardware commented