MB Pro - Soil moisture sensor data not stored for about one month **solved**

[Gyvate]

Since 05-December-2020 my MB Pro doesn't store any soil moisture data anymore nor can the soilmoisture data in general be accessed.
Details see
https://www.wxforum.net/index.php?topic=41130.0

[Gyvate]

solved with release 5.1 build 14233 for MB Pro

The sensors are back again in the database - leaving behind a one month gap to be filled.

[galfert]

If you figure out a way to backfill the missing data from Ecowitt.net data I would be interested in seeing how you did it. I probably could figure it out but while you are at it if you do it first just let us know. Seems to me like it would just be a matter of data manipulation of the csv file download in regards to the headers. I would probably do a small export from the Meteobridge to learn its import/export data structure and then just copy suit for the headers of he Ecowitt.net data to then do an import. Seems simple enough. I'm probably talking Greek to a lot of people right now.

I've been meaning on getting more into data export and import now that I have a Meteobridge RPI but I just haven't gotten to it yet. My new Meteobridge PRI would be much nicer if I'd at some point backfill with all my history. I have my history in a number of places....I just don't know yet where I would rather import from yet. I have data on WU and on a mySQL database that my old Meteobridge was sending data to for years. When I get around to it I'll probably write some documentation up on the experience.

[Gyvate]

I will - I will start with my meteotemplate sql database - because there I have an easy-to-use import interface - see below:
I wish Meteobridge offered such a nice and comfortable option/interface !! Here I can use the 5-minute values as that's my storing/archiving interval there.
Jachym (the developer of Meteotemplate) did really a nice job !!

Meteotemplate_Data_Import_01.PNG (161.72 KiB) Viewed 1307 times

Meteotemplate_Data_Import_02.PNG (107.29 KiB) Viewed 1307 times

Regarding MB:
My source will be the Ecowitt.net 5 minute csv files which for Meteobridge I will have to condense to one-hour entries, as the smallest values for the Soil Moisture tables th2xhum (x=1-8) is th2xhum_hour - no minute data here.

Doing it manually in Meteobridge would be too much: 24 entries/day * 30 days = 720 entries (if you enter only the hourly average value). * 5 sensors =3,600 entries.
If you want to take high/low/average it's 3 times as many: 10,800 entries ...


It will be easier to add full, new records (table entries) than update existing ones. For this update (which is needed here for the missing SM entires) probably a SQL script will be needed. For full records MB has a procedure for CSV files. Will have to study the wiki.

It might be easier to export the data of the whole month where the SM values are missing, delete the records from the database, enrich the export with the missing SM sensor values and then import them again.

[galfert]

Oh I hadn't considered that the MB records are hourly and my archive mySQL is 5 minute data. Yeah that needs to be condensed in some smart way. I wonder thought now that the Meteobridge does 1 minute data if you could simply import to the 1 minute database and then the Meteobridge could create its own hourly data from that 1 minute database? That would save some work.