[weewx-user] Re: Sky Cover data to pwsweather.com

[gjr80]

I should add my comments re METAR is my supposition; the observation 
related fields (as distinct from API keys, date-times, software name etc) 
in the PWS Weather upload string format are:

wind direction
wind speed
wind gust speed
temperature
hour rainfall
day rainfall
month rainfall
year rainfall
barometric pressure
dew point
humidity
solar radiation
UV

and of course the previously mentioned 'weather' field. Provided your 
station has the appropriate sensor WeeWX will upload all of these to PWS 
Weather with the exception of month rainfall and year rainfall.

Of course the other possibility is that PWS Weather could be deriving 'sky 
cover' itself though, I see no obvious source in the above fields though. 
Probably a question for PWS Weather, and if their answer is 'your station 
needs to upload it' then ask for some documentation; details of the field 
name, content, format etc because it does not appear in their PWS upload 
documentation they sent to me.

Gary



On Thursday, 18 February 2021 at 12:38:02 UTC+10 bchap...@gmail.com wrote:

> Thank you for the explanation.  I incorrectly thought that cloudcover was 
> the data expected by pwsweather.  Now that I see that it is more involved, 
> I will wait patiently.  The reason for my interest is that the AerisPulse 
> app gives me data from a station many miles from me when I am reporting 
> data to them.  Their explanation is that they only use data from stations 
> that report Sky Cover data.  All others are ignored.
>
> Again, thanks for the explanation.
>
>
> On Wednesday, February 17, 2021 at 7:53:39 PM UTC-5 gjr80 wrote:
>
>> Hi,
>>
>> Short answer is the WeeWX PWSWeather uploader does not support any form 
>> of 'sky cover percentage'. 
>>
>> In looking at the upload string format recently provided by PWSWeather 
>> the only field I can see that might support 'sky cover percentage' is the 
>> 'weather' field which is described as ' Current weather or sky conditions 
>> using standard METAR abbreviations and intensity (e.g. -RA, +SN, SKC, 
>> etc.)'. I expect you could include cloud coverage in octas in this somehow, 
>> but I am no METAR expert. The WeeWX PWSWeather uploader does not support 
>> the weather field and there is so simple config change available to the 
>> user make it do so. It would involve writing code. I do have a task to 
>> review the various uploaders included in the WeeWX core, but that is 
>> somewhat on the back burner at present and since WeeWX does not 
>> provide/generate METAR info per se, I am not sure whether that review would 
>> result in the WeeWX PWSWeather uploader supporting the 'weather' field.
>>
>> As Vince said I am intrigued as to what data it is that you want to 
>> upload. I am not aware of the GW1000 emitting any sort of cloud cover data, 
>> either via its API or through any of its weather service upload formats. 
>> You mention cloudbase, WeeWX will certainly calculate cloudbase provided 
>> the pre-requisite data is available (fields outTemp and outHumidity) but 
>> cloudbase is only a theoretical value for the cloud height; it does not in 
>> any way relate to percentage cloud cover.
>>
>> Gary
>> On Thursday, 18 February 2021 at 10:30:50 UTC+10 bchap...@gmail.com 
>> wrote:
>>
>>> I don't know.  I don't think it has anything to do with Belchertown.  
>>> pwsweather is looking for sky cover percentage.  I know that a few stations 
>>> report this and I'm wondering how it is done.  All other data is 
>>> reporting.  My data is calculating cloud base however, pwsweather is 
>>> looking for a percentage.  Any ideas?
>>>
>>>
>>> On Wednesday, February 17, 2021 at 5:59:44 PM UTC-5 vince wrote:
>>>
 On Wednesday, February 17, 2021 at 1:35:41 PM UTC-8 bchap...@gmail.com 
 wrote:

> I’m sending data to pwsweather.com using a GW1000 and I can’t figure 
> out how to send Sky Cover data.  conf file below
>
>
 Which element in which database has that data to begin with ?
 I'm sure not seeing it.

 Are you sure it's not something calculated magically by Belchertown and 
 not actually saved in a db by weewx ?
  

>>>

-- 
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/2589590a-05a9-48e7-9a26-ed3fa33588f9n%40googlegroups.com.

[weewx-user] Re: Sky Cover data to pwsweather.com

[bchap...@gmail.com]

Thank you for the explanation.  I incorrectly thought that cloudcover was 
the data expected by pwsweather.  Now that I see that it is more involved, 
I will wait patiently.  The reason for my interest is that the AerisPulse 
app gives me data from a station many miles from me when I am reporting 
data to them.  Their explanation is that they only use data from stations 
that report Sky Cover data.  All others are ignored.

Again, thanks for the explanation.


On Wednesday, February 17, 2021 at 7:53:39 PM UTC-5 gjr80 wrote:

> Hi,
>
> Short answer is the WeeWX PWSWeather uploader does not support any form of 
> 'sky cover percentage'. 
>
> In looking at the upload string format recently provided by PWSWeather the 
> only field I can see that might support 'sky cover percentage' is the 
> 'weather' field which is described as ' Current weather or sky conditions 
> using standard METAR abbreviations and intensity (e.g. -RA, +SN, SKC, 
> etc.)'. I expect you could include cloud coverage in octas in this somehow, 
> but I am no METAR expert. The WeeWX PWSWeather uploader does not support 
> the weather field and there is so simple config change available to the 
> user make it do so. It would involve writing code. I do have a task to 
> review the various uploaders included in the WeeWX core, but that is 
> somewhat on the back burner at present and since WeeWX does not 
> provide/generate METAR info per se, I am not sure whether that review would 
> result in the WeeWX PWSWeather uploader supporting the 'weather' field.
>
> As Vince said I am intrigued as to what data it is that you want to 
> upload. I am not aware of the GW1000 emitting any sort of cloud cover data, 
> either via its API or through any of its weather service upload formats. 
> You mention cloudbase, WeeWX will certainly calculate cloudbase provided 
> the pre-requisite data is available (fields outTemp and outHumidity) but 
> cloudbase is only a theoretical value for the cloud height; it does not in 
> any way relate to percentage cloud cover.
>
> Gary
> On Thursday, 18 February 2021 at 10:30:50 UTC+10 bchap...@gmail.com wrote:
>
>> I don't know.  I don't think it has anything to do with Belchertown.  
>> pwsweather is looking for sky cover percentage.  I know that a few stations 
>> report this and I'm wondering how it is done.  All other data is 
>> reporting.  My data is calculating cloud base however, pwsweather is 
>> looking for a percentage.  Any ideas?
>>
>>
>> On Wednesday, February 17, 2021 at 5:59:44 PM UTC-5 vince wrote:
>>
>>> On Wednesday, February 17, 2021 at 1:35:41 PM UTC-8 bchap...@gmail.com 
>>> wrote:
>>>
 I’m sending data to pwsweather.com using a GW1000 and I can’t figure 
 out how to send Sky Cover data.  conf file below


>>> Which element in which database has that data to begin with ?
>>> I'm sure not seeing it.
>>>
>>> Are you sure it's not something calculated magically by Belchertown and 
>>> not actually saved in a db by weewx ?
>>>  
>>>
>>

-- 
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/6f04ad2a-9fbf-44d2-a8f7-fe7ffef21d3an%40googlegroups.com.

[weewx-user] Re: Sky Cover data to pwsweather.com

[gjr80]

Hi,

Short answer is the WeeWX PWSWeather uploader does not support any form of 
'sky cover percentage'. 

In looking at the upload string format recently provided by PWSWeather the 
only field I can see that might support 'sky cover percentage' is the 
'weather' field which is described as ' Current weather or sky conditions 
using standard METAR abbreviations and intensity (e.g. -RA, +SN, SKC, 
etc.)'. I expect you could include cloud coverage in octas in this somehow, 
but I am no METAR expert. The WeeWX PWSWeather uploader does not support 
the weather field and there is so simple config change available to the 
user make it do so. It would involve writing code. I do have a task to 
review the various uploaders included in the WeeWX core, but that is 
somewhat on the back burner at present and since WeeWX does not 
provide/generate METAR info per se, I am not sure whether that review would 
result in the WeeWX PWSWeather uploader supporting the 'weather' field.

As Vince said I am intrigued as to what data it is that you want to upload. 
I am not aware of the GW1000 emitting any sort of cloud cover data, either 
via its API or through any of its weather service upload formats. You 
mention cloudbase, WeeWX will certainly calculate cloudbase provided the 
pre-requisite data is available (fields outTemp and outHumidity) but 
cloudbase is only a theoretical value for the cloud height; it does not in 
any way relate to percentage cloud cover.

Gary
On Thursday, 18 February 2021 at 10:30:50 UTC+10 bchap...@gmail.com wrote:

> I don't know.  I don't think it has anything to do with Belchertown.  
> pwsweather is looking for sky cover percentage.  I know that a few stations 
> report this and I'm wondering how it is done.  All other data is 
> reporting.  My data is calculating cloud base however, pwsweather is 
> looking for a percentage.  Any ideas?
>
>
> On Wednesday, February 17, 2021 at 5:59:44 PM UTC-5 vince wrote:
>
>> On Wednesday, February 17, 2021 at 1:35:41 PM UTC-8 bchap...@gmail.com 
>> wrote:
>>
>>> I’m sending data to pwsweather.com using a GW1000 and I can’t figure 
>>> out how to send Sky Cover data.  conf file below
>>>
>>>
>> Which element in which database has that data to begin with ?
>> I'm sure not seeing it.
>>
>> Are you sure it's not something calculated magically by Belchertown and 
>> not actually saved in a db by weewx ?
>>  
>>
>

-- 
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/1da78f13-0f11-4bd3-9c2e-774628bd0a56n%40googlegroups.com.

[weewx-user] Re: Sky Cover data to pwsweather.com

[bchap...@gmail.com]

I don't know.  I don't think it has anything to do with Belchertown.  
pwsweather is looking for sky cover percentage.  I know that a few stations 
report this and I'm wondering how it is done.  All other data is 
reporting.  My data is calculating cloud base however, pwsweather is 
looking for a percentage.  Any ideas?


On Wednesday, February 17, 2021 at 5:59:44 PM UTC-5 vince wrote:

> On Wednesday, February 17, 2021 at 1:35:41 PM UTC-8 bchap...@gmail.com 
> wrote:
>
>> I’m sending data to pwsweather.com using a GW1000 and I can’t figure out 
>> how to send Sky Cover data.  conf file below
>>
>>
> Which element in which database has that data to begin with ?
> I'm sure not seeing it.
>
> Are you sure it's not something calculated magically by Belchertown and 
> not actually saved in a db by weewx ?
>  
>

-- 
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/911ba3be-3364-41fc-b6b6-d1cf816929cbn%40googlegroups.com.

Re: [weewx-user] Fixing units in a new graph

['Jan-Jaap van der Geer' via weewx-user]

On Wednesday, February 17, 2021 at 11:27:40 PM UTC+1 tke...@gmail.com wrote:

> Formats and labels are keyed to *unit groups*, not observation types. If 
> you really want to use luminance (instead of illuminance), you need to tell 
> the system what unit group it is in. You do that by making an assignment to 
> the data structure weewx.units.obs_group_dict:
>
> import weewx.units
> weewx.units.obs_group_dict['luminance'] = 'group_illuminance'
>
> See the section *Assigning a unit group 
> * in 
> the Customizing Guide. 
>
> However, be aware that illuminance is not the same of luminance. 
> Illuminance measures the amount of light falling on a surface area. 
> Luminance measures the amount of light passing through a solid angle. Only 
> illuminance is measured in lux.
>

This is almost what I ended up doing:

import weewx.units
weewx.units.obs_group_dict['outTempBatteryStatus'] = 'group_volt'
weewx.units.obs_group_dict['luminosity'] = 'group_illuminance'

I hadn't picked up on the difference between luminance and illuminance. But 
the field I'm using is called yet another thing, luminosity. What's that 
than? Time for a bit of googling I suppose, although I'm not sure I'll go 
as far as adding a field especially for this. Since there's a field for 
luminosity I think maybe I'll use that regardless.

Thanks for the help!

Cheers,
Jan-Jaap

-- 
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/6b31a15e-07ee-48ba-aa59-956cc63e9678n%40googlegroups.com.

[weewx-user] Re: Sky Cover data to pwsweather.com

[vince]

On Wednesday, February 17, 2021 at 1:35:41 PM UTC-8 bchap...@gmail.com 
wrote:

> I’m sending data to pwsweather.com using a GW1000 and I can’t figure out 
> how to send Sky Cover data.  conf file below
>
>
Which element in which database has that data to begin with ?
I'm sure not seeing it.

Are you sure it's not something calculated magically by Belchertown and not 
actually saved in a db by weewx ?
 

-- 
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/bf1adb33-9875-4c21-9051-e3b116648d5bn%40googlegroups.com.

Re: [weewx-user] How to insert a special symbol in the format and labeling text

[Tom Keffer]

Most of the skin templates use utf-8 encoding, so the formal answer is that
special characters must be entered using that encoding.

However, if you cut and paste from a source such as copypastecharater.com,
99% of the time the paste will use utf-8 and it will display properly.


On Wed, Feb 17, 2021 at 2:18 PM D R  wrote:

> I have made some changes to the current.inc skin generating file and now
> want to tweak it just a smidge.
>
>
> In the current conditions, listing the various values, I used the
> ($trend) operator to get the difference from 24 hours ago.
>
> I had it in a line at the bottom of the listing of values, but see that
> the barometer uses a (...) form to indicate change.  I stuck the
> formatting for the temp difference after the current outside temp,
> within () and it works. Now I'm feeling brave and would like to add the
> capital Greek Delta symbol in front of the value.  I know it may be a
> little odd for someone who might casually look at the page, but this is
> for me.  I know in Word or Excel you can hold down the Alt key and type
> in the value, but I don't know if that is exclusively for Windows
> environments or not.
>
>
> I looked in the skins.conf and also for the default values for the
> database element values, but didn't find a delta that I could copy and
> paste.
>
> Is it possible to insert this character?  I know some special characters
> do show up, like the degree sign in F and C, and wind direction, so the
> Cheetah engine must be able to do it.
>
> May I ask for what that might be, or point to an area that explains how
> to do such insertions?
>
> Thanks, Dale
>
>
> --
> 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/7290361a-3495-1e63-48f5-7b2eac1d2f58%40gmail.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/CAPq0zEBjM6BGC0Vgknb-opDH8bx97k-DQpwWtYWoUQ4aX%3DXkqQ%40mail.gmail.com.

Re: [weewx-user] Fixing units in a new graph

[Tom Keffer]

Formats and labels are keyed to *unit groups*, not observation types. If
you really want to use luminance (instead of illuminance), you need to tell
the system what unit group it is in. You do that by making an assignment to
the data structure weewx.units.obs_group_dict:

import weewx.units
weewx.units.obs_group_dict['luminance'] = 'group_illuminance'

See the section *Assigning a unit group
* in the
Customizing Guide.

However, be aware that illuminance is not the same of luminance.
Illuminance measures the amount of light falling on a surface area.
Luminance measures the amount of light passing through a solid angle. Only
illuminance is measured in lux.

On Wed, Feb 17, 2021 at 1:28 PM 'Jan-Jaap van der Geer' via weewx-user <
weewx-user@googlegroups.com> wrote:

> On Tuesday, February 16, 2021 at 10:53:33 PM UTC+1 tke...@gmail.com wrote:
>
>> There's already a type for luminosity, but it's called "illuminance",
>> introduced in V4.2. It's a member of group_illuminance.
>>
>
>
>> See issue #613 , in
>> particular, this post.
>> 
>>
>
> Hm, I'm not sure that helps me. I've tried replacing the 'lux = " lux"'
> with 'illuminance = " lux"' and  adding 'illuminance = %.0f' to the
> StringFormats but there's still no unit on the graph and the low/high table
> still has lot's of digits behind the comma. I'm not sure what to do, but I
> do see that lux/illuminance might be a difficult one to get right because
> of naming confusion.
>
> But I have a graph for the voltage as well. That one also doesn't show the
> unit (v) in its graph. Maybe that's a better example. I added these values
> in weewx.conf:
>
> [[Defaults]]
>   [[[Units]]]
> Groups
>   group_volt = volt
>
> Labels
>   volt = " volt"
>
> But that does not add the unit to the volt-graph. What am I missing?
>
> Thinking about it a bit more I think I might be completely in the wrong
> area as there's nothing in the section I quoted that seems to tell weewx to
> use "°C" for temperatures but still it does.
>
> How does it know this?
>
> Cheers,
> Jan-Jaap
>
> --
> 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/0d1aad64-507e-4c76-a99d-99d0ee2c836cn%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/CAPq0zEDLGQF1rZxgig4B-T5Oa1xkHrf-3kfZa06aamCzQCM4Dw%40mail.gmail.com.

Re: [weewx-user] Fixing units in a new graph

['Jan-Jaap van der Geer' via weewx-user]

Aaaah, no matter. I just found the section 'Assigning a unit group' in the 
Customization guide. That seems to work... RTFM, I suppose... Thanks!

Cheers,
Jan-Jaap

On Wednesday, February 17, 2021 at 10:28:37 PM UTC+1 Jan-Jaap van der Geer 
wrote:

> On Tuesday, February 16, 2021 at 10:53:33 PM UTC+1 tke...@gmail.com wrote:
>
>> There's already a type for luminosity, but it's called "illuminance", 
>> introduced in V4.2. It's a member of group_illuminance. 
>>
>  
>
>> See issue #613 , in 
>> particular, this post. 
>> 
>>
>
> Hm, I'm not sure that helps me. I've tried replacing the 'lux = " lux"' 
> with 'illuminance = " lux"' and  adding 'illuminance = %.0f' to the 
> StringFormats but there's still no unit on the graph and the low/high table 
> still has lot's of digits behind the comma. I'm not sure what to do, but I 
> do see that lux/illuminance might be a difficult one to get right because 
> of naming confusion.
>
> But I have a graph for the voltage as well. That one also doesn't show the 
> unit (v) in its graph. Maybe that's a better example. I added these values 
> in weewx.conf:
>
> [[Defaults]]
>   [[[Units]]]
> Groups
>   group_volt = volt
>
> Labels
>   volt = " volt"
>   
> But that does not add the unit to the volt-graph. What am I missing?
>
> Thinking about it a bit more I think I might be completely in the wrong 
> area as there's nothing in the section I quoted that seems to tell weewx to 
> use "°C" for temperatures but still it does.
>
> How does it know this?
>
> Cheers,
> Jan-Jaap
>

-- 
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/253f38a2-ece8-4780-905e-bbc04517087bn%40googlegroups.com.

[weewx-user] How to insert a special symbol in the format and labeling text

[D R]

I have made some changes to the current.inc skin generating file and now 
want to tweak it just a smidge.



In the current conditions, listing the various values, I used the 
($trend) operator to get the difference from 24 hours ago.


I had it in a line at the bottom of the listing of values, but see that 
the barometer uses a (...) form to indicate change.  I stuck the 
formatting for the temp difference after the current outside temp, 
within () and it works. Now I'm feeling brave and would like to add the 
capital Greek Delta symbol in front of the value.  I know it may be a 
little odd for someone who might casually look at the page, but this is 
for me.  I know in Word or Excel you can hold down the Alt key and type 
in the value, but I don't know if that is exclusively for Windows 
environments or not.



I looked in the skins.conf and also for the default values for the 
database element values, but didn't find a delta that I could copy and 
paste.


Is it possible to insert this character?  I know some special characters 
do show up, like the degree sign in F and C, and wind direction, so the 
Cheetah engine must be able to do it.


May I ask for what that might be, or point to an area that explains how 
to do such insertions?


Thanks, Dale


--
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/7290361a-3495-1e63-48f5-7b2eac1d2f58%40gmail.com.

Re: [weewx-user] Looking for guidance on how to modify the Current Conditions section of the 'main page' of WeeWx

[D R]

Thank you for the replies on my question.  I think I have figured it out 
and now have a better understanding of how things work.



It is not always as one thinks it is!

Again, thank you for the replies and guidance.

Dale


--
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/52650a13-e557-b321-67d9-ab4e8150bf77%40gmail.com.

[weewx-user] Sky Cover data to pwsweather.com

[Bruce Chapman]

Help!!

I’m sending data to pwsweather.com using a GW1000 and I can’t figure out how to 
send Sky Cover data.  conf file below


Thanks!




# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.3.0

# CPD -- Added this to keep retrying!
loop_on_init = 1

##

# This section is for information about the station.

[Station]

 # Description of the station location
 location = "Granville, NY"

 # Latitude in decimal degrees. Negative for southern hemisphere
 latitude = 43.38771
 # Longitude in decimal degrees. Negative for western hemisphere.
 longitude = -73.27025

 # Altitude of the station, with unit it is in. This is downloaded from
 # from the station if the hardware supports it.
 altitude = 421, foot

 # Set to type of station hardware. There must be a corresponding stanza
 # in this file with a 'driver' parameter indicating the driver to be used.
 station_type = GW1000

 # If you have a website, you may specify an URL
 station_url = http://weather.slatevalley.net

 # The start of the rain year (1=January; 10=October, etc.). This is
 # downloaded from the station if the hardware supports it.
 rain_year_start = 1

 # Start of week (0=Monday, 6=Sunday)
 week_start = 6

##

[GW1000]
 driver = user.gw1000
 ip_address = 192.168.50.92
 port = 45000
 poll_interval = 20

##

[Vantage]
 # This section is for the Davis Vantage series of weather stations.

 # Connection type: serial or ethernet
 # serial (the classic VantagePro)
 # ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
 type = ethernet

 # If the connection type is serial, a port must be specified:
 # Debian, Ubuntu, Redhat, Fedora, and SuSE:
 # /dev/ttyUSB0 is a common USB port name
 # /dev/ttyS0 is a common serial port name
 # BSD:
 # /dev/cuaU0 is a common serial port name
 # port = /dev/ttyUSB0

 # If the connection type is ethernet, an IP Address/hostname is required:
 # host = 192.168.50.12

 ##
 # The rest of this section rarely needs any attention.
 # You can safely leave it "as is."
 ##

 # Serial baud rate (usually 19200)
 baudrate = 19200

 # TCP port (when using the WeatherLinkIP)
 tcp_port = 2

 # TCP send delay (when using the WeatherLinkIP):
 tcp_send_delay = 0.5

 # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
 loop_request = 1

 # The id of your ISS station (usually 1). If you use a wind meter connected
 # to a anemometer transmitter kit, use its id
 iss_id = 1

 # How long to wait for a response from the station before giving up (in
 # seconds; must be greater than 2)
 timeout = 10

 # How long to wait before trying again (in seconds)
 wait_before_retry = 1.2

 # How many times to try before giving up:
 max_tries = 10

 # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
 model_type = 2

# The driver to use:
#driver = weewx.drivers.vantage

##

# This section is for uploading data to Internet sites

[StdRESTful]

 [[StationRegistry]]
 # To register this weather station with weewx, set this to true
 register_this_station = true

 [[CWOP]]
 # This section is for configuring posts to CWOP.

 # If you wish to do this, set the option 'enable' to true,
 # and specify the station ID (e.g., CW1234).
 enable = true
 station = EW5855

 # If this is an APRS (radio amateur) station, uncomment
 # the following and replace with a passcode (e.g., 12345).
 #passcode = replace_me (APRS stations only)

 [[PWSweather]]
 # This section is for configuring posts to PWSweather.com.

 # If you wish to do this, set the option 'enable' to true,
 # and specify a station and password.
 # To guard against parsing errors, put the password in quotes.
 enable = true
 station = KNYGRANV5
 password = “*"

 [[Wunderground]]
 # This section is for configuring posts to the Weather Underground.

 # If you wish to do this, set the option 'enable' to true,
 # and specify a station (e.g., 'KORHOODR3') and password.
 # To guard against parsing errors, put the password in 

Re: [weewx-user] Fixing units in a new graph

['Jan-Jaap van der Geer' via weewx-user]

On Tuesday, February 16, 2021 at 10:53:33 PM UTC+1 tke...@gmail.com wrote:

> There's already a type for luminosity, but it's called "illuminance", 
> introduced in V4.2. It's a member of group_illuminance. 
>
 

> See issue #613 , in 
> particular, this post. 
> 
>

Hm, I'm not sure that helps me. I've tried replacing the 'lux = " lux"' 
with 'illuminance = " lux"' and  adding 'illuminance = %.0f' to the 
StringFormats but there's still no unit on the graph and the low/high table 
still has lot's of digits behind the comma. I'm not sure what to do, but I 
do see that lux/illuminance might be a difficult one to get right because 
of naming confusion.

But I have a graph for the voltage as well. That one also doesn't show the 
unit (v) in its graph. Maybe that's a better example. I added these values 
in weewx.conf:

[[Defaults]]
  [[[Units]]]
Groups
  group_volt = volt

Labels
  volt = " volt"
  
But that does not add the unit to the volt-graph. What am I missing?

Thinking about it a bit more I think I might be completely in the wrong 
area as there's nothing in the section I quoted that seems to tell weewx to 
use "°C" for temperatures but still it does.

How does it know this?

Cheers,
Jan-Jaap

-- 
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/0d1aad64-507e-4c76-a99d-99d0ee2c836cn%40googlegroups.com.

Re: [weewx-user] Re: Reboot GW1000 using monit?

[vince]

On Tuesday, February 16, 2021 at 8:29:51 PM UTC-8 graha...@gmail.com wrote:

> i would appreciate a recipe on how to bypass it (masquerading IPs to local 
> server and spoofing http request, and ntp request?) in the gw1000 wiki, and 
> appreciate even more it being an installation option on the driver/service
>
>
You want to look on wxforum.net in the 
https://www.wxforum.net/index.php?board=111.0 forum there and dig through 
the threads there.

Faking out the gateway isn't weewx-specific so to me it's no applicable to 
the driver/service, and the networking stuff you need to do is way outside 
the scope of weewx as an app.  Basically you need to set up a fake ecowitt 
webserver and force the queries from the gateway to go there, not to China. 
   The thread I'm aware of is 
https://www.wxforum.net/index.php?topic=40437.0 but there might be others. 
 My wifi/internet is very stable so I'm not aware that I've experienced the 
watchdog reboots here.
 

-- 
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/5d44bcd8-58a7-4cd8-a8fa-25394339043an%40googlegroups.com.

Re: [weewx-user] Re: One more option for Build Your Own enthusiasts

[Terry Steneker]

Can I just modify the code of the already installed driver or would I need 
to repackage and reinstall it. I may do that later but its another piece I 
need to learn.

Also how do I ensure its all running Python3?

Thanks for all the help.

Terry

On Tuesday, 16 February 2021 at 18:45:15 UTC-8 peterq...@gmail.com wrote:

> Driver looks like it's written for Python2 (the give away to me is the 
> print statement on the last line), so you might have a bit of fun fixing 
> python2/python3 issues. Not too terribly difficult. If you could get the 
> test program to work, you can probably get the driver to work too.
>
> On Tue, Feb 16, 2021 at 5:46 PM Terry Steneker  
> wrote:
>
>> I am using the driver located here: 
>> https://github.com/David-Enst/WeeWX-BCRobotics
>>
>> I am also attaching the file
>>
>>
>>
>> On Tuesday, 16 February 2021 at 16:53:24 UTC-8 peterq...@gmail.com wrote:
>>
>>> What driver are you using?
>>> It's going to be really tough to help with this because you have unique 
>>> hardware and aren't asking a very answerable question. 
>>>
>>> On Tue, Feb 16, 2021 at 3:26 PM Terry Steneker  
>>> wrote:
>>>

 I just purchased the BCRobotics board and tried to install the required 
 software for it. I ran into problems when I tried to test the BME280 using 
 the Adafruit ADS1x15 library. Kept getting errors and the python 
 Adafruit_BME280 library is deprecated. 

 Instead of trying to fix the errors I went the hard way and upgraded to 
 the adafruit-circuitpython libraries so I can also run Python3

 sudo pip3 install adafruit-circuitpython-bme280

 sudo pip3 install adafruit-circuitpython-ads1x15

 I then modified the BCRobotics-test-app.py to run under Python3 and the 
 upgraded Adafruit libraries.
 Tested the program and it works!

 I have attached the modified program.

 I need to modify the driver to work the same as the updated code but 
 not sure how to do that. Can I just substitute the same modifications that 
 I made to the test program? 

 Thanks
 Terry

 On Sunday, 24 November 2019 at 10:25:09 UTC-8 pred...@gmail.com wrote:

> Louis,
>
> thank you very much for your reply.
>
> I didn't realize they first did it with Python 2.7. I though you used 
> it in order for it to work with the interceptor driver.
>
> I'll keep using python 2.7 and your code but it seems that I'm missing 
> some libraries.
>
> (I think I had them all but I keep getting a " BME280_OSAMPLE_8' is 
> not defined " etc. errors) 
>
> I'll try and find the original code and libraries for Python 2.7 and 
> do the necessary adjustments.
>
> Thanks again!
>
> On Sun, Nov 24, 2019 at 7:15 PM Louis De Lange  
> wrote:
>
>> George,
>>
>> At the time when I completed that project the tutorial on the 
>> BC-Robotics website was written in Python 2.7 so I used all the 2.7 
>> libraries in my code.  With some research you should be able to convert 
>> the 
>> original code to work with python 3 libraries.
>>
>> Sorry, I have not updated anything because if it works why break it.
>>
>> LDL
>>
>> On Saturday, 23 November 2019 13:06:57 UTC-8, George Nimrodel wrote:
>>>
>>> Hey Louis,
>>>
>>> I'm trying to do exactly what you've done with the difference that I 
>>> have weewx running on the RPi and I'm using only the BME280 for 
>>> temperature 
>>> in a separate enclosure.
>>>
>>> I'm having a bit of a trouble with your code. I keep getting errors 
>>> regarding the libraries.
>>>
>>> I've noticed that you are not using the python 3 libraries from the 
>>> tutorial.
>>>
>>> I would appreciate it if you could tell me which steps you took that 
>>> are not included in the tutorial in order for your code to work.
>>>
>>> Any other pointers would also be appreciated
>>>
>>> Thank in advance!
>>>
>>> On Wednesday, December 12, 2018 at 5:53:25 AM UTC+2, Louis De Lange 
>>> wrote:

 I recently came across a really excellent solution for putting 
 together your own weather station on the cheap with high quality 
 sensors - 
 and most importantly a very useful weather HAT to use with a Raspberry 
 PI 
 to connect all the sensors.

 It comes complete with a 4 part step by step tutorial to assemble 
 the whole station, and basic code to upload the data to and online 
 service 
 - see link below:


 https://www.bc-robotics.com/tutorials/raspberry-pi-weather-station-part-1/

 I completed my own installation based on the instructions in the 
 tutorial and my station running on weewx is active at the link below

 http://peachlandweather.ca/mystation/

Re: [weewx-user] Added time to produce report on Ver 4.3

[philip....@gmail.com]

Have 2 pi's running, one is an experimental pi where if I change something 
on the web site I make sure it works before I add it to the main pi.
When I upgraded the main from v4.1.1 to v4.4 it worked OK but on the 
experimental pi it was there I noticed one of the reports was taking longer.
Now both are running v4.4 ok but not sure what caused the hiccup in the 
first place.
Have been playing with a monthly summaries web page which was the one 
report that started taking over 35 seconds to produce but is now OK on both 
machines.



On Tuesday, February 16, 2021 at 5:49:02 PM UTC tke...@gmail.com wrote:

> Just for posterity, what upgrade did you do?
>
> On Tue, Feb 16, 2021 at 9:33 AM philip@gmail.com  
> wrote:
>
>> Sorry guys upgraded my main machine and its all working OK.
>>
>>
>> On Monday, February 15, 2021 at 8:40:40 PM UTC philip@gmail.com 
>> wrote:
>>
>>> I have 2 davis consoles connected to the same Pi, the second one is only 
>>> used to record sun hours via the rain terminal and is then stored on the 
>>> sun.sdb database in the rain field.
>>> This database is exactly the same as the weewx.sdb just with a different 
>>> name and are both sqlite and Im using WEEWX MULTI to achieve this along 
>>> with a third for AIRLINK.
>>> The $WM is similar to the one used in NOAA reports #set $WM="%6.2f"
>>> The log with debug=1 will take a 2/3 days.
>>> On Monday, February 15, 2021 at 5:34:33 PM UTC tke...@gmail.com wrote:
>>>
 Not much information here, but I am not aware of any changes that would 
 cause this. 

 What is the nature of the binding 'sun_binding'? Is it a sqlite 
 database? MySQL on a remote server?

 I assume the placeholder $WM is a simple formatting string.

 How about a log? Set debug=1, restart weewxd, then post the log through 
 the first reporting cycle. Or, if it's easier, you can use wee_reports.


 On Mon, Feb 15, 2021 at 9:02 AM philip@gmail.com <
 philip@gmail.com> wrote:

> Hi
> I upgraded from v4.1.1 to v4.4 and noticed in the logs that a report 
> took 36 seconds to generate where it use to be only 1 second.
> Starting back from v4.1.1 I found that the extra time started when I 
> upgraded  from v4.2 to v4.3.
> Im using a Pi4 and on a Pi3 the time was over 70 seconds.
> After eliminating various pieces of code I find that the line
> #set $min1 = $day.rain.sum.inch.format($WM, add_label=False) was 
> causing the extra time.
> The following is an extract and not the full code but as the NOOA 
> report uses something similar and that works ok Im thinking that the 
> data_binding is perhaps the cause or have I got the code wrong and was 
> just 
> lucky in older versions.
>
> #for $day in $month($data_binding='sun_binding').days 
> =
> #set $min1 = $day.rain.sum.inch.format($WM, add_label=False)
> ===
> ===
> #end for
> Just wondered what changed in v4.3 as v4.2 work perfectly
>
> -- 
> 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/9a1f1311-b9a2-4f09-9349-7eaddc54ca4dn%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/64803a39-df6f-4678-b83c-08a94f20a85en%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/cea8a792-d499-47f8-8625-d7fa4af8b2a4n%40googlegroups.com.

Re: [weewx-user] spurious gaps within weather data - wh23xx on raspberry pi 3

['Michael Waldor' via weewx-user]

My watchdog is a very simple minded one - it regularly (once per minute 
using cron) searches /var/log/messages for USB messages. If it detects some 
the raspi will be automatically rebooted.

Sadly currently I've no access to my scripts - drop me a note if you still 
need it. Then I'll look into that ...

To be honest I do not know why my USB problems were solved. But besides 
updating involved software versions, I also started new services (e.g. 
Kodi), added an USB diskdrive, and a USB rs232 interface. For that I 
changed the USB ports (to avoid cable cluttering:-). Maybe your problem is 
simply solved by using another USB port? Or improving contacts by 
unplug/plugging?


Regards, Michael
Michael Waldor schrieb am Dienstag, 9. Februar 2021 um 10:34:06 UTC+1:

> In the meantime all my problems seem to be resolved - probabely due to 
> recent software updates:
>
> 1. No longer any USB problem after upgrading to recent raspbian (buster 
> 5.4.72-v7+).
> Previously, I encountered USB problems after some weeks. To detect them I 
> wrote a simple watchdog and rebooted my raspberry automatically. After 
> reboot USB always did recover. Additionally I did a reboot once per day. 
> Now these problems are gone, and my raspberry  is up since 38 days (the 
> day when I did the upgrade onto buster).
>
> 2. I've updated to weewx 4.x based with python 3.
> Beware, to use python 3 you have to use ANOTHER repository (see the 
> corresponding weewx documentation). If you don't switch the repository you 
> will stay with python 2. AND you must use special releases of the wh23xx 
> driver (NOT the official one, it's still at pyhton 2 as far as I know) and 
> for forecast.
>
> Concluding: After all these changes all my problems with that kind of 
> weather station are gone. Maybe one exception: If there is very heavy rain, 
> the base station will loose its contact with the sensor array despite the 
> short distance (only some meters). But of course that's not a weewx problem.
>
> I even use the same raspberry to run FHEM smart home and kodi multimedia.
> holger...@gmail.com schrieb am Montag, 8. Februar 2021 um 17:53:00 UTC+1:
>
>> Hi there,
>>
>> same thing here.
>>
>>
>>- WH2315 (Renkforce from Conrad)
>>- RaspberryPi 3B
>>- weewx 4.3.0
>>- Python 3.7
>>- SofaskinCW9009
>>- driver: wh23xx (EdwinGH fork)
>>
>> I'm also experiencing data gaps / lockups at random intervals (> once per 
>> day). I suspected RFI -> put RF chokes on all cables to an from the pi 
>> (snap ferrites and ferrite rings), shielded the USB cable with aluminum 
>> foil: problem persists.
>>
>> Of course I also changed the batteries in the outdoor unit: problem 
>> pesists.
>>
>> Here's the log:
>>
>> Feb  8 17:39:31 raspberrypi weewx[623] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 1.85 seconds
>> Feb  8 17:39:31 raspberrypi weewx[623] DEBUG weewx.manager: Daily summary 
>> version is 3.0
>> Feb  8 17:39:33 raspberrypi weewx[623] INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 1.66 seconds
>> Feb  8 17:39:33 raspberrypi weewx[623] INFO weewx.reportengine: Copied 0 
>> files to /var/www/html
>> Feb  8 17:39:33 raspberrypi weewx[623] DEBUG weewx.reportengine: Running 
>> report 'SmartphoneReport'
>> Feb  8 17:39:33 raspberrypi weewx[623] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
>> 'SmartphoneReport'
>> Feb  8 17:39:33 raspberrypi weewx[623] DEBUG weewx.cheetahgenerator: 
>> Using search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>> 'weewx.cheetahgenerator.Extras']
>> Feb  8 17:39:33 raspberrypi weewx[623] DEBUG weewx.manager: Daily summary 
>> version is 3.0
>> Feb  8 17:39:33 raspberrypi weewx[623] INFO weewx.cheetahgenerator: 
>> Generated 6 files for report SmartphoneReport in 0.11 seconds
>> Feb  8 17:39:33 raspberrypi weewx[623] DEBUG weewx.manager: Daily summary 
>> version is 3.0
>> Feb  8 17:39:33 raspberrypi weewx[623] INFO weewx.imagegenerator: 
>> Generated 6 images for report SmartphoneReport in 0.61 seconds
>> Feb  8 17:39:33 raspberrypi weewx[623] INFO weewx.reportengine: Copied 0 
>> files to /var/www/html/weewx/smartphone
>> Feb  8 17:39:33 raspberrypi weewx[623] DEBUG weewx.reportengine: Running 
>> report 'MobileReport'
>> Feb  8 17:39:34 raspberrypi weewx[623] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Mobile/skin.conf for report 
>> 'MobileReport'
>> Feb  8 17:39:34 raspberrypi weewx[623] DEBUG weewx.cheetahgenerator: 
>> Using search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>> 'weewx.cheetahgenerator.Extras']
>> Feb  8 17:39:34 raspberrypi weewx[623] DEBUG weewx.manager: