mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #301] [Bug]: MQTT disconnected #187
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#187
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 @twitchstick on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/301
Originally assigned to: @maziggy on GitHub.
Bug Description
My printer was added to Bambuddy but remains offline. LAN mode and Developer mode are enabled.
WARNING [backend.app.services.bambu_mqtt] [P1S Serial Number] MQTT disconnected: rc=Unspecified error, flags=DisconnectFlags(is_disconnect_packet_from_server=False)
Expected Behavior
It should connect and work.
Steps to Reproduce
Add P1S printer to Bambuddy
Printer Model
P1S
Bambuddy Version
0.1.8.1
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Linux (Other)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 8, 2026):
Please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@twitchstick commented on GitHub (Feb 8, 2026):
bambuddy-support-20260208-125736.zip
@maziggy commented on GitHub (Feb 8, 2026):
Show me the ouput of "docker compose exec bambuddy ping YOUR_PRINTER_IP"
@twitchstick commented on GitHub (Feb 8, 2026):
YES
YES
YES
docker run --rm --network=container:Bambuddy busybox ping 192.168.1.59
PING 192.168.1.59 (192.168.1.59): 56 data bytes
64 bytes from 192.168.1.59: seq=0 ttl=255 time=3.265 ms
64 bytes from 192.168.1.59: seq=1 ttl=255 time=2.114 ms
64 bytes from 192.168.1.59: seq=2 ttl=255 time=2.127 ms
64 bytes from 192.168.1.59: seq=3 ttl=255 time=5.788 ms
64 bytes from 192.168.1.59: seq=4 ttl=255 time=31.041 ms
64 bytes from 192.168.1.59: seq=5 ttl=255 time=8.466 ms
64 bytes from 192.168.1.59: seq=6 ttl=255 time=3.059 ms
64 bytes from 192.168.1.59: seq=7 ttl=255 time=2.164 ms
64 bytes from 192.168.1.59: seq=8 ttl=255 time=1.977 ms
64 bytes from 192.168.1.59: seq=9 ttl=255 time=39.727 ms
64 bytes from 192.168.1.59: seq=10 ttl=255 time=2.223 ms
^C
--- 192.168.1.59 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 1.977/9.268/39.727 ms
@twitchstick commented on GitHub (Feb 8, 2026):
I fixed it. I deleted and readded the printer. I didn’t scan the subnet this time. I manually added my printer and now it’s connected and working as expected.