-
Notifications
You must be signed in to change notification settings - Fork 16
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 Support for Pico S/C/Pro machines #8
Comments
@chiefwigms According to the readme from https://github.com/chiefwigms/picobrew_pico you figured out the protocol for the Pico S/C/Pro, correct? I'd love to upstream these changes. |
@chiefwigms Looks like the Pico reads it's recipes as JSON.
|
Yep - i have the Pico S/C/Pro protocol (loosely documented in routes_api.py) The pico doesn't have a real recipe aspect - the server pushes down a string for each pack that lists each step. I added a feature where you can create your own recipe and act as though it were one of Pico's Paks. I used JSON for both session data & the recipe because it was nearly plug in for HighCharts (live session graphing and historical sessions) as well as creating custom recipes via Tabulator. PicoBrew doesn't have a recipe builder for the Pico.. Here's what a recipe looks like (similar to the zymatic): |
I see. I guess I will just make the Zymatic recipes available in the Pico string format then for now. |
I think it may still be worth supporting Pico Pro api endpoints just for delivering the cleaning "recipes" as well as data logging for a manual brew even if the true custom recipes can't be supported. If you are open to it I can look into what it would take and make a pull request if I'm successful. |
@dlgreenwald Sounds good. Good for it. Happy to accept PRs. |
Right now, the picobrew-server only supports the Zymatic machine protocol. It would be cool to support newer machines from the
Pico
family as well.The text was updated successfully, but these errors were encountered: