date:20170721

[weewx-user] Re: Manual date entry

2017-07-21 Thread Charles Ross

Thanks Gary, I'll give it a go!

Much appreciated,

Chuck

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Manual date entry

2017-07-21 Thread gjr80

Hi,

Assuming you are using weeWX 3.6.0 or later the easiest approach will be to 
enter your misisng data in a file in CSV format and then import the data 
using the wee_import 
 utility. Have a 
good read through the wee_import documentation, in particular the section 
Importing 
from CSV files 
, you should 
find everything there you need to correctly format your data for import. Do 
make sure you make a backup of your database and do a dry run before doing 
any actual import in case things go awry.

Oh, if you are using an earlier version of weeWX, upgrade to 3.6.0 or later 
and then use wee_import :-)

Gary

On Saturday, 22 July 2017 09:22:03 UTC+10, Charles Ross wrote:
>
> Sorry, title should read manual data entry.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Manual date entry

2017-07-21 Thread Charles Ross

Sorry, title should read manual data entry.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Manual date entry

2017-07-21 Thread Charles Ross

Hello all,

I am missing 3 months of data on weewx, but I have the data on paper (daily 
data).  What's the easiest way to get this into weewx?  I'm hoping there may be 
some utility.

Big thanks for taking time to help.

Chuck

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator (No module named wdSearchX3)

2017-07-21 Thread gjr80

Hi,

Let's start with the obvious check first; is the file wdSearchX3.py in the 
directory /usr/share/weewx/user ? If it is not there then that is the cause 
of the problem, you will need to extract it from the weeWX-WD archive and 
copy it to /usr/share/weewx/user (though this begs the questions what else 
may have changed) so you might be best served by re-installing weeWX-WD. 

If wdSearchX3.py in the directory /usr/share/weewx/user then something else 
is amiss and we will require more info:

1. A log extract from weeWX startup including at least one full report 
generation cycle. To do this (1) ensure debug=1 in weewx.conf (you already 
have debug=1 in the above extract) (2) stop weeWX (3) start weeWX. You can 
monitor your log using tail -f /var/log/syslog (or whatever log file weeWX 
logs to). (4) Once a couple of report generation cycles are complete take a 
copy of the log from weeWX start up until the 2nd report generation cycle 
is complete and post the output here.

2. Knowing a bit more about your install and your weewx.conf may help. 
Easiest way to do this is with the weeWX utility wee_debug 
. Post a copy of the 
wee_debug output. Before you do post though check for any sensitive info in 
the output. The wee_debug output includes a copy of weewx.conf, wee_debug 
attempts to obfuscate any sensitive info but it's not perfect.

This leads to the graphics in my daily report not being updated (they are 
> all stuck to the 19th of July). All textual data and graphics in the 
> weekly, monthly and annual reports are still being updated.
>

It is interesting that you say your daily graphics (I presume you refer to 
the plots) are not updating but the plots and data on the weekly and longer 
are. The error you posted will only cause the weeWX-WD reports to be 
skipped and should have no effect on plots or weeWX generated html pages (I 
presume the reports and graphics you say are still being updated are the 
standard weeWX ones). Makes me wonder if there is more to this than meets 
the eye.

Gary

On Friday, 21 July 2017 23:58:28 UTC+10, cyrix2000 wrote:
>
> Hi,
>
> For two days weewx is throwing the exception: "unrecoverable exception in 
> generator weewx.cheetahgenerator.CheetahGenerator" and "no module named 
> wdSearchX3". This leads to the graphics in my daily report not being 
> updated (they are all stuck to the 19th of July). All textual data and 
> graphics in the weekly, monthly and annual reports are still being updated.
>
> The weird thing is that I didn't touch the server for at least a week, so 
> something must have changed by itself (updates?).
>
> Im running Ubuntu 16.04 on a RPi2 and weewx 3.7.1-1.
>
> Here the relevant bits from syslog:
>
> Jul 21 14:25:37 localhost weewx[20793]: reportengine: Running report 
> wdTesttags
> Jul 21 14:25:37 localhost weewx[20793]: reportengine: Found configuration 
> file /etc/weewx/skins/Testtags/skin.conf for report wdTesttags
> Jul 21 14:25:37 localhost weewx[20793]: cheetahgenerator: using search 
> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.wdSearchX3.wdMonthStats', 'user.wdSearchX3.wdTesttagsAgoRainTags', 
> 'user.wdSearchX3.wdLastRainTags', 'user.wdSearchX3.wdTimeSpanTags', 
> 'user.wdSearchX3.wdMaxAvgWindTags', 'user.wdSearchX3.wdMaxWindGustTags', 
> 'user.wdSearchX3.wdSundryTags', 'user.wdSearchX3.wdSkinDict', 
> 'user.wdSearchX3.wdMonthlyReportStats', 'user.wdSearchX3.wdWindroseTags', 
> 'user.wdSearchX3.wdWindRunTags', 'user.wdSearchX3.wdHourRainTags', 
> 'user.wdSearchX3.wdGdDays', 'user.wdSearchX3.wdForToday', 
> 'user.wdSearchX3.wdRainThisDay', 'user.wdSearchX3.wdRainDays', 
> 'user.wdAstroSearchX3.wdMoonApsis', 'user.wdAstroSearchX3.wdEclipse', 
> 'user.wdAstroSearchX3.wdEarthApsis', 
> 'user.wdAstroSearchX3.wdChineseNewYear', 'user.wdSearchX3.wdYestAlmanac', 
> 'user.wdSearchX3.wdTaggedStats', 'user.wdSearchX3.wdTaggedArchiveStats', 
> 'user.wdSearchX3.wdManualAverages']
> Jul 21 14:25:37 localhost weewx[20793]: manager: Daily summary version is 
> 1.0
> Jul 21 14:25:37 localhost weewx[20793]: reportengine: Caught unrecoverable 
> exception in generator weewx.cheetahgenerator.CheetahGenerator
> Jul 21 14:25:37 localhost weewx[20793]:   No module named 
> wdSearchX3
> Jul 21 14:25:37 localhost weewx[20793]:   Traceback (most 
> recent call last):
> Jul 21 14:25:37 localhost weewx[20793]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Jul 21 14:25:37 localhost weewx[20793]:   obj.start()
> Jul 21 14:25:37 localhost weewx[20793]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Jul 21 14:25:37 localhost weewx[20793]:   self.run()
> Jul 21 14:25:37 localhost weewx[20793]:

Re: [weewx-user] WMR 200 and weewx 3.1 missing values

2017-07-21 Thread Thomas Keffer

In weewx, if a driver detects a bad value, it should replace it with a
null. I'm not sure whether the existing driver does this (I did not write
it).

One of the reasons weewx is able to support so many different types of
hardware is that it has a very simple, and very consistent, data model
. One of the
guidelines of that model is, "The driver should emit only data it receives
from the hardware (no "filling in the gaps")." If you want to do that, that
would be the job of a weewx service.

However, we looked into caching values about a year ago and decided not to
do it for reasons given in the Issue thread
. What you're proposing is a
little simpler, but could run into some of the same problems.

-tk



On Fri, Jul 21, 2017 at 1:20 AM,  wrote:

> Hello,
>
> I have read this topic because i have the same trouble too. I used the
> latest version of weewx  (3.7.1)  and the latest driver version for wmr200
> (3.3.2).
>
> I have a WMR200 station since 2010.
> I wrote my own driver with c#. But I decided this year to plug my station
> to a Raspberrypi and my c# app not working. Then I decided to use Weewx.
>
> The WMR200 is well known to produce sometime bad values (NA ou null
> values) sometime the pressure, sometime temperature, ...
>
> In my c# driver, I used the following strategy, if i receive a null record
> for a field, i replace it with the previous recorded value (only the
> erreneous field, not the whole record)
>
> I think that could be done too in weewx. An other strategy could be done
> in StdQC an could allow us to reject a whole record if some values are
> errouneous eg NULL ou NA;
>
> Do you think that could be done in next version of the WMR200's driver. I
> don't know Python, I can't help to change the python WMR200 driver
>
> Congratulation for this very good job.
> Best regards
>
>
> Le samedi 28 mars 2015 02:21:26 UTC+1, Markus Roth a écrit :
>>
>> Works not i have the first N/A by the UV sensor.
>>
>> Other thinks to test ?
>>
>> Am Samstag, 28. März 2015 01:11:24 UTC+1 schrieb Thomas Keffer:
>>>
>>> My apologies. I am not very familiar with the WMR200 driver. It appears
>>> that it gets the archive interval from the [WMR200] section of weewx.conf.
>>> Try this:
>>>
>>> [WMR200]
>>> # This section is for the Oregon Scientific WMR200
>>>
>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>> model = WMR200
>>>
>>> archive_interval = 300
>>>
>>> # The driver to use:
>>> driver = weewx.drivers.wmr200
>>>
>>>
>>> -tk
>>>
>>> On Fri, Mar 27, 2015 at 4:44 PM, Markus Roth 
>>> wrote:
>>>
>>> i have set it to 300 but the webside update comes every 60 sec.
>>> Is that ok ?
>>>
>>> Am Freitag, 27. März 2015 22:17:53 UTC+1 schrieb Thomas Keffer:
>>>
>>> Try changing the record_generation option to 'software':
>>>
>>> [StdArchive]
>>> ...
>>> archive_interval = 300
>>> ...
>>> record_generation = software
>>>
>>> -tk
>>>
>>>
>>> On Fri, Mar 27, 2015 at 2:03 PM, Markus Roth 
>>> wrote:
>>>
>>> interesting at the confic stand :
>>>
>>> [StdArchive]
>>> # This section is for configuring the archive service.
>>>
>>> # If your station hardware supports data logging then the archive
>>> interval
>>> # will be downloaded from the station.
>>> # Otherwise, you must specify it below (in seconds):
>>> archive_interval = 300
>>>
>>> but i have not cange anything on it.
>>> Or you mean any other ?
>>>
>>>
>>> Am Freitag, 27. März 2015 21:27:39 UTC+1 schrieb Thomas Keffer:
>>>
>>> Thank you, Markus
>>>
>>> The problem is that you have a one minute archive interval. This is very
>>> short. There will be occasions where you temperature sensor will not emit a
>>> value within such a short time, and so you will get a null value for
>>> outTemp.
>>>
>>> Either live with the problem, or increase your archive interval to 5
>>> minutes.
>>>
>>> -tk
>>>
>>> On Fri, Mar 27, 2015 at 1:20 PM, Markus Roth 
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>> 484540.0, 'windDir': 283.5281664924813, 'outTemp': 42.8, 'windSpeed':
>>> 4.25017895328, 'inHumidity': 45.0, 'outTempFault': 0.0, 'windGust':
>>> 4.25017895328, 'uvBatteryStatus': 1.0, 'windFault': 0.0}
>>> LOOP:   2015-03-27 20:29:19 CET (1427484559) {'windchill': 39.0,
>>> 'dateTime': 1427484559, 'windDir': 315.0, 'windSpeed': 4.25017895328,
>>> 'windGust': 5.816034357120001, 'rainRate': 0, 'usUnits': 1, 'windGustDir':
>>> 315.0}
>>> LOOP:   2015-03-27 20:29:29 CET (1427484569) {'dateTime': 1427484569,
>>> 'inHumidity': 45, 'inDewpoint': 51.567189501858394, 'rainRate': 0,
>>> 'usUnits': 1, 'inTemp': 74.31}
>>> LOOP:   2015-03-27 20:29:32 CET (1427484572) {'windchill': 39.0,
>>> 'dateTime': 1427484572, 'windDir': 315.0, 'windSpeed': 4.25017895328,
>>> 'windGust': 5.816034357120001, 'rainRate': 0, 'usUnits': 1, 'windGustDir':
>>> 315.0}
>>> LOOP:   2015-03-27 20:29:32 CET (1427484572) {'dewpoint':
>>> 34.0588

[weewx-user] unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator (No module named wdSearchX3)

2017-07-21 Thread cyrix2000

Hi,

For two days weewx is throwing the exception: "unrecoverable exception in 
generator weewx.cheetahgenerator.CheetahGenerator" and "no module named 
wdSearchX3". This leads to the graphics in my daily report not being 
updated (they are all stuck to the 19th of July). All textual data and 
graphics in the weekly, monthly and annual reports are still being updated.

The weird thing is that I didn't touch the server for at least a week, so 
something must have changed by itself (updates?).

Im running Ubuntu 16.04 on a RPi2 and weewx 3.7.1-1.

Here the relevant bits from syslog:

Jul 21 14:25:37 localhost weewx[20793]: reportengine: Running report 
wdTesttags
Jul 21 14:25:37 localhost weewx[20793]: reportengine: Found configuration 
file /etc/weewx/skins/Testtags/skin.conf for report wdTesttags
Jul 21 14:25:37 localhost weewx[20793]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.wdSearchX3.wdMonthStats', 'user.wdSearchX3.wdTesttagsAgoRainTags', 
'user.wdSearchX3.wdLastRainTags', 'user.wdSearchX3.wdTimeSpanTags', 
'user.wdSearchX3.wdMaxAvgWindTags', 'user.wdSearchX3.wdMaxWindGustTags', 
'user.wdSearchX3.wdSundryTags', 'user.wdSearchX3.wdSkinDict', 
'user.wdSearchX3.wdMonthlyReportStats', 'user.wdSearchX3.wdWindroseTags', 
'user.wdSearchX3.wdWindRunTags', 'user.wdSearchX3.wdHourRainTags', 
'user.wdSearchX3.wdGdDays', 'user.wdSearchX3.wdForToday', 
'user.wdSearchX3.wdRainThisDay', 'user.wdSearchX3.wdRainDays', 
'user.wdAstroSearchX3.wdMoonApsis', 'user.wdAstroSearchX3.wdEclipse', 
'user.wdAstroSearchX3.wdEarthApsis', 
'user.wdAstroSearchX3.wdChineseNewYear', 'user.wdSearchX3.wdYestAlmanac', 
'user.wdSearchX3.wdTaggedStats', 'user.wdSearchX3.wdTaggedArchiveStats', 
'user.wdSearchX3.wdManualAverages']
Jul 21 14:25:37 localhost weewx[20793]: manager: Daily summary version is 
1.0
Jul 21 14:25:37 localhost weewx[20793]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Jul 21 14:25:37 localhost weewx[20793]:   No module named 
wdSearchX3
Jul 21 14:25:37 localhost weewx[20793]:   Traceback (most 
recent call last):
Jul 21 14:25:37 localhost weewx[20793]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Jul 21 14:25:37 localhost weewx[20793]:   obj.start()
Jul 21 14:25:37 localhost weewx[20793]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Jul 21 14:25:37 localhost weewx[20793]:   self.run()
Jul 21 14:25:37 localhost weewx[20793]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
Jul 21 14:25:37 localhost weewx[20793]:  
 self.initExtensions(gen_dict[section_name])
Jul 21 14:25:37 localhost weewx[20793]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
Jul 21 14:25:37 localhost weewx[20793]:   class_ = 
weeutil.weeutil._get_object(x)
Jul 21 14:25:37 localhost weewx[20793]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
Jul 21 14:25:37 localhost weewx[20793]:   mod = 
__import__(module)
Jul 21 14:25:37 localhost weewx[20793]:   ImportError: No 
module named wdSearchX3
Jul 21 14:25:37 localhost weewx[20793]:   Generator terminated
Jul 21 14:25:38 localhost weewx[20793]: reportengine: Running report 
wdClientraw
Jul 21 14:25:38 localhost weewx[20793]: reportengine: Found configuration 
file /etc/weewx/skins/Clientraw/skin.conf for report wdClientraw
Jul 21 14:25:38 localhost weewx[20793]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.wdSearchX3.wdMonthStats', 'user.wdSearchX3.wdLastRainTags', 
'user.wdSearchX3.wdTimeSpanTags', 'user.wdSearchX3.wdSundryTags', 
'user.wdSearchX3.wdSkinDict', 'user.wdSearchX3.wdWindRunTags', 
'user.wdSearchX3.wdYestAlmanac', 'user.wdSearchX3.wdTaggedStats', 
'user.wdSearchX3.wdTaggedArchiveStats', 'user.wdSearchX3.wdRainDays', 
'user.wdSearchX3.wdManualAverages']
Jul 21 14:25:38 localhost weewx[20793]: manager: Daily summary version is 
1.0
Jul 21 14:25:38 localhost weewx[20793]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Jul 21 14:25:38 localhost weewx[20793]:   No module named 
wdSearchX3
Jul 21 14:25:38 localhost weewx[20793]:   Traceback (most 
recent call last):
Jul 21 14:25:38 localhost weewx[20793]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Jul 21 14:25:38 localhost weewx[20793]:   obj.s

Re: [weewx-user] WMR 200 and weewx 3.1 missing values

2017-07-21 Thread jtomeh

Hello, 

I have read this topic because i have the same trouble too. I used the 
latest version of weewx  (3.7.1)  and the latest driver version for wmr200 
(3.3.2).

I have a WMR200 station since 2010. 
I wrote my own driver with c#. But I decided this year to plug my station 
to a Raspberrypi and my c# app not working. Then I decided to use Weewx.

The WMR200 is well known to produce sometime bad values (NA ou null values) 
sometime the pressure, sometime temperature, ... 

In my c# driver, I used the following strategy, if i receive a null record 
for a field, i replace it with the previous recorded value (only the 
erreneous field, not the whole record)

I think that could be done too in weewx. An other strategy could be done in 
StdQC an could allow us to reject a whole record if some values are 
errouneous eg NULL ou NA;

Do you think that could be done in next version of the WMR200's driver. I 
don't know Python, I can't help to change the python WMR200 driver 

Congratulation for this very good job.
Best regards


Le samedi 28 mars 2015 02:21:26 UTC+1, Markus Roth a écrit :
>
> Works not i have the first N/A by the UV sensor.
>
> Other thinks to test ?
>
> Am Samstag, 28. März 2015 01:11:24 UTC+1 schrieb Thomas Keffer:
>>
>> My apologies. I am not very familiar with the WMR200 driver. It appears 
>> that it gets the archive interval from the [WMR200] section of weewx.conf. 
>> Try this:
>>
>> [WMR200]
>> # This section is for the Oregon Scientific WMR200
>> 
>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>> model = WMR200
>>
>> archive_interval = 300
>> 
>> # The driver to use:
>> driver = weewx.drivers.wmr200
>>
>>
>> -tk
>>
>> On Fri, Mar 27, 2015 at 4:44 PM, Markus Roth  wrote:
>>
>> i have set it to 300 but the webside update comes every 60 sec.
>> Is that ok ?
>>
>> Am Freitag, 27. März 2015 22:17:53 UTC+1 schrieb Thomas Keffer:
>>
>> Try changing the record_generation option to 'software':
>>
>> [StdArchive]
>> ...
>> archive_interval = 300
>> ...
>> record_generation = software
>>
>> -tk
>>
>>
>> On Fri, Mar 27, 2015 at 2:03 PM, Markus Roth  wrote:
>>
>> interesting at the confic stand :
>>
>> [StdArchive]
>> # This section is for configuring the archive service.
>> 
>> # If your station hardware supports data logging then the archive 
>> interval
>> # will be downloaded from the station.
>> # Otherwise, you must specify it below (in seconds):
>> archive_interval = 300
>>
>> but i have not cange anything on it.
>> Or you mean any other ?
>>
>>
>> Am Freitag, 27. März 2015 21:27:39 UTC+1 schrieb Thomas Keffer:
>>
>> Thank you, Markus
>>
>> The problem is that you have a one minute archive interval. This is very 
>> short. There will be occasions where you temperature sensor will not emit a 
>> value within such a short time, and so you will get a null value for 
>> outTemp.
>>
>> Either live with the problem, or increase your archive interval to 5 
>> minutes.
>>
>> -tk
>>
>> On Fri, Mar 27, 2015 at 1:20 PM, Markus Roth  wrote:
>>
>>
>>
>>
>>
>> 484540.0, 'windDir': 283.5281664924813, 'outTemp': 42.8, 'windSpeed': 
>> 4.25017895328, 'inHumidity': 45.0, 'outTempFault': 0.0, 'windGust': 
>> 4.25017895328, 'uvBatteryStatus': 1.0, 'windFault': 0.0}
>> LOOP:   2015-03-27 20:29:19 CET (1427484559) {'windchill': 39.0, 
>> 'dateTime': 1427484559, 'windDir': 315.0, 'windSpeed': 4.25017895328, 
>> 'windGust': 5.816034357120001, 'rainRate': 0, 'usUnits': 1, 'windGustDir': 
>> 315.0}
>> LOOP:   2015-03-27 20:29:29 CET (1427484569) {'dateTime': 1427484569, 
>> 'inHumidity': 45, 'inDewpoint': 51.567189501858394, 'rainRate': 0, 
>> 'usUnits': 1, 'inTemp': 74.31}
>> LOOP:   2015-03-27 20:29:32 CET (1427484572) {'windchill': 39.0, 
>> 'dateTime': 1427484572, 'windDir': 315.0, 'windSpeed': 4.25017895328, 
>> 'windGust': 5.816034357120001, 'rainRate': 0, 'usUnits': 1, 'windGustDir': 
>> 315.0}
>> LOOP:   2015-03-27 20:29:32 CET (1427484572) {'dewpoint': 
>> 34.058845824728756, 'outHumidity': 71, 'heatindex': 42.8, 'dateTime': 
>> 1427484572, 'outTemp': 42.8, 'rainRate': 0, 'usUnits': 1}
>> LOOP:   2015-03-27 20:29:34 CET (1427484574) {'windchill': 41.0, 
>> 'dateTime': 1427484574, 'windDir': 270.0, 'windSpeed': 4.25017895328, 
>> 'windGust': None, 'rainRate': 0, 'usUnits': 1, 'windGustDir': None}
>> LOOP:   2015-03-27 20:29:38 CET (1427484578) {'UV': 0, 'rainRate': 0, 
>> 'usUnits': 1, 'dateTime': 1427484578}
>> LOOP:   2015-03-27 20:29:39 CET (1427484579) {'dateTime': 1427484579, 
>> 'inHumidity': 45, 'inDewpoint': 51.567189501858394, 'rainRate': 0, 
>> 'usUnits': 1, 'inTemp': 74.31}
>> LOOP:   2015-03-27 20:29:40 CET (1427484580) {'altimeter': 
>> 29.88777318369758, 'rainRate': 0, 'dateTime': 1427484580, 'barometer': 
>> 30.124040165386887, 'forecastIcon': 4, 'usUnits': 1}
>> LOOP:   2015-03-27 20:29:48 CET (1427484588) {'windchill': None, 
>> 'dateTime': 1427484588, 'windDir': 315.0, 'windSpee

[weewx-user] Davis soil moisture and temperature station and SDR receiver

2017-07-21 Thread Andrew Milner

Hi folks - slightly off topic but I know there are SDR users in this forum 


Does anyone know if it is possible to read the soil moisture readings 
directly from the soil and moisture stations using an SDR - or does the 
station have to transmit to a davis console.  If it is possible, can the 
ISS SDR interceptor driver be used to take the readings into a weewx 
database (having suitably extended the schema).  Can one use the SDR to 
obtain data from say 8 soil stations and an ISS.

Thanks in advance for any information.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Manual date entry

[weewx-user] Re: Manual date entry

[weewx-user] Manual date entry

[weewx-user] Manual date entry

[weewx-user] Re: unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator (No module named wdSearchX3)

Re: [weewx-user] WMR 200 and weewx 3.1 missing values

[weewx-user] unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator (No module named wdSearchX3)

Re: [weewx-user] WMR 200 and weewx 3.1 missing values

[weewx-user] Davis soil moisture and temperature station and SDR receiver

9 matches

Site Navigation

Mail list logo

Footer information