• Please visit and share your knowledge at our sister communities:
  • If you have not, please join our official Homebrewing Facebook Group!

    Homebrewing Facebook Group

[Version 2 Release] RaspberryPints - Digital Taplist Solution

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
I’m at my wits end. I can get my Swiss flow meters to register pours with water, but as soon as I put a keg of beer on, it doesn’t recognize anything. I have two taps with meters and same thing occurs on both. Works fine running water through, once keg with beer is on, doesn’t recognize pours. Is there some delay settings that need adjustment or something perhaps because of foam? Working on this problem for weeks. Thank you.
 
Is there some delay settings that need adjustment or something perhaps because of foam? Working on this problem for weeks.
What version are you running? I ask because my version has a log (/var/log/rpints.log) that might give some insights to what is going on. If it doesn't help I have some pending changes to add more tracing from the Arduino to track issues like these, I can commit them for you to get
 
What version are you running? I ask because my version has a log (/var/log/rpints.log) that might give some insights to what is going on. If it doesn't help I have some pending changes to add more tracing from the Arduino to track issues like these, I can commit them for you to get
I’m running the RandR+ version. I’ve looked at the log and when running water I see the pours recognized just fine. When I put the beer on and pour through tap, nothing registers on the log file. I put a meter on both pins when beer is running and I can see the voltage change as beer is running, but it’s not refreshing the screen or recognizing anything once flow stops. I’ll try to get the log file here. Running on a Arduino uno.
 
I’ll try to get the log file here. Running on a Arduino uno.
Think this is the first time Ive seen someone run into this issue.

I just committed my updates if you get the latest sketch and hex files (rerun the installer will prompt if you want to update)

You should also turn on debugging in python/Config.py by changing False#True to just True so the lines read
config['flowmon.debug' ] = True
#logging settings for pintdispatch
config['dispatch.debug' ] = True

once you test with the latest you will want to look for "RT L" in the log (it stands for Reset Tap Line it will then print the Pin, tap number, current millisecond on the arduino, last millisecond it got a pulse, difference between them, delay to send pour, current pulse count, and pour trigger value (number of pulses to send a pour)

Or simply put, post the log here an I can decipher
 
Think this is the first time Ive seen someone run into this issue.

I just committed my updates if you get the latest sketch and hex files (rerun the installer will prompt if you want to update)

You should also turn on debugging in python/Config.py by changing False#True to just True so the lines read
config['flowmon.debug' ] = True
#logging settings for pintdispatch
config['dispatch.debug' ] = True

once you test with the latest you will want to look for "RT L" in the log (it stands for Reset Tap Line it will then print the Pin, tap number, current millisecond on the arduino, last millisecond it got a pulse, difference between them, delay to send pour, current pulse count, and pour trigger value (number of pulses to send a pour)

Or simply put, post the log here an I can decipher
Thanks so much!

I've run the update and here is the output of the log after running beer through the tap.

pi@rpints:~ $ tail -f /var/log/rpints.log
2020-07-11 13:05:13 RPINTS: Not Configured to run Fan
2020-07-11 13:05:14 RPINTS: waiting for Arduino to come alive
2020-07-11 13:05:16 RPINTS: Arduino alive...
2020-07-11 13:05:16 RPINTS: getting config data for Arduino
2020-07-11 13:05:16 RPINTS: Arduino config, about to send: C:4:6:3:4:5:0:300:200:30:250:0:0:1|
2020-07-11 13:05:16 RPINTS: Waiting for Config Response
2020-07-11 13:05:16 RPINTS: Arduino says: C:4:6:3:4:5:0:300:200:30:250:0:0:1|

2020-07-11 13:05:16 RPINTS: listening to Arduino
2020-07-11 13:05:16 RPINTS: Sending Status;NOTOK;-1;0;0;0;0;0;|
2020-07-11 13:07:54 RPINTS: RT L 6 0 145411 145110 301 300 13 200
2020-07-11 13:07:54 RPINTS: Sending Status;NOTOK;-1;0;0;0;0;0;|
2020-07-11 13:07:57 RPINTS: RT L 6 0 147811 147510 301 300 17 200
2020-07-11 13:07:57 RPINTS: Sending Status;NOTOK;-1;0;0;0;0;0;|
2020-07-11 13:07:59 RPINTS: RT L 6 0 150284 149983 301 300 14 200
2020-07-11 13:07:59 RPINTS: Sending Status;NOTOK;-1;0;0;0;0;0;|
 
Try running tail -F /var/log/apache2/error.log and see if any errors are printed when you try and access the page.

You can also try looking at tail -F /var/log/apache2/access.log and you should see the GET message when you try and access the page.
pi@rpints:~ $ tail -F /var/log/apache2/error.log
[Sat Jul 11 16:06:10.932606 2020] [php7:warn] [pid 5225] [client ::1:57522] PHP Warning: Error while sending QUERY packet. PID=5225 in /var/www/html/admin/includes/managers/config_manager.php on line 13, referer: http://localhost/
[Sat Jul 11 16:06:10.932815 2020] [php7:error] [pid 5225] [client ::1:57522] PHP Fatal error: Uncaught Error: Call to a member function fetch_array() on bool in /var/www/html/admin/includes/managers/config_manager.php:14\nStack trace:\n#0 /var/www/html/includes/common.php(14): getAllConfigs()\n#1 /var/www/html/index.php(269): printBeerList(Array, '4', 'Keg')\n#2 {main}\n thrown in /var/www/html/admin/includes/managers/config_manager.php on line 14, referer: http://localhost/
[Sat Jul 11 16:06:13.822844 2020] [mpm_prefork:notice] [pid 609] AH00169: caught SIGTERM, shutting down
[Sat Jul 11 16:06:22.424354 2020] [:error] [pid 610] python_init: Python version mismatch, expected '2.7.15', found '2.7.16'.
[Sat Jul 11 16:06:22.447065 2020] [:error] [pid 610] python_init: Python executable found '/usr/bin/python'.
[Sat Jul 11 16:06:22.447133 2020] [:error] [pid 610] python_init: Python path being used '/usr/lib/python2.7:/usr/lib/python2.7/plat-arm-linux-gnueabihf:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'.
[Sat Jul 11 16:06:22.447214 2020] [:notice] [pid 610] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads.
[Sat Jul 11 16:06:22.447241 2020] [:notice] [pid 610] mod_python: using mutex_directory /tmp
[Sat Jul 11 16:06:22.674152 2020] [mpm_prefork:notice] [pid 610] AH00163: Apache/2.4.38 (Raspbian) mod_python/3.3.1 Python/2.7.16 configured -- resuming normal operations
[Sat Jul 11 16:06:22.674278 2020] [core:notice] [pid 610] AH00094: Command line: '/usr/sbin/apache2'

pi@rpints:~ $ tail -F /var/log/apache2/access.log
::1 - - [11/Jul/2020:07:14:02 -0400] "GET / HTTP/1.1" 200 2312 "-" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
::1 - - [11/Jul/2020:09:04:21 -0400] "GET /img/logo.png?1594466042 HTTP/1.1" 200 24423 "http://localhost/" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
::1 - - [11/Jul/2020:09:05:22 -0400] "GET / HTTP/1.1" 200 2312 "http://localhost/" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
::1 - - [11/Jul/2020:10:43:41 -0400] "GET /img/logo.png?1594472722 HTTP/1.1" 200 24423 "http://localhost/" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
::1 - - [11/Jul/2020:10:44:41 -0400] "GET / HTTP/1.1" 200 0 "http://localhost/" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
::1 - - [11/Jul/2020:10:49:42 -0400] "GET / HTTP/1.1" 200 2313 "-" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
::1 - - [11/Jul/2020:14:13:30 -0400] "GET /img/logo.png?1594478982 HTTP/1.1" 200 24423 "http://localhost/" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
10.0.0.188 - - [11/Jul/2020:10:52:34 -0400] "GET / HTTP/1.1" 200 2312 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
::1 - - [11/Jul/2020:14:14:31 -0400] "GET / HTTP/1.1" 500 1522 "http://localhost/" "Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Raspbian Chromium/78.0.3904.108 Chrome/78.0.3904.108 Safari/537.36"
10.0.0.188 - - [11/Jul/2020:15:21:51 -0400] "GET / HTTP/1.1" 500 1522 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36"
 
RT L 6 0 145411 145110 301 300 13 200
what this tells me is that it only got 13 pulses in 301 milliseconds. Thats not enough to register a pour as configured and if you would change the configuration to make it a pour it wouldn't have much meaning being so small.

Are you seeing a lot of foam with the flow meters attached?
 
what this tells me is that it only got 13 pulses in 301 milliseconds. Thats not enough to register a pour as configured and if you would change the configuration to make it a pour it wouldn't have much meaning being so small.

Are you seeing a lot of foam with the flow meters attached?
Not really. I get a little foam in the beginning but was pouring without foam for 2-3 seconds before shutting off.
 
pi@rpints:~ $ tail -F /var/log/apache2/error.log
[Sat Jul 11 16:06:10.932606 2020] [php7:warn] [pid 5225] [client ::1:57522] PHP Warning: Error while sending QUERY packet. PID=5225 in /var/www/html/admin/includes/managers/config_manager.php on line 13, referer: http://localhost/
[Sat Jul 11 16:06:10.932815 2020] [php7:error] [pid 5225] [client ::1:57522] PHP Fatal error: Uncaught Error: Call to a member function fetch_array() on bool in /var/www/html/admin/includes/managers/config_manager.php:14\nStack trace:\n#0 /var/www/html/includes/common.php(14): getAllConfigs()\n#1 /var/www/html/index.php(269): printBeerList(Array, '4', 'Keg')\n#2 {main}\n thrown in /var/www/html/admin/includes/managers/config_manager.php on line 14, referer: http://localhost/
what this is telling me is that the following lines are falling and instead of producing a result its returning false (which happens when the query fails)
$sql = "SELECT * FROM config";
$qry = $mysqli->query($sql);

being such a standard query I think its something with MariaDb setup that is causing it try (from the terminal - assuming you left the default database name - raspberrypints)
sudo mysql
use raspberrypints;
SELECT * FROM config;

Let me know if that works
 
[Sat Jul 11 16:06:10.932815 2020] [php7:error] [pid 5225] [client ::1:57522] PHP Fatal error: Uncaught Error: Call to a member function fetch_array() on bool in /var/www/html/admin/includes/managers/config_manager.php:14\nStack trace:\n#0 /var/www/html/includes/common.php(14): getAllConfigs()\n#1 /var/www/html/index.php(269): printBeerList(Array, '4', 'Keg')\n#2 {main}\n thrown in /var/www/html/admin/includes/managers/config_manager.php on line 14, referer: http://localhost/

It looks like the line of code that does SELECT * FROM CONFIG to get the configuration is failing and returning NULL. Then the fetch_array() method is called on the boolean value which triggers the error.

For some reason, the code can't access the database. Can you run the following
Bash:
sudo mysql -u root -p
and enter the root password to get into mariadb, then
SQL:
show databases;
You should see a raspberrypints database. Then type:
SQL:
use raspberrypints;
SELECT * FROM config;
 
I get a little foam in the beginning but was pouring without foam for 2-3 seconds before shutting off.
I don't use swiss flow so maybe someone else that does has this happen to them. My first thought was maybe the beer was over carbonated leading to the sensor missing pulses but it doesn't sound like it since you don't have foaming issues
 
I've been running six SF800s on the original R'Pints 2.0.1 since Memorial Day weekend 2014 and have never had a meter fail to register a pour.
Also, once I over-carbonated a wheat beer and when I put it in the keezer at a proper pressure naturally the excess CO2 started coming out of solution, which by itself was enough to trigger tiny pours throughout the day and night 'til I noticed the taplist was showing that keg emptying when I'd only poured one beer :)

So I'm not sure what's going on here tbh.

Cheers!
 
It looks like the line of code that does SELECT * FROM CONFIG to get the configuration is failing and returning NULL. Then the fetch_array() method is called on the boolean value which triggers the error.

For some reason, the code can't access the database. Can you run the following
Bash:
sudo mysql -u root -p
and enter the root password to get into mariadb, then
SQL:
show databases;
You should see a raspberrypints database. Then type:
SQL:
use raspberrypints;
SELECT * FROM config;
@RandR+ ... My database is named "RPints" ... however following the instruction provided by both of you and substituting my database name I do get 102 rows returned. I also get the same 102 rows returned for the "raspberrypints" database. (I used "RPints" as the database name, because using the default "raspberrypints" caused the installation to stop for some reason).

MariaDB [(none)]> show databases;
+--------------------+
| Database |
+--------------------+
| Rpints |
| information_schema |
| mysql |
| performance_schema |
| phpmyadmin |
| raspberrypints |
+--------------------+
6 rows in set (0.001 sec)

MariaDB [(none)]> use Rpints;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [Rpints]> SELECT * FROM config;
+-----+---------------------------+-----------------------------------+--------------------------------------------------------------+-------------+-----------------------+---------------------+---------------------+
| id | configName | configValue | displayName | showOnPanel | validation | createdDate | modifiedDate |
+-----+---------------------------+-----------------------------------+--------------------------------------------------------------+-------------+-----------------------+---------------------+---------------------+
| 1 | showTapNumCol | 1 | Show Tap Column | 1 | NULL | 2020-07-10 15:42:54 | 2020-07-10 15:42:54 |
| 2 | showBeerImages | 0 | Show Beer Images | 1 | NULL | 2020-07-10 15:42:54 | 2020-07-10 15:42:54 |
| 3 | showBreweryImages | 0 | Show Brewery Images | 1 | NULL | 2020-07-10 15:42:54 | 2020-07-10 15:42:54 |
| 4 | showSrmCol | 1 | Show SRM Column | 1 | NULL | 2020-07-10 15:42:54 | 2020-07-10 15:42:54 |
| 5 | showIbuCol | 1 | Show IBU Column | 1 | NULL | 2020-07-10 15:42:54 | 2020-07-10 15:42:54 |
| 6 | showAbvCol | 1 | Show ABV Column | 1 | NULL | 2020-07-10 15:42:54 | 2020-07-10 15:42:54 |

(Truncated for brevity)

102 rows in set (0.001 sec)
 
I've been running six SF800s on the original R'Pints 2.0.1 since Memorial Day weekend 2014 and have never had a meter fail to register a pour.
Also, once I over-carbonated a wheat beer and when I put it in the keezer at a proper pressure naturally the excess CO2 started coming out of solution, which by itself was enough to trigger tiny pours throughout the day and night 'til I noticed the taplist was showing that keg emptying when I'd only poured one beer :)

So I'm not sure what's going on here tbh.

Cheers!
Thanks for the feedback. I’ve been using them for years as well on the original r-pints as well. I know my setup physically works and have had foam at times too and it has works. I recently decided to move to RandR+ version and haven’t been able to get it to work on beer. It does work on water so it’s got to be related to foam or the trigger points. With water I got it dialed in at around 23000 pulses per gallon. I’m wondering if I need to scale the count delay settings as maybe it’s kicking too soon before a pour is registered if any foam is causing the pulses to “skip”.
 
@esdill next place I would look is the file /var/www/html/includes/config.php

If you dump this, it should contain something like
PHP:
<?php
    function db() {
        return new mysqli('localhost', 'RaspberryPints', 'RaspberryPints', 'raspberrypints');
    }
    $rpintsversion="2.9.0.1";
?>
The four arguments of the mysqli() function are database hostname, username, password, and database. Check that these match what you think they should be. You can test the connection by doing the following (my database username and password are both RaspberryPints because my machine isn't accessible outside my private subnet):
Bash:
mysql -u RaspberryPints -p
Enter password: RaspberryPints
SQL:
use raspberrypints;
SELECT * FROM config;

See if that works of if it throws an error.
 
Thanks for the feedback. I’ve been using them for years as well on the original r-pints as well. I know my setup physically works and have had foam at times too and it has works. I recently decided to move to RandR+ version and haven’t been able to get it to work on beer. It does work on water so it’s got to be related to foam or the trigger points. With water I got it dialed in at around 23000 pulses per gallon. I’m wondering if I need to scale the count delay settings as maybe it’s kicking too soon before a pour is registered if any foam is causing the pulses to “skip”.

In the original program the Arduino decides whether a pour happened. And if the code was enabled it would also send a kick message if the rotor rpm exceeded a threshold. So the constant you're changing is well down stream from those decision points.

When you say you have it working using water, does that mean you can get a pour to register properly on a tap for a chosen "beer", but you can't get an actual beer to register? I think that's what you've been saying but just want to confirm - because that's weird...

Cheers!
 
In the original program the Arduino decides whether a pour happened. And if the code was enabled it would also send a kick message if the rotor rpm exceeded a threshold. So the constant you're changing is well down stream from those decision points.

When you say you have it working using water, does that mean you can get a pour to register properly on a tap for a chosen "beer", but you can't get an actual beer to register? I think that's what you've been saying but just want to confirm - because that's weird...

Cheers!
Exactly. I have a dummy test beer set up on the tap. If I take my beer line cleaner container full of water and run it through the line with flow meter, it registers the “pour” just fine. I then hook up a keg with beer to the same line/settings and do not change anything other than tapping a keg full of beer, it doesn’t register the pours. I have a dual tap system with two different flow meters and the same thing happens on both. Water fine, beer nothing. Maybe it’s trying to tell me something....
 
lol! The world is full of weirdness these days, who knows.
Anyway, so the water pours get registered properly. Are you using the same pressure?
And is the pour "velocity" as best you can discern it reasonably similar between water and beer?

If all that is true I may have to start drinking more...

Cheers!
 
Water fine, beer nothing.

That's very odd! I just hooked up 5 brand-new SF800s and they work just fine. So if water works, but beer doesn't... does StarSan?

With you keg pressure and line length, how long does it take for your tap to pour one liter of beer? How long for one liter of water?
 
lol! The world is full of weirdness these days, who knows.
Anyway, so the water pours get registered properly. Are you using the same pressure?
And is the pour "velocity" as best you can discern it reasonably similar between water and beer?

If all that is true I may have to start drinking more...

Cheers!
Hard to say for sure. The water is a hand pump pressurized container. I’ve got my keg of beer with about 10 psig counter pressure. West coast IPA. I’ll try to fill a keg with water with same physical configuration to rule out those setup differences.
 
@kcscholl one other thought: do you have a 2k2 ohm pull-up resistor between the +5V and signal line on your SF800s? When you check the voltage between signal and ground, is it transitioning between a good
+4 or more volts and close to 1 volt? If it's hovering around 2 or 3 volts as the pulses go through, you might not be getting a clean pulse that the Arduino can recognize. This can cause intermittent problems which could correlate to switching between water and beer (correlation not implying causation).
 
@kcscholl one other thought: do you have a 2k2 ohm pull-up resistor between the +5V and signal line on your SF800s? When you check the voltage between signal and ground, is it transitioning between a good
+4 or more volts and close to 1 volt? If it's hovering around 2 or 3 volts as the pulses go through, you might not be getting a clean pulse that the Arduino can recognize. This can cause intermittent problems which could correlate to switching between water and beer (correlation not implying causation).
Good thought. I’m not using a pull-up resistor. I do recall the voltage bouncing around 2-3 V. I’ll try that and report back. Thanks!
 
@esdill next place I would look is the file /var/www/html/includes/config.php

If you dump this, it should contain something like
PHP:
<?php
    function db() {
        return new mysqli('localhost', 'RaspberryPints', 'RaspberryPints', 'raspberrypints');
    }
    $rpintsversion="2.9.0.1";
?>
The four arguments of the mysqli() function are database hostname, username, password, and database. Check that these match what you think they should be. You can test the connection by doing the following (my database username and password are both RaspberryPints because my machine isn't accessible outside my private subnet):
Bash:
mysql -u RaspberryPints -p
Enter password: RaspberryPints
SQL:
use raspberrypints;
SELECT * FROM config;

See if that works of if it throws an error.
config.php shows the database is 'localhost' and the user name, password, and database name all match what I entered in the installation script. When I enter my user name and password I can access the database:

i@rpints:~ $ mysql -u Erik -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 10640
Server version: 10.3.22-MariaDB-0+deb10u1 Raspbian 10

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]>

And when I dump the contents of the database I get the 102 rows that I would expect.

One thing I have noticed is that anywhere between 3 and 4 hours after I reboot and try to open the Raspberry Pints webpage, it finally does open SOMETIMES ... but the temperature readings show the time when I attempted to open the page and do not refresh. I'm at a loss where to go next, it was working great for months until I added the second probe and ran the update to have both probe readings appear on the main screen. Prior to running the update the two temperature readings would randomly change from one to the other or to both each time the web page refreshed, I read earlier in the thread that the newest update allowed then both to appear, so that's why I ran the update.
 
Good thought. I’m not using a pull-up resistor. I do recall the voltage bouncing around 2-3 V. I’ll try that and report back. Thanks!

The pull-up is definitely required - the original Arduino sketch does not invoke internal pull-ups for the meter inputs - and even if it did, they'd be over an order of magnitude weaker than what Swissflow recommends anyway.

That said, the notion that it has a bearing on this is spooky ;)

Cheers!
 
The pull-up is definitely required - the original Arduino sketch does not invoke internal pull-ups for the meter inputs - and even if it did, they'd be over an order of magnitude weaker than what Swissflow recommends anyway.

That said, the notion that it has a bearing on this is spooky ;)

Cheers!
OK, I was hoping that was it but still not working. I put a meter on it during the pour. Before the pour I have 4.98V. Start the pour and it’s bouncing all over the place. Below 2, an occasional over 4, and everything in between. I’m guessing that’s the issue but what is causing it is the question. The pours start foamy for a few seconds, but settles down to normal.
 
You'll never keep up with the actual waveform with a meter. If you have the pull-up on the data line now, that's goodness, and I can't imagine there's a further electrical issue at this point. This is pretty simple connectivity stuff.

So, back to the pours: you say "start foamy for a few seconds". That would be hella unacceptable to me, but given I can see the meters respond to the foam of a kicked keg, I'm not sure it's relevant here. Which still leaves me wondering wth is going on ;)

Cheers!
 
config.php shows the database is 'localhost' and the user name, password, and database name all match what I entered in the installation script. When I enter my user name and password I can access the database:

i@rpints:~ $ mysql -u Erik -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 10640
Server version: 10.3.22-MariaDB-0+deb10u1 Raspbian 10

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]>

And when I dump the contents of the database I get the 102 rows that I would expect.

One thing I have noticed is that anywhere between 3 and 4 hours after I reboot and try to open the Raspberry Pints webpage, it finally does open SOMETIMES ... but the temperature readings show the time when I attempted to open the page and do not refresh. I'm at a loss where to go next, it was working great for months until I added the second probe and ran the update to have both probe readings appear on the main screen. Prior to running the update the two temperature readings would randomly change from one to the other or to both each time the web page refreshed, I read earlier in the thread that the newest update allowed then both to appear, so that's why I ran the update.
Have you tried using exactly what is in config.php to connect to the db from the command line? Copy and paste the user_name, password and database from the config file. You may have a typo in there that you are overlooking. Sometimes you see something because you expect to see it.
 
I read earlier in the thread that the newest update allowed then both to appear, so that's why I ran the update.
That was the last update, maybe I messed it up, its working locally for.
Is the apache log you posted right after a reboot or was the Pi running for awhile.

One thing I just thought of is that the configs are from the admin section which uses /admin/includes/conn.php to connect to the database, make sure that has the correct settings in it. (I know that 2 different places doesn't make sense, but its simplified from the original)
 

Latest posts

Back
Top