mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #823] [Feature]: Date / Time Schedule Print Farm Overview #552
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#552
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 @sanjay2409 on GitHub (Mar 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/823
Originally assigned to: @maziggy on GitHub.
Problem or Use Case
1 Day View - 2 Day View.
Running Schedule Time Line to see when the prints are due to be finished.
Proposed Solution
There was a timeline view:
What prints are due next. What timeslot that falls into. See screenshot below.
Also a Push notification - print due to be finished in XYZ Time, (XYZ = 5mins - 10mins - 20mins.
Alternatives Considered
No response
Feature Category
Monitoring & Stats
Priority
Critical for my use case
Mockups or Examples
Contribution
Checklist
@maziggy commented on GitHub (Mar 28, 2026):
Yup, this is already on my list: re-design of the queue page. Let me see what I can do.
@sanjay2409 commented on GitHub (Mar 28, 2026):
Thanks. Not sure if this is part of the que page or schedule overview.
It would be nice at a glance to know ETA when I need to be back in the studio for the machines. Like a daily planner style. For example screen shot. I need to be back at the printers for approx 10am and 11:30am
@maziggy commented on GitHub (Mar 28, 2026):
Available/Fixed in branch dev and available with the next release or daily build. Please let me know if ot works for you.
Docs -> wiki.bambuddy.cool/features/print-queue/?h=time#timeline-view
@sanjay2409 commented on GitHub (Mar 28, 2026):
Unfortunately not working. I have two printers paused for a change over of filament. Nothing showing in the timeline.
@maziggy commented on GitHub (Mar 29, 2026):
And the prints were started via a schedule queue item?
@sanjay2409 commented on GitHub (Mar 29, 2026):
No. Not started. They were already running from the farm.
My thoughts or understanding... Is that the information in the printers dashboard will pull the information (ETA finish time, time remaining, progress bar (on/off))
It's the ETA finish time that dictates where it falls within the hour block of the daily view.
That's my thought process. Just a pull of information that's readily available, like a calendar overview. Regardless of how the prints are set up.
@maziggy commented on GitHub (Mar 29, 2026):
I think you need to explain it more detailed.
@sanjay2409 commented on GitHub (Mar 29, 2026):
So I set up prints in the studio or like any other farm.
I get on with other things and not always near the studio.
I get that there is notifications. And I have set that up.
But it would be good to have a calendar overview. That shows hours down the side. Showing in the hours (like a Google calendar day view/schedule view).
The only information here is what printers and prints are finishing in that hour.
For example if
Racking 3,4 and 5 have prints on and they all finish at 3pm
Then they would show up in the 3pm hour block.
I would know to be back in the studio for 3pm to clear the beds and start the next batch.
Racking 6,7 may finish at 5pm.
So I would return back to the studio at 5pm.
Screenshot of example attached.
Info is being pulled from ETA finish print time.
On the home dashboard in the top right you have next printer available in XXX HOURS. As it's almost finished. It's almost like that but a calendar day/schedule view
@maziggy commented on GitHub (Mar 30, 2026):
That differs from your feature request description. To avoid confusion, please open a new feature request and explain your desired workflow as detailed as possible.