[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[Paul McGeorge]

You could start by trying $current.soilMoist1 in your current.inc file if your 
using the seasons skin.  Read the customization guide for more options.
  
http://www.weewx.com/docs/customizing.htm#customizing_templates

-- 
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/13c206ea-7f20-4d1d-8ca1-c19946ae00eb%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[Paul McGeorge]

Yup could start by trying $current.soilmoist1 in your current.inc file if your 
using the seasons skin.  Read the customization guide for more options.  

http://www.weewx.com/docs/customizing.htm#customizing_templates

-- 
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/0d73cc15-02c7-431e-b0f4-1e4c7a2ccf30%40googlegroups.com.

Re: [weewx-user] Wunderfixer (Development Version)

[Thomas Keffer]

No. The URL to get existing data is hardwired in wunderfixer, the URL to
post new data is hardwired in weewx/restx.py.

-tk

On Mon, Feb 10, 2020 at 6:04 PM Ernest Jillson  wrote:

> Nope. Not your fault. Does it pull the URL from the weewx.conf?  I know I
> put those back to the original after weather underground gave up (for now)
> on their re-organization.
>
>
> On Mon, Feb 10, 2020 at 5:01 PM Thomas Keffer  wrote:
>
>> That doesn't surprise me. Unfortunately, there is really nothing we can
>> do about it. 😕
>>
>> On Mon, Feb 10, 2020 at 11:28 AM Ernest Jillson 
>> wrote:
>>
>>> I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and
>>> as before, it says it's doing everything it's supposed to do. So far, after
>>> 5 minutes, nothing on weather underground. I'll keep checking.
>>>
>>>
>>>
>>> On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:

 Could you try the present version of wunderfixer? I just patched it
 this morning.

 On Mon, Feb 10, 2020 at 6:50 AM Ernest Jillson 
 wrote:

> Checking here:
> https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily
>
> I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin
> folder.  My commands, minus my api key, were:
>
> cd /home/pi/weewx4/weewx-4.0.0b11/bin
> ./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key"
> --date=2020-01-29
>
> I applied the logic fix to get around the "204" error code. It
> definitely *thinks* it's sending the data. Lists every 5 minute 
> observation
> and says "...published." after each one.  I've done this three times or
> more over the last few days, so it's not a lag issue.
>
> It's looking like it may well be a WU problem that I'll just have to
> live with.
>
> Thanks for all your help.
>
>
> On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote:
>>
>> Hey, Ernest.
>>
>> If you check after some time has passed are the records there?
>> There is always a "lag" between the time the records are uploaded and
>> when they appear.
>> Also, be sure to check via the WU web portal and not some app like
>> WunderStation (which they've deprecated).
>>
>> Anyway, the wunderfixer is doing its job.  What happens on the WU
>> side is subject to their many bugs and infrastructure issues.  :-/
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad)
>>
>> On Feb 9, 2020, at 9:59 PM, Ernest Jillson  wrote:
>>
>> 
>> It "looks" like it's working for me, but doesn't.  I get this message:
>>
>> "No results returned from Weather Underground (perhaps a bad station
>> name??).
>> Publishing anyway."
>>
>> It then proceeds to upload all my 5 minute obs.  Only thing is, they
>> never show up on wunderground.
>>
>>
>>
>> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:
>>>
>>>
>>> Worked for me thanks.
>>>
>>> Richard
>>> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:

 Richard,
 It was a long thread.  Here is my workaround for the 204 response
 when the request is valid, but there are no records to return:

 $ diff wunderfixer wunderfixer_tk
 407,409c407
 < # Valid response, it's just that WU has no
 records for the requested date
 < # Return an empty list of TimeStamps (as in WU
 has no records)
 < return {}
 ---
 > raise IOError("Probably a bad station ID or
 invalid date")

 Or if the line numbers don't match yours, it looks like this in
 context:

 if hasattr(response, 'code') and response.code != 200:
 if response.code == 204:
 # Valid response, it's just that WU has no records
 for the requested date
 # Return an empty list of TimeStamps (as in WU has
 no records)
 return {}
 else:
 raise IOError("Bad response code returned: %d" %
 response.code)

 Regards,
 \Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPhone)

 On Feb 9, 2020, at 12:40 PM, Richard G  wrote:

 
 I had an outage of a week where no data was uploaded to
 wunderground. I discovered all the posts about the change of API etc. 
 so
 pulled down the development branch. This version with the api_key 
 allowed
 me to fix data on partial days i.e. when there was some data but on 
 days
 where there is no data at all then it fails

 Usin

Re: [weewx-user] Wunderfixer (Development Version)

[Ernest Jillson]

Nope. Not your fault. Does it pull the URL from the weewx.conf?  I know I
put those back to the original after weather underground gave up (for now)
on their re-organization.


On Mon, Feb 10, 2020 at 5:01 PM Thomas Keffer  wrote:

> That doesn't surprise me. Unfortunately, there is really nothing we can do
> about it. 😕
>
> On Mon, Feb 10, 2020 at 11:28 AM Ernest Jillson 
> wrote:
>
>> I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and
>> as before, it says it's doing everything it's supposed to do. So far, after
>> 5 minutes, nothing on weather underground. I'll keep checking.
>>
>>
>>
>> On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:
>>>
>>> Could you try the present version of wunderfixer? I just patched it this
>>> morning.
>>>
>>> On Mon, Feb 10, 2020 at 6:50 AM Ernest Jillson 
>>> wrote:
>>>
 Checking here:
 https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily

 I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin
 folder.  My commands, minus my api key, were:

 cd /home/pi/weewx4/weewx-4.0.0b11/bin
 ./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key"
 --date=2020-01-29

 I applied the logic fix to get around the "204" error code. It
 definitely *thinks* it's sending the data. Lists every 5 minute observation
 and says "...published." after each one.  I've done this three times or
 more over the last few days, so it's not a lag issue.

 It's looking like it may well be a WU problem that I'll just have to
 live with.

 Thanks for all your help.


 On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote:
>
> Hey, Ernest.
>
> If you check after some time has passed are the records there?
> There is always a "lag" between the time the records are uploaded and
> when they appear.
> Also, be sure to check via the WU web portal and not some app like
> WunderStation (which they've deprecated).
>
> Anyway, the wunderfixer is doing its job.  What happens on the WU side
> is subject to their many bugs and infrastructure issues.  :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Feb 9, 2020, at 9:59 PM, Ernest Jillson  wrote:
>
> 
> It "looks" like it's working for me, but doesn't.  I get this message:
>
> "No results returned from Weather Underground (perhaps a bad station
> name??).
> Publishing anyway."
>
> It then proceeds to upload all my 5 minute obs.  Only thing is, they
> never show up on wunderground.
>
>
>
> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:
>>
>>
>> Worked for me thanks.
>>
>> Richard
>> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:
>>>
>>> Richard,
>>> It was a long thread.  Here is my workaround for the 204 response
>>> when the request is valid, but there are no records to return:
>>>
>>> $ diff wunderfixer wunderfixer_tk
>>> 407,409c407
>>> < # Valid response, it's just that WU has no records
>>> for the requested date
>>> < # Return an empty list of TimeStamps (as in WU has
>>> no records)
>>> < return {}
>>> ---
>>> > raise IOError("Probably a bad station ID or
>>> invalid date")
>>>
>>> Or if the line numbers don't match yours, it looks like this in
>>> context:
>>>
>>> if hasattr(response, 'code') and response.code != 200:
>>> if response.code == 204:
>>> # Valid response, it's just that WU has no records
>>> for the requested date
>>> # Return an empty list of TimeStamps (as in WU has
>>> no records)
>>> return {}
>>> else:
>>> raise IOError("Bad response code returned: %d" %
>>> response.code)
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>>
>>> On Feb 9, 2020, at 12:40 PM, Richard G  wrote:
>>>
>>> 
>>> I had an outage of a week where no data was uploaded to
>>> wunderground. I discovered all the posts about the change of API etc. so
>>> pulled down the development branch. This version with the api_key 
>>> allowed
>>> me to fix data on partial days i.e. when there was some data but on days
>>> where there is no data at all then it fails
>>>
>>> Using database binding 'wx_binding', which is bound to database
>>> 'archive_sqlite'
>>>
>>> Weather Underground Station:   INORFOLK**
>>>
>>> Date to check: 2020-02-07
>>>
>>> Number of archive records: 288
>>>
>>> Could not get Weather Underground data.
>>>
>>> Reason: Probably a ba

Re: [weewx-user] Wunderfixer (Development Version)

[Thomas Keffer]

That doesn't surprise me. Unfortunately, there is really nothing we can do
about it. 😕

On Mon, Feb 10, 2020 at 11:28 AM Ernest Jillson  wrote:

> I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and
> as before, it says it's doing everything it's supposed to do. So far, after
> 5 minutes, nothing on weather underground. I'll keep checking.
>
>
>
> On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:
>>
>> Could you try the present version of wunderfixer? I just patched it this
>> morning.
>>
>> On Mon, Feb 10, 2020 at 6:50 AM Ernest Jillson  wrote:
>>
>>> Checking here:
>>> https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily
>>>
>>> I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin
>>> folder.  My commands, minus my api key, were:
>>>
>>> cd /home/pi/weewx4/weewx-4.0.0b11/bin
>>> ./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key"
>>> --date=2020-01-29
>>>
>>> I applied the logic fix to get around the "204" error code. It
>>> definitely *thinks* it's sending the data. Lists every 5 minute observation
>>> and says "...published." after each one.  I've done this three times or
>>> more over the last few days, so it's not a lag issue.
>>>
>>> It's looking like it may well be a WU problem that I'll just have to
>>> live with.
>>>
>>> Thanks for all your help.
>>>
>>>
>>> On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote:

 Hey, Ernest.

 If you check after some time has passed are the records there?
 There is always a "lag" between the time the records are uploaded and
 when they appear.
 Also, be sure to check via the WU web portal and not some app like
 WunderStation (which they've deprecated).

 Anyway, the wunderfixer is doing its job.  What happens on the WU side
 is subject to their many bugs and infrastructure issues.  :-/

 Regards,
 \Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPad)

 On Feb 9, 2020, at 9:59 PM, Ernest Jillson  wrote:

 
 It "looks" like it's working for me, but doesn't.  I get this message:

 "No results returned from Weather Underground (perhaps a bad station
 name??).
 Publishing anyway."

 It then proceeds to upload all my 5 minute obs.  Only thing is, they
 never show up on wunderground.



 On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:
>
>
> Worked for me thanks.
>
> Richard
> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:
>>
>> Richard,
>> It was a long thread.  Here is my workaround for the 204 response
>> when the request is valid, but there are no records to return:
>>
>> $ diff wunderfixer wunderfixer_tk
>> 407,409c407
>> < # Valid response, it's just that WU has no records
>> for the requested date
>> < # Return an empty list of TimeStamps (as in WU has
>> no records)
>> < return {}
>> ---
>> > raise IOError("Probably a bad station ID or invalid
>> date")
>>
>> Or if the line numbers don't match yours, it looks like this in
>> context:
>>
>> if hasattr(response, 'code') and response.code != 200:
>> if response.code == 204:
>> # Valid response, it's just that WU has no records
>> for the requested date
>> # Return an empty list of TimeStamps (as in WU has no
>> records)
>> return {}
>> else:
>> raise IOError("Bad response code returned: %d" %
>> response.code)
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>
>> On Feb 9, 2020, at 12:40 PM, Richard G  wrote:
>>
>> 
>> I had an outage of a week where no data was uploaded to wunderground.
>> I discovered all the posts about the change of API etc. so pulled down 
>> the
>> development branch. This version with the api_key allowed me to fix data 
>> on
>> partial days i.e. when there was some data but on days where there is no
>> data at all then it fails
>>
>> Using database binding 'wx_binding', which is bound to database
>> 'archive_sqlite'
>>
>> Weather Underground Station:   INORFOLK**
>>
>> Date to check: 2020-02-07
>>
>> Number of archive records: 288
>>
>> Could not get Weather Underground data.
>>
>> Reason: Probably a bad station ID or invalid date
>>
>> Exiting.
>>
>> The message "could not get Weather Underground data" is correct as
>> there isn't any for that day, but it then needs to upload so there is.
>> Looks like a bug but I thought I would check before reporting.
>>
>> Thanks
>>
>>
>> Richard
>>
>> --
>> You received 

[weewx-user] Re: Summaries customization: adding inside Temp and humidity

[Hervé Bouché]

Thanks for your answer.
When writing "they do not show up in the report until there are actual 
data", which "report" are you talking about? The "real-time" display 
through the skin or the "summary"?
In fact i would like this data to be in the "summary", that is  the 
home/weewx/public_html/NOAA/NOAA-/MM.txt files, as I already 
sucessfully get this data in the skin (wether using Seasons or NeoWX)

Hervé
 

-- 
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/e475dea1-544a-4220-ae12-971cd7521018%40googlegroups.com.

[weewx-user] Re: Summaries customization: adding inside Temp and humidity

[mwall]

On Monday, February 10, 2020 at 12:57:49 PM UTC-5, Hervé Bouché wrote:
>
> The only thing missing and necessary to me would be to add inside 
> temperature and humidity data (as well as their respective min/max/average, 
> etc... data) in the summaries.
>

the inside temperature and humidity are already included in the seasons 
skin.  however, like many other observations (UV, solar radiation, etc) 
they do not show up in the report until there are actual data.

you can easily extend the schema to support any number of sensors - details 
are in the weewx customization guide

finally, weewx4 includes an extended schema so most people will not have to 
extend the schema unless they have a lot of extra sensors (more than 8 
temperature/humidity sensors, 4 soil/moisture sensors).

m 

-- 
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/cef51604-4d6e-4016-8cf1-f0fc83484ac6%40googlegroups.com.

Re: [weewx-user] Wunderfixer (Development Version)

[Ernest Jillson]

I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and as 
before, it says it's doing everything it's supposed to do. So far, after 5 
minutes, nothing on weather underground. I'll keep checking.
 


On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:
>
> Could you try the present version of wunderfixer? I just patched it this 
> morning.
>
> On Mon, Feb 10, 2020 at 6:50 AM Ernest Jillson  > wrote:
>
>> Checking here: 
>> https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily
>>  
>> I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin 
>> folder.  My commands, minus my api key, were:
>>  
>> cd /home/pi/weewx4/weewx-4.0.0b11/bin
>> ./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key" 
>> --date=2020-01-29
>>  
>> I applied the logic fix to get around the "204" error code. It definitely 
>> *thinks* it's sending the data. Lists every 5 minute observation and says 
>> "...published." after each one.  I've done this three times or more over 
>> the last few days, so it's not a lag issue.
>>  
>> It's looking like it may well be a WU problem that I'll just have to live 
>> with.  
>>  
>> Thanks for all your help.
>>
>>
>> On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote:
>>>
>>> Hey, Ernest.
>>>
>>> If you check after some time has passed are the records there?
>>> There is always a "lag" between the time the records are uploaded and 
>>> when they appear.
>>> Also, be sure to check via the WU web portal and not some app like 
>>> WunderStation (which they've deprecated).
>>>
>>> Anyway, the wunderfixer is doing its job.  What happens on the WU side 
>>> is subject to their many bugs and infrastructure issues.  :-/
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad)
>>>
>>> On Feb 9, 2020, at 9:59 PM, Ernest Jillson  wrote:
>>>
>>> 
>>> It "looks" like it's working for me, but doesn't.  I get this message:
>>>  
>>> "No results returned from Weather Underground (perhaps a bad station 
>>> name??).
>>> Publishing anyway."
>>>  
>>> It then proceeds to upload all my 5 minute obs.  Only thing is, they 
>>> never show up on wunderground.
>>>  
>>>
>>>
>>> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:


 Worked for me thanks.

 Richard
 On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:
>
> Richard,
> It was a long thread.  Here is my workaround for the 204 response 
> when the request is valid, but there are no records to return:
>
> $ diff wunderfixer wunderfixer_tk
> 407,409c407
> < # Valid response, it's just that WU has no records 
> for the requested date
> < # Return an empty list of TimeStamps (as in WU has 
> no records)
> < return {}
> ---
> > raise IOError("Probably a bad station ID or invalid 
> date")
>
> Or if the line numbers don't match yours, it looks like this in 
> context:
>
> if hasattr(response, 'code') and response.code != 200:
> if response.code == 204:
> # Valid response, it's just that WU has no records for 
> the requested date
> # Return an empty list of TimeStamps (as in WU has no 
> records)
> return {}
> else:
> raise IOError("Bad response code returned: %d" % 
> response.code)
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPhone)
>
> On Feb 9, 2020, at 12:40 PM, Richard G  wrote:
>
> 
> I had an outage of a week where no data was uploaded to wunderground. 
> I discovered all the posts about the change of API etc. so pulled down 
> the 
> development branch. This version with the api_key allowed me to fix data 
> on 
> partial days i.e. when there was some data but on days where there is no 
> data at all then it fails
>
> Using database binding 'wx_binding', which is bound to database 
> 'archive_sqlite'
>
> Weather Underground Station:   INORFOLK**
>
> Date to check: 2020-02-07
>
> Number of archive records: 288
>
> Could not get Weather Underground data.
>
> Reason: Probably a bad station ID or invalid date
>
> Exiting.
>
> The message "could not get Weather Underground data" is correct as 
> there isn't any for that day, but it then needs to upload so there is. 
> Looks like a bug but I thought I would check before reporting.
>
> Thanks
>
>
> Richard
>
> -- 
> 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...@googlegroups.com.
> To view this discussion o

[weewx-user] Re: Wind gust speed differences.

[Ton Karsten]

Thank you for explaining.

Op maandag 10 februari 2020 10:10:56 UTC+1 schreef Ton Karsten:
>
> I note that there is a difference between the speed generated on the Weewx 
> website and the speed specified on the WU website and the WOW website data. 
> Is there an explanation for how this is possible and how to solve it?
>
> Regards,
> Ton
>

-- 
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/f6b14bae-6708-442e-8771-e253f4ebbe29%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Olivier Guyotot]

I haven't touched this in a while (it's just running on its own), my memory 
is a bit fuzzy... It will take time for me to properly remember everything.

That being said, there are 2 major things to check:
1. that your station is indeed working like a WS3000.
2. what is the correct configuration to use.

Let's start with 2.

In your case, the first thing to check is if you can use the default or if 
you need to update the vendor_id and product_id.

Just run 
lsusb
on your raspberry and please post the output 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/e83cb156-c184-4298-8fb5-7364e91e2576%40googlegroups.com.

Re: [weewx-user] Issue or misunderstanding with $latest tag ? (and one or two question related to database management)

[Thomas Keffer]

One option would be to put this in [StdCalibrate]

[StdCalibrate]
  [[Corrections]]
windSpeed = 0 if windSpeed is None else windSpeed

That will actually save the value 0 (zero) in your database.

Another option, not so drastic, is to interpret None as zero in your
templates. Instead of

The current windspeed is $current.windSpeed

use

The current windspeed is $current.windspeed.format(None_string="0")

-tk

On Mon, Feb 10, 2020 at 9:58 AM wysiwyg  wrote:

> Hello Thomas,
> Thanks for clarifying $latest tag, now I understand!
>
> Regarding the 15min... Well, I'm happy with 5min interval :D. It's a good
> trade off to keep database reasonable but with reactivity to capture short
> events (like a thunderstorm rain in my place with very high rainrate for a
> few minutes then slow down) Or to have shorter wait when debugging :-).
>
> But some data does not have anything interesting to show every 5min: like
> when there's no wind or no rain, reporting 0,0,0...for hours or days...
> That's why I tried this trick on my sensor, to save battery.
>
> Anyway, if my battery can deal with it, I can switch all to 5min interval
> (whatever there's wind or not). I have to do some experiments.
>
> --
> 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/70e582bd-8e1a-49c3-ba5a-5ad02249b643%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/CAPq0zEDrUVfkQoFmrFhP1m_LzUkYB34Ydk_a28bq4ikxT2YTSg%40mail.gmail.com.

Re: [weewx-user] Issue or misunderstanding with $latest tag ? (and one or two question related to database management)

[wysiwyg]

Hello Thomas,
Thanks for clarifying $latest tag, now I understand!

Regarding the 15min... Well, I'm happy with 5min interval :D. It's a good trade 
off to keep database reasonable but with reactivity to capture short events 
(like a thunderstorm rain in my place with very high rainrate for a few minutes 
then slow down) Or to have shorter wait when debugging :-).

But some data does not have anything interesting to show every 5min: like when 
there's no wind or no rain, reporting 0,0,0...for hours or days... 
That's why I tried this trick on my sensor, to save battery. 

Anyway, if my battery can deal with it, I can switch all to 5min interval 
(whatever there's wind or not). I have to do some experiments. 

-- 
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/70e582bd-8e1a-49c3-ba5a-5ad02249b643%40googlegroups.com.

[weewx-user] Summaries customization: adding inside Temp and humidity

[Hervé Bouché]

Hello, 
I am considering installing a weather station at my home and accessing data 
via Weewx.
I have already tried Weewx in simulator mode and it looks great to me.
The only thing missing and necessary to me would be to add inside 
temperature and humidity data (as well as their respective min/max/average, 
etc... data) in the summaries.
This is really necessary to me and I will not buy any weather station if 
this is not possible.
Will probably get a Oregon Scientific WMR300.

Is it possible to add such data to monthly and yearly summaries...*even for 
a newby as I am...* or is this a touchy process?

Many thanks,

Hervé

-- 
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/5a6b593b-64e0-4f90-86a9-e0812e49f5c1%40googlegroups.com.

Re: [weewx-user] Re: Pyehpem and International Space Station

[Kevin Davis]

Very cool.  Thanks for the input.   Certainly helps me to see a working
example!

On Mon, Feb 10, 2020 at 9:40 AM Walter Smith  wrote:

> Doing something very similar.  Cron job at midnight, Python script to
> format a list of stuff from Skyfield I want to display in my template.
> Prefix the list with a "#set global" line:
>
> with open('skyprint2A.txt','w') as f3:
>f3.write('#set global $skytext2 = ')
>json.dump(l_out_lines_txt, f3)
>
> which gives a file containing:
>
> #set global $skytext2 = [["Mon Feb 10", "06:57 AM", "Sun Rises 01:08
> earlier Length of Day 10:30:46 02:19 longer"], ["Mon Feb 10", "07:41 AM",
> "Mercury Rises  52% Illuminated"], ["Mon Feb 10", "08:08 AM", "Moon Sets"],
> ["Mon Feb 10", "08:42 AM", "Venus Rises  70% Illuminated"], ["Mon Feb 10",
> "05:28 PM", "Sun Sets 01:11 later"], ["Mon Feb 10", "07:01 PM", "Mercury
> Sets"], ["Mon Feb 10", "07:20 PM", "Moon Rises  95% Illuminated"], ["Mon
> Feb 10", "08:59 PM", "Venus Sets"], ["Tue Feb 11", "06:56 AM", "Sun Rises
> 01:10 earlier Length of Day 10:33:07 02:21 longer"], ["Tue Feb 11", "07:38
> AM", "Mercury Rises  47% Illuminated"], ["Tue Feb 11", "08:41 AM", "Venus
> Rises  70% Illuminated"], ["Tue Feb 11", "08:43 AM", "Moon Sets"], ["Tue
> Feb 11", "05:29 PM", "Sun Sets 01:11 later"], ["Tue Feb 11", "07:02 PM",
> "Mercury Sets"], ["Tue Feb 11", "08:34 PM", "Moon Rises  89% Illuminated"],
> ["Tue Feb 11", "09:01 PM", "Venus Sets"], ["Sat Feb 15", "04:17 PM", "Moon
> Phase Last Quarter"], ["Thu Mar 19", "10:49 PM", "Vernal Equinox"]]
>
> then in my template:
>
> #include "skyprint2A.txt"
>
> Sky Events
>   
>  
> Date
> Time
> Event
>  
>  #for $seq1 in $skytext2
> 
>$seq1[0]
>$seq1[1]
>$seq1[2]
> 
>  #end for
>   
>
> --
> 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/7e38d3ef-7a1c-4c6b-973a-b877ff72dc56%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/CAHiQ_B0Y3WfcX%2BeT6Gt%2BbCr4W9-%3DftYTV7YSLphrvmDfWpLVzw%40mail.gmail.com.

[weewx-user] Re: Pyehpem and International Space Station

[Walter Smith]

Doing something very similar.  Cron job at midnight, Python script to 
format a list of stuff from Skyfield I want to display in my template.  
Prefix the list with a "#set global" line:

with open('skyprint2A.txt','w') as f3:
   f3.write('#set global $skytext2 = ')
   json.dump(l_out_lines_txt, f3)

which gives a file containing:

#set global $skytext2 = [["Mon Feb 10", "06:57 AM", "Sun Rises 01:08 
earlier Length of Day 10:30:46 02:19 longer"], ["Mon Feb 10", "07:41 AM", 
"Mercury Rises  52% Illuminated"], ["Mon Feb 10", "08:08 AM", "Moon Sets"], 
["Mon Feb 10", "08:42 AM", "Venus Rises  70% Illuminated"], ["Mon Feb 10", 
"05:28 PM", "Sun Sets 01:11 later"], ["Mon Feb 10", "07:01 PM", "Mercury 
Sets"], ["Mon Feb 10", "07:20 PM", "Moon Rises  95% Illuminated"], ["Mon 
Feb 10", "08:59 PM", "Venus Sets"], ["Tue Feb 11", "06:56 AM", "Sun Rises 
01:10 earlier Length of Day 10:33:07 02:21 longer"], ["Tue Feb 11", "07:38 
AM", "Mercury Rises  47% Illuminated"], ["Tue Feb 11", "08:41 AM", "Venus 
Rises  70% Illuminated"], ["Tue Feb 11", "08:43 AM", "Moon Sets"], ["Tue 
Feb 11", "05:29 PM", "Sun Sets 01:11 later"], ["Tue Feb 11", "07:02 PM", 
"Mercury Sets"], ["Tue Feb 11", "08:34 PM", "Moon Rises  89% Illuminated"], 
["Tue Feb 11", "09:01 PM", "Venus Sets"], ["Sat Feb 15", "04:17 PM", "Moon 
Phase Last Quarter"], ["Thu Mar 19", "10:49 PM", "Vernal Equinox"]]

then in my template:

#include "skyprint2A.txt"
  
Sky Events
  
 
Date
Time
Event
 
 #for $seq1 in $skytext2

   $seq1[0]
   $seq1[1]
   $seq1[2]

 #end for
  

-- 
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/7e38d3ef-7a1c-4c6b-973a-b877ff72dc56%40googlegroups.com.

Re: [weewx-user] Issue or misunderstanding with $latest tag ? (and one or two question related to database management)

[Thomas Keffer]

$latest is the last archive record in the database. So, $latest.windSpeed
is the last wind speed in the database, whether null or not.

Unfortunately, there is no tag meaning "last non-null" value. You'd have to
write a search list extension.

But, I find the semantics of what you're trying to accomplish a little
hazy. If you're satisfied with 15-minute old data, why not just sample
every 15 minutes?

To answer your other question: the presence of null values will not affect
averages.

-tk

On Mon, Feb 10, 2020 at 9:01 AM wysiwyg  wrote:

> Hi There!
>
> I am working on my wind sensor currently, so far I have tuned my data to
> be emitted the following way (My weewx record interval is 5min):
>
> *When there is some wind:*
> Every five 5min, sensor will emit average windspeed/dir over last 5
> minutes and  max windgust/gustdir observed on a 10sec interval during the
> last 5 minutes.
> I tuned this way because I want to make sure weewx will record any extreme
> windgust I measure.
> If I send more than 1 sample of windgust in 5min period, weewx will
> average them to build its database record. (as far as I understood)
>
> *When there's no wind:* my sensor will emit a zero speed value every
> 15min to save battery, so it will miss ~2 database record over 3. I guess
> it's not a big deal as there's no wind.
> While writing this, I wonder if those missing "0" speed samples can affect
> some calculations, like average wind ?
>
>
>
> Anyway: due to those timings, It happens that I have no wind data on
> current database record: meaning $current.windSpeed will sporadically give
> N/A value (more often when there's no wind).
> I was expecting $latest.windSpeed to give me the last value recorded (in
> my situation 5-15min ago).
> But apparently, it's not working this way ?
> Is there a workaround possible ?
>
> Best regards,
> Frederic
>
>
>
>
>
>
> --
> 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/f5ac6ea6-caff-48e6-86de-1aa039f00541%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/CAPq0zEB6Cs%3DT1zNW_EwSTZqn1gmR-AuDFQO6EkX-7d0d5yBjcw%40mail.gmail.com.

[weewx-user] Issue or misunderstanding with $latest tag ? (and one or two question related to database management)

[wysiwyg]

Hi There!

I am working on my wind sensor currently, so far I have tuned my data to be 
emitted the following way (My weewx record interval is 5min):

*When there is some wind:*
Every five 5min, sensor will emit average windspeed/dir over last 5 minutes 
and  max windgust/gustdir observed on a 10sec interval during the last 5 
minutes.
I tuned this way because I want to make sure weewx will record any extreme 
windgust I measure.
If I send more than 1 sample of windgust in 5min period, weewx will average 
them to build its database record. (as far as I understood)

*When there's no wind:* my sensor will emit a zero speed value every 15min 
to save battery, so it will miss ~2 database record over 3. I guess it's 
not a big deal as there's no wind.
While writing this, I wonder if those missing "0" speed samples can affect 
some calculations, like average wind ?



Anyway: due to those timings, It happens that I have no wind data on 
current database record: meaning $current.windSpeed will sporadically give 
N/A value (more often when there's no wind).
I was expecting $latest.windSpeed to give me the last value recorded (in my 
situation 5-15min ago).
But apparently, it's not working this way ?  
Is there a workaround possible ?

Best regards,
Frederic






-- 
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/f5ac6ea6-caff-48e6-86de-1aa039f00541%40googlegroups.com.

[weewx-user] Re: wanted: users with ecowitt gw1000 wifi bridge

[Jim Y]

So, I am just starting to get things going, I have the gw1000, a rain 
gauge, external temp, and 2 soil moisture meters.  

Here's the output from the python command:
raw data: 
PASSKEY=&stationtype=GW1000B_V1.5.6&dateutc=2020-02-10+16:37:37&tempinf=71.8&humidityin=37&baromrelin=30.383&baromabsin=30.383&tempf=37.9&humidity=99&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=5.209&yearlyrainin=5.209&totalrainin=5.209&soilmoisture1=38&soilmoisture2=53&wh40batt=1.6&wh26batt=0&soilbatt1=1.7&soilbatt2=1.8&freq=915M&model=GW1000_Pro
raw packet: {'humidity_in': 37.0, 'soil_battery_1': 1.7, 'soil_battery_2': 
1.8, 'rain_total': 5.209, 'humidity_out': 99.0, 'temperature_in': 71.8, 
'rain': None, 'wh26_battery': 0.0, 'pressure': 30.383, 'temperature_out': 
37.9, 'soil_moisture_1': 38.0, 'soil_moisture_2': 53.0, 'dateTime': 
1581352657, 'rain_rate': 0.0, 'usUnits': 1}
mapped packet: {'pressure': 30.383, 'outHumidity': 99.0, 'rain': None, 
'dateTime': 1581352657, 'outTemp': 37.9, 'soilMoist1': 38.0, 'inHumidity': 
37.0, 'inTemp': 71.8, 'soilMoist2': 53.0, 'rainRate': 0.0, 'usUnits': 1}

When I open the local weewx website, I have the main "expected" data (temps 
and rain info), but nothing from the soil sensors.

When I run a systemctl status weewx, I get this:
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (running) since Mon 2020-02-10 08:48:13 PST; 2min 37s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 19836 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 20142 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
Tasks: 2 (limit: 4915)
   CGroup: /system.slice/weewx.service
   └─20188 python /usr/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Feb 10 08:48:13 hass weewx[20188]: restx: PWSweather: Posting not enabled.
Feb 10 08:48:13 hass weewx[20188]: restx: CWOP: Posting not enabled.
Feb 10 08:48:13 hass weewx[20188]: restx: WOW: Posting not enabled.
Feb 10 08:48:13 hass weewx[20188]: restx: AWEKAS: Posting not enabled.
Feb 10 08:48:13 hass weewx[20188]: engine: Starting up weewx version 3.9.2
Feb 10 08:48:13 hass weewx[20188]: engine: Starting main packet loop.
Feb 10 08:48:49 hass weewx[20188]: interceptor: MainThread: using 
'totalrainin' for rain_total
Feb 10 08:48:49 hass weewx[20188]: interceptor: MainThread: unrecognized 
parameter wh40batt=1.6
Feb 10 08:48:49 hass weewx[20188]: interceptor: MainThread: skipping rain 
measurement of 5.209: no last rain
Feb 10 08:49:50 hass weewx[20188]: interceptor: MainThread: unrecognized 
parameter wh40batt=1.6

I'm not especially worried about the missing battery level on the rain 
gauge, but can you point me where I need to go to get the soil moisture 
meters visible on the front end?  I've read so many forum posts at this 
point my eyes are crossed and I'm a bit lost about what config files I 
should be editing...


On Sunday, December 29, 2019 at 8:59:56 PM UTC-8, mwall wrote:
>
> the weewx-interceptor driver has been updated with explicit support for 
> the gw1000 wifi bridge, as well as support for weewx4/python3.
>
> instructions are at the weewx wiki:
>
> https://github.com/weewx/weewx/wiki/gw1000-recipe
>
> i would especially appreciate feedback from anyone with full sensor arrays 
> (wind, rain, uv), particulate sensors, soil moisture sensors, and any other 
> extended sensors offered by ecowitt.
>
> although the interceptor will now understand the extended weather 
> underground protocol, the 'fineoffset-bridge' type uses the ecowitt 
> protocol and a direct-to-weewx configuration (no dns hijack or sniffing or 
> other shenanigans required).  it does require a recent firmware on the 
> gw1000 (testing with 1.5.5)
>
> m
>  
>

-- 
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/d7275475-c7c4-4964-9ca5-8f09ca49f511%40googlegroups.com.

Re: [weewx-user] Wunderfixer (Development Version)

[Thomas Keffer]

Could you try the present version of wunderfixer? I just patched it this
morning.

On Mon, Feb 10, 2020 at 6:50 AM Ernest Jillson  wrote:

> Checking here:
> https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily
>
> I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin
> folder.  My commands, minus my api key, were:
>
> cd /home/pi/weewx4/weewx-4.0.0b11/bin
> ./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key"
> --date=2020-01-29
>
> I applied the logic fix to get around the "204" error code. It definitely
> *thinks* it's sending the data. Lists every 5 minute observation and says
> "...published." after each one.  I've done this three times or more over
> the last few days, so it's not a lag issue.
>
> It's looking like it may well be a WU problem that I'll just have to live
> with.
>
> Thanks for all your help.
>
>
> On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote:
>>
>> Hey, Ernest.
>>
>> If you check after some time has passed are the records there?
>> There is always a "lag" between the time the records are uploaded and
>> when they appear.
>> Also, be sure to check via the WU web portal and not some app like
>> WunderStation (which they've deprecated).
>>
>> Anyway, the wunderfixer is doing its job.  What happens on the WU side is
>> subject to their many bugs and infrastructure issues.  :-/
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad)
>>
>> On Feb 9, 2020, at 9:59 PM, Ernest Jillson  wrote:
>>
>> 
>> It "looks" like it's working for me, but doesn't.  I get this message:
>>
>> "No results returned from Weather Underground (perhaps a bad station
>> name??).
>> Publishing anyway."
>>
>> It then proceeds to upload all my 5 minute obs.  Only thing is, they
>> never show up on wunderground.
>>
>>
>>
>> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:
>>>
>>>
>>> Worked for me thanks.
>>>
>>> Richard
>>> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:

 Richard,
 It was a long thread.  Here is my workaround for the 204 response when
 the request is valid, but there are no records to return:

 $ diff wunderfixer wunderfixer_tk
 407,409c407
 < # Valid response, it's just that WU has no records
 for the requested date
 < # Return an empty list of TimeStamps (as in WU has no
 records)
 < return {}
 ---
 > raise IOError("Probably a bad station ID or invalid
 date")

 Or if the line numbers don't match yours, it looks like this in context:

 if hasattr(response, 'code') and response.code != 200:
 if response.code == 204:
 # Valid response, it's just that WU has no records for
 the requested date
 # Return an empty list of TimeStamps (as in WU has no
 records)
 return {}
 else:
 raise IOError("Bad response code returned: %d" %
 response.code)

 Regards,
 \Leon
 --
 Leon Shaner :: Dearborn, Michigan (iPhone)

 On Feb 9, 2020, at 12:40 PM, Richard G  wrote:

 
 I had an outage of a week where no data was uploaded to wunderground. I
 discovered all the posts about the change of API etc. so pulled down the
 development branch. This version with the api_key allowed me to fix data on
 partial days i.e. when there was some data but on days where there is no
 data at all then it fails

 Using database binding 'wx_binding', which is bound to database
 'archive_sqlite'

 Weather Underground Station:   INORFOLK**

 Date to check: 2020-02-07

 Number of archive records: 288

 Could not get Weather Underground data.

 Reason: Probably a bad station ID or invalid date

 Exiting.

 The message "could not get Weather Underground data" is correct as
 there isn't any for that day, but it then needs to upload so there is.
 Looks like a bug but I thought I would check before reporting.

 Thanks


 Richard

 --
 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...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%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...@googlegroups.com.
>> 

Re: [weewx-user] Uploading missing data to Weather Underground

[Thomas Keffer]

I've made the changes in commit 0658f05

.

With a response code of 204, wunderfixer now assumes a good station with no
data, instead of assuming a bad station ID.

Wish there was some way of telling them apart, but there isn't.

-tk

On Sun, Feb 9, 2020 at 11:46 AM iain MacDonnell  wrote:

>
>
> On Thursday, February 6, 2020 at 2:31:12 PM UTC-8, gjr80 wrote:
>>
>> OK, that explains the api_key issue. 3.9.2 (the latest release version)
>> does not use api_key, hence the error you receive. Subsequent to the
>> 3.9.2 release there have been numerous wunderfixer commits in an attempt to
>> have wunderfixer work properly given the changes/chaos at WU. Somewhere in
>> these commits api_key was introduced. WeeWX 4.0 will include the
>> wunderfixer with all of these commits, I have not kept across
>> wunderfixer/WU changes so i will let others advise on what wunderfixer
>> version to use with 3.9.2.
>>
>
> FWIW, I was able to use wunderfixer from the master branch, with the
> workaround from
> https://groups.google.com/forum/m/#!topic/weewx-user/P_omYBcdrFY . I just
> cloned the github repo, applied the workaround, and ran ./wunderfixer
> (after adding my api_key to my v3.9.2 weewx.conf)
>
> ~iain
>
>
>
> --
> 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/8ded3075-68ee-4099-be2b-11e2519fddef%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/CAPq0zEDyLFRvhGWuh2BkMmVDpcoV80%3DS3oVJEisTNqGKLhN1bw%40mail.gmail.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Dan Blanchard]

Agreed.  If this is the case, can I configure weewx to show a different 
pressure?  If so, how do I do that?

On Monday, February 10, 2020 at 6:00:07 AM UTC-8, ln77 wrote:
>
> 33” is clearly too high for the barometric pressure. It is within spitting 
> distance of what you would get if the pressure is corrected for your 2300’ 
> elevation twice. Maybe the station is giving the corrected pressure but 
> weewx is configured to think it’s the uncorrected pressure?
>
>   -Les
>
>
> On Feb 9, 2020, at 6:00 PM, Dan Blanchard  > wrote:
>
> 
> OK, let me absorb this information a bit and see what I can figure out.
>
> On Sunday, February 9, 2020 at 4:56:30 PM UTC-8, gjr80 wrote:
>>
>> On Monday, 10 February 2020 10:35:37 UTC+10, Dan Blanchard wrote:
>>>
>>> My station labels it as 'Pressure inHg' which is currently 30.30 and 
>>> matches others in the area.
>>>
>>
>> I presume you mean the station display. The use of 'Pressure' is 
>> consistent with it being station pressure but it could mean anything, would 
>> not be the first time weather station hardware manufacturers have been 
>> vague, liberal with the truth or just wrong.
>>
>> So I am a bit confused between what you said about barometric pressure 
>>> vs. raw pressure.
>>>
>>
>> Did you read the wiki article about the three different pressures that 
>> WeeWX uses? Could you explain what it is that confuses you?
>>  
>>
>>> Ultimately, is there a fix for me?  Can I make some kind of adjustment?
>>>
>>
>> Not sure what you are trying to fix, if the issue is that you want 
>> everything to display the same value then sure there are changes you can 
>> make. Since you can't change what the station hardware displays you need to 
>> change what WeeWX and WU displays. Changing what WeeWX displays is easy, as 
>> I said its a simple change to a template. Changing what WU displays is more 
>> complex and involves changing the WeeWX WU uploader to upload WeeWX field 
>> pressure instead of field barometer. If you go down this path you need 
>> to accept a few things. Firstly, your WU data will be inaccurate (it 
>> expects barometric pressure and you will be sending it station pressure). 
>> Secondly, your changes to the template will be safe but your changes to the 
>> WU uploader will likely be overwritten each time you upgrade WeeWX.
>>
>> I am not familiar with the WS-2813 so do not know if there is any ability 
>> to change what pressure it displays, I suspect there will not be a means 
>> though.
>>
>> At the end of the day you might be displaying a different value to a lot 
>> of other folks, doesn't make them right and you wrong though.
>>
>> Gary
>>
>>
>>
>>
>>
>>
>>> On Sunday, February 9, 2020 at 4:29:42 PM UTC-8, gjr80 wrote:

 Slightly, but still apples and oranges. By default WeeWX displays 
 barometric pressure so WeeWX and WU displaying the same 'pressure' is 
 expected behaviour. The 'pressure' displayed by WeeWX can be changed with 
 a 
 simple change to a template, unfortunately what cannot be changed is what 
 WU expects and (usually) what your station hardware displays.

 Gary

>>> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/c43f41d0-2280-4c62-b425-4ba19baa3f21%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/a4cc5af3-e7e1-4898-a458-0916dd167e09%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

[Ton vanN]

This thread makes interesting reading.

Have a Misol console type HP3001 (which probably is a next version/clone of 
HP3000), and assume therefore that the discussed HP3000/WS3000-driver will 
be applicable.
5 Sensors attached.
At processor-side have a configuration with Raspbian Buster on 
Raspberry_Zero_W
Installed ss described by Jack Stromberg at 
https://jackstromberg.com/2018/06/setting-up-weewx-with-a-raspberry-pi/
Lacking a better choice set WeeWX for 'Simulator'
Seems to work.

Next step is installation of the WS3000-driver, reconfig with that driver 
and then restart incl. de USB-interface to the Console of WS3000/HP300x
Have read the attachment to previous message, but NOOB needing simple 
instructions.

*Any hints for the next steps?*

Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>
> Here is an updated version of the driver, including:
> - the fix for sub-zero temperatures
> - improved error handling/retry (something that wasn't working properly 
> before)
> - the usb timeout is now a configuration setting
> - additional comments
>
> It probably won't fix the root cause of the 'crash' issue, but at least it 
> should now properly retry so the problem might be more transparent. And the 
> error reporting will be more useful to figure out what's wrong should an 
> exception occur.
>

-- 
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/a6439b41-4926-4fc9-915b-bb1319348ac1%40googlegroups.com.

Re: [weewx-user] Re: Weewx 4, any Gotchas to be aware of?

[Robert Anthony Pitera]

Thanks!

On Mon, Feb 10, 2020 at 9:00 AM gjr80  wrote:

> Best place to look is at the change history
>  on Github.
>
> Gary
>
> On Monday, 10 February 2020 23:33:55 UTC+10, Robert Anthony Pitera wrote:
>>
>> Is there a site/page that outlines the changes/features/breaking changes
>> of Weewx 4.x?
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/4tXWndEt9X0/unsubscribe.
> To unsubscribe from this group and all its topics, 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/88ba1565-fb97-4ab4-9ffe-4785fc5fd914%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/CAHh47B0YUHP7%3DUfvHX5dBF7cacpmWqwkWV4LTcYxjvtOC5dbNg%40mail.gmail.com.

Re: [weewx-user] Wunderfixer (Development Version)

[Ernest Jillson]

Checking here: 
https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily
 
I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin 
folder.  My commands, minus my api key, were:
 
cd /home/pi/weewx4/weewx-4.0.0b11/bin
./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key" --date=2020-01-29
 
I applied the logic fix to get around the "204" error code. It definitely 
*thinks* it's sending the data. Lists every 5 minute observation and says 
"...published." after each one.  I've done this three times or more over 
the last few days, so it's not a lag issue.
 
It's looking like it may well be a WU problem that I'll just have to live 
with.  
 
Thanks for all your help.


On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote:
>
> Hey, Ernest.
>
> If you check after some time has passed are the records there?
> There is always a "lag" between the time the records are uploaded and when 
> they appear.
> Also, be sure to check via the WU web portal and not some app like 
> WunderStation (which they've deprecated).
>
> Anyway, the wunderfixer is doing its job.  What happens on the WU side is 
> subject to their many bugs and infrastructure issues.  :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Feb 9, 2020, at 9:59 PM, Ernest Jillson  > wrote:
>
> 
> It "looks" like it's working for me, but doesn't.  I get this message:
>  
> "No results returned from Weather Underground (perhaps a bad station 
> name??).
> Publishing anyway."
>  
> It then proceeds to upload all my 5 minute obs.  Only thing is, they never 
> show up on wunderground.
>  
>
>
> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:
>>
>>
>> Worked for me thanks.
>>
>> Richard
>> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:
>>>
>>> Richard,
>>> It was a long thread.  Here is my workaround for the 204 response when 
>>> the request is valid, but there are no records to return:
>>>
>>> $ diff wunderfixer wunderfixer_tk
>>> 407,409c407
>>> < # Valid response, it's just that WU has no records for 
>>> the requested date
>>> < # Return an empty list of TimeStamps (as in WU has no 
>>> records)
>>> < return {}
>>> ---
>>> > raise IOError("Probably a bad station ID or invalid 
>>> date")
>>>
>>> Or if the line numbers don't match yours, it looks like this in context:
>>>
>>> if hasattr(response, 'code') and response.code != 200:
>>> if response.code == 204:
>>> # Valid response, it's just that WU has no records for 
>>> the requested date
>>> # Return an empty list of TimeStamps (as in WU has no 
>>> records)
>>> return {}
>>> else:
>>> raise IOError("Bad response code returned: %d" % 
>>> response.code)
>>>
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>>
>>> On Feb 9, 2020, at 12:40 PM, Richard G  wrote:
>>>
>>> 
>>> I had an outage of a week where no data was uploaded to wunderground. I 
>>> discovered all the posts about the change of API etc. so pulled down the 
>>> development branch. This version with the api_key allowed me to fix data on 
>>> partial days i.e. when there was some data but on days where there is no 
>>> data at all then it fails
>>>
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'archive_sqlite'
>>>
>>> Weather Underground Station:   INORFOLK**
>>>
>>> Date to check: 2020-02-07
>>>
>>> Number of archive records: 288
>>>
>>> Could not get Weather Underground data.
>>>
>>> Reason: Probably a bad station ID or invalid date
>>>
>>> Exiting.
>>>
>>> The message "could not get Weather Underground data" is correct as there 
>>> isn't any for that day, but it then needs to upload so there is. Looks like 
>>> a bug but I thought I would check before reporting.
>>>
>>> Thanks
>>>
>>>
>>> Richard
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com
>  
> 

Re: [weewx-user] Wunderfixer (Development Version)

[Leon Shaner]

Hey, Ernest.

If you check after some time has passed are the records there?
There is always a "lag" between the time the records are uploaded and when they 
appear.
Also, be sure to check via the WU web portal and not some app like 
WunderStation (which they've deprecated).

Anyway, the wunderfixer is doing its job.  What happens on the WU side is 
subject to their many bugs and infrastructure issues.  :-/

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad)

> On Feb 9, 2020, at 9:59 PM, Ernest Jillson  wrote:
> 
> 
> It "looks" like it's working for me, but doesn't.  I get this message:
>  
> "No results returned from Weather Underground (perhaps a bad station name??).
> Publishing anyway."
>  
> It then proceeds to upload all my 5 minute obs.  Only thing is, they never 
> show up on wunderground.
>  
> 
> 
>> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote:
>> 
>> Worked for me thanks.
>> 
>> Richard
>>> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote:
>>> Richard,
>>> It was a long thread.  Here is my workaround for the 204 response when the 
>>> request is valid, but there are no records to return:
>>> 
>>> $ diff wunderfixer wunderfixer_tk
>>> 407,409c407
>>> < # Valid response, it's just that WU has no records for 
>>> the requested date
>>> < # Return an empty list of TimeStamps (as in WU has no 
>>> records)
>>> < return {}
>>> ---
>>> > raise IOError("Probably a bad station ID or invalid date")
>>> 
>>> Or if the line numbers don't match yours, it looks like this in context:
>>> 
>>> if hasattr(response, 'code') and response.code != 200:
>>> if response.code == 204:
>>> # Valid response, it's just that WU has no records for the 
>>> requested date
>>> # Return an empty list of TimeStamps (as in WU has no 
>>> records)
>>> return {}
>>> else:
>>> raise IOError("Bad response code returned: %d" % 
>>> response.code)
>>> 
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPhone)
>>> 
> On Feb 9, 2020, at 12:40 PM, Richard G  wrote:
> 
 
 I had an outage of a week where no data was uploaded to wunderground. I 
 discovered all the posts about the change of API etc. so pulled down the 
 development branch. This version with the api_key allowed me to fix data 
 on partial days i.e. when there was some data but on days where there is 
 no data at all then it fails
 
 Using database binding 'wx_binding', which is bound to database 
 'archive_sqlite'
 
 Weather Underground Station:   INORFOLK**
 
 Date to check: 2020-02-07
 
 Number of archive records: 288
 
 Could not get Weather Underground data.
 
 Reason: Probably a bad station ID or invalid date
 
 Exiting.
 
 
 The message "could not get Weather Underground data" is correct as there 
 isn't any for that day, but it then needs to upload so there is. Looks 
 like a bug but I thought I would check before reporting.
 
 Thanks
 
 
 Richard
 -- 
 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...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%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/30ac8208-34d8-4b47-a8ac-636151c794c2%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/2417BCC3-A907-4DF6-B374-6CF6DD577657%40isylum.org.

[weewx-user] Re: Weewx 4, any Gotchas to be aware of?

[gjr80]

Best place to look is at the change history 
 on Github.

Gary

On Monday, 10 February 2020 23:33:55 UTC+10, Robert Anthony Pitera wrote:
>
> Is there a site/page that outlines the changes/features/breaking changes 
> of Weewx 4.x?
>
>

-- 
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/88ba1565-fb97-4ab4-9ffe-4785fc5fd914%40googlegroups.com.

Re: [weewx-user] Re: Mismatch Between Hardware and weeWX Data

[Les Niles]

33” is clearly too high for the barometric pressure. It is within spitting 
distance of what you would get if the pressure is corrected for your 2300’ 
elevation twice. Maybe the station is giving the corrected pressure but weewx 
is configured to think it’s the uncorrected pressure?

  -Les


> On Feb 9, 2020, at 6:00 PM, Dan Blanchard  wrote:
> 
> 
> OK, let me absorb this information a bit and see what I can figure out.
> 
>> On Sunday, February 9, 2020 at 4:56:30 PM UTC-8, gjr80 wrote:
>>> On Monday, 10 February 2020 10:35:37 UTC+10, Dan Blanchard wrote:
>>> My station labels it as 'Pressure inHg' which is currently 30.30 and 
>>> matches others in the area.
>> 
>> I presume you mean the station display. The use of 'Pressure' is consistent 
>> with it being station pressure but it could mean anything, would not be the 
>> first time weather station hardware manufacturers have been vague, liberal 
>> with the truth or just wrong.
>> 
>>> So I am a bit confused between what you said about barometric pressure vs. 
>>> raw pressure.
>> 
>> Did you read the wiki article about the three different pressures that WeeWX 
>> uses? Could you explain what it is that confuses you?
>>  
>>> Ultimately, is there a fix for me?  Can I make some kind of adjustment?
>> 
>> Not sure what you are trying to fix, if the issue is that you want 
>> everything to display the same value then sure there are changes you can 
>> make. Since you can't change what the station hardware displays you need to 
>> change what WeeWX and WU displays. Changing what WeeWX displays is easy, as 
>> I said its a simple change to a template. Changing what WU displays is more 
>> complex and involves changing the WeeWX WU uploader to upload WeeWX field 
>> pressure instead of field barometer. If you go down this path you need to 
>> accept a few things. Firstly, your WU data will be inaccurate (it expects 
>> barometric pressure and you will be sending it station pressure). Secondly, 
>> your changes to the template will be safe but your changes to the WU 
>> uploader will likely be overwritten each time you upgrade WeeWX.
>> 
>> I am not familiar with the WS-2813 so do not know if there is any ability to 
>> change what pressure it displays, I suspect there will not be a means though.
>> 
>> At the end of the day you might be displaying a different value to a lot of 
>> other folks, doesn't make them right and you wrong though.
>> 
>> Gary
>> 
>> 
>> 
>> 
>> 
>>> 
 On Sunday, February 9, 2020 at 4:29:42 PM UTC-8, gjr80 wrote:
 Slightly, but still apples and oranges. By default WeeWX displays 
 barometric pressure so WeeWX and WU displaying the same 'pressure' is 
 expected behaviour. The 'pressure' displayed by WeeWX can be changed with 
 a simple change to a template, unfortunately what cannot be changed is 
 what WU expects and (usually) what your station hardware displays.
 
 Gary
> 
> -- 
> 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/c43f41d0-2280-4c62-b425-4ba19baa3f21%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/A88D05B2-5FEF-41D6-99F2-A44DCF47F497%402pi.org.

[weewx-user] Re: Wind gust speed differences.

[gjr80]

There you have it. You have the Seasons skin and the 'wind' data it 
displays is the average wind speed seen over the archive period, it is not 
wind gust. WU will be receiving wind speed data every 2 odd seconds and it 
will be current data, on top of that who knows how WU determines wind gust 
(highest wind speed in last minute, 5 minutes, 10 minutes?). WOW will be 
getting both the average wind speed and the wind gust over the archive 
period but it will only get every third archive record.

I suspect you will not see all three the same very often if at all.

Gary

-- 
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/4af8e560-ea8a-43cc-b555-1c80f1a38938%40googlegroups.com.

Re: [weewx-user] 'ascii' codec can't decode byte 0xc3

[Thomas Keffer]

Skins have been backwards compatible for years and rarely have a problem
with an upgrade. There's no reason why a French skin written for V2.0 back
in 2012 wouldn't work with V4.0.

-tk

On Sun, Feb 9, 2020 at 9:50 AM Vetti52  wrote:

>
>
> Am Samstag, 8. Februar 2020 20:11:52 UTC+1 schrieb mwall:
>>
>> On Saturday, February 8, 2020 at 12:56:29 PM UTC-5, Vetti52 wrote:
>>>
>>> After that I am wondering, if there are attempts to prepare a common
>>> solution for internationalisation. It was not that easy to find all places,
>>> where english expressions had to be replaced. Well, in the Weewx wiki I
>>> found at least three solutions, a french standard skin, niculskin and
>>> Weewx-Weather34, which provide translations, each at its own way.
>>>
>>
>> there is not yet "one true way" for i18n, as you can see from the various
>> skin implementations.  however, l10n is somewhat more standard.
>>
>> the customization guide describes some sustainable approaches:
>>
>> http://weewx.com/docs/customizing.htm#localization
>>
>> some of the fallback/default changes in the weewx 3.9 releases made i18n
>> a bit easier
>>
>> lately i have been using some i18n libraries in javascript to ensure
>> translations between english, korean, and chinese.  it is tedious.  the
>> approaches tend to follow the old gettext approach, but on the plus side
>> there is better support for tense/plurals/etc using string formatting.
>>
>> i guess i would generalize to two approaches:
>>
>> 1) if the skin is tiny, then substitute strings (the gettext approach)
>>
>> 2) if the skin is more than a couple of pages, then create a separate
>> directory for each language.  try to consolidate common code if possible.
>>
>> and of course, if you eliminate words, then you don't have to translate,
>> just localize :)
>>
>> m
>>
>
> Ok, then 1) is evil, according to Thomas and Peter's opinions. Although
> the Weewx skin seems to be tiny, but gettext is scary. At least to me.
> Choice 2) looks close to, what the french skin (and my own) looks like,
> which followed the recipe of
> http://weewx.com/docs/customizing.htm#localization.
> Eliminating words may be simple, but, as we deal with a couple of termini
> technici, I think, it will not work well, to eliminate these words.
>
> So I would prefer 2). However, when looking to the developement of the
> french skin, you see the disadvantage of this kind of personal solutions,
> as soon as a new version of Weewx needs adoptions. Therefore, it would be
> better to build up rules, but not only providing "suggestions for
> localization". It should also include rules what to do, when updating
> Weewx. Maybe i18n should be separated from skins into a weewx.i18n library,
> which serves for labelling all of the present and future skins. Ok, this
> may become hard work, but IMHO is less evil than gettexting.
>
> --
> 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/7fc8dcea-cf8c-43a7-bd33-aa5aac71685d%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/CAPq0zEDSLe6DQ7np5VAAWZYp8TH3RNXvQqcGh4u4jb9bF39YSw%40mail.gmail.com.

[weewx-user] Re: set average readings to use different unit group than instantaneous readings

[gjr80]

On Monday, 10 February 2020 14:00:09 UTC+10, Thomas Carlin wrote:
>
> So there is no simple or easy way to modify it or assign it to a different 
> group in the config as to effect each template without having to touch 
> everything?
>
>
No. The groups are used to set the 'unit group' for an observation, so 
outTemp is typically assigned to group_temperature indicating (to WeeWX) 
that outTemp is a temperature which could be degree_C, degree_F or degree_E. 
You can then assign default formats for each unit, so you could have 
degree_C formatted with one decimal place and degree_F with no decimal 
places. This means you can use shortened tags that do not specify the 
formatting to use, for example $current.outTemp.degree_C would display the 
current outside temperature in C with one decimal place. If you change the 
default format for a given unit it will applies everywhere you use tags (in 
that skin/report) that have implicit formatting, which is most places in 
the Standard and Seasons skins. If you want to step outside this for 
particular fields/tags you need to use explicit formatting such as 
$current.outTemp.degree_C.format(format_string="%.2f") if you want to 
display the current outside temperature in C with two decimal places.

Gary


-- 
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/59fc3633-88d7-4b13-90bd-d0968cdeb601%40googlegroups.com.

[weewx-user] Re: Wind gust speed differences.

[Andrew Milner]

is your windgust weewx generated or provided by the vantage vue?  ie do you 
have sw record generation or hardware?



On Monday, 10 February 2020 15:42:33 UTC+2, Ton Karsten wrote:
>
> yes, everything as standard Weewx
> Weather station: Davis Vantage Vue Wireless
> Yes, use of WU rapid fire
> Website: http://weerstationnibbixwoud.nl/
> WU: https://www.wunderground.com/dashboard/pws/INOORDHO191
> WOW: https://wow.metoffice.gov.uk/observations/details/?site_id=942006001
> It is not exciting or, I was wondering how this is possible?
>
> Ton
>
> Op maandag 10 februari 2020 10:10:56 UTC+1 schreef Ton Karsten:
>>
>> I note that there is a difference between the speed generated on the 
>> Weewx website and the speed specified on the WU website and the WOW website 
>> data. 
>> Is there an explanation for how this is possible and how to solve it?
>>
>> Regards,
>> Ton
>>
>

-- 
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/31094165-d229-465c-ae0a-9ea981f26162%40googlegroups.com.

[weewx-user] Re: Wind gust speed differences.

[Ton Karsten]

yes, everything as standard Weewx
Weather station: Davis Vantage Vue Wireless
Yes, use of WU rapid fire
Website: http://weerstationnibbixwoud.nl/
WU: https://www.wunderground.com/dashboard/pws/INOORDHO191
WOW: https://wow.metoffice.gov.uk/observations/details/?site_id=942006001
It is not exciting or, I was wondering how this is possible?

Ton

Op maandag 10 februari 2020 10:10:56 UTC+1 schreef Ton Karsten:
>
> I note that there is a difference between the speed generated on the Weewx 
> website and the speed specified on the WU website and the WOW website data. 
> Is there an explanation for how this is possible and how to solve it?
>
> Regards,
> Ton
>

-- 
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/00c24e84-99da-4c88-8af4-51060312eb9e%40googlegroups.com.

[weewx-user] Re: Weewx 4, any Gotchas to be aware of?

[Robert Anthony Pitera]

Is there a site/page that outlines the changes/features/breaking changes of 
Weewx 4.x?

On Sunday, February 9, 2020 at 4:51:14 PM UTC-5, Mike Revitt wrote:
>
> Almost finished my port of Weewx 3.9.2 from my MAC to my new Rasberry Pi 
> today, but my S3 integration needs Boto3, which needs Python 3.
>
> So I am now deploying Weewx 4, but thought I would check to see if there 
> are any gotchas to be aware of before I go live with it. 
>
> I use a Vantage Vue as my weather source over USB.
>
>

-- 
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/e803fbbc-3e14-4878-b7d5-06ffd5b1e9b7%40googlegroups.com.

[weewx-user] Re: Wind gust speed differences.

[gjr80]

Hi,

Hard to anything definitively without a bit more info. What is the 'Weewx 
website', is that the Standard skin or Seasons skin or something else? What 
weather station are you using? Are you posting to WU using rapid fire? 

Typically the Standard and Seasons skins will be updated with each new 
archive record as is comes in. So if your archive interval is five minutes 
you will see an update every five minutes and the wind gust data on the 
page should reflect the highest wind speed seen in the previous archive 
interval (five minutes). WU can be updated using rapid fire or via normal 
archive records, the difference being rapid fire uses loop packet data from 
your station which tends use more of a 'point in time' value whereas 
non-rapid fire uses data from the archive record which should match what 
you see on the Standard and Seasons skins. How frequent rapid fires updates 
are sent depends on your station and how often it emits loop packets. Of 
course, we have no idea what WU does with your data once received. WOW on 
the other hand is updated with archive data but instead of being updated 
every archive interval the default update period is every 15 minutes. So if 
you had a five minute archive interval only every third archive record 
would be sent to WOW and it would be quite conceivable to see different 
values on WOW for up to two-thirds of the time.

One thing you could do is set debug = 2 in weewx.conf and then restart 
WeeWX. That will cause WeeWX to log the data being sent to WU and WOW. You 
could then see how the posted data compares to what is displayed on your 
site. Bear in mind that the units used in the data posted to WU and WOW is 
US customary so you may need to do some conversions if your site displays 
Metric.

Gary

On Monday, 10 February 2020 19:10:56 UTC+10, Ton Karsten wrote:
>
> I note that there is a difference between the speed generated on the Weewx 
> website and the speed specified on the WU website and the WOW website data. 
> Is there an explanation for how this is possible and how to solve it?
>
> Regards,
> Ton
>

-- 
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/277468ea-ce7e-41c2-a7f1-cd7009be227b%40googlegroups.com.

[weewx-user] Wind gust speed differences.

[Ton Karsten]

I note that there is a difference between the speed generated on the Weewx 
website and the speed specified on the WU website and the WOW website data. 
Is there an explanation for how this is possible and how to solve it?

Regards,
Ton

-- 
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/febbf07d-6b6d-4acb-a7a0-7f8e3998f1ca%40googlegroups.com.