Trevor Mack

Sent up a PR for this experience see the linked PR for details

No import capability exposed via the web server yet so going to leave this ticket open. The export component was merged and is available via `/backup/recipes` and `/backup/sessions` which download...

No clue why there is a total in that column cotter as we explicitly request there not to be in tabular. That is strange. The temperatures yeah that is less...

No this has not been done. This would be a nice addition for the PicoFerm and iSpindel support that has been added. I can see this being a simple user...

Having a pull down of "previously archived" (non monitored fermentation session) brew sessions would be a great way to "link / name" a fermentation session. This same experience should be...

That is likely a resume issue on server restart. if fermentation session wasn't completed the new data logs should likely be pushed to the existing active file instead. Neither @chiefwigms...

Opened a separate issue to track that one. See https://github.com/chiefwigms/picobrew_pico/issues/151

@BuckoWA have a shot at it sure. I don't have an iSpindel so wasn't sure what the "start logging" vs "stop logging" signals were. It really doesn't look like there...

With an iSpindel do you just get a new brew graph every 14 days? Reading through `routes_iSpindel_api.py` that is what it looks like to me at least... that seems less...

@wiltdavi I'm guessing the tilt support should be almost a mirror of the iSpindle stuff especially if using the webhook approach, if going the bluetooth route would need to have...