[GH-ISSUE #888] [Feature]: Remove Developer LAN mode is not enabled banner #607

Closed
opened 2026-05-06 12:31:20 +02:00 by BreizhHardware · 11 comments

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?

Image

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

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
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? <img width="512" height="97" alt="Image" src="https://github.com/user-attachments/assets/5158ed53-122c-4511-8c02-e14bd3e31210" /> ### 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 - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:31:20 +02:00
  • closed this issue
  • added the
    invalid
    label
Author
Owner

@maziggy commented on GitHub (Apr 4, 2026):

Not a problem, but is there a way to remove this?

Yes, enable developer mode. It's a requirement.

<!-- gh-comment-id:4187047627 --> @maziggy commented on GitHub (Apr 4, 2026): >Not a problem, but is there a way to remove this? Yes, enable developer mode. It's a requirement.
Author
Owner

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

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

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

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

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

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

@maziggy commented on GitHub (Apr 4, 2026):

From the docs.

Image
<!-- gh-comment-id:4187180518 --> @maziggy commented on GitHub (Apr 4, 2026): From the docs. <img width="833" height="182" alt="Image" src="https://github.com/user-attachments/assets/fc99adde-fa4e-4637-a1db-e6862b8318da" />
Author
Owner

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

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

@maziggy commented on GitHub (Apr 4, 2026):

Yes, I understand, but this is not the intention of Bambuddy.

<!-- gh-comment-id:4187185304 --> @maziggy commented on GitHub (Apr 4, 2026): Yes, I understand, but this is not the intention of Bambuddy.
Author
Owner

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

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

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

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

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

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

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

<!-- gh-comment-id:4198315972 --> @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!
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#607
No description provided.