meteohub.de

Hello,

We are logging all "act" data into a database table once per minute. In addition to that, we also have a query that runs at 1a local time, which puts in the "ydmin", "ydmax" and "avg@D1" values for the previous day.

When looking at this data, it almost seems that the "yd" values - specifically for the minimum, are not accurate. Our table that records current weather has a minimum value for yesterday's temperature at -1.4ºC -- which happened between 6.45a and 6.50a local time. Now, when looking at [th0temp-ydmin], the value is 4.8ºC, and [th0temp-ydmintime] shows 2016-12-18 at 21:49:46 ...

At the time 21:49:46 (local time), we *did* in fact have a temperature of 4.8ºC. But, as previously stated, the actual low for the day was -1.4ºC at 06:45:00.

Is there something I am doing wrong here, or by chance are the "yd" variables not recognizing the proper time zone?

Anyone seen anything like this before?

Something is wrong with the time zones. I do not know how to fix.

Not sure where you live (or what time zone) but have you checked the UTC v Local time comparison relative to the TimeZone setting? This is on the "System" tab in the Localization section.

Yes, the time there is accurate, both for UTC and local.

The issue (it seems) is that when we are getting values from yesterday, for example, they are not the values from our time zone. I'm 100% convinced that the "yd" values are from a 24-hour period of time that does not relate to our local time zone's midnight-to-midnight period. I just can't figure out the specific time offset ... It almost doesn't seem like it is using UTC's midnight-to-midnight 24-hour period either. It is very confusing.

This problem seems very similar to the issue we are also having (which is not important) where files uploaded via FTP have a date/time in the future.

There's something wonky about the time zone interpretations.

Nobody has any information about this?

Administrator?

We are using the Meteobridge as our primary source of weather data. If we can't have an accurate "yd" value, what good are those macros? We are trying to rely on this data to be accurate.

Our "yd" data is taken right after the new day begins (Pacific Standard Time). This data is bad. This is probably also true for any other time zone that uses Meteobridge. It seems that when calculating these template macros, the time zones are not accurate when referencing the beginning of a new day.

What can I do to fix my settings so this value is proper? Please, this is very important. Our data is not accurate.

Thank you.

Can you please give me remote access to your MB PRO in order to check this?
As I have just 1 hour offset between local time and UTC this is hard to find.
Please send URL and password to "info(at)meteobridge.com".

Email sent. Thanks!

Having read this discussion, I note there is a difference of 2 hours in the history data and the graphical data.

My timezone is set to Europe/Athens (UTC+2)

For yesterday the MBPro shows 7mm precipitation at 15:00 (UTC+2) in the history, which was the time of the actual event.

The 24 hour graph shows 7mm precipitation at 13:00 (UTC).

Furthermore, I noted recently that the history hourly rain amounts did not equal the day total.

There was a discrepancy of 2mm between the day total and the hourly totals. The history showed 0.2mm at 22:00 and 1.8mm at 23:00. The daily total was 2mm less than the sum of the hourly totals.

Does local time and UTC as displayed on "system" tab show the expected 2 hour difference?