Eh… You are using flashDFU and now you say you have an Arduino?
With the core/photon, we use a OneWire bus master and an level shifter for the outputs. It is not as DIY friendly as the Arduino and we do not support direct pin OneWire anymore, only via a bus master on the Photon.
Sorry for the confusion…
My current setup is a RPi model B with an arduino board. But with the new version, I wanted to update my setup to use some stuff I had around the house (PRi 2 and Photon). As you mentioned, the photon is a b#tch to get OneWire working. Going to have a look in your shop, do you offer those things to tinker with, myself?
Congrats on the awesome work btw.
You could buy just the bare board, with display and connectors, without Photon or enclosure.
Hi,
First of all congrats for the amazing project!
two or three weeks ago i managed to install and run brewpi using a debian virtual machine. Saturday i finally got my raspberry pi 2 and run all the steps to install it. At first look everything is fine, but i noticed that something is changed, from my vm to my raspberry installation like the data under maintence / control algorithm.
Im using an arduino uno, in that way, i belive i should use the legacy branch of brewpi. Right? is th updater.py able do downgrade a fresh install? is there a way to install tight from the begining the legacy branch?
I got this message a system log and it is concerning me a bit :
Dec 14 2015 13:53:02 Opening serial port
Dec 14 2015 13:53:02 Notification: Script started for beer 'None’
Dec 14 2015 13:53:12 Checking software version on controller…
Dec 14 2015 13:53:12 Found BrewPi v0.2.10 build unknown, running on an Arduino Uno with a revC shield on port /dev/ttyUSB0
Dec 14 2015 13:53:12 Warning: minimum BrewPi version compatible with this script is 0.4.0 but version number received is 0.2.10
Dec 14 2015 13:53:12 Warning: version number of local copy of logMessages.h does not match log version number received from controller.controller version = 1, local copy version = 2
Even with the controller working should i move back to legacy( taking in account that in no way i will be able to get my hands on a spark before and of january/16)?
Thanks in advance
Alessandro Sartor.
Yes, you should downgrade to the legacy branch. The instructions are posted above, under Arduino users.
Hey @Elco, I am not updated to 0.4.1 yet but am between beers and thought tonight be a good chance. I have set my controller up for remote viewing using much of what is mentioned in this thread:
I was going to run the updater but was wondering if I would have to go and reconfigure all of this stuff as well. If so, that is cool but I probably wouldn’t get myself into that tonight. Any thoughts?
Thanks!
I am doing this from the top of my head, so be careful and make a backup.
What I would do is commit that work into a new branch, called admin:
Create a new branch and check it out:
git branch admin git checkout admin
Stage the files with changes you want to keep.
Use git status to see which files changed.
Use git add <filename> to include them in the commit or git add -a to include all.
Create a new commit on your new branch: git commit
Then change back to master: git checkout master. And run the update script.
After the update script is done, switch back to your admin branch:
git checkout admin
And merge the changes of master in your admin branch.
git merge master
To understand what you are doing, I highly recommend this video that explains the basics of git.
It is called ‘git for ages 4 and up’.
1 Like
Thanks @Elco, I’m going to look over this closely and see if I can do it without screwing it up.
@mikmonken, have you updated?
@bryancm1 I’ve not updated and wasn’t planning on going to either as the set up I’m currently using is working perfectly.
For what sits worth though I have updated previous versions and the remote viewing function with the webpage password has been unaffected.
Thanks,
I finnally managed to get the raspberry pi working ok. Unfortunnelly with the virtual machice i was able upgrade and downgrade the software, but at raspberry PI i had to remove the actual software, clone both scripts and www part from git usinf the legacy option, and then fix permissions. I also had issues with the default www path that in both cases is /var/www/html and the install script always point to /var/www, it causes problems with permissions and also with the updates.
Anyway, i got everything working and i will brew my first batch with brewpi in the next week.
Thanks for the reply.
Ps.: If you ever consider to translate Brewpi to Brazilian Portuguese feel free to get in touch.
BR
Alessandro.
Would you mind posting a link on where to find it in the shop? Can’t seem to find it.
Hi,
We’ve just flashed to 0.4.1 our recently received BrewPi.
Everything works as expected (UI, Firmware, …) except one thing: configuring devices.
When I pick a configuration for a detected device, the json prints on the UI. Then, when I ask for a device detection again, the device is no more configured (not listed as ‘installed’). So, I can’t configure anything in fact 
I’ve noticed that instead of ‘Hardware Sensor’, the device type shows as ‘None’. Also, in test mode, the temperature are well read.
Any hints on what might be happening?
Thanks,
Guillaume
Was an EEPROM reset executed during the update? You can do one manually in advanced settings --> reset factory defaults.
1 Like
Hey Elco, i’m havnig issues downloading the firmware to my super old brewpi, uno revA.
I switched to the legacy branch but it fails on download.
Checking current firmware version…
Dec 19 2015 09:34:36 Opening serial port
Current firmware version on controller: 0.2.4
Checking GitHub for latest release…
Latest version on GitHub: 0.4.1
Version on GitHub is newer than your current version, downloading new version…
Downloading latest firmware…
Downloading firmware failed
*** Done updating BrewPi! ***
I have not tested this, but I think this should still work:
Download a release manually:
Upload via the web interface.
took a couple of goes but it worked thanks mate!
I have a brewpi spark handling fridge constant mode at 40f for my True T49 fridge for bottle storage. The new version works well but it has changed a few things and I’ve seen a few oddities.
1: Previous to 0.4.x the fan would only come on when the compressor came on to adjust the temperature. Now the fan is on all the time, except when earlier today it turned it off for ~6 hours before I noticed my temp graph looked all funky. I messed with it a bit and it seems to be back to normal, maybe.
2: I used to be able to adjust the max over/under for fridge constant, ie, if I have it set to 40f I had the max over set to 1.5f it wouldn’t turn on the compressor and fan until it was 41.5f. Now I have no control, and while it is super accurate it is not as power efficient as used to be. My fridge was built in 1993 and the compressor is rated for ~9 amps, so this was an area of interest for me.
When is multi chamber coming? I’m about to get back into brewing and I want to run another fridge for a fermentation chamber. Would be nice to have one brewpi control both.
-
I would configure the fan as manual actuator and turn it ON permanently.
-
You can now adjust the PWM period for the fridge. To have it turn on less often, increase the PWM period. For your bottle storage 1 hour will be fine probably. Set it to 3600.
Multi chamber: this requires a whole new web interface and data storage, so it will take us a few months.
I’m having some difficulties updating. I ran updater.py, and it said there was an error updating the firmware for my photon and that it was restoring defaults. After that, the brewpi had a blank white screen. I ran the updateFirmware.py script, and got the “unable to connect to device” error message. I tried putting the photon in DFU mode and tried both steps again, but with the same errors. A
t this point, I can’t get either script to recognize the photon. I don’t think the issue is cables or power supply, as this exact hardware setup was running just fine a week ago. Any ideas? Thanks!