mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #845] [Bug]: V2.2.2 - Printer Status switches between Online and Offline #573
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
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#573
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 @speedy764 on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/845
Originally assigned to: @maziggy on GitHub.
Bug Description
After the update from V.2.2.1 to V.2.2.2, the printer's status permanently switches between online and offline. The printer is definitely turned on. I have made a video about this.
Expected Behavior
I expect the correct status and a stable display.
Steps to Reproduce
I have no idea, as I cannot trace where the error originates from.
Printer Model
H2C
Bambuddy Version
V.2.2.2
Printer Firmware Version
V1.01.05.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
bambuddy-support-20260329-151847.zip
Screenshots
Additional Context
I have run a seconfd instance (same configuration) to follow the daily update, V.2.3.1. In in this version the issue is not occured. Seems to be only V.2.2.2.
Checklist
@maziggy commented on GitHub (Mar 30, 2026):
You MQTT connection is stale.
Please rebuild your Docker image from branch dev, or use the latest dail build. It includes a fix that may fix your issue. Please let me know. If it's still not working, please re-upload debug logs from new version and we'll investigate further.
@speedy764 commented on GitHub (Mar 31, 2026):
Problem was solved with a reboot of the VM and Docker container.