[weewx-user] Modify StdPrint to not print loop packets?

[bdf0506]

My log file is far too noisy in my docker implementation of wee experience, 
so I’m looking for a quick and easy way to only print the archive packets 
with StdPrint and then only print loop packets if debug is enabled. Is this 
easily possible? Or will I have to create my own service to run, as 
described in the customization guide?

Thanks in advance!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/75d759a9-9e93-4c8e-b6b9-e4a2ec8fe8f8n%40googlegroups.com.

Re: [weewx-user] Re: weewx crashed - issue with gw1000.py when Ecowitt WH45 5-in-1 combo sensor gets activated (5= T+PM2.5+PM10) [2b]

[gjr80]

OK, understand. Nothing to concern the GW1000 driver.

I suspect the vast majority of cases where WH45 obs are included in a skin 
will be user modified/developed skins and experience shows the user will 
format/order as the user sees fit. I suspect the default skins that ship 
with WeeWX will continue to be fairly generic in nature.

Gary
On Saturday, 2 January 2021 at 12:59:46 UTC+10 galfert wrote:

> The data comes off the GW1000 API in this order:
>
>   1　temp_co2
>
>   2　humi_co2 
>
>   3　pm10_co2
>
>   4　pm10_24h_co2
>
>   5　pm25_co2
>
>   6　pm25_24h_co2
>
>   7　co2 
>
>   8　co2_24h
>
>   9　co2_batt　
>
> I'm just trying to impart some input if it were to ever be included in any 
> default skin or presentation. This order is not good.
>
> * Reference: Official Ecowitt GW1000 API documentation. Which has limited 
> access by Ecowitt for now. I have it as I'm like an ambassador / liaison 
> for Ecowitt and the various software developers. Bound to by NDA.
>
>
>
> On Friday, January 1, 2021 at 9:48:14 PM UTC-5 galfert wrote:
>
>> I realize that this WH45 data is not yet part of any skin.  I was only 
>> trying to preempt its default inclusion in a skin. In that case my comments 
>> were that the PM2.5 be first and the PM10 data second. and the CO2 data 
>> third.
>>
>> The reason I state this is because in the raw data from the GW1000 API 
>> something you can't see unless you are in the know with the GW1000 API 
>> as I and Gary are (Ecowitt NDA regarding GW1000 API documentation). This 
>> note only will make sense to Gary. The data as is comes off the GW1000 
>> sends PM10 before PM2.5.
>>
>>
>> On Friday, January 1, 2021 at 5:53:28 PM UTC-5 lang@googlemail.com 
>> wrote:
>>
>>> As for me, the code of the new driver (0.2.1b1) works fine as far as I 
>>> can tell. 
>>>
>>> All data arrives and can be addressed, and the application doesn't crash 
>>> anymore.
>>> It can be archived (some assignment needed as not all fields are part of 
>>> the extended database schema),
>>> and it can be used in the reports.
>>>
>>> And the order in the field map is:
>>>
>>> ...
>>>
>>> 'pm2_5': 'pm251',  # =WH41/43 #1
>>>'pm2_52': 'pm252', # =WH41/43 #2
>>> 'pm2_53': 'pm253', # =WH41/43 #3
>>> 'pm2_54': 'pm254', # = WH41/43 #4
>>> 'pm2_55': 'pm255', # = WH45 PM2.5
>>> 'pm10': 'pm10',  # = WH45 PM10
>>> 'co2': 'co2',# =WH45 CO2
>>>
>>> ...  
>>>
>>> Temperature and Humidity are sorted into the extraTemperature 'section' 
>>> as #17
>>>
>>> Here I don't really understand George's request regarding sequence/order 
>>> either.
>>>
>>> "
>>> Please note that even though the raw data coming from this new sensor is 
>>> for the PM10 to come first and then the PM2.5 that is not the order that we 
>>> would typically refer to the sensor as ...it is *called the PM2.5, 
>>> PM10, CO2 sensor in that order*. Looking at the GW1000 API 
>>> documentation it baffles me why the engineers decided to send PM10 data 
>>> first. Also on the GW1000 mobile app (WS View) and on Ecowitt.net the order 
>>> is also PM2.5 first and then PM10. *I fee therefore that WeeWX should 
>>> keep the order as PM2.5 first and then PM10.*"
>>>
>>> @George: maybe you explain more in detail what exactly you mean, where 
>>> some sequence (order) is not maintained and why this is important .
>>>
>>> At least in the field map (in my terms/language: the weewx GW1000 driver 
>>> interface record declaration [but we may have different wording here, 
>>> depending on our
>>> programming language history]) exactly this sequence (order) is 
>>> maintained. Where else is this order missing ?
>>>
>>> At the end of the day, e.g. in the WSView app, it's a matter of 
>>> presentation. And which sequence/order you choose for showing this data in 
>>> the reports (e.g. Seasons skin)
>>> is up to you. There is no preset report for the WH45 data (yet), afaik, 
>>> but my knowledge may not be complete.
>>>
>>>
>>>
>>> On 01.01.2021 22:20, Paul Ward wrote:
>>>
>>> Gary I have a WH45 on order so subject to shipping delays I’m happy to 
>>> test the code too in couple of weeks when I get it, if you don’t release 
>>> beforehand.
>>>
>>> On Friday, January 1, 2021 at 1:26:45 AM UTC gjr80 wrote:
>>>
 WH45 support was coded some time ago though of course not tested with 
 an actual device. Have had a number of other features I was working on to 
 add at the same time which delayed release of the WH45 compatible version 
 of the driver. Rainer now has a copy of a compatible version of the driver 
 to test and once he confirms it works I will shortly afterwards release 
 the 
 WH45 compatible version. 

 As an aside, and on a technical note, this did highlight that I need to 
 change the approach the driver uses to dealing with sensor data from the 
 GW1000. Ideally adding an new sensor type should not 

Re: [weewx-user] Re: Rolling average for inTemp

[Tom Keffer]

The problem is that the value for line_gap_fraction is too low. It should
be more like 0.05.

Commit 94ae1e6

.

That doesn't help existing users, but it does it make less likely that new
users will trip up on it.

-tk

On Sat, Jan 2, 2021 at 4:51 PM p q  wrote:

> Thanks! Works now.
>
> So I think the example in the customization guide won't work either. I can
> update it and put in a pull request if that helps the next guy.
>
> On Sat, Jan 2, 2021 at 3:27 PM Tom Keffer  wrote:
>
>> You're getting bitten by "line gap fraction
>> ". This is an
>> option that prevents lines from being drawn across big gaps in the data.
>> The default is 0.01 (1%) of the x domain, or .27h, in this case. Your
>> aggregation interval is 30 minutes, a bit more than the max allowable gap.
>> Try this:
>>
>> [[[dayinside]]]
>>   line_gap_fraction = 0.1
>>   inTemp
>>   inTempAve
>>  color = 0x42b442 ##green
>>  data_type = inTemp
>>  aggregate_type = avg
>>  aggregate_interval = 1800
>>  label = Ave Temp
>>
>>
>>
>>
>> On Sat, Jan 2, 2021 at 3:15 PM p q  wrote:
>>
>>> [image: image.png]
>>> I guess the Groups UI doesn't like embedded images
>>>
>>> On Sat, Jan 2, 2021 at 3:13 PM peterq...@gmail.com <
>>> peterquinn...@gmail.com> wrote:
>>>
 FYI. This is what it looks like


 On Saturday, January 2, 2021 at 11:24:26 AM UTC-8 peterq...@gmail.com
 wrote:

> Hi,
>
> I'm trying to overlay a rolling average for inside temp. The heater
> going on and off introduces a cyclical pattern that I want to damp out. 
> I'm
> following the example
> in
> the customization guide, except using inTemp and it doesn't appear to be
> working. I put the following in skin.conf:
>
>   [[[dayinside]]]
> inTemp
> inTempAve
>  color = 0x42b442 ##green
>  data_type = inTemp
>  aggregate_type = avg
>  aggregate_interval = 1800
>  label = Ave Temp
>
> The title shows up in the right color but I don't get the average if I
> set the interval above about 600. Is there some limit for averages? I see
> the daily rain averages, so it looks like it should work. There are no
> error messages in the log, it just doesn't plot the average.
>
 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/d26604bb-9d9e-4c78-b480-15bb5419ac87n%40googlegroups.com
 
 .

>>>
>>>
>>> --
>>> Peter Quinn
>>> (415)794-2264
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/CAA1SM21%3D4wa4k3iP-MK1VemGvVK%2BWSw7LYGLBT3XnyuDOE5_OQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEApnZZP7%2B9jRzB7MnpQ%2BaaY6h78wKdA4SU2uyUPD%2BbEVA%40mail.gmail.com
>> 
>> .
>>
>
>
> --
> Peter Quinn
> (415)794-2264
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAA1SM22a82HsEFsi88N2f%3Dxmq-%2BCLh%3DbvRBiB2LphWxZ0F8%2Bkg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To 

Re: [weewx-user] Re: Rolling average for inTemp

[p q]

Thanks! Works now.

So I think the example in the customization guide won't work either. I can
update it and put in a pull request if that helps the next guy.

On Sat, Jan 2, 2021 at 3:27 PM Tom Keffer  wrote:

> You're getting bitten by "line gap fraction
> ". This is an option
> that prevents lines from being drawn across big gaps in the data. The
> default is 0.01 (1%) of the x domain, or .27h, in this case. Your
> aggregation interval is 30 minutes, a bit more than the max allowable gap.
> Try this:
>
> [[[dayinside]]]
>   line_gap_fraction = 0.1
>   inTemp
>   inTempAve
>  color = 0x42b442 ##green
>  data_type = inTemp
>  aggregate_type = avg
>  aggregate_interval = 1800
>  label = Ave Temp
>
>
>
>
> On Sat, Jan 2, 2021 at 3:15 PM p q  wrote:
>
>> [image: image.png]
>> I guess the Groups UI doesn't like embedded images
>>
>> On Sat, Jan 2, 2021 at 3:13 PM peterq...@gmail.com <
>> peterquinn...@gmail.com> wrote:
>>
>>> FYI. This is what it looks like
>>>
>>>
>>> On Saturday, January 2, 2021 at 11:24:26 AM UTC-8 peterq...@gmail.com
>>> wrote:
>>>
 Hi,

 I'm trying to overlay a rolling average for inside temp. The heater
 going on and off introduces a cyclical pattern that I want to damp out. I'm
 following the example
 in
 the customization guide, except using inTemp and it doesn't appear to be
 working. I put the following in skin.conf:

   [[[dayinside]]]
 inTemp
 inTempAve
  color = 0x42b442 ##green
  data_type = inTemp
  aggregate_type = avg
  aggregate_interval = 1800
  label = Ave Temp

 The title shows up in the right color but I don't get the average if I
 set the interval above about 600. Is there some limit for averages? I see
 the daily rain averages, so it looks like it should work. There are no
 error messages in the log, it just doesn't plot the average.

>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/d26604bb-9d9e-4c78-b480-15bb5419ac87n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Peter Quinn
>> (415)794-2264
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAA1SM21%3D4wa4k3iP-MK1VemGvVK%2BWSw7LYGLBT3XnyuDOE5_OQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEApnZZP7%2B9jRzB7MnpQ%2BaaY6h78wKdA4SU2uyUPD%2BbEVA%40mail.gmail.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM22a82HsEFsi88N2f%3Dxmq-%2BCLh%3DbvRBiB2LphWxZ0F8%2Bkg%40mail.gmail.com.

Re: [weewx-user] Re: Rolling average for inTemp

[Tom Keffer]

You're getting bitten by "line gap fraction
". This is an option
that prevents lines from being drawn across big gaps in the data. The
default is 0.01 (1%) of the x domain, or .27h, in this case. Your
aggregation interval is 30 minutes, a bit more than the max allowable gap.
Try this:

[[[dayinside]]]
  line_gap_fraction = 0.1
  inTemp
  inTempAve
 color = 0x42b442 ##green
 data_type = inTemp
 aggregate_type = avg
 aggregate_interval = 1800
 label = Ave Temp




On Sat, Jan 2, 2021 at 3:15 PM p q  wrote:

> [image: image.png]
> I guess the Groups UI doesn't like embedded images
>
> On Sat, Jan 2, 2021 at 3:13 PM peterq...@gmail.com <
> peterquinn...@gmail.com> wrote:
>
>> FYI. This is what it looks like
>>
>>
>> On Saturday, January 2, 2021 at 11:24:26 AM UTC-8 peterq...@gmail.com
>> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to overlay a rolling average for inside temp. The heater
>>> going on and off introduces a cyclical pattern that I want to damp out. I'm
>>> following the example
>>> in
>>> the customization guide, except using inTemp and it doesn't appear to be
>>> working. I put the following in skin.conf:
>>>
>>>   [[[dayinside]]]
>>> inTemp
>>> inTempAve
>>>  color = 0x42b442 ##green
>>>  data_type = inTemp
>>>  aggregate_type = avg
>>>  aggregate_interval = 1800
>>>  label = Ave Temp
>>>
>>> The title shows up in the right color but I don't get the average if I
>>> set the interval above about 600. Is there some limit for averages? I see
>>> the daily rain averages, so it looks like it should work. There are no
>>> error messages in the log, it just doesn't plot the average.
>>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/d26604bb-9d9e-4c78-b480-15bb5419ac87n%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Peter Quinn
> (415)794-2264
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAA1SM21%3D4wa4k3iP-MK1VemGvVK%2BWSw7LYGLBT3XnyuDOE5_OQ%40mail.gmail.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEApnZZP7%2B9jRzB7MnpQ%2BaaY6h78wKdA4SU2uyUPD%2BbEVA%40mail.gmail.com.

Re: [weewx-user] Re: Rolling average for inTemp

[p q]

[image: image.png]
I guess the Groups UI doesn't like embedded images

On Sat, Jan 2, 2021 at 3:13 PM peterq...@gmail.com 
wrote:

> FYI. This is what it looks like
>
>
> On Saturday, January 2, 2021 at 11:24:26 AM UTC-8 peterq...@gmail.com
> wrote:
>
>> Hi,
>>
>> I'm trying to overlay a rolling average for inside temp. The heater going
>> on and off introduces a cyclical pattern that I want to damp out. I'm
>> following the example
>> in
>> the customization guide, except using inTemp and it doesn't appear to be
>> working. I put the following in skin.conf:
>>
>>   [[[dayinside]]]
>> inTemp
>> inTempAve
>>  color = 0x42b442 ##green
>>  data_type = inTemp
>>  aggregate_type = avg
>>  aggregate_interval = 1800
>>  label = Ave Temp
>>
>> The title shows up in the right color but I don't get the average if I
>> set the interval above about 600. Is there some limit for averages? I see
>> the daily rain averages, so it looks like it should work. There are no
>> error messages in the log, it just doesn't plot the average.
>>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d26604bb-9d9e-4c78-b480-15bb5419ac87n%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM21%3D4wa4k3iP-MK1VemGvVK%2BWSw7LYGLBT3XnyuDOE5_OQ%40mail.gmail.com.

[weewx-user] Re: Rolling average for inTemp

[peterq...@gmail.com]

FYI. This is what it looks like


On Saturday, January 2, 2021 at 11:24:26 AM UTC-8 peterq...@gmail.com wrote:

> Hi,
>
> I'm trying to overlay a rolling average for inside temp. The heater going 
> on and off introduces a cyclical pattern that I want to damp out. I'm 
> following the example 
> in
>  
> the customization guide, except using inTemp and it doesn't appear to be 
> working. I put the following in skin.conf:
>
>   [[[dayinside]]]
> inTemp
> inTempAve
>  color = 0x42b442 ##green
>  data_type = inTemp
>  aggregate_type = avg
>  aggregate_interval = 1800
>  label = Ave Temp
>
> The title shows up in the right color but I don't get the average if I set 
> the interval above about 600. Is there some limit for averages? I see the 
> daily rain averages, so it looks like it should work. There are no error 
> messages in the log, it just doesn't plot the average.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d26604bb-9d9e-4c78-b480-15bb5419ac87n%40googlegroups.com.

Re: [weewx-user] Re: change wind direction from degress

[gjr80]

Hi,

There is no single setting you can change to have Seasons display 
directions as ordinates, unfortunately you will need to go through the 
relevant report templates(s) and change the formatting for each tag 
concerned to use .ordinal_compass. You will need to take care as some of 
the tags will look a little different to what you find in the Customization 
Guide. For example, in hilo.inc you will need to change:

$archive[1].wind.gustdir.format(add_label=False)

to

$archive[1].wind.gustdir.ordinal_compass

and

$archive[1].wind.vecdir.format(add_label=False)

to

$archive[1].wind.vecdir.ordinal_compass

You will probably want to remove some of the wind direction label tags (for 
example $unit.label.windDir) that show the degree symbol as well.

Other template files (statistics.inc springs to mind) may need similar 
changes as well, .

One other thing to keep in mind, changes to skins are fairly safe across 
upgrades but obviously not safe against a re-install. You might want to 
make note of your changes in case you need to re-apply them later.

Gary

On Sunday, 3 January 2021 at 07:50:29 UTC+10 hobbyl...@gmail.com wrote:

> i have allready read this section. the ask in if theres option to apears 
> in seasons skin the ordinates not with degress  by default , with setting 
> in skin.conf. reading the docs says the only option for group_direction is 
> degree_compass.
> tried to set degree_compass=ordinal_compass but weewx stoped after that 
> setting. 
>
>
>
>
> Στις Σάββατο, 2 Ιανουαρίου 2021 στις 7:33:20 μ.μ. UTC+2, ο χρήστης 
> peterq...@gmail.com έγραψε:
>
>> Have you looked here: http://weewx.com/docs/customizing.htm#Wind ?
>>
>> On Sat, Jan 2, 2021 at 9:31 AM Δημήτρης Βήχος  
>> wrote:
>>
>>> in current direction ok. i like to apply in all stastics  in day, weewk, 
>>> month, year .
>>>
>>> Στις Σάββατο, 2 Ιανουαρίου 2021 στις 2:57:27 μ.μ. UTC+2, ο χρήστης 
>>> storm...@gmail.com έγραψε:
>>>
 try this:   $current.windDir.ordinal_compass  

 On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com 
 wrote:

> hi everybody and happy new year!
>
> I wonder if there is a way to chande the wind direction statistics 
> from degrees to direction original
> for example from 360 to N 
> thank you!
>
 -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/f69d9d7c-1b48-4600-a139-30f0e14dbb3bn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Peter Quinn
>> (415)794-2264 <(415)%20794-2264>
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4246d79f-b0e0-4732-9d35-0f0d1df1c00fn%40googlegroups.com.

Re: [weewx-user] Rainfall data on 29 Feb

[Tom Keffer]

Still not following. What do you mean by "monthly mean precipitation"? Do
you mean the monthly total precipitation?

If so, what do you mean by "agree with my calculations"? How did you
calculate February's total? Directly from the database? Or, are you saying
that the total given for February on the page NOAA-2020.txt does not match
the total given on NOAA-2020-02.txt? Or, something else?

It would help if you included the NOAA-2020.txt and NOAA-2020-02.txt pages.
Or, even better, if they are online, include a link.

There just isn't enough information to diagnose the problem.

-tk

On Sat, Jan 2, 2021 at 7:46 AM Roger Saunders  wrote:

> When I select yearly summary on the weewx page: weewx/NOAA/NOAA-2020.txt
> the monthly mean precipitation listed there all agree with my calculations
> except for February. I tracked down the reason was that the rainfall amount
> on 29 Feb is not included in the Feb mean printed in NOAA-2020.txt Does
> that make sense?
> Roger
>
> On Saturday, 2 January 2021 at 14:37:13 UTC tke...@gmail.com wrote:
>
>> Hello, Roger
>>
>> Can you be more specific about what you're seeing? What stats are you
>> referring to? The tag $year.rain.sum? Something else? How is it not
>> matching your expectations?
>>
>> -tk
>>
>> On Sat, Jan 2, 2021 at 4:54 AM Roger Saunders  wrote:
>>
>>> Hi!
>>> I noticed that the annual rainfall stats from weewx doesn't include the
>>> 29th Feb in its calculations, easy to understand why.
>>> Roger
>>> PS Overall though really grateful of this useful software
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/a7187f60-4e68-4c1f-9c0a-d5edc44c21c5n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/47f15691-95c7-4de9-9f64-93b75e2a784dn%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEC3%3DpcFJ%3DjgAk%2BsLTqQmPyYKxNeqHpF_Y87GRWEZuh7_Q%40mail.gmail.com.

Re: [weewx-user] Re: change wind direction from degress

[Δημήτρης Βήχος]

i have allready read this section. the ask in if theres option to apears in 
seasons skin the ordinates not with degress  by default , with setting in 
skin.conf. reading the docs says the only option for group_direction is 
degree_compass.
tried to set degree_compass=ordinal_compass but weewx stoped after that 
setting. 




Στις Σάββατο, 2 Ιανουαρίου 2021 στις 7:33:20 μ.μ. UTC+2, ο χρήστης 
peterq...@gmail.com έγραψε:

> Have you looked here: http://weewx.com/docs/customizing.htm#Wind ?
>
> On Sat, Jan 2, 2021 at 9:31 AM Δημήτρης Βήχος  wrote:
>
>> in current direction ok. i like to apply in all stastics  in day, weewk, 
>> month, year .
>>
>> Στις Σάββατο, 2 Ιανουαρίου 2021 στις 2:57:27 μ.μ. UTC+2, ο χρήστης 
>> storm...@gmail.com έγραψε:
>>
>>> try this:   $current.windDir.ordinal_compass  
>>>
>>> On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com 
>>> wrote:
>>>
 hi everybody and happy new year!

 I wonder if there is a way to chande the wind direction statistics from 
 degrees to direction original
 for example from 360 to N 
 thank you!

>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f69d9d7c-1b48-4600-a139-30f0e14dbb3bn%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Peter Quinn
> (415)794-2264 <(415)%20794-2264>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/06f10b35-1f66-455d-aa3a-66dc32589151n%40googlegroups.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

[vince]

That is a great summary link.  Thanks !

On Saturday, January 2, 2021 at 12:40:26 PM UTC-8 lang@googlemail.com 
wrote:

> It works with all Ambient Weather sensors which are clones of Fine Offset 
> sensors.
>
> (Ambient also sells non-Fine Offset clone sensors and weather stations)
>
> What sensors these are, you can see at 
>
> https://www.wxforum.net/index.php?topic=40730.0
>
>
> On 02.01.2021 21:34, George Morgan wrote:
>
> Does the GW1000 work with all the AW sensors?
>
> On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:
>
>> Well there is a way to get from WS-2000 AW protocol to WeeWX...but you 
>> need a translator. You can use FOSHKplugin and that will convert AW 
>> protocol to Ecowitt protocol and then you can use the WeeWX Interceptor 
>> driver. 
>>
>>
>> On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com wrote:
>>
>>> Is there an effort to support the AW protocol for the WS-2000 server?  
>>> As a developer I would be interested in working on this if it is documented 
>>> (and maybe even if it is not).  My WS-2000 has the latest wifi and base 
>>> firmware installed. 
>>>
>>> I will also look into the GW-1000 and RTL SDR options.
>>>
>>> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>>>
 The best way is to buy the GW1000 and then it will pick up al your 
 WS-2000 sensors. Then you install WeeWX with the GW1000 API driver. 
 https://github.com/gjr80/weewx-gw1000

 There is not telnet with the WS-2000. The Interceptor driver will not 
 pick up all your sensorsif you have added optional sensors. Besides 
 with the WS-2000 it is too convoluted to get the Interceptor working 
 because there is no "Customized" server option with the supported protocol 
 for the Interceptor driver. The WS-2000 newly gained "Customized" server 
 upload option but it is Ambient protocol which is different than what the 
 Interceptor expects.


 On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com 
 wrote:

> Hi All, 
>
> I received a weather station for Christmas and realized really quickly 
> that I want / need something like weewx to make it much more capable.
>
> I saw in the list archives that others are using weewx with the 
> WS-2000, intercepting WU data.   Is there another method where weewx 
> polls 
> the WS-2000 or receives data directly from the WS-2000?  I noticed the 
> telnet protocol info on the AW website but haven't figured out which port 
> the WS-2000 is using for this communication?  If I am barking up the 
> wrong 
> tree, please let me know.
>
> BTW, I have a background in computer networking, software development 
> (day job), system administration (day job), and have been doing 
> automation 
> for many years.
>
> Please let me know if this is a more appropriate question for the dev 
> list.
>
> Happy New Year!
>
>
> -- 
 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com
  
 
 .

>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> 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+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAJ%2B0VHzg5APMmRJnbV6ubLfG%3DvpJFWsk9vwLwR%3DrfAz0-V0Lrg%40mail.gmail.com
>  
> 
> .
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5c241931-df84-44e8-b5a7-2f035c262987n%40googlegroups.com.

Re: [weewx-user] Re: CRITICAL __main__: **** must be real number, not NoneType OR CRITICAL __main__:*** %x formatpe or : an integer is required, not float

[Co van der lee]

Hi Luc,
Thanks a lot for your quick action, great! I found v0.20, brand new :)
I will update the driver with the following commands on the Rpi


   - sudo wget -O weewx-rtldavis-master.zip
   https://github.com/lheijst/weewx-rtldavis/archive/master.zip
   - sudo ./bin/wee_extension --install weewx-rtldavis-master.zip
   - sudo ./bin/wee_config --reconfigure --driver=user.rtldavis --no-prompt
   - reboot

is this the procedure or do I miss something?

For this update I need to go to the lake (Setup with 4g mobile connection)
no remote management.

i will report the results.

Compliments for your work to make 868Mhz SDR communication possible and
thanks again!

/Co


Op za 2 jan. 2021 om 17:38 schreef Luc Heijst :

> Hi Co,
>
> The error on line 938 occurs when no single message is received from the
> Davis station during an archive interval (typical 5 minutes).
> The error on line 1200 occurs when data is reveived from an analog
> temperature sensor. The 12-bit raw data is converted to 10 bits causing the
> integer type to be changed to a float.
> (This type of sensor is seldom used with Davis stations.)
>
> Luc
>
> Op zaterdag 2 januari 2021 om 10:47:10 UTC-3 schreef covan...@gmail.com:
>
>> Hi all,
>>
>>
>>
>> Ik hope someone can help me to automate errorhandling……….
>>
>>
>>
>> The Rpi with SDR (weewx 4.2 / Mysql / apache) runs well, at inexplicable
>> moments the loop is interrupted, see parts op the logfile.
>>
>>
>>
>> the weewx.service remains active only sub-processes have been stopped. a
>> /etc/init.d./weewx restart reactivate the loop until the next error.
>>
>>
>>
>> Question: my idea is a workaround, does anyone know how I can read out
>> the last 6 minutes of / var / log / syslog using a cron job (or script) and
>> if a text CRITICAL __main occurs that /etc/init.d./weewx restart will be
>> executed.
>>
>>
>>
>> or is there an easier way for a workaround.
>>
>> or will it cause other problems in the long term?
>>
>>
>>
>> Thnx a lot, in the meantime I'm going to consider a reinstall on another
>> Rpi 
>>
>>
>>
>> (29-12-202) @7:50
>>
>> · weewx.engine: Main loop exiting. Shutting engine down.
>>
>> · weewx.engine: Shutting down StdReport thread
>>
>> · user.rtldavis: shutdown process /home/pi/work/bin/rtldavis -ex
>> 200 -tf EU -tr 1
>>
>> · user.rtldavis: rtldavis with pid 1166 killed
>>
>> · *CRITICAL __main__:* Caught unrecoverable exception:
>>
>> · CRITICAL __main__:   must be real number, not NoneType
>>
>>
>>
>> earlier error (27-11-2020)
>>
>> · CRITICAL __main__:   %x format: an integer is
>> required, not float
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> LOGFILES -> ---
>>
>>
>>
>> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:05:00 CET (1609203900) to database 'weewx'
>>
>> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:05:00 CET (1609203900) to daily summary in 'weewx'
>>
>> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:10:00 CET (1609204200) to database 'weewx'
>>
>> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:10:00 CET (1609204200) to daily summary in 'weewx'
>>
>> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.engine: Garbage
>> collected 21556 objects in 0.09 seconds
>>
>> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:15:00 CET (1609204500) to database 'weewx'
>>
>> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:15:00 CET (1609204500) to daily summary in 'weewx'
>>
>> --loop still runs well
>> --
>>
>> Dec 29 07:45:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 07:45:00 CET (1609224300) to database 'weewx'
>>
>> Dec 29 07:45:17 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 07:45:00 CET (1609224300) to daily summary in 'weewx'
>>
>>
>>
>> Error started
>>
>>
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Shutting down
>> StdReport thread
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: shutdown
>> process /home/pi/work/bin/rtldavis -ex 200 -tf EU -tr 1
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: rtldavis with
>> pid 1166 killed
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: Caught
>> unrecoverable exception:
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   must
>> be real number, not NoneType
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
>> Traceback (most recent call last):
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
>> "/home/weewx/bin/weewx/engine.py", line 

Re: [weewx-user] Re: New to weewx, AW WS-2000

[Rainer Lang]

It works with all Ambient Weather sensors which are clones of Fine 
Offset sensors.


(Ambient also sells non-Fine Offset clone sensors and weather stations)

What sensors these are, you can see at

https://www.wxforum.net/index.php?topic=40730.0


On 02.01.2021 21:34, George Morgan wrote:

Does the GW1000 work with all the AW sensors?

On Sat, Jan 2, 2021, 11:41 AM galfert > wrote:


Well there is a way to get from WS-2000 AW protocol to WeeWX...but
you need a translator. You can use FOSHKplugin and that will
convert AW protocol to Ecowitt protocol and then you can use the
WeeWX Interceptor driver.


On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com
 wrote:

Is there an effort to support the AW protocol for the WS-2000
server?  As a developer I would be interested in working on
this if it is documented (and maybe even if it is not).  My
WS-2000 has the latest wifi and base firmware installed.

I will also look into the GW-1000 and RTL SDR options.

On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:

The best way is to buy the GW1000 and then it will pick up
al your WS-2000 sensors. Then you install WeeWX with the
GW1000 API driver.
https://github.com/gjr80/weewx-gw1000


There is not telnet with the WS-2000. The Interceptor
driver will not pick up all your sensorsif you have
added optional sensors. Besides with the WS-2000 it is too
convoluted to get the Interceptor working because there is
no "Customized" server option with the supported protocol
for the Interceptor driver. The WS-2000 newly gained
"Customized" server upload option but it is Ambient
protocol which is different than what the Interceptor expects.


On Saturday, January 2, 2021 at 10:29:32 AM UTC-5
gm@gmail.com wrote:

Hi All,

I received a weather station for Christmas and
realized really quickly that I want / need something
like weewx to make it much more capable.

I saw in the list archives that others are using weewx
with the WS-2000, intercepting WU data.   Is there
another method where weewx polls the WS-2000 or
receives data directly from the WS-2000?  I noticed
the telnet protocol info on the AW website but haven't
figured out which port the WS-2000 is using for this
communication?  If I am barking up the wrong tree,
please let me know.

BTW, I have a background in computer networking,
software development (day job), system administration
(day job), and have been doing automation for many years.

Please let me know if this is a more appropriate
question for the dev list.

Happy New Year!


-- 
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+...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com

.

-- 
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
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%40googlegroups.com

.

--
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 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAJ%2B0VHzg5APMmRJnbV6ubLfG%3DvpJFWsk9vwLwR%3DrfAz0-V0Lrg%40mail.gmail.com 
.


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

Re: [weewx-user] Re: New to weewx, AW WS-2000

[George Morgan]

Does the GW1000 work with all the AW sensors?

On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:

> Well there is a way to get from WS-2000 AW protocol to WeeWX...but you
> need a translator. You can use FOSHKplugin and that will convert AW
> protocol to Ecowitt protocol and then you can use the WeeWX Interceptor
> driver.
>
>
> On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com wrote:
>
>> Is there an effort to support the AW protocol for the WS-2000 server?  As
>> a developer I would be interested in working on this if it is documented
>> (and maybe even if it is not).  My WS-2000 has the latest wifi and base
>> firmware installed.
>>
>> I will also look into the GW-1000 and RTL SDR options.
>>
>> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>>
>>> The best way is to buy the GW1000 and then it will pick up al your
>>> WS-2000 sensors. Then you install WeeWX with the GW1000 API driver.
>>> https://github.com/gjr80/weewx-gw1000
>>>
>>> There is not telnet with the WS-2000. The Interceptor driver will not
>>> pick up all your sensorsif you have added optional sensors. Besides
>>> with the WS-2000 it is too convoluted to get the Interceptor working
>>> because there is no "Customized" server option with the supported protocol
>>> for the Interceptor driver. The WS-2000 newly gained "Customized" server
>>> upload option but it is Ambient protocol which is different than what the
>>> Interceptor expects.
>>>
>>>
>>> On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com
>>> wrote:
>>>
 Hi All,

 I received a weather station for Christmas and realized really quickly
 that I want / need something like weewx to make it much more capable.

 I saw in the list archives that others are using weewx with the
 WS-2000, intercepting WU data.   Is there another method where weewx polls
 the WS-2000 or receives data directly from the WS-2000?  I noticed the
 telnet protocol info on the AW website but haven't figured out which port
 the WS-2000 is using for this communication?  If I am barking up the wrong
 tree, please let me know.

 BTW, I have a background in computer networking, software development
 (day job), system administration (day job), and have been doing automation
 for many years.

 Please let me know if this is a more appropriate question for the dev
 list.

 Happy New Year!


 --
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAJ%2B0VHzg5APMmRJnbV6ubLfG%3DvpJFWsk9vwLwR%3DrfAz0-V0Lrg%40mail.gmail.com.

[weewx-user] Re: HP1000 and MQTT

[bell...@gmail.com]

Sounds like you might be interested in my MQTTSubscribeService 
 extension.
rich

On Saturday, 19 December 2020 at 10:45:47 UTC-5 ried...@gmail.com wrote:

> Hi there I run Weewx with an HP1000 weather station. Is it possible to 
> receive sensors that send data via MQTT in Weewx at the same time as the 
> HP1000. I would like to add additional data. greetings André  
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f84ecb08-b929-4ac6-a5c9-40f9e339bec1n%40googlegroups.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

[galfert]

Well there is a way to get from WS-2000 AW protocol to WeeWX...but you need 
a translator. You can use FOSHKplugin and that will convert AW protocol to 
Ecowitt protocol and then you can use the WeeWX Interceptor driver.


On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com wrote:

> Is there an effort to support the AW protocol for the WS-2000 server?  As 
> a developer I would be interested in working on this if it is documented 
> (and maybe even if it is not).  My WS-2000 has the latest wifi and base 
> firmware installed.
>
> I will also look into the GW-1000 and RTL SDR options.
>
> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>
>> The best way is to buy the GW1000 and then it will pick up al your 
>> WS-2000 sensors. Then you install WeeWX with the GW1000 API driver.
>> https://github.com/gjr80/weewx-gw1000
>>
>> There is not telnet with the WS-2000. The Interceptor driver will not 
>> pick up all your sensorsif you have added optional sensors. Besides 
>> with the WS-2000 it is too convoluted to get the Interceptor working 
>> because there is no "Customized" server option with the supported protocol 
>> for the Interceptor driver. The WS-2000 newly gained "Customized" server 
>> upload option but it is Ambient protocol which is different than what the 
>> Interceptor expects.
>>
>>
>> On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com wrote:
>>
>>> Hi All,
>>>
>>> I received a weather station for Christmas and realized really quickly 
>>> that I want / need something like weewx to make it much more capable.
>>>
>>> I saw in the list archives that others are using weewx with the WS-2000, 
>>> intercepting WU data.   Is there another method where weewx polls the 
>>> WS-2000 or receives data directly from the WS-2000?  I noticed the telnet 
>>> protocol info on the AW website but haven't figured out which port the 
>>> WS-2000 is using for this communication?  If I am barking up the wrong 
>>> tree, please let me know.
>>>
>>> BTW, I have a background in computer networking, software development 
>>> (day job), system administration (day job), and have been doing automation 
>>> for many years.
>>>
>>> Please let me know if this is a more appropriate question for the dev 
>>> list.
>>>
>>> Happy New Year!
>>>
>>>
>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%40googlegroups.com.

[weewx-user] Rolling average for inTemp

[peterq...@gmail.com]

Hi,

I'm trying to overlay a rolling average for inside temp. The heater going 
on and off introduces a cyclical pattern that I want to damp out. I'm 
following the example 
in
 
the customization guide, except using inTemp and it doesn't appear to be 
working. I put the following in skin.conf:

  [[[dayinside]]]
inTemp
inTempAve
 color = 0x42b442 ##green
 data_type = inTemp
 aggregate_type = avg
 aggregate_interval = 1800
 label = Ave Temp

The title shows up in the right color but I don't get the average if I set 
the interval above about 600. Is there some limit for averages? I see the 
daily rain averages, so it looks like it should work. There are no error 
messages in the log, it just doesn't plot the average.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b6d82d9a-937c-4e2e-bbf2-35011bf9b962n%40googlegroups.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

[George Morgan]

Is there an effort to support the AW protocol for the WS-2000 server?  As a
developer I would be interested in working on this if it is documented (and
maybe even if it is not).  My WS-2000 has the latest wifi and base firmware
installed.

I will also look into the GW-1000 and RTL SDR options.

On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:

> The best way is to buy the GW1000 and then it will pick up al your WS-2000
> sensors. Then you install WeeWX with the GW1000 API driver.
> https://github.com/gjr80/weewx-gw1000
>
> There is not telnet with the WS-2000. The Interceptor driver will not pick
> up all your sensorsif you have added optional sensors. Besides with the
> WS-2000 it is too convoluted to get the Interceptor working because there
> is no "Customized" server option with the supported protocol for the
> Interceptor driver. The WS-2000 newly gained "Customized" server upload
> option but it is Ambient protocol which is different than what the
> Interceptor expects.
>
>
> On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com wrote:
>
>> Hi All,
>>
>> I received a weather station for Christmas and realized really quickly
>> that I want / need something like weewx to make it much more capable.
>>
>> I saw in the list archives that others are using weewx with the WS-2000,
>> intercepting WU data.   Is there another method where weewx polls the
>> WS-2000 or receives data directly from the WS-2000?  I noticed the telnet
>> protocol info on the AW website but haven't figured out which port the
>> WS-2000 is using for this communication?  If I am barking up the wrong
>> tree, please let me know.
>>
>> BTW, I have a background in computer networking, software development
>> (day job), system administration (day job), and have been doing automation
>> for many years.
>>
>> Please let me know if this is a more appropriate question for the dev
>> list.
>>
>> Happy New Year!
>>
>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAJ%2B0VHxnezv2LzPuxGDq0i%2BUj41AodxVbN9TH0x_200JAah8BQ%40mail.gmail.com.

[weewx-user] Re: MQTT & Belchertown - mixed F & C units

[David Levine]

I did some more troubleshooting this morning. I looked at the weewx-mqtt 
code and saw if debug = 2, it would log the messages to the broker queue. 
What I see are only F values being sent to the MQTT broker such as:

Jan  2 17:30:36 raspberrypi weewx[14221] DEBUG user.mqtt: data: 
{'dateTime': '1609608633.0', 'usUnits': '1.0', 'rainRate_inch_per_hour': 
'0.0041459842519685035', 'hourRain_in': '0.0010364960629921259', 
'rain24_in': '0.7630002755905513', 'dayRain_in': '0.015043897637795279', 
'outTemp_F': '48.704', 'outHumidity': '65.82', 'pressure_inHg': 
'29.569262383375', 'outTempBatteryStatus': '2.58', 'UV': '1.13', 'rain_in': 
'0.0', 'windBatteryStatus': '2.58', 'radiation_Wpm2': '195.0', 
'altimeter_inHg': '29.8730484820492', 'barometer_inHg': 
'29.87618364623033', 'cloudbase_foot': '2760.0530237211146', 'dewpoint_F': 
'37.791766695627096', 'heatindex_F': '46.3679404', 'humidex_F': 
'48.704001'}

I am still seeing C units coming back while debugging the dev tools console 
when the Belchertown skin is receiving/logging the message like in my 
original post. Scanning the belcherown.js, with debug it is logging the 
incoming message so it is a head scratcher to me how one component is 
logging the outgoing message in F (US) while a different component is 
logging the incoming message in C (Metric)

David



On Friday, January 1, 2021 at 3:28:51 PM UTC-5 David Levine wrote:

> I have a new setup and working on adding MQTT to the mix. I went with 
> hivemq to start. What is occurring is the MQTT realtime refreshes appear to 
> be a celcius value and not my expected/configured fahrenheit value. Am I 
> missing a config setting/section?
>
> Below is a snippet of debug console output and what I notice is the first 
> message in the snippet shows temp in F which is what is expected. The 3rd 
> message shows everything in C which is unexpected. When I first load my web 
> page, it shows the temp, etc in F but after the first MQTT adjustment, a 
> couple of the values switch to C, though the label stays F. 
>
> belchertown.js?1609531535:37 MQTT: {"dateTime": "1609532099.0", "usUnits": 
> "1.0", "rainRate_inch_per_hour": "0.0", "hourRain_in": "0.0", "rain24_in": 
> "0.0", "dayRain_in": "0.0", "outTemp_F": "36.248", "outHumidity": "63.68", 
> "pressure_inHg": "30.143325340375", "outTempBatteryStatus": "2.559", "UV": 
> "0.15", "rain_in": "0.0", "windBatteryStatus": "2.559", "radiation_Wpm2": 
> "27.0", "altimeter_inHg": "30.451898910400498", "barometer_inHg": 
> "30.46410551847069", "cloudbase_foot": "2805.165679377027", "dewpoint_F": 
> "25.137271010741078", "heatindex_F": "36.248", "humidex_F": "36.248"}
>
> belchertown.js?1609531535:37 MQTT: {"dateTime": "1609532102.0", 
> "windSpeed_mph": "0.0", "usUnits": "1.0", "rainRate_inch_per_hour": "0.0", 
> "hourRain_in": "0.0", "rain24_in": "0.0", "dayRain_in": "0.0"}
>
> belchertown.js?1609531535:37 MQTT: {"dateTime": "1609532103.0", 
> "pressure_mbar": "1013.7152953417267", "outHumidity": "85.0", "inHumidity": 
> "97.0", "outTemp_C": "2.", "inTemp_C": "5.221", 
> "windSpeed_kph": "1.802465280003", "windGust_kph": 
> "1.802465280003", "windDir": "227.0", "radiation_Wpm2": "0.0", 
> "rain_cm": "0.0", "rainRate_mm_per_hour": "0.0", "UV": "0.0", 
> "extraTemp1_C": "7.8995", "extraTemp2_C": "6.901", 
> "extraHumid1": "85.0", "extraHumid2": "85.0", "rainBatteryStatus": "1.6", 
> "windBatteryStatus": "1.66", "barometer_mbar": "1013.7152953417267", 
> "altimeter_mbar": "1021.4013952324038", "windchill_C": 
> "2.", "heatindex_C": "2.", "dewpoint_C": 
> "0.5099126991358697", "inDewpoint_C": "4.785153750721902", 
> "maxSolarRad_Wpm2": "0.0", "cloudbase_meter": "345.781455500638", 
> "beaufort_count": "0.0", "appTemp_C": "0.5178210591074577", "humidex_C": 
> "2.", "hourRain_cm": "0.0", "rain24_cm": "0.02032", 
> "dayRain_mm": "0.20322", "usUnits": "16.0"}
>
> The first message looks correct and the 3rd message not so much. 
>
> Here's my MQTT config and what I added to the Belchertown/Extras section 
> of weewx.conf:
>
> [[MQTT]]
> server_url = mqtt://broker.hivemq.com:1883/
> topic = weather
> unit_system = US
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True
> 
> [[Belchertown]]
>  [[[Extras]]]
> # MQTT Websockets defaults
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = broker.hivemq.com
> mqtt_websockets_port = 8000
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = weather/loop
>
> Thanks!
> David
>

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

[weewx-user] Re: New to weewx, AW WS-2000

[galfert]

The best way is to buy the GW1000 and then it will pick up al your WS-2000 
sensors. Then you install WeeWX with the GW1000 API driver.
https://github.com/gjr80/weewx-gw1000

There is not telnet with the WS-2000. The Interceptor driver will not pick 
up all your sensorsif you have added optional sensors. Besides with the 
WS-2000 it is too convoluted to get the Interceptor working because there 
is no "Customized" server option with the supported protocol for the 
Interceptor driver. The WS-2000 newly gained "Customized" server upload 
option but it is Ambient protocol which is different than what the 
Interceptor expects.


On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com wrote:

> Hi All,
>
> I received a weather station for Christmas and realized really quickly 
> that I want / need something like weewx to make it much more capable.
>
> I saw in the list archives that others are using weewx with the WS-2000, 
> intercepting WU data.   Is there another method where weewx polls the 
> WS-2000 or receives data directly from the WS-2000?  I noticed the telnet 
> protocol info on the AW website but haven't figured out which port the 
> WS-2000 is using for this communication?  If I am barking up the wrong 
> tree, please let me know.
>
> BTW, I have a background in computer networking, software development (day 
> job), system administration (day job), and have been doing automation for 
> many years.
>
> Please let me know if this is a more appropriate question for the dev list.
>
> Happy New Year!
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a4f2febd-177e-4160-aef2-23d0f3a064d3n%40googlegroups.com.

Re: [weewx-user] Re: change wind direction from degress

[p q]

Have you looked here: http://weewx.com/docs/customizing.htm#Wind ?

On Sat, Jan 2, 2021 at 9:31 AM Δημήτρης Βήχος 
wrote:

> in current direction ok. i like to apply in all stastics  in day, weewk,
> month, year .
>
> Στις Σάββατο, 2 Ιανουαρίου 2021 στις 2:57:27 μ.μ. UTC+2, ο χρήστης
> storm...@gmail.com έγραψε:
>
>> try this:   $current.windDir.ordinal_compass
>>
>> On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com
>> wrote:
>>
>>> hi everybody and happy new year!
>>>
>>> I wonder if there is a way to chande the wind direction statistics from
>>> degrees to direction original
>>> for example from 360 to N
>>> thank you!
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f69d9d7c-1b48-4600-a139-30f0e14dbb3bn%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM21zutpcUPjAdY9VmdAcue6jMnn1tUPyA1Dae8E%3D1Via9w%40mail.gmail.com.

[weewx-user] Re: change wind direction from degress

[Δημήτρης Βήχος]

in current direction ok. i like to apply in all stastics  in day, weewk, 
month, year .

Στις Σάββατο, 2 Ιανουαρίου 2021 στις 2:57:27 μ.μ. UTC+2, ο χρήστης 
storm...@gmail.com έγραψε:

> try this:   $current.windDir.ordinal_compass  
>
> On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com 
> wrote:
>
>> hi everybody and happy new year!
>>
>> I wonder if there is a way to chande the wind direction statistics from 
>> degrees to direction original
>> for example from 360 to N 
>> thank you!
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f69d9d7c-1b48-4600-a139-30f0e14dbb3bn%40googlegroups.com.

[weewx-user] Re: change wind direction from degress

[Δημήτρης Βήχος]

in current dir ok. i like to apply in all statistics. in day in month etc. 
something like $day.windDir.ordinal_compass works?  

Στις Σάββατο, 2 Ιανουαρίου 2021 στις 2:57:27 μ.μ. UTC+2, ο χρήστης 
storm...@gmail.com έγραψε:

> try this:   $current.windDir.ordinal_compass  
>
> On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com 
> wrote:
>
>> hi everybody and happy new year!
>>
>> I wonder if there is a way to chande the wind direction statistics from 
>> degrees to direction original
>> for example from 360 to N 
>> thank you!
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0341887b-5802-41a0-84bf-2ad575ebd9f4n%40googlegroups.com.

[weewx-user] Re: CRITICAL __main__: **** must be real number, not NoneType OR CRITICAL __main__:*** %x formatpe or : an integer is required, not float

[Luc Heijst]

Hi Co,

The error on line 938 occurs when no single message is received from the 
Davis station during an archive interval (typical 5 minutes).
The error on line 1200 occurs when data is reveived from an analog 
temperature sensor. The 12-bit raw data is converted to 10 bits causing the 
integer type to be changed to a float.
(This type of sensor is seldom used with Davis stations.)

Luc

Op zaterdag 2 januari 2021 om 10:47:10 UTC-3 schreef covan...@gmail.com:

> Hi all,
>
>  
>
> Ik hope someone can help me to automate errorhandling………. 
>
>  
>
> The Rpi with SDR (weewx 4.2 / Mysql / apache) runs well, at inexplicable 
> moments the loop is interrupted, see parts op the logfile.
>
>  
>
> the weewx.service remains active only sub-processes have been stopped. a 
> /etc/init.d./weewx restart reactivate the loop until the next error.
>
>  
>
> Question: my idea is a workaround, does anyone know how I can read out the 
> last 6 minutes of / var / log / syslog using a cron job (or script) and if 
> a text CRITICAL __main occurs that /etc/init.d./weewx restart will be 
> executed.
>
>  
>
> or is there an easier way for a workaround.
>
> or will it cause other problems in the long term?
>
>  
>
> Thnx a lot, in the meantime I'm going to consider a reinstall on another 
> Rpi 
>
>  
>
> (29-12-202) @7:50  
>
> · weewx.engine: Main loop exiting. Shutting engine down.
>
> · weewx.engine: Shutting down StdReport thread
>
> · user.rtldavis: shutdown process /home/pi/work/bin/rtldavis -ex 
> 200 -tf EU -tr 1
>
> · user.rtldavis: rtldavis with pid 1166 killed
>
> · *CRITICAL __main__:* Caught unrecoverable exception:
>
> · CRITICAL __main__:   must be real number, not NoneType
>
>  
>
> earlier error (27-11-2020)
>
> · CRITICAL __main__:   %x format: an integer is required, 
> not float
>
>  
>
>  
>
>  
>
>  
>
>  
>
> LOGFILES -> ---
>
>  
>
> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:05:00 CET (1609203900) to database 'weewx'
>
> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:05:00 CET (1609203900) to daily summary in 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:10:00 CET (1609204200) to database 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:10:00 CET (1609204200) to daily summary in 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.engine: Garbage collected 
> 21556 objects in 0.09 seconds
>
> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:15:00 CET (1609204500) to database 'weewx'
>
> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:15:00 CET (1609204500) to daily summary in 'weewx'
>
> --loop still runs well 
> --
>
> Dec 29 07:45:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 07:45:00 CET (1609224300) to database 'weewx'
>
> Dec 29 07:45:17 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 07:45:00 CET (1609224300) to daily summary in 'weewx'
>
>  
>
> Error started
>
>  
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Shutting down 
> StdReport thread
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: shutdown process 
> /home/pi/work/bin/rtldavis -ex 200 -tf EU -tr 1
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: rtldavis with 
> pid 1166 killed
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: Caught 
> unrecoverable exception:
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   must be 
> real number, not NoneType
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> Traceback (most recent call last):
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File 
> "/home/weewx/bin/weewx/engine.py", line 210, in run
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File 
> "/home/weewx/bin/weewx/engine.py", line 241, in dispatchEvent
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> callback(event)
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File 
> "/home/weewx/bin/weewx/engine.py", line 630, in check_loop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> raise BreakLoop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> weewx.engine.BreakLoop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
>
> Dec 29 

[weewx-user] Re: CRITICAL __main__: **** must be real number, not NoneType OR CRITICAL __main__:*** %x formatpe or : an integer is required, not float

[Luc Heijst]

The errors are fixed in version 0.20

these are the changes:
line 935
if total_max_count > 0:
if total_max_count > 0 and self.stats['pct_good_all'] is not 
None:
line 941
if self.stats['curr_cnt'][i] > 0 and self.stats['count'][i] 
> 0:
if self.stats['curr_cnt'][i] > 0 and self.stats['count'][i] 
> 0 and self.stats['pct_good'] is not None:

line 1199
dbg_parse(2, "thermistor temp_raw=0x%03x temp_c=%s"
dbg_parse(2, "thermistor temp_raw=%s temp_c=%s"

Op zaterdag 2 januari 2021 om 10:47:10 UTC-3 schreef covan...@gmail.com:

> Hi all,
>
>  
>
> Ik hope someone can help me to automate errorhandling………. 
>
>  
>
> The Rpi with SDR (weewx 4.2 / Mysql / apache) runs well, at inexplicable 
> moments the loop is interrupted, see parts op the logfile.
>
>  
>
> the weewx.service remains active only sub-processes have been stopped. a 
> /etc/init.d./weewx restart reactivate the loop until the next error.
>
>  
>
> Question: my idea is a workaround, does anyone know how I can read out the 
> last 6 minutes of / var / log / syslog using a cron job (or script) and if 
> a text CRITICAL __main occurs that /etc/init.d./weewx restart will be 
> executed.
>
>  
>
> or is there an easier way for a workaround.
>
> or will it cause other problems in the long term?
>
>  
>
> Thnx a lot, in the meantime I'm going to consider a reinstall on another 
> Rpi 
>
>  
>
> (29-12-202) @7:50  
>
> · weewx.engine: Main loop exiting. Shutting engine down.
>
> · weewx.engine: Shutting down StdReport thread
>
> · user.rtldavis: shutdown process /home/pi/work/bin/rtldavis -ex 
> 200 -tf EU -tr 1
>
> · user.rtldavis: rtldavis with pid 1166 killed
>
> · *CRITICAL __main__:* Caught unrecoverable exception:
>
> · CRITICAL __main__:   must be real number, not NoneType
>
>  
>
> earlier error (27-11-2020)
>
> · CRITICAL __main__:   %x format: an integer is required, 
> not float
>
>  
>
>  
>
>  
>
>  
>
>  
>
> LOGFILES -> ---
>
>  
>
> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:05:00 CET (1609203900) to database 'weewx'
>
> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:05:00 CET (1609203900) to daily summary in 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:10:00 CET (1609204200) to database 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:10:00 CET (1609204200) to daily summary in 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.engine: Garbage collected 
> 21556 objects in 0.09 seconds
>
> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:15:00 CET (1609204500) to database 'weewx'
>
> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 02:15:00 CET (1609204500) to daily summary in 'weewx'
>
> --loop still runs well 
> --
>
> Dec 29 07:45:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 07:45:00 CET (1609224300) to database 'weewx'
>
> Dec 29 07:45:17 wsb-meteo weewx[1162] INFO weewx.manager: Added record 
> 2020-12-29 07:45:00 CET (1609224300) to daily summary in 'weewx'
>
>  
>
> Error started
>
>  
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Main loop 
> exiting. Shutting engine down.
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Shutting down 
> StdReport thread
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: shutdown process 
> /home/pi/work/bin/rtldavis -ex 200 -tf EU -tr 1
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: rtldavis with 
> pid 1166 killed
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: Caught 
> unrecoverable exception:
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   must be 
> real number, not NoneType
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> Traceback (most recent call last):
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File 
> "/home/weewx/bin/weewx/engine.py", line 210, in run
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File 
> "/home/weewx/bin/weewx/engine.py", line 241, in dispatchEvent
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> callback(event)
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File 
> "/home/weewx/bin/weewx/engine.py", line 630, in check_loop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   
> raise BreakLoop
>
> Dec 29 07:50:16 

Re: [weewx-user] Rainfall data on 29 Feb

[Roger Saunders]

When I select yearly summary on the weewx page: weewx/NOAA/NOAA-2020.txt 
the monthly mean precipitation listed there all agree with my calculations 
except for February. I tracked down the reason was that the rainfall amount 
on 29 Feb is not included in the Feb mean printed in NOAA-2020.txt Does 
that make sense?
Roger

On Saturday, 2 January 2021 at 14:37:13 UTC tke...@gmail.com wrote:

> Hello, Roger
>
> Can you be more specific about what you're seeing? What stats are you 
> referring to? The tag $year.rain.sum? Something else? How is it not 
> matching your expectations?
>
> -tk
>
> On Sat, Jan 2, 2021 at 4:54 AM Roger Saunders  wrote:
>
>> Hi!
>> I noticed that the annual rainfall stats from weewx doesn't include the 
>> 29th Feb in its calculations, easy to understand why. 
>> Roger
>> PS Overall though really grateful of this useful software
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/a7187f60-4e68-4c1f-9c0a-d5edc44c21c5n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/47f15691-95c7-4de9-9f64-93b75e2a784dn%40googlegroups.com.

[weewx-user] Re: best way to use weewx with a Davis station

[Mark Jenks]

You can still find the 6510USB for sale online.

On Thursday, December 31, 2020 at 2:41:01 PM UTC-6 pedal...@gmail.com wrote:

> Yes you can. I have a Davis Vantage Vue and Weatherlink Live and have that 
> ability with weewx
>
> On Thursday, December 31, 2020 at 12:45:40 PM UTC-5 Juan Antonio Mosquera 
> wrote:
>
>> ok ... and with weatherlink cloud weewx gets all current and historical 
>> data (I have seen that there is a weewx extension for weatherlink live to 
>> work). QUESTION: can I buy a davis vantage pro2 with weatherlink live and 
>> have historical data with weewx? (using the extension)
>>
>> O xoves, 31 de decembro de 2020 á/s 14:59:22 UTC+1, kk44...@gmail.com 
>> escribiu:
>>
>>> The adaptors for the console are discontinued. Davis now sells the 
>>> WeatherLinkLive device, only. 
>>>
>>> To use WeatherLinkLive you do not need a console at all. Unfortunately 
>>> you cannot use the device without setting it up by connecting it to the 
>>> cloud of Davis.
>>>
>>> The drivers for the old adaptors can read data saved in the device. 
>>> That's why you do not loose data if weewx is down for some time. The 
>>> drivers for WeatherLinkLive cannot read those data. Davis prevents it.
>>>
>>> Juan Antonio Mosquera schrieb am Donnerstag, 31. Dezember 2020 um 
>>> 10:16:20 UTC+1:
>>>

 hi, what is the best way to use weewx with a davis vantage vue2 or 
 davis vantage pro2 ?. weatherlink live? or ... USB console and datalogger?

 thanks.

>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/163dcd18-796a-4fbd-83a7-179220fda00en%40googlegroups.com.

[weewx-user] New to weewx, AW WS-2000

[George Morgan]

Hi All,

I received a weather station for Christmas and realized really quickly that
I want / need something like weewx to make it much more capable.

I saw in the list archives that others are using weewx with the WS-2000,
intercepting WU data.   Is there another method where weewx polls the
WS-2000 or receives data directly from the WS-2000?  I noticed the telnet
protocol info on the AW website but haven't figured out which port the
WS-2000 is using for this communication?  If I am barking up the wrong
tree, please let me know.

BTW, I have a background in computer networking, software development (day
job), system administration (day job), and have been doing automation for
many years.

Please let me know if this is a more appropriate question for the dev list.

Happy New Year!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAJ%2B0VHww9JXrK96Xa%2BU6%2BFxsvBfHJcZW%2Bb8My5_FVPP14kO2UQ%40mail.gmail.com.

Re: [weewx-user] CRITICAL __main__: **** must be real number, not NoneType OR CRITICAL __main__:*** %x formatpe or : an integer is required, not float

[Co van der lee]

Thanks for your quick response Tom, I posted it on lheist's Git. I hope he
can fix it?
The crazy thing is the spontaneous occurrence, every 5 minutes the loop
runs, some days without error and then suddenly this happend 

As a workaround for the time to fix .
- appear there other errors if i restart the weewx.server each hour
preventive? technicly possible with Cron.
- do you have an idea to automate when this occours (if message is CRITICAL
than ..) at script / tool? (read last 6 min. from syslog for CRITICAL
sign)

thanks! And keep up the good work! compliments for your work!

Op za 2 jan. 2021 om 15:30 schreef Tom Keffer :

> These are both simple errors in the driver rtldavis. Ask the driver's
> author to fix the problem.
>
> On Sat, Jan 2, 2021 at 5:47 AM Co van der lee 
> wrote:
>
>> Hi all,
>>
>>
>>
>> Ik hope someone can help me to automate errorhandling……….
>>
>>
>>
>> The Rpi with SDR (weewx 4.2 / Mysql / apache) runs well, at inexplicable
>> moments the loop is interrupted, see parts op the logfile.
>>
>>
>>
>> the weewx.service remains active only sub-processes have been stopped. a
>> /etc/init.d./weewx restart reactivate the loop until the next error.
>>
>>
>>
>> Question: my idea is a workaround, does anyone know how I can read out
>> the last 6 minutes of / var / log / syslog using a cron job (or script) and
>> if a text CRITICAL __main occurs that /etc/init.d./weewx restart will be
>> executed.
>>
>>
>>
>> or is there an easier way for a workaround.
>>
>> or will it cause other problems in the long term?
>>
>>
>>
>> Thnx a lot, in the meantime I'm going to consider a reinstall on another
>> Rpi 
>>
>>
>>
>> (29-12-202) @7:50
>>
>> · weewx.engine: Main loop exiting. Shutting engine down.
>>
>> · weewx.engine: Shutting down StdReport thread
>>
>> · user.rtldavis: shutdown process /home/pi/work/bin/rtldavis -ex
>> 200 -tf EU -tr 1
>>
>> · user.rtldavis: rtldavis with pid 1166 killed
>>
>> · *CRITICAL __main__:* Caught unrecoverable exception:
>>
>> · CRITICAL __main__:   must be real number, not NoneType
>>
>>
>>
>> earlier error (27-11-2020)
>>
>> · CRITICAL __main__:   %x format: an integer is
>> required, not float
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> LOGFILES -> ---
>>
>>
>>
>> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:05:00 CET (1609203900) to database 'weewx'
>>
>> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:05:00 CET (1609203900) to daily summary in 'weewx'
>>
>> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:10:00 CET (1609204200) to database 'weewx'
>>
>> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:10:00 CET (1609204200) to daily summary in 'weewx'
>>
>> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.engine: Garbage
>> collected 21556 objects in 0.09 seconds
>>
>> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:15:00 CET (1609204500) to database 'weewx'
>>
>> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 02:15:00 CET (1609204500) to daily summary in 'weewx'
>>
>> --loop still runs well
>> --
>>
>> Dec 29 07:45:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 07:45:00 CET (1609224300) to database 'weewx'
>>
>> Dec 29 07:45:17 wsb-meteo weewx[1162] INFO weewx.manager: Added record
>> 2020-12-29 07:45:00 CET (1609224300) to daily summary in 'weewx'
>>
>>
>>
>> Error started
>>
>>
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Shutting down
>> StdReport thread
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: shutdown
>> process /home/pi/work/bin/rtldavis -ex 200 -tf EU -tr 1
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: rtldavis with
>> pid 1166 killed
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: Caught
>> unrecoverable exception:
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   must
>> be real number, not NoneType
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
>> Traceback (most recent call last):
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
>> "/home/weewx/bin/weewx/engine.py", line 210, in run
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
>> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
>> "/home/weewx/bin/weewx/engine.py", line 241, in dispatchEvent
>>
>> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
>> callback(event)
>>
>> Dec 29 

Re: [weewx-user] Rainfall data on 29 Feb

[Tom Keffer]

Hello, Roger

Can you be more specific about what you're seeing? What stats are you
referring to? The tag $year.rain.sum? Something else? How is it not
matching your expectations?

-tk

On Sat, Jan 2, 2021 at 4:54 AM Roger Saunders  wrote:

> Hi!
> I noticed that the annual rainfall stats from weewx doesn't include the
> 29th Feb in its calculations, easy to understand why.
> Roger
> PS Overall though really grateful of this useful software
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a7187f60-4e68-4c1f-9c0a-d5edc44c21c5n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAPZrwiv%3DU4Us8fevMqWxwyN2unPCjn%3DkxsAmT%3D8m%3DrEA%40mail.gmail.com.

Re: [weewx-user] CRITICAL __main__: **** must be real number, not NoneType OR CRITICAL __main__:*** %x formatpe or : an integer is required, not float

[Tom Keffer]

These are both simple errors in the driver rtldavis. Ask the driver's
author to fix the problem.

On Sat, Jan 2, 2021 at 5:47 AM Co van der lee  wrote:

> Hi all,
>
>
>
> Ik hope someone can help me to automate errorhandling……….
>
>
>
> The Rpi with SDR (weewx 4.2 / Mysql / apache) runs well, at inexplicable
> moments the loop is interrupted, see parts op the logfile.
>
>
>
> the weewx.service remains active only sub-processes have been stopped. a
> /etc/init.d./weewx restart reactivate the loop until the next error.
>
>
>
> Question: my idea is a workaround, does anyone know how I can read out the
> last 6 minutes of / var / log / syslog using a cron job (or script) and if
> a text CRITICAL __main occurs that /etc/init.d./weewx restart will be
> executed.
>
>
>
> or is there an easier way for a workaround.
>
> or will it cause other problems in the long term?
>
>
>
> Thnx a lot, in the meantime I'm going to consider a reinstall on another
> Rpi 
>
>
>
> (29-12-202) @7:50
>
> · weewx.engine: Main loop exiting. Shutting engine down.
>
> · weewx.engine: Shutting down StdReport thread
>
> · user.rtldavis: shutdown process /home/pi/work/bin/rtldavis -ex
> 200 -tf EU -tr 1
>
> · user.rtldavis: rtldavis with pid 1166 killed
>
> · *CRITICAL __main__:* Caught unrecoverable exception:
>
> · CRITICAL __main__:   must be real number, not NoneType
>
>
>
> earlier error (27-11-2020)
>
> · CRITICAL __main__:   %x format: an integer is required,
> not float
>
>
>
>
>
>
>
>
>
>
>
> LOGFILES -> ---
>
>
>
> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 02:05:00 CET (1609203900) to database 'weewx'
>
> Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 02:05:00 CET (1609203900) to daily summary in 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 02:10:00 CET (1609204200) to database 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 02:10:00 CET (1609204200) to daily summary in 'weewx'
>
> Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.engine: Garbage collected
> 21556 objects in 0.09 seconds
>
> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 02:15:00 CET (1609204500) to database 'weewx'
>
> Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 02:15:00 CET (1609204500) to daily summary in 'weewx'
>
> --loop still runs well
> --
>
> Dec 29 07:45:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 07:45:00 CET (1609224300) to database 'weewx'
>
> Dec 29 07:45:17 wsb-meteo weewx[1162] INFO weewx.manager: Added record
> 2020-12-29 07:45:00 CET (1609224300) to daily summary in 'weewx'
>
>
>
> Error started
>
>
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Shutting down
> StdReport thread
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: shutdown process
> /home/pi/work/bin/rtldavis -ex 200 -tf EU -tr 1
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: rtldavis with
> pid 1166 killed
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: Caught
> unrecoverable exception:
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   must be
> real number, not NoneType
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
> Traceback (most recent call last):
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
> "/home/weewx/bin/weewx/engine.py", line 210, in run
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
> "/home/weewx/bin/weewx/engine.py", line 241, in dispatchEvent
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
> callback(event)
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
> "/home/weewx/bin/weewx/engine.py", line 630, in check_loop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
> raise BreakLoop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
> weewx.engine.BreakLoop
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   During
> handling of the above exception, another exception occurred:
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
> Traceback (most recent call last):
>
> Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
> 

[weewx-user] CRITICAL __main__: **** must be real number, not NoneType OR CRITICAL __main__:*** %x formatpe or : an integer is required, not float

[Co van der lee]

Hi all,



Ik hope someone can help me to automate errorhandling……….



The Rpi with SDR (weewx 4.2 / Mysql / apache) runs well, at inexplicable
moments the loop is interrupted, see parts op the logfile.



the weewx.service remains active only sub-processes have been stopped. a
/etc/init.d./weewx restart reactivate the loop until the next error.



Question: my idea is a workaround, does anyone know how I can read out the
last 6 minutes of / var / log / syslog using a cron job (or script) and if
a text CRITICAL __main occurs that /etc/init.d./weewx restart will be
executed.



or is there an easier way for a workaround.

or will it cause other problems in the long term?



Thnx a lot, in the meantime I'm going to consider a reinstall on another
Rpi 



(29-12-202) @7:50

· weewx.engine: Main loop exiting. Shutting engine down.

· weewx.engine: Shutting down StdReport thread

· user.rtldavis: shutdown process /home/pi/work/bin/rtldavis -ex
200 -tf EU -tr 1

· user.rtldavis: rtldavis with pid 1166 killed

· *CRITICAL __main__:* Caught unrecoverable exception:

· CRITICAL __main__:   must be real number, not NoneType



earlier error (27-11-2020)

· CRITICAL __main__:   %x format: an integer is required,
not float











LOGFILES -> ---



Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 02:05:00 CET (1609203900) to database 'weewx'

Dec 29 02:05:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 02:05:00 CET (1609203900) to daily summary in 'weewx'

Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 02:10:00 CET (1609204200) to database 'weewx'

Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 02:10:00 CET (1609204200) to daily summary in 'weewx'

Dec 29 02:10:16 wsb-meteo weewx[1162] INFO weewx.engine: Garbage collected
21556 objects in 0.09 seconds

Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 02:15:00 CET (1609204500) to database 'weewx'

Dec 29 02:15:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 02:15:00 CET (1609204500) to daily summary in 'weewx'

--loop still runs well
--

Dec 29 07:45:16 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 07:45:00 CET (1609224300) to database 'weewx'

Dec 29 07:45:17 wsb-meteo weewx[1162] INFO weewx.manager: Added record
2020-12-29 07:45:00 CET (1609224300) to daily summary in 'weewx'



Error started



Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Main loop exiting.
Shutting engine down.

Dec 29 07:50:16 wsb-meteo weewx[1162] INFO weewx.engine: Shutting down
StdReport thread

Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: shutdown process
/home/pi/work/bin/rtldavis -ex 200 -tf EU -tr 1

Dec 29 07:50:16 wsb-meteo weewx[1162] INFO user.rtldavis: rtldavis with pid
1166 killed

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: Caught
unrecoverable exception:

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   must be
real number, not NoneType

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
Traceback (most recent call last):

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
"/home/weewx/bin/weewx/engine.py", line 210, in run

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
"/home/weewx/bin/weewx/engine.py", line 241, in dispatchEvent

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
callback(event)

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
"/home/weewx/bin/weewx/engine.py", line 630, in check_loop

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
raise BreakLoop

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
weewx.engine.BreakLoop

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   During
handling of the above exception, another exception occurred:

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
Traceback (most recent call last):

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
"/home/weewx/bin/weewx/engine.py", line 646, in post_loop

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: 
self._catchup(self.engine.console.genArchiveRecords)

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__: File
"/home/weewx/bin/weewx/engine.py", line 690, in _catchup

Dec 29 07:50:16 wsb-meteo weewx[1162] CRITICAL __main__:   for
record in 

[weewx-user] Re: change wind direction from degress

[storm...@gmail.com]

try this:   $current.windDir.ordinal_compass  

On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com wrote:

> hi everybody and happy new year!
>
> I wonder if there is a way to chande the wind direction statistics from 
> degrees to direction original
> for example from 360 to N 
> thank you!
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/995611b6-cbd3-4207-96df-f634c43bea89n%40googlegroups.com.

[weewx-user] Rainfall data on 29 Feb

[Roger Saunders]

Hi!
I noticed that the annual rainfall stats from weewx doesn't include the 
29th Feb in its calculations, easy to understand why. 
Roger
PS Overall though really grateful of this useful software

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a7187f60-4e68-4c1f-9c0a-d5edc44c21c5n%40googlegroups.com.

[weewx-user] Adding new folder to Belchertown skin

[weather list]

I have added a folder to the Belchertown skin containing some html files which 
are updated daily. The folder has an index.html.tmpl file and adding to the 
skin.conf [[ToDate]] list creates the folder and generates the index.html page 
but the HTML files are not updated. How do I configure it so that its contents 
are automatically uploaded periodically to the HTML_ROOT?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/90946D66-F53F-42B5-B674-2A183212ACE4%40gmail.com.

[weewx-user] change wind direction from degress

[hobbyl...@gmail.com]

hi everybody and happy new year!

I wonder if there is a way to chande the wind direction statistics from 
degrees to direction original
for example from 360 to N 
thank you!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/44611b68-5913-4918-a482-abeb16b1811en%40googlegroups.com.