Re: [weewx-user] Re: problem with wind in WMR300

[Liz]

On Fri, 11 Jan 2019 10:03:16 -0800 (PST)
Juan Antonio Mosquera 
wrote:

> Sorry for the inconvenience with this problem, I've wasted your time.

Not at all. You have reminded us all to think a little wider when
troubleshooting.


Liz

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

Re: [weewx-user] Metric v US databases

[Liz]

On Fri, 11 Jan 2019 19:23:05 -0800 (PST)
Andrew Milner  wrote:

> Having read for the umpteenth time recently comments implying that
> there is no need to change the database units from US to Metric I
> thought it was time to give my pennyworth.  IMHO there is every
> reason in the world to change the units if one is living in the rest
> of the world outside the US. When (not if) one has to look at the
> database to resolve an issue using sqlite3 or MySQL there is nothing
> worse than being faced with a load of data which is unrecognisable
> and means nothing since the units are such they are never seen during
> daily life.  pressures of 30. mean nothing when daily pressures
> are in mbar and temperatures are meaningless when in farenheit and
> daily weather temperatures are in Celsius.  IMHO if you live outside
> the US your database should be Metric or Metricwx so that the data
> becomes meaningful when viewed directly.
> 
> I agree that for the purposes of weewx this is not necessary as all 
> conversions will happen automatically.
> 
> One final thing which I have done to my MySQL database is to redefine
> the columns to limit the number of decimal places to 2 in most
> cases.  This makes viewing with MySQL directly much much more
> readable and gets rid of the totally unnecessary additional decimal
> places with little (if any) effect on weewx.
> 

+1
Liz

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

[weewx-user] Re: Metric v US databases

[ponolan]

Agree 100%.

https://mentalfloss.com/article/55895/countries-havent-adopted-metric-system

If someone forked WeeWX with metric units I'd switch.

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

[weewx-user] Re: Metric v US databases

[ponolan]

metric units *only*, that is. 

I am well aware that it's possible to use metric units. I didn't change the 
default as I knew I'd upload data to a couple of US sites and, well, we've 
all read about screw-ups resulting from mismatched units so I just went 
with it initially, thinking I could change it later. I'm still using the 
sqlite db. At some point I'll switch and that may be a moment to deal with 
it. But, yes, 100%, having relatable data matters. US units mean nothing to 
me, despite having lived in the US for a few years--as a grad student a 
long time ago. I've lived on four continents and traveled a lot (nearly 100 
countries), mostly for work. As I've never visited Liberia or Myanmar the 
only place I've ever encountered non internationally standard units is the 
US. 

OK, using a fork is perhaps over-reacting and it's reasonable for US 
software to default to US units, but having had to deal far too often with 
printing US documents on ISO standard paper (among other things), I have a 
well developed antipathy to "America first" in all its forms. It would just 
be great to see the US join the rest of the world, even symbolically.


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

Re: [weewx-user] Re: Metric v US databases

[Thomas Keffer]

Geez, you people make it sound like WeeWX defaults to US Customary out of
some sort of sheer stubbornness on my part.

First, I'm an earth scientist. I can tell you the depth and temperature of
the ocean's thermocline in metric, but wouldn't have a clue what it is in
US. Except for daily experiences, it's the only unit system I'm familiar
with.

Second, take a look through the code base, and you won't find any bias
towards US. Everything is parameterized and unit-agnostic. If you were to
fork the code, I don't know what you'd change.

Third, you have total freedom to change, or even to adopt a mix of US and
Metric. Stop your whining (or, to be completely English-agnostic, that's
whinging for you Brits and Aussies).

Finally, like it or not, most of the instruments out there emit at least a
mix of US Customary through their APIs, including the most popular one,
Vantage, which is exclusively US. For those users, US would be the "native"
system, and results in the best fidelity between source and database. If
you don't agree with that, fine: change.

And, don't blame me for the shape of US documents.

-tk



On Sat, Jan 12, 2019 at 3:04 AM  wrote:

> metric units *only*, that is.
>
> I am well aware that it's possible to use metric units. I didn't change
> the default as I knew I'd upload data to a couple of US sites and, well,
> we've all read about screw-ups resulting from mismatched units so I just
> went with it initially, thinking I could change it later. I'm still using
> the sqlite db. At some point I'll switch and that may be a moment to deal
> with it. But, yes, 100%, having relatable data matters. US units mean
> nothing to me, despite having lived in the US for a few years--as a grad
> student a long time ago. I've lived on four continents and traveled a lot
> (nearly 100 countries), mostly for work. As I've never visited Liberia or
> Myanmar the only place I've ever encountered non internationally standard
> units is the US.
>
> OK, using a fork is perhaps over-reacting and it's reasonable for US
> software to default to US units, but having had to deal far too often with
> printing US documents on ISO standard paper (among other things), I have a
> well developed antipathy to "America first" in all its forms. It would just
> be great to see the US join the rest of the world, even symbolically.
>
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Metric v US databases

[ponolan]

No imputations of personal cussedness were implied, more of a suggestion 
that it would be nice to see a default of international standards first. 
That is all. Your own expertise and background are well known and respected 
by anyone who's bothered to inform themselves. Apologies if you thought 
otherwise. My suggestion of forking was an expression of annoyance with the 
whole business of the US's eccentricity, not on the practical, functional 
significance, and I tried to acknowledge and qualify.

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

[weewx-user] Re: change noaa report wind direction

[Luigi Carbonera]

  Yes, right . N, S, SE or NNW
I tried with this suggested but it does not work


   HEAT   COOL AVG
  MEAN   DEGDEG  
WIND   DOM
DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH   
TIMEDIR
---
#for $day in $month.days
#if $day.barometer.count.raw
$day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE) 
$day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time) 
$day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time) 
$day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE) 
$day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE) 
$day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time) 
$day.windDir.ordinal_compass($Dir,$NONE)
#else
$day.dateTime.format($D)
#end if
#end for
---
$month.outTemp.avg.nolabel($Temp,$NONE) 
$month.outTemp.max.nolabel($Temp,$NONE)
$month.outTemp.maxtime.format($D) 
$month.outTemp.min.nolabel($Temp,$NONE)
$month.outTemp.mintime.format($D) $month.heatdeg.sum.nolabel($Temp,$NONE) 
$month.cooldeg.sum.nolabel($Temp,$NONE) 
$month.rain.sum.nolabel($Rain,$NONE) $month.wind.avg.nolabel($Wind,$NONE) 
$month.wind.max.nolabel($Wind,$NONE)$month.wind.maxtime.format($D) 
$month.windDir.ordinal_compass($Dir)




Il giorno sabato 12 gennaio 2019 02:06:50 UTC+1, gjr80 ha scritto:
>
> Hi,
>
> If I understand you correctly you want N, S, SE or NNW rather than numeric 
> degrees? If so did you try $day.windDir.ordinal_compass ? Note there is 
> no space between the $ and day and you don't need the .nolabel
>
> Gary
>
> On Saturday, 12 January 2019 07:04:35 UTC+10, Luigi Carbonera wrote:
>>
>> Hello
>> I have to change the wind direction in the noaa report
>> by degrees such as NNE .. NW .. SE
>> I tried with  "  $ day.windDir.ordinal_compass.nolabel  "   without 
>> success.
>> and put the point between the data
>>
>> #for $day in $month.days
>> #if $day.barometer.count.raw
>> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE) 
>> $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time) 
>> $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time) 
>> $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE) 
>> $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE) 
>> $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time) 
>> $day.windDir.ordinal_compass.nolabel($Dir,$NONE)
>> #else
>> $day.dateTime.format($D)
>> #end if
>> #end for
>>
>>
>>
>> This is because I have a php program that reads me the text files noaa 
>> and I would also do it for WeeWx
>> http://sacilemeteo.altervista.org/statd/rapporto-mensile.php 
>>
>> Solution?
>> Thank you
>> Luigi
>>
>> generated  WeeWx
>>
>>
>>
>>TEMPERATURE (°C), RAIN (mm), WIND SPEED (km/h)
>>
>>  HEAT   COOL AVG
>>   MEAN   DEGDEG  
>> WIND   DOM
>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   
>> HIGH   TIMEDIR
>>
>> ---
>>  01   -0,91,9  12:24   -2,8  20:43   19,30,00,02,2   
>> 12,9  12:33242
>>  021,05,3  04:04   -3,1  23:34   17,40,00,03,1   
>> 27,4  10:16356
>>  03   -2,90,4  14:39   -5,0  18:39   21,30,00,02,3   
>> 20,9  12:14190
>>  04   -4,6   -1,4  15:33   -7,3  07:49   23,00,00,02,5   
>> 12,9  10:33211
>>  05   -0,44,3  21:58   -5,9  01:47   18,70,00,02,1   
>> 12,9  21:51355
>>  064,08,5  14:580,1  01:53   14,30,00,03,2   
>> 14,5  16:03 43
>>  07   -0,70,9  00:00   -1,8  23:59   19,00,00,01,0   
>> 11,3  10:57139
>>  08   -1,6   -0,2  23:50   -3,3  18:54   19,90,00,01,4   
>> 12,9  02:58203
>>  090,73,9  12:50   -1,4  23:52   17,60,00,02,1   
>> 16,1  14:23 58
>>  10   -0,83,3  15:34   -2,8  20:23   19,20,00,02,5   
>> 14,5  13:14 92
>>  11   -3,2   -0,2  14:03   -5,9  07:52   21,50,00,02,1   
>> 17,7  13:13228
>>  12
>>
>>
>> generated WeatherLink Is OK
>>
>>
>>
>>TEMPERATURE (°C), RAIN  (mm), WIND SPEED (km/hr)
>>
>>   HEAT  COOLAVG
>> MEAN  DEG   DEG 
>> WIND DOM
>> DAY TEMP  HIGH   TIME   LOWTIME   DAYS  DAYS  RAIN  SPEED HIGH   
>> TIMEDIR
>>
>> 
>>  1   1.8   7.8   12.43  -2.18.05  16.4   

Re: [weewx-user] Re: change noaa report wind direction

[Thomas Keffer]

You need to specify an aggregation to go with the $day tag. For example,
for temperature you have $day.outTemp.max, which says you want the max
temperature for the day. A tag $day.outTemp is meaningless. Similarly for
windDir.

Which leads me to the next question: are you sure you want windDir? Most
aggregates (min, max, sum, avg, etc.) don't make much sense for a compass
direction. You probably want the vector averages. Try something like
$day.wind.vecdir, which is the average vector direction.

-tk

On Sat, Jan 12, 2019 at 7:53 AM Luigi Carbonera 
wrote:

>   Yes, right . N, S, SE or NNW
> I tried with this suggested but it does not work
>
>
>HEAT   COOL AVG
>   MEAN   DEGDEG
> WIND   DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
> HIGH   TIMEDIR
>
> ---
> #for $day in $month.days
> #if $day.barometer.count.raw
> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE)
> $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time)
> $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time)
> $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE)
> $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE)
> $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time)
> $day.windDir.ordinal_compass($Dir,$NONE)
> #else
> $day.dateTime.format($D)
> #end if
> #end for
>
> ---
> $month.outTemp.avg.nolabel($Temp,$NONE)
> $month.outTemp.max.nolabel($Temp,$NONE)
> $month.outTemp.maxtime.format($D)
> $month.outTemp.min.nolabel($Temp,$NONE)
> $month.outTemp.mintime.format($D) $month.heatdeg.sum.nolabel($Temp,$NONE)
> $month.cooldeg.sum.nolabel($Temp,$NONE)
> $month.rain.sum.nolabel($Rain,$NONE) $month.wind.avg.nolabel($Wind,$NONE)
> $month.wind.max.nolabel($Wind,$NONE)$month.wind.maxtime.format($D)
> $month.windDir.ordinal_compass($Dir)
>
>
>
>
> Il giorno sabato 12 gennaio 2019 02:06:50 UTC+1, gjr80 ha scritto:
>>
>> Hi,
>>
>> If I understand you correctly you want N, S, SE or NNW rather than
>> numeric degrees? If so did you try $day.windDir.ordinal_compass ? Note
>> there is no space between the $ and day and you don't need the .nolabel
>>
>> Gary
>>
>> On Saturday, 12 January 2019 07:04:35 UTC+10, Luigi Carbonera wrote:
>>>
>>> Hello
>>> I have to change the wind direction in the noaa report
>>> by degrees such as NNE .. NW .. SE
>>> I tried with  "  $ day.windDir.ordinal_compass.nolabel  "   without
>>> success.
>>> and put the point between the data
>>>
>>> #for $day in $month.days
>>> #if $day.barometer.count.raw
>>> $day.dateTime.format($D) $day.outTemp.avg.nolabel($Temp,$NONE)
>>> $day.outTemp.max.nolabel($Temp,$NONE) $day.outTemp.maxtime.format($Time)
>>> $day.outTemp.min.nolabel($Temp,$NONE) $day.outTemp.mintime.format($Time)
>>> $day.heatdeg.sum.nolabel($Temp,$NONE) $day.cooldeg.sum.nolabel($Temp,$NONE)
>>> $day.rain.sum.nolabel($Rain,$NONE) $day.wind.avg.nolabel($Wind,$NONE)
>>> $day.wind.max.nolabel($Wind,$NONE) $day.wind.maxtime.format($Time)
>>> $day.windDir.ordinal_compass.nolabel($Dir,$NONE)
>>> #else
>>> $day.dateTime.format($D)
>>> #end if
>>> #end for
>>>
>>>
>>>
>>> This is because I have a php program that reads me the text files noaa
>>> and I would also do it for WeeWx
>>> http://sacilemeteo.altervista.org/statd/rapporto-mensile.php
>>>
>>> Solution?
>>> Thank you
>>> Luigi
>>>
>>> generated  WeeWx
>>>
>>>
>>>
>>>TEMPERATURE (°C), RAIN (mm), WIND SPEED (km/h)
>>>
>>>  HEAT   COOL AVG
>>>   MEAN   DEGDEG
>>> WIND   DOM
>>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
>>> HIGH   TIMEDIR
>>>
>>> ---
>>>  01   -0,91,9  12:24   -2,8  20:43   19,30,00,02,2
>>> 12,9  12:33242
>>>  021,05,3  04:04   -3,1  23:34   17,40,00,03,1
>>> 27,4  10:16356
>>>  03   -2,90,4  14:39   -5,0  18:39   21,30,00,02,3
>>> 20,9  12:14190
>>>  04   -4,6   -1,4  15:33   -7,3  07:49   23,00,00,02,5
>>> 12,9  10:33211
>>>  05   -0,44,3  21:58   -5,9  01:47   18,70,00,02,1
>>> 12,9  21:51355
>>>  064,08,5  14:580,1  01:53   14,30,00,03,2
>>> 14,5  16:03 43
>>>  07   -0,70,9  00:00   -1,8  23:59   19,00,00,01,0
>>> 11,3  10:57139
>>>  08   -1,6   -0,2  23:50   -3,3  18:54   19,90,00,01,4
>>> 12,9  02:58203
>>>  090,73,9  12:50   -1,4  23:52   17,60,00,02,1
>>> 16,1  14:23 58
>>>  10   -0,83,3  15:34   -2,8  20:23   19,20,00,02

Re: [weewx-user] Option -y of wee_device --dump or --clear-memory does not work

[Heriberto Ochoa]

Hello, I'm actually try use the file vantage.py

as
they recommended me, but in the comment of this issue
 mention the opposite, of not
mix file with another version of weewx, as the master, so, as fix this
principal error??

On Fri, Jan 11, 2019 at 3:42 PM Heriberto Ochoa 
wrote:

> The previous message is after of replace the file vantage.py for this
> 
>  .
>
> On Fri, Jan 11, 2019 at 9:57 AM Heriberto Ochoa 
> wrote:
>
>> The parameters --reconfiguration is done but while I configure in the
>> option of select the drivers not work, the output is the next:
>>
>> Installed drivers include:
>>   0) AcuRite (weewx.drivers.acurite)
>>   1) CC3000  (weewx.drivers.cc3000)
>>   2) FineOffsetUSB   (weewx.drivers.fousb)
>>   3) Simulator   (weewx.drivers.simulator)
>>   4) TE923   (weewx.drivers.te923)
>>   5) Ultimeter   (weewx.drivers.ultimeter)
>>   6) ?   (weewx.drivers.vantage)   cannot import name int2byte
>>   7) WMR100  (weewx.drivers.wmr100)
>>   8) WMR200  (weewx.drivers.wmr200)
>>   9) WMR300  (weewx.drivers.wmr300)
>>  10) WMR9x8  (weewx.drivers.wmr9x8)
>>  11) WS1 (weewx.drivers.ws1)
>>  12) WS23xx  (weewx.drivers.ws23xx)
>>  13) WS28xx  (weewx.drivers.ws28xx)
>> choose a driver [6]:
>> Traceback (most recent call last):
>>   File "bin/wee_config", line 115, in 
>> main()
>>   File "bin/wee_config", line 110, in main
>> config_mgr.run(args, options)
>>   File "/home/weewx/bin/weecfg/config.py", line 102, in run
>> self.modify_config(config_dict, options)
>>   File "/home/weewx/bin/weecfg/config.py", line 120, in modify_config
>> stn_info = self.get_stn_info(config_dict, options)
>>   File "/home/weewx/bin/weecfg/config.py", line 151, in get_stn_info
>> stn_info.update(weecfg.prompt_for_driver_settings(driver))
>>   File "/home/weewx/bin/weecfg/__init__.py", line 1136, in
>> prompt_for_driver_settings
>> __import__(driver)
>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 18, in 
>> from weeutil.weeutil import to_int, int2byte
>> ImportError: cannot import name int2byte
>>
>>
>> The service of weewx it was stop previously, and in the syslog not show
>> nothing, the last line show that the service it was stop
>>
>> On Thu, Jan 10, 2019 at 7:19 PM Thomas Keffer  wrote:
>>
>>> Be sure to post the log file: it should tell you why the configurator
>>> did not load.
>>>
>>> On Thu, Jan 10, 2019 at 5:08 PM Heriberto Ochoa 
>>> wrote:
>>>
 I'm trying but now that remplace the file and try configurate the
 intervals, I get the next output:

 pi@raspberrypi:/home/weewx $ sudo bin/wee_device weewx.conf
 --set-interval=5
 Using configuration file weewx.conf
 Cannot load configurator for Vantage

 On Thu, Jan 10, 2019 at 5:09 PM Thomas Keffer 
 wrote:

> Fixed.
>
> However, you need *just* the version of vantage.py from the
> development branch, not everything. The development branch is a work in
> progress, and not always in a runnable state.
>
> -tk
>
> On Thu, Jan 10, 2019 at 3:58 PM Heriberto Ochoa <
> h.oc...@sistemasa3.com> wrote:
>
>> And with command --set-interval of wee_device the output is the next:
>>
>> pi@raspberrypi:~/weewx/bin $ sudo ./wee_device
>> /home/pi/weewx/weewx.conf --set-interval=5
>> Using configuration file /home/pi/weewx/weewx.conf
>> No configuration for device 'unspecified'
>>
>> On Thu, Jan 10, 2019 at 4:55 PM Heriberto Ochoa <
>> h.oc...@sistemasa3.com> wrote:
>>
>>> I'm trying recofigure the service weewx of the next shape:
>>> pi@raspberrypi:~/weewx/bin $ ./wee_config /home/pi/weewx/weewx.conf
>>> --reconfigure
>>> Traceback (most recent call last):
>>>   File "./wee_config", line 121, in 
>>> main()
>>>   File "./wee_config", line 115, in main
>>> config_mgr.run(args, options)
>>>   File "/home/pi/weewx/bin/weecfg/config.py", line 41, in run
>>> if not options.patch_skins \
>>> AttributeError: Values instance has no attribute 'patch_skins'
>>>
>>> the version is development of git repository
>>>
>>> On Thu, Jan 10, 2019 at 1:30 PM Thomas Keffer 
>>> wrote:
>>>
 The fix is in the Vantage driver version 3.1.0, while your email
 shows 3.0.11.

 I would guess that you downloaded from the git branch 'master'
 instead of 'development'.

 Try the version
 
 in development.

 -tk

 On Thu, Jan 10, 2019 at 11:33 AM Heriberto Ochoa <

Re: [weewx-user] Option -y of wee_device --dump or --clear-memory does not work

[Thomas Keffer]

Yes. The version of vantage.py that you linked to can only be used with the
development branch of WeeWX.

Sorry for any confusion.

-tk

On Sat, Jan 12, 2019 at 9:12 AM Heriberto Ochoa 
wrote:

> Hello, I'm actually try use the file vantage.py
> 
>  as
> they recommended me, but in the comment of this issue
>  mention the opposite, of not
> mix file with another version of weewx, as the master, so, as fix this
> principal error??
>
> On Fri, Jan 11, 2019 at 3:42 PM Heriberto Ochoa 
> wrote:
>
>> The previous message is after of replace the file vantage.py for this
>> 
>>  .
>>
>> On Fri, Jan 11, 2019 at 9:57 AM Heriberto Ochoa 
>> wrote:
>>
>>> The parameters --reconfiguration is done but while I configure in the
>>> option of select the drivers not work, the output is the next:
>>>
>>> Installed drivers include:
>>>   0) AcuRite (weewx.drivers.acurite)
>>>   1) CC3000  (weewx.drivers.cc3000)
>>>   2) FineOffsetUSB   (weewx.drivers.fousb)
>>>   3) Simulator   (weewx.drivers.simulator)
>>>   4) TE923   (weewx.drivers.te923)
>>>   5) Ultimeter   (weewx.drivers.ultimeter)
>>>   6) ?   (weewx.drivers.vantage)   cannot import name
>>> int2byte
>>>   7) WMR100  (weewx.drivers.wmr100)
>>>   8) WMR200  (weewx.drivers.wmr200)
>>>   9) WMR300  (weewx.drivers.wmr300)
>>>  10) WMR9x8  (weewx.drivers.wmr9x8)
>>>  11) WS1 (weewx.drivers.ws1)
>>>  12) WS23xx  (weewx.drivers.ws23xx)
>>>  13) WS28xx  (weewx.drivers.ws28xx)
>>> choose a driver [6]:
>>> Traceback (most recent call last):
>>>   File "bin/wee_config", line 115, in 
>>> main()
>>>   File "bin/wee_config", line 110, in main
>>> config_mgr.run(args, options)
>>>   File "/home/weewx/bin/weecfg/config.py", line 102, in run
>>> self.modify_config(config_dict, options)
>>>   File "/home/weewx/bin/weecfg/config.py", line 120, in modify_config
>>> stn_info = self.get_stn_info(config_dict, options)
>>>   File "/home/weewx/bin/weecfg/config.py", line 151, in get_stn_info
>>> stn_info.update(weecfg.prompt_for_driver_settings(driver))
>>>   File "/home/weewx/bin/weecfg/__init__.py", line 1136, in
>>> prompt_for_driver_settings
>>> __import__(driver)
>>>   File "/home/weewx/bin/weewx/drivers/vantage.py", line 18, in 
>>> from weeutil.weeutil import to_int, int2byte
>>> ImportError: cannot import name int2byte
>>>
>>>
>>> The service of weewx it was stop previously, and in the syslog not show
>>> nothing, the last line show that the service it was stop
>>>
>>> On Thu, Jan 10, 2019 at 7:19 PM Thomas Keffer  wrote:
>>>
 Be sure to post the log file: it should tell you why the configurator
 did not load.

 On Thu, Jan 10, 2019 at 5:08 PM Heriberto Ochoa 
 wrote:

> I'm trying but now that remplace the file and try configurate the
> intervals, I get the next output:
>
> pi@raspberrypi:/home/weewx $ sudo bin/wee_device weewx.conf
> --set-interval=5
> Using configuration file weewx.conf
> Cannot load configurator for Vantage
>
> On Thu, Jan 10, 2019 at 5:09 PM Thomas Keffer 
> wrote:
>
>> Fixed.
>>
>> However, you need *just* the version of vantage.py from the
>> development branch, not everything. The development branch is a work in
>> progress, and not always in a runnable state.
>>
>> -tk
>>
>> On Thu, Jan 10, 2019 at 3:58 PM Heriberto Ochoa <
>> h.oc...@sistemasa3.com> wrote:
>>
>>> And with command --set-interval of wee_device the output is the next:
>>>
>>> pi@raspberrypi:~/weewx/bin $ sudo ./wee_device
>>> /home/pi/weewx/weewx.conf --set-interval=5
>>> Using configuration file /home/pi/weewx/weewx.conf
>>> No configuration for device 'unspecified'
>>>
>>> On Thu, Jan 10, 2019 at 4:55 PM Heriberto Ochoa <
>>> h.oc...@sistemasa3.com> wrote:
>>>
 I'm trying recofigure the service weewx of the next shape:
 pi@raspberrypi:~/weewx/bin $ ./wee_config
 /home/pi/weewx/weewx.conf --reconfigure
 Traceback (most recent call last):
   File "./wee_config", line 121, in 
 main()
   File "./wee_config", line 115, in main
 config_mgr.run(args, options)
   File "/home/pi/weewx/bin/weecfg/config.py", line 41, in run
 if not options.patch_skins \
 AttributeError: Values instance has no attribute 'patch_skins'

 the version is development of git repository

 On Thu, Jan 10, 2019 at 1:30 PM Thomas Keffer 
 wrote:

> The fix is in the Vantage driver version 3.1.0, while your email
> shows 3.0.11.
>
> I would guess that you dow

[weewx-user] Re: use Weewx on raspberry

[Patrick Tranchant]

hello Gary or Pat
here are some values ​​found and comparison with my scripts ( excel file in 
attach)
I don't have always data with rain and wind !!!

*Oops I just saw that I forgot to put* "record_generation = software";

*but it changes nothing, I think*

*have a good week-end.*

Patrick

On Saturday, December 8, 2018 at 3:40:43 PM UTC+1, Patrick Tranchant wrote:
>
> hello I am a newbie from France ( sorry for my english )
>
> I want to use weewx on a raspberry with a weather station built by myself 
> (view on Magpi)
> I don't see my station on your website to configure :
>
> Weather Station Hardware Comparison: I don't found my weather station.
> Do you have a solution or how to configure Weewx
>
> thank you for your help
>
> Patrick
>

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


valeurs-weewx-vs-scripts-python.xlsx
Description: MS-Excel 2007 spreadsheet

Re: [weewx-user] Re: Metric v US databases

[Andrew Milner]

…… and from my point of view it was trying to disagree with the premise of 
'do not change unless you have to' when in fact, for most of the world, 
life is much much easier if you do change and store data as metric.  In 
particular it is highly likely that most of the world set their stations to 
display metric even if the native data is US and so it makes logical sense 
(to me at least) to say that if you display metric set the database to 
metric and let weewx take care of any device conversions - but keep the 
database in the units you usually use/display.  I think, but cannot recall 
exactly, that in fact fine offset and its many clones stores data as metric 
and outputs metric.

Anyways Tom, as I said in the first place, it is not a real issue, but I do 
feel users should feel free to set the database to whatever units they use, 
and not feel obliged (because of warnings etc) to have their database in 
'alien' units.  Moreover, if the database is metric then the default unit 
groups and units should default to match.

It's still great sw and immensely flexible and I love it - even if I do 
have an occasional whine or winge or whinge or whatever.  Maybe another 
wine is called for.



On Saturday, 12 January 2019 16:11:31 UTC+2, pon...@gmail.com wrote:
>
> No imputations of personal cussedness were implied, more of a suggestion 
> that it would be nice to see a default of international standards first. 
> That is all. Your own expertise and background are well known and respected 
> by anyone who's bothered to inform themselves. Apologies if you thought 
> otherwise. My suggestion of forking was an expression of annoyance with the 
> whole business of the US's eccentricity, not on the practical, functional 
> significance, and I tried to acknowledge and qualify.
>

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

Re: [weewx-user] Re: Metric v US databases

[Colin Larsen]

First thing I did was set my db to metric, no issues at all. Freedom of
choice. Perhaps the "warning" is a little over the top but common sense
should prevail.

Colin

On Sun, 13 Jan 2019, 07:59 Andrew Milner  …… and from my point of view it was trying to disagree with the premise of
> 'do not change unless you have to' when in fact, for most of the world,
> life is much much easier if you do change and store data as metric.  In
> particular it is highly likely that most of the world set their stations to
> display metric even if the native data is US and so it makes logical sense
> (to me at least) to say that if you display metric set the database to
> metric and let weewx take care of any device conversions - but keep the
> database in the units you usually use/display.  I think, but cannot recall
> exactly, that in fact fine offset and its many clones stores data as metric
> and outputs metric.
>
> Anyways Tom, as I said in the first place, it is not a real issue, but I
> do feel users should feel free to set the database to whatever units they
> use, and not feel obliged (because of warnings etc) to have their database
> in 'alien' units.  Moreover, if the database is metric then the default
> unit groups and units should default to match.
>
> It's still great sw and immensely flexible and I love it - even if I do
> have an occasional whine or winge or whinge or whatever.  Maybe another
> wine is called for.
>
>
>
> On Saturday, 12 January 2019 16:11:31 UTC+2, pon...@gmail.com wrote:
>>
>> No imputations of personal cussedness were implied, more of a suggestion
>> that it would be nice to see a default of international standards first.
>> That is all. Your own expertise and background are well known and respected
>> by anyone who's bothered to inform themselves. Apologies if you thought
>> otherwise. My suggestion of forking was an expression of annoyance with the
>> whole business of the US's eccentricity, not on the practical, functional
>> significance, and I tried to acknowledge and qualify.
>>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: change noaa report wind direction

[Luigi Carbonera]

Hello
Hi there is the average wind direction in the NOAA report.
Instead expressed in degrees both in N-NE - E etc.
With this I have in degrees  $day.wind.vecdir.nolabel($Dir,$NONE)
TEMPERATURE (°C), RAIN (mm), WIND SPEED (km/h)

 HEAT   COOL AVG
  MEAN   DEGDEG  
WIND   DOM
DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH   
TIMEDIR
---
 01   -0,91,9  12:24   -2,8  20:43   19,30,00,02,2   12,9  
12:33242
 021,05,3  04:04   -3,1  23:34   17,40,00,03,1   27,4  
10:16356
 03   -2,90,4  14:39   -5,0  18:39   21,30,00,02,3   20,9  
12:14190
 04   -4,6   -1,4  15:33   -7,3  07:49   23,00,00,02,5   12,9  
10:33211


I would like to

MEAN  DEG   DEG WIND DOM
DAY TEMP  HIGH   TIME   LOWTIME   DAYS  DAYS  RAIN  SPEED HIGH   
TIMEDIR

 1   1.8   7.8   12.43  -2.18.05  16.4   0.0   0.0   1.3  14.5   
12.33   NNE
 2   3.2  12.1   12.15  -3.38.06  15.1   0.0   0.0   4.5  40.2   
13.10 N
 3   1.3   7.6   13.40  -4.37.47  17.0   0.0   0.0   3.5  17.7
4.44   WSW
 4   0.6   5.5   14.13  -4.17.59  17.7   0.0   0.0   4.5  25.7   
13.00NE
 5  -1.1   4.4   15.35  -4.87.08  19.3   0.0   0.0   1.3  11.3   
15.09   NNE

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

Re: [weewx-user] Re: change noaa report wind direction

[Thomas Keffer]

$day.wind.vecdir.ordinal_compass should get you what you want.

-tk

On Sat, Jan 12, 2019 at 2:36 PM Luigi Carbonera 
wrote:

> Hello
> Hi there is the average wind direction in the NOAA report.
> Instead expressed in degrees both in N-NE - E etc.
> With this I have in degrees  $day.wind.vecdir.nolabel($Dir,$NONE)
> TEMPERATURE (°C), RAIN (mm), WIND SPEED (km/h)
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG
> WIND   DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
> HIGH   TIMEDIR
>
> ---
>  01   -0,91,9  12:24   -2,8  20:43   19,30,00,02,2   12,9
> 12:33242
>  021,05,3  04:04   -3,1  23:34   17,40,00,03,1   27,4
> 10:16356
>  03   -2,90,4  14:39   -5,0  18:39   21,30,00,02,3   20,9
> 12:14190
>  04   -4,6   -1,4  15:33   -7,3  07:49   23,00,00,02,5   12,9
> 10:33211
>
>
> I would like to
>
> MEAN  DEG   DEG WIND
> DOM
> DAY TEMP  HIGH   TIME   LOWTIME   DAYS  DAYS  RAIN  SPEED HIGH
> TIMEDIR
>
> 
>  1   1.8   7.8   12.43  -2.18.05  16.4   0.0   0.0   1.3  14.5
> 12.33   NNE
>  2   3.2  12.1   12.15  -3.38.06  15.1   0.0   0.0   4.5  40.2
> 13.10 N
>  3   1.3   7.6   13.40  -4.37.47  17.0   0.0   0.0   3.5  17.7
> 4.44   WSW
>  4   0.6   5.5   14.13  -4.17.59  17.7   0.0   0.0   4.5  25.7
> 13.00NE
>  5  -1.1   4.4   15.35  -4.87.08  19.3   0.0   0.0   1.3  11.3
> 15.09   NNE
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: change noaa report wind direction

[Luigi Carbonera]

It does not work with $day.wind.vecdir.ordinal_compass($Dir,$NONE)
It does not send the NOAA.txt

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

Re: [weewx-user] Re: Metric v US databases

[gjr80]

I guess since a couple of my recent posts have been the catalyst for this 
thread it is appropriate that I reply.

I think that what has been been omitted here is the context of my posts. In 
both cases I was helping novice weeWX users, one who was clearly having 
'units' issues and another who after a reinstall their target_unit setting 
had changed. From my point of view if you are tracking down a 'units' issue 
one of the last things you ought to be doing is changing database units, it 
may well have no effect on the problem but it is a further complication 
that is not needed. In the second case the change of target_unit actually 
caused weeWX to exit. One could argue that is justification for the warning 
to not change this setting unless you know what you are doing.

I am well aware of the convenience of having your database use a unit 
system that matches/largely matches your locally used units. I live in 
Australia and I changed my unit system to Metric many years ago so I have 
no problem whatsoever if one chooses to change ones database unit system. 
However, for a new user, particularly one who is having issues or is not 
prone to looking under the hood, starting with the default to get a stable 
system in my view is appropriate advice. I see similarities with moving 
from SQLite to MySQL/MariaDB, no problems with the change but probably not 
something a new user/novice should do from the start.

I stand by the advice I gave in the context it was given. I guess that is 
the beauty of FOSS, anyone is welcome to submit a change request and/or add 
a page to the wiki.

I have nothing further to say on this topic.

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

[weewx-user] Re: use Weewx on raspberry

[gjr80]

Patrick,

On Sunday, 13 January 2019 03:53:38 UTC+10, Patrick Tranchant wrote:
> hello Gary or Pat
> here are some values ​​found and comparison with my scripts ( excel file 
> in attach)
> I don't have always data with rain and wind !!!
>

It is very hard to draw any conclusions from your spreadsheet. I am not 
sure what data your US and FR rows represent but seeing as you mention 
dateTime, usUnits and interval I am guessing that these have come from the 
archive table in your database. If this is the case you need to take some 
care in comparing them to other data. The data in an archive record (each 
row in your archive table) is based on the accumulation of all of the loop 
packets generated by your driver over the archive period (in your case 5 
minutes). In most cases the archive record value is an average of all the 
loop values seen (eg temperature, pressure, wind speed) but some are an 
accumulation (eg rain). If you wish to compare the results from your python 
program to weeWX then you need to compare with point-in-time values or the 
loop data rather than anything in the archive table (this assumes that your 
python program reads instantaneous values and does not average over time). 
You would also need to make sure you were obtaining values at the same 
point in time, I don't know how often your sensors update but if your 
python program reads the sensors 5 seconds before the weeWX driver does 
then the sensor may have changed value. 

Assuming that your python program and weeWX reside on the same machine what 
you could do is open two terminal windows and arrange them so you can see 
both on screen at the same time. In one window run weeWX directly so you 
can observe the values in individual loop packets. In the other window run 
your python program and have it display its results on screen. Focus on one 
observation at a time and compare the values in both windows, temperature, 
humidity and pressure are good starters as they should not change too 
rapidly; wind speed and rain are poor choices as they change too rapidly 
and too slowly respectively. If you wanted to record data from comparison 
later be sure to include some sort of timestamp/system date-time on your 
python observations. If you capture the weeWX screen output then you should 
have a timestamp for the loop packets generated by your driver.

I hope this helps.
 

> *Oops I just saw that I forgot to put* "record_generation = software";
>
> *but it changes nothing, I think*
>
> *have a good week-end.*
>

Now that I think of it on your system having record_generation = hardware 
would not matter as if your driver is not capable of generating a hardware 
archive record (and your driver is not capable) weeWX automatically falls 
back to generating one in software. At least having record_generation = 
software in weewx.conf makes it clear how your system/driver is to function.
 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: change noaa report wind direction

[Thomas Keffer]

It's just $day.wind.vecdir.ordinal_compass.




On Sat, Jan 12, 2019 at 3:24 PM Luigi Carbonera 
wrote:

>
> It does not work with $day.wind.vecdir.ordinal_compass($Dir,$NONE)
> It does not send the NOAA.txt
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

I have managed to get the Standard skin loaded on my weather website 
www.wilsonbayweather.com...2 small adjustments I would like to 
make..how do I show the historical max and min for temp, wind, rain 
etcand how might I include a jpeg photo from webcam showing a picture 
every hour or so? Thanks in advance.you guys have been fabulous in 
helping a newbie!

On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd 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 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Real Time Gauges (RTGD) for Steel Series

[nineback]

I am just starting to attempt to set these up.  I intend to use the
post_gauge-data.php to get the files on my off-site server.  The
instructions say:

 

Note: If the SteelSeries weeWX skin is installed either disable the skin or
ensure that the Realtime gauge-data extension generated gauge-data.txt file
is saved to a different location to that generated by the SteelSeries weeWX
skin.

 

Doesn't the SS skin generate the index.html file and the graphs.  I might
have read somewhere that the graphs do not work with the RTGD extension but
I would think you need the index.html?  So do go into the weex.conf file and
but ##skin=ss and that is all other than modifying the rtgd.py file?

 

Tom

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

RE: [weewx-user] Real Time Gauges (RTGD) for Steel Series

[nineback]

OK.  I see more detailed instructions in the rtgd.py file.  I’ll give it a go 
though I may wait until tomorrow morning when I am fresh.  The steps seem 
pretty involved for us novices.  It does appear as though the gauge-data.txt 
file generated by SS is placed in the public_html/ss directory and the RTGD 
will place it in the public_html do it should not be an issue.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
nineb...@gmail.com
Sent: Saturday, January 12, 2019 7:55 PM
To: weewx-user@googlegroups.com
Subject: [weewx-user] Real Time Gauges (RTGD) for Steel Series

 

I am just starting to attempt to set these up.  I intend to use the 
post_gauge-data.php to get the files on my off-site server.  The instructions 
say:

 

Note: If the SteelSeries weeWX skin is installed either disable the skin or 
ensure that the Realtime gauge-data extension generated gauge-data.txt file is 
saved to a different location to that generated by the SteelSeries weeWX skin.

 

Doesn’t the SS skin generate the index.html file and the graphs.  I might have 
read somewhere that the graphs do not work with the RTGD extension but I would 
think you need the index.html?  So do go into the weex.conf file and but 
##skin=ss and that is all other than modifying the rtgd.py file?

 

Tom

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

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

[gjr80]

Correct, you just want to disable generation of gauge-data.txt by the skin. 
As you have found the instructions in rtgd.py (step 6 I think) are correct.

The offending staff member has since been fired.

Gary

On Sunday, 13 January 2019 12:07:52 UTC+10, nine...@gmail.com wrote:
>
> OK.  I see more detailed instructions in the rtgd.py file.  I’ll give it a 
> go though I may wait until tomorrow morning when I am fresh.  The steps 
> seem pretty involved for us novices.  It does appear as though the 
> gauge-data.txt file generated by SS is placed in the public_html/ss 
> directory and the RTGD will place it in the public_html do it should not be 
> an issue.
>
>  
>
> Tom
>
>  
>
> *From:* weewx...@googlegroups.com   > *On Behalf Of *nine...@gmail.com 
> *Sent:* Saturday, January 12, 2019 7:55 PM
> *To:* weewx...@googlegroups.com 
> *Subject:* [weewx-user] Real Time Gauges (RTGD) for Steel Series
>
>  
>
> I am just starting to attempt to set these up.  I intend to use the 
> post_gauge-data.php to get the files on my off-site server.  The 
> instructions say:
>
>  
>
> *Note:* If the SteelSeries weeWX skin is installed either disable the 
> skin or ensure that the *Realtime gauge-data* extension generated 
> *gauge-data.txt* file is saved to a different location to that generated 
> by the SteelSeries weeWX skin.
>
>  
>
> Doesn’t the SS skin generate the index.html file and the graphs.  I might 
> have read somewhere that the graphs do not work with the RTGD extension but 
> I would think you need the index.html?  So do go into the weex.conf file 
> and but ##skin=ss and that is all other than modifying the rtgd.py file?
>
>  
>
> Tom
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com .
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[gjr80]

Hi,

There are a few steps involved in achieving what you want to do. First the 
historical max/min - by this I presume you mean all time statistics - those 
that cover all of your weeWX data and not just the last day, month or year. 

If I have this right you need to extend weeWX so that you can access stats 
from all of your data, this is most easily achieved by installing the 
xstats example extension. You will find the xstats files are in the 
/usr/share/doc/weewx/examples directory. I would install manually and just 
follow step 1 in the readme.txt remembering later that you will need to 
enable the alltime stats for your templates/reports by following step 2. 
You can install xstats using wee_extension but that will also install the 
example web page which you probably do not want.

Now that you have xstats installed you can use tags like 
$alltime.outTemp.max in report templates to display the maximum outside 
temperature. The time it occurred will be $alltime.outTemp.maxtime. Just 
like $day, $month and $year tags but you use $alltime. If you are not 
familiar with weeWX tags it is worth reading the Tags section 
 of the Customization Guide.

To use the $alltime tags you will probably want to create a new page or 
modify an existing one. It is really up to you want you want to do. To 
modify an existing page have a look at the .tmpl files in you Standard skin 
directory /etc/weewx/skins/Standard. These are the files weeWX uses to 
generate a corresponding .html page. You will see how tags are used in a 
template, in a nutshell where you place a tag weeWX will replace that with 
the relevant data when the reports are generated. The process is a little 
more involved if you want to create a new page as not only do you need to 
modify/create a page but you also need to modify skin.conf to have weeWX 
generate the new page. You may also need to modify other pages to include a 
link to your new page. A good starting point may be to take a copy of 
/etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl and 
start modifying. Have a good poke around the templates and skin.conf (and 
[StdReport] in weewx.conf) to see how it comes together. 

Including an image in a weeWX generated page can be relatively 
straightforward. If you have a look in index.html.tmpl you will see lines 
such as:



This line creates a HTML img tag that displays the daily temperature and 
dewpoint plot. If whatever you use to generate your webcam image can create 
a file named, say, webcam.jpg then that keeps it easy, you may be able to 
create a new img tag but using webcam.jpg (rather than daytempdew.png), you 
may need to add a path in front of the file name. If your webcam image is 
timestamped like webcam201901131345.jpg then that gets a little more 
complicated. If you can drop your webcam image into the weeWX directory 
structure under /var/www/html/weewx then you can very easily use weeWX to 
upload your webcam image to your web server if you wish. There are many 
different ways to achieve this, I have outlined one and I am sure other 
will have other ways. At the end of the day it will likely depend on your 
setup.

You have started on the slippery slope of customising your weeWX install, 
the process can appear daunting but do persist and feel free to continue to 
ask if not sure.

Gary
 
On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote:
>
> I have managed to get the Standard skin loaded on my weather website 
> www.wilsonbayweather.com...2 small adjustments I would like to 
> make..how do I show the historical max and min for temp, wind, rain 
> etcand how might I include a jpeg photo from webcam showing a picture 
> every hour or so? Thanks in advance.you guys have been fabulous in 
> helping a newbie!
>
>

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

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

WOW! thank you so much, Gary, for the pointers.I will get on to that in 
the next few days!

On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>
> Hi,
>
> There are a few steps involved in achieving what you want to do. First the 
> historical max/min - by this I presume you mean all time statistics - those 
> that cover all of your weeWX data and not just the last day, month or year. 
>
> If I have this right you need to extend weeWX so that you can access stats 
> from all of your data, this is most easily achieved by installing the 
> xstats example extension. You will find the xstats files are in the 
> /usr/share/doc/weewx/examples directory. I would install manually and 
> just follow step 1 in the readme.txt remembering later that you will need 
> to enable the alltime stats for your templates/reports by following step 2. 
> You can install xstats using wee_extension but that will also install the 
> example web page which you probably do not want.
>
> Now that you have xstats installed you can use tags like 
> $alltime.outTemp.max in report templates to display the maximum outside 
> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just 
> like $day, $month and $year tags but you use $alltime. If you are not 
> familiar with weeWX tags it is worth reading the Tags section 
>  of the Customization Guide.
>
> To use the $alltime tags you will probably want to create a new page or 
> modify an existing one. It is really up to you want you want to do. To 
> modify an existing page have a look at the .tmpl files in you Standard 
> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses 
> to generate a corresponding .html page. You will see how tags are used in a 
> template, in a nutshell where you place a tag weeWX will replace that with 
> the relevant data when the reports are generated. The process is a little 
> more involved if you want to create a new page as not only do you need to 
> modify/create a page but you also need to modify skin.conf to have weeWX 
> generate the new page. You may also need to modify other pages to include a 
> link to your new page. A good starting point may be to take a copy of 
> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl 
> and start modifying. Have a good poke around the templates and skin.conf 
> (and [StdReport] in weewx.conf) to see how it comes together. 
>
> Including an image in a weeWX generated page can be relatively 
> straightforward. If you have a look in index.html.tmpl you will see lines 
> such as:
>
> 
>
> This line creates a HTML img tag that displays the daily temperature and 
> dewpoint plot. If whatever you use to generate your webcam image can create 
> a file named, say, webcam.jpg then that keeps it easy, you may be able to 
> create a new img tag but using webcam.jpg (rather than daytempdew.png), 
> you may need to add a path in front of the file name. If your webcam image 
> is timestamped like webcam201901131345.jpg then that gets a little more 
> complicated. If you can drop your webcam image into the weeWX directory 
> structure under /var/www/html/weewx then you can very easily use weeWX to 
> upload your webcam image to your web server if you wish. There are many 
> different ways to achieve this, I have outlined one and I am sure other 
> will have other ways. At the end of the day it will likely depend on your 
> setup.
>
> You have started on the slippery slope of customising your weeWX install, 
> the process can appear daunting but do persist and feel free to continue to 
> ask if not sure.
>
> Gary
>  
> On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote:
>>
>> I have managed to get the Standard skin loaded on my weather website 
>> www.wilsonbayweather.com...2 small adjustments I would like to 
>> make..how do I show the historical max and min for temp, wind, rain 
>> etcand how might I include a jpeg photo from webcam showing a picture 
>> every hour or so? Thanks in advance.you guys have been fabulous in 
>> helping a newbie!
>>
>>

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

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

Just BTW, the readme.txt is wrong about where wee_extension is 
stored.as under a deb install it is stored in /usr/share/weewx/

When I run the suggested command, this is what I get.

pi@raspberrypi:~ $ wee_extension --install=/usr/share/weewx/wee_extension
Request to install '/usr/share/weewx/wee_extension'
Extracting from tar archive /usr/share/weewx/wee_extension
Traceback (most recent call last):
  File "/usr/bin/wee_extension", line 83, in 
main()
  File "/usr/bin/wee_extension", line 75, in main
ext.install_extension(options.install)
  File "/usr/share/weewx/weecfg/extension.py", line 110, in 
install_extension
self.tmpdir, self.logger)
  File "/usr/share/weewx/weecfg/__init__.py", line 1240, in extract_tar
tar_archive = tarfile.open(filename, mode='r')
  File "/usr/lib/python2.7/tarfile.py", line 1680, in open
raise ReadError("file could not be opened successfully")
tarfile.ReadError: file could not be opened successfully



On Sunday, 13 January 2019 17:15:11 UTC+13, monmul wrote:
>
> WOW! thank you so much, Gary, for the pointers.I will get on to that 
> in the next few days!
>
> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>>
>> Hi,
>>
>> There are a few steps involved in achieving what you want to do. First 
>> the historical max/min - by this I presume you mean all time statistics - 
>> those that cover all of your weeWX data and not just the last day, month or 
>> year. 
>>
>> If I have this right you need to extend weeWX so that you can access 
>> stats from all of your data, this is most easily achieved by installing the 
>> xstats example extension. You will find the xstats files are in the 
>> /usr/share/doc/weewx/examples directory. I would install manually and 
>> just follow step 1 in the readme.txt remembering later that you will 
>> need to enable the alltime stats for your templates/reports by following 
>> step 2. You can install xstats using wee_extension but that will also 
>> install the example web page which you probably do not want.
>>
>> Now that you have xstats installed you can use tags like 
>> $alltime.outTemp.max in report templates to display the maximum outside 
>> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just 
>> like $day, $month and $year tags but you use $alltime. If you are not 
>> familiar with weeWX tags it is worth reading the Tags section 
>>  of the Customization Guide.
>>
>> To use the $alltime tags you will probably want to create a new page or 
>> modify an existing one. It is really up to you want you want to do. To 
>> modify an existing page have a look at the .tmpl files in you Standard 
>> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses 
>> to generate a corresponding .html page. You will see how tags are used in a 
>> template, in a nutshell where you place a tag weeWX will replace that with 
>> the relevant data when the reports are generated. The process is a little 
>> more involved if you want to create a new page as not only do you need to 
>> modify/create a page but you also need to modify skin.conf to have weeWX 
>> generate the new page. You may also need to modify other pages to include a 
>> link to your new page. A good starting point may be to take a copy of 
>> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl 
>> and start modifying. Have a good poke around the templates and skin.conf 
>> (and [StdReport] in weewx.conf) to see how it comes together. 
>>
>> Including an image in a weeWX generated page can be relatively 
>> straightforward. If you have a look in index.html.tmpl you will see 
>> lines such as:
>>
>> 
>>
>> This line creates a HTML img tag that displays the daily temperature and 
>> dewpoint plot. If whatever you use to generate your webcam image can create 
>> a file named, say, webcam.jpg then that keeps it easy, you may be able 
>> to create a new img tag but using webcam.jpg (rather than daytempdew.png), 
>> you may need to add a path in front of the file name. If your webcam image 
>> is timestamped like webcam201901131345.jpg then that gets a little more 
>> complicated. If you can drop your webcam image into the weeWX directory 
>> structure under /var/www/html/weewx then you can very easily use weeWX 
>> to upload your webcam image to your web server if you wish. There are many 
>> different ways to achieve this, I have outlined one and I am sure other 
>> will have other ways. At the end of the day it will likely depend on your 
>> setup.
>>
>> You have started on the slippery slope of customising your weeWX install, 
>> the process can appear daunting but do persist and feel free to continue to 
>> ask if not sure.
>>
>> Gary
>>  
>> On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote:
>>>
>>> I have managed to get the Standard skin loaded on my weather website 
>>> www.wilsonbayweather.com...2 small adjustments I would like to 
>>> make..how do