Skip to content

Release 0.5.1 (Multi-Chamber)
Compare
Choose a tag to compare
@lbussy lbussy released this 11 Feb 00:31
0.5.1
835e7c1

Release 0.5.1

As with the previous release, since these repositories are intricately intertwined, the same release notes will be provided in each.

This release most significantly brings full multi-chamber support. The core work remains mostly intact, however multi-chamber support is now baked in. To take advantage of this, when prompted give a "chamber name." For instance if you enter "chamber1", the following will happen:

  • A sub-directory under /home/brewpi and /var/www/html named "chamber1" will be created for the application
  • You will be presented with choice of which plugged-in Arduino to associate with that chamber, and it will be named "/dev/chamber1"
  • A systemd unit file will be created named "chamber1", able to be controlled with that name, i.e. sudo systemctl status chamber1, etc.
  • The web page title will be changed from "BrewPi Legacy Remix" to "BLR: Chamber1"
  • The beer-panel section (just under the logo) will show the name of the brew, followed by "in Chamber1"

Changes include:

  • Changed to use daemon mode for brewpi and wifi check
  • Delete crontab and the mess that surrounds it
  • Remove checkWiFi script
  • Add doDaemon, doWiFi, doBrewPi for systemd support
  • Fixed internal calls not passing command line arguments (like --help)
  • Fixed WiFi to properly manage interfaces (ifconfig vs ifdown/up)
  • Rearranged install functions to flow more easily for new users
  • Reordered includes to catch more important things first
  • Changed uninstall to optionally leave packages (added levels)
  • Script starts within 5 seconds of pressing button in web UI
  • Fixed internal conflict checking within brewpi.py
  • Removed check for pi's password if pi does not exist
  • Added indicator to "Fermenting" line in web UI as well as page title when in multi-chamber mode

Some known issues:

  • The script (still) does not seem to log to the stdout/stderr after flashing an Arduino via the web UI. Temp logging and control seems to be unharmed. Suggest a restart or reboot after for now (logged as issue #1 in WWW). I hope to get to this next
Assets 2
Loading