WeeWX data export utility ready for testing
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
WeeWX data export utility ready for testing
Hi all WeeWX users with Meteotemplate,
I have finished version 0.6 of my data export utility for Meteotemplate.
This utility exports weewx data to csv files to be imported in both MT's 'alldata' and 'alldataExtra' tables.
I plan to include this utility in Matthew Wall's meteotemplate uploader package, but first I want to test this utility via this user group.
When you like to receive the export utility for testing, send a mail to ljm.heijst@gmail.com and I'll send you the file together with instructions how to use.
Cheers, Luc
I have finished version 0.6 of my data export utility for Meteotemplate.
This utility exports weewx data to csv files to be imported in both MT's 'alldata' and 'alldataExtra' tables.
I plan to include this utility in Matthew Wall's meteotemplate uploader package, but first I want to test this utility via this user group.
When you like to receive the export utility for testing, send a mail to ljm.heijst@gmail.com and I'll send you the file together with instructions how to use.
Cheers, Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hello Luc
I tried it and got an issue:
Using username "root".
root@192.168.133.138's password:
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 29 10:13:20 2017 from jochen-medion8.fritz.box
root@rasp_OS_Test:~# python /home/weewx/util/export_mt.py --config=/home/weewx/weewx.conf
Traceback (most recent call last):
File "/home/weewx/util/export_mt.py", line 65, in <module>
import weecfg
ImportError: No module named weecfg
root@rasp_OS_Test:~#
root@rasp_OS_Test:~#
What to do?
Thank you for your help
Joachim
I tried it and got an issue:
Using username "root".
root@192.168.133.138's password:
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct 29 10:13:20 2017 from jochen-medion8.fritz.box
root@rasp_OS_Test:~# python /home/weewx/util/export_mt.py --config=/home/weewx/weewx.conf
Traceback (most recent call last):
File "/home/weewx/util/export_mt.py", line 65, in <module>
import weecfg
ImportError: No module named weecfg
root@rasp_OS_Test:~#
root@rasp_OS_Test:~#
What to do?
Thank you for your help
Joachim
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
Hello Joachim,
Did you run the following command?
PYTHONPATH=/home/weewx/bin python /home/weewx/util/export_mt.py --config=/home/weewx/weewx.conf
It seems you only runned the second part of the command:
python /home/weewx/util/export_mt.py --config=/home/weewx/weewx.conf
Cheers, Luc
Did you run the following command?
PYTHONPATH=/home/weewx/bin python /home/weewx/util/export_mt.py --config=/home/weewx/weewx.conf
It seems you only runned the second part of the command:
python /home/weewx/util/export_mt.py --config=/home/weewx/weewx.conf
Cheers, Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
You are right. (Of course). Csv produced perfect. Now I am working on the import. I try to solve the problems first myself.
Cheers
Joachim
You are right. (Of course). Csv produced perfect. Now I am working on the import. I try to solve the problems first myself.
Cheers
Joachim
Regards from Bavaria
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
Your program had to convert a database of 32 MB. It works fine and produces csv-fikes for 4 years. But the program stops in 2017 always at the same place:
The csv-file shows:
and so on, last row is
The database is too big for an upload. But for me there are no strange fugres in there at this place where the program stops. If you need something of the database let me know. The conversion of the units and so on works well. I'm using US-units anad they are displayed as European units (°C, mm, km/h)
Thank you fo your help
Cheers
Joachim
Your program had to convert a database of 32 MB. It works fine and produces csv-fikes for 4 years. But the program stops in 2017 always at the same place:
Code: Select all
exported 14000 records; timestamp last record: 2017-03-14 23:16:00 CET (1489529760)
Traceback (most recent call last):
File "/home/weewx/util/export_mt.py", line 288, in <module>
main()
File "/home/weewx/util/export_mt.py", line 171, in main
datadict = weewx.units.to_std_system(datadict, weewx.METRIC)
File "/home/weewx/bin/weewx/units.py", line 1224, in to_std_system
_datadict_target = StdUnitConverters[unit_system].convertDict(datadict)
File "/home/weewx/bin/weewx/units.py", line 795, in convertDict
target_dict[obs_type] = self.convert(as_value_tuple(obs_dict, obs_type))[0]
File "/home/weewx/bin/weewx/units.py", line 762, in convert
new_val_t = convert(val_t, new_unit_type)
File "/home/weewx/bin/weewx/units.py", line 1089, in convert
new_val = conversion_func(val_t[0]) if val_t[0] is not None else None
File "/home/weewx/bin/weewx/units.py", line 243, in <lambda>
'inch' : {'cm' : lambda x : x * CM_PER_INCH,
TypeError: can't multiply sequence by non-int of type 'float'
root@rasp_OS_Test:~#
Code: Select all
2017/03/14 23:06,3.70,79.0,1034.29,0.00,0.00,0.00,0.00,,,22.00,43.0,
2017/03/14 23:11,3.50,79.0,1034.45,0.00,0.00,0.00,0.00,,,22.00,42.0,
2017/03/14 23:16,3.50,79.0,1034.45,0.00,0.00,0.00,0.00,,,22.10,43.0,
2017/03/14 23:21,3.50,81.0,1034.34,0.00,1.08,0.00,0.00,,,22.10,43.0,
2017/03/14 23:26,3.40,80.0,1034.37,0.00,0.00,0.00,0.00,,,22.10,43.0,
2017/03/14 23:31,3.30,81.0,1034.40,0.00,0.00,0.00,0.00,,,22.10,43.0,
2017/03/14 23:36,3.30,80.0,1034.29,0.00,0.00,0.00,0.00,,,22.10,43.0,
2017/03/14 23:41,3.10,80.0,1034.56,0.00,0.00,0.00,0.00,,,22.10,43.0,
2017/03/14 23:45,3.10,82.0,1034.35,0.00,2.52,0.00,0.00,,,22.10,43.0,
2017/03/14 23:50,3.10,82.0,1034.45,0.00,1.08,0.00,0.00,,,22.10,43.0,
2017/03/14 23:56,3.10,82.0,1034.35,0.00,1.08,0.00,0.00,,,22.10,43.0,
2017/03/15 00:00,3.10,82.0,1034.45,0.00,1.08,0.00,0.00,,,22.10,43.0,
2017/03/15 00:06,3.10,82.0,1034.56,0.00,1.08,0.00,0.00,,,22.10,43.0,
2017/03/15 00:11,3.00,81.0,1034.48,0.00,0.00,0.00,0.00,,,22.10,43.0,
2017/03/15 00:16,2.90,82.0,1034.61,0.00,0.00,0.00,0.00,,,22.10,43.0,
Code: Select all
2017/03/15 08:21,7.60,61.0,1032.71,1.08,2.52,0.00,0.00,225,,21.50,45.0,
Thank you fo your help
Cheers
Joachim
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
Hi Joachim,
The export utility has a problem with your data at 2017/03/15 08:21 (or shortly after).
It is about inch, so probably the rain value or rain-rate value.
Can you have a look at your database at this date-time and look at the data if there is something unusual?
Thanks in advance.
Luc
The export utility has a problem with your data at 2017/03/15 08:21 (or shortly after).
It is about inch, so probably the rain value or rain-rate value.
Can you have a look at your database at this date-time and look at the data if there is something unusual?
Thanks in advance.
Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
I didn't find any difference in that time. When I started your program from 2017-03-16 same issue. When I started it from 2017-03-17 it worked fine. No issues
When I tried to import this, I got the follwoing protocol which says that only 11562 data sets of 52592 were imported.
In "your" csv file the last set is from 2017/11/01 18:05
No remarks in red.
By the way: do you know the path to the database ofe Meteotemplate? So I will check it there also?
I overwrite the data because MT runs with the simulator and not with the WH1080. So I copy real data to check the other functions of MT. No other differences in the weewx.config.
Thanks
Cheers
Joachim
I didn't find any difference in that time. When I started your program from 2017-03-16 same issue. When I started it from 2017-03-17 it worked fine. No issues


When I tried to import this, I got the follwoing protocol which says that only 11562 data sets of 52592 were imported.
This is data set 11562.loading CSV/text file from ../importWeewx/ExportMT_2017A.csv
File loaded successfully.
Header row in the file, skipping first line.
The imported file has 52592 data sets.
Import type: overwrite
Starting to parse data.
Last row of the protocol:
All ok, imported (overwritten if exists): 2017-04-26 08:00
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,P,W,G,R,RR,B,S,D,A) values ('2017-04-26 08:00',1.7,1.7,1.7,99.0,1010.09,1.1,3.6,1.89,0.00,315,null,1.6,-0.3)
In "your" csv file the last set is from 2017/11/01 18:05
No remarks in red.
By the way: do you know the path to the database ofe Meteotemplate? So I will check it there also?
I overwrite the data because MT runs with the simulator and not with the WH1080. So I copy real data to check the other functions of MT. No other differences in the weewx.config.
Thanks
Cheers
Joachim
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
Hi Joachim,
I will send you a new version of export_mt.py which will continue after a TypeError.
Then only the line(s) with 'bad' data will be skipped in the export.
Then you say in your last message that the last imported row is data set 11562.
I wonder: how do you know? To my knowledge there is no counter which says how many lines were imported.
BTW: You have to scroll the output window to the bottom to see which record (date) was imported last.
May be there is a maximum time for the execution of the import data (don't know for sure).
If so, this could be an explanation why not all data of the csv file is imported.
For your information: I plan to change the data import programs of MT (for the next release of MT) which will report some more details like the number of handled rows and in case of 'Skip existing' the number of inserted lines.
You don't need a 'path to the database of MT'. The database directory contains non-readable files. You need a program like PhpMyAdmin to show and manipulate the data of the MySQL (or MariaDB) database.
You could also use Meteotemplates program: 'Setup | Control Panel | Database | Edit Data' to look at your data of a certain date. As long as you don't use the buttons 'Edit' or 'Delete' no data won't be changed.
Cheers, Luc
I will send you a new version of export_mt.py which will continue after a TypeError.
Then only the line(s) with 'bad' data will be skipped in the export.
Then you say in your last message that the last imported row is data set 11562.
I wonder: how do you know? To my knowledge there is no counter which says how many lines were imported.
BTW: You have to scroll the output window to the bottom to see which record (date) was imported last.
May be there is a maximum time for the execution of the import data (don't know for sure).
If so, this could be an explanation why not all data of the csv file is imported.
For your information: I plan to change the data import programs of MT (for the next release of MT) which will report some more details like the number of handled rows and in case of 'Skip existing' the number of inserted lines.
You don't need a 'path to the database of MT'. The database directory contains non-readable files. You need a program like PhpMyAdmin to show and manipulate the data of the MySQL (or MariaDB) database.
You could also use Meteotemplates program: 'Setup | Control Panel | Database | Edit Data' to look at your data of a certain date. As long as you don't use the buttons 'Edit' or 'Delete' no data won't be changed.
Cheers, Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
it's no secret about the data sets. I opened the csv file with EdtPad Pro 7 and switched on line numbers.
Thank you again for your help. Then I will wait for your new version of the import program.
Cheers
Joachim
it's no secret about the data sets. I opened the csv file with EdtPad Pro 7 and switched on line numbers.

Thank you again for your help. Then I will wait for your new version of the import program.
Cheers
Joachim
Regards from Bavaria
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
I made a first run. Your part runs now witout errors. Here is a dump with the critical time from your CSV
As you see the import stopped again:
[/quoteLoading CSV/text file from ../importWeewx/ExportMT_2017.csv
File loaded successfully.
Header row in the file, skipping first line.
The imported file has 56773 data sets.
Import type: overwrite
Starting to parse data. [/quote]
and then
Cheers
Joachim
I made a first run. Your part runs now witout errors. Here is a dump with the critical time from your CSV
I must say that my old WH1080 became crazy. The firmware wasn' later able to send the data every 300 seconds. You couldn't change the interval at all. Later on it was completely damaged and I bought a new one.2017/03/15 08:11,6.80,63.0,1032.92,2.52,5.04,0.00,0.00,225,,21.40,45.0,
2017/03/15 08:16,6.80,63.0,1033.14,2.52,5.04,0.00,0.00,225,,21.50,45.0,
2017/03/15 08:21,7.60,61.0,1032.71,1.08,2.52,0.00,0.00,225,,21.50,45.0,
2017/03/15 08:26,37.58,57.0,30.53,0.67,1.57,0.00,0.00,180,,70.88,45.0,
2017/03/15 08:31,3.10,57.0,1034.24,1.08,2.52,0.00,0.00,180,,21.70,45.0,
2017/03/15 08:36,,,,,,0.00,0.00,,,21.80,45.0,
2017/03/15 08:41,10.90,50.0,1032.18,0.00,2.52,0.00,0.00,,,21.80,45.0,
As you see the import stopped again:
[/quoteLoading CSV/text file from ../importWeewx/ExportMT_2017.csv
File loaded successfully.
Header row in the file, skipping first line.
The imported file has 56773 data sets.
Import type: overwrite
Starting to parse data. [/quote]
and then
Here it stopped. "Your" last data set was:All ok, imported (overwritten if exists): 2017-04-06 08:38
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,P,W,G,R,RR,B,S,D,A) values ('2017-04-06 08:38',5.5,5.5,5.5,51.0,1025.21,2.5,5.0,0.00,0.00,0,null,-3.9,2.5)
All ok, imported (overwritten if exists): 2017-04-06 08:43
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,P,W,G,R,RR,B,S,D,A) values ('2017-04-06 08:43',5.6,5.6,5.6,51.0,1025.40,2.5,5.0,0.00,0.00,0,null,-3.8,2.6)
All ok, imported (overwritten if exists): 2017-04-06 08:48
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,P,W,G,R,RR,B,S,D,A) values ('2017-04-06 08:48',5.7,5.7,5.7,51.0,1025.37,1.1,3.6,0.00,0.00,0,null,-3.8,3)
I will test, if I start at this date or later what will happen. Before importing I stopped weewx.017/11/01 18:05,4.50,85.0,1026.84,0.00,0.00,0.00,0.00,,,23.15,54.0,
Cheers
Joachim
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
Hi Joachim,
The problem was with the data of 08:36 where a value of null inches rain was converted to cm.
If the import was stopped due to a time-out you can also try to do an import with a date just BEFORE the date it stopped last time (e.g. 2017-04-06 08:38).
When it stopped for another reason, it will stop at the very same timestamp.
Luc
The problem was with the data of 08:36 where a value of null inches rain was converted to cm.
If the import was stopped due to a time-out you can also try to do an import with a date just BEFORE the date it stopped last time (e.g. 2017-04-06 08:38).
When it stopped for another reason, it will stop at the very same timestamp.
Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
I did it in that way you described it. The result below:
It's always nearly the same. Round about data sets of one month were imported than import is stopped. So I deleted the data sets which were sent and start again.
Joachim
I did it in that way you described it. The result below:
The csv-file starts atImporting data from CSV/text file...
Errors will be highlighted in red...
Loading CSV/text file from ../importWeewx/ExportMT_2017.csv
File loaded successfully.
Header row in the file, skipping first line.
The imported file has 46849 data sets.
Import type: overwrite
Starting to parse data.
The import stops atDateTime,T,H,P,W,G,R,RR,B,S,TIN,HIN,UV
2017/04/06 00:08,9.00,75.0,1021.93,0.00,1.08,0.00,0.00,,,22.40,62.0,
It's this data set in the csv-fileAll ok, imported (overwritten if exists): 2017-05-07 04:20
INSERT INTO alldata (DateTime,T,Tmax,Tmin,H,P,W,G,R,RR,B,S,D,A) values ('2017-05-07 04:20',9.3,9.3,9.3,95.0,1013.80,2.5,6.1,0.71,0.00,225,null,8.5,8.5)
Next test beginning at 2017-05-062017/07/05 04:09,13.40,95.0,1020.49,1.08,2.52,0.00,0.00,180,,22.30,54.0,
2017/07/05 04:15,13.60,93.0,1020.23,1.08,2.52,0.00,0.00,180,,22.30,54.0,
2017/07/05 04:20,13.80,91.0,1020.18,1.08,2.52,0.00,0.00,180,,22.20,54.0,
2017/07/05 04:25,14.00,90.0,1020.02,2.52,3.60,0.00,0.00,180,,22.20,54.0,
It's always nearly the same. Round about data sets of one month were imported than import is stopped. So I deleted the data sets which were sent and start again.
Joachim
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
Hi Joachim,
Looks like a time-out to me.
Did you time how long an import takes?
Luc
Looks like a time-out to me.
Did you time how long an import takes?
Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
I will try it tomorrow. In the meantime I'm proud having installed phpMyadmin.
I didn't know which circumstances show me that the import is finished. The page of MT needs some time to be printed to the screen. Perhaps I will take the time from "pushing the button" till the complete report is printed on the screen.
Cheers
Joachim
I will try it tomorrow. In the meantime I'm proud having installed phpMyadmin.

Cheers
Joachim
Regards from Bavaria
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Sorry that you didn't hear anything from me for a long time. I had a lot of work with my house. I ran several tests. The import stops after roundabout 2 minutes. It doesn't matter if it is from a csv-finle or from Wunderground. The report on the new tab of the browser shows the data sets and that the import is ok. But you cannot show the data in the different programs of Meteotemplate. It seems that they don't exist in the database alldata.
Your program runs perfect.
Cheers
Joachim
Your program runs perfect.
Cheers
Joachim
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
We need more error checking in the import programs. When no data is found in your database the insert queries possibly failed because of (user) rights.
I will work on it the coming weeks.
Cheers, Luc
I will work on it the coming weeks.
Cheers, Luc
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Hi Luc,
it worked already with "your" csv-files (there no probs with the rights). Helpful would be, when the protocol of MT which is produced during import would show when the import is finished.
If it's possible or necessary to change some test conditions, let me know. I will try it.
Cheers
Joachim
(first snow in Bavaria)
it worked already with "your" csv-files (there no probs with the rights). Helpful would be, when the protocol of MT which is produced during import would show when the import is finished.
If it's possible or necessary to change some test conditions, let me know. I will try it.
Cheers
Joachim
(first snow in Bavaria)
Regards from Bavaria
- Luc
- Developer
- Posts: 168
- Joined: Mon Aug 21, 2017 6:40 am
- Location: Paramaribo, Suriname
- Station model: Davis Pro 2 (2x)
- Software: WeeWX
- Contact:
Re: WeeWX data export utility ready for testing
Hi Joachim and Jachym,
The data received by the api is stored with rounded 5-minute time stamps like 07:20:00, 07:25:00 etc.
I think the import program should have the same rounded time stamps.
Let me explain.
When a csv file has a record with time stamp 07:20:12, it should be better stored with a rounded time stamp like 07:20:00, otherwise we would end with two registrations in the database: 07:20:00 (api) and 07:20:12 (import).
In such a case the flag 'don't overwrite existing records' would have no meaning because the time stamps differ 12 seconds and both records would be present in the database. This is a situation which we don't want.
Also when the csv file has more than one record in 5 minutes, the import program should perform an aggregation like the api does. So average for most values, latest for rain and max for wind gust.
Another thing.
Someone wanted to import only one or two fields. I have to think about this if this is possible.
When a new import program is finished I like to test it by some users before it will be part of a new mt version.
Luc
The data received by the api is stored with rounded 5-minute time stamps like 07:20:00, 07:25:00 etc.
I think the import program should have the same rounded time stamps.
Let me explain.
When a csv file has a record with time stamp 07:20:12, it should be better stored with a rounded time stamp like 07:20:00, otherwise we would end with two registrations in the database: 07:20:00 (api) and 07:20:12 (import).
In such a case the flag 'don't overwrite existing records' would have no meaning because the time stamps differ 12 seconds and both records would be present in the database. This is a situation which we don't want.
Also when the csv file has more than one record in 5 minutes, the import program should perform an aggregation like the api does. So average for most values, latest for rain and max for wind gust.
Another thing.
Someone wanted to import only one or two fields. I have to think about this if this is possible.
When a new import program is finished I like to test it by some users before it will be part of a new mt version.
Luc
-
- Newbie
- Posts: 1
- Joined: Sun Oct 14, 2018 4:23 pm
- Station model: Davis Vantage pro 2
- Software: Weewx
Re: WeeWX data export utility ready for testing
Hello,
This is exactly what I need. How do I get a copy of this script?
Thanks,
CR
This is exactly what I need. How do I get a copy of this script?
Thanks,
CR
-
- Observer
- Posts: 18
- Joined: Sat Sep 09, 2017 6:20 pm
- Location: Bavaria
- Station model: FineOffset WH1080
- Software: WeeWX
Re: WeeWX data export utility ready for testing
Regards from Bavaria
-
- Forecaster
- Posts: 101
- Joined: Sun Aug 20, 2017 1:04 pm
- Location: Sanford, Manitoba, Canada
- Station model: Davis VP2
- Software: WeeWx
- Contact:
Re: WeeWX data export utility ready for testing
Excellent script,
My router has been acting up and disconnecting from the internet for 1-7 hours every day, I've used this just about daily to back fill the meteotemplate database from weewx.
Works flawlessly
Bill
My router has been acting up and disconnecting from the internet for 1-7 hours every day, I've used this just about daily to back fill the meteotemplate database from weewx.
Works flawlessly
Bill
-
- Observer
- Posts: 13
- Joined: Fri Apr 20, 2018 10:41 am
- Location: Koblenz / Germany
- Station model: Davis Pro 2 aktiv
- Software: weewx 4.1.1
- Contact:
Re: WeeWX data export utility ready for testing
Hi - i have a small not topic regarded question.
After a crash of the filesystem on our pi - we tried to setup a clean and fresh installation of weewx. We are still using the sync_lh9.py script till today to fill our archive server with data. But i am just to stupid to get it work again...
Maybe someone can help us to manage this problem.
After a crash of the filesystem on our pi - we tried to setup a clean and fresh installation of weewx. We are still using the sync_lh9.py script till today to fill our archive server with data. But i am just to stupid to get it work again...
Maybe someone can help us to manage this problem.
Code: Select all
Sep 21 23:42:58 PWS systemd[1]: Starting LSB: weewx weather system...
Sep 21 23:42:59 PWS weewx[2735] INFO __main__: Initializing weewx version 4.1.1
Sep 21 23:42:59 PWS weewx[2735] INFO __main__: Using Python 3.7.3 (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
Sep 21 23:42:59 PWS weewx[2735] INFO __main__: Platform Linux-5.4.51-v7+-armv7l-with-debian-10.4
Sep 21 23:42:59 PWS weewx[2735] INFO __main__: Locale is 'de_DE.UTF-8'
Sep 21 23:42:59 PWS weewx[2735] INFO __main__: PID file is /var/run/weewx.pid
Sep 21 23:42:59 PWS weewx[2739] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Sep 21 23:42:59 PWS weewx[2739] INFO __main__: Debug is 1
Sep 21 23:42:59 PWS weewx[2739] DEBUG __main__: Initializing engine
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
Sep 21 23:42:59 PWS weewx[2723]: Starting weewx weather system: weewx.
Sep 21 23:42:59 PWS systemd[1]: Started LSB: weewx weather system.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.drivers.vantage: Driver version is 3.2.1
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.drivers.vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.drivers.vantage: Gentle wake up of console successful
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.drivers.vantage: Hardware type is 16
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.drivers.vantage: ISS ID is 2
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.drivers.vantage: Hardware name: Vantage Pro2
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.engine.StdTimeSynch
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.engine.StdTimeSynch
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.engine.StdConvert
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.engine: StdConvert target unit is 0x10
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.engine.StdConvert
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.engine.StdCalibrate
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.engine.StdQC
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.engine.StdQC
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.wxservices.StdWXCalculate
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.manager: Daily summary version is 1.0
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.wxservices: The following values will be calculated: pressure=prefer_hardware, altimeter=prefer_hardware, appTemp=prefer_hardware, barometer=prefer_hardware, beaufort=prefer_hardware, cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, heatindex=prefer_hardware, humidex=prefer_hardware, inDewpoint=prefer_hardware$
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.wxservices: The following algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.wxservices.StdWXCalculate
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.engine.StdArchive
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.engine: Archive will use data binding wx_binding
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.engine: Record generation will be attempted in 'hardware'
Sep 21 23:42:59 PWS weewx[2739] ERROR weewx.engine: The archive interval in the configuration file (300) does not match the station hardware interval (60).
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.engine: Using archive interval of 60 seconds (specified by hardware)
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Use LOOP data in hi/low calculations: 1
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.engine.StdArchive
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.restx.StdStationRegistry
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.restx: StationRegistry: Station will be registered.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.restx.StdStationRegistry
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.restx.StdWunderground
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.restx: WU essentials: {}
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.restx: Wunderground-RF: Data for station IWINNING12 will be posted
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.restx.StdWunderground
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.restx.StdPWSweather
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.restx: PWSweather: Posting not enabled.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.restx.StdPWSweather
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.restx.StdCWOP
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.restx: CWOP: Posting not enabled.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.restx.StdCWOP
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.restx.StdWOW
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.restx: WOW: Posting not enabled.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.restx.StdWOW
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service weewx.restx.StdAWEKAS
Sep 21 23:42:59 PWS weewx[2739] INFO weewx.restx: AWEKAS: Data will be uploaded for user wsko001
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Finished loading service weewx.restx.StdAWEKAS
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.engine: Loading service user.sync_lh9.SyncService
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.manager: Daily summary version is 1.0
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.manager: Daily summary version is 1.0
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.restx: Shut down AWEKAS thread.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.restx: Shut down Wunderground-RF thread.
Sep 21 23:42:59 PWS weewx[2739] DEBUG weewx.restx: Shut down StationRegistry thread.
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: Caught unrecoverable exception:
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** invalid syntax (sync_lh9.py, line 109)
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** Traceback (most recent call last):
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** File "/usr/share/weewx/weewxd", line 148, in main
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** engine = weewx.engine.StdEngine(config_dict)
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** File "/usr/share/weewx/weewx/engine.py", line 75, in __init__
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** self.loadServices(config_dict)
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** File "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** obj = weeutil.weeutil.get_object(svc)(self,config_dict)
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** File "/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** mod = __import__(module)
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** File "/usr/share/weewx/user/sync_lh9.py", line 109
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** if self.entity_id <> "":
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** ^
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** SyntaxError: invalid syntax
Sep 21 23:42:59 PWS weewx[2739] CRITICAL __main__: **** Exiting.
Wetterservice Koblenz