Yes, you should run this command twice:
docker run -it --name brewpi-dfu --privileged -v ~/brewpi-data:/data --rm brewpi/brewpi-raspbian python utils/flashDfu.py --tag=0.5.4 --noreset --autodfu
Exit with CTRL-C the first time. It should now be running in DFU mode. Then run it again. When you have set up wifi, the Spark will download a new bootloader from the Particle server.
Hi Elco,
I tried to run the entire script and got the message:
“dfu-util: Cannot open DFU device 2b04:d006” I am sure you know why.
The 2nd time the script was executed the final screen message was
Download done
File downloaded successfully
Programming done
The new firmware version 0.5.4 is successfully installed
Use of the Particle app went also successfully, giving the BrewPI Spark an IP address 192.168.1.172 on the screen.
I have changed the IP-address in the maintenance panel (http://raspberrypi.local/#), but I cannot update the device list. I got the following error:
Error while receiving device configuration: Couldn’t write to socket: [111] Connection refused Is the script running?
The script is not running and I cannot get it running for some reasons?
I can Ping the device over my network, so far so good!
Thanks for your help!
BR Ken
In the maintenance panel -> log files, you should see the error that causes the script not to run.
Hi Elco,
There is nothing logged since 22mar2018 as shown below, which is all that’s found under Maintenance/View Logs tab. Looking in our community I can see others have had the same issue, but obviously, no one after you introduced the Docker technology. Can it be something with the folder structure on my Raspberry Pi? When I press the key “Start Script” nothing is logged in the “log window dialog”. Does this say something? Maybe that the system is not running at all. Everything looks fine on Brewpi Spark showing IP address 192.168.1.172.
Hope this gives you a hint!
BR Ken
Mar 22 2018 20:43:54 Notification: Script started for beer ‘My First BrewPi Run’
Mar 22 2018 20:43:54 Connecting to controller…
Mar 22 2018 20:43:54 Background thread for serial started
Mar 22 2018 20:44:04 Warning: Cannot receive version number from controller. Check your port setting in the Maintenance Panel or in settings/config.cfg.
Mar 22 2018 20:55:05 stopScript message received on socket. Stopping script and writing dontrunfile to prevent automatic restart
Mar 22 2018 20:55:05 Background thread for serial stopped
Hej Elco,
I have just tried the USB connection (serial port), but I cannot start script either through that interface. There is nothing communicated to the log windows (stderr:), which is really strange, since I stil got the error shown below, when trying to refresh devicelist?
Error while receiving device configuration: Couldn’t write to socket: [111] Connection refused Is the script running?
BR Ken
Hi Ken,
This was caused by a bug that I just fixed.
If you update the container (in portainer click the recreate container button and pull the latest image), then it will start working again.
Sorry for the trouble it caused you.
Hi Elco,
Sounds good you found a bug and fixed it 
I am not sure how to recreate containers and pull the image, is it with this script “docker-compose up --build”?
BR Ken
Hi Elco
I found the recreate button, but running the recreation gives a failure “Unable to remove container”, then the contianer list is empty.Shall I reload the containers by running the portainer docker image?
BR Ken
Ah, I think you tried re-create portainer. This doesn’t work, it cannot recreate itself.
Remove the old container:
docker stop portainer
docker rm portainer
And then create it again with the docker run command as described on the wiki.
Hi Elco,
I have created the portainer again with the docker script, but the script will still not start. Do you think I still have the version with the bug?.
If I restart http://raspberrypi.local/ the web interface does not remember the IP address. Does this give you a hint?
BR Ken
When you did ‘docker run’, it re-used the old image. You can now just recreate the brewpi container and pull the latest image from the portainer UI.
The IP address is received and stored by the script, so without the script running it will indeed not be remembered.
Hi Elco
I guess both containers one at a time, must be recreated and pull the latest image enabled?
BR Ken
Don’t recreate portainer, just BrewPi
Hi Elco,
Everything works Container successfully recreated. I was not aware of the portainer should not be recreated.
Cheers Ken
That’s why I explained that 5 messages ago 
Maybe we should revise/include the recreation of containers on wiki.brewpi.com. Setting up devices also makes troubles for some in our community, is this described somewhere?. Who is allowed to revise wiki.brewpi?
BR Ken
Anyone can submit changes. They do have to be approved before they are public though.
Hi Elco,
Today I needed to deploy the portainer docker image, since the image was no longer running on raspberry PI for some reason (the image might just have stopped running). However after executing the deploy command from puTTY, the docker web interface http://raspberrypi:local:9000 did not start in the web browser, even though Brewpi is running just fine, and the connection to Brewpi Spark also worked fine.
Do you know what I did wrong?
BR Ken
And if you use a dot instead of a colon?
Check that the portainer container is running with docker ps
docker ps gives
saying that the docker is running?
I used the web address http://raspberrypi.local:9000/
