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

[GH-ISSUE #298] [Feature]: Support other printer manufacturers #186

Closed
opened 2026-05-07 00:07:11 +02:00 by BreizhHardware · 3 comments

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

  • 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 @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 - [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-07 00:07:11 +02:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

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

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

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

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

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

<!-- gh-comment-id:3877583653 --> @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.
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-maziggy-1#186
No description provided.