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

Edit: Disregard... for some reason I read your post as being that it worked when rotating one direction but not the other (even though you clearly explained it doesn’t work rotating either direction). Sorry about that!

If you have another encoder I would give it a try. Otherwise, hopefully someone with experience with builds that incorporate an encoder might have seen this in the past and can opine.

 

It seems exceedingly unlikely with all of the BrewPi success out there (not to mention Arduino temperature projects) that all of a sudden they are not capable of supporting 5V.

 

And yet, 4 of the 6 I currently have soldered up don't seem to work...

 

It’s obviously the common element.

Your soldering.

 

Just look at this beautiful soldering job:

Is that a blob of solder running over the edge of the edge of the PCB? Heck yeah it is!

 

I have (counts fingers) five BrewPi Bluetooth minions running with CadiBrewer shields so it's not likely the pcbs that are the problem.
I would make sure all of the pull-up resistors are in place, and that there's no solder bridging between the encoder header pins.
Also, I use bare encoder switches; some have used encoders with small PCBs attached but often those have resistors included that may not be helpful.

Finally, make sure the encoder is getting a GND connection to the "rotary" side as well as the "pushbutton" side. The whole works depends on the encoder/pushbutton grounding signals while relying on pull-up resistors to re-establish "high" levels...

Cheers!

 

The bigger the blob the better the job

 

Hello,

I'm very interested in this project and I'm fairly new to the world of Linux. I'm wanting to learn more about it, and I thought this might be a good way to do so, but a lot of this is making my head spin on how to go about this project. So I apologize if this has been asked before, but will this work with raspberry pi 4? Are there any suggestions on which hardware is 'best' or most supported? It looks like you can use just the pi and your hydrometer of choice, but I wasnt sure if it's suggested to use the E8266 instead for any reason other than multiple chamber support. I appreciate any help!

 

Is there anything special I need to do on my Pi to get Fermentrack to see my Tilt hydrometer? I've added my Tilt into my dashboard, but no readings yet. My Pi has bluetooth, currently paired to my Arduino controller. I had to manually pair it to the Pi to get Fermentrack to see it properly, do I need to do the same for the Tilt?

 

No, Fermentrack should be able to pick-up the tilt via Bluetooth and no Pi changes are needed.

Is your Fermentrack Pi and Tilts near each other? If the tilts are standing straight up or on their side, they go into a sleep mode and don’t transmit. I put mine in a glass of water to have them transmit a signal. Though remedial, make sure you have the correct color tilt chosen.

Your ‘Connection Type” is set to Bluetooth, yes?

 

Yup, connection type is Bluetooth, made sure the right color was selected, and I moved my Pi right up against the conical. Tilt seems to be on and active, as it appears in the iPhone app. Bluetooth is definitely working on the Pi, as my controllers are running solely on bluetooth.

 

Hey there! I wouldn’t be shocked if this project (or BrewPi in general!) ended up being the first foray into Linux for a lot of home brewers. The instructions are designed so that even Linux newcomers will (hopefully!) be able to get a successful build with minimal issues. That said, to your questions:

Can you use a Raspberry Pi 4?

Yep! This project will work great with a RPi 4, though if you haven't picked one up yet, the 3B+ is probably the better option. The Pi 4 is a powerful piece of hardware but has some cooling issues that I'm guessing the Raspberry Pi folks will work to fix over the next few months. Of course, if you already have a Pi 4, you're good to go.

Which hardware is the best?

It depends! For most people, the Pi 3B+ is probably the ideal combination of price and power. That said, Fermentrack isn't a resource hog - the Pi Zero Wireless can run it as well (just slightly slower). I don't recommend the non-wireless versions of the Pi (Either the 2 or non-wireless Zero) as they require a bit more work for most people to get up and running - and won't support a Tilt if you opt to add one later.

Temperature Controllers, Fermentrack, and the ESP8266

This is where things start getting a bit technical! Fermentrack is a software package that is designed to support legacy BrewPi-based temperature controllers as well as a handful of specific gravity sensors. One of the options for a legacy BrewPi-based temperature controller is the port I maintain of the BrewPi firmware to the ESP8266. As you noted, using the ESP8266 (as opposed to the Arduino) makes multi-chamber builds easier - but it also adds WiFi support, thus removing the need to keep your temperature controller chained to your Pi.

Multi-chamber support is a feature of Fermentrack rather than the ESP8266 port - you can control multiple chambers while using Arduino-based controllers as well, but it's a bit more difficult as a result of the USB cable requirement.


As you start working on your build, feel free to post any questions you have in this thread. I'm happy to help answer anything you want to know!

 

That's... odd? Which raspberry pi do you have? Are you using the internal bluetooth adapter or one that you have added via USB?

 

Raspberry Pi 3 Model B, and using the internal bluetooth.

 

I have two RPi4's now. Both work very well. They do need a fan, so get the case with that (maybe $2 more.) Even the Foundation's cases are beginning to ship with these. There's also a small fan hat ($12 at the link but I have seen them even cheaper) which would be ideal for folks wanting to use a custom case setup for their system.

That said, there is no reason you NEED that power (and corresponding price) just to run a temp control system. The 3B+ is a great little board and just about perfect in all respects for this project.

 

What I've been saying all along

No doubt the 4 has a place but it's wasted on anything we've been doing on HBT with the exception of BruControl...and that only runs under Windows 10, which doesn't quite run on the 4 yet and in any case isn't officially supported...yet. Outside of home brewing there are usage models that can take advantage of the memory and horsepower (modest file server, NAS, maybe lightweight video stuff, equally lightweight gaming) but inside...no so much...

Cheers!

 

Just got this running tonight on a Pi 4 and an Arduino Uno. I've been following the thread for quite a while and reading up on the supporting documentation. I was sweating a few parts and took a couple of evenings to get it working, but wow, this is really cool. Just need to install it in a cabinet. Wiring is in proof of concept mode right now. Don't judge.

 

Hi gents, does anyone know what causes this random issue where the temp isn’t displayed. It just happens every now and then.

 

I would check the logs. The sensors may be disconnecting for some reason.

 

How do you check the logs?

 

I am not that familiar with fermentrack; but in the original Brewpi GUI, the logs can be found in the maintenance panel. I would assume that they can be accessed from the Fermentrack GUI as well. Hopefully @Thorrak can elaborate. If you can SSH into the controller, they should be in the following directory:

/home/fermentrack/fermentrack/log/dev-[name]-stdout.log
/home/fermentrack/fermentrack/log/dev-[name]-stderr.log

(according to the docs)

 

Ok I know how to ssh into the PI . But I dont know what to type to view the log files?

 

For BrewPi and a named instance, it'd be something like:

Code:

 sudo nano /home/brewpi/brewpi1/logs/stderr.txt

Your path may be different...

Cheers!

 

Click the help icon in the upper right. There are links to view the logs on that page.

 

Thanks guys, here's the log. Its as sometime yesterday that it happened. I rebooted the controller and it fixed it. Does the log tell us anything? that line in bold??

Jan 10 2020 00:10:04 Controller debug message: INFO MESSAGE 20: No peak detected. Drifting down after cooling, current temp: 7.2, estimated peak: 6.3. Previous cool estimator: 0.770, New cool estimator: 0.512..
Jan 10 2020 00:19:09 Notification: Beer temperature set to 6.0 degrees in web interface
Jan 10 2020 00:19:09 Controller debug message: INFO MESSAGE 12: Received new setting: mode = b
Jan 10 2020 00:19:10 Controller debug message: INFO MESSAGE 12: Received new setting: beerSet = 6.0
Jan 10 2020 00:30:52 Error: controller is not responding to new data requests. Exiting.
Jan 10 2020 00:31:03 Connection type WiFi selected. Trying TCP serial (WiFi)
Jan 10 2020 00:31:03 Connecting to BrewPi esp6810598.local (via 192.168.1.105) on port 23
Jan 10 2020 00:31:06 Successfully connected to controller.
Jan 10 2020 00:31:06 Notification: Script started for beer 'Wookey jack'
Jan 10 2020 00:31:16 Checking software version on controller...
Jan 10 2020 00:31:16 Found BrewPi v0.2.4, running commit 00000000, running on an ESP 8266 on port 192.168.1.105:23

Jan 10 2020 00:31:16 BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
Jan 10 2020 00:31:16 Bound to TCP socket on port 2551, interface localhost
Jan 10 2020 00:31:17 Installed devices received: [{"i": 0, "t": 3, "c": 1, "b": 0, "f": 2, "h": 1, "d": 0, "p": 16, "v": 0, "x": 1}, {"i": 1, "t": 3, "c": 1, "b": 0, "f": 3, "h": 1, "d": 0, "p": 14, "v": 0, "x": 1}, {"i": 2, "t": 1, "c": 1, "b": 1, "f": 9, "h": 2, "d": 0, "p": 12, "v": 9.75, "a": "28AAB45C53140101", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 12, "v": 21.0, "a": "28AA355953140186", "j": 0.0}]
Jan 10 2020 00:31:18 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Jan 10 2020 00:55:28 Controller debug message: INFO MESSAGE 18: Negative peak detected: 14.4, estimated: 16.0. Previous cool estimator: 0.512, New cool estimator: 0.637.
Jan 10 2020 01:03:06 Error: controller is not responding to new data requests. Exiting.
Jan 10 2020 01:03:17 Connection type WiFi selected. Trying TCP serial (WiFi)
Jan 10 2020 01:03:17 Connecting to BrewPi esp6810598.local (via 192.168.1.105) on port 23
Jan 10 2020 01:03:20 Successfully connected to controller.
Jan 10 2020 01:03:20 Notification: Script started for beer 'Wookey jack'
Jan 10 2020 01:03:30 Checking software version on controller...
Jan 10 2020 01:03:30 Found BrewPi v0.2.4, running commit 00000000, running on an ESP 8266 on port 192.168.1.105:23

Jan 10 2020 01:03:30 BrewPi version received was 0.2.4 which this script supports in 'legacy' branch mode.
Jan 10 2020 01:03:30 Bound to TCP socket on port 2551, interface localhost
Jan 10 2020 01:03:31 Installed devices received: [{"i": 0, "t": 3, "c": 1, "b": 0, "f": 2, "h": 1, "d": 0, "p": 16, "v": 0, "x": 1}, {"i": 1, "t": 3, "c": 1, "b": 0, "f": 3, "h": 1, "d": 0, "p": 14, "v": 1, "x": 1}, {"i": 2, "t": 1, "c": 1, "b": 1, "f": 9, "h": 2, "d": 0, "p": 12, "v": 8.313, "a": "28AAB45C53140101", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 12, "v": 12.75, "a": "28AA355953140186", "j": 0.0}]
Jan 10 2020 01:03:32 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 13, "x": 1}]
Jan 10 2020 02:45:03 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 28AA355953140186
Jan 10 2020 02:45:03 Controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 0, address 28AA355953140186
Jan 10 2020 05:45:25 Controller debug message: INFO MESSAGE 18: Negative peak detected: 3.5, estimated: 3.2. Previous cool estimator: 0.637, New cool estimator: 0.525.
Jan 10 2020 06:13:26 Controller debug message: INFO MESSAGE 18: Negative peak detected: 3.9, estimated: 3.8. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 06:38:21 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.1, estimated: 4.1. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 06:59:55 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.0, estimated: 4.0. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 07:22:44 Controller debug message: INFO MESSAGE 18: Negative peak detected: 3.8, estimated: 3.7. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 07:48:18 Controller debug message: INFO MESSAGE 18: Negative peak detected: 3.8, estimated: 3.8. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 08:10:49 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.3, estimated: 4.4. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 09:53:06 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.4, estimated: 4.4. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 11:10:00 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.3, estimated: 4.3. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 12:23:52 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.2, estimated: 4.3. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 13:46:20 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.2, estimated: 4.3. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 15:08:58 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.1, estimated: 4.2. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 16:31:24 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.2, estimated: 4.3. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 17:58:43 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.1, estimated: 4.2. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 19:24:50 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.1, estimated: 4.2. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 20:51:40 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.0, estimated: 4.1. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 10 2020 21:25:26 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 28AAB45C53140101
Jan 10 2020 21:25:26 Controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 0, address 28AAB45C53140101
Jan 10 2020 22:23:20 Controller debug message: INFO MESSAGE 18: Negative peak detected: 3.9, estimated: 4.1. Previous cool estimator: 0.525, New cool estimator: 0.525.

 

Clearly unstable, with the nic and probes being randomly dropped.
How are you powering this agent?

Cheers!

 

Im using a 5v power supply. Not a Chinese ebay one either. This one..

https://www.jaycar.com.au/15w-5v-3a-enclosed-power-supply/p/MP3295

 

I'd also check the temp sensor connections. Is there a chance they are loose?

 

Those usually have an adjustment pot to the right of the terminal block. Have you set the regulator with a meter?
Losing nic and probes are unlikely to have a common root cause aside from low voltage...

Cheers!

 

No I havent but I know what your talking about. I will check it with my meter. It just happened again today. its worked fine for months now.

Jan 11 2020 01:09:25 Controller debug message: INFO MESSAGE 18: Negative peak detected: 4.1, estimated: 4.1. Previous cool estimator: 0.525, New cool estimator: 0.525.
Jan 11 2020 02:11:13 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 28AAB45C53140101
Jan 11 2020 02:11:13 Controller debug message: WARNING 2: Temperature sensor disconnected pin 0, address 28AA355953140186
Jan 11 2020 02:41:13 Controller debug message: INFO MESSAGE 20: No peak detected. Drifting down after cooling, current temp: 10.2, estimated peak: 4.1. Previous cool estimator: 0.525, New cool estimator: 0.350..

 

I had a 5V 2A brick like that one die after 5 years. It happens.
fwiw, you can ignore the INFO messages regarding peak detection. Those just let you know the firmware is adjusting its pseudo PID to more closely track the chamber response...

Cheers!

 

I checked them and they seem fine. I have two of these so I will swap the probes over and see which one fails. The voltage was 5.15V so I assume thats ok?

 

Yeah, that should be fine, actually. Assuming it's stable something else must be going on...

Cheers!

 

I can't change the probes over. The second one I built uses XLR connects. The first doesnt. Ill see how it goes and if it fails again Ill pull the plug apart and double check the solder joins. Thanks gents.

 

Hope y’all can help with my latest roadblock!

I had set up Fermentrack on my Pi while on Stretch, and I just upgraded to Buster. I am getting a 502 Bad Gateway when pulling up the dashboard.

I also updated to Python 3, and I was reading in another thread (https://www.homebrewtalk.com/forum/...-wifi-brewpi-no-arduino-needed.586476/page-44) that there may be an issue when updating to Python 2 to 3 causing a Bad Gateway error. Does this ring any bells?

 

Can you pull up google.com (or any other web site outside your LAN) on the RPi's Chromium browser successfully?

Cheers!

 

I believe it was working with other sites. I was also checking via VNC viewer so at least that connection was being made out of the network. My VNC connection keeps going down, and I can only assume the Pi is freezing, as I have to manually reboot to get it back online. Maybe it needs a wipe and reinstall, I don't know. I can check on the website loading later when I have the chance to reboot it, and I'll let you know.

 

OK I'm a long time UK home brewer but have just gotten into the wonderful world of Arduino/Raspberry Pi. As i work away from home a lot I want something reliable to keep an eye on fermentation while I'm away - just upgraded to a 14 gal Chronical too so a bit harder to control beer temp with just an STC1000 taped to a plastic bucket.

I've built an Arduino Setup as per the schematic i found here (which i believe came from FuzzeWuzze) except that:
a) i have added a 20x4 LCD screen connected through an I2C doodad to SDL and SDA pins and
b) i have 3x 3 meter DS18B20 probes rather than two and i used a 5k resistor as i didnt have a 4.7 to hand and i read somewhere that 5k will do.

I've downloaded and installed the glorious fermentrack in my Pi4 without issue and have plugged in and flashed my Arduino with the I2C variant and it's recognised and showing on my Fermentrack Dashboard.

OK now here is where i'm stuck! I've looked through this post but cant find anything obvious.

I cant get any reading for the sensor temps!
Things I've tried:
i) Different variants flashed onto the Arduino - no joy and i don't get my LCD working either.
ii) in the configure sensor Pins screen i can assign pin 5 & 6 to heating/cooling but my only other options are pin 2 and 10 and neither have anything plugged into them. My 3 sensors are plugged into A4 as per schematic.
iii) I ran a Debug (attached along with the log) which said that the Udev Availability Test failed "pyudev is not available, or isn't loaded" but i'm a noob and have no idea what that means or how to fix it.

If anyone out there can help I'd be grateful - if they're in the county of Cornwall there is a pint waiting for you!

Many thanks and sorry for the long post

Chard

 

Which firmware did you flash?

 

2nd one down on the Arduino Options:

BrewPi Remix
Version: 0.2.12
Revision: 0.1
Variant: I2C

Is that what you mean Lee?