mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #888] [Feature]: Remove Developer LAN mode is not enabled banner #608
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#608
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 @nicktags on GitHub (Apr 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/888
Originally assigned to: @maziggy on GitHub.
Problem or Use Case
Not a problem, but is there a way to remove this?
Proposed Solution
Option to acknowledge and not have it pop up again.
Alternatives Considered
No response
Feature Category
Monitoring & Stats
Priority
Nice to have
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Apr 4, 2026):
Yes, enable developer mode. It's a requirement.
@nicktags commented on GitHub (Apr 4, 2026):
That's a shame. Not all of us want to enable developer mode. For anyone that finds this, I was able to remove the banner with AdBlock.
@maziggy commented on GitHub (Apr 4, 2026):
It's not a shame, it's a requirement of Bambuddy!
Can you imagine how many issues we receive, because developer mode is not enabled? That is generating lots of work on our side. So calling it a shame is certainly not appropriate.
@nicktags commented on GitHub (Apr 4, 2026):
Fair. It's working perfectly fine for me with developer mode disabled. I'm not asking to completely remove that banner. Just not make it persistent. Have user check a box that they acknowledge and not have it come back. What functionality am I missing by having it disabled?
@maziggy commented on GitHub (Apr 4, 2026):
From the docs.
@nicktags commented on GitHub (Apr 4, 2026):
For me that's perfect. I only want it to have read access. What I dont want is to lose the ability to use Bambu studio/app.
@maziggy commented on GitHub (Apr 4, 2026):
Yes, I understand, but this is not the intention of Bambuddy.
@piitaya commented on GitHub (Apr 7, 2026):
Hi @maziggy, sorry for jumping straight into a PR (#908) without following the contribution rules.
I'd like to share my interest in this feature. I use Bambuddy purely for monitoring and filament tracking, and it works perfectly for my setup without developer mode. I actually prefer it over Spoolman because of the sub-type support and better filament naming.
I fully understand the support burden concern, would you reconsider if the toggle were opt-in, hidden in settings, and gated behind an explicit acknowledgment that some features may not work and that related issues won't be accepted (e.g. in a confirmation dialog).
Thanks for all your work on Bambuddy.
@bemble commented on GitHub (Apr 7, 2026):
Hi @maziggy, I share @piitaya use case.
I moved from Spoolman for the all-in-one spool inventory and tracking with my Bambu printer, that Bambuddy does super well, thanks for that.
That’s the only thing I use in Bambuddy, and I don’t need to switch my printer in local mode for that, and I don’t want to switch my printer to local mode just to get rid of this header, I have more to loose; I’m not the only user of my printer and other households are using the app, for example.
@maziggy commented on GitHub (Apr 7, 2026):
That's not the purpse of Bambuddy and in the past we saw many weird issues when developer mode was not enabled. So this is a requirement ti run Bambuddy and therefore we will not remove the warning.
@piitaya commented on GitHub (Apr 7, 2026):
Understood, thanks for the clear answer. Bambuddy isn't quite the right fit for my setup then, but thanks for all your work on it!