mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #298] [Feature]: Support other printer manufacturers #185
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#185
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 @jhf2442 on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/298
Problem or Use Case
as the name states, bambuddy is focussing on Bambu printers. While few features only make sense on bambu printers, most of the app can also enable print farms with different printer brands (e.g. Prusa) or mixed setups: archives, queues,
Proposed Solution
For Prusa, there is PrusaLink that allows to send gcode to a printer on the local network, quite similar to Bambu's implementation.
Would be willing to implement and test (we have multiple prusa printers in our local fablab)
Alternatives Considered
No response
Feature Category
Print Archiving
Priority
Nice to have
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Feb 8, 2026):
The question is: who would maintaining the Prusa part of the code long term? As we are implementing new Bambuddy features, this may also affect the Prusa part of the code.
@atl285 commented on GitHub (Feb 8, 2026):
I thought about support of other printers too! For example support of Klipper printers. The question is, are there real features, which only are available for Bambu Lab printers? And how is the logic of the code designed? Maybe it would be possible, if the printer support is modular, so that a module for another type of printer, e.g. Prusa, could communicate via an plugin type interface.
For me it's not clear at the moment, where the project does going. I like it, but I watching at the moment. The only function, which makes sense for me at the moment is the archive of prints and the nice statistics.
@maziggy commented on GitHub (Feb 10, 2026):
I don't think that this is something for the current stage of Bambuddy. You never know what happens, but for now it is not going to happen.