starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #1178] [Bug]: Raspberry Pi 4 CPU temperature allways around 70°C #855

New issue

Open

opened 2026-05-06 12:33:26 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

2026-05-06 12:33:26 +02:00

Owner

Originally created by @VID-PRO on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1178

Originally assigned to: @maziggy on GitHub.

Component

SpoolBuddy

Bug Description

The Raspberry Pi CPU temperature is allways around 70°C.
This is too high. it should be between 40 and 60°C

This is due to a high load.

I have passive heatsinks attached, but that is not enough

Expected Behavior

it should be between 40 and 60°C

what heatsinks are required?
or do we need an active colling?

Steps to Reproduce

just let the spoolbuddy idle

Printer Model

Not printer-related

Bambuddy Version

0.2.4b1

SpoolBuddy Version

0.2.3.2

Printer Firmware Version

No response

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

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 @VID-PRO on GitHub (Apr 30, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1178 Originally assigned to: @maziggy on GitHub. ### Component SpoolBuddy ### Bug Description The Raspberry Pi CPU temperature is allways around 70°C. This is too high. it should be between 40 and 60°C This is due to a high load. I have passive heatsinks attached, but that is not enough ### Expected Behavior it should be between 40 and 60°C what heatsinks are required? or do we need an active colling? ### Steps to Reproduce just let the spoolbuddy idle ### Printer Model Not printer-related ### Bambuddy Version 0.2.4b1 ### SpoolBuddy Version 0.2.3.2 ### Printer Firmware Version _No response_ ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### 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 added the

feedback

bug

labels

2026-05-06 12:33:26 +02:00

BreizhHardware commented

2026-05-06 12:33:26 +02:00

Author

Owner

@maziggy commented on GitHub (May 1, 2026):

My Spoolbuddy runs with simple heat sinks the whole day with temps under 60°C.

temp=55.5'C

Do you used the Spoolbuddy install script?

@maziggy commented on GitHub (May 1, 2026): My Spoolbuddy runs with simple heat sinks the whole day with temps under 60°C. > temp=55.5'C Do you used the Spoolbuddy install script?

BreizhHardware commented

2026-05-06 12:33:26 +02:00

Author

Owner

@maziggy commented on GitHub (May 1, 2026):

Also do you set a display blanking timeout?

@maziggy commented on GitHub (May 1, 2026): Also do you set a display blanking timeout?

BreizhHardware commented

2026-05-06 12:33:26 +02:00

Author

Owner

@VID-PRO commented on GitHub (May 1, 2026):

Yes i used the install script.
Setting the blank time did nothing. Screen is allways on

@VID-PRO commented on GitHub (May 1, 2026): Yes i used the install script. Setting the blank time did nothing. Screen is allways on

BreizhHardware commented

2026-05-06 12:33:27 +02:00

Author

Owner

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

Setting the blank time did nothing.

Then there's something wrong. Please re-install from dev branch.

@maziggy commented on GitHub (May 2, 2026): > Setting the blank time did nothing. Then there's something wrong. Please re-install from dev branch.

BreizhHardware commented

2026-05-06 12:33:27 +02:00

Author

Owner

@maziggy commented on GitHub (May 6, 2026):

@maziggy commented on GitHub (May 6, 2026): ?