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

[ChrisThomas]

@Thorrak Is the PCB and BOM in a state that I can start ordering bits? I'm thinking of starting the building of new setup next month so I can start ordering stuff from China.


Chris

 

[Thorrak]

@Thorrak Is the PCB and BOM in a state that I can start ordering bits? I'm thinking of starting the building of new setup next month so I can start ordering stuff from China.


Chris

Yep! I’ve been using the boards on my end for a bit now with no issues. Let me know if you have any questions as you order!

 

[Nateb]

Huh. That's a first...

It sounds like there's an issue with the pidfile, which is a small file that gets written out to ensure that you don't have two instances of BrewPi-script launched at the same time, with both trying to control the same device. This shouldn't happen -- but clearly, in your case, it did. I would be concerned that this is a sign that there might be an issue with your SD card -- before you do anything, I would back up whatever data you have on it you want to save. Once that's done, you've got three options for how to handle it:

Option 1 - Restart the RPi. This is the easiest option, but the one least likely to solve the problem. Still though, might be worth a shot!

Option 2 - Delete the BrewPi device and recreate it. This should result in a brand new device ID being assigned which means a new pidfile. Not guaranteed to fix the problem, but highly likely!

Option 3 - Re-run the install script. I think this should nuke your Docker container which should delete the pidfile. I'd try this last, unless you don't want to delete the BrewPi device, in which case you can try this second. You can use the exact same install script that you have saved from when you first installed Fermentrack here - the script is idempotent.

I believe I had the same issue last week with a couple controllers that had been unplugged for a while. After restarting the pi all devices showed back up.

 

[ChrisThomas]

Yep! I’ve been using the boards on my end for a bit now with no issues. Let me know if you have any questions as you order!

@Thorrak Just double checking the BOM... I'm going surface mount, I've got the resistors, capacitors and MOSFET. So my order list is quite small, just the PCB and D32 Pro. Unless you have a strong recommendation for the new display?

I'm making the assumption that I can initially use my existing PSU (2A), relays (SSR) and display (LCD2004)?


Chris

 

[Thorrak]

@Thorrak Just double checking the BOM... I'm going surface mount, I've got the resistors, capacitors and MOSFET. So my order list is quite small, just the PCB and D32 Pro. Unless you have a strong recommendation for the new display?

I'm making the assumption that I can initially use my existing PSU (2A), relays (SSR) and display (LCD2004)?


Chris

Yep! My recommendation is for the new display as it's pretty, but functionally you're fine to use an LCD2004. (Or use an LCD2004 initially and upgrade later)

I would go ahead and pick some 10 pin (5x2) box headers up if you're placing an order from China just so you can solder it on now if you think you may ever want to upgrade later, but that just saves you having to disconnect/reconnect everything at a later date.

 

[ChrisThomas]

@Thorrak Am I right in saying that if I went for the D32 Pro and the (recommended) TFT, then I don't need the box header and the display plugs into the D32 Pro rather than the PCB?

I think I'll still follow your recommendation and add the box header though, future proofing???? Just going through the PCB and BOM double checking what I might need to order.


Chris

 

[ChrisThomas]

Oh, just went to Oshpark to order PCBs, a bit pricier than I expected, going to have to wait 'till next month... Think I'll get everything else ordered this week though.

 

[Thorrak]

Oh, just went to Oshpark to order PCBs, a bit pricier than I expected, going to have to wait 'till next month... Think I'll get everything else ordered this week though.

Is it the UK shipping that's killing it? If so, ping me -- there's a fab that I've been told is cheaper to get shipped to some international destinations, but isn't one I've used personally.

 

[ChrisThomas]

@Thorrak Not the shipping, but I guess it's just price increases we're all seeing everywhere. I got some PCBS from Oshpark back in May for under $10, $26 for these. I've recently retired so have to be a bit more circumspect with expediture.

 

[Thorrak]

@Thorrak Am I right in saying that if I went for the D32 Pro and the (recommended) TFT, then I don't need the box header and the display plugs into the D32 Pro rather than the PCB?

I think I'll still follow your recommendation and add the box header though, future proofing???? Just going through the PCB and BOM double checking what I might need to order.


Chris

Correct. The box header allows the use of screens other than the LoLin one, including a few that are physically larger if you were ever so inclined. My thought is that if you ever mount the PCB in a case you would have to remove it to add the box header later, so it’s cheap insurance to add it now.

@Thorrak Not the shipping, but I guess it's just price increases we're all seeing everywhere. I got some PCBS from Oshpark back in May for under $10, $26 for these. I've recently retired so have to be a bit more circumspect with expediture.

Unfortunately, that’s more a function of the size of the PCB than inflation. OSHPark has never been cheap - especially for “mid-size” PCBs like this one which is why the cost is so high vs. the smaller PCBs you likely ordered before. I’ll shoot you a PM with some of what I’ve found from looking at fabs.

 

[pdavidc]

Hoping I can get a little help or a push in the direction of a similar post I missed...

Have been running Fermentrack for a few years. Recently changed internet providers and thus wifi settings. I have updated the wifi on the pi and both esp8622 controllers. I use Fing and can see all three on my network. However, Fermentrack "Cannot receive LCD text from Controller/Script" for either controller. Both controllers are running and the temp sensors work fine (as seen on lcd screen)

I have started and restarted both the pi and controllers (in different orders as well) to no avail.

I have reflashed one of the controllers and it did not resolve the issue.

Debub of both connection shows "failed" on DNS Lookup Test and Connection Test. Although connection test is trying the ip from the old wifi. I don't know how to fix that.

Trying to install a new Device reports that I have no uninstalled mDNS devices and no found mDNS devices match any installed in Fermentrack.

The only thing I have not tried in deleting the controllers and seeing if I can then reinstall them.

Appreciate any help or direction to thread.

Dave

 

[jjmak]

I, too, have another of those dreaded "Cannot receive LCD text from Controller/Script" messages. Everything had been working fine for months, but had a power outage here today in Florida from Hurricane Nicole (Raspberry Pi is plugged into battery backup but guess lost juice at some point). I've been trying for hours to get Ardunio to speak to Pi, no luck. I can ssh into Pi. Any suggestions on commands to send to Arduino to reboot it?

 

[Desmop]

I, too, have another of those dreaded "Cannot receive LCD text from Controller/Script" messages. Everything had been working fine for months, but had a power outage here today in Florida from Hurricane Nicole (Raspberry Pi is plugged into battery backup but guess lost juice at some point). I've been trying for hours to get Ardunio to speak to Pi, no luck. I can ssh into Pi. Any suggestions on commands to send to Arduino to reboot it?

I would re-install Fermentrack, this solved the problem for me. SSH and enter the install command.

curl -L install.fermentrack.com | bash

 

[jjmak]

Worked perfectly, @Desmop ! Many thanks for the quick response!

 

[rebellion-brewing]

Hello - hoping for some help here. Brand new user - I cannot for the life of me get any of my ispindel data to show in this screen.

If I configure my iSpindel to send MQTT, I can view that data fine - so I know the ispindel will connect to my network.

Any ideas?

Fermentrack is sitting on port 8890.

 

[rebellion-brewing]

Hello - hoping for some help here. Brand new user - I cannot for the life of me get any of my ispindel data to show in this screen.

If I configure my iSpindel to send MQTT, I can view that data fine - so I know the ispindel will connect to my network.

Any ideas?

Fermentrack is sitting on port 8890.

I am an idiot - you need the http:// when configuring the iSpindel Path/URI

 

[rebellion-brewing]

Okay - I have this running on my rPi, however I'd like to run via docker on my unraid server.

When running

docker pull jdbeeler/fermentrack

I get an error

/entrypoint: line 9: POSTGRES_USER: unbound variable

 

[kdw2pd]

Is there a way to change the port in the non-Docker Fermentrack installation? Trying to get Fermentrack set up on my 3a+, and the Docker installation doesn't seem to want to cooperate. When I run the semi-automated non_docker script, it installs fine, but doesn't give me the option to change the port like it did with the Docker version. I'd like to run Raspberry Pints on the same Pi if possible.

 

[LBussy]

Is there a way to change the port in the non-Docker Fermentrack installation? Trying to get Fermentrack set up on my 3a+, and the Docker installation doesn't seem to want to cooperate. When I run the semi-automated non_docker script, it installs fine, but doesn't give me the option to change the port like it did with the Docker version. I'd like to run Raspberry Pints on the same Pi if possible.

Thorrak is on vaca but I might be able to get you close.

Fermentrack runs on nginx, and your Pi is close enough to Ubuntu to flow those instructions on this page:

https://www.tecmint.com/change-nginx-port-in-linux/
The file /etc/nginx/sites-enabled/default may not be the one it uses, check that sites-enabled directory for other files, it's possible Fermentrack is not using the default site.

 

[RayZab]

Hi all, I’ve been using fermentrack for a while now, with a few minor issues. However when starting up my raspberry pi and arduino uno today to start a new batch, I am getting the dreaded “Cannot receive LCD text” message. I’ve tried restarting both devices multiple times and also debugged the device connection (fermentrack tells me the Uno is active and all tests pass except for the USB serial number test). Any idea what I can do to get the two devices to connect?

 

[mper]

Hi all, I’ve been using fermentrack for a while now, with a few minor issues. However when starting up my raspberry pi and arduino uno today to start a new batch, I am getting the dreaded “Cannot receive LCD text” message. I’ve tried restarting both devices multiple times and also debugged the device connection (fermentrack tells me the Uno is active and all tests pass except for the USB serial number test). Any idea what I can do to get the two devices to connect?

Can you check the full error message in the logfile? Press the questionmark and check the logfiles

 

[RayZab]

Can you check the full error message in the logfile? Press the questionmark and check the logfiles

 

[mper]

View attachment 807938

Fermentrack thinks there is a process already running. It creates a file with the extension brewpi-[num].pid under /tmp, I have brewpi-1.pid on my setup. You can try to remove these files and restart the pi to see if the script starts up. If the problem repeats then there might be something corrupt in your configuration/database.

so in the shell go to the catalog
cd /tmp

list all pid files
ls *.pid

remove the file
rm <name of file>.pid

 

[RayZab]

Fermentrack thinks there is a process already running. It creates a file with the extension brewpi-[num].pid under /tmp, I have brewpi-1.pid on my setup. You can try to remove these files and restart the pi to see if the script starts up. If the problem repeats then there might be something corrupt in your configuration/database.

so in the shell go to the catalog
cd /tmp

list all pid files
ls *.pid

remove the file
rm <name of file>.pid

No luck. Wondering if I should just reset the RPi at this point and start over.

 

[mper]

No luck. Wondering if I should just reset the RPi at this point and start over.

You can try to remove the brewpi device first and add it as a new device again to see if that works.

 

[Sawaya_brewing]

Hi everyone. I am having an issue with my Fermentrack "Cannot receive LCD text from Controller/Script" I am using a Raspberry Pi 3 with an Arduino Uno. I installed through Docker and updated the installation as well. I find that I need to shut it down and restart a few times and it will eventually connect. Once it connects I can complete my fermentation without any issues (everything else is working). When I go to debugging connection, everything passes except USB Serial Number Test, which fails. I uninstalled the arduino and set it up again, but that didn't help at all. Would appreciate any help at all with the USB Serial Number Test failing issue. Thanks in advance!

 

[mper]

Hi everyone. I am having an issue with my Fermentrack "Cannot receive LCD text from Controller/Script" I am using a Raspberry Pi 3 with an Arduino Uno. I installed through Docker and updated the installation as well. I find that I need to shut it down and restart a few times and it will eventually connect. Once it connects I can complete my fermentation without any issues (everything else is working). When I go to debugging connection, everything passes except USB Serial Number Test, which fails. I uninstalled the arduino and set it up again, but that didn't help at all. Would appreciate any help at all with the USB Serial Number Test failing issue. Thanks in advance!

Can you check what errors you get in the logfile ? Press the questionmark in the menu to view all the logfiles. In order to use the serial port the container must be run in privilged mode and the /dev filesystem needs to be imported into the container.

 

[Sawaya_brewing]

Can you check what errors you get in the logfile ? Press the questionmark in the menu to view all the logfiles. In order to use the serial port the container must be run in privilged mode and the /dev filesystem needs to be imported into the container.

Appreciate the quick reply. Here is the log, kind of weird, I fired it up and it worked right away, but still get that error when I click on debug. What do I need to do to run it in privlidged mode?


Dec 15 2022 16:53:05 Refreshing dbConfig
Dec 15 2022 16:53:05 Connection type Serial selected. Opening serial port.
Dec 15 2022 16:53:05 Connected via serial to port /dev/ttyACM0
Dec 15 2022 16:53:05 Notification: Script started, with no active beer being logged
Dec 15 2022 16:53:15 Checking software version on controller...
Dec 15 2022 16:53:15 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revA shield on port /dev/ttyACM0

Dec 15 2022 16:53:15 BrewPi version received was 0.2.10 which this script supports in 'legacy' branch mode.
Dec 15 2022 16:53:15 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 15 2022 16:53:15 Bound to TCP socket on port 2473, interface localhost
Dec 15 2022 16:53:15 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": 57.537, "a": "28587979970403BF", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 18, "v": 53.037, "a": "2824E47997040301", "j": 0.0}]
Dec 15 2022 16:53:15 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 4, "x": 1}]
Dec 15 2022 16:58:02 Refreshing dbConfig
Dec 15 2022 16:58:02 Connection type Serial selected. Opening serial port.
Dec 15 2022 16:58:02 Connected via serial to port /dev/ttyACM0
Dec 15 2022 16:58:02 Notification: Script started, with no active beer being logged
Dec 15 2022 16:58:12 Checking software version on controller...
Dec 15 2022 16:58:12 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revA shield on port /dev/ttyACM0

Dec 15 2022 16:58:12 BrewPi version received was 0.2.10 which this script supports in 'legacy' branch mode.
Dec 15 2022 16:58:12 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 15 2022 16:58:12 Bound to TCP socket on port 2473, interface localhost
Dec 15 2022 16:58:13 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": 57.199, "a": "28587979970403BF", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 18, "v": 53.037, "a": "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}]

 

[mper]

Appreciate the quick reply. Here is the log, kind of weird, I fired it up and it worked right away, but still get that error when I click on debug. What do I need to do to run it in privlidged mode?


Dec 15 2022 16:53:05 Refreshing dbConfig
Dec 15 2022 16:53:05 Connection type Serial selected. Opening serial port.
Dec 15 2022 16:53:05 Connected via serial to port /dev/ttyACM0
Dec 15 2022 16:53:05 Notification: Script started, with no active beer being logged
Dec 15 2022 16:53:15 Checking software version on controller...
Dec 15 2022 16:53:15 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revA shield on port /dev/ttyACM0

Dec 15 2022 16:53:15 BrewPi version received was 0.2.10 which this script supports in 'legacy' branch mode.
Dec 15 2022 16:53:15 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 15 2022 16:53:15 Bound to TCP socket on port 2473, interface localhost
Dec 15 2022 16:53:15 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": 57.537, "a": "28587979970403BF", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 18, "v": 53.037, "a": "2824E47997040301", "j": 0.0}]
Dec 15 2022 16:53:15 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 4, "x": 1}]
Dec 15 2022 16:58:02 Refreshing dbConfig
Dec 15 2022 16:58:02 Connection type Serial selected. Opening serial port.
Dec 15 2022 16:58:02 Connected via serial to port /dev/ttyACM0
Dec 15 2022 16:58:02 Notification: Script started, with no active beer being logged
Dec 15 2022 16:58:12 Checking software version on controller...
Dec 15 2022 16:58:12 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revA shield on port /dev/ttyACM0

Dec 15 2022 16:58:12 BrewPi version received was 0.2.10 which this script supports in 'legacy' branch mode.
Dec 15 2022 16:58:12 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 15 2022 16:58:12 Bound to TCP socket on port 2473, interface localhost
Dec 15 2022 16:58:13 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": 57.199, "a": "28587979970403BF", "j": 0.0}, {"i": 3, "t": 1, "c": 1, "b": 0, "f": 5, "h": 2, "d": 0, "p": 18, "v": 53.037, "a": "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}]

It looks like it works fine according to the logs. There are no errors and it can read the data fine. I only use wifi connection so I have not really tried the usb connection.

What error do you get when trying the debug connection ? Do you get any errors in the log after that ?

 

[Sawaya_brewing]

It looks like it works fine according to the logs. There are no errors and it can read the data fine. I only use wifi connection so I have not really tried the usb connection.

What error do you get when trying the debug connection ? Do you get any errors in the log after that ?

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