mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #1105] [Bug]: developer mode detection broken #788
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#788
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 @m4rtini2 on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1105
Originally assigned to: @maziggy on GitHub.
Component
Bambuddy
Bug Description
The detection of the developer mode is sending false values.
After adding a printer i started a print and verified it was printing by opening the video stream.
Some time later i remotly checked if the print succsseded but the video stream was too dark. I toggled the light on but it did not turn on. The symbol on the page changed but the printer does not react.
When uploading a bug report from the main page the server included a settings file containing the info the developer mode is off. Which is not correct!
This error report got dissmissed as invalid even after posting pictures of the developer mode being turned on in the slicer and was closed before i could upload pictures from the printer proving the devloper mode is was turned on.
Expected Behavior
The light should turn on.
Steps to Reproduce
1 Add a printer
2 print some thing
3 wait untli light turns off
4 click the light on symbol
5 watch the printer
Printer Model
H2C
Bambuddy Version
0.2.3.2
SpoolBuddy Version
No response
Printer Firmware Version
01.01.02.00
Installation Method
Other
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
No response
Screenshots
Additional Context
Developer mode is enabled on the printer and in Bambulab Studio.
BamBuddy was installed with a helper script from https://community-scripts.org/ in an LXC on the Proxmox hypervisor.
Checklist
@maziggy commented on GitHub (Apr 23, 2026):
Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@m4rtini2 commented on GitHub (Apr 23, 2026):
Its allready here https://github.com/maziggy/bambuddy/issues/1100
[edited wrong reference]
The same from collected now
bambuddy-support-20260423-195656.zip
@maziggy commented on GitHub (Apr 23, 2026):
Bambuddy cannot connect to your printer at all.
So obviously the printer is reachable via the network, but the printer doesn't accept any connection from Bambuddy. The only reason for this, that comes to my mind, is: developer mode is not enabled.
Since we have no data.....
@m4rtini2 commented on GitHub (Apr 23, 2026):
I can stream a video by clicking the camera icon. With the room light on i can see a clear picture.
When i turn the printer off it is shown as offline, when its turned on it shows connected OK OK door closed.
The printer is from January 2026, serial number starts with 31B8BP...
somtimes it drops connection for a second and shows offline, file manager works
@maziggy commented on GitHub (Apr 23, 2026):
BL obviously introdcued new serial numbers for the H2C. Need to add a new serial prefix.
@m4rtini2 commented on GitHub (Apr 23, 2026):
I did not enter the real serial number in the printer profile. But i tried a second profile with the original serial number and it did not connect correctly either. I wish bambuddy would connect to the printer without real device serial number. Just with ip and access code, like bambustudio.
@maziggy commented on GitHub (Apr 24, 2026):
New serial prefix was added. Available/Fixed in branch dev and available with the next release or daily build.
Looked at the support package — the symptom isn't a developer-mode detection bug, it's that the MQTT connection is successful but your printer never publishes anything on the topic Bambuddy is subscribed to. The log shows a clean 60-second loop of: connect → subscribe to device//report → zero messages → stale timeout → reconnect →
repeat, forever. Because no report frames ever arrive, developer_mode stays null (unknown, not "off"), state stays "unknown", and firmware_version stays empty — the support-info values you saw are all just "we've had no data to populate these from."
Two things to check on the printer side:
@m4rtini2 commented on GitHub (Apr 24, 2026):
Thank you for clarifiyng the issue. I see this is a user error and apologize for the incorrect bug report. Please edit the title if helpful for documentation. I have not tested the dev branch but the connection works now. Here is what i did.
On the printer i have turned 'lan only' off and then on again, enabled 'developer-mode' and refreshed the access code. After that i turned the printer off and on.
Still on the 0.2.3.2 version in the 'printers' page i deleted the printer and added it again. This time i used auto-discovery, which i have overseen last time. The printer was found and after entering the access code i can see all the printer and ams information. Toggling light or configuring filaments in ams works.
@maziggy commented on GitHub (Apr 24, 2026):
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!