mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #1020] [Bug]: Spoolbuddy won't turn off lcd display #716
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#716
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 @hibikipr on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1020
Originally assigned to: @maziggy on GitHub.
Bug Description
after updating to v0.2.3b3 the LCD won't go to sleep. I understand the css blackout got replaced with functionality to turn off the actual lcd, but that is not working. have run the install script again and reboot but the screen stays on forever.
have also updated to the daily builds to see if there is any difference on this behavior. Currently at daily of v0.2.3b4
Expected Behavior
LCD turns off after configured timeout.
Steps to Reproduce
on SpoolBuddy - go to settings -> Display
set desired screen blank timeout.
restart pi
screen stays on all the time
Printer Model
H2C
Bambuddy Version
v0.2.3.b4
Printer Firmware Version
01.01.05.00
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
No response
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Apr 18, 2026):
Huh?
@hibikipr commented on GitHub (Apr 18, 2026):
it started not working with v0.2.3b3 since it doesn't do screen blackout anymore. still present in the daily builds of v0.2.3.b4
@maziggy commented on GitHub (Apr 18, 2026):
I'm using it all day with 0.2.3b4 without any issues.
Check the logs.
@hibikipr commented on GitHub (Apr 18, 2026):
will do - thanks
@maziggy commented on GitHub (Apr 18, 2026):
Let me know your findings.
@TravisWilder commented on GitHub (Apr 19, 2026):
can not see any issues on current dev 0.2.4b1