VP2 solar radiation and wview data import

[tolien]

I have a Davis Vantage Pro 2 Plus (i.e. with the solar radiation and UV sensors). Currently it's connected to wview with data exported into a Postgres database but I'm looking to switch wview for weewx, not least because with Debian Buster releasing in the next few weeks I expect I'll have problems upgrading the VM that wview runs on and would rather not be stuck with Stretch forever.

I've tested that if the wview archive DB is copied into place and weewx restarted, it'll import the data and go from there and (based on this old post) the daily summary tables are populated using the archive table. The Postgres export part (at least for the archive table) looks like it can be done with https://github.com/jorabra/weewx-postgres-exporter. For the fun of it, I've already forked the exporter and made it work with Python 3 — I'll probably add support for exporting the daily summaries too.

However, I've noticed that the maximum solar radiation is lower than what's shown in wview and it looks like that's because the daily archive table is populated with archive rather than hilow data.

I guess my two questions are:

- I gather that the daily summary tables are updated using LOOP data, i.e. once weewx is connected to the console itself will this all just work for future data, and the max value in there will be the max value the console saw?

- would there be any interest in a patch/util that takes the wview hilow tables and updates the daily archive with min/max and minTime/maxTime? I've got most of the work done on some Python that'll take the wview radiation table and use it to populate the weewx archive_day_radiation, if that's even a sane approach to take.

Cheers.

[Thomas Keffer]

Welcome to weewx!

I guess my two questions are:

- I gather that the daily summary tables are updated using LOOP data, i.e. once weewx is connected to the console itself will this all just work for future data, and the max value in there will be the max value the console saw?

That's correct. By default, the daily mins and maxes updated with LOOP data, if they are available.

- would there be any interest in a patch/util that takes the wview hilow tables and updates the daily archive with min/max and minTime/maxTime? I've got most of the work done on some Python that'll take the wview radiation table and use it to populate the weewx archive_day_radiation, if that's even a sane approach to take.

Five years ago, that would have been extremely useful, but, these days, I don't think there are many wview installations still out there, so I don't know that your utility would find much use.

Cheers,

-tk