Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to schedule when the kiln starts #59

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mburazin
Copy link

@jbruce12000 I implemented this PR in cooperation with my friend @marktilles who had this idea for the delayed start of the kiln and has been in contact with you previously. What follows is the description of this implementation.

This PR adds the possibility to use a datepicker in the modal after clicking the start button to schedule when the kiln should start running by itself automatically followed by clicking the newly created appropriate button.

Screenshot 2021-12-17 at 22 33 04

The timer is implemented in the backend and the start is triggered there so closing or refreshing the browser does not stop it.

When the kiln start gets scheduled, the frontend state changes so that the glowing timer icon is now shown instead of the
previously unused door icon (hope that's ok). The state is also displayed as SCHEDULED and above it the info states when it's due to start: "Start at: ..."

Screenshot 2021-12-17 at 22 33 26

Now this state is shown whenever the page is opened in the browser until the kiln starts running. To cancel the scheduled run, one just needs to click the "Stop" button in the same way as when stopping the running kiln.

Would appreciate if you and anyone else could review and test this. Any feedback is welcome and I can make changes as needed.

This adds the possibility to use a datepicker in the modal after
clicking the start button to schedule when the kiln should start
running by itself automatically.
The timer is implemented in the backend and the start is triggered
there so closing or refreshing the browser does not stop it.
In the state when it's "waiting to start", the frontend state
changes so that the glowing timer icon is now shown instead of the
previously unused door icon. The state is also displayed as
SCHEDULED and above it the info states when it's due to start:
"Start at: ..."
@jbruce12000
Copy link
Owner

Interesting. I've always done this through the api, using cron or at to start the job.

@koboldgn
Copy link

@mburazin I will be happy to help you test if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants