starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 13:45:32 +02:00

[GH-ISSUE #872] [Bug]: Print Bed Cooled Notification not working #594

New issue

Closed

opened 2026-05-06 12:31:13 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-06 12:31:13 +02:00

Owner

Originally created by @MERCURIALZED on GitHub (Apr 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/872

Originally assigned to: @maziggy on GitHub.

Bug Description

I have set a bed cooled threshold of 35c.
It does not fire at 35c, or any other temp below 35c.
It never fires.
All other notifications work.

I am aware of this closed issue. https://github.com/maziggy/bambuddy/issues/497

Expected Behavior

See a notification in the log function under Settings> Notifications> Providers
I expected to receive a notification in my configured web book notification provider

Steps to Reproduce

start print
finish print
let machine cool with door open or closed from 70c.
_- Door Open in this case to speed the cooling process so the log is not excessively long just to reproduce the issue. Logs started at 37C to reduce log size in hopes of capturing the event succinctly _

Printer Model

P2S

Bambuddy Version

v0.2.2.2

Printer Firmware Version

01.00.05.00

Installation Method

Docker

Operating System

Linux (Other)

Relevant Logs / Support Package

bambuddy-support-20260402-061915.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
My printer has Developer Mode enabled

Originally created by @MERCURIALZED on GitHub (Apr 2, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/872 Originally assigned to: @maziggy on GitHub. ### Bug Description - I have set a bed cooled threshold of 35c. - It does not fire at 35c, or any other temp below 35c. - It never fires. - All other notifications work. I am aware of this closed issue. https://github.com/maziggy/bambuddy/issues/497 ### Expected Behavior - See a notification in the log function under Settings> Notifications> Providers - I expected to receive a notification in my configured web book notification provider ### Steps to Reproduce - start print - finish print - let machine cool with door open or closed from 70c. _- Door Open in this case to speed the cooling process so the log is not excessively long just to reproduce the issue. Logs started at 37C to reduce log size in hopes of capturing the event succinctly _ ### Printer Model P2S ### Bambuddy Version v0.2.2.2 ### Printer Firmware Version 01.00.05.00 ### Installation Method Docker ### Operating System Linux (Other) ### Relevant Logs / Support Package [bambuddy-support-20260402-061915.zip](https://github.com/user-attachments/files/26429099/bambuddy-support-20260402-061915.zip) ### Screenshots <img width="755" height="548" alt="Image" src="https://github.com/user-attachments/assets/4d94d48d-6a89-42ef-8003-ed0281a6dc1e" /> ### 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-06 12:31:13 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:31:13 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 2, 2026):

The root cause is the same as #497 — after a print completes, your P2S firmware (01.00.05.00) stops including bed_temper in MQTT updates. The previous fix sent periodic pushall requests to force fresh data, but your firmware doesn't include bed temperature even in pushall responses. The cached value stays frozen at the end-of-print temperature, the 30-minute polling loop never sees it drop below threshold, and times out silently.

I've replaced the entire polling approach with an event-driven one. Instead of polling cached temperatures on a timer, Bambuddy now registers a waiter when your print completes and reacts instantly whenever bed_temper data actually arrives via MQTT — no timeout, no stale data. The notification fires as soon as the printer reports the bed is at or below your configured threshold, whenever that may be.

Available/Fixed in branch dev and available with the next release or daily build.

Please let me know if it works for you.

@maziggy commented on GitHub (Apr 2, 2026): The root cause is the same as #497 — after a print completes, your P2S firmware (01.00.05.00) stops including bed_temper in MQTT updates. The previous fix sent periodic pushall requests to force fresh data, but your firmware doesn't include bed temperature even in pushall responses. The cached value stays frozen at the end-of-print temperature, the 30-minute polling loop never sees it drop below threshold, and times out silently. I've replaced the entire polling approach with an event-driven one. Instead of polling cached temperatures on a timer, Bambuddy now registers a waiter when your print completes and reacts instantly whenever bed_temper data actually arrives via MQTT — no timeout, no stale data. The notification fires as soon as the printer reports the bed is at or below your configured threshold, whenever that may be. Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.

BreizhHardware commented

2026-05-06 12:31:14 +02:00

Author

Owner

@MERCURIALZED commented on GitHub (Apr 2, 2026):

The root cause is the same as #497 — after a print completes, your P2S firmware (01.00.05.00) stops including bed_temper in MQTT updates. The previous fix sent periodic pushall requests to force fresh data, but your firmware doesn't include bed temperature even in pushall responses. The cached value stays frozen at the end-of-print temperature, the 30-minute polling loop never sees it drop below threshold, and times out silently.

I've replaced the entire polling approach with an event-driven one. Instead of polling cached temperatures on a timer, Bambuddy now registers a waiter when your print completes and reacts instantly whenever bed_temper data actually arrives via MQTT — no timeout, no stale data. The notification fires as soon as the printer reports the bed is at or below your configured threshold, whenever that may be.

Available/Fixed in branch dev and available with the next release or daily build.

Please let me know if it works for you.

Home from work. Will test tonight and report back!

@MERCURIALZED commented on GitHub (Apr 2, 2026): > The root cause is the same as [#497](https://github.com/maziggy/bambuddy/issues/497) — after a print completes, your P2S firmware (01.00.05.00) stops including bed_temper in MQTT updates. The previous fix sent periodic pushall requests to force fresh data, but your firmware doesn't include bed temperature even in pushall responses. The cached value stays frozen at the end-of-print temperature, the 30-minute polling loop never sees it drop below threshold, and times out silently. > > I've replaced the entire polling approach with an event-driven one. Instead of polling cached temperatures on a timer, Bambuddy now registers a waiter when your print completes and reacts instantly whenever bed_temper data actually arrives via MQTT — no timeout, no stale data. The notification fires as soon as the printer reports the bed is at or below your configured threshold, whenever that may be. > > Available/Fixed in branch dev and available with the next release or daily build. > > Please let me know if it works for you. Home from work. Will test tonight and report back!

BreizhHardware commented

2026-05-06 12:31:14 +02:00

Author

Owner

@MERCURIALZED commented on GitHub (Apr 5, 2026):

Can confirm that the latest daily build does resolve this issue. Thank you for your work!

@MERCURIALZED commented on GitHub (Apr 5, 2026): Can confirm that the latest daily build does resolve this issue. Thank you for your work!

BreizhHardware commented

2026-05-06 12:31:14 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 7, 2026):

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Apr 7, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!