I think there is an issue with the "Outdoor temp" "Year" and "All" min-record. I think "Year" and "All" by a mistake are the same as "Month". Min temp in database is 5.4 (uploaded by MeteoBridge) and min "Year" and "All" shows 9.2 (min temp for "Month" really is 9.2):
Regards
Last edited by droiddk on Mon Oct 03, 2016 10:13 pm, edited 2 times in total.
May be this is a misconception what meteobridge does. All data for day, month, year, all is recorded from live data meteobridge is receiving. When you start connecting your meteobridge to your station in August, then it will not know what has happened before. If you have yearly data to be added, you have to do that manually. After that meteobridge will continue to sum up correctly, but it needs you to manually set the data that meteobridge has not seen by itself so far.
But I connected my station to the Meteobridge in May and lowest (temp) in datebase (MySql receiving from Meteobridge) is from June so that value should have been "through" Meteobridge?
Other records are from May, June and July.
I have changed to a directly usb-connection to the Vantage Pro2 console, I was using the MeteoStick before, maybe that has something to do with it? But some of the existing records are from when the MetroStick was connected..,
Because the weather station is not sending this data. I explained how it works.
The Meteobridge got the data (that happens to be a record) from the weather station (as "normal" "live" data) and sent it to the sql-database. This data (that happens to be a record) is not listed on the live-page (records).
If the Meteobridge is able to put the data (that happens to be a record) into a database using SQL then it should also be possible to show it on live-tab as a record. Correct?
I totally understand this:
When you start connecting your meteobridge to your station in August, then it will not know what has happened before. If you have yearly data to be added, you have to do that manually. After that meteobridge will continue to sum up correctly, but it needs you to manually set the data that meteobridge has not seen by itself so far.
But this is not the case in this situation, station was connected in May (early) and live data with record went through the Meteobridge in May (late).
Last edited by droiddk on Wed Sep 07, 2016 1:22 pm, edited 2 times in total.
So you say in May you had a yearly maximum in outdoor temp that got overwritten by lower monthly outdoor temps in the following months?
If so that is something I did not detected in observing my rig.
admin wrote:So you say in May you had a yearly maximum in outdoor temp that got overwritten by lower monthly outdoor temps in the following months?
If so that is something I did not detected in observing my rig.
Anybody else out there having this problem?
I'm not sure if I get you right, but in May I had my lowest outdoor reading if I search for lowest in my MySQL. My MySQL only gets its data from the Meteobridge. But, on the live page, the lowest outdoor reading is from August and if I get it right then the reading from May should be there and not the one from August.
I only did change from the MeteoStick to a usb-connection to my Davis Vantage Pro2 console. That was in August (but "wrong" record is not from the day I did the change), but some of my other records on the live tab is when the Meteostick was connected so it is only related to "Outdoor Temp Year Min" and "Outdoor Temp All Min"
This picture shows the issue, table show lowest temperature in database, all data in database inserted by Meteobridge,:
Regards
Last edited by droiddk on Mon Oct 03, 2016 10:13 pm, edited 1 time in total.
