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

[mper]

So I unplugged it and replugged it and now I am getting Cannot receive LCD text again. Here is the log.
Debug has everything passed except USB Serial Number Test.

"2824E47997040301", "j": 0.0}]
Dec 15 2022 16:58:13 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 4, "x": 1}]
Dec 16 2022 22:57:45 Refreshing dbConfig
Dec 16 2022 22:57:45 Connection type Serial selected. Opening serial port.
Dec 16 2022 22:57:45 Connected via serial to port /dev/ttyACM0
Dec 16 2022 22:57:45 Notification: Script started, with no active beer being logged
Dec 16 2022 22:57:55 Checking software version on controller...
Dec 16 2022 22:57:56 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revA shield on port /dev/ttyACM0

Dec 16 2022 22:57:56 BrewPi version received was 0.2.10 which this script supports in 'legacy' branch mode.
Dec 16 2022 22:57:56 Warning: version number of local copy of logMessages.h does not match log version number received from controller.controller version = 1, local copy version = 3. This is generally a non-issue, as thus far log messages have only been added - not changed.
Dec 16 2022 22:57:56 Bound to TCP socket on port 2473, interface localhost
Dec 16 2022 22:57:56 Installed devices received: [{"i": 0, "t": 3, "c": 1, "b": 0, "f": 2, "h": 1, "d": 0, "p": 5, "v": 0, "x": 1}, {"i": 1, "t": 3, "c": 1, "b": 0, "f": 3, "h": 1, "d": 0, "p": 6, "v": 0, "x": 1}, {"i": 2, "t": 1, "c": 1, "b": 1, "f": 9, "h": 2, "d": 0, "p": 18, "v": 54.949, "a": "28587979970403BF", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 18, "v": 54.611, "a": "2824E47997040301", "j": 0.0}]
Dec 16 2022 22:57:56 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 4, "x": 1}]
Dec 16 2022 23:20:32 Refreshing dbConfig
Dec 16 2022 23:20:32 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:20:38 Refreshing dbConfig
Dec 16 2022 23:20:38 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:20:48 Refreshing dbConfig
Dec 16 2022 23:20:48 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit

It looks like there is a process running and when you unplugged the device it tried to start a new processs without closing down the old one. Does it work if you restart the pi? If so its probably a bug

 

[Sawaya_brewing]

I shut it down, unplugged it and turned it back on again, still getting Cannot receive LCD text. Here is the log.

Dec 16 2022 23:38:18 Refreshing dbConfig
Dec 16 2022 23:38:18 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:38:28 Refreshing dbConfig
Dec 16 2022 23:38:28 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:38:38 Refreshing dbConfig
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/django/__init__.py", line 579, in connect
return real_connect(self)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 197, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/postgresql/base.py", line 185, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/lib/python3.9/site-packages/psycopg2/__init__.py", line 127, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL: the database system is shutting down


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/app/brewpi-script/brewpi.py", line 159, in <module>
dbConfig = refresh_dbConfig()
File "/app/brewpi-script/brewpi.py", line 109, in refresh_dbConfig
return models.BrewPiDevice.objects.get(id=device_id)
File "/usr/local/lib/python3.9/site-packages/django/db/models/manager.py", line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 411, in get
num = len(clone)
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 258, in __len__
self._fetch_all()
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 1261, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 57, in __iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
File "/usr/local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1152, in execute_sql
cursor = self.connection.cursor()
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 260, in cursor
return self._cursor()
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 236, in _cursor
self.ensure_connection()
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/django/__init__.py", line 579, in connect
return real_connect(self)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 197, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/postgresql/base.py", line 185, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/lib/python3.9/site-packages/psycopg2/__init__.py", line 127, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.OperationalError: FATAL: the database system is shutting down

Sentry is attempting to send 2 pending error messages
Waiting up to 2 seconds
Press Ctrl-C to quit
Dec 16 2022 23:41:38 Refreshing dbConfig
Dec 16 2022 23:41:38 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:41:48 Refreshing dbConfig
Dec 16 2022 23:41:48 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:41:58 Refreshing dbConfig
Dec 16 2022 23:41:58 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:42:08 Refreshing dbConfig
Dec 16 2022 23:42:08 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit

 

[mper]

I shut it down, unplugged it and turned it back on again, still getting Cannot receive LCD text. Here is the log.

Dec 16 2022 23:38:18 Refreshing dbConfig
Dec 16 2022 23:38:18 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:38:28 Refreshing dbConfig
Dec 16 2022 23:38:28 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:38:38 Refreshing dbConfig
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/django/__init__.py", line 579, in connect
return real_connect(self)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 197, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/postgresql/base.py", line 185, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/lib/python3.9/site-packages/psycopg2/__init__.py", line 127, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: FATAL: the database system is shutting down


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/app/brewpi-script/brewpi.py", line 159, in <module>
dbConfig = refresh_dbConfig()
File "/app/brewpi-script/brewpi.py", line 109, in refresh_dbConfig
return models.BrewPiDevice.objects.get(id=device_id)
File "/usr/local/lib/python3.9/site-packages/django/db/models/manager.py", line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 411, in get
num = len(clone)
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 258, in __len__
self._fetch_all()
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 1261, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 57, in __iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
File "/usr/local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1152, in execute_sql
cursor = self.connection.cursor()
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 260, in cursor
return self._cursor()
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 236, in _cursor
self.ensure_connection()
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 220, in ensure_connection
self.connect()
File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/django/__init__.py", line 579, in connect
return real_connect(self)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/base.py", line 197, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/local/lib/python3.9/site-packages/django/utils/asyncio.py", line 26, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/postgresql/base.py", line 185, in get_new_connection
connection = Database.connect(**conn_params)
File "/usr/local/lib/python3.9/site-packages/psycopg2/__init__.py", line 127, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.OperationalError: FATAL: the database system is shutting down

Sentry is attempting to send 2 pending error messages
Waiting up to 2 seconds
Press Ctrl-C to quit
Dec 16 2022 23:41:38 Refreshing dbConfig
Dec 16 2022 23:41:38 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:41:48 Refreshing dbConfig
Dec 16 2022 23:41:48 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:41:58 Refreshing dbConfig
Dec 16 2022 23:41:58 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit
Dec 16 2022 23:42:08 Refreshing dbConfig
Dec 16 2022 23:42:08 Another instance of BrewPi is already running, which will conflict with this instance. This instance will exit

I don’t really know whats causing this, the execption points to some database issue and it cannot connect to the postgress db. I think @Thorrak would need to give guidance on this.

 

[Sawaya_brewing]

I don’t really know whats causing this, the execption points to some database issue and it cannot connect to the postgress db. I think @Thorrak would need to give guidance on this.

@mper I appreciate your input. Is there an easy way to assign usb ports manually? Not sure if that would resolve the issue? I would really like to get the system running and stable again. Would it be easier to just install an esp8266 in place of the uno and bypass the usb alltogether. I do not see a diagram at all that shows where the wiring connects into the esp8266 if I want to direct swap with the uno, any way of pointing me in the right direction? Attached is how I am connected now and the esp8266 pinout. Uno has a 5v connection and the esp8366 has 3.3v, not sure if that would be an issue. Thanks!

 

[RayZab]

I had the “another instance of brewpi running” error yesterday. I ended up completely starting over on my RPi. Everything appears to be working now, but I can’t get my tilt to connect due to the missing python connectivity flag issue. I was able to follow the command used the bin folder as another person suggested and it appeared that setcap worked. However, I’m still getting the same tilt connection issue. Any ideas?

 

[Sawaya_brewing]

I ended up starting over and reinstalling Fermentrack. When I went to start the guided setup of connecting the Arduino, the auto-detection found a device even though I had nothing attached. Seems related to my issue posted above where sometimes the arduino is connected and other times it doesn't when starting Fermentrack. Any tips on how to go about this?

 

[troyp42]

Hi guys, is there anyway you can use VNC to connect to your pi then open fermentrack and check on your fermentations when away from home? If so is it easy to setup?

 

[troyp42]

No one seems to be using fermentrack anymore. I posted 3 weeks ago and no one has posted since?

Anyway does anyone else get this error from time to time? Ive been getting it in both of my controllers and there was mention of faulty power supplies but a mate of mine is using the same power supplies and he has never had this issue? its been going on for 3 years now.

 

[rkhanso]

I use OpenVPN to check my home/local LAN devices when away. There are free VPN options like that you can install on your phone and a device at home to get remote access. Just connect the VPN and browse like you're at home.

Your temperature screenshot doesn't look like an error. It's just not seeing temp sensors and reporting a temperature. Do you have a Beer and a Fridge temp sensor set up? If you wait some time, does a different sensor rotate to show in the display that has a temperature measurement?

I believe there are still people using Fermentrack. I used it for a long time and it works great. But I've sold my conical fermenter setup and switched to pressure fermenting in corny kegs inside and don't really need temp control anymore.

 

[JnR_NaT]

I am still using Fermentrack, but nowadays running in Docker off my NAS.

Your error, of you gontonthat controller, and pins, can you still see a probe allocated against it?

 

[troyp42]

I am still using Fermentrack, but nowadays running in Docker off my NAS.

Your error, of you gontonthat controller, and pins, can you still see a probe allocated against it?

The probes are allocated in settings but says temp value: none. When I trued to . When I tried to refresh sensor temp readings I get this error.

Could It be that I have faulty temp sensors on both of my controllers? On the other controller I hard wired the sensors and bypassed a 3 pin plug I was using. But it still gives me this error more so than this one Im showing above which usually never fails and has only just started doing this.

 

[troyp42]

I am still using Fermentrack, but nowadays running in Docker off my NAS.

Your error, of you gontonthat controller, and pins, can you still see a probe allocated against it?

Ok I fixed this temp controller. it was a loose temp sensor wire. But.... That still doesnt explain my issue of temp controller 2 randomly switching to dashes every now and again over the last few years. Maybe I should just swap out the power supply? I do have another one. I assume the 1 wire sensors are fine or it wouldn't work ok for over a week at a time before failing again. A reboot always fixes it and then it will work again for another week or so.

 

[JnR_NaT]

I had a very similar issue, when I was using cheep knock-off DS18b20 probes, I ended up getting Dallas Instrument versions and have been good since

 

[troyp42]

I had a very similar issue, when I was using cheep knock-off DS18b20 probes, I ended up getting Dallas Instrument versions and have been good since

yeh I was thinking of maybe getting better probes. The probes i bought from eBay were only $4.95 each. The probes I can get from another supplier Aus electronic direct are $21 each but I want to make sure they aren’t the same eBay cheapies they are selling.

 

[Lalo_uy]

To be sure they are original you need to buy at a authorized reseler.
Go to Mouser. They do not sell waterproof ones, only the to96 sensor.
You need to solder the wire and waterproof them yourself.

 

[Thorrak]

To be sure they are original you need to buy at a authorized reseler.
Go to Mouser. They do not sell waterproof ones, only the to96 sensor.
You need to solder the wire and waterproof them yourself.

I’ve personally been inclined to just not waterproof them as of late, since I always end up using a Thermo well anyways. If the Thermo well leaks then I figure I have bigger problems than a wet sensor.

Of course - that’s on batches where I use a wired beer sensor. Most of my recent batches have used the latest ESP32 firmware which pulls temps directly from a tilt.

No one seems to be using fermentrack anymore. I posted 3 weeks ago and no one has posted since?

I don’t have any stats on usage, but based on errors hitting sentry I know there are at least a few users out there. That said, I agree that some kind of “state of the software” update might be in order as the updates have been a bit slower for the past year. I’m going to go to a brewery later this afternoon I think — If I do, I’ll try to get something drafted.

 

[Thorrak]

The past year has been a busy one for me -- but admittedly most of those changes haven't been as visible to Fermentrack users, especially during the latter half of the year. Here's what's been going on:

New Fermentrack features in 2022​

Released​

There was only one major release in 2022, the "Final Dockerless and Backup & Restore" release. The full release notes are here, but the major feature this release introduced were backup & restore functionality based on Django's "dump" feature.

Due to the fact that this release still supports non-docker installs there is some "legacy" code remaining in this release which can cause issues - including the infamous "python flag" bug people have encountered/reported on in this thread.

Related Projects/Unreleased​

Midway through 2022 I announced a new port of the BrewPi firmware over to the ESP32. This firmware is partially supported by the 2022 release of Fermentrack noted above, but most of the support for the new features the ESP32 brings are currently sitting unreleased on the "docker-dev" branch. This includes support for Bluetooth "fridge" temperature sensors, the use of Tilt Pros as "beer" sensors, and the use of Kasa WiFi switches as relays (thereby enabling a fully "solder-free" BrewPi experience).

In addition to the work to support BrewPi-ESP32, I've also been working on a complete refactor of the "launcher" for BrewPi-script instances in order to eliminate the use of Circus in Fermentrack. Circus is the process manager which (currently) enables an instance of BrewPi-script to be launched for each individual controller you have installed in Fermentrack. Unfortunately, Circus seems to have been largely abandoned by its developers, and brings with it requirements for packages (zmq) that have created significant headache in maintaining Fermentrack. The replacement launcher is mostly complete, but is not bug-free, and is the primary reason that this code has not been officially released.

Completing these features, getting them tested, and released are the immediate next steps - which I hope to do in the coming weeks/months. I'll cover the longer term outlook in my next post.

 

[NeoBrew]

Thank you Thorrak for working on and maintaining this software. I use it on my fermentation chamber and have been quite happy with it. I will be bummed the day I fire it up for a brew and it doesn't work!

I would offer more peer support for questions on here, but I barely know how to make mine work.

 

[troyp42]

Thanks Thorrak. Ive been using Fermentrack for many many years now and have also managed to get a few brew club guys onto it as well. Appreciate all you do for it.

 

[Thorrak]

Upcoming (Medium-term) Changes/Features​

Tilt Hydrometer & TiltBridge Support​

The original Tilt Hydrometer support was built into Fermentrack long before the TiltBridge concept was concieved. Unfortunately, some of the "best practices" that were decided during development of TiltBridge have not yet made their way back into Fermentrack. In the future, my plan is to replace the Fermentrack Tilt daemon and replace it with a new workflow that leverages the same pipes and plumbing as TiltBridge. My hope is that this will simplify the code base and UI, pipe Tilt readings through a supportable interface, and eliminate some of the errors/confusion that have cropped up as Fermentrack has grown over the years.

BrewFlasher Rebranding & BrewFlasher Web Integration​

Fermentrack's built-in firmware flashing process inspired the development of the desktop BrewFlasher app, which then in turn inspired BrewFlasher Web Edition about this time last year. Last year I additionally migrated the central firmware management functions from fermentrack.com to brewflasher.com.

Going forward, I would like to present all three options within Fermentrack, leveraging the BrewFlasher branding where appropriate. The existing Fermentrack implementation requires that users connect controllers to the Raspberry Pi, where some users may find connecting the controller to their local computer to be preferable. By presenting all three options within Fermentrack users will be able to select the option that is most convenient for them given their setup.

First-class 64-Bit (Desktop & RPi) Support​

Historically, Fermentrack was designed to be deployed on a Raspberry Pi. As Raspberry Pis have become difficult or expensive to source (and as the use of virtual machines has continued to grow) I've seen an increasing number of users convert from Raspberry Pi-based builds to builds using traditional desktop architecture. Going forward, I plan to target both architectures equally, with releases only being officially made when images/packages can be built for the armv7 (32-bit RPi), aarch64 (64-bit RPi), and amd64 (modern desktops & virtual machines) platforms.

Although technically this alone is not a change as I currently already build packages for all 3 architectures, the influence of this decision can be seen in the items listed above. Converting to a "TiltBridge Daemon" means that users without an RPi will be able to receive the same level of support from Fermentrack as users who use an RPi's built-in bluetooth adapter. Integrating BrewFlasher Web means that users running on VMs can flash controllers from their local desktop. While I plan to continue to target Raspberry Pis and leverage their built-in functionality as appropriate, my goal going forward will be to build functionality in a way that is hardware-agnostic.

Longer Term​

BrewPi REST​

Looking further ahead, my plan is to convert the BrewPi-ESP WiFi firmware (both ESP8266 and ESP32) to use a true REST interface to communicate with Fermentrack rather than the "telnet" interface currently in use. In order to prevent having to support two separate communication platforms in Fermentrack, this will require developing a "serial to REST" daemon that can convert existing Arduino (and legacy ESP-based serial) controllers to leverage a REST interface. Development of the new "serial to REST" daemon as well as the conversion of Fermentrack away from BrewPi-Script are both expected to be longer-term projects.

 

[JnR_NaT]

yeh I was thinking of maybe getting better probes. The probes i bought from eBay were only $4.95 each. The probes I can get from another supplier Aus electronic direct are $21 each but I want to make sure they aren’t the same eBay cheapies they are selling.

Are you in Australia, if so the ones from Altronics are good to go

 

[troyp42]

Are you in Australia, if so the ones from Altronics are good to go

Yes I am and Altronics isnt far from me at all. Thanks heaps for letting me know Ill go get some today.

 

[fredrichl]

Hi, i'm new here and i've been brewing and fermenting in a manual manner for a couple of years, and i have now gotten to the point equipmentwise where i can start to automate stuff. I got a fridge, tilt, an inkbird and a heat belt. My questions about Fermentrack are: Does it have support for a inkbird itc 308? And is it possible to get it to interact with google docs the way TiltPI does (Uploading sg and temp and making a graph in a calc?)

 

[day_trippr]

I'll leave the gist of that question for @Thorrak but the Inkbird ITC-308 has zero communication capabilities.
Nothing is going to control or even monitor one of those...

 

[fredrichl]

It has wifi, right now i control it manually with the tuya app.

 

[day_trippr]

Ok, that would be the ITC-308-WIFI.

Cheers!

 

[fredrichl]

Ah, sorry for being a tad unclear. I didn't know they existed without wifi.

I just bought one from my local brewing shop and assumed that was the concept so to speak

 

[waynerob11]

Wondering if you can help - I have Fermentrack installed on a fresh installation of Buster 32 bit - without issue - except when I am trying to flash a controller - I have tried esp8266, Wavgat Uno R3 they just report failure - managed to flash a nano but fermentrack would not recognise pin allocations - been into Raspi config and enabled USB serial - followed the fermentrack doc instructions to the letter - just frustrated

 

[Thorrak]

Hi, i'm new here and i've been brewing and fermenting in a manual manner for a couple of years, and i have now gotten to the point equipmentwise where i can start to automate stuff. I got a fridge, tilt, an inkbird and a heat belt. My questions about Fermentrack are: Does it have support for a inkbird itc 308? And is it possible to get it to interact with google docs the way TiltPI does (Uploading sg and temp and making a graph in a calc?)

Currently, that hardware is not supported. I don't necessarily object to having support for other temperature controllers added to Fermentrack, but it's not a feature that I am likely to build myself. That said - Fermentrack is open source, and pull requests are welcome!

Google Docs integration is a bit trickier -- my experience with TiltBridge has not been stellar, unfortunately. For Google Docs integrations to work, typically users have to go in, edit scripts, fiddle with the developer console, etc. -- none of which are conducive to a positive end user experience. I actually have a project planned to help move away from google docs for active data collection, though there is no ETA on that as it's a ways down in the queue.

Wondering if you can help - I have Fermentrack installed on a fresh installation of Buster 32 bit - without issue - except when I am trying to flash a controller - I have tried esp8266, Wavgat Uno R3 they just report failure - managed to flash a nano but fermentrack would not recognise pin allocations - been into Raspi config and enabled USB serial - followed the fermentrack doc instructions to the letter - just frustrated

It's hard to tell exactly what you might be experiencing. Which hardware exactly are you trying to flash -- you mention an ESP8266, an Arduino Uno clone, and a "nano" - exactly which boards/firmware did you try? Did the flashing itself fail, or are the issues just related to pin assignment?

 

[waynerob11]

I have five fermenters, not necessarily going all at once but could be - so I need at least 11 io pins (10 for heat/cool and one for DS18B20 probes) and the esp8266 doesn't have that many so I'm stuck with the Arduino boards and have Fermentrack running on a RP3B with 32 bit Buster Legacy, I had tried the latest OS version and then tried the legacy both have the same result.
When I get to flash a controller, I initially tried a Wavgat Uno R3 from Ali Express after downloading the drivers and ensuring the Blink program uploads and works which it does, but after selecting the uno board and having it found by fermentrack, the flashing process fails, so I tried an Arduino Nano which flashed successfully but Fermentrack doesn't recognise the pinouts will not allow me to assign pins. Then i tried the ESP8266 NodeMCU V3 30 PINS IoT WiFi Dev Board which also fails to flash.
The RP3B has enough pins, why I can't just use the Pi and dispense with the Arduino.
I would also like to measure Pressure but can't see anywhere if Fermentrack can do that. Happy to use an Arduino Mega if need be, but no option available in Fermentrack to use that board.
I have ordered a genuine Uno R3 to see if that helps.
Your advice would be greatly appreciated.