starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #980] [Bug]: Virtual Printer not connecting to latest Bambu Studio 2.5.3.61 #683

New issue

Closed

opened 2026-05-07 00:12:45 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:12:45 +02:00

Owner

Originally created by @PurseChicken on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/980

Originally assigned to: @maziggy on GitHub.

Bug Description

I was prompted today to update Bambu Studio to the latest version. I updated as prompted and afterwards, I can no longer connect to a Proxy Printer in bambuddy. I get the ambiguous -1 error (Connect Failed! Code =-1).

I enabled debug mode and attempted to connect twice. Once by just clicking the printer in the list and next by attempting to add it new again. Attached is the debug log if its helpful.

Expected Behavior

Everything should work with the latest Studio version.

Steps to Reproduce

Go to device tab in latest bambu studio.
Attempt to connect to a Proxy Printer
Observe failure.

Printer Model

P1S

Bambuddy Version

v0.2.3b3

Printer Firmware Version

01.10.00.00

Installation Method

Other

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
My printer has Developer Mode enabled

Originally created by @PurseChicken on GitHub (Apr 14, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/980 Originally assigned to: @maziggy on GitHub. ### Bug Description I was prompted today to update Bambu Studio to the latest version. I updated as prompted and afterwards, I can no longer connect to a Proxy Printer in bambuddy. I get the ambiguous -1 error (Connect Failed! Code =-1). I enabled debug mode and attempted to connect twice. Once by just clicking the printer in the list and next by attempting to add it new again. Attached is the debug log if its helpful. ### Expected Behavior Everything should work with the latest Studio version. ### Steps to Reproduce Go to device tab in latest bambu studio. Attempt to connect to a Proxy Printer Observe failure. ### Printer Model P1S ### Bambuddy Version v0.2.3b3 ### Printer Firmware Version 01.10.00.00 ### Installation Method Other ### Operating System Linux (Other) ### Relevant Logs / Support Package <REMOVED> ### 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 - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:12:45 +02:00

closed this issue
added the
invalid
label

BreizhHardware commented

2026-05-07 00:12:46 +02:00

Author

Owner

@PurseChicken commented on GitHub (Apr 14, 2026):

Not sure if its normal, but Studio reaches the bind server on :3002, completes the detect exchange, then disconnects ~1s later and never proceeds to bind/MQTT. No retry, no TLS error logged — it just walks away.
From bambuddy.log:

12:31:02,820 bind_server: client connected from <studio>:60762
12:31:02,823 bind_server: received: {'login': {'command': 'detect', 'sequence_id': '20002'}}
12:31:02,823 bind_server: sent detect response (serial=<...>)
12:31:03,825 bind_server: client <studio>:60762 disconnected

My guess is Studio's updated client is now validating something in the detect response it previously accepted — possibly stricter checks on the dev_ip, serial format, model code, or a new field it now expects. Would be worth diffing the detect response payload against what current Studio expects.

@PurseChicken commented on GitHub (Apr 14, 2026): Not sure if its normal, but Studio reaches the bind server on :3002, completes the detect exchange, then disconnects ~1s later and never proceeds to bind/MQTT. No retry, no TLS error logged — it just walks away. From bambuddy.log: ``` 12:31:02,820 bind_server: client connected from <studio>:60762 12:31:02,823 bind_server: received: {'login': {'command': 'detect', 'sequence_id': '20002'}} 12:31:02,823 bind_server: sent detect response (serial=<...>) 12:31:03,825 bind_server: client <studio>:60762 disconnected ``` My guess is Studio's updated client is now validating something in the detect response it previously accepted — possibly stricter checks on the dev_ip, serial format, model code, or a new field it now expects. Would be worth diffing the detect response payload against what current Studio expects.

BreizhHardware commented

2026-05-07 00:12:46 +02:00

Author

Owner

@PurseChicken commented on GitHub (Apr 14, 2026):

Well i am the ID10T. I totally forgot about the bambuddy certificate. Latest studio overwrote the cert, so i had to add it back. Once i did this everything worked as expected. My apologies!

@PurseChicken commented on GitHub (Apr 14, 2026): Well i am the ID10T. I totally forgot about the bambuddy certificate. Latest studio overwrote the cert, so i had to add it back. Once i did this everything worked as expected. My apologies!

BreizhHardware referenced this issue

2026-05-07 00:16:00 +02:00

[PR #693] [MERGED] Feature: Advanced Authentication User Email Notifications #1099