I'm considering to sell my Davis station and use my Ecowitt station as my weather station
The Ecowitt runs smoothly and is cheaper in parts/sensors
I have the WS90 with the GW2000 and 2551 console with additional lightning and temp/sensors and a extra rainfall sensor
I already read data from the gateway into my nano SD
Since the nano is housed in my console I will have to go with a different meteobridge, pro black or Pi
I want the same features as my nano SD like graphs etc.
Question: how to export/migrate my min/max data together with my historical data to a new meteobridge?
Is this possible?
Any tips/hints are appreciated
From nano SD to meteobridge pro black...
Moderator: Mattk
- wsnoordbergum
- Expert Boarder
- Posts: 156
- Joined: Wed Jan 14, 2015 12:33 pm
- Location: Friesland/Netherlands
- Contact:
Re: From nano SD to meteobridge pro black...
#1: I would go for a RPi - not for a MB Pro - and best a RPi4B (the 2 GB RAM version is enough). You will also need a SLC microSD card, but you will then have a very performant system with pages very fast displayed - even a 7 day custom graphic report with many sensors is displayed in a few seconds.
I can tell because I have both: MB on RPi4B and 2 MB Pro (1 red, 1 black).
#2: you can connect your GW2000 via the GW1000 API interface to your MB and (if you want) also the HP2551 console via the custom server to MB.
Also both in parallel if you want to have different sensor combinations per console.
MB Pro/NANO and RPi allow up to 5 stations in parallel (but only the RPi4 can handle more than one station with proper performance, escpecially when you have extra sensors beyond the classical wind, T/H/P, rain, solar senosrs or even archive minute based).
#3: you can export your NANO data and (re-)import them into the new MB solution (e.g. RPi).
if your data is minute based, MB will calculate the hourly min/max values during import.
if it's only hour based, one should be able to export the min/max data separately and re-import them e.g. with different time stamps inside the hour.
I'm sure that there are quite a few possibilities including in the extreme case updating the hourly min/max table entries with a MySQL script
Maybe @Boris (=@admin) knows a smart(er) approach ...
I can tell because I have both: MB on RPi4B and 2 MB Pro (1 red, 1 black).
#2: you can connect your GW2000 via the GW1000 API interface to your MB and (if you want) also the HP2551 console via the custom server to MB.
Also both in parallel if you want to have different sensor combinations per console.
MB Pro/NANO and RPi allow up to 5 stations in parallel (but only the RPi4 can handle more than one station with proper performance, escpecially when you have extra sensors beyond the classical wind, T/H/P, rain, solar senosrs or even archive minute based).
#3: you can export your NANO data and (re-)import them into the new MB solution (e.g. RPi).
if your data is minute based, MB will calculate the hourly min/max values during import.
if it's only hour based, one should be able to export the min/max data separately and re-import them e.g. with different time stamps inside the hour.
I'm sure that there are quite a few possibilities including in the extreme case updating the hourly min/max table entries with a MySQL script
Maybe @Boris (=@admin) knows a smart(er) approach ...
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
- wsnoordbergum
- Expert Boarder
- Posts: 156
- Joined: Wed Jan 14, 2015 12:33 pm
- Location: Friesland/Netherlands
- Contact:
Re: From nano SD to meteobridge pro black...
Thanks for the reply
Guess a RPI will be the way to go
I already have a slc class SD card in use
Also additional sensors
I will do some research on the RPI and meteobridge to get familiar with this setup
Thanks again
Guess a RPI will be the way to go
I already have a slc class SD card in use
Also additional sensors
I will do some research on the RPI and meteobridge to get familiar with this setup
Thanks again
Re: From nano SD to meteobridge pro black...
it's a bit unstructured in the WiKi
read
https://meteobridge.com/wiki/index.php/ ... croSD_card
https://meteobridge.com/wiki/index.php/ ... d_inserted
read
https://meteobridge.com/wiki/index.php/ ... croSD_card
https://meteobridge.com/wiki/index.php/ ... d_inserted
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
- wsnoordbergum
- Expert Boarder
- Posts: 156
- Joined: Wed Jan 14, 2015 12:33 pm
- Location: Friesland/Netherlands
- Contact:
Re: From nano SD to meteobridge pro black...
Still a few questions,
Is it possible to make use of my stored configuration settings and use the backup file of my settings on the Rpi platform?
That way my meteobridge is way easier to configure, I do not have to configure all my settings and services manually.
And what about my historical and high/low data?
Do I have to do the export/import manually or can I just click restore database (provided my database backup is on the SD card)
I have read the instructions for installing meteobridge on a Rpi, we'll see how that goes.
Is it possible to make use of my stored configuration settings and use the backup file of my settings on the Rpi platform?
That way my meteobridge is way easier to configure, I do not have to configure all my settings and services manually.
And what about my historical and high/low data?
Do I have to do the export/import manually or can I just click restore database (provided my database backup is on the SD card)
I have read the instructions for installing meteobridge on a Rpi, we'll see how that goes.
Re: From nano SD to meteobridge pro black...
I have never tried, but I think that the config-file is platform independent.
You should be able to load it into MB on RPi too.
Even if the RPi doesn't take it, the config-file is easy to read and you can copy your settings - especially the event settings - easily into new events.
I once migrated a MB Pro database to the RPi and it worked - should be the same with a NANO SD MB database.
You will have to put the DB backup on a FAT32 formatted USB device (stick, thumb drive, disk, ...) and connect it to the RPi.
MB should find it and the database file to restore.
If not, you can still do it manually. Connect to the RPi with e.g. puTTY via SSH. You will have to create a mount point for the USB device (mkdir /tmp/mnt/data/USB), mount the USB stick into the file system; (e.g. mount /dev/sda1 /tmp/mnt/data/USB), delete whatever is as dbase* in the /tmp/mnt directory (rm /tmp/mnt/dbase*) and then copy the backup database file (e.g. cp /tmp/mnt/data/USB/dbase-202209191900 /tmp/mnt) and rename it to "dbase" ( mv /tmp/mnt/dbase-202209191900 /tmp/mnt/dbase) and reboot. (database name = example name).
You should be able to load it into MB on RPi too.
Even if the RPi doesn't take it, the config-file is easy to read and you can copy your settings - especially the event settings - easily into new events.
I once migrated a MB Pro database to the RPi and it worked - should be the same with a NANO SD MB database.
You will have to put the DB backup on a FAT32 formatted USB device (stick, thumb drive, disk, ...) and connect it to the RPi.
MB should find it and the database file to restore.
If not, you can still do it manually. Connect to the RPi with e.g. puTTY via SSH. You will have to create a mount point for the USB device (mkdir /tmp/mnt/data/USB), mount the USB stick into the file system; (e.g. mount /dev/sda1 /tmp/mnt/data/USB), delete whatever is as dbase* in the /tmp/mnt directory (rm /tmp/mnt/dbase*) and then copy the backup database file (e.g. cp /tmp/mnt/data/USB/dbase-202209191900 /tmp/mnt) and rename it to "dbase" ( mv /tmp/mnt/dbase-202209191900 /tmp/mnt/dbase) and reboot. (database name = example name).
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
- wsnoordbergum
- Expert Boarder
- Posts: 156
- Joined: Wed Jan 14, 2015 12:33 pm
- Location: Friesland/Netherlands
- Contact:
Re: From nano SD to meteobridge pro black...
Well today I got two RPi which I bought secondhand, and with some problems got it finally working on my wifi.
Next is to get the database into the Rpi
See if I can get it to work.
One question though, in my RPi station setup I have the GW2000 as the primary station, and the luftdaten as station nr.1
On my Nano SD I have the Davis VP2 as primary station, luftdaten as station 1 and the GW2000 as station 2
I guess this can give problems with mapping, and sensor history data?
Is it better to start with new database?
I will give it a try, see how it goes, since I'm still in the trial and error period with the RPi
My data from the Rpi is not being uploaded so no worries
Next is to get the database into the Rpi
See if I can get it to work.
One question though, in my RPi station setup I have the GW2000 as the primary station, and the luftdaten as station nr.1
On my Nano SD I have the Davis VP2 as primary station, luftdaten as station 1 and the GW2000 as station 2
I guess this can give problems with mapping, and sensor history data?
Is it better to start with new database?
I will give it a try, see how it goes, since I'm still in the trial and error period with the RPi
My data from the Rpi is not being uploaded so no worries
Re: From nano SD to meteobridge pro black...
sorry for the long reply but it's difficult to tell in less words along with good examples
in principle it doesn't matter which station number you assign to which station - however, when you have history data, the new station #0 will continue to write its data to the old station #0, whatever station that was, etc. if you continue using your old database files
So if you want to migrate your station data from your NANO by just copying the database, you'll have a "disrupted" history.
There are two ways out of this situation I can think of:
1. you use the same station # assignment on the RPi as you had on the NANO
2. you start with a new database - and you export all the data you need from each station (NANO) and import them into the new MB on RPi station by changing the station qualifier of the sensor names.
e.g. you export station#2 th2!0hum from your NANO and import it as th0!0hum into the Rpi etc.
That means you have to do a mass rename in your export files before you re-import them.
The way I do such things is:
a) do the export and make sure your export script uses the full sensor names: e.g. th0!0temp and not th0temp for station #0 (primary), and 1! for #1 and 2! for number #2
b) load the export file into Excel (or Notepad) and make a find/replace over the whole file: e.g. find 2! and replace with e.g. 0! - this will be easy as the character sequence 0! or 1! or 2! is unique in the file
b) best is to do an export for direct import => one line per exported interval with EPOCH date, sensor name and value
e.g. 1665516600 th0!0temp 15.3 (see also example below)
as the export will not give this directly but will produce each sensor of a subsequent time stamp (but for the direct import you'll need all same time stamps of different sensors one after the other, you have again to load the file into e.g. EXCEL (Notepad won't work here) and mark the first column and then sort it from A-Z and save it as the import file.
Example:
your export will look like
1665516600 th0!0temp 15.6
1665516900 th0!0temp 15.7
1665517200 th0!0temp 15.6
1665517500 th0!0temp 15.8
etc.
but what you need is
1665516600 th0!0temp 13.5
1665516600 th0!0hum 68
1665516600 th0!0seapress 1025.6
etc. (assuming you have 5-minute data - the export interval you define in your export event)
find below an example for the export definition - to be saved under a speaking file name like e.g. NANO_St0.exp into the ..\data\templates directory (you'll need a similar one for station #1 and station #2 - just replace 0! by 1! or 2!) - you'll have to add sensors which are not in the example and remove those you don't have - MB will create the export then as ..\data\export\NANO_St0-2022100219-min5.txt
(if the export interval was 5 minutes and the export was for the 02-Oct-2022 from 19:00 through 19:59 - the file name will contain the time span and the interval in the file name: e.g. for 2022 until start of the export, the file name would be NANO_St0-2022-min.txt, one minute interval)
#--------------- start Meteobridge export for direct import into Meteobridge ----
# modified Standard CSV template with data in metric units
#
$# date,time,temperature[C],humidity[%],intemp[C],inhum[%],dew point[C],sealevel pressure[hPa],abspress,avg wind speed[m/s],gust speed[m/s],winddir,rainfall[mm],Solar [W/m2],UVI,PM25(1),PM25(2),extra-temp1 [C],extra-hum1 [%],extra-temp2 [C],extra-hum2 [%],extra-temp3 [C],extra-hum3 [%],extra-temp4 [C],extra-hum4 [%],extra-temp5 [C],extra-hum5 [%],extra-temp6 [C],extra-hum6 [%],extra-temp7 [C],extra-hum7 [%],extra-temp8 [C], extra-hum8 [%],soil moisture (1) [%],soil moisture (2) [%],soil moisture (3) [%],soil moisture (4) [%],soil moisture (5) [%],lightning last occurrance,lightning distance,lightning total,WH45-temp-in,WH45-hum-in,WH45-CO2,WH45-PM25,WH45-PM10
[epoch] th0!0temp [th0!0temp-max:]
[epoch] th0!0hum [th0!0hum-max.0:]
[epoch] thb0!0temp [thb0!0temp-max:]
[epoch] thb0!0hum [thb0!0hum-avg.0:]
[epoch] th0!0dew [th0!0dew-avg.1:]
[epoch] thb0!0seapress [thb0!0seapress-avg.1:]
[epoch] thb0!0press [thb0!0press-avg.1:]
[epoch] wind0!0avgwind [wind0!0avgwind-max.1:]
[epoch] wind0!0wind [wind0!0wind-max.1:]
[epoch] wind0!0dir [wind0!0dir-avg.0:]
[epoch] rain0!0total [rain0!0total-sum.1:]
[epoch] rain0!1total [rain0!1total-sum.1:]
[epoch] sol0!0rad [sol0!0rad-max.2:]
[epoch] uv0!0index [uv0!0index-avg.1:]
[epoch] air0!0pm [air0!0pm-max.2:]
[epoch] air0!1pm [air0!1pm-max.2:]
[epoch] th0!1temp [th0!1temp-avg.1:]
[epoch] th0!1hum [th0!1hum-avg.1:]
[epoch] th0!2temp [th0!2temp-avg.1:]
[epoch] th0!2hum [th0!2hum-avg.1:]
[epoch] th0!3temp [th0!3temp-avg.1:]
[epoch] th0!3hum [th0!3hum-avg.1:]
[epoch] th0!4temp [th0!4temp-avg.1:]
[epoch] th0!4hum [th0!4hum-avg.1:]
[epoch] th0!5temp [th0!5temp-avg.1:]
[epoch] th0!5hum [th0!5hum-avg.1:]
[epoch] th0!6temp [th0!6temp-avg.1:]
[epoch] th0!6hum [th0!6hum-avg.1:]
[epoch] th0!7temp [th0!7temp-avg.1:]
[epoch] th0!7hum [th0!7hum-avg.1:]
[epoch] th0!8temp [th0!8temp-avg.1:]
[epoch] th0!8hum [th0!8hum-avg.1:]
[epoch] th0!20hum [th0!20hum-avg.0:]
[epoch] th0!21hum [th0!21hum-avg.0:]
[epoch] th0!22hum [th0!22hum-avg.0:]
[epoch] th0!23hum [th0!23hum-avg.0:]
[epoch] th0!24hum [th0!24hum-avg.0:]
[epoch] lgt0!0energy [lgt0!0total-nonzerotime=epoch:]
[epoch] lgt0!0dist [lgt0!0dist-lastval.0:0]
[epoch] lgt0!0total [lgt0!0total-dmax.0:0]
[epoch] th0!9temp [th0!9temp-avg.1:]
[epoch] th0!9hum [th0!9hum-avg.1:]
[epoch] data0!4num [data0!4num-avg.0:]
[epoch] air0!4pm [air0!4pm-avg.1:]
[epoch] air0!5pm [air0!5pm-avg.1:]
#--------------- end Meteobridge export for direct import into Meteobridge ----

in principle it doesn't matter which station number you assign to which station - however, when you have history data, the new station #0 will continue to write its data to the old station #0, whatever station that was, etc. if you continue using your old database files
So if you want to migrate your station data from your NANO by just copying the database, you'll have a "disrupted" history.
There are two ways out of this situation I can think of:
1. you use the same station # assignment on the RPi as you had on the NANO
2. you start with a new database - and you export all the data you need from each station (NANO) and import them into the new MB on RPi station by changing the station qualifier of the sensor names.
e.g. you export station#2 th2!0hum from your NANO and import it as th0!0hum into the Rpi etc.
That means you have to do a mass rename in your export files before you re-import them.
The way I do such things is:
a) do the export and make sure your export script uses the full sensor names: e.g. th0!0temp and not th0temp for station #0 (primary), and 1! for #1 and 2! for number #2
b) load the export file into Excel (or Notepad) and make a find/replace over the whole file: e.g. find 2! and replace with e.g. 0! - this will be easy as the character sequence 0! or 1! or 2! is unique in the file
b) best is to do an export for direct import => one line per exported interval with EPOCH date, sensor name and value
e.g. 1665516600 th0!0temp 15.3 (see also example below)
as the export will not give this directly but will produce each sensor of a subsequent time stamp (but for the direct import you'll need all same time stamps of different sensors one after the other, you have again to load the file into e.g. EXCEL (Notepad won't work here) and mark the first column and then sort it from A-Z and save it as the import file.
Example:
your export will look like
1665516600 th0!0temp 15.6
1665516900 th0!0temp 15.7
1665517200 th0!0temp 15.6
1665517500 th0!0temp 15.8
etc.
but what you need is
1665516600 th0!0temp 13.5
1665516600 th0!0hum 68
1665516600 th0!0seapress 1025.6
etc. (assuming you have 5-minute data - the export interval you define in your export event)
find below an example for the export definition - to be saved under a speaking file name like e.g. NANO_St0.exp into the ..\data\templates directory (you'll need a similar one for station #1 and station #2 - just replace 0! by 1! or 2!) - you'll have to add sensors which are not in the example and remove those you don't have - MB will create the export then as ..\data\export\NANO_St0-2022100219-min5.txt
(if the export interval was 5 minutes and the export was for the 02-Oct-2022 from 19:00 through 19:59 - the file name will contain the time span and the interval in the file name: e.g. for 2022 until start of the export, the file name would be NANO_St0-2022-min.txt, one minute interval)
#--------------- start Meteobridge export for direct import into Meteobridge ----
# modified Standard CSV template with data in metric units
#
$# date,time,temperature[C],humidity[%],intemp[C],inhum[%],dew point[C],sealevel pressure[hPa],abspress,avg wind speed[m/s],gust speed[m/s],winddir,rainfall[mm],Solar [W/m2],UVI,PM25(1),PM25(2),extra-temp1 [C],extra-hum1 [%],extra-temp2 [C],extra-hum2 [%],extra-temp3 [C],extra-hum3 [%],extra-temp4 [C],extra-hum4 [%],extra-temp5 [C],extra-hum5 [%],extra-temp6 [C],extra-hum6 [%],extra-temp7 [C],extra-hum7 [%],extra-temp8 [C], extra-hum8 [%],soil moisture (1) [%],soil moisture (2) [%],soil moisture (3) [%],soil moisture (4) [%],soil moisture (5) [%],lightning last occurrance,lightning distance,lightning total,WH45-temp-in,WH45-hum-in,WH45-CO2,WH45-PM25,WH45-PM10
[epoch] th0!0temp [th0!0temp-max:]
[epoch] th0!0hum [th0!0hum-max.0:]
[epoch] thb0!0temp [thb0!0temp-max:]
[epoch] thb0!0hum [thb0!0hum-avg.0:]
[epoch] th0!0dew [th0!0dew-avg.1:]
[epoch] thb0!0seapress [thb0!0seapress-avg.1:]
[epoch] thb0!0press [thb0!0press-avg.1:]
[epoch] wind0!0avgwind [wind0!0avgwind-max.1:]
[epoch] wind0!0wind [wind0!0wind-max.1:]
[epoch] wind0!0dir [wind0!0dir-avg.0:]
[epoch] rain0!0total [rain0!0total-sum.1:]
[epoch] rain0!1total [rain0!1total-sum.1:]
[epoch] sol0!0rad [sol0!0rad-max.2:]
[epoch] uv0!0index [uv0!0index-avg.1:]
[epoch] air0!0pm [air0!0pm-max.2:]
[epoch] air0!1pm [air0!1pm-max.2:]
[epoch] th0!1temp [th0!1temp-avg.1:]
[epoch] th0!1hum [th0!1hum-avg.1:]
[epoch] th0!2temp [th0!2temp-avg.1:]
[epoch] th0!2hum [th0!2hum-avg.1:]
[epoch] th0!3temp [th0!3temp-avg.1:]
[epoch] th0!3hum [th0!3hum-avg.1:]
[epoch] th0!4temp [th0!4temp-avg.1:]
[epoch] th0!4hum [th0!4hum-avg.1:]
[epoch] th0!5temp [th0!5temp-avg.1:]
[epoch] th0!5hum [th0!5hum-avg.1:]
[epoch] th0!6temp [th0!6temp-avg.1:]
[epoch] th0!6hum [th0!6hum-avg.1:]
[epoch] th0!7temp [th0!7temp-avg.1:]
[epoch] th0!7hum [th0!7hum-avg.1:]
[epoch] th0!8temp [th0!8temp-avg.1:]
[epoch] th0!8hum [th0!8hum-avg.1:]
[epoch] th0!20hum [th0!20hum-avg.0:]
[epoch] th0!21hum [th0!21hum-avg.0:]
[epoch] th0!22hum [th0!22hum-avg.0:]
[epoch] th0!23hum [th0!23hum-avg.0:]
[epoch] th0!24hum [th0!24hum-avg.0:]
[epoch] lgt0!0energy [lgt0!0total-nonzerotime=epoch:]
[epoch] lgt0!0dist [lgt0!0dist-lastval.0:0]
[epoch] lgt0!0total [lgt0!0total-dmax.0:0]
[epoch] th0!9temp [th0!9temp-avg.1:]
[epoch] th0!9hum [th0!9hum-avg.1:]
[epoch] data0!4num [data0!4num-avg.0:]
[epoch] air0!4pm [air0!4pm-avg.1:]
[epoch] air0!5pm [air0!5pm-avg.1:]
#--------------- end Meteobridge export for direct import into Meteobridge ----
WH4000SE 1.6.6/1 x DP1500/4 x GW1000 1.7.7/GW1100 2.3.0/HP1000SE Pro 1.9.3//2 x WH2650 1.7.7/GW2000 3.1.0
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
2xMeteobridge Pro [B+R] 15161, 2xRPi4B-2GB/16/32 3139,VM128 1704
Weather Landing page: https://meshka.eu
Ecowitt WiKi: https://meshka.eu/Ecowitt/dokuwiki
- wsnoordbergum
- Expert Boarder
- Posts: 156
- Joined: Wed Jan 14, 2015 12:33 pm
- Location: Friesland/Netherlands
- Contact:
Re: From nano SD to meteobridge pro black...
Thanks for the reply
Got some work to do it seems
Have a nice day
Got some work to do it seems

Have a nice day