Fermentrack: Fermentation monitoring & BrewPi-www Replacement for Raspberry Pi

[bloombrews]

I assume you already know by the way, but SPINDELMATE is supported by/available within BrewFlasher.

YES!
I am just now setting up my first Spindelmate, and I am stuck trying to figure out how I can find my
8 chipher iBLOPPER
number (e.g."10278845") as username!.....
I am on Spindelmates, cloud login - ILTPILLHUB
I know this is not your project, and I did ask this question on that Forum, and waiting a reply. I was able to find this ID when I first set up your Tiltbridge, cloud data logging (after a few fishing around attempts, to find this...) But this is with another ESP32 board that is now in use on top of a fermentor, working great.
Thanks for the quick reply!

 

[Thorrak]

YES!
I am just now setting up my first Spindelmate, and I am stuck trying to figure out how I can find my
8 chipher iBLOPPER
number (e.g."10278845") as username!.....
I am on Spindelmates, cloud login - ILTPILLHUB
I know this is not your project, and I did ask this question on that Forum, and waiting a reply. I was able to find this ID when I first set up your Tiltbridge, cloud data logging (after a few fishing around attempts, to find this...) But this is with another ESP32 board that is now in use on top of a fermentor, working great.
Thanks for the quick reply!

Hopefully you get a reply there - I haven’t ever used it, and this isn’t the place to ask questions as it’s not supported in Fermentrack.

 

[Burnf16]

Generic Push Target question. After upgrading from v11 (to v14 and v15) generic push target is sending empty data, and only sending it one time after restarting the controller. Is anyone else having this issue?

Details:
I use Node Red running in a container on the same RPi as Fermentrack to receive data from the Generic Push Target. Node Red then sends data to Home Assistant running on a separate Pi via MQTT.

The issue I'm having is when I have v.14 (also v.15) firmware installed (on both 8266 and ESP32), data received by Node Red is empty:

{"api_key": "", "version": "1.0", "brewpi_devices": [], "gravity_sensors": []}

When I go back to v.11 on an 8266 it works normally. Any help is greatly appreciated!

 

[Thorrak]

Generic Push Target question. After upgrading from v11 (to v14 and v15) generic push target is sending empty data, and only sending it one time after restarting the controller. Is anyone else having this issue?

Details:
I use Node Red running in a container on the same RPi as Fermentrack to receive data from the Generic Push Target. Node Red then sends data to Home Assistant running on a separate Pi via MQTT.

The issue I'm having is when I have v.14 (also v.15) firmware installed (on both 8266 and ESP32), data received by Node Red is empty:

{"api_key": "", "version": "1.0", "brewpi_devices": [], "gravity_sensors": []}

When I go back to v.11 on an 8266 it works normally. Any help is greatly appreciated!

That’s… weird. Let me dig into the code.

 

[kdw2pd]

Is there a way for Fermentrack to capture iSpindel data from an iSpindHub repeater? I currently have my iSpindels connected to Fermentrack, and am having the well-known issue of not getting data out of SS fermenters. I know it supports TiltBridge, so wasn't sure if there was an iSpindel equivalent that could be used.

 

[bloombrews]

Is there a way for Fermentrack to capture iSpindel data from an iSpindHub repeater? I currently have my iSpindels connected to Fermentrack, and am having the well-known issue of not getting data out of SS fermenters. I know it supports TiltBridge, so wasn't sure if there was an iSpindel equivalent that could be used.

@Thorrak knows the answer, but I am sure if you link the Tiltbridge to your Fementrack, you will no longer have problems getting readings out of the Ss tanks. Although I am using two Tilts with the Tiltbridge (no repeater needed !!), I would expect the iSpindle to work just as good. Let us know if that works.

 

[kdw2pd]

@Thorrak knows the answer, but I am sure if you link the Tiltbridge to your Fementrack, you will no longer have problems getting readings out of the Ss tanks. Although I am using two Tilts with the Tiltbridge (no repeater needed !!), I would expect the iSpindle to work just as good. Let us know if that works.

Will a TiltBridge capture iSpindel data? I assumed not.

 

[Thorrak]

Will a TiltBridge capture iSpindel data? I assumed not.

It will not, unfortunately.

Is there a way for Fermentrack to capture iSpindel data from an iSpindHub repeater? I currently have my iSpindels connected to Fermentrack, and am having the well-known issue of not getting data out of SS fermenters. I know it supports TiltBridge, so wasn't sure if there was an iSpindel equivalent that could be used.

Probably! I haven’t tested it, but I think that it retains the same data format as the iSpindel, so it should work.

 

[RocketBrewer]

Hey @Thorrak, I did a guided tilt calibration, and it went well until I got to the end and got this message:
View attachment 816866

Hey @Thorrak, did you ever get a chance to look into what was going on with this issue?

 

[bloombrews]

HAPPY 5years old, BIRTHDAY!
A few days too late, but so is my brain....
THANKS @Thorrak !!!

 

[Derp]

Any idea what would cause the values in the second row to be empty? I have my chamber set to 40F (fridge constant), and it's maintaining the temperature, and the log data and LCD display show the correct temperatures.

After doing a fresh install after several years of rock-solid service, things have been a little unstable, but I thought I'd narrowed it down to an undervoltage problem. (My outlet's USB jack wasn't putting out enough power.)

How can I troubleshoot this problem?

 

[Thorrak]

The purple "Fridge Temp" panel, you mean?

 

[Derp]

The purple "Fridge Temp" panel, you mean?

Shouldn't the whole second row show the beer temp, fridge temp, control mode, and log interval?

 

[troyp42]

Hi guys, Ive been running to temp controllers with fermentrack for many years now. I washaving issues where every now and again my temp probe display would just disappear from the lcd screen and id get dashed lines instead so I eventually changed temp probes and that has finally ifxed the problem.
If I was to build a new temp controller using an esp32 board are the instructions exactly the same as using the esp8266? Also are there any advantages to using the ESP32 board?

 

[Thorrak]

Shouldn't the whole second row show the beer temp, fridge temp, control mode, and log interval?

Yeah, apologies - I was trying to confirm what you meant in this case by "second row".

To test it, you'll need to look at the URL for the dashboard to get the ID of your controller internal to Fermentrack. For example, if the URL is

http://192.168.1.X/devices/6/dashboard/

then you would need to make note of the number "6". Then, use this to craft the URL of the endpoint that provides this data which will be something like:

http://192.168.1.X/api/panel/6/

(but replacing "6" in this URL with your device's ID). Don't forget the trailing slash! Post what you see here, and I can likely see what is going on.

Hi guys, Ive been running to temp controllers with fermentrack for many years now. I washaving issues where every now and again my temp probe display would just disappear from the lcd screen and id get dashed lines instead so I eventually changed temp probes and that has finally ifxed the problem.
If I was to build a new temp controller using an esp32 board are the instructions exactly the same as using the esp8266? Also are there any advantages to using the ESP32 board?

The instructions are mostly the same, aside from the assembly of the PCB itself (which has slightly different components). The controller can be flashed using Fermentrack, BrewFlasher, or BrewFlasher Web (just like the ESP8266) and you can use the same set of hardware. The advantages to the ESP32 come from the ability to use additional hardware, as well as having a board that I plan to support into the future. For a full comparison, you can take a look here at the project documentation.

One thing to note -- the dream of the "solder free BrewPi" isn't here yet, as the ESP32's Bluetooth support doesn't yet fully work. Once Espressif releases the next version of the Arduino framework this is expected to be resolved, but that is still weeks/months away.

 

[Derp]

Yeah, apologies - I was trying to confirm what you meant in this case by "second row".

To test it, you'll need to look at the URL for the dashboard to get the ID of your controller internal to Fermentrack. For example, if the URL is

http://192.168.1.X/devices/6/dashboard/

then you would need to make note of the number "6". Then, use this to craft the URL of the endpoint that provides this data which will be something like:

http://192.168.1.X/api/panel/6/

(but replacing "6" in this URL with your device's ID). Don't forget the trailing slash! Post what you see here, and I can likely see what is going on.

Thanks for your help!

 

[troyp42]

The instructions are mostly the same, aside from the assembly of the PCB itself (which has slightly different components). The controller can be flashed using Fermentrack, BrewFlasher, or BrewFlasher Web (just like the ESP8266) and you can use the same set of hardware. The advantages to the ESP32 come from the ability to use additional hardware, as well as having a board that I plan to support into the future. For a full comparison, you can take a look here at the project documentation.

One thing to note -- the dream of the "solder free BrewPi" isn't here yet, as the ESP32's Bluetooth support doesn't yet fully work. Once Espressif releases the next version of the Arduino framework this is expected to be resolved, but that is still weeks/months away.

Thanks for the repsonse mate. That sounds interesting. Ill certainly give it a go and build a new controller with an esp32. Not because I need one, but because its fun to build.. Cheers

 

[ShaneB]

Yeah, apologies - I was trying to confirm what you meant in this case by "second row".

To test it, you'll need to look at the URL for the dashboard to get the ID of your controller internal to Fermentrack. For example, if the URL is

http://192.168.1.X/devices/6/dashboard/

then you would need to make note of the number "6". Then, use this to craft the URL of the endpoint that provides this data which will be something like:

http://192.168.1.X/api/panel/6/

(but replacing "6" in this URL with your device's ID). Don't forget the trailing slash! Post what you see here, and I can likely see what is going on.



The instructions are mostly trrhe same, aside from the assembly of the PCB itself (which has slightly different components). The controller can be flashed using Fermentrack, BrewFlasher, or BrewFlasher Web (just like the ESP8266) and you can use the same set of hardware. The advantages to the ESP32 come from the ability to use additional hardware, as well as having a board that I plan to support into the future. For a full comparison, you can take a look here at the project documentation.

One thing to note -- the dream of the "solder free BrewPi" isn't here yet, as the ESP32's Bluetooth support doesn't yet fully work. Once Espressif releases the next version of the Arduino framework this is expected to be resolved, but that is still weeks/months away.

Hey Thorrak,

Thanks for this project, you inspired me to buy a 3d printer to print out your BrewPi case, I'm currently printing (about 24hr print) the US Outlet case, any chance you can upload the .stl file for your new D32 Pro Case Lid? The one that uses the new TFT screen instead of the older LCD.

I can attest the prices you sell your cases for are very reasonable, it seems like the going rate is $10 setup fee + $5/hr + filament to have something printed. That would cost around $110 at the settings I'm printing at (0.4mm nozzle, 40% infill and about 50mm/sec print speed. I need to play with klipper and a 0.6mm nozzle to see if I can speed things up for future prints. So far PLA seems strong enough but I also got some PETG to play with at some point.

 

[gromitdj]

This one?

TiltBridge Case - D32 Pro /w TFT

I don't know that he has a version of fermentrack that works on the D32 Pro.

 

[ShaneB]

This one?

TiltBridge Case - D32 Pro /w TFT

I don't know that he has a version of fermentrack that works on the D32 Pro.

Here is the d32 pro pcb BrewPi-ESP32 - Partially Assembled PCB by Fermentrack on Tindie

I'm looking for the file to print this, it's the cover for the brewpi outlet box to support the d32 TFT screen.
https://www.tindie.com/products/thorrak/brewpi-case-lid-for-lolin-d32-pro-lcd-v111/
It should be easy to modify the existing lcd cover but I just got into 3d printing a few days ago and haven't attempted creating any designs yet.

Also I noticed the box I printed only has 2 standoffs for the esp32 pcb, but the pcb has 3 holes. Seems like the version on thingverse is older and the one on github v1.2 has 3 holes. I printed the older version on accident.

 

[Thorrak]

This one?

TiltBridge Case - D32 Pro /w TFT

I don't know that he has a version of fermentrack that works on the D32 Pro.

I do, actually -- but only recently (and the case has only existed as of two weeks ago!)

Here is the d32 pro pcb BrewPi-ESP32 - Partially Assembled PCB by Fermentrack on Tindie

I'm looking for the file to print this, it's the cover for the brewpi outlet box to support the d32 TFT screen.
https://www.tindie.com/products/thorrak/brewpi-case-lid-for-lolin-d32-pro-lcd-v111/
It should be easy to modify the existing lcd cover but I just got into 3d printing a few days ago and haven't attempted creating any designs yet.

Also I noticed the box I printed only has 2 standoffs for the esp32 pcb, but the pcb has 3 holes. Seems like the version on thingverse is older and the one on github v1.2 has 3 holes. I printed the older version on accident.

I just uploaded the updated files to Printables and at some point I'll push a commit to GitHub with the update as well.

 

[gromitdj]

Why is this news to me?

...Now I have to build one.

 

[Derp]

Thorrak,

Did you see the images I posted here?

https://www.homebrewtalk.com/thread...acement-for-raspberry-pi.649303/post-10261987
Any suggestions?

 

[Thorrak]

Thorrak,

Did you see the images I posted here?

https://www.homebrewtalk.com/thread...acement-for-raspberry-pi.649303/post-10261987
Any suggestions?

I did, and I apologize as I thought I had replied, but apparently hallucinated that.

No - I don’t know offhand why that would happen. The same IDs used to populate the list of controllers (and LCD) on the main controller list are the IDs used to query/populate things such as the panels on the device dashboards. It’s possible that something weird is going on somewhere where I used an ID in a way I shouldn’t, but that seems very odd as it’s not something that I would think possible.

You did post a screenshot briefly that had an error about a device ID not being found — is that something you see often, or was it a one-off?

 

[Derp]

You did post a screenshot briefly that had an error about a device ID not being found — is that something you see often, or was it a one-off?

I do, but I deleted the screenshot because I assumed it was referring to the Tilt device I'd powered off after fermentation was complete, and didn't want to muddy the waters.

 

[Thorrak]

You shouldn’t see any error messages up at the top like that just because a device is turned off. Those error messages relate to some kind of internal error relating to Fermentrack itself.

My guess is that the error message & your issues are related. Can you check the following to help debug? Feel free to PM the screenshots to me if you prefer.

1. Log into Fermentrack, and click the "gear" in the upper right.
2. Log in if necessary, and then click "Django Admin Panel"
3. Under "App" you should see "BrewPi Devices". Click that.
4. A list of your currently set up BrewPi devices should appear. Can you then post a screenshot of that list?
5. Up at the top, under "Django Administration" click "Home" to go back to the main admin page, and then click on "Gravity Sensors" under "Gravity"
6. You should see a list of your currently set up gravity devices. Can you take a screenshot of that list?

If you get error messages for any of the above, let me know. That is also helpful to debug

 

[Derp]

You shouldn’t see any error messages up at the top like that just because a device is turned off. Those error messages relate to some kind of internal error relating to Fermentrack itself.

My guess is that the error message & your issues are related. Can you check the following to help debug? Feel free to PM the screenshots to me if you prefer.

1. Log into Fermentrack, and click the "gear" in the upper right.
2. Log in if necessary, and then click "Django Admin Panel"
3. Under "App" you should see "BrewPi Devices". Click that.
4. A list of your currently set up BrewPi devices should appear. Can you then post a screenshot of that list?
5. Up at the top, under "Django Administration" click "Home" to go back to the main admin page, and then click on "Gravity Sensors" under "Gravity"
6. You should see a list of your currently set up gravity devices. Can you take a screenshot of that list?

If you get error messages for any of the above, let me know. That is also helpful to debug

I saw the "Unable to load device with ID 1" error at the top at when I rebooted the Pi, but it's gone now. I also have the "Cannot receive LCD text from Controller/Script" message. I also see multiple instances of the following in syslog. Is this normal?

Jun 11 23:17:17 fermentrack kernel: [450477.788008] w1_master_driver w1_bus_master1: Attaching one wire slave 00.a32400000000 crc b7
Jun 11 23:17:17 fermentrack kernel: [450477.792915] w1_master_driver w1_bus_master1: Family 0 for 00.a32400000000.b7 is not registered.
Jun 11 23:17:53 fermentrack kernel: [450513.601414] w1_master_driver w1_bus_master1: Attaching one wire slave 00.632400000000 crc 7d
Jun 11 23:17:53 fermentrack kernel: [450513.606645] w1_master_driver w1_bus_master1: Family 0 for 00.632400000000.7d is not registered.
Jun 11 23:18:39 fermentrack kernel: [450559.675376] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e32400000000 crc f1
Jun 11 23:18:39 fermentrack kernel: [450559.683633] w1_master_driver w1_bus_master1: Family 0 for 00.e32400000000.f1 is not registered.
Jun 11 23:19:27 fermentrack kernel: [450607.304825] w1_master_driver w1_bus_master1: Attaching one wire slave 00.132400000000 crc 85
Jun 11 23:19:27 fermentrack kernel: [450607.310168] w1_master_driver w1_bus_master1: Family 0 for 00.132400000000.85 is not registered.
Jun 11 23:20:13 fermentrack kernel: [450654.106537] w1_master_driver w1_bus_master1: Attaching one wire slave 00.932400000000 crc 09
Jun 11 23:20:13 fermentrack kernel: [450654.111807] w1_master_driver w1_bus_master1: Family 0 for 00.932400000000.09 is not registered.

I can search for other log events, if necessary.

Thanks for your help.

 

[Bago-0]

I have a Synology NAS and was wondering if Fermentrack could run on the Synology rather than a RaspberryPi.

 

[Thorrak]

I have a Synology NAS and was wondering if Fermentrack could run on the Synology rather than a RaspberryPi.

Yes, but I don’t recommend it.

That said, I actually run my primary instance of Fermentrack in a Synology NAS, so take that with a grain of salt.

The issue you’re going to face is that support depends on which NAS you have

 

[Bago-0]

Ok thanks. I should probably stick to the Raspberry Pi as it is working well and quit messing with things.