Beta releases now available

Hi Guys,

A new firmware release is coming. And it has been a while since the last one.

We would like to speed up our release cycle and a way to achieve that is to start providing beta releases: firmware and other code which we think is ready for release, but has not had enough testing to be merged into our stable master branch.

Warning

The beta releases are not well tested and might be unstable. The whole reason we are doing beta releases is to get more testing to ensure it is stable. It is not recommended to run a beta release with your carefully brewed beer. Please only use it in a test run.

Beta testers wanted

So you would like to help us test, great! See the bottom of this post on how to get the beta release. Please use this topic to give feedback on the release. If you encounter any problems on the beta release, please keep them in this topic.

Please also post positive feedback! If you encountered a problem before, let us know if it is solved in the beta release. Please see the release notes for what should be fixed.

How to install the beta release?

I have refactored our update system to make it easy to install a specific release. So to get the beta, please run the following commands:

cd ~/brewpi-tools
sudo python updater.py --ask

If you use the --ask option, the updater will ask you which branches/versions you would like to install. For the script, web interface and firmware. You should pick beta on each.

Example:

For the web interface:

Available branches on the remote 'github' for /var/www:
[0] beta
[1] develop
[2] feature/chart-export
[3] feature/notifications
[4] legacy
[5] master
[6] Skip updating this repository
Enter the number of the branch you wish to update [beta]: 0

For the firmware:

 Current firmware version on controller: 0.4.3a

Checking GitHub for available release...

Available releases:

[0] 0.4.3beta3
[1] 0.4.2
[2] 0.4.1
[3] 0.4.0
[4] 0.3.0a
[5] 0.2.11
[10] Cancel firmware update
Enter the number [0-10] of the version you want to program [default = 1 (0.4.2)]0

Arduino

As with all coming firmware updates, this is not for Arduino. We cannot fit our current firmware into the Arduino and Arduino users should stay stick with the legacy branch. I will merge some of the improvements in the firmware update process into Arduino, but if you are already have yours up and running, you probably won’t notice.

Final note

Please note that we will release the firmware soon if we don’t encounter further issues. If you don’t want any hassle, just wait for the stable release and leave the beta testing to others.

Cheers!

2 Likes

Hi @elco,

I’ve tried a number of times to upgrade to the beta release without luck.

I can use the brewpi-tools/updater.py script to update /home/brewpi, /var/www/html and the firmware. But upgrading to 0.4.3beta3 of the firmware leaves the BrewPi in a broken state.

The display just glows white, a blank screen. The controller then becomes unresponsive with the following output from brewpi-tools/updater.py:

The update script can automatically check your controller firmware version and program it with the latest release on GitHub, would you like to do this now? [Y/n]:
Stopping any running instances of BrewPi to check/update controller…

Checking current firmware version…
Mar 15 2016 19:43:32 Opening serial port
Unable to receive version from controller.
Is your controller unresponsive and do you wish to try restoring your firmware? [y/N]:

I can recover the BrewPi by resetting with the setup button pressed until I receive the yellow light and flash back to 0.4.2 successfully. But I cannot get 0.4.3beta3 installed and working.

I have tried leaving the other software unchanged:

  • /home/brewpi to develop
  • /var/www/html to master
  • Firmware to 0.4.3beta3

I have tried to run everything at beta:

  • /home/brewpi to beta
  • /var/www/html to beta
  • Firmware to 0.4.3beta3

Either results in an unresponsive BrewPi with a blank, white, screen.

Are there any logs I can provide to help or diagnostics you’d like me to run?

Cheers,
Bill

Hi Bill,

Can you post the log for the firmware update?
Updating to beta will only work if you update the script to beta as well (currently equal to develop though).

You can do just the firmware update with:

cd /home/brewpi/utils
sudo python updateFirmware.py --beta

Cheers

To be clear, this is still with the single-control loop web-interface? No changes there.

Hi Elco,

I didn’t pay attention to what version was taken, but my brewpi-tools/update.py was updated. I remember because it made me run it a second time after fetching a new/other version.

Are you after a log file, or just the output of the updateFirmware.py run? I’m not sure where log files are stored, but here is what I ran and the results.

pi@raspberrypi:~ $ cd ~brewpi/utils
pi@raspberrypi:/home/brewpi/utils $ sudo python updateFirmware.py --beta

Stopping any running instances of BrewPi to check/update controller…
Quit message sent to BrewPi instance with pid 1007!

Checking current firmware version…
Mar 15 2016 21:10:08 Opening serial port
Found BrewPi v0.4.2 build 0.4.2-0-g446b226, running on a Particle Photon with a V2 shield on port /dev/ttyACM0

Current firmware version on controller: 0.4.2

Checking GitHub for available release…

Available releases:

[0] 0.4.3beta3
[1] 0.4.2
[2] 0.4.1
[3] 0.4.0
[4] 0.3.0a
[5] 0.2.11
[6] Cancel firmware update
Enter the number [0-6] of the version you want to program [default = 1 (0.4.2)]0
Would you like me to try to restore you settings after programming? [Y/n]:

Would you like me to try to restore your configured devices after programming? [Y/n]:

Downloading firmware…
downloading https://github.com/BrewPi/firmware/releases/download/0.4.3beta3/brewpi-photon-0.4.3-beta3-0-g7e11dfa.bin
Updated system firmware for the photon found in release 0.4.3beta3
downloading https://github.com/BrewPi/firmware/releases/download/0.4.3beta3/system-part1-0.4.9-photon.bin
downloading https://github.com/BrewPi/firmware/releases/download/0.4.3beta3/system-part2-0.4.9-photon.bin
Downloaded new system firmware to:

/home/brewpi/utils/downloads/0.4.3beta3/system-part1-0.4.9-photon.bin
and

/home/brewpi/utils/downloads/0.4.3beta3/system-part2-0.4.9-photon.bin

Latest firmware downloaded to /home/brewpi/utils/downloads/0.4.3beta3/brewpi-photon-0.4.3-beta3-0-g7e11dfa.bin

Updating firmware…

**** Photon Program script started ****
Settings will be restored if possible
Devices will be restored if possible
Checking old version before programming.
Mar 15 2016 21:10:38 Opening serial port
Checking current version: Found BrewPi v0.4.2 build 0.4.2-0-g446b226, running on a Particle Photon with a V2 shield on port /dev/ttyACM0

Requesting old settings from Photon…
Saved old settings to file settings-Mar-15-2016-21-10-41.json

Found a Photon and running as root/sudo, using DFU mode to flash firmware.

Trying to automatically reboot into DFU mode and update your firmware.

If the Photon does not reboot into DFU mode automatically, please put it in DFU mode manually.
Running command: sudo /usr/bin/python /home/brewpi/utils/flashDfu.py --autodfu --noreset --file=/home/brewpi/utils/downloads/0.4.3beta3
Will automatically reboot newly detected photons into DFU mode
Using local files instead of downloading a release.

Using dfu-util binary at /home/brewpi/utils/downloads/dfu-util
Detecting DFU devices
Did not find any DFU devices.
Is your Photon or Spark Core running in DFU mode (blinking yellow)?
Waiting until a DFU device is connected…
Found new serial port connected: (’/dev/ttyACM0’, ‘Particle Photon’)
Putting Photon in DFU mode
Found 1 devices: [‘2b04:d006’]
Device identified as Particle Photon
Now writing BrewPi firmware /home/brewpi/utils/downloads/0.4.3beta3/brewpi-photon-0.4.3-beta3-0-g7e11dfa.bin
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Filter on vendor = 0x2b04 product = 0xd006
Opening DFU capable USB device… ID 2b04:d006
Run-time device DFU version 011a
Found DFU: [2b04:d006] devnum=0, cfg=1, intf=0, alt=0, name="@Internal Flash /0x08000000/03016Ka,01016Kg,01064Kg,07128Kg"
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
No valid DFU suffix signature
Warning: File has no DFU suffix
DfuSe interface name: "Internal Flash "
Downloading to address = 0x080a0000, size = 86820

File downloaded successfully
Programming done

Updating firmware over DFU finished

Waiting for device to reset.
Mar 15 2016 21:11:00 Opening serial port
Warning: Cannot receive version number from controller. Your controller is either not programmed yet or running a very old version of BrewPi. It will be reset to defaults.
Resetting EEPROM to default settings
Now checking which settings and devices can be restored…
Warning: Cannot receive version number from controller after programming.
Something must have gone wrong. Restoring settings/devices settings failed.

BrewPi script will restart automatically.

BrewPi is left in a broken state again.

Cheers,
Bill

Yes.

@bill For some reason it is skipping the system image update. The mismatch with the older system image is then causing the broken state. I will try to reproduce and fix it asap. Thanks for the feedback.

Ok. Got a brew session planned for the coming weekend. Will try to install the updated this evening (leaving me enough time to rollback if needed before the weekend).

Please try again, the updater should now be fixed.

Hi Elco,

I can confirm it now works, I am running 0.4.3b. Thanks for looking into this and resolving it so quickly!

pi@raspberrypi:~ $ cd brewpi-tools/
pi@raspberrypi:~/brewpi-tools $ sudo python updater.py --ask
Using interactive (advanced) update with user input

######################################################

Welcome to the BrewPi Updater!

######################################################

Checking whether the update script is up to date
/home/pi/brewpi-tools is up-to-date.

*** Updating BrewPi script repository ***

Stopping running instances of BrewPi
You are on branch develop

Available branches on the remote ‘origin’ for /home/brewpi:
[0] beta
[1] develop
[2] feature/ejsloggingdate
[3] legacy
[4] master
[5] Skip updating this repository
Enter the number of the branch you wish to update [develop]:0
The beta branch is not your currently active branch - would you like me to check it out for you now? (Required to continue) [Y/n]:
Your branch is behind ‘origin/beta’ by 1 commit, and can be fast-forwarded.
(use “git pull” to update your local branch)
Successfully switched to beta
The latest commit in /home/brewpi is 4f3313481b5e07a8a33092780a039468b82cbbb5 on Tue, 15 Mar 2016 09:58:56
The latest commit on origin/beta is eee55d3afc96135b8383795665d36db4ebfff35b on Tue, 15 Mar 2016 23:46:36
*** Updates are available! ****
Would you like to update /home/brewpi from origin/beta [Y/n]:
Updating 4f33134…eee55d3
Fast-forward
programController.py | 4 ++±
utils/flashDfu.py | 54 ++++++++++++++++++++++++++++++++±---------------
utils/updateFirmware.py | 2 ±
3 files changed, 41 insertions(+), 19 deletions(-)
beta updated!

*** Updating BrewPi web interface repository ***
The path ‘/var/www’ does not seem to be a valid git repository
What path did you install the BrewPi web interface scripts to? /var/www/html
You are on branch master

Available branches on the remote ‘origin’ for /var/www/html:
[0] beta
[1] develop
[2] feature/chart-export
[3] feature/notifications
[4] legacy
[5] master
[6] Skip updating this repository
Enter the number of the branch you wish to update [master]:0
The beta branch is not your currently active branch - would you like me to check it out for you now? (Required to continue) [Y/n]:
Your branch is up-to-date with ‘origin/beta’.
Successfully switched to beta
The latest commit in /var/www/html is 3418ec082d881463aa3ef80984930c50fef70bd3 on Fri, 04 Dec 2015 04:02:58
The latest commit on origin/beta is 3418ec082d881463aa3ef80984930c50fef70bd3 on Fri, 04 Dec 2015 04:02:58
Your local version of /var/www/html is up to date!

One our more repositories were updated, running runAfterUpdate.sh from /home/brewpi/utils…
Installing dependencies, updating CRON and fixing file permissions…
Cleaning up BrewPi script directory…
Deleted 14 old .pyc files

***** Installing/updating required packages… *****

Reading package lists… Done
Building dependency tree
Reading state information… Done
apache2 is already the newest version.
build-essential is already the newest version.
git-core is already the newest version.
libapache2-mod-php5 is already the newest version.
php5 is already the newest version.
php5-cgi is already the newest version.
php5-cli is already the newest version.
php5-common is already the newest version.
python-dev is already the newest version.
python-pip is already the newest version.
The following packages were automatically installed and are no longer required:
libdrm-freedreno1 libdrm-nouveau2 libdrm-radeon1 libelf1 libllvm3.5
Use ‘apt-get autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

***** Installing/updating required python packages via pip… *****

Requirement already up-to-date: pyserial in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: psutil in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: simplejson in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: configobj in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: gitpython in /usr/local/lib/python2.7/dist-packages
Requirement already up-to-date: six in /usr/local/lib/python2.7/dist-packages (from configobj)
Requirement already up-to-date: gitdb>=0.6.4 in /usr/local/lib/python2.7/dist-packages (from gitpython)
Requirement already up-to-date: smmap>=0.8.5 in /usr/local/lib/python2.7/dist-packages (from gitdb>=0.6.4->gitpython)
Cleaning up…

***** Done processing BrewPi dependencies *****

***** Updating cron for the brewpi user… *****

no crontab for brewpi
Checking entry for brewpi …
Done checking entry brewpi …
Checking entry for wifichecker …
Done checking entry wifichecker …
Restarting cron
[ ok ] Restarting cron (via systemctl): cron.service.

***** Fixing file permissions for /var/www *****

***** Fixing file permissions for /home/brewpi *****

The update script can automatically check your controller firmware version and program it with the latest release on GitHub, would you like to do this now? [Y/n]:
Stopping any running instances of BrewPi to check/update controller…

Checking current firmware version…
Mar 16 2016 00:15:24 Opening serial port
Found BrewPi v0.4.2 build 0.4.2-0-g446b226, running on a Particle Photon with a V2 shield on port /dev/ttyACM0

Current firmware version on controller: 0.4.2

Checking GitHub for available release…

Available releases:

[0] 0.4.3beta3
[1] 0.4.2
[2] 0.4.1
[3] 0.4.0
[4] 0.3.0a
[5] 0.2.11
[6] Cancel firmware update
Enter the number [0-6] of the version you want to program [default = 1 (0.4.2)]0
Would you like me to try to restore you settings after programming? [Y/n]:

Would you like me to try to restore your configured devices after programming? [Y/n]:

Downloading firmware…
downloading https://github.com/BrewPi/firmware/releases/download/0.4.3beta3/brewpi-photon-0.4.3-beta3-0-g7e11dfa.bin
Updated system firmware for the photon found in release 0.4.3beta3
downloading https://github.com/BrewPi/firmware/releases/download/0.4.3beta3/system-part1-0.4.9-photon.bin
downloading https://github.com/BrewPi/firmware/releases/download/0.4.3beta3/system-part2-0.4.9-photon.bin
Downloaded new system firmware to:

/home/brewpi/utils/downloads/0.4.3beta3/system-part1-0.4.9-photon.bin
and

/home/brewpi/utils/downloads/0.4.3beta3/system-part2-0.4.9-photon.bin

Latest firmware downloaded to:
/home/brewpi/utils/downloads/0.4.3beta3/brewpi-photon-0.4.3-beta3-0-g7e11dfa.bin

Updating firmware…

**** Photon Program script started ****
Settings will be restored if possible
Devices will be restored if possible
Checking old version before programming.
Mar 16 2016 00:15:43 Opening serial port
Checking current version: Found BrewPi v0.4.2 build 0.4.2-0-g446b226, running on a Particle Photon with a V2 shield on port /dev/ttyACM0

Requesting old settings from Photon…
Saved old settings to file settings-Mar-16-2016-00-15-46.json

Found a Photon and running as root/sudo, using DFU mode to flash firmware.

Trying to automatically reboot into DFU mode and update your firmware.

If the Photon does not reboot into DFU mode automatically, please put it in DFU mode manually.
Running command: sudo /usr/bin/python /home/brewpi/utils/flashDfu.py --autodfu --noreset --file=/home/brewpi/utils/downloads/0.4.3beta3 --system1=/home/brewpi/utils/downloads/0.4.3beta3/system-part1-0.4.9-photon.bin --system2=/home/brewpi/utils/downloads/0.4.3beta3/system-part2-0.4.9-photon.bin
Will automatically reboot newly detected photons into DFU mode
Using local files instead of downloading a release.

Using dfu-util binary at /home/brewpi/utils/downloads/dfu-util
Detecting DFU devices
Did not find any DFU devices.
Is your Photon or Spark Core running in DFU mode (blinking yellow)?
Waiting until a DFU device is connected…
Found new serial port connected: (’/dev/ttyACM0’, ‘Particle Photon’)
Putting Photon in DFU mode
Found 1 devices: [‘2b04:d006’]
Device identified as Particle Photon
First updating system firmware for the Photon, part 1: /home/brewpi/utils/downloads/0.4.3beta3/system-part1-0.4.9-photon.bin
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Filter on vendor = 0x2b04 product = 0xd006
Opening DFU capable USB device… ID 2b04:d006
Run-time device DFU version 011a
Found DFU: [2b04:d006] devnum=0, cfg=1, intf=0, alt=0, name="@Internal Flash /0x08000000/03016Ka,01016Kg,01064Kg,07128Kg"
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
No valid DFU suffix signature
Warning: File has no DFU suffix
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08020000, size = 249916

File downloaded successfully
Continuing updating system firmware for the Photon, part 2: /home/brewpi/utils/downloads/0.4.3beta3/system-part2-0.4.9-photon.bin
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Filter on vendor = 0x2b04 product = 0xd006
Opening DFU capable USB device… ID 2b04:d006
Run-time device DFU version 011a
Found DFU: [2b04:d006] devnum=0, cfg=1, intf=0, alt=0, name="@Internal Flash /0x08000000/03016Ka,01016Kg,01064Kg,07128Kg"
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuDNLOAD-IDLE, status = 0
aborting previous incomplete transfer
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
No valid DFU suffix signature
Warning: File has no DFU suffix
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08060000, size = 181428

File downloaded successfully
Now writing BrewPi firmware /home/brewpi/utils/downloads/0.4.3beta3/brewpi-photon-0.4.3-beta3-0-g7e11dfa.bin
dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Filter on vendor = 0x2b04 product = 0xd006
Opening DFU capable USB device… ID 2b04:d006
Run-time device DFU version 011a
Found DFU: [2b04:d006] devnum=0, cfg=1, intf=0, alt=0, name="@Internal Flash /0x08000000/03016Ka,01016Kg,01064Kg,07128Kg"
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuDNLOAD-IDLE, status = 0
aborting previous incomplete transfer
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
No valid DFU suffix signature
Warning: File has no DFU suffix
DfuSe interface name: "Internal Flash "
Downloading to address = 0x080a0000, size = 86820

File downloaded successfully
Programming done

Updating firmware over DFU finished

Waiting for device to reset.
Mar 16 2016 00:16:24 Opening serial port
Checking new version: Found BrewPi v0.4.3b build 0.4.3b2-0-g3de44b0, running on a Particle Photon with a V2 shield on port /dev/ttyACM0

Resetting EEPROM to default settings
INFO MESSAGE 15: EEPROM initialized
Now checking which settings and devices can be restored…
Trying to restore compatible settings from 0.4.2 to 0.4.3b
Migrating these settings: [[“tempFormat”, “C”], [“fridgeSet”, null], [“beerSet”, null], [“mode”, “t”], [“heater1_kp”, 10.0], [“heater1_ti”, 600], [“heater1_td”, 60], [“heater1_infilt”, 1], [“heater1_dfilt”, 4], [“heater2_kp”, 10.0], [“heater2_ti”, 600], [“heater2_td”, 60], [“heater2_infilt”, 1], [“heater2_dfilt”, 4], [“cooler_kp”, 10.0], [“cooler_ti”, 1800], [“cooler_td”, 200], [“cooler_infilt”, 1], [“cooler_dfilt”, 4], [“beer2fridge_kp”, 2.0], [“beer2fridge_ti”, 7200], [“beer2fridge_td”, 1200], [“beer2fridge_infilt”, 1], [“beer2fridge_dfilt”, 4], [“beer2fridge_pidMax”, 10.0], [“minCoolTime”, 120], [“minCoolIdleTime”, 180], [“heater1PwmPeriod”, 4], [“heater2PwmPeriod”, 4], [“coolerPwmPeriod”, 1200], [“deadTime”, 1800]]
Omitting these settings: []
INFO MESSAGE 12: Received new setting: tempFormat = C
INFO MESSAGE 12: Received new setting: fridgeSet = null
INFO MESSAGE 12: Received new setting: beerSet = null
INFO MESSAGE 12: Received new setting: mode = t
INFO MESSAGE 12: Received new setting: heater1_kp = 10.0
INFO MESSAGE 12: Received new setting: heater1_ti = 600
INFO MESSAGE 12: Received new setting: heater1_td = 60
INFO MESSAGE 12: Received new setting: heater1_infilt = 1
INFO MESSAGE 12: Received new setting: heater1_dfilt = 4
INFO MESSAGE 12: Received new setting: heater2_kp = 10.0
INFO MESSAGE 12: Received new setting: heater2_ti = 600
INFO MESSAGE 12: Received new setting: heater2_td = 60
INFO MESSAGE 12: Received new setting: heater2_infilt = 1
INFO MESSAGE 12: Received new setting: heater2_dfilt = 4
INFO MESSAGE 12: Received new setting: cooler_kp = 10.0
INFO MESSAGE 12: Received new setting: cooler_ti = 1800
INFO MESSAGE 12: Received new setting: cooler_td = 200
INFO MESSAGE 12: Received new setting: cooler_infilt = 1
INFO MESSAGE 12: Received new setting: cooler_dfilt = 4
INFO MESSAGE 12: Received new setting: beer2fridge_kp = 2.0
INFO MESSAGE 12: Received new setting: beer2fridge_ti = 7200
INFO MESSAGE 12: Received new setting: beer2fridge_td = 1200
INFO MESSAGE 12: Received new setting: beer2fridge_infilt = 1
INFO MESSAGE 12: Received new setting: beer2fridge_dfilt = 4
INFO MESSAGE 12: Received new setting: beer2fridge_pidMax = 10.0
INFO MESSAGE 12: Received new setting: minCoolTime = 120
INFO MESSAGE 12: Received new setting: minCoolIdleTime = 180
INFO MESSAGE 12: Received new setting: heater1PwmPeriod = 4
INFO MESSAGE 12: Received new setting: heater2PwmPeriod = 4
INFO MESSAGE 12: Received new setting: coolerPwmPeriod = 1200
INFO MESSAGE 12: Received new setting: deadTime = 1800
Now trying to restore previously installed devices: [{u’a’: u’3A430621000000D0’, u’c’: 1, u’b’: 0, u’d’: 0, u’f’: 8, u’i’: 0, u’h’: 3, u’n’: 0, u’p’: 0, u’t’: 5, u’x’: 0}, {u’a’: u’3A430621000000D0’, u’c’: 1, u’b’: 0, u’d’: 0, u’f’: 8, u’i’: 1, u’h’: 3, u’n’: 1, u’p’: 0, u’t’: 5, u’x’: 0}, {u’a’: u’3AC70621000000E6’, u’c’: 1, u’b’: 0, u’d’: 0, u’f’: 8, u’i’: 2, u’h’: 3, u’n’: 0, u’p’: 0, u’t’: 5, u’x’: 0}, {u’a’: u’3AC70621000000E6’, u’c’: 1, u’b’: 0, u’d’: 0, u’f’: 8, u’i’: 3, u’h’: 3, u’n’: 1, u’p’: 0, u’t’: 5, u’x’: 0}]
Restoring device: {“a”: “3A430621000000D0”, “c”: 1, “b”: 0, “d”: 0, “f”: 8, “i”: 0, “h”: 3, “n”: 0, “p”: 0, “t”: 5, “x”: 0}
Photon reports: device updated to: {“i”:0,“t”:5,“c”:1,“b”:0,“f”:8,“h”:3,“d”:0,“p”:0,“x”:0,“a”:“3A430621000000D0”,“n”:0}

Restoring device: {“a”: “3A430621000000D0”, “c”: 1, “b”: 0, “d”: 0, “f”: 8, “i”: 1, “h”: 3, “n”: 1, “p”: 0, “t”: 5, “x”: 0}
Photon reports: device updated to: {“i”:1,“t”:5,“c”:1,“b”:0,“f”:8,“h”:3,“d”:0,“p”:0,“x”:0,“a”:“3A430621000000D0”,“n”:1}

Restoring device: {“a”: “3AC70621000000E6”, “c”: 1, “b”: 0, “d”: 0, “f”: 8, “i”: 2, “h”: 3, “n”: 0, “p”: 0, “t”: 5, “x”: 0}
Photon reports: device updated to: {“i”:2,“t”:5,“c”:1,“b”:0,“f”:8,“h”:3,“d”:0,“p”:0,“x”:0,“a”:“3AC70621000000E6”,“n”:0}

Restoring device: {“a”: “3AC70621000000E6”, “c”: 1, “b”: 0, “d”: 0, “f”: 8, “i”: 3, “h”: 3, “n”: 1, “p”: 0, “t”: 5, “x”: 0}
Photon reports: device updated to: {“i”:3,“t”:5,“c”:1,“b”:0,“f”:8,“h”:3,“d”:0,“p”:0,“x”:0,“a”:“3AC70621000000E6”,“n”:1}

Restoring installed devices done!
**** Program script done! ****
BrewPi script will restart automatically.

*** Done updating BrewPi! ***

Thanks for confirming it works now.

Update worked fine, up and running. No issues so far, I will post if I discover anything…

Seems to run pretty good. Some interessting behaviours of the fridge setting, this happen after rebooting. I will do some further tests on the weekend to see if this can somehow be reproduced:

Thanks for the feedback, that looks like the PID input filter being initialized with a too high temperature (to explain the low peak), which is then quickly filtered back to the real input. The derivative gain explains the high peak.

Nice! Been traveling a couple of weeks coming back to see this… Will help testing as much as possible.

This seems to be fixed. Cannot see this in my test anymore. Was seen on every restart with earlier versions.

_Hopefully fixed initialialization of filters with wrong data (85C), because sensors were read before a conversion was started. A lot changed in the init sequence and I don’t see this problem myself anymore. Please report you still encounter it.

Doing a first mash (RIMS-tube based) with the 0.4.3b3 firmware. Overshoot seems to too good under control now as it approximates the target beer-temp but doesn’t really reach it.

What you can do is increase Kp for more aggressive control. You could also reduce Td (to anticipate less for overshoot based on the derivative) and reduce Ti (to correct steady state errors faster).

i will change the settings for the next brew end of this week. At least, I still hit the the target OG (1.057 instead of 1.058).

With upgrade my graph lines are choppy - temperature value keeps jumping up and down between two adjacent values: