[GH-ISSUE #301] [Bug]: MQTT disconnected #187

Closed
opened 2026-05-06 12:27:00 +02:00 by BreizhHardware · 5 comments

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

  • 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
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 ```shell ``` ### 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
BreizhHardware 2026-05-06 12:27:00 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@maziggy commented on GitHub (Feb 8, 2026):

Please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

<!-- gh-comment-id:3867729946 --> @maziggy commented on GitHub (Feb 8, 2026): Please attach a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
Author
Owner

@twitchstick commented on GitHub (Feb 8, 2026):

bambuddy-support-20260208-125736.zip

<!-- gh-comment-id:3867758038 --> @twitchstick commented on GitHub (Feb 8, 2026): [bambuddy-support-20260208-125736.zip](https://github.com/user-attachments/files/25163393/bambuddy-support-20260208-125736.zip)
Author
Owner

@maziggy commented on GitHub (Feb 8, 2026):

  • Printer is is Lan Only mode?
  • Developer mode is enabled on printer ?
  • Docker is using network mode host?

Show me the ouput of "docker compose exec bambuddy ping YOUR_PRINTER_IP"

<!-- gh-comment-id:3867907566 --> @maziggy commented on GitHub (Feb 8, 2026): - Printer is is Lan Only mode? - Developer mode is enabled on printer ? - Docker is using network mode host? Show me the ouput of "docker compose exec bambuddy ping YOUR_PRINTER_IP"
Author
Owner

@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

<!-- gh-comment-id:3868045283 --> @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
Author
Owner

@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.

<!-- gh-comment-id:3868151705 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#187
No description provided.