Closed — Consolidated into #237
The temporary profile lifecycle is now part of the Pour-Over Meticulous Machine Integration (#237).
The implementation will still produce a reusable TempProfileService class that future features (recipes, guest profiles, dev iteration) can consume — but it's scoped and delivered as part of the pour-over feature rather than as a standalone abstraction.
Original description preserved below for reference.
Description
Currently, the pyMeticulous API requires all profiles to be saved persistently to the Meticulous machine. There is no native way to run a profile temporarily without leaving it stored on the machine.
This feature would enable a "Temporary Profile Mode" on the Meticulous machine — allowing users to run one-off espresso profiles without cluttering the machine's profile storage with temporary configurations.
Suggested automated flow
- Create the profile on the machine (persists)
- Apply it (load as active)
- Start the shot
- Purge the brew cylinder upon completion
- Delete the profile after completion
Closed — Consolidated into #237
The temporary profile lifecycle is now part of the Pour-Over Meticulous Machine Integration (#237).
The implementation will still produce a reusable
TempProfileServiceclass that future features (recipes, guest profiles, dev iteration) can consume — but it's scoped and delivered as part of the pour-over feature rather than as a standalone abstraction.Original description preserved below for reference.
Description
Currently, the pyMeticulous API requires all profiles to be saved persistently to the Meticulous machine. There is no native way to run a profile temporarily without leaving it stored on the machine.
This feature would enable a "Temporary Profile Mode" on the Meticulous machine — allowing users to run one-off espresso profiles without cluttering the machine's profile storage with temporary configurations.
Suggested automated flow