BrewBlox Basic questions

#1

Hi
I have been running a brewpi spark for some time now (awesome product by the way) I have finally found BrewBlox (there should really be a link on the old brewpi site :wink: ) And I cant wait to start expanding my system. but there is three questions i don’t seem to find a good answer for:

  1. Is the “spark” referenced in the documentation the “brewpi spark 3”?
  2. If so does the “brewpi spark 3” require new firmware?
  3. And most important: do you require 1 “brewpi spark 3”/spark for each setup? Meaning if you are to run 2 converted fridges and one 3 kettle brewing setup. How many sparks would you need?

Bjørn

#2

It is a software update for the Spark. You can flash it as part of the install process. I do recommend a fresh raspbian install.

With the BrewBlox firmware the Spark can control multiple processes.

A BrewBlox server (the pi) can serve multiple sparks. You could opt to use a separate spark for fermentation and for mashing to keep your cables shorter and your processes somewhat independent.

#3

Tanks for a quick reply…

Just to start working on my next shopping list then:)

#4

Hi Elco,
I am at the end of Brewblox installation but not sure what to respond to the setup questions under Step 5 in the Getting started guide. Please advise?

BR Ken

image

#5

Before you run setup, navigate to the install dir (default brewblox, so cd brewblox)

#6

Hi Bob,
It looks likes that Brewblox directory is not created since I got the error as shown below
BR Ken
image

#7

Have you done brewblox-ctl install first?

#8

I did the installation with the following input


And for some reason, I still got the error
image

BR Ken

#9

If you run ls, it will show the directories. A brewblox one should be among them.

#10

Hi Bob
It seems that only pi directory have been created since ls command just shows
image

image

BR Ken

#11

Out of curiosity, try ls -a in the pi home directory. I wonder if it stripped the “/” from “./BrewBlox” (which would make it a hidden directory).

If this is the case, you should be able to unhide it with mv .BrewBlox BrewBlox.

#12

I have tried to run the “brewblox-ctl install” command once more with the same result as shown below.
At the end of the execution, errors occur.
BR Ken

#13

It seems like brewblox-ctl install exited with an error before it created the directory.
To fix this, you could try to reboot your raspberry, and then run the following commands:

curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
brewblox-ctl install
brewblox-ctl setup
#14

Linux is case sensitive…

1 Like
#15

Hi Bob,
I have tried to run the commands. During execution of the last commend I got the following question. What should be replied to this question?
BR Ken
image

#16

My bad on that one: you should navigate to your install dir before running brewblox-ctl setup.

Did your brewblox-ctl install complete without errors this time? Can you see your install directory if you run ls -a?

#17

Running ls -a shows
image
and cd ./brewblox shows
image
Means that something goes wrong during installation?

BR Ken

#18

Did you reboot your raspberry?
Did your install command finish successfully?
What was the output of the install command?

#19

The installation is executed after cold boot and output is shown below
The following shell commands will be used:

     sudo apt update
     sudo apt upgrade -y
     sudo apt install -y libssl-dev libffi-dev
     curl -sSL https://get.docker.com | sh
     sudo usermod -aG docker $USER
     sudo /usr/bin/python3 -m pip install -U docker-compose
     mkdir -p ./brewblox
     touch ./brewblox/.env
     /usr/bin/python3 -m dotenv.cli --quote never -f ./brewblox/.env set BRE                                                       WBLOX_RELEASE edge
     /usr/bin/python3 -m dotenv.cli --quote never -f ./brewblox/.env set BRE                                                       WBLOX_CFG_VERSION 0.0.0
     sudo reboot

Press ENTER to continue, Ctrl+C to cancel

Running command:
sudo apt update

Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Hit:3 https://download.docker.com/linux/raspbian stretch InRelease
Err:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease
The following signatures couldn’t be verified because the public key is not av ailable: NO_PUBKEY 9165938D90FDDD2E
Err:1 http://archive.raspberrypi.org/debian stretch InRelease
The following signatures couldn’t be verified because the public key is not av ailable: NO_PUBKEY 82B129927FA3303E
Fetched 40.3 kB in 2s (16.9 kB/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG erverified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG erified because the public key is not available: NO_PUBKEY 82B129927FA3303E
W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/stretch/InRelease The following signatures couldn’t be verified beca
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/stretch/InRelease The following signatures couldn’t be verified because
W: Some index files failed to download. They have been ignored, or old ones used instead.

Running command:
sudo apt upgrade -y

Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Running command:
sudo apt install -y libssl-dev libffi-dev

Reading package lists… Done
Building dependency tree
Reading state information… Done
libffi-dev is already the newest version (3.2.1-6).
libssl-dev is already the newest version (1.1.0j-1~deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Running command:
curl -sSL https://get.docker.com | sh

Executing docker install script, commit: 2f4ae48

  • sudo -E sh -c apt-get update -qq >/dev/null
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://raspbian.raspberrypi.org/raspbian stretch InRelease: The following signatures could n’t be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian stretch InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
    W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/stretch/InRelease The following signatures could n’t be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E
    W: Failed to fetch http://archive.raspberrypi.org/debian/dists/stretch/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
    W: Some index files failed to download. They have been ignored, or old ones used instead.
  • sudo -E sh -c apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
  • sudo -E sh -c curl -fsSL “https://download.docker.com/linux/raspbian/gpg” | apt-key add -qq - >/dev/null
    Warning: apt-key output should not be parsed (stdout is not a terminal)
  • sudo -E sh -c echo “deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable” > /etc/apt/source s.list.d/docker.list
  • sudo -E sh -c apt-get update -qq >/dev/null
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://raspbian.raspberrypi.org/raspbian stretch InRelease: The following signatures could n’t be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian stretch InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
    W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/stretch/InRelease The following signatures could n’t be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E
    W: Failed to fetch http://archive.raspberrypi.org/debian/dists/stretch/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
    W: Some index files failed to download. They have been ignored, or old ones used instead.
  • [ -n ]
  • sudo -E sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
    E: Unable to locate package docker-ce

Error: Command ‘curl -sSL https://get.docker.com | sh’ returned non-zero exit status 100

#20

Thank you. If your install command output ends with “error: XXXX”, you shouldn’t continue running commands: it means something went wrong that must be solved first.

It appears this specific issue is in the Raspberry Pi itself, not in BrewBlox.
A google search indicates a possible solution:

wget http://archive.raspbian.org/raspbian.public.key -O - | sudo apt-key add -
curl -sSL https://get.docker.com | sh

If this still ends in an error, you may have a corrupted SD card. In that case it’s best to restart the install guide from the beginning.