mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #193] [Bug]: No connections possible after starting Bambuddy #118
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#118
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 @Cassiopeia1980 on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/193
Originally assigned to: @maziggy on GitHub.
Bug Description
Hello,
after starting Bambuddy, I can no longer connect to a printer (X1C, P1S) in the Bambu Studio slicer. The slicer displays the error message "code=-1". Other applications also lose their connection. If I stop Bambuddy, the problem is immediately resolved and everything connects again. What am I doing wrong?
Regards
Hallo,
nach dem Start von Bambuddy, kann ich mich nicht mehr mit einem Drucker (X1C, P1S) im Slicer Bambu Studio verbinden. Der Slicer gibt die Fehlermeldung "code=-1" aus. Auch andere anwendungen bekommen keine Verbindung mehr. Stoppe ich Bambuddy, ist das Problem direkt behoben und alles verbindet wieder. Was mache ich falsch?
Gruß
Expected Behavior
That a connection is possible.
Steps to Reproduce
Start Bambuddy
Connection immediately unavailable
Close Bambuddy
Connection immediately available
Printer Model
P1S
Bambuddy Version
v0.1.6b11
Printer Firmware Version
01.09.01.00 (P1S), 01.11.02.00 (X1C)
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
Screenshots
bambuddy-support-20260130-150643.zip
Additional Context
No response
Checklist
@maziggy commented on GitHub (Jan 30, 2026):
These are no debug logs.
Anyway....I can't find any errors in your logs. I don't think that this is Bambuddy related. The only thing which just came to my mind is, that the host running Bambuddy has the same IP address as the printer. At least the kind of defect would match.
@Cassiopeia1980 commented on GitHub (Jan 30, 2026):
The printers are located at 192.168.1.128 and 181 respectively, and Bambuddy at 192.168.2.35. There shouldn't be any interference.
@maziggy commented on GitHub (Jan 30, 2026):
Hmmmm....to be honest: I don't have a clue. Unfortunately.
Why shouldn't the printer lose it's network connectivity.....wait.....what does "Other applications also lose their connection" exactly mean? When Bambuddy is running, can you ping printer's IP address?
@Cassiopeia1980 commented on GitHub (Jan 30, 2026):
Sorry, we've misunderstood each other; the network connection remains. It's just that nothing can connect to the printer except Bambuddy. The slicer finds the printer, but it looks like it doesn't have a free connection slot.
@Cassiopeia1980 commented on GitHub (Jan 30, 2026):
Other current applications include Filaman, for example. This allows the spool to be loaded into the AMS. Yes, I can ping both printers.
@maziggy commented on GitHub (Jan 30, 2026):
I have really no idea. I'm sorry.
Bambuddy only subscribes to the MQTT stream, which is always sent by the printer. Doesn't matter if there are subscribers or not. So I couldn't think about anything in Bambuddy forcing this issue.
@IROKILLER commented on GitHub (Jan 30, 2026):
I don't know if that will help.
I'm currently having the same problem with my A1 printer not connecting to Bambustudio. I also had trouble getting Bambuddy to work before, until I discovered that I had a Docker container on the network using the same MQTT port that Bambuddy needs. I changed the port of the other container and suddenly it worked. I'm running Bambuddy on Unraid.
@Cassiopeia1980 commented on GitHub (Jan 30, 2026):
Okay, I found the problem. It's not Bambuddy. It's my need for control and Bambulab. I have a Panda Touch, Home Assistant, Filaman, BambuStudio, and now Bambuddy. Apparently, there's a connection limit. When I added Bambuddy, I exceeded the maximum number of connections. It was just a coincidence that it happened with Bambuddy. This means that if I disable one of the other systems, everything works normally. Thank you all so much for your help anyway.