Re: [weewx-user] Re: Acurite not so accurate on sunny days

[Craig Thom]

Software Defined Radio.  The way I am using with weewx is with a USB tuner 
built for DVB-T TV broadcasts in other countries (but not the U.S.) that 
use the RTL2832U chipset.  People discovered that these tuners could cover 
a much larger range than DVB-T and have been using them for receiving all 
kinds of stuff, including the 433 MHz signals used by wireless weather 
sensors (and a lot of other stuff in the home).

rtl_sdr handles controlling the radio, and rtl_433 decodes packets from 
known devices.  The weewx sdr driver uses rtl_433 to get the packets of 
information directly from the weather sensor.

The radio receivers are available for $10-$20 all over the place online. 
 Since they were intended for TV in other countries the antenna connection 
is often unusual, but that doesn't matter if you are using the antenna that 
comes with it.

My antenna is a monopole, so it needs to be sitting on a piece of metal to 
work best.  It's magnetic, so I've just got it stuck to the side panel of 
an old computer.

On Friday, April 14, 2017 at 12:31:23 PM UTC-4, Tony Turner wrote:
>
>
>
> On Thursday, April 13, 2017 at 6:32:27 PM UTC-5, Andy wrote:
>>
>> (snip) I am also using the SDR and a Honeywell sensor from Craigslist 
>> free section.
>
>
> Maybe I'm just dumb but what is and SDR?? 
>

-- 
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.

Re: [weewx-user] Re: Acurite not so accurate on sunny days

[Tony Turner]

On Thursday, April 13, 2017 at 6:32:27 PM UTC-5, Andy wrote:
>
> (snip) I am also using the SDR and a Honeywell sensor from Craigslist free 
> section.


Maybe I'm just dumb but what is and SDR?? 

-- 
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.

Re: [weewx-user] Re: Amending spurious readings in the database

[Andrew Milner]

>From the noaa reports it is impossible to know if your issues are related
to a single comms issue corrupting many values in one loop record for
example, or if it is different issues with different sensors at different
times and on different occasions.

Not knowing your station type does not help much either!!

Not knowing if the log says anything to match the 'corrupted' data does not
help to identify the problems and causes.

Taking your example of a wind at 128.9 knots - it would be helpful to see
the log and database records for the period of spike - 15 minutes to spike
+ 15 minutes for example.

Supplying us with NOAA data is not a substitute for the actual database
data captured by weewx - the noaa report is, after all, derived from the
database and not the other way around!!

It may also be relevant to know if your station is supplying partial data
from different sensors in different loopr ecords or true complete loop data
and archive records.



On 14 April 2017 at 15:26, Auchtermuchty Weather 
wrote:

> The colour coding makes it easier (for me) to spot the days with rogue
> data although sorting the data by (say) windspeed is another say to find it
> and yes, I realise what I need to do to find the values.  I put the
> spreadsheet up to show people what I was seeing.
>
> My question was if this is a sign of sensors reaching the end of their
> life, given most of the rogue values have occurred since the start of March
> this year.
>
>
>
> On Friday, 14 April 2017 10:02:52 UTC+1, Andrew Milner wrote:
>
>> What you need to do is to use the NOAA data to possibly pinpoint a rogue
>> day, and then check the archive table to see if there is a single rogue
>> record.
>>
>> If there is then you can just correct the rogue record or delete it even,
>> and rebuild the stats tables and noaa files if required.
>>
>> You should check the log at around the time the rogue record or recoprds
>> were inserted into the database and see if there were issues recorded in
>> the log.  Maybe you have a comms problem.
>>
>> I could not tell what we were supposed to deduce from the colour coded
>> noaa data - since there were so many colours in use!!
>>
>>
>>
>> On Friday, 14 April 2017 11:19:15 UTC+3, Auchtermuchty Weather wrote:
>>
>>> Have picked up my NOAA data into excel, and find that nearly all my
>>> 'bad' values are since 1st March this year.  It was December 2016 when I
>>> replaced the Pi with a better one with the then up-to-date version of Weewx.
>>>
>>> XLXS file attached - I have colour coded the values in each appropriate
>>> column.
>>>
>>> Makes me think I do have a sensor problem or problems.  :(
>>>
>>>
>>> On Wednesday, 12 April 2017 09:20:06 UTC+1, Auchtermuchty Weather wrote:
>>>
 I am getting the odd spike in my readings, for example:


TEMPERATURE (C), RAIN (mm), WIND SPEED (knots)

  HEAT   COOL AVG
   MEAN   DEGDEG
 WIND   DOM
 DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
 HIGH   TIMEDIR
 
 ---
 013.5   13.1  11:12   -1.1  04:31   14.80.00.00.4
 6.0  07:19 22
 024.3   13.4  05:56   -0.7  00:02   14.00.0  148.81.8
 44.9  05:56 25
 034.3   11.9  11:31   -2.3  07:56   14.00.05.10.7
 8.6  22:43191
 045.26.7  15:304.0  08:30   13.20.09.90.7
 12.6  09:50207
 055.6   10.3  15:25   -0.2  23:51   12.70.03.60.0
 3.3  07:37108
 065.2   16.7  14:55   -0.3  01:18   13.10.01.20.1
 43.5  15:34130
 075.1   12.4  11:19  -15.1  08:56   13.20.0  807.90.4
 8.0  16:15 77
 087.3   13.3  11:314.8  07:30   11.00.02.41.7
 19.2  11:44360
 098.0   14.3  14:262.7  23:51   10.30.0  271.81.2
 11.9  08:48345
 106.0   10.2  16:021.2  02:30   12.40.0   76.80.1
 26.4  07:35249
 11   10.2   16.3  14:02  -38.0  15:328.10.0  625.50.6
 128.9  06:15 29


 There is no way there has been a wind speed of 128.9 knots!

 I can't remember how to fix these, nor can I remember if there is a
 setup somewhere to reject readings outside the parameters.

 --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/wP9HauD6dNA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the 

[weewx-user] Re: Amending spurious readings in the database

[Auchtermuchty Weather]

The colour coding makes it easier (for me) to spot the days with rogue data 
although sorting the data by (say) windspeed is another say to find it and 
yes, I realise what I need to do to find the values.  I put the spreadsheet 
up to show people what I was seeing.

My question was if this is a sign of sensors reaching the end of their 
life, given most of the rogue values have occurred since the start of March 
this year.



On Friday, 14 April 2017 10:02:52 UTC+1, Andrew Milner wrote:

> What you need to do is to use the NOAA data to possibly pinpoint a rogue 
> day, and then check the archive table to see if there is a single rogue 
> record.
>
> If there is then you can just correct the rogue record or delete it even, 
> and rebuild the stats tables and noaa files if required.
>
> You should check the log at around the time the rogue record or recoprds 
> were inserted into the database and see if there were issues recorded in 
> the log.  Maybe you have a comms problem.
>
> I could not tell what we were supposed to deduce from the colour coded 
> noaa data - since there were so many colours in use!!
>
>
>
> On Friday, 14 April 2017 11:19:15 UTC+3, Auchtermuchty Weather wrote:
>
>> Have picked up my NOAA data into excel, and find that nearly all my 'bad' 
>> values are since 1st March this year.  It was December 2016 when I replaced 
>> the Pi with a better one with the then up-to-date version of Weewx.
>>
>> XLXS file attached - I have colour coded the values in each appropriate 
>> column.
>>
>> Makes me think I do have a sensor problem or problems.  :(
>>  
>>
>> On Wednesday, 12 April 2017 09:20:06 UTC+1, Auchtermuchty Weather wrote:
>>
>>> I am getting the odd spike in my readings, for example:
>>>
>>>
>>>TEMPERATURE (C), RAIN (mm), WIND SPEED (knots)
>>>
>>>  HEAT   COOL AVG
>>>   MEAN   DEGDEG  
>>> WIND   DOM
>>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   
>>> HIGH   TIMEDIR
>>>
>>> ---
>>> 013.5   13.1  11:12   -1.1  04:31   14.80.00.00.4
>>> 6.0  07:19 22
>>> 024.3   13.4  05:56   -0.7  00:02   14.00.0  148.81.8   
>>> 44.9  05:56 25
>>> 034.3   11.9  11:31   -2.3  07:56   14.00.05.10.7
>>> 8.6  22:43191
>>> 045.26.7  15:304.0  08:30   13.20.09.90.7   
>>> 12.6  09:50207
>>> 055.6   10.3  15:25   -0.2  23:51   12.70.03.60.0
>>> 3.3  07:37108
>>> 065.2   16.7  14:55   -0.3  01:18   13.10.01.20.1   
>>> 43.5  15:34130
>>> 075.1   12.4  11:19  -15.1  08:56   13.20.0  807.90.4
>>> 8.0  16:15 77
>>> 087.3   13.3  11:314.8  07:30   11.00.02.41.7   
>>> 19.2  11:44360
>>> 098.0   14.3  14:262.7  23:51   10.30.0  271.81.2   
>>> 11.9  08:48345
>>> 106.0   10.2  16:021.2  02:30   12.40.0   76.80.1   
>>> 26.4  07:35249
>>> 11   10.2   16.3  14:02  -38.0  15:328.10.0  625.50.6  
>>> 128.9  06:15 29
>>>
>>>
>>> There is no way there has been a wind speed of 128.9 knots!
>>>
>>> I can't remember how to fix these, nor can I remember if there is a 
>>> setup somewhere to reject readings outside the parameters.
>>>
>>>

-- 
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: Amending spurious readings in the database

[Andrew Milner]

What you need to do is to use the NOAA data to possibly pinpoint a rogue 
day, and then check the archive table to see if there is a single rogue 
record.

If there is then you can just correct the rogue record or delete it even, 
and rebuild the stats tables and noaa files if required.

You should check the log at around the time the rogue record or recoprds 
were inserted into the database and see if there were issues recorded in 
the log.  Maybe you have a comms problem.

I could not tell what we were supposed to deduce from the colour coded noaa 
data - since there were so many colours in use!!



On Friday, 14 April 2017 11:19:15 UTC+3, Auchtermuchty Weather wrote:

> Have picked up my NOAA data into excel, and find that nearly all my 'bad' 
> values are since 1st March this year.  It was December 2016 when I replaced 
> the Pi with a better one with the then up-to-date version of Weewx.
>
> XLXS file attached - I have colour coded the values in each appropriate 
> column.
>
> Makes me think I do have a sensor problem or problems.  :(
>  
>
> On Wednesday, 12 April 2017 09:20:06 UTC+1, Auchtermuchty Weather wrote:
>
>> I am getting the odd spike in my readings, for example:
>>
>>
>>TEMPERATURE (C), RAIN (mm), WIND SPEED (knots)
>>
>>  HEAT   COOL AVG
>>   MEAN   DEGDEG  
>> WIND   DOM
>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   
>> HIGH   TIMEDIR
>>
>> ---
>> 013.5   13.1  11:12   -1.1  04:31   14.80.00.00.46.0  
>> 07:19 22
>> 024.3   13.4  05:56   -0.7  00:02   14.00.0  148.81.8   44.9  
>> 05:56 25
>> 034.3   11.9  11:31   -2.3  07:56   14.00.05.10.78.6  
>> 22:43191
>> 045.26.7  15:304.0  08:30   13.20.09.90.7   12.6  
>> 09:50207
>> 055.6   10.3  15:25   -0.2  23:51   12.70.03.60.03.3  
>> 07:37108
>> 065.2   16.7  14:55   -0.3  01:18   13.10.01.20.1   43.5  
>> 15:34130
>> 075.1   12.4  11:19  -15.1  08:56   13.20.0  807.90.48.0  
>> 16:15 77
>> 087.3   13.3  11:314.8  07:30   11.00.02.41.7   19.2  
>> 11:44360
>> 098.0   14.3  14:262.7  23:51   10.30.0  271.81.2   11.9  
>> 08:48345
>> 106.0   10.2  16:021.2  02:30   12.40.0   76.80.1   26.4  
>> 07:35249
>> 11   10.2   16.3  14:02  -38.0  15:328.10.0  625.50.6  128.9  
>> 06:15 29
>>
>>
>> There is no way there has been a wind speed of 128.9 knots!
>>
>> I can't remember how to fix these, nor can I remember if there is a setup 
>> somewhere to reject readings outside the parameters.
>>
>>

-- 
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.