[weewx-user] Re: Having yesterday's rain listed right under Rain Rate, Rain Today in the Current Conditions section

[Dale Reid]

Just a follow up note to thank Paul and others for information and after I 
added the two lines of instructions, plus had rain two days in a row, found 
things work very well.  Thanks.  Dale

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ef73c68b-26cf-4936-abb0-9ba41f79d80do%40googlegroups.com.

Re: [weewx-user] Cydia pomonella

[Tom Keffer]

Thank you for your thoughtful letter!

Two things come to mind:

First, "growing degree days
" is now a
first-class type, analogous to heating- and cooling-degree days.

Second, see issue #341 , which
discusses support for generating JSON series using the Cheetah generator.
The intention was to use these series to drive things like Highchart plots.
Nothing much has happened to the issue recently (it's nearly 2 years old),
but perhaps this is what you had in mind?

On Mon, Jun 22, 2020 at 10:37 AM Chuck Rhode 
wrote:

> A couple of years ago, I developed growing-degree-day graphs to display
> codling moth development using *weeWX*.
>
> o http://lacusveris.com/cydia/index.shtml
>
> I've been lurking on the weewx-user@googlegroups.com mailing list
> since then.  Now, I'm finally ready to upgrade to *weeWX 4*, but I
> have some embroidery on the *python 2* code that I need to migrate to
> *python 3*.  The magnitude of this task causes me to rethink my
> two-year-old approach.
>
> I cloned weeWX's *ImageGenerator* to access its own database, do its
> own growing-degree-day calculations, and generate its own Python
> Imaging Lib (PIL) images.  This was not easy, but it was good enough
> ... then.
>
> Today, I'm bedeviled by notions that perhaps a more general approach
> would be nearly as easy (or hard) to achieve and might find utility
> for other *weeWX* applications.  I guess you'd say I've fallen in love
> with *cheetah* and have taken to looking at all problems as templating
> applications.  (Full disclosure: I seem to recall that, in a previous
> life, I was a SPERRY (Univac/UNiSYS) *SKEL* programmer.)
>
> ... so I ask this somewhat rhetorical question:
>
> Has there been any discussion about templating image generation
> through *cheetah*?
>
> I don't recall seeing any such discussion although I've seen some talk
> about others' frustrations with the limitations of *ImageGenerator*
> that mirror my own.  Apparently the limitation of not being able to
> draw y-axis horizons has been lifted in *weeWX 4*, but limitations
> such as not being able to apply a second y-axis have not.  To be sure,
> these limitations do not wreck the whole notion of *weeWX* or prevent
> users' workarounds like mine.  On the other hand, they are examples
> only and surely don't exhaust the kinds of drawings that
> *ImageGenerator* in particular and PIL in general are NOT suited to.
>
> In my mind templating is for text only, so I'm mystified by what I'm
> asking.  I can't feature what an imaging template would look like.
>
> On the other hand, I'm attracted to the notion of providing the
> growing-degree-day calculations through *get_extension_list* for use
> by *cheetah* in templates for ... generating images.
>
> o Perhaps images could be conjured in real-time using something like
>   Google Chart's Visualization JavaScript APIs.  Embedding the
>   JavaScript (and data) in *cheetah* templates should be
>   straightforward.  This relies on (an indeterminate amount of) client
>   horsepower being available to conjure the images.  Also, the host
>   site will wish to serve the (huge burden of) JavaScript on every
>   access to avoid the appearance of cross-site scripting if possible.
>   And it makes any such application dependent on a big, fickle outside
>   software-development organization, which will be forever totally
>   oblivious of the needs of the *weeWX* community among others.
>
> o Perhaps images could be conjured ahead of time as they are now using
>   a *python* script, but the script itself would be a *cheetah*
>   template.  This would allow specially calculated data to be
>   embedded.  Images could then be uploaded and served to all comers
>   without further modification until the next generation cycle with
>   great savings of client-side and server-side resources.
>
>   I'm not talking here about a generalized image-scripting language,
>   but a *python* module that imports some handy special-purpose
>   classes to make *weeWX* image generation fairly terse.  Of course,
>   images are deceptively simple things that hide excruciatingly
>   detailed specs.  Templating images will not be easy.  It will not
>   replace *ImageGenerator*, nor will it ever be for the
>   faint-of-heart.
>
>   I think generating a *python* image-generation script from *cheetah*
>   has the advantage, though, of abstracting image generation from the
>   database structure, reporting cycles, and *weeWX* implementation
>   details.  It would promote *weeWX* extensibility.  Also, it opens
>   the possibility of using plotting packages other than PIL.  My
>   inclination is to use *matplotlib* instead.  Would those who have
>   used both recommend something else?
>
> > If you can looke into the Seedes of Time,
> > And say, which Graine will grow, and which will not,
> > Speake then to me, who neyther begge, nor feare
> > Your fauors, nor 

Re: [weewx-user] Re: Full day highcharts question

[Pat]

Change your aggregate_interval to match your gapSize and see if that helps. 

On Monday, June 22, 2020 at 7:05:00 PM UTC-4, Didier Decoodt wrote:
>
> Oupss
> It seems to be correct but the aggregate_interval is not correct, every 5 
> mn instead of 1 day for monthly graphic...
> aggregate_type=none is not appropriate...
> (with  aggregate_type=last the curve continue after "now")
> I think the problem is linked with rainTotal variable, 
>
> Le lun. 22 juin 2020 à 22:18, Didier Decoodt  > a écrit :
>
>> Thanks for this documentation
>>
>> Le lun. 22 juin 2020 à 21:10, Pat > a 
>> écrit :
>>
>>> rain total works? That's good though I don't know how! :)
>>>
>>> For the aggregates, Belchertown borrows that from weewx's Seasons and 
>>> Standard skins. Here's more information from their documentation 
>>> . 
>>>
>>> On Monday, June 22, 2020 at 2:47:40 PM UTC-4, Didier Decoodt wrote:

 Pat, I put aggregate_type = none instead of max, and it's work!!!
 I don't really understand aggregate_type effect
 differences between none, sum, min, max and avg?
 [image: image.png]

 Le lun. 22 juin 2020 à 19:40, Pat  a écrit :

>>> I raised this as an issue and 
> Tom mentioned for the day charts you should probably be using last as the 
> aggregate, not max. 
>
> I'll look into rainTotal since that's a Belchertown observation. 
>
>
> On Friday, June 19, 2020 at 2:02:44 PM UTC-4, Pat wrote:
>>
>> No, not sure. I assume it's because the data points aren't reset to 
>> "None" using this new way of getting data for the rain observation?
>>
>> Gary - did you create an issue for this? I'd hate to patch something 
>> in the skin to only undo it if/when Tom properly patches this.
>>
>> On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com 
>> wrote:
>>>
>>> Oh, just a small problem:
>>> For Rain graph, the curve continue after "now"! (screenshot attached)
>>> All others curves stop at datetime=now, it's correct)
>>> The problem concern "rainTotal" and is also available for day, week, 
>>> month and year time_length
>>> Have you an idea?
>>>
>>> hereafter the part of grah.conf
>>>
>>> [week]
>>> # Chart Timespan Defaults
>>> title = "Cette semaine"
>>> show_button = true
>>> button_text = "SEMAINE"
>>> time_length = week
>>> tooltip_date_format = ""
>>> type = spline
>>> aggregate_type = max
>>> aggregate_interval = 3600 # 1 hour
>>> gapsize = 360 # 1 hour in milliseconds
>>>
>>> [[chart1]]
>>> title = Température
>>> [[[outTemp]]]
>>> color = "#b2df8a"
>>> [[[dewpoint]]]
>>> yAxis_label = ( °C )
>>> yAxis_tickInterval = 2
>>> yAxis_softMin = 0
>>> 
>>> [[chart2]]
>>> title = Pluie
>>> [[[rainTotal]]]  < 
>>> Problem
>>> color = "#f7a35c"
>>> name = Cumul
>>> [[[rain]]]
>>> color = "#268bd2"
>>> aggregate_type = sum
>>> name = pluie
>>> type = column
>>> yAxis_tickInterval = 1
>>> yAxis_label = ( mm )
>>> yAxis_min = 0
>>>
>>>
>>> Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :
>>>
 Awesome! Glad that it worked for you


 On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com 
 wrote:
>
> Thanks it's work 
>
>
> Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :
>
>> Thanks, Gary, for this comprehensive explanation.
>>
>> Based on what you wrote I was now able to plot an entire day.
>>
>> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>>
>> The trick is quite simple: I just had to define an aggregation 
>> for the daily charts. I.e. adding the following two lines to the 
>> graphs.conf:
>>
>> aggregate_type = max
>>
>> aggregate_interval = 300
>>
>>
>>
>> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
>
 To unsubscribe from this group and stop receiving emails from it, send 
> an email to weewx...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/35aa4d91-2dd6-4fc5-882d-78ddfd99c18co%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this 

Re: [weewx-user] Monthly Summaries are empty

[John Pierce]

On Mon, Jun 22, 2020 at 4:51 AM Tom Keffer  wrote:

> This is a known problem with v4.1.0. An upgrade to V4.1.1 will fix you up.
>
> After the upgrade, delete all your NOAA files and let WeeWX
> regenerate them.
>

so I was already on 4.1.1...


well, I stopped weewx, deleted /var/weewx/reports/NOAA/*.txt, and restarted
weewx, and still no-go on those summaries...  The current month is
partially populated as expected, but all previous months are empty.

https://freescruz.com/weewx/tabular.html?report=NOAA/NOAA-2020-05.txtas
an example of said previous month.

ditto current year is partially populated, but the prior years since i
started running weewx are empty.






-- 
-john r pierce
  recycling used bits in santa cruz

-- 
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/CAJnkzX%2B%2BA_Q%2BOy%2BOMfJhMROiPmoy4LWDDRWup6VS80LmeHJ3WQ%40mail.gmail.com.

Re: [weewx-user] Re: Full day highcharts question

[Didier Decoodt]

Oupss
It seems to be correct but the aggregate_interval is not correct, every 5
mn instead of 1 day for monthly graphic...
aggregate_type=none is not appropriate...
(with  aggregate_type=last the curve continue after "now")
I think the problem is linked with rainTotal variable,

Le lun. 22 juin 2020 à 22:18, Didier Decoodt  a
écrit :

> Thanks for this documentation
>
> Le lun. 22 juin 2020 à 21:10, Pat  a écrit :
>
>> rain total works? That's good though I don't know how! :)
>>
>> For the aggregates, Belchertown borrows that from weewx's Seasons and
>> Standard skins. Here's more information from their documentation
>> .
>>
>> On Monday, June 22, 2020 at 2:47:40 PM UTC-4, Didier Decoodt wrote:
>>>
>>> Pat, I put aggregate_type = none instead of max, and it's work!!!
>>> I don't really understand aggregate_type effect
>>> differences between none, sum, min, max and avg?
>>> [image: image.png]
>>>
>>> Le lun. 22 juin 2020 à 19:40, Pat  a écrit :
>>>
>> I raised this as an issue and
 Tom mentioned for the day charts you should probably be using last as the
 aggregate, not max.

 I'll look into rainTotal since that's a Belchertown observation.


 On Friday, June 19, 2020 at 2:02:44 PM UTC-4, Pat wrote:
>
> No, not sure. I assume it's because the data points aren't reset to
> "None" using this new way of getting data for the rain observation?
>
> Gary - did you create an issue for this? I'd hate to patch something
> in the skin to only undo it if/when Tom properly patches this.
>
> On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com
> wrote:
>>
>> Oh, just a small problem:
>> For Rain graph, the curve continue after "now"! (screenshot attached)
>> All others curves stop at datetime=now, it's correct)
>> The problem concern "rainTotal" and is also available for day, week,
>> month and year time_length
>> Have you an idea?
>>
>> hereafter the part of grah.conf
>>
>> [week]
>> # Chart Timespan Defaults
>> title = "Cette semaine"
>> show_button = true
>> button_text = "SEMAINE"
>> time_length = week
>> tooltip_date_format = ""
>> type = spline
>> aggregate_type = max
>> aggregate_interval = 3600 # 1 hour
>> gapsize = 360 # 1 hour in milliseconds
>>
>> [[chart1]]
>> title = Température
>> [[[outTemp]]]
>> color = "#b2df8a"
>> [[[dewpoint]]]
>> yAxis_label = ( °C )
>> yAxis_tickInterval = 2
>> yAxis_softMin = 0
>>
>> [[chart2]]
>> title = Pluie
>> [[[rainTotal]]]  < Problem
>> color = "#f7a35c"
>> name = Cumul
>> [[[rain]]]
>> color = "#268bd2"
>> aggregate_type = sum
>> name = pluie
>> type = column
>> yAxis_tickInterval = 1
>> yAxis_label = ( mm )
>> yAxis_min = 0
>>
>>
>> Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :
>>
>>> Awesome! Glad that it worked for you
>>>
>>>
>>> On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com
>>> wrote:

 Thanks it's work 


 Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :

> Thanks, Gary, for this comprehensive explanation.
>
> Based on what you wrote I was now able to plot an entire day.
>
> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>
> The trick is quite simple: I just had to define an aggregation for
> the daily charts. I.e. adding the following two lines to the 
> graphs.conf:
>
> aggregate_type = max
>
> aggregate_interval = 300
>
>
>
> --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.

>>> To unsubscribe from this group and stop receiving emails from it, send
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/35aa4d91-2dd6-4fc5-882d-78ddfd99c18co%40googlegroups.com
 
 .

>>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> 

Re: [weewx-user] Re: No solar reading from Davis Vantage Pro2

[peter]

The solar radiation disappeared after a few hours. I stopped weewx and ran 
it manually according to instructions.
I do get "REC" and "LOOP" packets none of which contain "radiation".

This is an example output (apologies for creating a long post).

> LOOP:   2020-06-22 22:46:13 CEST (1592858773) altimeter: 30.0073613589, 
> appTemp: 74.7712992355, barometer: 30.006, cloudbase: 5542.93514687, 
> consBatteryVoltage: 1.59, dateTime: 1592858773, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 51.0494853538, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 6, forecastRule: 75, heatindex: 74.4, 
> humidex: 77.1941299914, inDewpoint: 58.9079078442, inHumidity: 53.0, 
> insideAlarm: 0, inTemp: 77.4, leafWet4: 0.0, maxSolarRad: 0.0, monthET: 
> 0.27, monthRain: 8.10236220675, outHumidity: 44.0, outsideAlarm1: 0, 
> outsideAlarm2: 0, outTemp: 74.4, pressure: 29.7612224179, rain: 0.0, 
> rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
> soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1592795760, 
> sunset: 1592852400, trendIcon: 20, txBatteryStatus: 1, usUnits: 1, 
> windchill: 74.4, windDir: None, windGust: 1.0, windGustDir: 44.0, 
> windSpeed: 0.0, windSpeed10: 0.0, yearET: 15.06, yearRain: 19.7952755955
> LOOP:   2020-06-22 22:46:15 CEST (1592858775) altimeter: 30.0073613589, 
> appTemp: 74.2080302355, barometer: 30.006, cloudbase: 5542.93514687, 
> consBatteryVoltage: 1.59, dateTime: 1592858775, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 51.0494853538, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, forecastIcon: 6, forecastRule: 75, heatindex: 74.4, 
> humidex: 77.1941299914, inDewpoint: 58.9079078442, inHumidity: 53.0, 
> insideAlarm: 0, inTemp: 77.4, leafWet4: 0.0, maxSolarRad: 0.0, monthET: 
> 0.27, monthRain: 8.10236220675, outHumidity: 44.0, outsideAlarm1: 0, 
> outsideAlarm2: 0, outTemp: 74.4, pressure: 29.7612224179, rain: 0.0, 
> rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
> soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1592795760, 
> sunset: 1592852400, trendIcon: 20, txBatteryStatus: 1, usUnits: 1, 
> windchill: 74.4, windDir: 44.0, windGust: 1.0, windGustDir: 44.0, 
> windSpeed: 1.0, windSpeed10: 0.0, yearET: 15.06, yearRain: 19.7952755955
> REC:2020-06-22 22:46:00 CEST (1592858760) altimeter: 30.0083600788, 
> appTemp: 74.2080302355, barometer: 30.007, cloudbase: 5542.93514687, 
> consBatteryVoltage: 1.59, dateTime: 1592858760, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 51.0494853538, ET: 0.0, extraAlarm1: 0.0, extraAlarm2: 0.0, 
> extraAlarm3: 0.0, extraAlarm4: 0.0, extraAlarm5: 0.0, extraAlarm6: 0.0, 
> extraAlarm7: 0.0, extraAlarm8: 0.0, forecastIcon: 6.0, forecastRule: 75, 
> heatindex: 74.4, highOutTemp: 74.5, humidex: 77.1941299914, inDewpoint: 
> 58.9079078442, inHumidity: 53.0, insideAlarm: 0.0, inTemp: 77.4, interval: 
> 1, leafWet4: 0.0, lowOutTemp: 74.4, maxSolarRad: 0.0, monthET: 0.27, 
> monthRain: 8.10236220675, outHumidity: 44.0, outsideAlarm1: 0.0, 
> outsideAlarm2: 0.0, outTemp: 74.4, pressure: 29.7622142603, rain: 0.0, 
> rainAlarm: 0.0, rainRate: 0.0, rxCheckPercent: 100.0, soilLeafAlarm1: 0.0, 
> soilLeafAlarm2: 0.0, soilLeafAlarm3: 0.0, soilLeafAlarm4: 0.0, stormRain: 
> 0.0, sunrise: 1592795760.0, sunset: 1592852400.0, trendIcon: 20.0, 
> txBatteryStatus: 1, usUnits: 1, windchill: 74.4, windDir: 45.0, windGust: 
> 1.0, windGustDir: 45.0, windrun: 0.01667, windSpeed: 1.0, 
> windSpeed10: 0.0, yearET: 15.06, yearRain: 19.7952755955
>

I'll try and find out if the console shows the solar radiation value. It 
probably does since a reboot resolves the problem. My absolute time is 
accurate but I'll set up an NTP anyway and also get me a RTC for my RPi. 

Dne nedelja, 21. junij 2020 22.38.35 UTC+2 je oseba Tom Keffer napisala:
>
> The DMPAFT log entry is normal. 
>
> Is a value for solar radiation appearing on the console?
>
> If you run weewxd directly from the command line, does it show a value for 
> radiation?
>
> -tk
>
> On Sun, Jun 21, 2020 at 1:26 PM peter > 
> wrote:
>
>> Thanks, vince,
>> I will install it and see if it works better. I assume the issue is in 
>> the correct date? Why then only for a solar reading?
>> The issue only happens on this setup but not on other 2 I own, that's why 
>> I'm surprised.
>>
>>
>> Dne nedelja, 21. junij 2020 22.18.50 UTC+2 je oseba vince napisala:
>>>
>>> I'd start by ensuring the pi has quality time.  Generally running NTP 
>>> works better than the built-in systemd time software.  An inexpensive 
>>> realtime clock module also tends to help.  There are 'dozens' of posts here 
>>> about the importance of having accurate date+time especially on devices 
>>> like a pi that have no built-in RTC typically.
>>>
>> -- 
>> You received this message because you are subscribed to the Google 

Re: [weewx-user] Wunderground doesn't accept my data

[Ernest Jillson]

I'm helping someone set up a brand new pi with weewx and vantage vue. We
are getting the same thing in the logs. Failed to publish record. This is
using python 3 and weewx 4.x (latest). It says it's adding records to
database, but fails upload to WU. He even tried changing the password.
Meanwhile I've been running fine with 3.9.2 and python 2.

I'll be following this thread to see what the resolution might end up being.


On Sun, Jun 21, 2020 at 4:27 PM Tom Keffer  wrote:

> I don't blame you.
>
> On Sun, Jun 21, 2020 at 12:23 PM David Barto  wrote:
>
>> Perhaps I should just give up on the WU. PWSweather takes my data just
>> fine, and I'll add the NWS and a couple of others in the near
>> future.
>>
>> David
>>
>> On Jun 21, 2020, at 12:18 PM, Tom Keffer  wrote:
>>
>> Sounds like yet another WU SNAFU.
>>
>> You could try disabling RapidFire and just use regular postings. RF has
>> always been unreliable.
>>
>> -tk
>>
>> On Sun, Jun 21, 2020 at 12:16 PM David Barto  wrote:
>>
>>> Enclosing with quotes didn=E2=80=99t change anything and I logged out/in
>>> from Wunderground and explicitly typed in the password. That worked.
>>>
>>>enable = true
>>>station = KCAPOWAY177
>>>password ="AlphaNumericDataH3Re"
>>># Set the following to True to have weewx use the WU "Rapidfire"
>>># protocol. Not all hardware can support it. See the User's Guide.
>>>rapidfire = True
>>>
>>> Still failing. Debug is set to 1, is there anything else that could be
>>> useful?
>>>
>>> David
>>>
>>> On Jun 21, 2020, at 11:42 AM, Tom Keffer  wrote:
>>>
>>> OK, now you have an *upload* problem, which suggests a password
>>> problem. Make sure you're using the right password. Does it have any
>>> special characters in it? If so, enclose with quotes in weewx.conf.
>>>
>>> -tk
>>>
>>> On Sun, Jun 21, 2020 at 11:32 AM David Barto  wrote:
>>>
 Curl gets a 204. So my configuration ’should’ be working.

 password is set to the password I login with.

 Wunderfixer still returning a 503, so that is unusual.

 I’m now seeing.

 Jun 21 11:26:19 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:15 PDT (1592763975): Failed upload after
 1 tries
 Jun 21 11:26:24 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:19 PDT (1592763979): Failed upload after
 1 tries
 Jun 21 11:26:30 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:25 PDT (1592763985): Failed upload after
 1 tries
 Jun 21 11:26:35 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:29 PDT (1592763989): Failed upload after
 1 tries
 Jun 21 11:26:40 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:35 PDT (1592763995): Failed upload after
 1 tries
 Jun 21 11:26:45 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:39 PDT (1592763999): Failed upload after
 1 tries
 Jun 21 11:26:50 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:45 PDT (1592764005): Failed upload after
 1 tries
 Jun 21 11:26:55 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:49 PDT (1592764009): Failed upload after
 1 tries
 Jun 21 11:27:00 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:26:55 PDT (1592764015): Failed upload after
 1 tries
 Jun 21 11:27:05 Magrathea weewx[23591]: restx: Wunderground-RF: Failed
 to publish record 2020-06-21 11:27:01 PDT (1592764021): Failed upload after
 1 tries

 And https://www.wunderground.com/dashboard/pws/KCAPOWAY177 still
 reports ‘offline’.

 I’ve got ‘debug = 1’ in my configuration, so what else would be useful
 to include to finish this up?

 David

 On Jun 21, 2020, at 10:48 AM, Tom Keffer  wrote:

 Blank page is probably good, and hopefully means that it's accepting
 the API key. To be sure, try curl:

 curl -i '
 https://api.weather.com/v2/pws/observations/all/1day?stationId=KCAPOWAY177=json=m=X
 '


 where, again, X is your API key. This will give you the returned
 status code. I would expect 204.

 NB: the API key is necessary to *download* data, the password is
 necessary to *upload* data. So, you want the API key.

 -tk

 On Sun, Jun 21, 2020 at 9:48 AM David Barto  wrote:

> Weird, when presented my very long API key I get back a blank page.
> I’ll assume that is good. When I give it the short key I get back
>
> {"metadata":{"transaction_id":"##"},"success":false,"errors":[{"error":{"code":"CDN-0001","message":"Invalid
> apiKey."}}]}
>
> What debugging do I 

Re: [weewx-user] Re: Full day highcharts question

[Didier Decoodt]

Thanks for this documentation

Le lun. 22 juin 2020 à 21:10, Pat  a écrit :

> rain total works? That's good though I don't know how! :)
>
> For the aggregates, Belchertown borrows that from weewx's Seasons and
> Standard skins. Here's more information from their documentation
> .
>
> On Monday, June 22, 2020 at 2:47:40 PM UTC-4, Didier Decoodt wrote:
>>
>> Pat, I put aggregate_type = none instead of max, and it's work!!!
>> I don't really understand aggregate_type effect
>> differences between none, sum, min, max and avg?
>> [image: image.png]
>>
>> Le lun. 22 juin 2020 à 19:40, Pat  a écrit :
>>
> I raised this as an issue and
>>> Tom mentioned for the day charts you should probably be using last as the
>>> aggregate, not max.
>>>
>>> I'll look into rainTotal since that's a Belchertown observation.
>>>
>>>
>>> On Friday, June 19, 2020 at 2:02:44 PM UTC-4, Pat wrote:

 No, not sure. I assume it's because the data points aren't reset to
 "None" using this new way of getting data for the rain observation?

 Gary - did you create an issue for this? I'd hate to patch something in
 the skin to only undo it if/when Tom properly patches this.

 On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com
 wrote:
>
> Oh, just a small problem:
> For Rain graph, the curve continue after "now"! (screenshot attached)
> All others curves stop at datetime=now, it's correct)
> The problem concern "rainTotal" and is also available for day, week,
> month and year time_length
> Have you an idea?
>
> hereafter the part of grah.conf
>
> [week]
> # Chart Timespan Defaults
> title = "Cette semaine"
> show_button = true
> button_text = "SEMAINE"
> time_length = week
> tooltip_date_format = ""
> type = spline
> aggregate_type = max
> aggregate_interval = 3600 # 1 hour
> gapsize = 360 # 1 hour in milliseconds
>
> [[chart1]]
> title = Température
> [[[outTemp]]]
> color = "#b2df8a"
> [[[dewpoint]]]
> yAxis_label = ( °C )
> yAxis_tickInterval = 2
> yAxis_softMin = 0
>
> [[chart2]]
> title = Pluie
> [[[rainTotal]]]  < Problem
> color = "#f7a35c"
> name = Cumul
> [[[rain]]]
> color = "#268bd2"
> aggregate_type = sum
> name = pluie
> type = column
> yAxis_tickInterval = 1
> yAxis_label = ( mm )
> yAxis_min = 0
>
>
> Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :
>
>> Awesome! Glad that it worked for you
>>
>>
>> On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com
>> wrote:
>>>
>>> Thanks it's work 
>>>
>>>
>>> Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :
>>>
 Thanks, Gary, for this comprehensive explanation.

 Based on what you wrote I was now able to plot an entire day.

 [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]

 The trick is quite simple: I just had to define an aggregation for
 the daily charts. I.e. adding the following two lines to the 
 graphs.conf:

 aggregate_type = max

 aggregate_interval = 300



 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/35aa4d91-2dd6-4fc5-882d-78ddfd99c18co%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/d738ffbd-0729-42a0-8b0e-15aa37381d95o%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [weewx-user] Re: Full day highcharts question

[Pat]

rain total works? That's good though I don't know how! :)

For the aggregates, Belchertown borrows that from weewx's Seasons and 
Standard skins. Here's more information from their documentation 
. 

On Monday, June 22, 2020 at 2:47:40 PM UTC-4, Didier Decoodt wrote:
>
> Pat, I put aggregate_type = none instead of max, and it's work!!!
> I don't really understand aggregate_type effect
> differences between none, sum, min, max and avg?
> [image: image.png]
>
> Le lun. 22 juin 2020 à 19:40, Pat > a 
> écrit :
>
>> I raised this as an issue and 
>> Tom mentioned for the day charts you should probably be using last as the 
>> aggregate, not max. 
>>
>> I'll look into rainTotal since that's a Belchertown observation. 
>>
>>
>> On Friday, June 19, 2020 at 2:02:44 PM UTC-4, Pat wrote:
>>>
>>> No, not sure. I assume it's because the data points aren't reset to 
>>> "None" using this new way of getting data for the rain observation?
>>>
>>> Gary - did you create an issue for this? I'd hate to patch something in 
>>> the skin to only undo it if/when Tom properly patches this.
>>>
>>> On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com 
>>> wrote:

 Oh, just a small problem:
 For Rain graph, the curve continue after "now"! (screenshot attached)
 All others curves stop at datetime=now, it's correct)
 The problem concern "rainTotal" and is also available for day, week, 
 month and year time_length
 Have you an idea?

 hereafter the part of grah.conf

 [week]
 # Chart Timespan Defaults
 title = "Cette semaine"
 show_button = true
 button_text = "SEMAINE"
 time_length = week
 tooltip_date_format = ""
 type = spline
 aggregate_type = max
 aggregate_interval = 3600 # 1 hour
 gapsize = 360 # 1 hour in milliseconds

 [[chart1]]
 title = Température
 [[[outTemp]]]
 color = "#b2df8a"
 [[[dewpoint]]]
 yAxis_label = ( °C )
 yAxis_tickInterval = 2
 yAxis_softMin = 0
 
 [[chart2]]
 title = Pluie
 [[[rainTotal]]]  < Problem
 color = "#f7a35c"
 name = Cumul
 [[[rain]]]
 color = "#268bd2"
 aggregate_type = sum
 name = pluie
 type = column
 yAxis_tickInterval = 1
 yAxis_label = ( mm )
 yAxis_min = 0


 Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :

> Awesome! Glad that it worked for you
>
>
> On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com 
> wrote:
>>
>> Thanks it's work 
>>
>>
>> Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :
>>
>>> Thanks, Gary, for this comprehensive explanation.
>>>
>>> Based on what you wrote I was now able to plot an entire day.
>>>
>>> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>>>
>>> The trick is quite simple: I just had to define an aggregation for 
>>> the daily charts. I.e. adding the following two lines to the 
>>> graphs.conf:
>>>
>>> aggregate_type = max
>>>
>>> aggregate_interval = 300
>>>
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/35aa4d91-2dd6-4fc5-882d-78ddfd99c18co%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d738ffbd-0729-42a0-8b0e-15aa37381d95o%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Didier Decoodt]

Pat, I put aggregate_type = none instead of max, and it's work!!!
I don't really understand aggregate_type effect
differences between none, sum, min, max and avg?
[image: image.png]

Le lun. 22 juin 2020 à 19:40, Pat  a écrit :

> I raised this as an issue and
> Tom mentioned for the day charts you should probably be using last as the
> aggregate, not max.
>
> I'll look into rainTotal since that's a Belchertown observation.
>
>
> On Friday, June 19, 2020 at 2:02:44 PM UTC-4, Pat wrote:
>>
>> No, not sure. I assume it's because the data points aren't reset to
>> "None" using this new way of getting data for the rain observation?
>>
>> Gary - did you create an issue for this? I'd hate to patch something in
>> the skin to only undo it if/when Tom properly patches this.
>>
>> On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com wrote:
>>>
>>> Oh, just a small problem:
>>> For Rain graph, the curve continue after "now"! (screenshot attached)
>>> All others curves stop at datetime=now, it's correct)
>>> The problem concern "rainTotal" and is also available for day, week,
>>> month and year time_length
>>> Have you an idea?
>>>
>>> hereafter the part of grah.conf
>>>
>>> [week]
>>> # Chart Timespan Defaults
>>> title = "Cette semaine"
>>> show_button = true
>>> button_text = "SEMAINE"
>>> time_length = week
>>> tooltip_date_format = ""
>>> type = spline
>>> aggregate_type = max
>>> aggregate_interval = 3600 # 1 hour
>>> gapsize = 360 # 1 hour in milliseconds
>>>
>>> [[chart1]]
>>> title = Température
>>> [[[outTemp]]]
>>> color = "#b2df8a"
>>> [[[dewpoint]]]
>>> yAxis_label = ( °C )
>>> yAxis_tickInterval = 2
>>> yAxis_softMin = 0
>>>
>>> [[chart2]]
>>> title = Pluie
>>> [[[rainTotal]]]  < Problem
>>> color = "#f7a35c"
>>> name = Cumul
>>> [[[rain]]]
>>> color = "#268bd2"
>>> aggregate_type = sum
>>> name = pluie
>>> type = column
>>> yAxis_tickInterval = 1
>>> yAxis_label = ( mm )
>>> yAxis_min = 0
>>>
>>>
>>> Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :
>>>
 Awesome! Glad that it worked for you


 On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com
 wrote:
>
> Thanks it's work 
>
>
> Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :
>
>> Thanks, Gary, for this comprehensive explanation.
>>
>> Based on what you wrote I was now able to plot an entire day.
>>
>> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>>
>> The trick is quite simple: I just had to define an aggregation for
>> the daily charts. I.e. adding the following two lines to the graphs.conf:
>>
>> aggregate_type = max
>>
>> aggregate_interval = 300
>>
>>
>>
>> --
> 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/35aa4d91-2dd6-4fc5-882d-78ddfd99c18co%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAvt3%3DQR7cfL%3DGxHq1priA5eJ-8Lo9v0Y9xawhPjqd5KW17tEQ%40mail.gmail.com.

[weewx-user] Re: Issue getting BME280 Pressure Data

[Troy Roberts]

I figured out my issue. The "Import bme280" was pulling the wrong bme280.py 
file. I renamed the wrong file then stop/start weewx and now all is working. 

-- 
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/4938f0c6-ede9-41ce-b27f-02e538a9098fo%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[Pat]

I raised this as an issue and 
Tom mentioned for the day charts you should probably be using last as the 
aggregate, not max. 

I'll look into rainTotal since that's a Belchertown observation. 


On Friday, June 19, 2020 at 2:02:44 PM UTC-4, Pat wrote:
>
> No, not sure. I assume it's because the data points aren't reset to "None" 
> using this new way of getting data for the rain observation?
>
> Gary - did you create an issue for this? I'd hate to patch something in 
> the skin to only undo it if/when Tom properly patches this.
>
> On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com wrote:
>>
>> Oh, just a small problem:
>> For Rain graph, the curve continue after "now"! (screenshot attached)
>> All others curves stop at datetime=now, it's correct)
>> The problem concern "rainTotal" and is also available for day, week, 
>> month and year time_length
>> Have you an idea?
>>
>> hereafter the part of grah.conf
>>
>> [week]
>> # Chart Timespan Defaults
>> title = "Cette semaine"
>> show_button = true
>> button_text = "SEMAINE"
>> time_length = week
>> tooltip_date_format = ""
>> type = spline
>> aggregate_type = max
>> aggregate_interval = 3600 # 1 hour
>> gapsize = 360 # 1 hour in milliseconds
>>
>> [[chart1]]
>> title = Température
>> [[[outTemp]]]
>> color = "#b2df8a"
>> [[[dewpoint]]]
>> yAxis_label = ( °C )
>> yAxis_tickInterval = 2
>> yAxis_softMin = 0
>> 
>> [[chart2]]
>> title = Pluie
>> [[[rainTotal]]]  < Problem
>> color = "#f7a35c"
>> name = Cumul
>> [[[rain]]]
>> color = "#268bd2"
>> aggregate_type = sum
>> name = pluie
>> type = column
>> yAxis_tickInterval = 1
>> yAxis_label = ( mm )
>> yAxis_min = 0
>>
>>
>> Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :
>>
>>> Awesome! Glad that it worked for you
>>>
>>>
>>> On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com 
>>> wrote:

 Thanks it's work 


 Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :

> Thanks, Gary, for this comprehensive explanation.
>
> Based on what you wrote I was now able to plot an entire day.
>
> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>
> The trick is quite simple: I just had to define an aggregation for the 
> daily charts. I.e. adding the following two lines to the graphs.conf:
>
> aggregate_type = max
>
> aggregate_interval = 300
>
>
>
>

-- 
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/35aa4d91-2dd6-4fc5-882d-78ddfd99c18co%40googlegroups.com.

[weewx-user] Cydia pomonella

[Chuck Rhode]

A couple of years ago, I developed growing-degree-day graphs to display
codling moth development using *weeWX*.

o http://lacusveris.com/cydia/index.shtml

I've been lurking on the weewx-user@googlegroups.com mailing list
since then.  Now, I'm finally ready to upgrade to *weeWX 4*, but I
have some embroidery on the *python 2* code that I need to migrate to
*python 3*.  The magnitude of this task causes me to rethink my
two-year-old approach.

I cloned weeWX's *ImageGenerator* to access its own database, do its
own growing-degree-day calculations, and generate its own Python
Imaging Lib (PIL) images.  This was not easy, but it was good enough
... then.

Today, I'm bedeviled by notions that perhaps a more general approach
would be nearly as easy (or hard) to achieve and might find utility
for other *weeWX* applications.  I guess you'd say I've fallen in love
with *cheetah* and have taken to looking at all problems as templating
applications.  (Full disclosure: I seem to recall that, in a previous
life, I was a SPERRY (Univac/UNiSYS) *SKEL* programmer.)

... so I ask this somewhat rhetorical question:

Has there been any discussion about templating image generation
through *cheetah*?

I don't recall seeing any such discussion although I've seen some talk
about others' frustrations with the limitations of *ImageGenerator*
that mirror my own.  Apparently the limitation of not being able to
draw y-axis horizons has been lifted in *weeWX 4*, but limitations
such as not being able to apply a second y-axis have not.  To be sure,
these limitations do not wreck the whole notion of *weeWX* or prevent
users' workarounds like mine.  On the other hand, they are examples
only and surely don't exhaust the kinds of drawings that
*ImageGenerator* in particular and PIL in general are NOT suited to.

In my mind templating is for text only, so I'm mystified by what I'm
asking.  I can't feature what an imaging template would look like.

On the other hand, I'm attracted to the notion of providing the
growing-degree-day calculations through *get_extension_list* for use
by *cheetah* in templates for ... generating images.

o Perhaps images could be conjured in real-time using something like
  Google Chart's Visualization JavaScript APIs.  Embedding the
  JavaScript (and data) in *cheetah* templates should be
  straightforward.  This relies on (an indeterminate amount of) client
  horsepower being available to conjure the images.  Also, the host
  site will wish to serve the (huge burden of) JavaScript on every
  access to avoid the appearance of cross-site scripting if possible.
  And it makes any such application dependent on a big, fickle outside
  software-development organization, which will be forever totally
  oblivious of the needs of the *weeWX* community among others.

o Perhaps images could be conjured ahead of time as they are now using
  a *python* script, but the script itself would be a *cheetah*
  template.  This would allow specially calculated data to be
  embedded.  Images could then be uploaded and served to all comers
  without further modification until the next generation cycle with
  great savings of client-side and server-side resources.

  I'm not talking here about a generalized image-scripting language,
  but a *python* module that imports some handy special-purpose
  classes to make *weeWX* image generation fairly terse.  Of course,
  images are deceptively simple things that hide excruciatingly
  detailed specs.  Templating images will not be easy.  It will not
  replace *ImageGenerator*, nor will it ever be for the
  faint-of-heart.

  I think generating a *python* image-generation script from *cheetah*
  has the advantage, though, of abstracting image generation from the
  database structure, reporting cycles, and *weeWX* implementation
  details.  It would promote *weeWX* extensibility.  Also, it opens
  the possibility of using plotting packages other than PIL.  My
  inclination is to use *matplotlib* instead.  Would those who have
  used both recommend something else?

> If you can looke into the Seedes of Time,
> And say, which Graine will grow, and which will not,
> Speake then to me, who neyther begge, nor feare
> Your fauors, nor your hate.

I'd like my development not to conflict with previous or future
*weeWX* development.  Are there things that have been tried and
abandoned that would impact image templating?  Are there things in
the works that would conflict with using *matplotlib*?  Are there
better options for image templating?

-- 
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/20200622123641.08a30e2c%40quixote.LacusVeris.com.

[weewx-user] Re: Weewx tag to show last time it rained

[Mikael Fredriksson]

Hi! Just installed this extension. Works perfectly. Just want to change the 
language in "days", "hours", and "minutes" in $time_since_last_rain tag. Where 
do I make this change? 

regards Mikael

-- 
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/8247f927-bcf6-4da4-ae1b-47282f6d51d1o%40googlegroups.com.

[weewx-user] Re: Issue getting BME280 Pressure Data

[rich T]

In your weewx.conf file, do you have the following?

##

# Options for extension 'bme280wx'
[Bme280wx]
temperature_must_have = ""
humidityKeys = inHumidity
pressureKeys = pressure
pressure_must_have = outTemp
i2c_port = 1
humidity_must_have = ""
i2c_address = 0x77
usUnits = US
temperatureKeys = inTemp

##

On Monday, June 22, 2020 at 10:16:03 AM UTC-4, Troy Roberts wrote:
>
> Hello,
>
> I am having some issues getting BME280 pressure data into my weewx data. I 
> am currently capturing data from an Acurite 5n1 using SDR which is running 
> off a raspberry pi 3. The weewx version is 4.1.1 and all my data is 
> uploading with no issue. I wanted to added pressure data so I followed the 
> guide at (https://gitlab.com/wjcarpenter/bme280wx), which led me to (
> https://pypi.org/project/RPi.bme280/) to get i2c ports up and running. 
> After getting that setup and running the following code, I am able to read 
> all the data from the BME280 sensor.
>
> import smbus2import bme280
> port = 1address = 0x76bus = smbus2.SMBus(port)
> calibration_params = bme280.load_calibration_params(bus, address)
> # the sample method will take a single reading and return a# 
> compensated_reading objectdata = bme280.sample(bus, address, 
> calibration_params)
> # the compensated_reading class has the following 
> attributesprint(data.id)print(data.timestamp)print(data.temperature)print(data.pressure)print(data.humidity)
> # there is a handy string representation tooprint(data)
>
>
> With the following output:
> pi@raspberrypi:~/Desktop $ python BME280_Test.py
> d8bceed7-07e4-499f-a28e-c29928734eab
> 2020-06-22 09:55:51.107513
> 25.5355866359
> 1016.85232725
> 46.209928
> compensated_reading(id=d8bceed7-07e4-499f-a28e-c29928734eab, timestamp=
> 2020-06-22 09:55:51.107513, temp=25.536 °C, pressure=1016.85 hPa, humidity
> =46.21 % rH)
>
>
> After that, I've ran the wee_extension --install command to install 
> bme280wx. I then stop weewx and then started it again and I keep getting 
> the following error:
>
> Jun 22 09:58:36 raspberrypi weewx[455] INFO user.sdr: startup process 
> 'rtl_433 -M utc -F json'
> Jun 22 09:58:36 raspberrypi weewxd: bme280: bme280wx configuration 
> {u'temperature_must_have': u'', u'humidityKeys': u'inHumidity', 
> u'pressureKeys': u'pressure', u'pressure_must_have': u'inTemp', 
> u'i2c_port': u'1', u'humidity_must_have': u'', u'i2c_address': u'0x76', 
> u'usUnits': u'US', u'temperatureKeys': u'inTemp'}
> Jun 22 09:58:36 raspberrypi weewx[455] INFO user.sdr: shutdown process 
> rtl_433 -M utc -F json
> Jun 22 09:58:47 raspberrypi weewx[455] INFO user.sdr: timed out waiting 
> for stderr-thread
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: Caught 
> unrecoverable exception:
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> 'module' object has no attribute 'load_calibration_params'
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> Traceback (most recent call last):
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
> "/usr/share/weewx/weewxd", line 148, in main
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> engine = weewx.engine.StdEngine(config_dict)
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 75, in __init__
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> self.loadServices(config_dict)
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
> "/usr/share/weewx/weewx/engine.py", line 138, in loadServices
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> obj = weeutil.weeutil.get_object(svc)(self,config_dict)
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
> "/usr/share/weewx/user/bme280wx.py", line 61, in __init__
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> self.calibration_params = bme280.load_calibration_params(self.bus, 
> self.address)
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> AttributeError: 'module' object has no attribute 'load_calibration_params'
> Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
> Exiting.
>
> I'm not sure why this is occurring because I don't get this error running 
> the test code above which calls the 'load_calibration_params' Any ideas?
>
> Thanks,
> Troy
>

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

Re: [weewx-user] Issues with Station Registry

[Bostjan Potocnik]

Hi,

I copied it and tested. It seems OK!

...
Jun 22 17:20:58 RPi-SDR weewx[6982] INFO weewx.restx: StationRegistry: 
Published record 2020-06-22 17:20:00 CEST (1592839200)

...

Thanks a lot!


Regards,
  Boštjan

On 22. 06. 20 14:38, Tom Keffer wrote:
Try this version of restx.py. It should replace the version in 
/usr/share/weewx/weewx/restx.py.


-tk

On Mon, Jun 22, 2020 at 5:27 AM Tom Keffer > wrote:


Unfortunately, putting quotes around the name will not help.

Apparently, the Python 2 version of urllib.parse.quote_plus(),
which escapes special characters, does not work with unicode. I
will come up with a patch.

In the meantime, you can use Python 3.

-tk

On Mon, Jun 22, 2020 at 4:59 AM Greg from Oz mailto:ubeau...@gmail.com>> wrote:

It will probably work if you put quotes around the name

location = "text example"

-- 
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/584b3eb2-08b0-4c4c-ba41-d21632d95767o%40googlegroups.com.

--
You received this message because you are subscribed to a topic in the 
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/j2uo6FmdOaU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3DGCqqOHP5Mr-KdynSL6po96%3D_oZSYyudwQb_-uKZnZw%40mail.gmail.com 
.



--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4a691bff-d21e-e1c4-601d-9317529b33ce%40gmail.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Ich habe jetzt einen eigenen Iframe code gemacht damit gibt es keine 
Fehlermeldungen mehr!
Vielen Dank für die Hilfen, werden nun vorerst mal ein wenig mit den 
verschiedenen Möglichkeiten für Diagramme spielen.
Gruss Geni

Am Samstag, 20. Juni 2020 20:54:59 UTC+2 schrieb Manfred Maier:
>
> Am Widget habe ich nichts geändert.
>
> In der .htaccess Datei auf dem Webserver habe ich folgenden Code eingefügt:
> # Extra Security Headers
> 
> Header set Feature-Policy "geolocation 'none'"
> 
>
> Bei manchen Browsers (leider nicht bei allen) unterdrückt dieser Code die 
> Standort-Abfrage der Windy-Widgets.
>
> Ich kann mir aber nicht vorstellen, dass dies der Grund dafür ist, dass 
> bei Dir eine Fehlermeldung kommt und bei mir nicht.
> Bekommst Du die gleiche Fehlermeldung, wenn Du auf andere Seiten mit dem 
> Belchertown-Skin gehst?
>
> Hast Du schon mal im Forum von Windy nachgelesen, ob das Problem bekannt 
> ist?
>
> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 17:04:32 UTC+2:
>
>> Ich verwende Firefox 77.0.1 (64-Bit), die Fehlermeldung kommt aber nur 
>> von meiner Seite, bei Deiner gibt es keine!
>> Was ist bei Windy bei dir anders?
>>
>> Am Samstag, 20. Juni 2020 13:08:25 UTC+2 schrieb Manfred Maier:
>>>
>>> Das Widget von Meteoblue ist leider nach unten hin nicht responsive. 
>>> Bisher ist Meteoblue aber die beste und schönste Vorhersage, die ich 
>>> gefunden habe.
>>> Sowohl DarkSky als auch Aeris liegen hier bei mir von den Vorhersagen 
>>> her leider deutlich daneben.
>>>
>>> Die Fehlermeldung von Windy bekomme ich nicht. Welchen Browser (mit 
>>> Version) verwendest Du?
>>>  
>>>
>>> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 13:04:10 UTC+2:
>>>
 Auf dem Handy wird aber abgeschnitten!

 warum kommt die Fehlermeldung von Windy

 Am Samstag, 20. Juni 2020 11:29:05 UTC+2 schrieb Manfred Maier:
>
> Responsive ist es bei mir auch nur in Grenzen.
> Es gibt eine minimale Breite, ab der das Widget dann abgeschnitten 
> wird. Nur nach oben hin skaliert es schön.
>
> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 10:21:01 
> UTC+2:
>
>> @Manfred
>> Der Eintrag gemäss deinen Angaben funktioniert aber nicht Responsiv, 
>> irgendwie bekommt das iframe die benutzte breite nicht mit.
>> Hast du eine Idee?
>>
>> Am Freitag, 19. Juni 2020 13:14:23 UTC+2 schrieb Manfred Maier:
>>>
>>> Ist bei mir in der index_hook_after_charts.inc drin.
>>>
>>>
>>> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis 
>>> anlegen
>>> 2) den folgenden Code reinkopieren
>>> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
>>> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
>>> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
>>> Code gibt's auf Meteoblue unter Website-Widgets).
>>>
>>> 
>>> 
>>> 
>>> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed=1=0=7=CELSIUS=KILOMETER_PER_HOUR=image;
>>>  
>>>  frameborder="0" scrolling="YES" allowtransparency="true" 
>>> sandbox="allow-same-origin allow-scripts allow-popups 
>>> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
>>> padding-left: 16px; padding-right: 16px">
>>> 
>>> 
>>>
>>>

-- 
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/1a9f933a-052d-4d9e-9320-bdeb976bb35do%40googlegroups.com.

Re: [weewx-user] Monthly Summaries are empty

[John Pierce]

Ah.   I'm on 4.1.1, I went straight there from 3.x

I'll try deleting those NOAA files when I'm next at the terminal...



On Mon, Jun 22, 2020, 4:51 AM Tom Keffer  wrote:

> This is a known problem with v4.1.0. An upgrade to V4.1.1 will fix you up.
>
> After the upgrade, delete all your NOAA files and let WeeWX
> regenerate them.
>
> -tk
>
> On Sun, Jun 21, 2020 at 6:09 PM jhn.p...@gmail.com 
> wrote:
>
>> I upgraded to 4.1.latest a few weeks ago, its running on an RPi3 w/
>> Raspbian Stretch (and installed via apt-get from the Stretch
>> repositories)...
>>
>> I just noticed, my monthly summary tables are content-free, other than
>> the current month... see
>> https://freescruz.com/weewx/tabular.html?report=NOAA/NOAA-2020-05.txt for
>> an example.
>>
>> oh, the annual summaries for previous years are empty, too.
>>
>> do I need to run something special to generate these?   afaik my database
>> goes back 2-3 years.   I'm using mysql on an external server... actually
>> mariadb 10.3.13, installed from FreeBSD 11.3 Ports.
>>
>> --
>> 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/95e85665-b226-4de1-a778-0a7c983f54a6n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/r7qQLToOS6I/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEDiEHq1V9aNQbDE82o%2ByXi507pF-9e1RpnKU%2BH-ueWjnw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAJnkzXK7iC_K8riLv836W4r6gcWbeVDBO1Y7yRC%3D%3DP3HFbc9jQ%40mail.gmail.com.

[weewx-user] Issue getting BME280 Pressure Data

[Troy Roberts]

Hello,

I am having some issues getting BME280 pressure data into my weewx data. I 
am currently capturing data from an Acurite 5n1 using SDR which is running 
off a raspberry pi 3. The weewx version is 4.1.1 and all my data is 
uploading with no issue. I wanted to added pressure data so I followed the 
guide at (https://gitlab.com/wjcarpenter/bme280wx), which led me to (
https://pypi.org/project/RPi.bme280/) to get i2c ports up and running. 
After getting that setup and running the following code, I am able to read 
all the data from the BME280 sensor.

import smbus2import bme280
port = 1address = 0x76bus = smbus2.SMBus(port)
calibration_params = bme280.load_calibration_params(bus, address)
# the sample method will take a single reading and return a# 
compensated_reading objectdata = bme280.sample(bus, address, calibration_params)
# the compensated_reading class has the following 
attributesprint(data.id)print(data.timestamp)print(data.temperature)print(data.pressure)print(data.humidity)
# there is a handy string representation tooprint(data)


With the following output:
pi@raspberrypi:~/Desktop $ python BME280_Test.py
d8bceed7-07e4-499f-a28e-c29928734eab
2020-06-22 09:55:51.107513
25.5355866359
1016.85232725
46.209928
compensated_reading(id=d8bceed7-07e4-499f-a28e-c29928734eab, timestamp=2020-
06-22 09:55:51.107513, temp=25.536 °C, pressure=1016.85 hPa, humidity=46.21 
% rH)


After that, I've ran the wee_extension --install command to install 
bme280wx. I then stop weewx and then started it again and I keep getting 
the following error:

Jun 22 09:58:36 raspberrypi weewx[455] INFO user.sdr: startup process 
'rtl_433 -M utc -F json'
Jun 22 09:58:36 raspberrypi weewxd: bme280: bme280wx configuration 
{u'temperature_must_have': u'', u'humidityKeys': u'inHumidity', 
u'pressureKeys': u'pressure', u'pressure_must_have': u'inTemp', 
u'i2c_port': u'1', u'humidity_must_have': u'', u'i2c_address': u'0x76', 
u'usUnits': u'US', u'temperatureKeys': u'inTemp'}
Jun 22 09:58:36 raspberrypi weewx[455] INFO user.sdr: shutdown process 
rtl_433 -M utc -F json
Jun 22 09:58:47 raspberrypi weewx[455] INFO user.sdr: timed out waiting for 
stderr-thread
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: Caught 
unrecoverable exception:
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
'module' object has no attribute 'load_calibration_params'
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
Traceback (most recent call last):
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 148, in main
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
engine = weewx.engine.StdEngine(config_dict)
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 75, in __init__
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
self.loadServices(config_dict)
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   obj 
= weeutil.weeutil.get_object(svc)(self,config_dict)
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__: File 
"/usr/share/weewx/user/bme280wx.py", line 61, in __init__
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
self.calibration_params = bme280.load_calibration_params(self.bus, 
self.address)
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   
AttributeError: 'module' object has no attribute 'load_calibration_params'
Jun 22 09:58:47 raspberrypi weewx[455] CRITICAL __main__:   Exiting.

I'm not sure why this is occurring because I don't get this error running 
the test code above which calls the 'load_calibration_params' Any ideas?

Thanks,
Troy

-- 
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/766873cb-751f-4844-949e-73b8a7c0fd8bo%40googlegroups.com.

Re: [weewx-user] Re: weewx not updating after upgrade from 3.9 to 4.1.1

[miso k]

like the system of updating will be practically the same, leaving or 
overwriting the configuration files.
and the result of updating will be the same.

M.

Dňa nedeľa, 21. júna 2020 14:20:43 UTC+2 Tom Keffer napísal(a):
>
> I don't know what you mean by "the same thing."
>
> On Sun, Jun 21, 2020 at 5:13 AM miso k > 
> wrote:
>
>> Actually I have an old backup of SD card - rolled back and updated with 
>> the new Database file.
>> So I am running the 3.9.2 WeeWX again.
>>
>> Will the updating with setup.py do the same thing, as updating throug DEB 
>> package?
>>
>>
>> Dňa nedeľa, 21. júna 2020 13:46:05 UTC+2 Tom Keffer napísal(a):
>>>
>>> The log you showed is very short, and does not include the start up of 
>>> weewx. See the article *Help! Posting to weewx-user 
>>> * for 
>>> how to get a good log.
>>>
>>> -tk
>>>
>>> On Sun, Jun 21, 2020 at 1:58 AM miso k  wrote:
>>>
 Can I downgrade to previous version?

 Dňa nedeľa, 21. júna 2020 10:57:09 UTC+2 miso k napísal(a):
>
> Hello,
> I just recently updated my RPi weewx 3.9.x to latest 4.1.1. 
>
> I have not upgraded my conf files - choosed N option, during update.
>
> The webpage actualisations are not working. Can anybody help me, 
> please? What should I change?
>
> sudo tail  /var/log/syslog
>> Jun 21 10:44:18 raspberrypi systemd[1]: systemd-hostnamed.service: 
>> Succeeded.
>> Jun 21 10:44:49 raspberrypi systemd[1]: Started Session c3 of user pi.
>> Jun 21 10:45:40 raspberrypi dbus-daemon[312]: [system] Activating via 
>> systemd: service name='org.freedesktop.PackageKit' 
>> unit='packagekit.service' requested by ':1.26' (uid=0 pid=1138 
>> comm="/usr/bin/gdbus call --system --dest org.freedeskto")
>> Jun 21 10:45:40 raspberrypi systemd[1]: Starting PackageKit Daemon...
>> Jun 21 10:45:40 raspberrypi PackageKit: daemon start
>> Jun 21 10:45:40 raspberrypi dbus-daemon[312]: [system] Successfully 
>> activated service 'org.freedesktop.PackageKit'
>> Jun 21 10:45:40 raspberrypi systemd[1]: Started PackageKit Daemon.
>> Jun 21 10:50:45 raspberrypi PackageKit: daemon quit
>> Jun 21 10:50:45 raspberrypi systemd[1]: packagekit.service: Main 
>> process exited, code=killed, status=15/TERM
>> Jun 21 10:50:45 raspberrypi systemd[1]: packagekit.service: Succeeded.
>
>
> Thanks,
> Michal
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/19b8ed5a-cd01-4983-8903-c725d01880d1o%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/9bd888a3-88b9-4148-8ef1-4addfbba67cbo%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6a86568a-e556-41b0-9bc7-53fd82797725o%40googlegroups.com.

Re: [weewx-user] Issues with Station Registry

[Tom Keffer]

Try this version of restx.py. It should replace the version in
/usr/share/weewx/weewx/restx.py.

-tk

On Mon, Jun 22, 2020 at 5:27 AM Tom Keffer  wrote:

> Unfortunately, putting quotes around the name will not help.
>
> Apparently, the Python 2 version of urllib.parse.quote_plus(), which
> escapes special characters, does not work with unicode. I will come up with
> a patch.
>
> In the meantime, you can use Python 3.
>
> -tk
>
> On Mon, Jun 22, 2020 at 4:59 AM Greg from Oz  wrote:
>
>> It will probably work if you put quotes around the name
>>
>> location = "text example"
>>
>> --
>> 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/584b3eb2-08b0-4c4c-ba41-d21632d95767o%40googlegroups.com
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3DGCqqOHP5Mr-KdynSL6po96%3D_oZSYyudwQb_-uKZnZw%40mail.gmail.com.
#
#Copyright (c) 2009-2020 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#
"""Publish weather data to RESTful sites such as the Weather Underground.

GENERAL ARCHITECTURE

Each protocol uses two classes:

 o A weewx service, that runs in the main thread. Call this the
"controlling object"
 o A separate "threading" class that runs in its own thread. Call this the
"posting object".
 
Communication between the two is via an instance of queue.Queue. New loop
packets or archive records are put into the queue by the controlling object
and received by the posting object. Details below.
 
The controlling object should inherit from StdRESTful. The controlling object
is responsible for unpacking any configuration information from weewx.conf, and
supplying any defaults. It sets up the queue. It arranges for any new LOOP or
archive records to be put in the queue. It then launches the thread for the
posting object.
 
When a new LOOP or record arrives, the controlling object puts it in the queue,
to be received by the posting object. The controlling object can tell the
posting object to terminate by putting a 'None' in the queue.
 
The posting object should inherit from class RESTThread. It monitors the queue
and blocks until a new record arrives.

The base class RESTThread has a lot of functionality, so specializing classes
should only have to implement a few functions. In particular, 

 - format_url(self, record). This function takes a record dictionary as an
   argument. It is responsible for formatting it as an appropriate URL. 
   For example, the station registry's version emits strings such as
 http://weewx.com/register/register.cgi?weewx_info=2.6.0a5_info= ...
   
 - skip_this_post(self, time_ts). If this function returns True, then the
   post will be skipped. Otherwise, it is done. The default version does two
   checks. First, it sees how old the record is. If it is older than the value
   'stale', then the post is skipped. Second, it will not allow posts more
   often than 'post_interval'. Both of these can be set in the constructor of
   RESTThread.

 - post_request(self, request, data). This function takes a urllib.request.Request object
   and is responsible for performing the HTTP GET or POST. The default version
   simply uses urllib.request.urlopen(request) and returns the result. If the post
   could raise an unusual exception, override this function and catch the
   exception. See the WOWThread implementation for an example.
   
 - check_response(self, response). After an HTTP request gets posted, the webserver sends
   back a "response." This response may contain clues as to whether the post
   worked.  By overriding check_response() you can look for these clues. For
   example, the station registry checks all lines in the response, looking for
   any that start with the string "FAIL". If it finds one, it raises a
   FailedPost exception, signaling that the post did not work.
   
In unusual cases, you might also have to implement the following:
  
 - get_request(self, url). The default version of this function creates
   an urllib.request.Request object from the url, adds a 'User-Agent' header,
   then returns it. You may need to override this function if you need to add
   other headers, such as "Authorization" header.

 - get_post_body(self, record). Override this function if you want to do an HTTP
   POST (instead of GET). It should return a tuple. First element is the body
   of the POST, the second element is the type of the body. An example would
   be (json.dumps({'city' : 'Sacramento'}), 

Re: [weewx-user] Issues with Station Registry

[Tom Keffer]

Unfortunately, putting quotes around the name will not help.

Apparently, the Python 2 version of urllib.parse.quote_plus(), which
escapes special characters, does not work with unicode. I will come up with
a patch.

In the meantime, you can use Python 3.

-tk

On Mon, Jun 22, 2020 at 4:59 AM Greg from Oz  wrote:

> It will probably work if you put quotes around the name
>
> location = "text example"
>
> --
> 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/584b3eb2-08b0-4c4c-ba41-d21632d95767o%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAGWSV8yjKcoW6x9n6iVGpo3VqfstZGBja%2By_k6yA6C_g%40mail.gmail.com.

[weewx-user] Issues with Station Registry

[Greg from Oz]

It will probably work if you put quotes around the name 

location = "text example"

-- 
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/584b3eb2-08b0-4c4c-ba41-d21632d95767o%40googlegroups.com.

Re: [weewx-user] Monthly Summaries are empty

[Tom Keffer]

This is a known problem with v4.1.0. An upgrade to V4.1.1 will fix you up.

After the upgrade, delete all your NOAA files and let WeeWX regenerate them.

-tk

On Sun, Jun 21, 2020 at 6:09 PM jhn.p...@gmail.com 
wrote:

> I upgraded to 4.1.latest a few weeks ago, its running on an RPi3 w/
> Raspbian Stretch (and installed via apt-get from the Stretch
> repositories)...
>
> I just noticed, my monthly summary tables are content-free, other than the
> current month... see
> https://freescruz.com/weewx/tabular.html?report=NOAA/NOAA-2020-05.txt for
> an example.
>
> oh, the annual summaries for previous years are empty, too.
>
> do I need to run something special to generate these?   afaik my database
> goes back 2-3 years.   I'm using mysql on an external server... actually
> mariadb 10.3.13, installed from FreeBSD 11.3 Ports.
>
> --
> 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/95e85665-b226-4de1-a778-0a7c983f54a6n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDiEHq1V9aNQbDE82o%2ByXi507pF-9e1RpnKU%2BH-ueWjnw%40mail.gmail.com.

Re: [weewx-user] Re: After fresh installation no current data

[Andre]

Many thanks, Graham.
Now it works like a charm. So many pathes there. The web server was 
misconfigured with dirty pathes.

Am Montag, 22. Juni 2020 10:49:21 UTC+2 schrieb Graham Eddy:
>
> it says it is generating files.
> check the timestamps on the files in the weewx public_html directory 
> (where the generated files are put)
>
> On 22 Jun 2020, at 6:45 pm, Andre > 
> wrote:
>
> Here my syslog after reboot
>
> Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Getting 
> archive packets since 2020-06-22 10:35:00 CEST (1592814900)
> Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Gentle 
> wake up of console successful
> Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Retrieving 
> 1 page(s); starting index= 4
> Jun 22 10:40:16 weewx weewx[1426] INFO weewx.manager: Added record 2020-06
> -22 10:40:00 CEST (1592815200) to database 'weewx.sdb'
> Jun 22 10:40:16 weewx weewx[1426] INFO weewx.manager: Added record 2020-06
> -22 10:40:00 CEST (1592815200) to daily summary in 'weewx.sdb'
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.drivers.vantage: Requesting 
> 200 LOOP packets.
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.drivers.vantage: Gentle 
> wake up of console successful
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras']
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.manager: Daily summary 
> version is 2.0
> Jun 22 10:40:24 weewx weewx[1426] INFO weewx.cheetahgenerator: Generated 8 
> files for report SeasonsReport in 6.77 seconds
> Jun 22 10:40:24 weewx weewx[1426] DEBUG weewx.manager: Daily summary 
> version is 2.0
> Jun 22 10:40:26 weewx weewx[1426] INFO weewx.imagegenerator: Generated 15 
> images for report SeasonsReport in 1.93 seconds
> Jun 22 10:40:26 weewx weewx[1426] INFO weewx.reportengine: Copied 5 files 
> to /var/weewx/reports
>
> I get no current data on my homepage...its still on 2020-06-21 16:05
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/f22f2682-d7d4-4580-b4d8-b101055b4c3co%40googlegroups.com
>  
> 
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4786b77a-7c2c-4331-bba4-fd15ce1634a7o%40googlegroups.com.

Re: [weewx-user] Re: After fresh installation no current data

[Graham Eddy]

it says it is generating files.
check the timestamps on the files in the weewx public_html directory (where the 
generated files are put)

> On 22 Jun 2020, at 6:45 pm, Andre  wrote:
> 
> Here my syslog after reboot
> 
> Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Getting 
> archive packets since 2020-06-22 10:35:00 CEST (1592814900)
> Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Gentle wake up 
> of console successful
> Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Retrieving 1 
> page(s); starting index= 4
> Jun 22 10:40:16 weewx weewx[1426] INFO weewx.manager: Added record 2020-06-22 
> 10:40:00 CEST (1592815200) to database 'weewx.sdb'
> Jun 22 10:40:16 weewx weewx[1426] INFO weewx.manager: Added record 2020-06-22 
> 10:40:00 CEST (1592815200) to daily summary in 'weewx.sdb'
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Running reports 
> for latest time in the database.
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.drivers.vantage: Requesting 200 
> LOOP packets.
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Running report 
> 'SeasonsReport'
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.drivers.vantage: Gentle wake up 
> of console successful
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport'
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.cheetahgenerator: Using search 
> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.manager: Daily summary version 
> is 2.0
> Jun 22 10:40:24 weewx weewx[1426] INFO weewx.cheetahgenerator: Generated 8 
> files for report SeasonsReport in 6.77 seconds
> Jun 22 10:40:24 weewx weewx[1426] DEBUG weewx.manager: Daily summary version 
> is 2.0
> Jun 22 10:40:26 weewx weewx[1426] INFO weewx.imagegenerator: Generated 15 
> images for report SeasonsReport in 1.93 seconds
> Jun 22 10:40:26 weewx weewx[1426] INFO weewx.reportengine: Copied 5 files to 
> /var/weewx/reports
> 
> I get no current data on my homepage...its still on 2020-06-21 16:05
> 
> -- 
> 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/f22f2682-d7d4-4580-b4d8-b101055b4c3co%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/623F660F-DBE1-474B-8FCB-317B7A8E3637%40gmail.com.

[weewx-user] Re: After fresh installation no current data

[Andre]

Here my syslog after reboot

Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2020-06-22 10:35:00 CEST (1592814900)
Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jun 22 10:40:16 weewx weewx[1426] DEBUG weewx.drivers.vantage: Retrieving 1 
page(s); starting index= 4
Jun 22 10:40:16 weewx weewx[1426] INFO weewx.manager: Added record 2020-06-
22 10:40:00 CEST (1592815200) to database 'weewx.sdb'
Jun 22 10:40:16 weewx weewx[1426] INFO weewx.manager: Added record 2020-06-
22 10:40:00 CEST (1592815200) to daily summary in 'weewx.sdb'
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Running reports 
for latest time in the database.
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jun 22 10:40:17 weewx weewx[1426] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 22 10:40:24 weewx weewx[1426] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 6.77 seconds
Jun 22 10:40:24 weewx weewx[1426] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 22 10:40:26 weewx weewx[1426] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 1.93 seconds
Jun 22 10:40:26 weewx weewx[1426] INFO weewx.reportengine: Copied 5 files 
to /var/weewx/reports

I get no current data on my homepage...its still on 2020-06-21 16:05

-- 
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/f22f2682-d7d4-4580-b4d8-b101055b4c3co%40googlegroups.com.

[weewx-user] Re: After fresh installation no current data

[Andre]

I tried this first

1. Unplug the console, take out the batteries, and wait a minute or two.

After this I tried this

wee_device --dump

And get the following message

pi@weewx:~ $ sudo wee_device --dump
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Proceeding will dump all data in the logger.
Are you sure you want to proceed (y/n)? y
Starting dump ...
 Traceback (most recent call last):020-06-22 10:15:00 CEST (1592813700)
  File "/usr/share/weewx/wee_device", line 78, in 
main()
  File "/usr/share/weewx/wee_device", line 74, in main
device.configure(config_dict)
  File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in configure
self.do_options(options, parser, config_dict, not options.noprompt)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 2099, in do_options
self.dump_logger(station, config_dict, options.noprompt)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 2701, in 
dump_logger
for record in converted_generator:
  File "/usr/share/weewx/weewx/units.py", line 1364, in __next__
_record = next(self.input_generator)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 695, in 
genArchiveDump
_page = self.port.get_data_with_crc16(267, prompt=_ack, 
max_tries=self.max_tries)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 232, in 
get_data_with_crc16
raise weewx.WeeWxIOError("Timeout in get_data_with_crc16")
weewx.WeeWxIOError: Timeout in get_data_with_crc16

Do I have a generally problem with my console or with the USB-Connector?

Regards Andre

-- 
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/06a296ab-d5f2-4e75-bd27-a7002e749bd6o%40googlegroups.com.

[weewx-user] After fresh installation no current data

[Andre]

My SD card from Raspberry Pi has stopped working. And now I had to do a 
fresh install of weewx. My last installation was over 3 years ago and 
unfortunately I forgot almost everything.

The basic installation of weewx seems to have worked, but I don't get any 
current data displayed. The last value is from 2020-06-21 16:05:00 CEST.

Here is my syslog

pi@weewx:~ $ sudo tail -f /var/log/syslog
Jun 22 08:40:16 weewx weewx[4491] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 22 08:40:19 weewx weewx[4491] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 3.01 seconds
Jun 22 08:40:19 weewx weewx[4491] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 22 08:40:21 weewx weewx[4491] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 2.11 seconds
Jun 22 08:40:21 weewx weewx[4491] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx
Jun 22 08:40:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jun 22 08:40:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jun 22 08:40:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jun 22 08:40:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Jun 22 08:40:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 'RSYNC' 
not enabled. Skipping.
Jun 22 08:45:15 weewx weewx[4491] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2020-06-21 16:05:00 CEST (1592748300)
Jun 22 08:45:15 weewx weewx[4491] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jun 22 08:45:15 weewx weewx[4491] DEBUG weewx.drivers.vantage: Retrieving 
38 page(s); starting index= 1
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.drivers.vantage: DMPAFT 
complete: page timestamp 2020-06-21 09:25:00 CEST (1592724300) less than 
final timestamp 2020-06-21 16:05:00 CEST (1592748300)
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.drivers.vantage: Catch up 
complete.
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.reportengine: Running reports 
for latest time in the database.
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Jun 22 08:45:16 weewx weewx[4491] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 22 08:45:19 weewx weewx[4491] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 3.00 seconds
Jun 22 08:45:19 weewx weewx[4491] DEBUG weewx.manager: Daily summary 
version is 2.0
Jun 22 08:45:21 weewx weewx[4491] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 2.12 seconds
Jun 22 08:45:21 weewx weewx[4491] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx
Jun 22 08:45:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Jun 22 08:45:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Jun 22 08:45:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Jun 22 08:45:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Jun 22 08:45:21 weewx weewx[4491] DEBUG weewx.reportengine: Report 'RSYNC' 
not enabled. Skipping.

I am happy about helpful tips.

Regards Andre

-- 
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/1ef9707c-0a5a-4761-8534-9dc44ecdae83o%40googlegroups.com.

[weewx-user] Issues with Station Registry

[Bostjan Potocnik]

Hi,

with version 4.1.1 I have problems with Station Registry. I guess it has to 
do with station location name and locale used!
If i'm correct "\u0161" is leter "š" and the name of my station location is:

[Station]

# Description of the station location
location = Loka pri Mengšu


Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: StationRegistry: 
Unexpected exception of type 
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** Traceback (most 
recent call last):
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 378, in run_loop
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** 
self.process_record(_record, dbmanager)
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 426, in process_record
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** _url = 
self.format_url(_full_record)
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 1489, in format_url
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** 
_liststr.append(urllib.parse.quote_plus(StationRegistryThread._FORMATS[_key] 
% v, '='))
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: ***   File 
"/usr/lib/python2.7/urllib.py", line 1306, in quote_plus
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** s = quote(s, 
safe + ' ')
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: ***   File 
"/usr/lib/python2.7/urllib.py", line 1301, in quote
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** return 
''.join(map(quoter, s))
Jun 21 21:10:40 RPi-SDR weewx[1348] ERROR weewx.restx: *** KeyError: 
u'\u0161'

Regards,

Boštjan

-- 
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/b01183f7-d71a-434e-8c26-ca065baebecco%40googlegroups.com.