BrewPi Remix – What’s Old is New Again

[LBussy]

Like I said earlier, I get to flash fine with BrewFlasher. I can access it, use my Smartphone and configure it. Although I put an mDNS name, it seems that it is not registered. I can locate the device in the list of devices connected to my router using the MAC address (I have more devices with the ESP label… they are sonoff devices for the lights in the house.) I don't know if it is normal that the mDNS label is not recorded.

mDNS is a broadcast thing, so if it's on your network and your router doesn't filter broadcast (some do) then it should work.

If you are using Windows, try zeroConfServiceBrowser. It should show all of the devices broadcasting on your network. These days there should always be at least a few. If you see none, then the problem is either your computer or your network. Are you able to connect to your Raspberry Pi by name? Can you ping your ESP device by name from the Pi?

 

[blau]

Hello,
With ZeroconfServiceBrowser I can recognize my wemos D1 mini and see the ip and the host. They respond to ping from your ip and ping from your host. From the pc and from the Raspberry. How do I access them to change Host and IP? or access your setup?
Can you tell me the connection pinouts on the Wemos D1 mini to install the probes and relays and try to recognize them?
Thanks

 

[LBussy]

With ZeroconfServiceBrowser I can recognize my wemos D1 mini and see the ip and the host. They respond to ping from your ip and ping from your host. From the pc and from the Raspberry.

Excellent, all good then.

How do I access them to change Host and IP? or access your setup?

There is no direct configuration on the device at this point. You configure BrewPi to use the device by an entry in the "/home/brewpi/settings/config.cfg" file. It probably has something like this now:

port = auto
altport = None

Delete those and add an entry like this:

port = socket://192.168.168.143:23

Change the IP address to reflect the IP of your controller, leave the ":23" at the end.

Can you tell me the connection pinouts on the Wemos D1 mini to install the probes and relays and try to recognize them?

• D0 - Heat
• D5 - Cool
• D6 - OneWire

 

[blau]

Hello,
Tell me if I have understood the process correctly:
When I have configured my wemos D1 mini: it has taken an IP address offered by the router's dhcp. For example: 192.168.1.xx. This IP is the one that you tell me that I have to configure in the file Config.cfg port = socket: //192.168.1.xx: 23 in this way raspberry will use this port to communicate with my wemos D1 mini. If this is correct, the problem will be in my new location, the range of IP's is different 192.168.100.xx for this reason I think I would have to modify the IP that my wemos D1 mini has assigned.

• D0 - Heat
• D5 - Cool
• D6 - OneWire

is this for relays or for ssr?Some days ago, you commented that there was a little connection difference. I'm going to use ssr.
Thanks

 

[LBussy]

I think I would have to modify the IP that my wemos D1 mini has assigned.

I am reasonably sure there is no web server in the controller, so there's nothing for you to connect to. There is a TELNET server (which is how the application connects.) The easiest way to erase the settings is to use the BrewPi web interface if you can connect. If you cannot, then use BrewFlasher, re-flash, and be sure to choose the "erase flash." Just re-flashing does not erase the WiFi settings. After that you should be able to connect to it as an Access point", and connect it to the new network.

is this for relays or for ssr? Some days ago, you commented that there was a little connection difference. I'm going to use ssr.

Relays will use the same pins. The SSR is generally set up opposite of how a relay is set:

Under "Pin Type", the SSR is set up as "Non-Inverted."

 

[blau]

Ok, I think that with these indications I could put the system to work. This weekend I am looking for a quiet time. I will continue to report.
Thanks.

 

[Brewski_59]

Lee
what could cause this?:
2021-03-13 20:33:36 [E] Failed to parse Purple Tilt from Tiltbridge payload.

Oh, never mind. I just realized the date. I know what caused this. How can I delete this post?

 

[LBussy]

Not sure you can delete a post - I can ignore it if you like.

 

[blau]

Hello,
new steps, new problems.
Brewpi remix installed. multi-camera, but at the moment only one. configured the file config.cfg with the ip corresponding to the only D1mini (with a probe and a ssr connected). the ip answers ping both from a pc and from the raspberrypi. It seems all correct.
I access the page for the first time and it returns a wrong temperature reading (20º) in the header. It seems that things are going well.
I access the "device Configuration" section. I refresh device list, at first an error but finally it shows me a list with several devices, among them I recognize the probe. I configure and update but the temperature reading does not work. After this everything is worse. In the header of the page I only get "Cannot connect to script" and although I refresh again I do not get anything in the list of devices. I restart the system and I always get this last state. In the terminal type viewer, I always get "Error while receiving device configuration: SintaxError: token C in JSON at position 0"
the system returns ping still. I understand that there must be a communication problem with the D1mini, but I don't know what to do.
Any ideas?
Thanks

 

[LBussy]

I always get "Error while receiving device configuration: SintaxError: token C in JSON at position 0"

Confirmed - you can switch to the "devel" branch to get past this error (change path as appropriate if you are using multi-chamber):

cd /home/brewpi
sudo git checkout devel
sudo /home/brewpi/utils/doPerms.sh
sudo systemctl restart brewpi

That should get you past that error, I was working on it yesterday but it is not in the master branch yet.

I configure and update but the temperature reading does not work.

I am banging my head against this one right now. It's been a bit since I tested that workflow but I noticed this yesterday as well. Stand by for now on that one.

 

[blau]

cd /home/brewpi sudo git checkout devel sudo /home/brewpi/utils/doPerms.sh sudo systemctl restart brewpi

"sudo systemctl restart brewpi" returns "Failed to restart brewpi.service: Unit brewpi.service not found"

 

[LBussy]

If you have added multi-chamber, then use "sudo systemctl restart {chambername}"

 

[blau]

I understand, I have corrected the syntax and now fine. Anyway the problem persists, nothing has been solved. I keep getting "Cannot connect to script" in the header and "error while receiving ..." in the terminal of "device configuration" It doesn't show any device.

 

[LBussy]

I forgot one thing ... in the directory issue the command: "sudo git pull", then do the doPerms and restart again.

 

[LBussy]

I configure and update but the temperature reading does not work.

Okay, this is fixed in devel AND in my current fermentation chamber.

I'll release it later this week, but for now, the steps are:

cd /home/brewpi
sudo git fetch --all
sudo git checkout devel
sudo git pull
sudo /home/brewpi/utils/doPerms.sh
sudo systemctl restart brewpi

 

[LBussy]

0.7.3 Bugfix Release

This release addresses the following:

• 640af2f - Error when requesting devices
• d83f05b - Error (Silent failure) when setting devices

Upgrading

Existing users of BrewPi Remix 0.5.3 and above may upgrade with:

sudo /home/brewpi/utils/doUpdate.sh

If you are not on version 0.5.3 or above (or if you have no idea what version you are on,) use the following command to upgrade to the latest version:

curl -L upgrade.brewpiremix.com | sudo bash

This must be run from within your /home/brewpi directory, or from each chamber directory in multi-chamber mode.

Returning from Devel Branch

If you followed the above instructions to use the Devel branch, you must revert first. Please do the following:

cd /home/brewpi
sudo git fetch --all
sudo git checkout master
sudo /home/brewpi/utils/doPerms.sh

At this point you should tun the upgrade command above:

sudo /home/brewpi/utils/doUpdate.sh

 

[blau]

Hello, I have updated and I have seen some error in the process, maybe it is normal. The error persists but, do not take it as a definitive information. I'm away from home, doing the update remotely (remote.it works great, thanks for the tip) Today is a long day at work for me and I don't get home until tomorrow. Once there I am going to restore a backup copy of my Sd and do the new installation. When I have it done I report the result. Thanks for such continuous support.

 

[Brewski_59]

0.7.3 Bugfix Release

This release addresses the following:

• 640af2f - Error when requesting devices
• d83f05b - Error (Silent failure) when setting devices

Upgrading

Existing users of BrewPi Remix 0.5.3 and above may upgrade with:

sudo /home/brewpi/utils/doUpdate.sh

If you are not on version 0.5.3 or above (or if you have no idea what version you are on,) use the following command to upgrade to the latest version:

curl -L upgrade.brewpiremix.com | sudo bash

This must be run from within your /home/brewpi directory, or from each chamber directory in multi-chamber mode.

Returning from Devel Branch

If you followed the above instructions to use the Devel branch, you must revert first. Please do the following:

cd /home/brewpi
sudo git fetch --all
sudo git checkout master
sudo /home/brewpi/utils/doPerms.sh

At this point you should tun the upgrade command above:

sudo /home/brewpi/utils/doUpdate.sh

I followed the above instructions to revert to master. Yet My version reports as

BrewPi Remix version: 0.7.3 (devel) [ 2959fa2

Shouldn't it have changed to Master?

 

[LBussy]

I have updated and I have seen some error in the process, maybe it is normal.

No, errors would not be normal. I need to see what they are if you saved them.

Shouldn't it have changed to Master?

Yes, I'll run through the workflow here in a bit and triple-check.

 

[LBussy]

Shouldn't it have changed to Master?

I think I see where we went sideways. For you *only* do the following:

cd ~/brewpi-tools-rmx/
git fetch --all
git checkout master
cd /home/brewpi
sudo git fetch --all
sudo git checkout master
cd /var/www/html
sudo git fetch --all
sudo git checkout master

Then you can do the update:

sudo /home/brewpi/utils/doUpdate.sh

The back-story: BrewPi Remix is made of three separate repositories. I'm going to reduce that to two "soon", and may go to one. It's a carry-over from the way Elco did the original project. The update will not change your branch by design. I have a script I have been working on to manage switching between branches but it's not done yet.

 

[Brewski_59]

Updated

BrewPi Remix version: 0.7.3 (master) [ 830d698 - 0.7.3 Bugfix Release (#66) ]

 

[duncan.brown]

@LBussy I'm thinking about switching my SS Brewtech Fermeters from the FTSS to BrewPi Remix. Taking a quick look at the code, am I correct that all of actual process-control work is done from the brewpiLoop() on the Arduino and the Pi code is just used to provide a web interface that reads/writes data over the serial link and provides the logging?

 

[LBussy]

Pretty much. The UI does allow things like temp profiles, but maintenance of a given temperature is all in the controller.

If you are thinking glycol, there's a couple of non-obvious things that we can walk through but I did create a glycol branch in devel this week.

 

[duncan.brown]

Pretty much. The UI does allow things like temp profiles, but maintenance of a given temperature is all in the controller.

Great, thank you.

If you are thinking glycol, there's a couple of non-obvious things that we can walk through but I did create a glycol branch in devel this week.

Yes, my Arduinos will be running relays for the glycol pumps and relays for the heater belts on the fermenters, with one-wire temperature sensors in the thermowells. It looks like

https://github.com/brewpi-remix/brewpi-firmware-rmx/issues/14
is implementing the glycol fixes?

 

[LBussy]

It looks like https://github.com/brewpi-remix/brewpi-firmware-rmx/issues/14 is implementing the glycol fixes?

Yessir. Right now it's easiest if you use PIO and build the "Glycol" variant. You'll use the Beer ONLY probe. If you are going to control the Glycol chiller with BrewPi then you'll need a second "chamber" but you can always keep a view on the Brew's chamber by using a "Room" probe in the glycol.

I don't have Glycol here, so it's been a crapshoot to figure out how to support it with some style. I mean I have zero doubts about the temperature control, it's more about it actually saying things like "Glycol" and "Fermenter" in the UI.

If you are wanting to use an ESP device instead, that may be a little more work (for me, not you).

 

[duncan.brown]

Perfect, thanks. I just ordered another Pi B+ to run it, so when that arrives I'll start playing around with the install. I'll be running each fermenter on its own Uno to keep things simple. My glycol chiller has it's own thermostat, so I'll just use a probe to monitor the temperature but not control it.

 

[LBussy]

Sounds good, sir. PR's, complaints, ideas, and kibitzing are all accepted.

 

[blau]

No, errors would not be normal. I need to see what they are if you saved them.

Sorry I couldn't save the error.

Anyway, once I have returned home, I have done the following:
- I have restored a copy of my sd
- I have installed brewpiRemix again.
- I have configured config.cfg.
- I check ping to the IP of the mini D1 (from my pc and from raspberry)
- I access the brewpi host page.
- I open the page "device configuration". It has not detected devices on the first try, I suppose it is normal due to the wifi communication.
- I configure devices "0 and 2" and apply ...
You can see the result. The devices are not installed.
I have to say that I have checked the cables of my installation.
My connection is this:
+ 5v -> + 5v Mini D1; + 5v SSR; Endurance; red probe lead.
-5v -> - 5v Mini D1; black probe wire
D5 -> -5v SSR
D6 -> Resistance; yellow probe lead.

 

[LBussy]

I see the issue, I don't believe the issue. I'm having some github challenges apparently and I'll have to figure that out after coffee. Please standby.

 

[LBussy]

Okay - for the technical folks who may get a kick out of this: You actually have to press the "merge" button to merge code. Go figure!

Sorry about the problems. If you have upgraded already, just do it again and it will work.

Also, @blau: The only device that should be assigned to "Beer 1" is the beer probe. All of the rest should be "Chamber Device." I need to remove that "configuration" one of these days.