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

Brewer's Friend 728
Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum

Help Support Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
adman said:
It was stretch, but I just upgraded to buster.
Click to expand...
That also works!

If anyone else has issues, the revised fix script is posted. Same command/instructions as before:

1. Log into your Pi as the `pi` user via SSH
2. Run: curl -L "https://raw.githubusercontent.com/thorrak/fermentrack-tools/master/fix-environment.sh" | sudo bash


This will fix most issues with most environments, including - now - installing Python 3.7.7 on Stretch where necessary. If a new Python 3.7 installation is required, this script can take up to several hours to run, as it requires compiling Python from source. Fun times (but at least it's all automatic).

Note - Although I've tested this script on a local Pi running Stretch, I can't guarantee that this script will fix all issues, or won't cause different problems. It's intended for use on Fermentrack installs that were set up initially using the "one step curl" command. (ie. installed to the fermentrack user at /home/fermentrack/fermentrack with a virtual environment in /home/fermentrack/venv/). I'm guessing this probably covers 95% of installations.
 
Last edited:
Thorrak said:
That also works!

If anyone else has issues, the revised fix script is posted. Same command/instructions as before:

1. Log into your Pi as the `pi` user via SSH
2. Run: curl -L "https://raw.githubusercontent.com/thorrak/fermentrack-tools/master/fix-environment.sh" | sudo bash


This will fix most issues with most environments, including - now - installing Python 3.7.7 on Stretch where necessary. If a new Python 3.7 installation is required, this script can take up to several hours to run, as it requires compiling Python from source. Fun times (but at least it's all automatic).

Note - Although I've tested this script on a local Pi running Stretch, I can't guarantee that this script will fix all issues, or won't cause different problems. It's intended for use on Fermentrack installs that were set up initially using the "one step curl" command. (ie. installed to the fermentrack user at /home/fermentrack/fermentrack with a virtual environment in /home/fermentrack/venv/). I'm guessing this probably covers 95% of installations.
Click to expand...
Ok. I tried again and got almost the identical error (see below). Is it possible to do a reinstall from the one-step curl script and keep all of my settings?

EDITED to add some additional troubleshooting info: RPi 3B+ running raspian; recently upgraded from Stretch to Buster; fully up-to-date per apt. I am also running PiHole on this pi, but PiHole is running on port 8080, while Fermentrack is on port 80. Everything was running peachy until the most recent update.

Thanks,
-Adam

Code: 
~ $ curl -L "https://raw.githubusercontent.com/thorrak/fermentrack-tools/master/fix-environment.sh" | sudo bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  7696  100  7696    0     0  39875      0 --:--:-- --:--:-- --:--:-- 39875
::: Verifying free disk space...

::: Checking for Internet connection:
::: Internet connection Success!

::: Reinstalling dependencies using apt-get
::: apt is updated - Triggering install of all packages.
::: Apt-packages reinstalled successfully.

::: Python 3.7 is installed. Continuing.
::: Making sure everything is owned by fermentrack

::: Enabling python to query bluetooth without being root
::: Switching to the Fermentrack user and doing all the other bits...
Stopping Circus
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/circusctl", line 7, in <module>
    from circus.circusctl import main
ModuleNotFoundError: No module named 'circus'
Upgrading pip
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/pip3", line 7, in <module>
    from pip import main
ModuleNotFoundError: No module named 'pip'
Fetching, resetting, and pulling from git...
Fetching origin
HEAD is now at f801053 Setting DJANGO_ALLOW_ASYNC_UNSAFE for calls from tilt_monitor_aio.py (Fixes #456)
Already up to date.
Re-installing Python packages from requirements.txt via pip3
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/pip3", line 7, in <module>
    from pip import main
ModuleNotFoundError: No module named 'pip'
Running manage.py migrate/fix_sqlite_for_django_2/collectstatic...
Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from django.db import IntegrityError
ModuleNotFoundError: No module named 'django'
Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from django.db import IntegrityError
ModuleNotFoundError: No module named 'django'
Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from django.db import IntegrityError
ModuleNotFoundError: No module named 'django'
Quitting Circus
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/circusctl", line 7, in <module>
    from circus.circusctl import main
ModuleNotFoundError: No module named 'circus'
Calling updateCronCircus to restart Circus...
Starting Fermentrack supervisor: circusd: Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/circusd", line 7, in <module>
    from circus.circusd import main
ModuleNotFoundError: No module named 'circus'
failed, please see logfile.

Done! Exiting.
 
Last edited:
adman said:
Ok. I tried again and got almost the identical error (see below). Is it possible to do a reinstall from the one-step curl script and keep all of my settings?

Thanks,
-Adam

Code: 
~ $ curl -L "https://raw.githubusercontent.com/thorrak/fermentrack-tools/master/fix-environment.sh" | sudo bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  7696  100  7696    0     0  39875      0 --:--:-- --:--:-- --:--:-- 39875
::: Verifying free disk space...

::: Checking for Internet connection:
::: Internet connection Success!

::: Reinstalling dependencies using apt-get
::: apt is updated - Triggering install of all packages.
::: Apt-packages reinstalled successfully.

::: Python 3.7 is installed. Continuing.
::: Making sure everything is owned by fermentrack

::: Enabling python to query bluetooth without being root
::: Switching to the Fermentrack user and doing all the other bits...
Stopping Circus
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/circusctl", line 7, in <module>
    from circus.circusctl import main
ModuleNotFoundError: No module named 'circus'
Upgrading pip
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/pip3", line 7, in <module>
    from pip import main
ModuleNotFoundError: No module named 'pip'
Fetching, resetting, and pulling from git...
Fetching origin
HEAD is now at f801053 Setting DJANGO_ALLOW_ASYNC_UNSAFE for calls from tilt_monitor_aio.py (Fixes #456)
Already up to date.
Re-installing Python packages from requirements.txt via pip3
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/pip3", line 7, in <module>
    from pip import main
ModuleNotFoundError: No module named 'pip'
Running manage.py migrate/fix_sqlite_for_django_2/collectstatic...
Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from django.db import IntegrityError
ModuleNotFoundError: No module named 'django'
Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from django.db import IntegrityError
ModuleNotFoundError: No module named 'django'
Traceback (most recent call last):
  File "manage.py", line 4, in <module>
    from django.db import IntegrityError
ModuleNotFoundError: No module named 'django'
Quitting Circus
Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/circusctl", line 7, in <module>
    from circus.circusctl import main
ModuleNotFoundError: No module named 'circus'
Calling updateCronCircus to restart Circus...
Starting Fermentrack supervisor: circusd: Traceback (most recent call last):
  File "/home/fermentrack/venv/bin/circusd", line 7, in <module>
    from circus.circusd import main
ModuleNotFoundError: No module named 'circus'
failed, please see logfile.

Done! Exiting.
Click to expand...

Weird. It's like your venv doesn't have pip. VERY STRANGE. This is on your Stretch install?

Let's just nuke your venv & rebuild it. If you are on Stretch, log in via ssh and run the following:

sudo apt-get install -y libzmq5-dev
sudo su fermentrack
cd "/home/fermentrack"
rm -rf ~/venv/
python3.7 -m venv /home/fermentrack/venv
rm /home/fermentrack/venv/bin/python3
ln -s /home/fermentrack/venv/bin/python3.7 /home/fermentrack/venv/bin/python3
source /home/fermentrack/venv/bin/activate
pip install -vv --no-binary pyzmq pyzmq
/home/fermentrack/venv/bin/python3 -m pip install numpy scipy matplotlib ipython jupyter pandas sympy nose

...then re-run the "fix environment" script to clean everything else up.
 
Thorrak said:
Weird. It's like your venv doesn't have pip. VERY STRANGE. This is on your Stretch install?

Let's just nuke your venv & rebuild it. If you are on Stretch, log in via ssh and run the following:

sudo apt-get install -y libzmq5-dev
sudo su fermentrack
cd "/home/fermentrack"
rm -rf ~/venv/
python3.7 -m venv /home/fermentrack/venv
rm /home/fermentrack/venv/bin/python3
ln -s /home/fermentrack/venv/bin/python3.7 /home/fermentrack/venv/bin/python3
source /home/fermentrack/venv/bin/activate
pip install -vv --no-binary pyzmq pyzmq
/home/fermentrack/venv/bin/python3 -m pip install numpy scipy matplotlib ipython jupyter pandas sympy nose

...then re-run the "fix environment" script to clean everything else up.
Click to expand...
My RPi was on Stretch. Then I updated to the newest Fermentrack and started to get the 502 bad gateway error. Then tried the "fix environment" script multiple times. It appeared to hang on the part involving "stopping circus", so I killed it each time. Then I saw something suggesting that I update to Buster so I did that. Then I ran the old "fix environment" script, which resulted in the error I posted yesterday afternoon. Then this morning I ran the new "fix environment" script, which resulted in the error posted above. Should I do the steps you describe above to nuke/rebuild the venv on my current Buster install?
 
adman said:
My RPi was on Stretch. Then I updated to the newest Fermentrack and started to get the 502 bad gateway error. Then tried the "fix environment" script multiple times. It appeared to hang on the part involving "stopping circus", so I killed it each time. Then I saw something suggesting that I update to Buster so I did that. Then I ran the old "fix environment" script, which resulted in the error I posted yesterday afternoon. Then this morning I ran the new "fix environment" script, which resulted in the error posted above. Should I do the steps you describe above to nuke/rebuild the venv on my current Buster install?
Click to expand...

Buster should be fine out of the box, but yes - you can run those steps to rebuild your venv and should be fine
 
Thorrak said:
Buster should be fine out of the box, but yes - you can run those steps to rebuild your venv and should be fine
Click to expand...
Hot diggity. Took a while to rebuild everything (particularly numpy, I think that took 20+ minutes), but nuking/rebuilding the venv and then re-running the fix environment script fixed stuff. I'm back, baby!
 
adman said:
Hot diggity. Took a while to rebuild everything (particularly numpy, I think that took 20+ minutes), but nuking/rebuilding the venv and then re-running the fix environment script fixed stuff. I'm back, baby!
Click to expand...
Reading this, I realize that I didn’t say “THANKS!” to @Thorrak—not only for personally troubleshooting my issue, but for making this excellent tool in the first place. Thanks again, good sir!
 
adman said:
Reading this, I realize that I didn’t say “THANKS!” to @Thorrak—not only for personally troubleshooting my issue, but for making this excellent tool in the first place. Thanks again, good sir!
Click to expand...

Fermentrack is without question an awesome project - John's work to create Fermentrack has been great. I used 'BrewPi' for a bit, but then they went down the Photon path and felt to me to go more commercial than open source. Fermentrack, at the time, was, in my opinion, better then Brewpi, a 'bug or two' not withstanding (not sure it could be called a 'bug', but not showing when heating or cooling was taking place was frustrating - that, obviously, has since been fixed), than BrewPi (that was two or so years ago), and as of now, it's simply awesome. Way better than it was two years ago, and it was really good then. The way John has integrated the Tilt sensors with it - just awesome.
 
Last edited:
adman said:
Reading this, I realize that I didn’t say “THANKS!” to @Thorrak—not only for personally troubleshooting my issue, but for making this excellent tool in the first place. Thanks again, good sir!
Click to expand...
Cougar281 said:
Fermentrack is without question an awesome project - John's work to create Fermentrack has been great. I used 'BrewPi' for a bit, but then they went down the Photon path and felt to me to go more commercial than open source. Fermentrack, at the time, was, in my opinion, better then Brewpi, a 'bug or two' not withstanding (not sure it could be called a 'bug', but not showing when heating or cooling was taking place was frustrating - that, obviously, has since been fixed), than BrewPi (that was two or so years ago), and as of now, it's simply awesome. Way better than it was two years ago, and it was really good then. The way John has integrated the Tilt sensors with it - just awesome.
Click to expand...

I'm glad you guys like the project! I'm always happy to help with bugs/feature requests - feel free to reach out if you find any other issues, or have any feature requests. ;)
 
Thorrak said:
I'm glad you guys like the project! I'm always happy to help with bugs/feature requests - feel free to reach out if you find any other issues, or have any feature requests. ;)
Click to expand...

On that note.. :) Is there a way that I've missed to export/save/print the graph and any relevant data (like maybe OG, FG, ABV, etc) for a logged fermentation? I typically put my brew sheets into a folder, and it would be nice to be able to save a copy out of Fermentrack to include.

But honestly,probably the biggest benefit is that because of the ESP8266 'BrewPi' firmware, along with the TiltBridge, you don't NEED to use a Raspberry Pi - There's nothing wrong with Raspberry Pis, but if you're like me, you want a 'recovery plan'... That's 'doable' with a RPi, but not 'easy'. Or quick. The only reason I used a RPi two years ago was because that was the only way I could get the Tilt data into Fermentrack. Fast forward to now with the TiltBridge, I've created a Ubuntu based VM to run Fermentrack, so when upgrade time comes, I can just shut down, take a snapshot, boot up and then do the upgrade (You CAN take snapshots while a machine is running, but if it's an option, shutting down first is cleaner) - if something goes horribly sideways, just revert to snapshot and continue on as if nothing happened.
 
Last edited:
I went to go turn on my Fermentrack setup to ferment for the first time in a while and couldn't connect to it via anything but SSH because I was getting a bad gateway error if I tried to connect via the web interface. Came on here and was able to successfully use the script that repaired the issue.

My issue is that now when I try to create a beer and log it errors out and displays this:
Capturrqwtaye.JPG


Also I have tried completing the final Django update step as the banner notification indicates needs to be done, but no matter what the banner notification is still present. Does this mean that the step did not complete successfully? I would think that if you had completed it successfully the banner notification would go away.
Capturddddde.JPG
 
I'm trying to set up my Arduino BrewPi running Fermentrack, and am running into a snag. I have Fermentrack running just fine on a Pi 3B, and have an ESP8266 BrewPi running great through it. After flashing the Uno R3 with the latest BrewPi Remix, the Arduino boots up. However, unlike the ESP8266, when I go to configure sensors and pins, I don't see the OneWire options or heating/cooling, I just see a list of Pin 5(), 6, 2, and 10. When I try and assign either 2 or 10 ('cuz I read elsewhere that 5 and 6 are the heat/cool relays) to the probes, it tells me: "Failed to write the configuration to the controller. If this continues, try resetting the EEPROM on the controller. " I tried resetting EEPROM, no avail.

Any suggestions? My wiring looks fine as far as I can tell, but since that's the most likely source, I'll try taking that apart piece by piece and see if that's the issue.
 
Last edited:
Hi @Thorrak I'm having an issue getting the heating to work. I've described my issue below and what steps I've taken to troubleshoot. Is there maybe something simple/obvious that I should try first?

My Setup:

Issue:
  • When fermentrack initiates heat mode, it doesn't send a signal to the heating relay (typically a red led should light at that relay when the heat is engaged).

What changed recently:
  • I'm not sure if this started to happen before or after I updated fermentrack this week, because I haven't needed the heat function for a month or so.
  • Updated fermentrack and receiving the "Fermentrack has upgraded to a newer copy of Django which requires an additional step to complete. Click here to trigger this step and restart Fermentrack." banner.
Troubleshooting:
Step 1: Double checked and cooling mode was working properly in initial configuration (as-built and configured last year and working up until now).

Step 2: I initially assumed either relay or board went bad, so I swapped the pin configuration (D5 and D0) in fermentrack for heating and cooling relays (so that opposite relays would be triggered for heating and cooling). Upon initiating cooling in fermentrack, the cooling relay circuit was closed. Upon initiating heating in fermentrack, no response. This confirmed both relays and board working properly.

Step 3: For the hell of it, I opened the temperature controller and swapped the pins around a bit between cooling, heating, door pins. Tried restarting fermentrack. Tried power cycling the controller. Same response every time, cooling working fine but no heat signal being sent.
 

Attachments

  • update log.txt
    7 KB · Views: 1
Hello,

Having issues with adding configuring devices on a new setup.
Raspberry Pi running a fresh install (Buster) and using Arduino controllers. Ran Fermentrack one line install, found both Arduino's I'm using and was able to flash both of them via Fermentrack.

I get to the Configure Sensors screen, try to assign sensors and continue getting "Failed to write the configuration to the controller. If this continues, try resetting the EEPROM on the controller. "

I've reset the EEPROM numerous times from Fermentrack, checked my wiring several times, restarted, etc. Here's what the error log shows:
"
May 10 2020 18:14:30 Connection type Serial selected. Opening serial port.
May 10 2020 18:14:30 Connected via serial to port /dev/ttyUSB0
May 10 2020 18:14:30 Notification: Script started, with no active beer being logged
May 10 2020 18:14:40 Checking software version on controller...
May 10 2020 18:14:40 Found BrewPi v0.2.12 build 8d36524, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0

May 10 2020 18:14:40 BrewPi version received was 0.2.12 which this script supports in 'legacy' branch mode.
May 10 2020 18:14:40 Bound to TCP socket on port 2788, interface localhost
May 10 2020 18:14:41 Installed devices received: []
May 10 2020 18:14:41 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 10 2020 18:25:11 Resetting controller to factory defaults
May 10 2020 18:25:13 Controller debug message: INFO MESSAGE 15: EEPROM initialized
May 10 2020 18:25:13 Installed devices received: []
May 10 2020 18:25:13 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 10 2020 18:25:13 Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
May 10 2020 18:25:14 Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
May 10 2020 18:25:14 Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMax = 90.0
May 10 2020 18:25:15 Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMin = 20.
May 10 2020 18:30:45 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 2, "x": "1"}
May 10 2020 18:30:48 Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
May 10 2020 18:30:48 Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
May 10 2020 18:30:48 Installed devices received: []
May 10 2020 18:30:48 Controller debug message: ERROR 3: Device definition update specification is invalid
May 10 2020 18:30:48 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]"

Thanks you.
 
alxman2021 said:
Hi @Thorrak I'm having an issue getting the heating to work. I've described my issue below and what steps I've taken to troubleshoot. Is there maybe something simple/obvious that I should try first?

My Setup:

Issue:
  • When fermentrack initiates heat mode, it doesn't send a signal to the heating relay (typically a red led should light at that relay when the heat is engaged).

What changed recently:
  • I'm not sure if this started to happen before or after I updated fermentrack this week, because I haven't needed the heat function for a month or so.
  • Updated fermentrack and receiving the "Fermentrack has upgraded to a newer copy of Django which requires an additional step to complete. Click here to trigger this step and restart Fermentrack." banner.
Troubleshooting:
Step 1: Double checked and cooling mode was working properly in initial configuration (as-built and configured last year and working up until now).

Step 2: I initially assumed either relay or board went bad, so I swapped the pin configuration (D5 and D0) in fermentrack for heating and cooling relays (so that opposite relays would be triggered for heating and cooling). Upon initiating cooling in fermentrack, the cooling relay circuit was closed. Upon initiating heating in fermentrack, no response. This confirmed both relays and board working properly.

Step 3: For the hell of it, I opened the temperature controller and swapped the pins around a bit between cooling, heating, door pins. Tried restarting fermentrack. Tried power cycling the controller. Same response every time, cooling working fine but no heat signal being sent.
Click to expand...

When it is supposed to be heating, what does the LCD say? (either the real LCD or the "virtual" LCD) Does it say "Heating for XhXXm" or something else?

Heating is entirely handled on the controller, so there is no reason that an update to Fermentrack should impact it. It has to either be firmware related or hardware related.
 
bmcgarry said:
Hello,

Having issues with adding configuring devices on a new setup.
Raspberry Pi running a fresh install (Buster) and using Arduino controllers. Ran Fermentrack one line install, found both Arduino's I'm using and was able to flash both of them via Fermentrack.

I get to the Configure Sensors screen, try to assign sensors and continue getting "Failed to write the configuration to the controller. If this continues, try resetting the EEPROM on the controller. "

I've reset the EEPROM numerous times from Fermentrack, checked my wiring several times, restarted, etc. Here's what the error log shows:
"
May 10 2020 18:14:30 Connection type Serial selected. Opening serial port.
May 10 2020 18:14:30 Connected via serial to port /dev/ttyUSB0
May 10 2020 18:14:30 Notification: Script started, with no active beer being logged
May 10 2020 18:14:40 Checking software version on controller...
May 10 2020 18:14:40 Found BrewPi v0.2.12 build 8d36524, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0

May 10 2020 18:14:40 BrewPi version received was 0.2.12 which this script supports in 'legacy' branch mode.
May 10 2020 18:14:40 Bound to TCP socket on port 2788, interface localhost
May 10 2020 18:14:41 Installed devices received: []
May 10 2020 18:14:41 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 10 2020 18:25:11 Resetting controller to factory defaults
May 10 2020 18:25:13 Controller debug message: INFO MESSAGE 15: EEPROM initialized
May 10 2020 18:25:13 Installed devices received: []
May 10 2020 18:25:13 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 10 2020 18:25:13 Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
May 10 2020 18:25:14 Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
May 10 2020 18:25:14 Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMax = 90.0
May 10 2020 18:25:15 Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMin = 20.
May 10 2020 18:30:45 Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 2, "x": "1"}
May 10 2020 18:30:48 Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
May 10 2020 18:30:48 Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
May 10 2020 18:30:48 Installed devices received: []
May 10 2020 18:30:48 Controller debug message: ERROR 3: Device definition update specification is invalid
May 10 2020 18:30:48 Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]"

Thanks you.
Click to expand...

Which Arduino firmware are you using?
 
@Thorrak Not sure if you saw this, but still unsure how to get the ability to log back after doing the update.
Guper said:
I went to go turn on my Fermentrack setup to ferment for the first time in a while and couldn't connect to it via anything but SSH because I was getting a bad gateway error if I tried to connect via the web interface. Came on here and was able to successfully use the script that repaired the issue.

My issue is that now when I try to create a beer and log it errors out and displays this:
View attachment 678444

Also I have tried completing the final Django update step as the banner notification indicates needs to be done, but no matter what the banner notification is still present. Does this mean that the step did not complete successfully? I would think that if you had completed it successfully the banner notification would go away.
View attachment 678445
Click to expand...
 
Guper said:
@Thorrak Not sure if you saw this, but still unsure how to get the ability to log back after doing the update.
Click to expand...

Hey there - Sorry, I didn't see this! The error that you're getting is as a result of the issue the banner is trying to get you to fix. Let's see if we can figure out why that script didn't fix everything.


Can you click the link in the banner once more, give it ~1 minute or so, then do the following:

1. Log into Fermentrack
2. Click the "?" in the upper right hand corner of the screen
3. Click the "Upgrade Log" link at the bottom
4. Copy & Paste this into a private message & send to me?
 
Thorrak said:
I just pushed what I think should fix your issue @bmcgarry . Update to the latest Fermentrack dev branch and you should be good to go.
Click to expand...
Thank you so much for the quick response. Unfortunately, no dice. Still does the same thing.

Code: 
 May 12 2020 02:05:32   Connection type Serial selected. Opening serial port.
 May 12 2020 02:05:32   Connected via serial to port /dev/ttyUSB0
 May 12 2020 02:05:32   Notification: Script started, with no active beer being logged
 May 12 2020 02:05:42   Checking software version on controller...
 May 12 2020 02:05:42   Found BrewPi v0.2.12 build 8d36524, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0

 May 12 2020 02:05:42   BrewPi version received was 0.2.12 which this script supports in 'legacy' branch mode.
 May 12 2020 02:05:42   Bound to TCP socket on port 2788, interface localhost
 May 12 2020 02:05:43   Installed devices received: []
 May 12 2020 02:05:43   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
 May 12 2020 02:09:04   Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 2, "x": "1"}
 May 12 2020 02:09:06   Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
 May 12 2020 02:09:06   Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
 May 12 2020 02:09:06   Installed devices received: []
 May 12 2020 02:09:06   Controller debug message: ERROR 3: Device definition update specification is invalid
 May 12 2020 02:09:09   Installed devices received: []
 May 12 2020 02:09:09   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
 May 12 2020 02:09:34   Resetting controller to factory defaults
 May 12 2020 02:09:36   Controller debug message: INFO MESSAGE 15: EEPROM initialized
 May 12 2020 02:09:36   Installed devices received: []
 May 12 2020 02:09:36   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
 May 12 2020 02:09:36   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 May 12 2020 02:09:37   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
 May 12 2020 02:09:37   Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMax = 90.0
 May 12 2020 02:09:38   Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMin = 20.
 May 12 2020 02:11:22   Connection type Serial selected. Opening serial port.
 May 12 2020 02:11:22   Connected via serial to port /dev/ttyUSB0
 May 12 2020 02:11:22   Notification: Script started, with no active beer being logged
 May 12 2020 02:11:32   Checking software version on controller...
 May 12 2020 02:11:32   Found BrewPi v0.2.12 build 8d36524, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0

 May 12 2020 02:11:32   BrewPi version received was 0.2.12 which this script supports in 'legacy' branch mode.
 May 12 2020 02:11:32   Bound to TCP socket on port 2788, interface localhost
 May 12 2020 02:11:32   Installed devices received: []
 May 12 2020 02:11:32   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
 May 12 2020 02:13:01   Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 19, "x": "1"}
 May 12 2020 02:13:03   Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
 May 12 2020 02:13:03   Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
 May 12 2020 02:13:03   Installed devices received: []
 May 12 2020 02:13:03   Controller debug message: ERROR 3: Device definition update specification is invalid
 May 12 2020 02:13:03   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
 May 12 2020 02:13:17   Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 6, "x": "1"}
 May 12 2020 02:13:19   Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
 May 12 2020 02:13:19   Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
 May 12 2020 02:13:19   Installed devices received: []
 May 12 2020 02:13:19   Controller debug message: ERROR 3: Device definition update specification is invalid
 May 12 2020 02:13:19   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
 
bmcgarry said:
Thank you so much for the quick response. Unfortunately, no dice. Still does the same thing.

Code: 
 May 12 2020 02:05:32   Connection type Serial selected. Opening serial port.
May 12 2020 02:05:32   Connected via serial to port /dev/ttyUSB0
May 12 2020 02:05:32   Notification: Script started, with no active beer being logged
May 12 2020 02:05:42   Checking software version on controller...
May 12 2020 02:05:42   Found BrewPi v0.2.12 build 8d36524, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0

May 12 2020 02:05:42   BrewPi version received was 0.2.12 which this script supports in 'legacy' branch mode.
May 12 2020 02:05:42   Bound to TCP socket on port 2788, interface localhost
May 12 2020 02:05:43   Installed devices received: []
May 12 2020 02:05:43   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 12 2020 02:09:04   Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 2, "x": "1"}
May 12 2020 02:09:06   Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
May 12 2020 02:09:06   Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
May 12 2020 02:09:06   Installed devices received: []
May 12 2020 02:09:06   Controller debug message: ERROR 3: Device definition update specification is invalid
May 12 2020 02:09:09   Installed devices received: []
May 12 2020 02:09:09   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 12 2020 02:09:34   Resetting controller to factory defaults
May 12 2020 02:09:36   Controller debug message: INFO MESSAGE 15: EEPROM initialized
May 12 2020 02:09:36   Installed devices received: []
May 12 2020 02:09:36   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 12 2020 02:09:36   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
May 12 2020 02:09:37   Controller debug message: INFO MESSAGE 12: Received new setting: tempFormat = F
May 12 2020 02:09:37   Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMax = 90.0
May 12 2020 02:09:38   Controller debug message: INFO MESSAGE 12: Received new setting: tempSetMin = 20.
May 12 2020 02:11:22   Connection type Serial selected. Opening serial port.
May 12 2020 02:11:22   Connected via serial to port /dev/ttyUSB0
May 12 2020 02:11:22   Notification: Script started, with no active beer being logged
May 12 2020 02:11:32   Checking software version on controller...
May 12 2020 02:11:32   Found BrewPi v0.2.12 build 8d36524, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0

May 12 2020 02:11:32   BrewPi version received was 0.2.12 which this script supports in 'legacy' branch mode.
May 12 2020 02:11:32   Bound to TCP socket on port 2788, interface localhost
May 12 2020 02:11:32   Installed devices received: []
May 12 2020 02:11:32   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 12 2020 02:13:01   Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 19, "x": "1"}
May 12 2020 02:13:03   Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
May 12 2020 02:13:03   Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
May 12 2020 02:13:03   Installed devices received: []
May 12 2020 02:13:03   Controller debug message: ERROR 3: Device definition update specification is invalid
May 12 2020 02:13:03   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
May 12 2020 02:13:17   Received applyDevice request, updating to: {"i": 0, "c": 1, "b": 0, "f": 5, "h": 1, "p": 6, "x": "1"}
May 12 2020 02:13:19   Device updated to: {"i":0,"t":0,"c":0,"b":0,"f":0,"h":0,"d":0,"p":0}
May 12 2020 02:13:19   Controller debug message: ERROR 8: Cannot assign device type 1 to hardware 1
May 12 2020 02:13:19   Installed devices received: []
May 12 2020 02:13:19   Controller debug message: ERROR 3: Device definition update specification is invalid
May 12 2020 02:13:19   Available devices received: [{"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 2, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 5, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 6, "x": 1}, {"i": -1, "t": 0, "c": 1, "b": 0, "f": 0, "h": 1, "d": 0, "p": 19, "x": 1}]
Click to expand...

What function are you trying to assign - and to what device? Re-reading the logs, it looks like you're trying to assign "f": 5 to "h": 1 - that is, you're trying to assign the "Fridge Sensor" function to a plain, non-OneWire pin.

Separately, are you intending to use the RevC shield definition firmware? That is the "shift register" LCD implementation.
 
Thorrak said:
Hey there - Sorry, I didn't see this! The error that you're getting is as a result of the issue the banner is trying to get you to fix. Let's see if we can figure out why that script didn't fix everything.


Can you click the link in the banner once more, give it ~1 minute or so, then do the following:

1. Log into Fermentrack
2. Click the "?" in the upper right hand corner of the screen
3. Click the "Upgrade Log" link at the bottom
4. Copy & Paste this into a private message & send to me?
Click to expand...


No worries! Here's the info you asked for:

"

Rebuilding app Authentication and Authorization...
Rebuilding model <class 'django.contrib.auth.models.Permission'> - FK Check Disabled: True
Rebuilding model <class 'django.contrib.auth.models.Group_permissions'> - FK Check Disabled: True
Rebuilding model <class 'django.contrib.auth.models.Group'> - FK Check Disabled: True
Rebuilding model <class 'django.contrib.auth.models.User_groups'> - FK Check Disabled: True
Rebuilding model <class 'django.contrib.auth.models.User_user_permissions'> - FK Check Disabled: True
Rebuilding model <class 'django.contrib.auth.models.User'> - FK Check Disabled: True
Rebuilding app Content Types...
Rebuilding model <class 'django.contrib.contenttypes.models.ContentType'> - FK Check Disabled: True
Rebuilding app Sessions...
Rebuilding model <class 'django.contrib.sessions.models.Session'> - FK Check Disabled: True
Rebuilding app Messages...
Rebuilding app Static Files...
Rebuilding app App...
Rebuilding model <class 'app.models.BrewPiDevice'> - FK Check Disabled: True
Rebuilding model <class 'app.models.Beer'> - FK Check Disabled: True
Rebuilding model <class 'app.models.FermentationProfile'> - FK Check Disabled: True
Rebuilding model <class 'app.models.FermentationProfilePoint'> - FK Check Disabled: True
Rebuilding model <class 'app.models.OldControlConstants'> - FK Check Disabled: True
Rebuilding model <class 'app.models.NewControlConstants'> - FK Check Disabled: True
Rebuilding app Firmware_Flash...
Rebuilding model <class 'firmware_flash.models.DeviceFamily'> - FK Check Disabled: True
Rebuilding model <class 'firmware_flash.models.Firmware'> - FK Check Disabled: True
Rebuilding model <class 'firmware_flash.models.Board'> - FK Check Disabled: True
Rebuilding model <class 'firmware_flash.models.FlashRequest'> - FK Check Disabled: True
Rebuilding model <class 'firmware_flash.models.Project'> - FK Check Disabled: True
Traceback (most recent call last):
File "manage.py", line 25, in <module>
execute_from_command_line(sys.argv)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/base.py", line 328, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/base.py", line 369, in execute
output = self.handle(*args, **options)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 233, in handle
fake_initial=fake_initial,
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 247, in apply_migration
migration_recorded = True
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/sqlite3/schema.py", line 35, in __exit__
self.connection.check_constraints()
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/sqlite3/base.py", line 331, in check_constraints
bad_value, referenced_table_name, referenced_column_name
django.db.utils.IntegrityError: The row in table 'firmware_flash_firmware' with primary key '17' has an invalid foreign key: firmware_flash_firmware.project_id contains a value 'project_id' that does not have a corresponding value in firmware_flash_project.id.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 86, in _execute
return self.cursor.execute(sql, params)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/sqlite3/base.py", line 396, in execute
return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: no such table: firmware_flash_project

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

Traceback (most recent call last):
File "manage.py", line 29, in <module>
execute_from_command_line(['manage.py', 'fix_sqlite_for_django_2'])
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/base.py", line 328, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/core/management/base.py", line 369, in execute
output = self.handle(*args, **options)
File "/home/fermentrack/fermentrack/app/management/commands/fix_sqlite_for_django_2.py", line 97, in handle
self.fix_sqlite_for_django_2()
File "/home/fermentrack/fermentrack/app/management/commands/fix_sqlite_for_django_2.py", line 91, in fix_sqlite_for_django_2
editor._remake_table(model)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/sqlite3/schema.py", line 287, in _remake_table
self.quote_name(model._meta.db_table),
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 142, in execute
cursor.execute(sql, params)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 100, in execute
return super().execute(sql, params)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 68, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 86, in _execute
return self.cursor.execute(sql, params)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/utils.py", line 86, in _execute
return self.cursor.execute(sql, params)
File "/home/fermentrack/venv/lib/python3.7/site-packages/django/db/backends/sqlite3/base.py", line 396, in execute
return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: firmware_flash_project
ok
ok

"
 
Guper said:
No worries! Here's the info you asked for:

<massive log file>
Click to expand...

Try updating to the latest dev branch I pushed out a few minutes ago and re-run the fix_sqlite script by clicking the banner. It's not a perfect fix as it only works for the firmware_flash objects, but I'm hoping those are the only ones impacted by this specific issue.

If that doesn't work, grab the upgrade log again and send it to me in a private message. The logs are pretty long, unfortunately - no need to clutter this thread. :)
 
Hello friends, I developed a low cost project for fermentation and cold control. I decided to do it step by step after several friends set up and gave me positive feedback on the system.

I will leave some photos and the link of the channel I created on Youtube for this and other projects. If you like it please leave your feedback. I hope it helps. Hug brothers !!



Screenshot_20200512-223829_Blynk.jpg

Screenshot_20200512-224451_Blynk.jpg
 
Thorrak said:
When it is supposed to be heating, what does the LCD say? (either the real LCD or the "virtual" LCD) Does it say "Heating for XhXXm" or something else?

Heating is entirely handled on the controller, so there is no reason that an update to Fermentrack should impact it. It has to either be firmware related or hardware related.
Click to expand...

The LCD says 'heating for XhXXm' like it should.

Okay, I will try first re-flashing the firmware and then I think I have a spare esp8266 board I can swap out.
 
hfagner said:
Hello friends, I developed a low cost project for fermentation and cold control. I decided to do it step by step after several friends set up and gave me positive feedback on the system.

I will leave some photos and the link of the channel I created on Youtube for this and other projects. If you like it please leave your feedback. I hope it helps. Hug brothers !!



View attachment 680117
View attachment 680116
Click to expand...


Looks nice!

You might want to start a new thread. This one should stay focused on @Thorrak's Fermentrack. Or you could ask a mod to move your post to it's own thread.
 
Last edited:
Thorrak said:
Try updating to the latest dev branch I pushed out a few minutes ago and re-run the fix_sqlite script by clicking the banner. It's not a perfect fix as it only works for the firmware_flash objects, but I'm hoping those are the only ones impacted by this specific issue.

If that doesn't work, grab the upgrade log again and send it to me in a private message. The logs are pretty long, unfortunately - no need to clutter this thread. :)
Click to expand...


I think I PM'd you, but I'm not sure because it's "start a conversation" rather than send a message, but I'm assuming that's equivalent for HBT.
 
Hi
Haven't been brewing for a while so my Fermentrack hasent been used. Booted it up yesterday and it worked fine. Did an upgrade and after that I only get a 502 bad gateway error when I try to connect. Tried to run the fix environment scrip and also the other stuff that was mentioned but didnt work.Anything I can do to fix it? I have an image of the sd card with the older version so if I cant get it to work I can flash that :)
 
Following up on megatrond's post, I ran an upgrade of the Dev branch yesterday. My Pi's been running at a solid 75-100% CPU usage since. Running htop shows that it's the fermentrack user's processes. Does the latest push require a lot of updating that it would take almost 24hrs? It's been a bit since my last update, and when trying to access the site, I'm getting a timeout error.
 
Guper said:
I think I PM'd you, but I'm not sure because it's "start a conversation" rather than send a message, but I'm assuming that's equivalent for HBT.
Click to expand...

That’s the PM function - reply incoming!


MegaTrond said:
Hi
Haven't been brewing for a while so my Fermentrack hasent been used. Booted it up yesterday and it worked fine. Did an upgrade and after that I only get a 502 bad gateway error when I try to connect. Tried to run the fix environment scrip and also the other stuff that was mentioned but didnt work.Anything I can do to fix it? I have an image of the sd card with the older version so if I cant get it to work I can flash that :)
Click to expand...

I’ve found a couple of issues that have popped up with some of the precompiled binaries for some of the packages Fermentrack depends on, so I rewrote the “fix-environment” script this weekend to recompile them from source instead. Try re-running the fix environment script now.


HarlemBrewDoug said:
Following up on megatrond's post, I ran an upgrade of the Dev branch yesterday. My Pi's been running at a solid 75-100% CPU usage since. Running htop shows that it's the fermentrack user's processes. Does the latest push require a lot of updating that it would take almost 24hrs? It's been a bit since my last update, and when trying to access the site, I'm getting a timeout error.
Click to expand...

I can see it taking up to an hour on Pi Zeros, but 75-100% for 24 hours seems incorrect.

Try restarting your Pi, logging in via SSH, then run the command discussed in this issue on GitHub.
 
Thanks @Thorrak :)
Fermentrack is up and running again but I have this message on top: Fermentrack has upgraded to a newer copy of Django which requires an additional step to complete. Click here to trigger this step and restart Fermentrack.
Clicked on the link and waited several minutes but nothing seems to happen. Waited some more, did a reboot and tried again. Same thing.....
 
MegaTrond said:
Thanks @Thorrak :)
Fermentrack is up and running again but I have this message on top: Fermentrack has upgraded to a newer copy of Django which requires an additional step to complete. Click here to trigger this step and restart Fermentrack.
Clicked on the link and waited several minutes but nothing seems to happen. Waited some more, did a reboot and tried again. Same thing.....
Click to expand...
This is the same issue as @Guper - I’m trying to figure out a fix. Can you click the link in the banner once more, give it ~1 minute or so, then do the following:

1. Log into Fermentrack
2. Click the "?" in the upper right hand corner of the screen
3. Click the "Upgrade Log" link at the bottom
4. Copy & Paste this into a private message & send to me?

The log is going to be really long, hence the PM. :)
 
How do I get BrewFlasher to run? Downloaded zip file from here Unzipped and extracted files to the desktop.Capture 27.JPG
Not sure which file to click on to open the program. When I click on some of the files I get a command prompt window that loads files then disappears.not sure what I'm doing wrong
EDIT : Nevermind- I found the post where I asked this same question in another thread-
 
Last edited:

Similar threads

duncan.brown
Brewery Dashboard
Replies
18
Views
2K
suprchunk
suprchunk
T
Homebrew interface built in Qt for Raspberry Pi
Replies
9
Views
3K
nordork
N
M
Replacement firmware for iSpindel (GravityMon)
10 11 12
Replies
450
Views
29K
dtashmore547
D
LBussy
BrewPi Remix – What’s Old is New Again
22 23 24
Replies
920
Views
60K
day_trippr
day_trippr
S
My fermentrack/brewpi-esp8266 Build
Replies
24
Views
5K
bcowmoo
bcowmoo
BrewSwag 300

Latest posts

Back
Top