BrewPi Remix – What’s Old is New Again

[bloombrews]

I honestly have no idea how you even got any readings if the OneWire is on the wrong pin.

It has been "working" for 3 days with the input pin still on A4, not A0
It is possible that this card does not have the glycol option on it?
I always picked this option when i did a new sd card, so I have no idea either
I just put another different card into a different Raspberry Pi, and it seems to be working also -
It has not been running long enough to see if the relay's will open and close for Heat or Cooling

 

[LBussy]

Glycol is on the Arduino, not the Pi. You must have the correct firmware flashed for your woring, you should be able to see the board version in the stdout.txt log.

 

[bloombrews]

Glycol is on the Arduino, not the Pi. You must have the correct firmware flashed for your woring, you should be able to see the board version in the stdout.txt log.

Yes, Lee! I was just trying to see if it could be a misbehaving Pi or a corrupted sd card. I did not try another UNO
But, so far, it is switching the relays for Heat and Cool good so far....
Not sure If I got the correct syntax to see the logs-
Thanks for being patient with a dank unranked amateur

hacker - Me!

 

[bloombrews]

eth0 Link is down
on reboot. This may be the problem why my connection to the GUI of the RPRemix goes down periodically?
I do not use an ethernet cable, but use a wireless dongle in the RPi. I am not sure upon reboot, that if there is no cable pluged in to the Pi, that eth0 will automatically go down. The UNO is running the script, as I can see the relays opening and closing periodically for Heat and Cool. So it looks like it is just an RPi issue that drops the connection periodically, and my GUI freezes on the RPiRemix dashboard. I never had this problem a few weeks ago, when I used the same pi, but with the Legecy version of BrewPi . I also got the latest version of Raspian desktop, and this is possibly where the problem may be.
When the RPi freezes up, both the red and green lights stay constant on.
Any thoughts ?

 

[LBussy]

Not sure If I got the correct syntax to see the logs-

You would have to use cat, more or tail to see the logs:

cat /home/brewpi/logs/stdout.txt

These are Unix utilities, a plethora of information may be found about these utilities by using man (manual), e.g.:

man cat

When the RPi freezes up, both the red and green lights stay constant on.

That really suggests a Pi issue, but it's hard to say. One thing I can think of that definitely makes things slow down is if you use the same log for multiple brews (like your chart is months old.) Do you start a a new one each time?

The eth0 being down is not an issue.

 

[bloombrews]

You would have to use cat, more or tail to see the logs:

cat /home/brewpi/logs/stdout.txt

These are Unix utilities, a plethora of information may be found about these utilities by using man (manual), e.g.:

man cat

That really suggests a Pi issue, but it's hard to say. One thing I can think of that definitely makes things slow down is if you use the same log for multiple brews (like your chart is months old.) Do you start a a new one each time?

The eth0 being down is not an issue.

I have the same issue with an ongoing log, or start with a new card and wait until it can parse data to the graph.
I thought yesterday, that it may be an issue with Wi-Fi extender I put in, to try and boost the signal of the Rapt Pill wifi. I took it out of service, and rebooted to the main home router (good signal, 4/5 bars). The script would run fine as usual, then go blank, maybe a half-hour to hour later, when I was not actively working in the GUI on something. There is a question asked when you download the Remix, if you want to run a sub-routine periodically to verify Wi-Fi is established. I am paraphrasing this. I thought today I would try a new card, download a fresh copy, and say "NO" to this question. Then see if the RPi would keep its connection to the wifi and script. I am not sure how to delete/back out, this part of the download, so as not to screw any variables up, I would do a fresh copy.
Thanks again, Lee

 

[LBussy]

There is a question asked when you download the Remix, if you want to run a sub-routine periodically to verify Wi-Fi is established. I am paraphrasing this. I thought today I would try a new card, download a fresh copy, and say "NO" to this question. Then see if the RPi would keep its connection to the wifi and script. I am not sure how to delete/back out, this part of the download, so as not to screw any variables up, I would do a fresh copy.

The wifi check is a remnant of the original BrewPi. I kept it because people are sure they need it. I don't believe it's the same problem it once was, which is why it is now a default "No" on the installer.

If you have enabled it and want to turn it off, issue these two commands:

sudo systemctl stop wificheck
sudo systemctl disable wificheck

If you have not installed it and want it installed:

sudo /home/brewpi/utils/doDaemon.sh

 

[bloombrews]

Is there anyway to remove old "Installed Devices" (temperature sensors), under the Maintenance Panel from the UNO?
I removed all the sensors from the controller, and when you do a Refresh, all the old ones show up as "Installed". This is confusing when your trying to install new sensors, and old one-wire addresses keep showing up on the installed list, even though they do not exist.
After happily running BrewPiLegacy for 7 years, I am not giving up fixing this new install.

This can be my problem - I am getting a "Low voltage detected" message. I then used another 5v switchable power supply (I been using for years OK on same B+3 Pi ) and get the same message
I issued these commands -
vcgencmd get_throttled and get "throttled=#####"
and this command - dmesg this comes back - "Under-voltage detected!"
I plugged in another 5v switchable power supply and get the same low voltage warning. I will try another RPi B+3 with this card and supply and see if the message comes back, then I know it is the supply and not the Pi voltage regulator on the board or something else.

 

[day_trippr]

Erase the Arduino eeprom.

Maintenance Panel - Advanced Settings, then scroll the Control Constants pane to the bottom, and click on the "Reset controller to factory defaults" button....

Cheers!

 

[LBussy]

This can be my problem - I am getting a "Low voltage detected" message. I then used another 5v switchable power supply (I been using for years OK on same B+3 Pi ) and get the same message
I issued these commands -
vcgencmd get_throttled and get "throttled=#####"
and this command - dmesg this comes back - "Under-voltage detected!"
I plugged in another 5v switchable power supply and get the same low voltage warning. I will try another RPi B+3 with this card and supply and see if the message comes back, then I know it is the supply and not the Pi voltage regulator on the board or something else.

This is very likely your problem. Get a real Raspberry Pi power supply and see if the issue goes away. $8 to get rid of your issues is cheap.

 

[bloombrews]

This is very likely your problem. Get a real Raspberry Pi power supply and see if the issue goes away. $8 to get rid of your issues is cheap.

@day_trippr
I'm almost There.....! I dug out a CanaKit power supply, and Viola! It has been 100% stable for hours now. (Dont use a switched after-market supply)
I am trying to get the Probes up now, and something I never seen before, keeps happening when I "Apply" the settings. For some reason, Detected devices sees both the room probe and the warm probe under my ass, to keep warmer
But, after "Apply", both Temps go to reading the same temp?
Here DETECTED- Before Applying
second picture you will see, INSTALLED, after hitting Apply after each line I define (or after I define both lines, the try Apply)

 

[day_trippr]

But, after "Apply", both Temps go to reading the same temp?

Well that's certainly not right. Does it do that repeatedly?
Did you do the eeprom reset thing before you started configuring the devices?

Cheers!

 

[LBussy]

I'm almost There.....! I dug out a CanaKit power supply, and Viola! It has been 100% stable for hours now. (Dont use a switched after-market supply)

That was me that time - but after Dave has told me that liek 1000 times.

I am trying to get the Probes up now, and something I never seen before, keeps happening when I "Apply" the settings. For some reason, Detected devices sees both the room probe and the warm probe under my ass, to keep warmer
But, after "Apply", both Temps go to reading the same temp?
Here DETECTED- Before Applying
second picture you will see, INSTALLED, after hitting Apply after each line I define (or after I define both lines, the try Apply)

Do the EEPROM reset Dave mentions. That's an Arduino bug.

 

[bloombrews]

Well that's certainly not right. Does it do that repeatedly?
Did you do the eeprom reset thing before you started configuring the devices?

Cheers!

YES, it keeps doing the same "thing". Sometimes it will pick the first temperature to repeat twice, and other times it will pick the second different temp to reapeat twice.
YES, I did reset the eeprom by your instructions, and also reading the Documentation, to make sure I did not forget anything.
This is really weird! I am not certain if you MUST Apply each change individually, or you can do a "universal" Apply by changing all the detected devices, and then apply? I tried both ways and keeps coming back with the same value, it picks one of the probes, at seemingly random, as the other different temp probe value disappears (although you can see the different 1-wire address)

 

[bloombrews]

Do the EEPROM reset Dave mentions. That's an Arduino bug.

Yes @LBussy , I did the "Factory Reset" of the eeprom
Thanks

 

[LBussy]

Reset, set one and apply, see if it accepts the change. If it does, keep doing that.

 

[bloombrews]

Reset, set one and apply, see if it accepts the change. If it does, keep doing that.

I did that Lee. Then when I go to the second "detected" probe to assign it, then Apply, shazam....now both temperatures are the same! This has to be a bug

 

[Thorrak]

I did that Lee. Then when I go to the second "detected" probe to assign it, then Apply, shazam....now both temperatures are the same! This has to be a bug

Is this an ESP32/ESP8266 or an Arduino? (Apologies if you answered this!)

 

[bloombrews]

Is this an ESP32/ESP8266 or an Arduino? (Apologies if you answered this!)

Its a Seinsmart UNO. I could try changing it to another UNO. I have a few laying around that successfully ran the Legacy for years

 

[bloombrews]

@Thorrak , @LBussy , and @day_trippr , Is this a "CASE", of use an original Arduino, or good luck? I used these Seinsmart, RexQualis, and another clone that just says UNO, on the Legacy and had no problems. Not sure what Controller I used out of my Stash? I did post a picture of the controller a dozen posts back, and I think @day_trippr said it has the same Chips as the Arduino (paraphrasing)
Thanks the Beer God"s, my Baltic Porter Lager is chugging along, thanks to the Seinsmart never crashing, but the Pi running it is a disaster!
I was looking to buy a new Pi, and see the RPi 4's are now $130 with a quad core 64 bit. Damn! What ever happened to the Poor People buying the $35 Pi in the past? I thought it was a "Steal", and bought a bunch, so I would not have to go in the other room, and grab the only 1 that I had...

 

[day_trippr]

I am not certain if you MUST Apply each change individually, or you can do a "universal" Apply by changing all the detected devices, and then apply?

Most of my UNO R3 modules are Sainsmarts.

When I set up an UNO I rattle through all of the available device settings top to bottom hitting each "Apply" button along the way. I don't think there's a way to set all the devices then "Apply" them simultaneously...

Cheers!

 

[bloombrews]

Well.... the new transformer did help the Raspberry Pi from misbehaving. I can freely surf the internet, the Green light flashes every 10 seconds or so, the Red light is obviously on steady. So I think I eliminated the Pi as the culprit for the Remix script loosing the updates to the GUI graph and script.
This is seperate Pi, with good applied temp sensors, running my Baltic Porter and others, the past few weeks. @day_trippr , @LBussy , not the one with the sensors that I can not apply from yesterday. (Have not retried today)
You can see several drops of the Script, the past week, and last night. I have to reboot to get it up again

 

[day_trippr]

Have you looked at the log files for the above system to see if there were events logged when the link took a dirt nap?

Cheers!

 

[bloombrews]

I had to do 2 reboots this time. First time all I got was a blank screen with no Raspberry desktop. I had to Control+Function+Alt+Del, and play around with Control+Alt+F1, to force my Terminal to open, so I could sudo reboot now. I unchecked the Chamber Setting for this screenshot -

 

[day_trippr]

So the temperature is ramping up but it's strange to me that there is such a wide spread between the beer and chamber sensors through that plot - the lines never get close never mind cross...

Cheers!

 

[bloombrews]

So the temperature is ramping up but it's strange to me that there is such a wide spread between the beer and chamber sensors through that plot - the lines never get close never mind cross...

Cheers!

The "Chamber" temperature is just the second temp probe sitting near the 300 watt rod heater (heating the beer attached with a tri-clamp) It is acting more of a Room Temperature probe, The Beer probe is in a thermowell on the tank. The cooling is with cold 36 degree water.
This is on the RevC Shield
The other Pi I am having problems getting the probe readings to Apply, is on the Glycol Shield
I do not cycle a fridge compressor. And no Chamber.
I am in the process of either using Fermwrap tape, a smaller 100 watt rod heater, or a heating plate, so the heat overshoot is not so drastic
thanks @day_trippr

 

[day_trippr]

Ah, I didn't realize this was one of your glycol setups. Probe readings make a little more sense now

 

[bloombrews]

Ah, I didn't realize this was one of your glycol setups. Probe readings make a little more sense now

I think I drove @LBussy crazy over the years, with all my hack jobs. If it was never tested, leave it to me, to screw it up.
My system works really well with the BPR. I never had a chance yet to run it with the Glycol PID, so I expect to see the Heat/Cool cycles to hone in better when I do. Just have to get the Device Configuration to work.....
Thanks again @day_trippr , your helping a LOT of people make better beer!

 

[bloombrews]

Okay, try this for now:

curl -L https://raw.githubusercontent.com/brewpi-remix/brewpi-tools-rmx/CVE-2022-24765/bootstrap.sh | sudo bash

I'm not completely done with testing the install, but I passed the spot where you got the error. Here is the change for those who are curious. Technically adding a vulnerability, but I'm just reverting the security change in git which should not matter with a Raspberry Pi. If it does matter, you should already know how to fix this.

Lee,
Is this the "goto" line command to download Remix? Your original line near the beginning of this thread, still does not work
It took a little bit of searching to find this above (Page 15)
I gave up trying to get my probes to "Apply" correctly and am starting over fresh BPR
Thanks

 

[LBussy]

Is this the "goto" line command to download Remix?

Temporarily, if you have a new Raspbian image. This will work, as soon as I make my next release the original will work again.