[weewx-user] Re: Weewx Highcharts units question

[Jd D]

Hi Gary,
Thanks great timing.
I had just finished looking at the high charts python code in user 
directory and figured it was in the weewx conf file that it was getting 
done and then I saw your post. 
So all is good.
Thanks again
Jerry

On Monday, June 3, 2019 at 6:07:54 PM UTC-7, Jd D wrote:
>
> Hi Gary,
>
> I have installed the latest version of the weewx extension for Highcharts 
> and have it all working with one exception and that is units. I have a US 
> system and the units are metric. I can look in the json data and the units 
> are metric. Yet in the tmpl file I see the tmpl functionality to get the 
> units and I am also displaying all the rest of the database and the units 
> are correct for US. The usunits field is a 1 in the database.  I did not 
> see any config entry in weewx.conf to change the units like there is for 
> CumulusRealtime which for me is set to US.
> Thanks for you help
> Jerry
>

-- 
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/2bca8c9f-713a-4003-90f5-73d7c144604d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Run Mutliple SDRs Drivers

[gjr80]

Perhaps its semantics but one WeeWX instance can only run one driver. The 
common way around this limitation is to run the second 'driver' as a 
service and augment packets/records as applicable. This requires one of the 
drivers to have been written to run as a service - not that difficult, most 
of the underlying code remains the same it is just really the interface to 
WeeWX that is different. Of course this ignores any issues associated with 
multiple SDR hardware devices.

And of course the other approach is to run two instances of WeeWX, not that 
difficult.

Gary

On Tuesday, 4 June 2019 11:57:19 UTC+10, rich T wrote:
>
> Wondering if there was a way to run multiple SDR drivers (RTLdavis and 
> SDR) using one instance of 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/396f6302-ca15-4f8a-8f0a-23423e0143bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[gjr80]

Agree that WeeWX-WD has struck again and caused the error that was posted. 
Am sure this been fixed in a later version, I will track that one down and 
post a link as necessary.

I also think there is another somewhat more critical issue - refer to the 
highlighted lines:

Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Initializing weewx 
version 3.9.1
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Using Python 2.7.13 (
default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Platform Linux-4.19.42-v7
+-armv7l-with-debian-9.9
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: Locale is 'en_GB.UTF-8'
Jun  3 23:29:29 raspberrypi weewx[22046]: engine: pid file is /var/run/weewx
.pid
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Using configuration file /
etc/weewx/weewx.conf
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Loading station type SDR (
user.sdr)
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: driver version is 
0.14rc1
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: sensor map is {
'windGust': 'wind_gust.0:*.OSWGR800Packet', 'windSpeed': 
'wind_speed.0:*.OSWGR800Packet', 'windBatteryStatus': 
'battery.0:*.OSWGR800Packet', 'windDir': 'wind_dir.0:*.OSWGR800Packet', 
'outHumidity': 'humidity.1:*.OSTHGR810Packet', 'outTemp': 
'temperature.1:*.OSTHGR810Packet', 'outTempBatteryStatus': 
'battery.1:*.OSTHGR810Packet', 'rain_total': 'rain_total.0:*.OSPCR800Packet'
, 'rainBatteryStatus': 'battery.0:*.OSPCR800Packet', 'extraTemp1': 
'temperature.1:14.RubicsonTempPacket', 'UV': 'uv_index.1:*.OSUV800Packet', 
'pressure': 'pressure.1:*.OSBTHGN129Packet', 'inTemp': 
'temperature.1:*.OSBTHGN129Packet', 'inHumidity': 
'humidity.1:*.OSBTHGN129Packet', 'inTempBatteryStatus': 
'battery.1:*.OSBTHGN129Packet'}
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: deltas is {
'strikes': 'strikes_total', 'rain': 'rain_total'}
Jun  3 23:29:29 raspberrypi weewx[22051]: sdr: MainThread: startup process 
'/usr/local/bin/rtl_433 
-q -U'
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: StdConvert target unit is 
0x1
Jun  3 23:29:29 raspberrypi weewx[22051]: wxcalculate: The following values 
will be calculated: barometer=software, windchill=prefer_hardware, dewpoint=
prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=
prefer_hardware, heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=
prefer_hardware, ET=prefer_hardware, altimeter=software, cloudbase=
prefer_hardware
Jun  3 23:29:29 raspberrypi weewx[22051]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Archive will use data 
binding wx_binding
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Record generation will be 
attempted in 'hardware'
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Using archive interval of 
90 seconds (specified in weewx configuration)
Jun  3 23:29:29 raspberrypi weewx[22051]: engine: Using binding 'wx_binding' 
to database 'weewx'
Jun  3 23:29:29 raspberrypi weewx[22051]: manager: Starting backfill of 
daily summaries
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: WdArchive will use 
data binding wd_binding
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: Using binding 
'wd_binding' to database 'weewxwd'
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: Starting backfill of 
daily summaries
Jun  3 23:29:29 raspberrypi kernel: [113521.231818] r820t 4-001a: 
destroying instance
Jun  3 23:29:29 raspberrypi kernel: [113521.232349] dvb_usb_v2: 'Realtek 
RTL2832U reference design:1-1.4' successfully deinitialized and disconnected
Jun  3 23:29:29 raspberrypi weewx[22051]: manager: Starting backfill of 
daily summaries
Jun  3 23:29:29 raspberrypi weewx[22051]: WdArchive: Daily summaries up to 
date.
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: Zambretti: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: Zambretti: 
interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: NWS: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: WU: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: WU: interval
=10800 max_age=604800 api_key=b92d location=pws:IRHNEALP38 fc=
hourly10day
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: OWM: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: UKMO: 
forecast version 3.2.14
Jun  3 23:29:29 raspberrypi weewx[22051]: forecast: MainThread: Aeris: 
forecast version 3.2.14
Jun  3 23:29:30 raspberrypi weewx[22051]: forecast: MainThread: WWO: 
forecast version 3.2.14
Jun  3 23:29:30 raspberrypi 

[weewx-user] Re: Weewx Highcharts units question

[gjr80]

Jerry,

Been a while since I have touched this one, and I note there is a dead link 
in the weewx-highcharts wiki for changing the plot units - guess I should 
fix that.

Anyway, you should be able to change the units used in the json file via 
weewx.conf - it's not a US/Metric switch but rather a config option for 
each unit group . If you have a look at the [StdReport] stanza in weewx.conf 
you should have a [[Highcharts]] [[[Units]]] Groups stanza that 
will probably look something like:

[StdReport]

[[Highcharts]]

[[[Units]]]

Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = hPa
group_rain = mm
group_rainrate = mm_per_hour
group_speed = km_per_hour
group_speed2 = km_per_hour2
group_temperature = degree_C

Change the group_ option settings as required. The values are standard 
WeeWX unit group names as per the Group column in the Unit groups, members 
and options table in the Units appendix to the Customization Guide 
. There may be some stale_age 
settings that could delay re-generation of the json files, just delete the 
json output files on your WeeWX machine to force regeneration on the next 
report cycle.

A bit pressed for time so have not had a change to test this, if the above 
does not work could you please post your [StdReport] stanza and I will have 
a closer look.

Gary

On Tuesday, 4 June 2019 11:07:54 UTC+10, Jd D wrote:
>
> Hi Gary,
>
> I have installed the latest version of the weewx extension for Highcharts 
> and have it all working with one exception and that is units. I have a US 
> system and the units are metric. I can look in the json data and the units 
> are metric. Yet in the tmpl file I see the tmpl functionality to get the 
> units and I am also displaying all the rest of the database and the units 
> are correct for US. The usunits field is a 1 in the database.  I did not 
> see any config entry in weewx.conf to change the units like there is for 
> CumulusRealtime which for me is set to US.
> Thanks for you help
> Jerry
>

-- 
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/40891a54-2f4f-4014-a4c4-30426eb10d1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Weewx 3.9.1 and Vantage Pro 2

[Thomas Keffer]

Yes. Somewhere along the line, Davis put in firmware that attempts to
validate the type of logger you have. This was an attempt on their part to
make it hard for 3rd party loggers. A side effect is that old loggers will
not work in new consoles.

So, I suspect you are either using a 3rd party logger, or trying to use an
old logger in your new console. If the latter, Davis will swap them out.
Contact them.

Or, I could be completely wrong!

-tk


On Mon, Jun 3, 2019 at 2:14 PM Alexis Domjan  wrote:

> Hi,
>
> We have multiple Vantage Pro 2 we bought several years ago. We're using
> vproweather which works pretty well.
>
> However, the last station we bought seems to be slightly different and we
> can't get it work with vproweather, so I had a look on Weewx, installed
> version 3.9.1 and tried it.
>
> But I see the same issue. Basically any command sent to the Vantage Pro 2
> ends with: SECURED-LOGGER FAILED.
>
> So when I start Weewx daemon, it says:
>
> Jun  3 22:58:09 solar1 weewx[2715]: vantage: Gentle wake up of console
> successful
> Jun  3 22:58:09 solar1 weewx[2715]: vantage: No  received from console
>
> And indeed it doesn't get a ACK but the string: SECURED-LOGGER FAILED.
>
> I read a thread here:
> https://groups.google.com/forum/#!searchin/weewx-user/SECURED%7Csort:date/weewx-user/1FOCgQqFZtM/IZ4-0Q5uEAAJ
>
> It is exactly the same problem I encounter. Sadly, the solution isn't
> documented.
>
> It is like if Davis included some kind of authentication or something like
> this and we are not allowed to use it something else than their Windows
> software.
>
> Would anyone have any idea about this issue ?
>
> Thank you,
> kind regards.
>
> --
> 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/4acbe3b5-decb-4983-8b9a-ed75a8ab89fa%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPq0zEAiZiiVTvx6SAhAVhgSUHnWu-b%2BdHvks_HTVCsTyWQK4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[Thomas Keffer]

The problem is not with WeeWX, but with the weewxwd3 extension you
installed. It does not seem to check for missing data before attempting to
calculate humidity.

On Mon, Jun 3, 2019 at 2:36 PM St. B.  wrote:

> Ok,
>
> Below is the the /var/log/messages generated when running systemctl
> restart weewx.
>
> Weirdly enough systemctl start weewx does not seem to run anything.
>
> Stack trace when running from command prompt is as follows :
> root@raspberrypi:~# weewxd /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 890, in main
> engine.run()
>   File "/usr/share/weewx/weewx/engine.py", line 191, in run
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>   File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> callback(event)
>   File "/usr/share/weewx/user/weewxwd3.py", line 144, in new_loop_packet
> wd_data['humidex'] =
> weewx.wxformulas.humidexC(data_metricwx['outTemp'],
> KeyError: 'outTemp'
> root@raspberrypi:~#
>
> Associated message traces are in mylog.shell
>
> On Monday, June 3, 2019 at 11:19:52 PM UTC+2, Pat wrote:
>>
>> Nothing jumping out. Pasting some logs and debugs would be super helpful.
>> See Help! Posting to weewx user
>> 
>>
>>
>>
>> On Monday, June 3, 2019 at 4:49:17 PM UTC-4, St. B. wrote:
>>>
>>> Hi,
>>>
>>> I decided (because my WU forecast where not working anymore) to update
>>> weewx to 3.9.1. on my raspberry running debian stretch.
>>> downloaded the weewx.3.9.1.all.deb installed, and kept my conf files.
>>> Upon install completion, no restart of the service.
>>>
>>> When starting, weewx starts the mainloop then shutsdown, wait for RTL
>>> process shutdown and dies.
>>> rtl runs fine from the command prompt.
>>> when running from the command prompt weewxd starts, and dies quickly
>>> with an invalid key "windSpeed" or some other key.
>>> These keys are in my mappings, but did not change since 3.6
>>>
>>> I ran a full update of my raspberry and am now at deb 9.9, but still no
>>> weewx.
>>>
>>> What obvious "you must check when updating" did I miss on this one ?
>>>
>>> Regards;
>>>
>>> --
> 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/66dc95b4-7dff-42f7-9d7f-476efdbe8225%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPq0zEAz-G5Ys_wSQAAj%2BObMNCBKCZcdGFZijGFrChiPd9nw6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx Highcharts units question

[Jd D]

Hi Gary,

I have installed the latest version of the weewx extension for Highcharts 
and have it all working with one exception and that is units. I have a US 
system and the units are metric. I can look in the json data and the units 
are metric. Yet in the tmpl file I see the tmpl functionality to get the 
units and I am also displaying all the rest of the database and the units 
are correct for US. The usunits field is a 1 in the database.  I did not 
see any config entry in weewx.conf to change the units like there is for 
CumulusRealtime which for me is set to US.
Thanks for you help
Jerry

-- 
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/0c7a4e54-4b9d-4a8a-85ac-1c667c35a4ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

[Rod Yager]

I’ve already migrated the today logic into my local version of wunderfixer, 
which runs as a cron job at 05:58, 11:58, 17:58 and 23:58.

This works as expected here.

The only circumstance I can see in which it would break is if I make a request 
for today’s data  at 23:59:59.95 on my machine. The transmission delay (and 
possibly differences in the clocks) will mean that WU receives my request at a 
time when it thinks it is 00:00:00.01 on the following day (my time) and so it 
will return the (empty) data for the day after the date on which I made the 
request. We can’t worry about such things.


Rod



On 4 Jun 2019, at 7:55 am, Leon Shaner 
mailto:l...@isylum.org>> wrote:

Thanks, Rod!  =D

Those are precisely the same tests I ran and exact same results that noted, 
before  before publishing.  =D
Plus a ton of checks against my own station, KMIDEARB5, west of UTC.

As before, even more important than these 'historical' API tests is to query 
against the current day at different times throughout the day, such as before 
and after your midnight and before and after UTC midnight.  That logic which 
uses the 'today' API (rapid) for today is the one we will likely keep no matter 
what IBM does with the well-known bugs in the 'historical' API.

(I can't test the 'today' logic 100% without changing my localtime on my system 
and I don't want to do that, which is why I appreciate help from others to 
validate the code).  =D

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

On Jun 3, 2019, at 5:39 PM, Rod Yager 
mailto:r...@yager.net.au>> wrote:

Dear Leon,

Thanks for all your work on this. This works as well as we are going to be able 
to manage unless and until WU fixes the bug.

The remaining issue affects just one date, the  “change-over” date when WU 
transitions to returning the correct data - and will only bite for stations 
east of UTC, and only in the hours that they are ahead of UTC.

Currently, for me, that date is 2019-05-28. When it originally asks for 
2019-05-28, it returns the data for 2019-05-29. Wunderfixer then tries to 
compensate by asking for 2019-05-27. But 2019-05-27 is a date before the WU 
bug, and so it returns the data for 2019-05-27. We can’t work around this, 
because no request to WU will actually return the data we want. The only fix is 
to wait a few hours until the UTC date is aligned with the Sydney date.

Good news is that for stations west of UTC, this won’t happen as the bug causes 
a duplicate day, not a missing day.

Here’s the output for the requests for my station from 2019-05-27 (before the 
WU bug kicks in) to today 2019-06-04.


[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-27  --test --verbose | (head -n 11 ; tail -n 3)
Using configuration file /home/weewx/weewx.conf.
Weather Underground Station:   ISYDNEY155
Date to check: 2019-05-27
WU API obsTimeLocal:   2019-05-27
epoch: 1558879200 date_epoch_local: 2019-05-27 00:00:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:00:00Z obsTimeLocal: 2019-05-27 00:00:00
epoch: 1558879500 date_epoch_local: 2019-05-27 00:05:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:05:00Z obsTimeLocal: 2019-05-27 00:05:00
epoch: 1558879800 date_epoch_local: 2019-05-27 00:10:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:10:00Z obsTimeLocal: 2019-05-27 00:10:00
epoch: 1558880100 date_epoch_local: 2019-05-27 00:15:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:15:00Z obsTimeLocal: 2019-05-27 00:15:00
epoch: 1558880400 date_epoch_local: 2019-05-27 00:20:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:20:00Z obsTimeLocal: 2019-05-27 00:20:00
epoch: 1558880700 date_epoch_local: 2019-05-27 00:25:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:25:00Z obsTimeLocal: 2019-05-27 00:25:00
epoch: 1558881000 date_epoch_local: 2019-05-27 00:30:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:30:00Z obsTimeLocal: 2019-05-27 00:30:00
epoch: 1558965000 date_epoch_local: 2019-05-27 23:50:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-27T13:50:00Z obsTimeLocal: 2019-05-27 23:50:00
epoch: 1558965300 date_epoch_local: 2019-05-27 23:55:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-27T13:55:00Z obsTimeLocal: 2019-05-27 23:55:00
Number of WU records:  288
[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-28  --test --verbose | (head -n 11 ; tail -n 3)

No results returned from Weather Underground (perhaps a bad station name??).
Using configuration file /home/weewx/weewx.conf.
Weather Underground Station:   ISYDNEY155
Date to check: 2019-05-28
WU API obsTimeLocal:   2019-05-29
WU API RETURNED WRONG DATE!!!
WU API COMPENSATION DATE:  2019-05-27
WU API obsTimeLocal:   2019-05-27
WU API COMPENSATION FAILURE! ABORTING!!!
Number of WU records:  0
[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-29  --test --verbose | (head -n 11 ; tail -n 3)
Using 

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

[Leon Shaner]

Thanks, Rod!  =D

Those are precisely the same tests I ran and exact same results that noted, 
before  before publishing.  =D
Plus a ton of checks against my own station, KMIDEARB5, west of UTC.

As before, even more important than these 'historical' API tests is to query 
against the current day at different times throughout the day, such as before 
and after your midnight and before and after UTC midnight.  That logic which 
uses the 'today' API (rapid) for today is the one we will likely keep no matter 
what IBM does with the well-known bugs in the 'historical' API.

(I can't test the 'today' logic 100% without changing my localtime on my system 
and I don't want to do that, which is why I appreciate help from others to 
validate the code).  =D

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

> On Jun 3, 2019, at 5:39 PM, Rod Yager  wrote:
> 
> Dear Leon,
> 
> Thanks for all your work on this. This works as well as we are going to be 
> able to manage unless and until WU fixes the bug. 
> 
> The remaining issue affects just one date, the  “change-over” date when WU 
> transitions to returning the correct data - and will only bite for stations 
> east of UTC, and only in the hours that they are ahead of UTC.
> 
> Currently, for me, that date is 2019-05-28. When it originally asks for 
> 2019-05-28, it returns the data for 2019-05-29. Wunderfixer then tries to 
> compensate by asking for 2019-05-27. But 2019-05-27 is a date before the WU 
> bug, and so it returns the data for 2019-05-27. We can’t work around this, 
> because no request to WU will actually return the data we want. The only fix 
> is to wait a few hours until the UTC date is aligned with the Sydney date.
> 
> Good news is that for stations west of UTC, this won’t happen as the bug 
> causes a duplicate day, not a missing day.
> 
> Here’s the output for the requests for my station from 2019-05-27 (before the 
> WU bug kicks in) to today 2019-06-04.
> 
> 
> [rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
> 2019-05-27  --test --verbose | (head -n 11 ; tail -n 3)
> Using configuration file /home/weewx/weewx.conf.
> Weather Underground Station:   ISYDNEY155
> Date to check: 2019-05-27
> WU API obsTimeLocal:   2019-05-27
> epoch: 1558879200 date_epoch_local: 2019-05-27 00:00:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:00:00Z obsTimeLocal: 2019-05-27 00:00:00
> epoch: 1558879500 date_epoch_local: 2019-05-27 00:05:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:05:00Z obsTimeLocal: 2019-05-27 00:05:00
> epoch: 1558879800 date_epoch_local: 2019-05-27 00:10:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:10:00Z obsTimeLocal: 2019-05-27 00:10:00
> epoch: 1558880100 date_epoch_local: 2019-05-27 00:15:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:15:00Z obsTimeLocal: 2019-05-27 00:15:00
> epoch: 1558880400 date_epoch_local: 2019-05-27 00:20:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:20:00Z obsTimeLocal: 2019-05-27 00:20:00
> epoch: 1558880700 date_epoch_local: 2019-05-27 00:25:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:25:00Z obsTimeLocal: 2019-05-27 00:25:00
> epoch: 1558881000 date_epoch_local: 2019-05-27 00:30:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-26T14:30:00Z obsTimeLocal: 2019-05-27 00:30:00
> epoch: 1558965000 date_epoch_local: 2019-05-27 23:50:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-27T13:50:00Z obsTimeLocal: 2019-05-27 23:50:00
> epoch: 1558965300 date_epoch_local: 2019-05-27 23:55:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-27T13:55:00Z obsTimeLocal: 2019-05-27 23:55:00
> Number of WU records:  288
> [rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
> 2019-05-28  --test --verbose | (head -n 11 ; tail -n 3)
> 
> No results returned from Weather Underground (perhaps a bad station name??).
> Using configuration file /home/weewx/weewx.conf.
> Weather Underground Station:   ISYDNEY155
> Date to check: 2019-05-28
> WU API obsTimeLocal:   2019-05-29
> WU API RETURNED WRONG DATE!!!
> WU API COMPENSATION DATE:  2019-05-27
> WU API obsTimeLocal:   2019-05-27
> WU API COMPENSATION FAILURE! ABORTING!!!
> Number of WU records:  0
> [rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
> 2019-05-29  --test --verbose | (head -n 11 ; tail -n 3)
> Using configuration file /home/weewx/weewx.conf.
> Weather Underground Station:   ISYDNEY155
> Date to check: 2019-05-29
> WU API obsTimeLocal:   2019-05-30
> WU API RETURNED WRONG DATE!!!
> WU API COMPENSATION DATE:  2019-05-28
> WU API obsTimeLocal:   2019-05-29
> epoch: 1559052000 date_epoch_local: 2019-05-29 00:00:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-28T14:00:00Z obsTimeLocal: 2019-05-29 00:00:00
> epoch: 1559052300 date_epoch_local: 2019-05-29 00:05:00 tz: Australia/Sydney 
> obsTimeUtc: 2019-05-28T14:05:00Z obsTimeLocal: 

[weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[Pat]

I'm not seeing much here for me to go on, but some more questions: did you 
change your database? I wonder if it's locked or modified?

What happens if you run  weewxd /etc/weewx/weewx.conf

Paste the output if/when it crashes. 


On Monday, June 3, 2019 at 5:36:16 PM UTC-4, St. B. wrote:
>
> Ok, 
>
> Below is the the /var/log/messages generated when running systemctl 
> restart weewx.
>
> Weirdly enough systemctl start weewx does not seem to run anything.
>
> Stack trace when running from command prompt is as follows : 
> root@raspberrypi:~# weewxd /etc/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 890, in main
> engine.run()
>   File "/usr/share/weewx/weewx/engine.py", line 191, in run
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>   File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> callback(event)
>   File "/usr/share/weewx/user/weewxwd3.py", line 144, in new_loop_packet
> wd_data['humidex'] = 
> weewx.wxformulas.humidexC(data_metricwx['outTemp'],
> KeyError: 'outTemp'
> root@raspberrypi:~#
>
> Associated message traces are in mylog.shell
>
> On Monday, June 3, 2019 at 11:19:52 PM UTC+2, Pat wrote:
>>
>> Nothing jumping out. Pasting some logs and debugs would be super helpful. 
>> See Help! Posting to weewx user 
>> 
>>
>>
>>
>> On Monday, June 3, 2019 at 4:49:17 PM UTC-4, St. B. wrote:
>>>
>>> Hi, 
>>>
>>> I decided (because my WU forecast where not working anymore) to update 
>>> weewx to 3.9.1. on my raspberry running debian stretch.
>>> downloaded the weewx.3.9.1.all.deb installed, and kept my conf files.
>>> Upon install completion, no restart of the service.
>>>
>>> When starting, weewx starts the mainloop then shutsdown, wait for RTL 
>>> process shutdown and dies.
>>> rtl runs fine from the command prompt.
>>> when running from the command prompt weewxd starts, and dies quickly 
>>> with an invalid key "windSpeed" or some other key.
>>> These keys are in my mappings, but did not change since 3.6
>>>
>>> I ran a full update of my raspberry and am now at deb 9.9, but still no 
>>> weewx.
>>>
>>> What obvious "you must check when updating" did I miss on this one ?
>>>
>>> Regards;
>>>
>>>

-- 
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/62c99f94-1063-4591-ab5c-4e37d5b4e85c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

[Rod Yager]

Dear Leon,

Thanks for all your work on this. This works as well as we are going to be able 
to manage unless and until WU fixes the bug.

The remaining issue affects just one date, the  “change-over” date when WU 
transitions to returning the correct data - and will only bite for stations 
east of UTC, and only in the hours that they are ahead of UTC.

Currently, for me, that date is 2019-05-28. When it originally asks for 
2019-05-28, it returns the data for 2019-05-29. Wunderfixer then tries to 
compensate by asking for 2019-05-27. But 2019-05-27 is a date before the WU 
bug, and so it returns the data for 2019-05-27. We can’t work around this, 
because no request to WU will actually return the data we want. The only fix is 
to wait a few hours until the UTC date is aligned with the Sydney date.

Good news is that for stations west of UTC, this won’t happen as the bug causes 
a duplicate day, not a missing day.

Here’s the output for the requests for my station from 2019-05-27 (before the 
WU bug kicks in) to today 2019-06-04.


[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-27  --test --verbose | (head -n 11 ; tail -n 3)
Using configuration file /home/weewx/weewx.conf.
Weather Underground Station:   ISYDNEY155
Date to check: 2019-05-27
WU API obsTimeLocal:   2019-05-27
epoch: 1558879200 date_epoch_local: 2019-05-27 00:00:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:00:00Z obsTimeLocal: 2019-05-27 00:00:00
epoch: 1558879500 date_epoch_local: 2019-05-27 00:05:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:05:00Z obsTimeLocal: 2019-05-27 00:05:00
epoch: 1558879800 date_epoch_local: 2019-05-27 00:10:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:10:00Z obsTimeLocal: 2019-05-27 00:10:00
epoch: 1558880100 date_epoch_local: 2019-05-27 00:15:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:15:00Z obsTimeLocal: 2019-05-27 00:15:00
epoch: 1558880400 date_epoch_local: 2019-05-27 00:20:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:20:00Z obsTimeLocal: 2019-05-27 00:20:00
epoch: 1558880700 date_epoch_local: 2019-05-27 00:25:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:25:00Z obsTimeLocal: 2019-05-27 00:25:00
epoch: 1558881000 date_epoch_local: 2019-05-27 00:30:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-26T14:30:00Z obsTimeLocal: 2019-05-27 00:30:00
epoch: 1558965000 date_epoch_local: 2019-05-27 23:50:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-27T13:50:00Z obsTimeLocal: 2019-05-27 23:50:00
epoch: 1558965300 date_epoch_local: 2019-05-27 23:55:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-27T13:55:00Z obsTimeLocal: 2019-05-27 23:55:00
Number of WU records:  288
[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-28  --test --verbose | (head -n 11 ; tail -n 3)

No results returned from Weather Underground (perhaps a bad station name??).
Using configuration file /home/weewx/weewx.conf.
Weather Underground Station:   ISYDNEY155
Date to check: 2019-05-28
WU API obsTimeLocal:   2019-05-29
WU API RETURNED WRONG DATE!!!
WU API COMPENSATION DATE:  2019-05-27
WU API obsTimeLocal:   2019-05-27
WU API COMPENSATION FAILURE! ABORTING!!!
Number of WU records:  0
[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-29  --test --verbose | (head -n 11 ; tail -n 3)
Using configuration file /home/weewx/weewx.conf.
Weather Underground Station:   ISYDNEY155
Date to check: 2019-05-29
WU API obsTimeLocal:   2019-05-30
WU API RETURNED WRONG DATE!!!
WU API COMPENSATION DATE:  2019-05-28
WU API obsTimeLocal:   2019-05-29
epoch: 1559052000 date_epoch_local: 2019-05-29 00:00:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-28T14:00:00Z obsTimeLocal: 2019-05-29 00:00:00
epoch: 1559052300 date_epoch_local: 2019-05-29 00:05:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-28T14:05:00Z obsTimeLocal: 2019-05-29 00:05:00
epoch: 1559052600 date_epoch_local: 2019-05-29 00:10:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-28T14:10:00Z obsTimeLocal: 2019-05-29 00:10:00
epoch: 1559052900 date_epoch_local: 2019-05-29 00:15:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-28T14:15:00Z obsTimeLocal: 2019-05-29 00:15:00
epoch: 1559137800 date_epoch_local: 2019-05-29 23:50:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-29T13:50:00Z obsTimeLocal: 2019-05-29 23:50:00
epoch: 1559138100 date_epoch_local: 2019-05-29 23:55:00 tz: Australia/Sydney 
obsTimeUtc: 2019-05-29T13:55:00Z obsTimeLocal: 2019-05-29 23:55:00
Number of WU records:  288
[rodyager@moses ~]$ /home/weewx/bin/wunderdates3 --epsilon=125 --date 
2019-05-30  --test --verbose | (head -n 11 ; tail -n 3)
Using configuration file /home/weewx/weewx.conf.
Weather Underground Station:   ISYDNEY155
Date to check: 2019-05-30
WU API obsTimeLocal:   2019-05-31
WU API RETURNED WRONG DATE!!!
WU API COMPENSATION DATE:  2019-05-29
WU API 

[weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[St. B.]

Ok, 

Below is the the /var/log/messages generated when running systemctl restart 
weewx.

Weirdly enough systemctl start weewx does not seem to run anything.

Stack trace when running from command prompt is as follows : 
root@raspberrypi:~# weewxd /etc/weewx/weewx.conf
Traceback (most recent call last):
  File "/usr/bin/weewxd", line 64, in 
weewx.engine.main(options, args)
  File "/usr/share/weewx/weewx/engine.py", line 890, in main
engine.run()
  File "/usr/share/weewx/weewx/engine.py", line 191, in run
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
  File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
callback(event)
  File "/usr/share/weewx/user/weewxwd3.py", line 144, in new_loop_packet
wd_data['humidex'] = weewx.wxformulas.humidexC(data_metricwx['outTemp'],
KeyError: 'outTemp'
root@raspberrypi:~#

Associated message traces are in mylog.shell

On Monday, June 3, 2019 at 11:19:52 PM UTC+2, Pat wrote:
>
> Nothing jumping out. Pasting some logs and debugs would be super helpful. 
> See Help! Posting to weewx user 
> 
>
>
>
> On Monday, June 3, 2019 at 4:49:17 PM UTC-4, St. B. wrote:
>>
>> Hi, 
>>
>> I decided (because my WU forecast where not working anymore) to update 
>> weewx to 3.9.1. on my raspberry running debian stretch.
>> downloaded the weewx.3.9.1.all.deb installed, and kept my conf files.
>> Upon install completion, no restart of the service.
>>
>> When starting, weewx starts the mainloop then shutsdown, wait for RTL 
>> process shutdown and dies.
>> rtl runs fine from the command prompt.
>> when running from the command prompt weewxd starts, and dies quickly with 
>> an invalid key "windSpeed" or some other key.
>> These keys are in my mappings, but did not change since 3.6
>>
>> I ran a full update of my raspberry and am now at deb 9.9, but still no 
>> weewx.
>>
>> What obvious "you must check when updating" did I miss on this one ?
>>
>> Regards;
>>
>>

-- 
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/66dc95b4-7dff-42f7-9d7f-476efdbe8225%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


mylog
Description: Binary data


mylog.shell
Description: Binary data

[weewx-user] Re: weewx stop working after upgrading from 3.6.x to 3.9.1

[Pat]

Nothing jumping out. Pasting some logs and debugs would be super helpful. 
See Help! Posting to weewx user 




On Monday, June 3, 2019 at 4:49:17 PM UTC-4, St. B. wrote:
>
> Hi, 
>
> I decided (because my WU forecast where not working anymore) to update 
> weewx to 3.9.1. on my raspberry running debian stretch.
> downloaded the weewx.3.9.1.all.deb installed, and kept my conf files.
> Upon install completion, no restart of the service.
>
> When starting, weewx starts the mainloop then shutsdown, wait for RTL 
> process shutdown and dies.
> rtl runs fine from the command prompt.
> when running from the command prompt weewxd starts, and dies quickly with 
> an invalid key "windSpeed" or some other key.
> These keys are in my mappings, but did not change since 3.6
>
> I ran a full update of my raspberry and am now at deb 9.9, but still no 
> weewx.
>
> What obvious "you must check when updating" did I miss on this one ?
>
> Regards;
>
>

-- 
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/ed29c761-6a6c-4303-9abe-9626caab8069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Weewx 3.9.1 and Vantage Pro 2

[Alexis Domjan]

Hi,

We have multiple Vantage Pro 2 we bought several years ago. We're using 
vproweather which works pretty well.

However, the last station we bought seems to be slightly different and we 
can't get it work with vproweather, so I had a look on Weewx, installed 
version 3.9.1 and tried it. 

But I see the same issue. Basically any command sent to the Vantage Pro 2 
ends with: SECURED-LOGGER FAILED.

So when I start Weewx daemon, it says:

Jun  3 22:58:09 solar1 weewx[2715]: vantage: Gentle wake up of console 
successful
Jun  3 22:58:09 solar1 weewx[2715]: vantage: No  received from console

And indeed it doesn't get a ACK but the string: SECURED-LOGGER FAILED.

I read a thread here: 
https://groups.google.com/forum/#!searchin/weewx-user/SECURED%7Csort:date/weewx-user/1FOCgQqFZtM/IZ4-0Q5uEAAJ
 


It is exactly the same problem I encounter. Sadly, the solution isn't 
documented.

It is like if Davis included some kind of authentication or something like 
this and we are not allowed to use it something else than their Windows 
software.

Would anyone have any idea about this issue ?

Thank you,
kind regards.

-- 
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/4acbe3b5-decb-4983-8b9a-ed75a8ab89fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx stop working after upgrading from 3.6.x to 3.9.1

[St. B.]

Hi, 

I decided (because my WU forecast where not working anymore) to update 
weewx to 3.9.1. on my raspberry running debian stretch.
downloaded the weewx.3.9.1.all.deb installed, and kept my conf files.
Upon install completion, no restart of the service.

When starting, weewx starts the mainloop then shutsdown, wait for RTL 
process shutdown and dies.
rtl runs fine from the command prompt.
when running from the command prompt weewxd starts, and dies quickly with 
an invalid key "windSpeed" or some other key.
These keys are in my mappings, but did not change since 3.6

I ran a full update of my raspberry and am now at deb 9.9, but still no 
weewx.

What obvious "you must check when updating" did I miss on this one ?

Regards;

-- 
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/d0d18421-b227-49cd-ad01-e873f5420f4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

[Leon Shaner]

All,
There are updates to the wunderdates utilities, to implement the following:

Add +/- 1-day compensation logic to workaround WU 'historical' API bug, 
depending on whether station is east/west of UTC, and whether it is within X 
hours of UTC midnight, relative to the local station time.

These wunderdates utilities are for debug purposes only to aid in testing the 
WU behavior, while IBM works to fix the actual bug (no intention of adding this 
logic to wunderfixer, which will remain broken until IBM fixes their API).

The bugs are well known / well documented.
The continued use of wunderdates is just to keep an eye on IBM's progress in 
fixing the bugs, e.g. keep an eye out for if the behavior changes / improves.

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

> On Jun 1, 2019, at 1:17 PM, Leon Shaner  wrote:
> 
> All,
> 
> I'm testing a new approach.  Below you will find links to an updated 
> wunderdates utility that can be used to validate whether I am on the right 
> track.
> The wunderdates utility simply dumps out timestamp related records from what 
> WU returns from the query.
> 
> We're looking mainly at the obsTimeUtc and obsTimeLocal values, which were 
> demonstrated under the prior approach to be returning the wrong dates when 
> within the stations localtime +/- offset from UTC.
> 
> The new approach is to detect if the requested date is 'today' and if so, use 
> a different API URL that already assumes 'today' and will hopefully not be 
> subject to the UTC offset bugs we've been chasing with the historical data 
> API URL.
> 
> I have my crontab set to do another test approaching my UTC offset, just 
> after coming within the offset, and then again just before and after midnight 
> localtime.
> (Same test I did before, but now with the new approach in place).
> 
> Here is the utility for anyone else that wants to check out the behavior:
> 
> https://github.com/UberEclectic/weewx/blob/wuapi/bin/wunderdates3
> https://github.com/UberEclectic/weewx/blob/wuapi/bin/wunderdates4
> 
> Which version you pull will depend on which base weewx you are running.
> Pull the one that matches your weewx version and place it in bin, next to 
> wunderfixer, and it will take the same arguments as wunderfixer.
> 
> You can just try wunderfixer as you normally would (with --apikey) and then 
> run wunderdates(3 or 4) with exact same arguments to be able to see what 
> actual timestamps WU is sending back for the date queried.
> Parameters like --epsilon don't have any effect in the case of wunderdates, 
> but I left it there so you don't have to change options when running the util 
> to get the debug output.
> 
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
> 
>> On May 30, 2019, at 12:40 AM, Leon Shaner  wrote:
>> 
>> Rod,
>> Thanks again for this.
>> 
>> Since the in-progress version of wunderfixer doesn't really show you the 
>> dates that come back from WU, I have written a tool just to debug the dates.
>> 
>> The command-line input and basing of defaults on weewx.conf works the same 
>> as wunderfixer, except it doesn't look at your DB at all.  It only prints 
>> out datestamps in various incarnations coming back from WU and as compared 
>> to your system's localtime.
>> 
>> It would be helpful to see the "wunderdates" output at times like you've 
>> shown below, a la before and after your localtime rolls around to UTC 
>> midnight.
>> 
>> Since you are at UTC + 10, another interesting time would be 11+ hours on 
>> either side of UTC midnight, in addition to within 9 or less hours.  This is 
>> just to make sure we're covering all the corner cases.
>> 
>> Gary reported a difference for stations that are east vs. west of GMT, and I 
>> expect we're really chasing the same bug in that there is some bad math WU 
>> is doing based on UTC offset, but since an offset can be +/-, the effects go 
>> in opposite directions date-wise, depending on which side of the UTC 
>> dateline your station is located.
>> 
>> At least that is what I surmise may be happening, but the wunderdates 
>> utility should shed light one way or the other.  =D
>> 
>> The wunderdates utility is available at the links below.
>> 
>> https://github.com/UberEclectic/weewx/blob/wuapi/bin/wunderdates3
>> https://github.com/UberEclectic/weewx/blob/wuapi/bin/wunderdates4
>> 
>> Which version you pull will depend on which base weewx you are running.
>> Pull the one that matches your weewx version and place it in bin, next to 
>> wunderfixer, and it will take the same arguments as wunderfixer.
>> 
>> You can just try wunderfixer as you normally would (with --apikey) and then 
>> run wunderdates(3 or 4) with exact same arguments to be able to see what 
>> actual timestamps WU is sending back for the date queried.
>> Parameters like --epsilon don't have any effect in the case of wunderdates, 
>> but I left it there so you don't have to change options when running the 
>> util to get the debug output.
>> 

[weewx-user] Re: Web Server auf dem Raspberry Apache2

[Günther Wrana]

Hallo dort


/etc/apache2/conf.d 

steht das darin 

Alias /weewx /home/weewx/public_html

  Options FollowSymlinks
  AllowOverride None


Ist das korrekt? Stimmt das mit den Leerzeichen? Ist die Datei korrekt?
Den es funktioniert immer noch nicht.

Not Found

The requested URL /weewx was not found on this server.
--
Apache/2.4.25 (Raspbian) Server at localhost Port 80

-- 
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/d5dc47c0-42b4-41d8-aa4e-e1575cb6be32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Juan Antonio Mosquera]

it is possible that a vim swap file was the cause.

sorry!

El lunes, 3 de junio de 2019, 20:55:04 (UTC+2), Pat escribió:
>
> The installation of the skin shouldn't break weewx.conf. What was deleted 
> from your weewx.conf?
>
>
> On Monday, June 3, 2019 at 2:48:18 PM UTC-4, Juan Antonio Mosquera wrote:
>>
>> This problem is in weewx.conf 
>>
>> installation crash this file backup is necesary!
>>
>> Greetings.
>>
>> El lunes, 3 de junio de 2019, 20:35:12 (UTC+2), Juan Antonio Mosquera 
>> escribió:
>>>
>>> Hi...
>>>
>>> rare... i had 1.0 version... i update... and...
>>>
>>> jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
>>> exception in engine:
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most 
>>> recent call last):
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 884, in main
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
>>> engine_class(config_dict)
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>>> self.loadServices(config_dict)
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>>> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 304, in __init__
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>>> target_unit_nickname = config_dict['StdConvert']['target_unit']
>>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>>> "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
>>> dict.__getitem__(self, key)
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 
>>> 'StdConvert'
>>> jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.
>>>
>>>
>>> what problem¿?
>>>
>>> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:

 Belchertown skin 1.0 is released!

 This update contains a lot of updates and changes including *an entire 
 rewrite of the Highcharts system* which allows you to make almost any 
 graph you want for almost any time span you want. You can see some 
 examples 
 of the charts you can make on the BelchertownWeather.com website 
 graphs page .

 You can add/remove/change/reorder any chart, change colors, add 
 observation plots, categorize for all time. Almost anything you want to do 
 is available! The skin comes with the standard 4 charts ready to go, but 
 there's extensive Belchertown Charts Documentation 
 
  
 which can help you get started. 

 In addition to the Charts there's now a dark mode (which has an 
 auto-switching mode based on sunset/sunrise), more flexibility for 
 translations, user customized station observation table which is updated 
 in 
 real time if the MQTT Websockets are enabled, and a lot more. Check the 
 release notes for all the details! 

 You can download the latest release here 
 ,
  
 and read all of the details on the changes here: 
 https://github.com/poblabs/weewx-belchertown/releases

 *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
 uninstall everything and reinstall new. This is due to the Chart system 
 being fully rewritten and the potential for conflicts. Please read 
 this upgrade guide if you are upgrading from an older version of 
 Belchertown skin 
 
 . 

 Thanks to all the beta testers and translators over the last couple of 
 months help me iron out all the kinks and shape the skin in a way that can 
 be translated a little easier! 

 Attached are some examples of the charts that can be made. If you find 
 any issues, you can reply here or open an issue on the Belchertown 
 skin GitHub page . 

>>>

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

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

The installation of the skin shouldn't break weewx.conf. What was deleted 
from your weewx.conf?


On Monday, June 3, 2019 at 2:48:18 PM UTC-4, Juan Antonio Mosquera wrote:
>
> This problem is in weewx.conf 
>
> installation crash this file backup is necesary!
>
> Greetings.
>
> El lunes, 3 de junio de 2019, 20:35:12 (UTC+2), Juan Antonio Mosquera 
> escribió:
>>
>> Hi...
>>
>> rare... i had 1.0 version... i update... and...
>>
>> jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
>> exception in engine:
>> jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
>> jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most 
>> recent call last):
>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>> "/usr/share/weewx/weewx/engine.py", line 884, in main
>> jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
>> engine_class(config_dict)
>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>> self.loadServices(config_dict)
>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>> "/usr/share/weewx/weewx/engine.py", line 304, in __init__
>> jun 03 20:30:43 meteomontaos weewx[4029]:   
>> target_unit_nickname = config_dict['StdConvert']['target_unit']
>> jun 03 20:30:43 meteomontaos weewx[4029]: File 
>> "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
>> jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
>> dict.__getitem__(self, key)
>> jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 'StdConvert'
>> jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.
>>
>>
>> what problem¿?
>>
>> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>>
>>> Belchertown skin 1.0 is released!
>>>
>>> This update contains a lot of updates and changes including *an entire 
>>> rewrite of the Highcharts system* which allows you to make almost any 
>>> graph you want for almost any time span you want. You can see some examples 
>>> of the charts you can make on the BelchertownWeather.com website graphs 
>>> page .
>>>
>>> You can add/remove/change/reorder any chart, change colors, add 
>>> observation plots, categorize for all time. Almost anything you want to do 
>>> is available! The skin comes with the standard 4 charts ready to go, but 
>>> there's extensive Belchertown Charts Documentation 
>>> 
>>>  
>>> which can help you get started. 
>>>
>>> In addition to the Charts there's now a dark mode (which has an 
>>> auto-switching mode based on sunset/sunrise), more flexibility for 
>>> translations, user customized station observation table which is updated in 
>>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>>> release notes for all the details! 
>>>
>>> You can download the latest release here 
>>> ,
>>>  
>>> and read all of the details on the changes here: 
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>>> uninstall everything and reinstall new. This is due to the Chart system 
>>> being fully rewritten and the potential for conflicts. Please read this 
>>> upgrade guide if you are upgrading from an older version of Belchertown 
>>> skin 
>>> 
>>> . 
>>>
>>> Thanks to all the beta testers and translators over the last couple of 
>>> months help me iron out all the kinks and shape the skin in a way that can 
>>> be translated a little easier! 
>>>
>>> Attached are some examples of the charts that can be made. If you find 
>>> any issues, you can reply here or open an issue on the Belchertown skin 
>>> GitHub page . 
>>>
>>

-- 
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/76e3000e-b564-460f-abe9-609b38670a51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Juan Antonio Mosquera]

This problem is in weewx.conf 

installation crash this file backup is necesary!

Greetings.

El lunes, 3 de junio de 2019, 20:35:12 (UTC+2), Juan Antonio Mosquera 
escribió:
>
> Hi...
>
> rare... i had 1.0 version... i update... and...
>
> jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
> exception in engine:
> jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
> jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most recent 
> call last):
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 884, in main
> jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
> engine_class(config_dict)
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
> jun 03 20:30:43 meteomontaos weewx[4029]:   
> self.loadServices(config_dict)
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> jun 03 20:30:43 meteomontaos weewx[4029]:   
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/share/weewx/weewx/engine.py", line 304, in __init__
> jun 03 20:30:43 meteomontaos weewx[4029]:   
> target_unit_nickname = config_dict['StdConvert']['target_unit']
> jun 03 20:30:43 meteomontaos weewx[4029]: File 
> "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
> jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
> dict.__getitem__(self, key)
> jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 'StdConvert'
> jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.
>
>
> what problem¿?
>
> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>
>> Belchertown skin 1.0 is released!
>>
>> This update contains a lot of updates and changes including *an entire 
>> rewrite of the Highcharts system* which allows you to make almost any 
>> graph you want for almost any time span you want. You can see some examples 
>> of the charts you can make on the BelchertownWeather.com website graphs 
>> page .
>>
>> You can add/remove/change/reorder any chart, change colors, add 
>> observation plots, categorize for all time. Almost anything you want to do 
>> is available! The skin comes with the standard 4 charts ready to go, but 
>> there's extensive Belchertown Charts Documentation 
>> 
>>  
>> which can help you get started. 
>>
>> In addition to the Charts there's now a dark mode (which has an 
>> auto-switching mode based on sunset/sunrise), more flexibility for 
>> translations, user customized station observation table which is updated in 
>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>> release notes for all the details! 
>>
>> You can download the latest release here 
>> ,
>>  
>> and read all of the details on the changes here: 
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>> uninstall everything and reinstall new. This is due to the Chart system 
>> being fully rewritten and the potential for conflicts. Please read this 
>> upgrade guide if you are upgrading from an older version of Belchertown skin 
>> 
>> . 
>>
>> Thanks to all the beta testers and translators over the last couple of 
>> months help me iron out all the kinks and shape the skin in a way that can 
>> be translated a little easier! 
>>
>> Attached are some examples of the charts that can be made. If you find 
>> any issues, you can reply here or open an issue on the Belchertown skin 
>> GitHub page . 
>>
>

-- 
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/6ef9c708-32c5-4fab-a281-4060dc2d71b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Juan Antonio Mosquera]

Hi...

rare... i had 1.0 version... i update... and...

jun 03 20:30:43 meteomontaos weewx[4029]: engine: Caught unrecoverable 
exception in engine:
jun 03 20:30:43 meteomontaos weewx[4029]:   'StdConvert'
jun 03 20:30:43 meteomontaos weewx[4029]:   Traceback (most recent 
call last):
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 884, in main
jun 03 20:30:43 meteomontaos weewx[4029]:   engine = 
engine_class(config_dict)
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
jun 03 20:30:43 meteomontaos weewx[4029]:   
self.loadServices(config_dict)
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
jun 03 20:30:43 meteomontaos weewx[4029]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/share/weewx/weewx/engine.py", line 304, in __init__
jun 03 20:30:43 meteomontaos weewx[4029]:   
target_unit_nickname = config_dict['StdConvert']['target_unit']
jun 03 20:30:43 meteomontaos weewx[4029]: File 
"/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__
jun 03 20:30:43 meteomontaos weewx[4029]:   val = 
dict.__getitem__(self, key)
jun 03 20:30:43 meteomontaos weewx[4029]:   KeyError: 'StdConvert'
jun 03 20:30:43 meteomontaos weewx[4029]:   Exiting.


what problem¿?

El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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/2dc9c929-26b6-4e6c-8b9b-5e20d38278b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[vince]

On Monday, June 3, 2019 at 10:23:04 AM UTC-7, Joe Santas wrote:
>
> Awesome release well done.  Quick question im up and running all good.  I 
> have a Darksky key and have the 8 day forecasts showing but they are 
> incorrect.  Im assuming a location issue.  Where can i change this?
>
>
>
check your lat/lon in weewx.conf

-- 
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/15607a94-98ae-46d6-a409-a0be75aa607b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Joe Santas]

Awesome release well done.  Quick question im up and running all good.  I 
have a Darksky key and have the 8 day forecasts showing but they are 
incorrect.  Im assuming a location issue.  Where can i change this?

Regards


On Sunday, June 2, 2019 at 2:57:56 AM UTC+10, Pat wrote:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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/919952f4-d4fe-4917-95af-bbed3540668d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: [ANNOUNCE] weewx-aqi: A Plugin for Air Quality Index Calculations

[Hartmut Schweidler]

thank you for the information.

I will test it on the weekend

Thank you
Hartmut

-- 
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/8ab638a7-e3f8-4764-9823-c68f84f3f06b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] locale in user/extensions.py failed

[Thomas Keffer]

I would guess that your RPi does not have a  default locale set. To see
what locales it has been set to, use a simple "locale" command. Here's what
I get:

pi@RPi-bug ~ $ *locale*
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

The easiest way to set a default locale is to use dpkg-reconfigure:

$ *sudo dpkg-reconfigure locales*

-tk

On Mon, Jun 3, 2019 at 7:14 AM Chris Richmond  wrote:

> I'm sure this is simply, but I'm setting up a new RPi for a VantageVue and
> tweaking extensions.py to check for good time.
> When I ran this stand-alone, locale.setlocale(locale.LC_ALL, '') failed.
>
> pi2c_/home/weewx/bin/user> python
> Python 2.7.13 (default, Sep 26 2018, 18:42:22)
> [GCC 6.3.0 20170516] on linux2
> >>> import locale
> >>> locale.setlocale(locale.LC_ALL, '')
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python2.7/locale.py", line 581, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
> >>> locale.setlocale(locale.LC_ALL, 'C')
> 'C'
> >>>
>
> And from searching:
> pi2c_/home/weewx/bin/user> locale -a
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_MESSAGES to default locale: No such file or directory
> locale: Cannot set LC_COLLATE to default locale: No such file or directory
> C
> C.UTF-8
> POSIX
> en_US.utf8
>
> So something is missing from the RPi itself that causes a weewxd failure.
> Setting the value to 'C' does work, but an empty string does not.  I had
> other
> wierd redraw problems with vim of all things and ended up with these in my
> .cshrc:
> setenv LANG ASCII
> setenv LC_ALL ASCII
> setenv LANGUAGE ASCII
>
> Chris
>
> --
> 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/3f955101-2645-4c59-a858-b996ba61c087%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPq0zEAsLtQSD_hU7SoZsh8Tgt2ZZEJLC3ZKRK_yiWv7Vv4KRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] locale in user/extensions.py failed

[Chris Richmond]

I'm sure this is simply, but I'm setting up a new RPi for a VantageVue and 
tweaking extensions.py to check for good time.
When I ran this stand-alone, locale.setlocale(locale.LC_ALL, '') failed.

pi2c_/home/weewx/bin/user> python
Python 2.7.13 (default, Sep 26 2018, 18:42:22) 
[GCC 6.3.0 20170516] on linux2
>>> import locale
>>> locale.setlocale(locale.LC_ALL, '')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/locale.py", line 581, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
>>> locale.setlocale(locale.LC_ALL, 'C')
'C'
>>> 

And from searching:
pi2c_/home/weewx/bin/user> locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
C.UTF-8
POSIX
en_US.utf8

So something is missing from the RPi itself that causes a weewxd failure.
Setting the value to 'C' does work, but an empty string does not.  I had 
other
wierd redraw problems with vim of all things and ended up with these in my 
.cshrc:
setenv LANG ASCII
setenv LC_ALL ASCII
setenv LANGUAGE ASCII

Chris

-- 
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/3f955101-2645-4c59-a858-b996ba61c087%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: have a prob with a not loaded or installed Python package

[gjr80]

OK, so requests is installed and python can find it. Let's try running 
WeeWX directly  
rather than as a daemon. Try:

$ sudo /home/weewx/bin/weewxd /home/weewx/weewx.conf

Does that display any error on the console or in the log? Your log output 
should be in /var/log/syslog unless you have changed it. If there are any 
errors (console or log) post them back here.

Also, is it possible to capture the console output as text and post it 
rather than posting screen capture images, screen capture images are rather 
difficult to read at times on a mobile device.

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/ec1373e7-3a19-4a66-a158-01dfb50557e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: have a prob with a not loaded or installed Python package

[Dirk]

yes worked


Am Montag, 3. Juni 2019 14:26:56 UTC+2 schrieb gjr80:
>
> OK, so what happens if you launch a python shell and try to import 
> requests, eg:
>
> $ python
> >>>import requests
>
> Is requests found?
>
> Gary
>
> On Monday, 3 June 2019 22:14:15 UTC+10, Dirk wrote:
>>
>> @Gary, all the stuff iss installed on my Raspi,  
>>
>> $ sudo pip install requests
>> $ sudo pip install python-dateutil
>>
>> and all what here is writen:
>> http://weewx.com/docs/setup.htm
>>
>> the prob is that weeutil, cannot import these librarys and in these way i 
>> have found a way to install it with setup.py, but it dosent work.
>> I have in the moment no idea why these not work and we i can add the 2 
>> additional librarys in the weewx-container that my extension will work.
>>
>>

-- 
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/54d892f7-d611-476a-92d6-29f4a3128804%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: have a prob with a not loaded or installed Python package

[gjr80]

OK, so what happens if you launch a python shell and try to import 
requests, eg:

$ python
>>>import requests

Is requests found?

Gary

On Monday, 3 June 2019 22:14:15 UTC+10, Dirk wrote:
>
> @Gary, all the stuff iss installed on my Raspi,  
>
> $ sudo pip install requests
> $ sudo pip install python-dateutil
>
> and all what here is writen:
> http://weewx.com/docs/setup.htm
>
> the prob is that weeutil, cannot import these librarys and in these way i 
> have found a way to install it with setup.py, but it dosent work.
> I have in the moment no idea why these not work and we i can add the 2 
> additional librarys in the weewx-container that my extension will work.
>
>

-- 
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/f2e61bde-6d0e-473f-99c7-24aa3d44d18e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: have a prob with a not loaded or installed Python package

[Dirk]

@Gary, all the stuff iss installed on my Raspi,  

$ sudo pip install requests
$ sudo pip install python-dateutil

and all what here is writen:
http://weewx.com/docs/setup.htm

the prob is that weeutil, cannot import these librarys and in these way i have 
found a way to install it with setup.py, but it dosent work.
I have in the moment no idea why these not work and we i can add the 2 
additional librarys in the weewx-container that my extension will work.

-- 
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/0cb4994c-7768-480b-be04-2985af6a6254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

To uninstall the skin you can run the wee_extension --uninstall Belchertown 
command. Then just look in your skins folder for anything left behind, and 
your bin/user folder for anything left behind. Then just a quick check of 
the weewx.conf for anything left behind. Then try again with the 
wee_extension --install command to reinstall it. 

Though I'm not sure you need to go that route, nor reinstalling weewx 
either. If you don't have a backup of weewx.conf, you can compare yours to 
the base install one which can be found here 
. There's probably a 
line in StdReport or something that got removed by mistake. 


On Monday, June 3, 2019 at 7:52:24 AM UTC-4, Andy Hudson-Smith wrote:
>
> Its an experimental set up and i think i must have deleted something tbh - 
> not worried about the data though - would a fresh install make sense - if 
> so is there an easy route to delete/reinstall?
>
> Sorry!
>
> Andy
>
> On Monday, 3 June 2019 12:50:08 UTC+1, Pat wrote:
>>
>> Nothing else was listed in the syslog output? Based on what you have here 
>> it doesn't look like the skin is even running yet - so there's something 
>> else going on. Check your backup (hopefully you have one, I advised it in 
>> my instructions) and see if you deleted something by mistake?
>>
>> On Monday, June 3, 2019 at 6:21:51 AM UTC-4, Andy Hudson-Smith wrote:
>>>
>>> Not quite sure what i have done wrong tbh - but ran through the upgrade 
>>> instructions and weewx no longer seems to start?
>>>
>>> status comes up with
>>>
>>> Jun 03 11:14:51 weewx systemd[1]: Started LSB: weewx weather system.
>>> Jun 03 11:14:51 weewx weewx[434]: engine: Error while parsing 
>>> configuration file
>>> Jun 03 11:14:51 weewx weewx[434]: Reason: 'Parsing failed with 
>>> several e
>>>   First error at line 184.'
>>>
>>> I know this is vague so any idea of where to start would be great...
>>>
>>> Andy
>>>
>>>

-- 
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/800d27ac-a8d3-4613-9781-7379e83862e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

['Andy Hudson-Smith' via weewx-user]

Its an experimental set up and i think i must have deleted something tbh - 
not worried about the data though - would a fresh install make sense - if 
so is there an easy route to delete/reinstall?

Sorry!

Andy

On Monday, 3 June 2019 12:50:08 UTC+1, Pat wrote:
>
> Nothing else was listed in the syslog output? Based on what you have here 
> it doesn't look like the skin is even running yet - so there's something 
> else going on. Check your backup (hopefully you have one, I advised it in 
> my instructions) and see if you deleted something by mistake?
>
> On Monday, June 3, 2019 at 6:21:51 AM UTC-4, Andy Hudson-Smith wrote:
>>
>> Not quite sure what i have done wrong tbh - but ran through the upgrade 
>> instructions and weewx no longer seems to start?
>>
>> status comes up with
>>
>> Jun 03 11:14:51 weewx systemd[1]: Started LSB: weewx weather system.
>> Jun 03 11:14:51 weewx weewx[434]: engine: Error while parsing 
>> configuration file
>> Jun 03 11:14:51 weewx weewx[434]: Reason: 'Parsing failed with 
>> several e
>>   First error at line 184.'
>>
>> I know this is vague so any idea of where to start would be great...
>>
>> Andy
>>
>>

-- 
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/e6eff4e9-9e73-4ba6-9798-b1ee04356356%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

Nothing else was listed in the syslog output? Based on what you have here 
it doesn't look like the skin is even running yet - so there's something 
else going on. Check your backup (hopefully you have one, I advised it in 
my instructions) and see if you deleted something by mistake?

On Monday, June 3, 2019 at 6:21:51 AM UTC-4, Andy Hudson-Smith wrote:
>
> Not quite sure what i have done wrong tbh - but ran through the upgrade 
> instructions and weewx no longer seems to start?
>
> status comes up with
>
> Jun 03 11:14:51 weewx systemd[1]: Started LSB: weewx weather system.
> Jun 03 11:14:51 weewx weewx[434]: engine: Error while parsing 
> configuration file
> Jun 03 11:14:51 weewx weewx[434]: Reason: 'Parsing failed with 
> several e
>   First error at line 184.'
>
> I know this is vague so any idea of where to start would be great...
>
> Andy
>
>

-- 
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/a70a1408-0555-4d4b-bf8f-aa85e18044ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

['Andy Hudson-Smith' via weewx-user]

 

Its in the StdReport section - line 184 is marked below with a star  - (?)


[StdReport]


# Where the skins reside, relative to WEEWX_ROOT

SKIN_ROOT = /etc/weewx/skins


# Where the generated reports should go, relative to WEEWX_ROOT

HTML_ROOT = /var/weewx/reports


*   # The database binding indicates which data should be used in reports.

data_binding = wx_binding


[[SeasonsReport]]

# The SeasonsReport uses the 'Seasons' skin, which contains the

# images, templates and plots for the report.

skin = Seasons

enable = false

On Monday, 3 June 2019 11:35:30 UTC+1, Andrew Milner wrote:
>
> I would start looking around line 184 of weewx.conf and see if you can 
> spot the issue.  The error message is very precise - so start looking where 
> the message tells you to look
>
>
>
> On Monday, 3 June 2019 13:21:51 UTC+3, Andy Hudson-Smith wrote:
>>
>> Not quite sure what i have done wrong tbh - but ran through the upgrade 
>> instructions and weewx no longer seems to start?
>>
>> status comes up with
>>
>> Jun 03 11:14:51 weewx systemd[1]: Started LSB: weewx weather system.
>> Jun 03 11:14:51 weewx weewx[434]: engine: Error while parsing 
>> configuration file
>> Jun 03 11:14:51 weewx weewx[434]: Reason: 'Parsing failed with 
>> several e
>>   First error at line 184.'
>>
>> I know this is vague so any idea of where to start would be great...
>>
>> Andy
>>
>>

-- 
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/17a956cc-097d-4c99-8fb0-374657026acc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

[Andrew Milner]

I would start looking around line 184 of weewx.conf and see if you can spot 
the issue.  The error message is very precise - so start looking where the 
message tells you to look



On Monday, 3 June 2019 13:21:51 UTC+3, Andy Hudson-Smith wrote:
>
> Not quite sure what i have done wrong tbh - but ran through the upgrade 
> instructions and weewx no longer seems to start?
>
> status comes up with
>
> Jun 03 11:14:51 weewx systemd[1]: Started LSB: weewx weather system.
> Jun 03 11:14:51 weewx weewx[434]: engine: Error while parsing 
> configuration file
> Jun 03 11:14:51 weewx weewx[434]: Reason: 'Parsing failed with 
> several e
>   First error at line 184.'
>
> I know this is vague so any idea of where to start would be great...
>
> Andy
>
>

-- 
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/daf5124f-f901-4075-9f60-67bea7f5df39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin 1.0 released!

['Andy Hudson-Smith' via weewx-user]

Not quite sure what i have done wrong tbh - but ran through the upgrade 
instructions and weewx no longer seems to start?

status comes up with

Jun 03 11:14:51 weewx systemd[1]: Started LSB: weewx weather system.
Jun 03 11:14:51 weewx weewx[434]: engine: Error while parsing configuration file
Jun 03 11:14:51 weewx weewx[434]: Reason: 'Parsing failed with several e
  First error at line 184.'

I know this is vague so any idea of where to start would be great...

Andy

-- 
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/774ac809-c04f-4bd9-9046-9d86e25f8f3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: [ANNOUNCE] weewx-aqi: A Plugin for Air Quality Index Calculations

[jonathan koren]

Actually, you should use this one: 
https://github.com/jonathankoren/weewx-aqi/archive/v1.1.1.tar.gz

On Sunday, June 2, 2019 at 11:06:46 PM UTC-7, jonathan koren wrote:
>
>
> I had to push version but the solution is pretty easy. You can download 
> the new version from 
> https://github.com/jonathankoren/weewx-aqi/archive/v1.1.0.tar.gz
>
> You can either reinstall the whole thing, but the two files that got 
> modified were service.py and calculators.py, so you can just drop those in 
> if you want. Nothing else changed beyond the README.md . 
>
> Inside your skin.conf you'll need to add a new SearchList:
>
> [CheetahGenerator]
> search_list_extensions = user.aqi.service.AqiSearchList
>
>
> Then, inside your index.html.tmpl. you can use the new $aqi template to 
> get the color and description out.
>
>
> The AQI value (e.g. "9"): 
> $current($data_binding='aqi_binding').aqi_pm2_5
>
> The AQI category: 
>
> $aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).category
>
>
> The AQI category's color in hex:
>
> $aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).color;
>
>
>
> Putting everything together, you can do something like:
>
> 
> $current($data_binding='aqi_binding').aqi_pm2_5 
> $aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).category
> 
>
>
> Sorry this took a code change, but your email did give the motivation I 
> needed to fix this.
>
> I guess, I should wrap up the EU AQI calculator, even if I'm having 
> trouble getting it to download CAMS data to fill in missing values.
>
> On Friday, May 31, 2019 at 1:00:36 AM UTC-7, jonathan koren wrote:
>>
>>
>> Honestly, that’s pretty hard to get that to work if I remember correctly. 
>> It’s not very cheetah template friendly. I haven’t looked at this in a 
>> while, but let me take a look at it this weekend.
>>
>> On Thursday, May 30, 2019 at 1:20:15 AM UTC-7, Hartmut Schweidler wrote:
>>>
>>> Hallo,
>>>
>>> I'm looking for an example in aqi.html.tmpl
>>>
>>> like "AQIs have categorical labels associated with the AQI values. The 
>>> index of the current category is available via 
>>> $latest('aqi_binding').aqi_pm2_5_category. From this, the label and 
>>> color category can be found via (hex_color, category_label) = 
>>> service.aqi_standard.interpret_aqi_index(index)"
>>>
>>> ich suche nach einem Beispiel für die Verwendung der Farben in einer 
>>> AQI-Seite
>>>
>>> Hartmut
>>>
>>

-- 
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/3bdce2c4-3f3e-46b7-aad9-d95f6a63f579%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: [ANNOUNCE] weewx-aqi: A Plugin for Air Quality Index Calculations

[jonathan koren]

I had to push version but the solution is pretty easy. You can download the 
new version from 
https://github.com/jonathankoren/weewx-aqi/archive/v1.1.0.tar.gz

You can either reinstall the whole thing, but the two files that got 
modified were service.py and calculators.py, so you can just drop those in 
if you want. Nothing else changed beyond the README.md . 

Inside your skin.conf you'll need to add a new SearchList:

[CheetahGenerator]
search_list_extensions = user.aqi.service.AqiSearchList


Then, inside your index.html.tmpl. you can use the new $aqi template to get 
the color and description out.


The AQI value (e.g. "9"): 
$current($data_binding='aqi_binding').aqi_pm2_5

The AQI category: 

$aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).category


The AQI category's color in hex:

$aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).color;



Putting everything together, you can do something like:


$current($data_binding='aqi_binding').aqi_pm2_5 
$aqi($current($data_binding='aqi_binding').aqi_pm2_5_category).category



Sorry this took a code change, but your email did give the motivation I 
needed to fix this.

I guess, I should wrap up the EU AQI calculator, even if I'm having trouble 
getting it to download CAMS data to fill in missing values.

On Friday, May 31, 2019 at 1:00:36 AM UTC-7, jonathan koren wrote:
>
>
> Honestly, that’s pretty hard to get that to work if I remember correctly. 
> It’s not very cheetah template friendly. I haven’t looked at this in a 
> while, but let me take a look at it this weekend.
>
> On Thursday, May 30, 2019 at 1:20:15 AM UTC-7, Hartmut Schweidler wrote:
>>
>> Hallo,
>>
>> I'm looking for an example in aqi.html.tmpl
>>
>> like "AQIs have categorical labels associated with the AQI values. The 
>> index of the current category is available via 
>> $latest('aqi_binding').aqi_pm2_5_category. From this, the label and 
>> color category can be found via (hex_color, category_label) = 
>> service.aqi_standard.interpret_aqi_index(index)"
>>
>> ich suche nach einem Beispiel für die Verwendung der Farben in einer 
>> AQI-Seite
>>
>> Hartmut
>>
>

-- 
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/5b6932ab-dff2-406e-ba21-f4c20a9476aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.