Trevor Mack

yeah that sounds fine by me, I'd guess the payloads are a bit different

Besides labeling fermentation sessions it would be great if we could associate sessions with "batches" (BrewFather language). This way for a specific brew batch we could link: 1) brew session(s)...

Yeah even in the Pico device brewing code there is a bunch of duplicate code. The API contracts are all separate, but the underlying data representation could be refactored, but...

@marcchabot do you have or know how to get access to any of the server logs to see if there was a server error that might have created this scenario?...

Also what is the firmware version that is reported on your Still?

No the pico machines don't validate certificates... and only the Z actually even uses https (though still doesn't validate certificate). This stupidity by PB allows us to take advantage of...

``` Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings ``` That is just a warning that we...

Don't see anything in the request log that would result in that. Though will do some local testing to see if I can reproduce at all.

@chrisscott let me know how I can help. Basically we have a single "routes.py" file per device series to keep things manageable. Model.py is where all the "models" are stored....

I'd recommend restarting the PicoStill and Z at least once and see if this experience persists. Did you try that by chance? I haven't had time to get the Still...