Blade_Beam
Member
If I could remember the login....phpmyadmin
If I could remember the login....phpmyadmin
FixedIf I could remember the login....
For anyone else who is experiencing this problem (as I was on each of 2 installs: One on a Model B rev 2 with 32 gb running buster and the second on Pi 4 2 gb with 64gb same OS) using the RandR+ branch of the command line (curl -L https://raw.githubusercontent.com/rtlindne/RaspberryPints/master/util/installRaspberryPints | sudo bash) the problem does not seem to be overheating, corrupted databases, lack of hard wiring the probe, insufficiently powered Pi, etc (at least in my case) but rather that the Pi and/or the software is loosing track of where the temperature probe is and therefore defaults out to the minimum reading of 32 F in the setup of raspberry pints minimum and maximum or just freezes on the last good measurement, time and date. (I determined this by watching the folder containing the probe data dissapear at some point under /sys/bus/w1/devices, or if it was there, returning the correct temperature as described below, but raspberry pints did not show that data.)Well ... I replaced all connections between the probe and the RPi and now have the probe directly connected to the RPi GPIO header (I had some terminal strips for the transition from inside the keezer to outside the keezer, I have eliminated them) ... and now I am getting good, regular temp readings. The only remaining issue is that the temp reading is not displaying in the upper right corner like it should, even though "Show Avg Temperature on home screen" is set to "on".
sudo nano /boot/config.txt
sudo raspi-config
and enabled the one-wire interface#added this to see if I could get the probe to stabilize
gpiopin=4
sudo reboot
cd /sys/bus/w1/devices
ls
cd 28-0206917714fc
cat w1_slave
Just to be clear, I did enable the one-wire probe through the interface provided by the sudo raspi-config command. I think that is how the line "dtoverlay=w1-gpio" gets inserted into the config.txt file. My only addition was the "gpiopin=4" which I believe is pin 7 on my Pi(s).I'm a bit surprised you could access the probes at all without enabling the interface.
Never tried that myself. Haven't needed to declare the pin, either, but maybe this is all a Buster thing...
Cheers!
I quite literally just did a as I would for any water connection in my house and used teflon tape on the threads. No problems or leaks that I’ve seen yetI have a question for anyone that is familiar with BSPP pipe threads. I have flowmeters which have 3/8" male BSPP threads, and I have hose barbs that have 3/8" female BSPP threads. There is no shoulder on the flowmeters, so the seal needs to be made internally (between the end of the male flowmeter and the inner end of the female hose barb). Do I use copper crush washers inside the hose barbs? Do I use o-rings inside the hose barbs? And if so, any idea what size they would be?
That was my first try ... 6 to 8 wraps of teflon tape on each connection and tightened them up. Woke up to a gallon of beer on the floor of my keezer.I quite literally just did a as I would for any water connection in my house and used teflon tape on the threads. No problems or leaks that I’ve seen yet
However is there any way to get it to auto refresh? If I pour the display stays the same (direct off the pi and accessed via the Pi's IP). It displays the new values once refreshed but can't imagine this is normal?
sudo apt-get install xdotool x11-xserver-utils
refresh.sh
in /home/pi
that contains#!/bin/sh
/bin/sleep 6
/usr/bin/lxterminal --command watch -n 90 xdotool key ctrl+F5 &
chmod 755 /home/pi/refresh.sh
/home/pi/refresh.sh
. You can also add it to /etc/xdg/lxsession/LXDE-pi/autostart
if you want it started automatically.-n 90
. You can tweak this as you want. Since the window with the focus should always be chromium, if it's in kiosk mode, this will trigger a reload of the page.I've been hitting the same issue with my install and here's what I found. There's no JavaScript or HTML in the main index.php page to trigger a periodic refresh, so any updates you make (adding a new tap, changing a keg, etc.) need a manual refresh on the browser that's displaying the R'Pints home page.
As @day_trippr said, if you're using the flowmon daemon, this opens a multicast socket that listens for connection a connection from browsers (The links below are to my fork of the RandR+ version):
https://github.com/duncan-brown/RaspberryPints/blob/master/python/ws/rpupdate_wsh.py#L36
Then there is JavaScript run by the R'Pints index.php onload() to open a web socket connection to this server:
https://github.com/duncan-brown/RaspberryPints/blob/master/admin/scripts/ws.js#L45
If an update message gets sent from the server flowmon to the browser via the web socket, it triggers a reload of the web page:
https://github.com/duncan-brown/RaspberryPints/blob/master/admin/scripts/ws.js#L58
This will update the whole page.
However, it looks like information from Plaato is just pulled like a static database query by apache when you load index.php:
https://github.com/duncan-brown/RaspberryPints/blob/master/index.php#L75
After that, there's no communication to tell your browser to refresh the page and it stays static unless you do a manual reload.
Fixes to R'Pints would be:
If you want a workaround without hacking R'Pints, you could use the following trick on the machine that is running chromium in kiosk mode to display the beers. First, install a couple of extra tools with:
- Add some code to index.php to get it to do a refresh every e.g. 300 seconds so at least you're no more than 5 mins out of date. I might put in a patch to do this, if the attempt to open a web socket fails because the user isn't running flowmon.
- Fix the web socket code to update when things other than flowmon change, but since Plaato data is pulled from the remote Plaato server, that would need a daemon on the R'Pints server to interrogate it for changes, which is more complexity and CPU load than option 1, so probably not worth the effort.
Bash:sudo apt-get install xdotool x11-xserver-utils
The create a script calledrefresh.sh
in/home/pi
that contains
Bash:#!/bin/sh /bin/sleep 6 /usr/bin/lxterminal --command watch -n 90 xdotool key ctrl+F5 &
Make this script executable by running the commandchmod 755 /home/pi/refresh.sh
Then start this script when you start the browser by running the command/home/pi/refresh.sh
. You can also add it to/etc/xdg/lxsession/LXDE-pi/autostart
if you want it started automatically.
The script will send CTRL+F5 to the window that has the focus every 90 seconds (set by-n 90
. You can tweak this as you want. Since the window with the focus should always be chromium, if it's in kiosk mode, this will trigger a reload of the page.
So just install the latest Raspian and then just run the command 'curl -L install.rpints.com | sudo bash'?Follow this link here.. Also read this thread from about 100 pages onwards. Lot of reading I know but you will learn heaps.
Nice kegerator..
https://www.rpints.com/
That was my first try ... 6 to 8 wraps of teflon tape on each connection and tightened them up. Woke up to a gallon of beer on the floor of my keezer.
I purchased some iSentrol stainless steel flowmeters from AliExpress, they're 1/4" BSPP. I have some 6MM ID X 9MM OD and 6 MM ID x 10MM OD copper crush washers on the way from eBay, hopefully one of those sizes will fit. If not, I'll try some o-rings.Ouch. You definitely need a washer with BSPP. The last P stands for parallel so the threads don't have the tapering of NPT (the usual North American thread) or BSPT. Just wrapping with teflon tape is a gamble. What type of flow meters do you have? I have some SF800s on the way from the Netherlands, so if you have those I can measure the washer size before I install them.
I have stainless flowmeters (male) with stainless barbs (female), both threaded in 1/4" BSPP. I'm just not used to BSPP fittings, everything I've used in the past was NPT and teflon tape is all you need.If found and determined to use a female BSPP barbed fitting with an SF800 I think you'd be best taking it to a hardware store and finding a nice thick flat Buna-N gasket that will stuff into the threaded end of the fitting. I would be leery of using an actual metal crush water with plastic fittings as it's easy enough to blow the back out of these things through over-torque - and that's with rubber gaskets.
fwiw, both models of John Guest fittings I have used with my SF800 meter fleet have captive integrated gaskets. While the latest/current version I'm usingi is 8mm OD by 3/8 BSPP to accommodate the EVAbarrier tubing I converted to, I used 3/8 OD by 3/8 BSPP with a stemmed 3/8 OD to 3/16" barb insert to work with the Bevlex 200 3/16" ID line I used to run. That would be a reliable solution here.
I greatly prefer the full PTC system with the EVAbarrier vs barbs 'n' clamps 'n' stuff.
Cheers!
I have stainless flowmeters (male) with stainless barbs (female), both threaded in 1/4" BSPP. I'm just not used to BSPP fittings, everything I've used in the past was NPT and teflon tape is all you need.
Yeah mate. You can choose the RANDR+ version or the TOBOR version i think its called. I chose RANDR+.So just install the latest Raspian and then just run the command 'curl -L install.rpints.com | sudo bash'?
Yes, I've seen that page, but thanks! My situation is slightly different than the BSPP example on that sheet, the male end of my fitting has no shoulder, so an external crush washer will not work, the seal needs to be made at the very end of the male fitting where it bottoms out into the female fitting. Hopefully the crush washers I have coming will fit inside the female fitting yet will be large enough to seal against the male end.If it's metal to metal, then you should be good with the copper crush washer. I'm a John Guest shop like @day_trippr so my plan is to use the BSPP to 3/8" OD fittings Swissflow includes to go directly to my BevSeal Ultra.
Here's a page with some nice images explaining why you need the washer:
https://www.ralstoninst.com/news/story/the-difference-between-npt-bspp-and-bspt-seals
the male end of my fitting has no shoulder
Exactly! Unfortunately, the face of the male fitting is not machined to fit an o-ring, it is just a flat mating surface. Hopefully the internal crush washers will seal the joints, if not then I'll try to find some flat rubber or nylon washers or something. Good idea with the CO2 test, I have an empty keg I can connect and pressurize to test each of the connections for leaks before connecting my full kegs to them.Ah, I see from the image of the sensor. Looks like you are making a HIAB (flat-face) BSPP fitting:
https://www.hoseandfittings.com/int-thread-id/#hiab
Normally that uses a rubber o-ring to make the seal, but I'd give the copper crush washer a go (with a drip tray under the sensor) and see what happens. You could do a test where you just pressurize it with 25 psi of CO2, then squirt the connections with star san, and watch for bubbles (if you don't want to risk an initial test with beer).
Yeah mate. You can choose the RANDR+ version or the TOBOR version i think its called. I chose RANDR+.
MoreJust to be clear, I did enable the one-wire probe through the interface provided by the sudo raspi-config command. I think that is how the line "dtoverlay=w1-gpio" gets inserted into the config.txt file. My only addition was the "gpiopin=4" which I believe is pin 7 on my Pi(s).
I'm a bit surprised as well that this is required, but my Raspberry Pints is still chugging along with the most recent temp and time flawlessly.
If I remember correctly from all the threads I looked through to figure this out, you are not running the RandR+ branch. This might also contribute to how the temp data is being called or somehow forgotten and might explain why you didn't need to add this step. Curious to know if there is a correspondence between flavor of this software and this problem. From my experience, it certainly is consistent across models of Pi running the same OS.
In any case, the install script provided a great way to get rpints running. Many thanks to everyone who contributed to it.
More fun with the role of the /boot/config.txt file was had when I attempted to run my Pi 4 2 gb with rpints installed from a 16 gb SSD drive instead of the SD card.For anyone else who is experiencing this problem (as I was on each of 2 installs: One on a Model B rev 2 with 32 gb running buster and the second on Pi 4 2 gb with 64gb same OS) using the RandR+ branch of the command line (curl -L https://raw.githubusercontent.com/rtlindne/RaspberryPints/master/util/installRaspberryPints | sudo bash) the problem does not seem to be overheating, corrupted databases, lack of hard wiring the probe, insufficiently powered Pi, etc (at least in my case) but rather that the Pi and/or the software is loosing track of where the temperature probe is and therefore defaults out to the minimum reading of 32 F in the setup of raspberry pints minimum and maximum or just freezes on the last good measurement, time and date. (I determined this by watching the folder containing the probe data dissapear at some point under /sys/bus/w1/devices, or if it was there, returning the correct temperature as described below, but raspberry pints did not show that data.)
To fix this I followed instructions in this article (Using DS18B20 Digital Temperature Sensors with the Raspberry Pi - Raspberry Pi Spy ) by implementing the following commands:
sudo nano /boot/config.txt
at the bottom of the file you will see the following if you have gone throughsudo raspi-config
and enabled the one-wire interface
dtoverlay=w1-gpio
below that I added the specific gpiopin number that the data wire from the probe was connected to on the Pi through the 4.7K resistor. It looks like this in my config.txt:
#added this to see if I could get the probe to stabilize gpiopin=4
I then did a
sudo reboot
logged back in, went to
cd /sys/bus/w1/devices
did als
selected the number of my probe and went into that directory:
cd 28-0206917714fc
and then ran
cat w1_slave
to get the reading:
b6 01 55 05 7f 7e 81 66 ad : crc=ad YES
b6 01 55 05 7f 7e 81 66 ad t=27375
t=27375 tells the software that the temperature is 27.375 C
I've run this for most of a day and it keeps on updating everything correctly on the landing page upper right-hand corner.
Hopefully, this will help someone experiencing this problem, as it took me quite some time to find this fix.
Yeah mate. You can choose the RANDR+ version or the TOBOR version i think its called. I chose RANDR+.
Yes, that sounds correct, hard metric 2mm pitch. I cut them all off and used TinyXLRs...
I am based in the UK and the Swiss flow meters are not really a thing over here as far as I can tell.
Enter your email address to join: