I could be mistaken, but back when I was building the iSpindel support I don't think that the message payload included a device-calibrated gravity. I'm working on rebuilding gravity support for Fermentrack 2 -- if it includes one now, I can definitely add that as an option.
Fermentrack: Fermentation monitoring & BrewPi-www Replacement for Raspberry Pi
- Thread starter Thorrak
- Start date
Help Support Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum:
Hey there - I apologize for the delayed response on this one -- we're in the process of moving, and due to a combination of poor timing and other life changes are having to effectively move four separate times over a month and a half. You happened to post this right as we were working through the first leg of the moves, but I'm hoping to have everything back to normal by late May.
Unfortunately, periodic "cannot receive LCD text" errors are what prompted the rewrite of the BrewPi-Script daemon early last year which is also what prompted the development of Fermentrack 2. I don't have a good solution for Legacy Fermentrack, but should have a solution for Fermentrack 2 to use Arduinos (and serial-connected devices) within the next few months. This is the feature I'm working on next after gravity support.
How do I Create a New Beer Profile and have the current beer temperature, be a variable number, as Set Point 1, and say add 6 degrees over the next 2 days?
I do not want to keep creating new beer profiles, with 0s (zero seconds, or the current temperature) being the first start set point that I must say what it is, and then the second point would be 2d (2 days) X+6 degrees. I just want the new profile to see what the current temperature is, on its own, and + or - degrees over set days.
In the past, I kept creating new Beer Profiles, with whatever the current temperature of the beer that is now fermenting, having to define this temperature as Set Point 1 - 0s.
I do not want to keep creating new beer profiles, with 0s (zero seconds, or the current temperature) being the first start set point that I must say what it is, and then the second point would be 2d (2 days) X+6 degrees. I just want the new profile to see what the current temperature is, on its own, and + or - degrees over set days.
In the past, I kept creating new Beer Profiles, with whatever the current temperature of the beer that is now fermenting, having to define this temperature as Set Point 1 - 0s.
At the moment, there aren't variable setpoint beer profiles, but I was thinking of creating something like this as a "cold crash now" button for the end of fermentation. Is that what you're trying to do, or are you thinking of doing this at the start of fermentation? (If so, is your beer temperature really that variable at the start? Do you no-chill or something?)
This is, at or near the end! I just want the profile to see what the exact current temp is, and either warm up to get the last gravity points out (or diacetyl clean up), or cool down (or crash). I just dont want to look at what the exact current temperature is ..... then create a New Profile, defining this as the start point, and then the second point would be + or -
EXACTLY, @Thorrak ! "cold crash now" OR warm up NOW, button, will prevent having to make a new beer profile. This new button will insert an add-on Profile, that picks up at current temperature. Therefore, no need for anyone to manually look at the current temperature, make this set point 1, and then setpoint 2.... would be your crash or accelerated warm-up.
Thanks!
Or just being able to hold a temp until I want to trigger the next step of a profile, like for a diacetyl rest after fermentation slows. 
Yes, but this is a little easier to do - Just turn off Profile and then Set Beer Constant temperature.Or just being able to hold a temp until I want to trigger the next step of a profile, like for a diacetyl rest after fermentation slows.
So much labor went into this project from John, @Thorrak , me crying about a quicker way to accomplish something, makes me wonder if he needs to send me a bill..
Agreed! And @Thorrak has repeatedly rejected my offers to contribute to help him cover at least his out of pocket expenses. He is truly a generous soul, and I hope to at least send him a couple beers after he gets settled in his new house!So much labor went into this project from John, @Thorrak , me crying about a quicker way to accomplish something, makes me wonder if he needs to send me a bill..
As it is, I usually break up each profile into several smaller profiles because it's hard to know exactly when I want to start to ramp up for a diacetyl rest or starting a cold crash. I know that he hopes to make it so a Tilt can trigger different steps of a profile eventually, but I hadn't really considered a way to manually trigger each step until he mentioned adding a "Cold Crash Button". It would save having so many profiles if there was a way to have a complete profile that included "stop points" that require a trigger (whether manual, or by Tilt reading) to continue to the next set point.
I think Thorrak appreciates peoples ideas and input, and knows he's free to use or discard suggestions as he sees fit. I'm sure that Fermentrack wouldn't be what it is, if not for him taking the ideas that knuckleheads like me throw at him and making them work
I am doing the same "thing". I have way more Profiles than beers I brewed, hoping one of the Profiles will fit my Cold Crash or Diacetyl cleanup.Agreed! And @Thorrak has repeatedly rejected my offers to contribute to help him cover at least his out of pocket expenses. He is truly a generous soul, and I hope to at least send him a couple beers after he gets settled in his new house!
As it is, I usually break up each profile into several smaller profiles because it's hard to know exactly when I want to start to ramp up for a diacetyl rest or starting a cold crash. I know that he hopes to make it so a Tilt can trigger different steps of a profile eventually, but I hadn't really considered a way to manually trigger each step until he mentioned adding a "Cold Crash Button". It would save having so many profiles if there was a way to have a complete profile that included "stop points" that require a trigger (whether manual, or by Tilt reading) to continue to the next set point.
I think Thorrak appreciates peoples ideas and input, and knows he's free to use or discard suggestions as he sees fit. I'm sure that Fermentrack wouldn't be what it is, if not for him taking the ideas that knuckleheads like me throw at him and making them work
This Software would cost a lot of money if only sold to whoever had the money! If you look at the commercial control systems, they don't do anything much better than Fermentrack or BrewPi. Really have to thank the recent programmers that are keeping this alive - @LBussy and @Thorrak !!
I don't think my problem is a Fermentrack one but there might be some ideas.
I live remotely so have 4G home broadband. The LTE router has most configurable settings hidden by the provider (no help there). Router is connected to a switch and then three wireless Access Points by cable. One is in the shed I ferment my beer (very, very cheap AP, only bought for intermittent use).
I built two controllers with what I had to hand. One esp8266, one esp32. The former works fine.
The esp32 built controller works fine connected to AP in the house. Connected to AP in brew shed it counts down from nine minutes "cooling starts in..." until it reaches five minutes and then resets - loses contact, reconnects, starts counting down from nine minutes again. Repeat ad infinitum.
I tried reflashing, resetting, restarting etc. Any ideas welcome. Is the solution likely to be a new AP, rebuild with esp8266? I don't want to give up on it too fast.
I live remotely so have 4G home broadband. The LTE router has most configurable settings hidden by the provider (no help there). Router is connected to a switch and then three wireless Access Points by cable. One is in the shed I ferment my beer (very, very cheap AP, only bought for intermittent use).
I built two controllers with what I had to hand. One esp8266, one esp32. The former works fine.
The esp32 built controller works fine connected to AP in the house. Connected to AP in brew shed it counts down from nine minutes "cooling starts in..." until it reaches five minutes and then resets - loses contact, reconnects, starts counting down from nine minutes again. Repeat ad infinitum.
I tried reflashing, resetting, restarting etc. Any ideas welcome. Is the solution likely to be a new AP, rebuild with esp8266? I don't want to give up on it too fast.
Which esp32. I had all sorts of issues with an S2 mini build freezing up etc a while back and have been just fine with the classic d1 mini esp8266 instead. I haven’t tried the a S2 again in a while cause I’ve been busy.
It's a generic esp32S. WROOM-32 development board. 32 pins. Like these.
You think I should rebuild with esp8266 and not bother with esp32? I quite liked the idea of having a display, not that it would be that much use in a shed.
https://www.amazon.co.uk/ESP-32S-Development-Bluetooth-Microcontroller-ESP-WROOM-32/dp/B08DR5T897/ref=mp_s_a_1_2_sspa?crid=3FSRI87Q15L49&dib=eyJ2IjoiMSJ9.GuBsuGdyJnZWjhrahsw5gXBTSu6AoPpBOCuSqDkMDsasIDDQgCX18UdkzIQPjmgDKuZ_eAnfgRbrRFEjpMM9y-yPTyhD4IS0x_3-t9wWiQtqYyrYH4aNvl5OAehNDakVmi_3N-nQDtSPPuxi0hxYTRfOF2GHsDG39zS1vAZVsOWt0aRwyhqJbyv9FRCwX8auBihqtAYQ-S1NVqmtjipHNQ.kEc16YysO-G8Iwu6ta_EPdzYu7K1r3Xo6poHACFs9gs&dib_tag=se&keywords=esp32+development+board&qid=1717920582&sprefix=esp32,aps,259&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9waG9uZV9zZWFyY2hfYXRm&psc=1
You think I should rebuild with esp8266 and not bother with esp32? I quite liked the idea of having a display, not that it would be that much use in a shed.
https://www.amazon.co.uk/ESP-32S-Development-Bluetooth-Microcontroller-ESP-WROOM-32/dp/B08DR5T897/ref=mp_s_a_1_2_sspa?crid=3FSRI87Q15L49&dib=eyJ2IjoiMSJ9.GuBsuGdyJnZWjhrahsw5gXBTSu6AoPpBOCuSqDkMDsasIDDQgCX18UdkzIQPjmgDKuZ_eAnfgRbrRFEjpMM9y-yPTyhD4IS0x_3-t9wWiQtqYyrYH4aNvl5OAehNDakVmi_3N-nQDtSPPuxi0hxYTRfOF2GHsDG39zS1vAZVsOWt0aRwyhqJbyv9FRCwX8auBihqtAYQ-S1NVqmtjipHNQ.kEc16YysO-G8Iwu6ta_EPdzYu7K1r3Xo6poHACFs9gs&dib_tag=se&keywords=esp32+development+board&qid=1717920582&sprefix=esp32,aps,259&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9waG9uZV9zZWFyY2hfYXRm&psc=1
Last edited:
Out of curiousity, which version of the firmware are you working with? Does it happen to be one of the the v16 alphas?
And, uh, exactly how remote is this brew shed?
And, uh, exactly how remote is this brew shed?
Version is BrewPi-ESP32 - WiFi I2c Display, v15d, I have some I2c displays, was thinking about using them but I don't have a box big enough to accommodate. Was wondering if the fact there isn't a display attached would cause problems but it works fine unless sited in the shed, which is where it should be 
The shed isn't particularly remote from the house, as sheds go. The house is in the Outer Hebrides.
The shed isn't particularly remote from the house, as sheds go. The house is in the Outer Hebrides.
Hmm, v15d surprises me. Have you tried the v16 alpha? While I can't think of anything that changed that would resolve the issues you describe, there are a bunch of updates to v16 that were targeted at connection stability, and might help here.
My expectation was that you were already on the v16 alpha. Due to a bug in Espressif's framework, to have Inkbird support enabled in the v16 alpha requires that I monitor for a loss of the bluetooth radio. If no bluetooth devices happened to be in range of the controller, it might have interpreted that as the radio locking up.
My expectation was that you were already on the v16 alpha. Due to a bug in Espressif's framework, to have Inkbird support enabled in the v16 alpha requires that I monitor for a loss of the bluetooth radio. If no bluetooth devices happened to be in range of the controller, it might have interpreted that as the radio locking up.
I'll give it a go. No harm trying, not wildly difficult, especially so given your impressive flashing tool. Better than trying to flash with Arduino IDE
I don't really want you to waste your time on this since I doubt it's a Fermentrack issue but the error log is here if you want to see it, this snippet of text is repeated over and over.
I don't really want you to waste your time on this since I doubt it's a Fermentrack issue but the error log is here if you want to see it, this snippet of text is repeated over and over.
Last edited:
