I am running weewx 3.5.0 and everything was working properly while running
the simulator. weewx,weewxDB, and meteotemplate were populating the db's.
Today I installed an Acurite 5-in-1 and enabled the driver. weewx and
weexDB are updating properly, and the live values in meteotemplate are
updating, but the barometer is reporting ~27 which is configured to be out
of bounds so the clientraw.txt is setting -- for the barometer.
When running http://<hostname
deleted>/meteotemplate/update/wd.php?pass=<password deleted> the scripts
shows:
Latest DB record timestamp detected: 1969-12-31 18:00:00
Latest cached timestamp detected: 2016-10-24 21:30:00
Smallest interval between uploads to database set to: 300 seconds.
Difference between latest db timestamp and cached timestamp: 1477362600
seconds.
The difference is more than or equal to the desired interval, therefore
database should now be updated.
The database will now be updated with the following query:
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,W,G,R,RR,B,S,D,A) values
('2016-10-24
21:30:00',70.34,70.34,70.34,63,0.8,2.1864801,0.20078751,0,150,--,57,72.1)
The meteotemplate db is not updated, but if I se phpmyadmin and run:
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,W,G,R,RR,B,S,D,A) values
('2016-10-24
21:30:00',70.34,70.34,70.34,63,0.8,2.1864801,0.20078751,0,150,--,57,72.1)
phpmyadmin returns:
#1064 - You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near
'57,72.1)' at line 1
If I put any data into the barometer field and run it again the
meteotemplate db is populated with a valid entry, or Null if I use a value
outside of 28-32.
Is there a way to have meteotemplate update the db even if the value is --
in clientraw.txt?
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
