meteohub.de

Hi,

I've experienced an issue lately with the data in Meteobridge Pro2, when one of the transmitters in my set-up began to show some faulty behaviour.

I have a moderately complex set-up; an ISS labelled Transmitter 1 which provides temperature and humidity data, a solar transmitter (Transmitter 2 ...

Can confirm that this issue is now resolved, cheers. Do I mark this as solved or...?

Thanks very much for investigating and fixing the issue, it was perhaps quite a niche problem, but happy to have been able to contribute! I shall upload the latest build and watch for the next rains.

Dan

Could you try the SQL export, that is the exact service I am experiencing the issue with. Also, I use the period "every started minute", rather than "every minute", if that makes any difference.

Screenshot 2024-07-16 194907.png

I'm running a Meteobridge PRO2 black, with Jul 10 2024 build ...

Now that it has rained a bit more, you can better see the pattern. I only show here the readings every 10 minutes, so I could fit it all int he one screenshot. I am though exporting the values from Meteobridge into this table every minute still, as I said before.

The test is the direct export from Meteobridge to an SQL table, using the Meteobridge tags. The SQL I am using is the very same SQL which I pasted in my first message.

The result, in my SQL table, looks like this:
Screenshot 2024-07-15 090711.png

In the above case, I format the time stamps so ...

Meteobridge does allow you to set a timezone, agreed, although it doesn't let you set your timezone to UTC (another bug/problem) perhaps,

The tags '[UYYYY]-[UMM]-[UDD] [Uhh]:[Umm]:00' do allow you to convert the meteobridge timestamp into a UTC timestamp for downstream use, and I am happy that ...

Hi admin,

No problem, I included the entire SQL in-case you could see an issue with something.

So first, please note that I export to a database every minute and I want the timestamp to be in UTC - '[UYYYY]-[UMM]-[UDD] [Uhh]:[Umm]:00'

The problem expression is, as you correctly said - [rain0total ...

Here is another example of the phenomenon, (with displaced rainrates also fixed...) But the lower value for accumulated rainfall since 2300Z (as meteobridge resets at 0000 local time) on the hour, every hour is clear to see.

Thanks all for comments on this - and apologies for only replying now!

Appreciate it's quite a niche request, thanks for considering anyway. I did use the suggestion of interrogating the .dat files and writing my own script to export these values into a separate database for further processing ...

Hi all,

I think I may have discovered a bug when exporting observations at 1 minute resolution using SQL.

Here is my SQL - insert Meteobridge (Timestamp, Temperature_C, TemperatureDelta60_C, TemperatureDelta1440_C, TemperatureMax1_C, TemperatureMin1_C, WetBulb_C, DewPoint_C, DewPointMax1_C ...

[th0temp-delta1h:NULL], [th0temp-delta24h:NULL]

Those are the expressions I am using. Unfortunately, it's not a consistently repeatable bug, so I think it will be hard to trace. I now circumvent it by recalculating the deltas from the temperatures, so it is not a problem for me anymore. However, I ...

The admin of this site was - viewtopic.php?p=12627#p12627 - or at least it was mentioned.

Yes, it is marginal, but it is important to me to get it exactly right, and moreover, it may expose a bug within meteobridge to be examined. Over the past few weeks I have found this to be persistent, the data exported to a log is always 1-minute out from the data inserted via SQL.

Anyone? Thanks.