[weewx-user] Re: Installing WeatherCloud Extension - Error

[Chotechai Piyavongsiri]

It is v.0.11 (know by peeking inside the tar file)

On Tuesday, 2 April 2019 10:02:35 UTC+7, Chotechai Piyavongsiri wrote:
>
> Here it is. Not sure what version it is.
>
> On Monday, 1 April 2019 16:45:15 UTC+7, Dave McCreath wrote:
>>
>> Has anyone got a copy of the tarball?
>>
>> Just asking, you never know.
>>
>> Dave
>>
>> On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>>>
>>> Thanks for getting back to me.  Looks like the link is down so unable to 
>>> download it!
>>>
>>> Regards
>>>
>>> Dave
>>>
>>> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:

 Hi,

 You need to replace x.y in the command you are using to install with 
 the version number in the install file you downloaded. The current version 
 appears to be 0.11 so try:

 $ wee_extension --install weewx-wcloud-0.11.tgz

 Using x.y or x.y.z is a common shorthand used to indicate you need to 
 replace the letters with the version you are using. Saves a bit of work 
 continually updating (and may be getting them out of date) instructions.

 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: Installing WeatherCloud Extension - Error

[Chotechai Piyavongsiri]

Here it is. Not sure what version it is.

On Monday, 1 April 2019 16:45:15 UTC+7, Dave McCreath wrote:
>
> Has anyone got a copy of the tarball?
>
> Just asking, you never know.
>
> Dave
>
> On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>>
>> Thanks for getting back to me.  Looks like the link is down so unable to 
>> download it!
>>
>> Regards
>>
>> Dave
>>
>> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> You need to replace x.y in the command you are using to install with the 
>>> version number in the install file you downloaded. The current version 
>>> appears to be 0.11 so try:
>>>
>>> $ wee_extension --install weewx-wcloud-0.11.tgz
>>>
>>> Using x.y or x.y.z is a common shorthand used to indicate you need to 
>>> replace the letters with the version you are using. Saves a bit of work 
>>> continually updating (and may be getting them out of date) instructions.
>>>
>>> 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-wcloud-x.y.tgz
Description: GNU Unix tar archive

[weewx-user] Re: Can two weewx servers receive data from one IP Observer?

[Chotechai Piyavongsiri]

Hi Chris,

Interesting; but both servers are using wifi communication.

On Monday, 1 April 2019 20:12:29 UTC+7, tomn...@frontier.com wrote:
>
> There are slightly fancier ethernet switches that can do port mirroring 
> that might do the trick.  I suppose of you had
> an ethernet hub  (not a switch), that would work also.
>
> Chris
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Has WU changed its API Key length

[Stefan Kear]

I've noticed this too but with the Amazon Echo devices. The new WU API key 
is 32 characters in length whereas the old key was 16. I tried to set the 
new API key with the current Weather Underground Alexa skill and "she" 
would only accept the first 16 characters. I'm unable to get the skill to 
work again since the new key is too long. It was a pretty cool skill when 
it was working.
Uploading to WU from my PWS works with no issues.
http://echohill.net/weather/

Stefan


On Monday, 1 April 2019 18:43:14 UTC-4, Paul Oversmith wrote:
>
> Have been using Weather Underground to download forecasts for several 
> years. 
> Stopped working with a key error end of March, 2019.  So I  got a new API 
> key, but now getting the following messages:
> Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
> download forecast from '
> http://api.wunderground.com/api/cbc1/hourly10day/q/34231.json
> '
>
> Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
> error in response: keynotfound: this key does not exist
>
> Seeing that the last 4 characters are outside the block out text, I was 
> wondering if they increased the key length and that is what is preventing 
> getting the forecast. Or perhaps I need to delete some of the API key. my 
> key is: d7xcbc1
>
> Uploads to WU work.
>
> Tried to download a current version of the forecasting code, but the site 
> seems to be down.
>
> Any suggestions on how to fix?
>
>
>

-- 
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: Has WU changed its API Key length

[Paul Oversmith]

I did some more checking and the WU API keys and calls have changed.  If 
you upload to WU you can get a new key. But until the forecasting code is 
updated they will not work because they change the API calls.

Any timeline for issuing a new forecasting addon WeewX?

For those that have not seen the WU notice, here it is:

If you have a personal weather station that uploads to Weather Underground 
and have been waiting to get a key for the new API, here are the 
instructions.

Please note that if you do NOT download data from the Weather Underground 
API, you probably don't need a key.  Uploading data to Wunderground from 
your PWS is not the same thing.



Dear PWS uploaders, thank you for your continued loyalty and patience!

*The gateway for the new API keys for PWS uploaders is open.*

Cut and paste this URL into your browser:  
https://www.wunderground.com/member/api-keys 


If you are not logged in, you will be asked to.  The system will also 
verify that you have a PWS uploading to the system.

You will then see a blank box below “Your API keys”.  Agree to the new 
Terms and Conditions by clicking in the small box next to “I agree”, click 
on the blue “GENERATE” box, and your new key will be created.  

The key will be masked on the screen, but you can use the “Show” link below 
the box to see it.  There is also another blue box, which, when clicked, 
copies the key to your clipboard.

If you have any problems, log out and log back in again.  If that does not 
resolve the problem, *please email me at victoria.gard...@ibm.com 
*
.

*Next*, once you have your new key, you can use it in the NEW (not old!) 
API’s commands.  The documentation for those commands is here:  
https://docs.google.com/document/d/1eKCnKXI9xnoMGRRzOL1xPCBihNV2rOet08qpE_gArAY/edit

The new API should work immediately once you have the new key in the new 
commands.

Remember that the new keys work on the new API only, and the old keys work 
on the old API only.

Old API keys that are associated with a PWS will be kept working until *March 
22, 2019.*  However, that will be *the very last day for those API keys to 
work*, so you should transition as quickly as you can to the new API.  

Victoria Gardner
Weather Underground API customer service

On Monday, April 1, 2019 at 6:43:14 PM UTC-4, Paul Oversmith wrote:
>
> Have been using Weather Underground to download forecasts for several 
> years. 
> Stopped working with a key error end of March, 2019.  So I  got a new API 
> key, but now getting the following messages:
> Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
> download forecast from '
> http://api.wunderground.com/api/cbc1/hourly10day/q/34231.json
> '
>
> Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
> error in response: keynotfound: this key does not exist
>
> Seeing that the last 4 characters are outside the block out text, I was 
> wondering if they increased the key length and that is what is preventing 
> getting the forecast. Or perhaps I need to delete some of the API key. my 
> key is: d7xcbc1
>
> Uploads to WU work.
>
> Tried to download a current version of the forecasting code, but the site 
> seems to be down.
>
> Any suggestions on how to fix?
>
>
>

-- 
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] weewx-multi with identical Fine Offset USB WS1081

[Harold Jarvie]

I am trying to run weewx-multi on a beagebone with 2 fousb WS1081 stations 
mammoth1 and mammoth2

mammoth1 runs fine but running mammoth2  generates the log below

I have tried using port = /dev/usb/hiddev0 for mammoth1 and port = 
/dev/usb/hiddev1 for mammoth2  but appears to be ignored

Apr  2 12:34:18 beaglebone weewx-mammoth2[13917]: engine: Initializing 
weewx version 3.9.1
Apr  2 12:34:18 beaglebone weewx-mammoth2[13917]: engine: Using Python 
2.7.13 (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Apr  2 12:34:18 beaglebone weewx-mammoth2[13917]: engine: Platform 
Linux-4.14.103-ti-r100-armv7l-with-debian-9.5
Apr  2 12:34:18 beaglebone weewx-mammoth2[13917]: engine: Locale is 
'en_US.UTF-8'
Apr  2 12:34:18 beaglebone weewx-mammoth2[13917]: engine: pid file is 
/var/run/weewx-mammoth2.pid
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: engine: Using 
configuration file /etc/weewx/mammoth2.conf
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: engine: Debug is 1
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: engine: Initializing 
engine
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: engine: Loading station 
type FineOffsetUSB (weewx.drivers.fousb)
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: fousb: driver version is 
1.9
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: fousb: polling mode is 
PERIODIC
Apr  2 12:34:18 beaglebone weewx-mammoth2[13926]: fousb: polling interval 
is 48
Apr  2 12:34:19 beaglebone weewx-mammoth2[13926]: fousb: found station on 
USB bus= device=
Apr  2 12:34:19 beaglebone weewx-mammoth2[13926]: fousb: Unable to claim 
USB interface 0: [Errno 16] Resource busy
Apr  2 12:34:19 beaglebone weewx-mammoth2[13926]: import of driver failed: 
[Errno 16] Resource busy ()
Apr  2 12:34:19 beaglebone weewx-mammoth2[13926]: engine: Unable to load 
driver: [Errno 16] Resource busy
Apr  2 12:34:19 beaglebone weewx-mammoth2[13926]:   Exiting... 


Any help appreciated
   

-- 
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] Has WU changed its API Key length

[Paul Oversmith]

Have been using Weather Underground to download forecasts for several 
years. 
Stopped working with a key error end of March, 2019.  So I  got a new API 
key, but now getting the following messages:
Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: 
download forecast from 
'http://api.wunderground.com/api/cbc1/hourly10day/q/34231.json'

Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: error 
in response: keynotfound: this key does not exist

Seeing that the last 4 characters are outside the block out text, I was 
wondering if they increased the key length and that is what is preventing 
getting the forecast. Or perhaps I need to delete some of the API key. my 
key is: d7xcbc1

Uploads to WU work.

Tried to download a current version of the forecasting code, but the site 
seems to be down.

Any suggestions on how to fix?


-- 
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] weewx-forecast-3.3.2

[zListserv]

lancet.mit.edu times out when I try to download the most recent version of 
weewx-forecast.

Is there another source?  Does anyone have a copy stored elsewhere?

(Sorry for the initial post.  My auto correct got the better of me.)

-- 
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] save a value for next iteration

[Thomas Keffer]

Sorry,  WeeWX is largely stateless. The database is the only persistent
store between report generations.

On Mon, Apr 1, 2019 at 2:18 PM  wrote:

> No, really what I want is to save a value in order to use it, if I need
> it, in one of the next iteration...
>
> Il giorno lunedì 1 aprile 2019 22:47:36 UTC+2, Thomas Keffer ha scritto:
>>
>> You would be "making up" data, which is very much against the philosophy
>> of WeeWX. Nevertheless, if you really want to do this, it is possible.
>> Basically, you do a database look up for the previous record. If you are
>> using a 60 second archive period (very short, BTW), it would look something
>> like this (NOT TESTED):
>>
>> #set $now = $current.dateTime.raw
>> #set $then = $now - 60
>>
>> The temperature now is $current.outTemp; for the previous record it
>> was $current(timestamp=$then).outTemp 
>>
>> On Mon, Apr 1, 2019 at 1:02 PM  wrote:
>>
>>> My vantage vue station and weewx are set that they save the meteo values
>>> every minute.
>>>
>>> I there a way to "remember" a value from a previous iteration? e.g., say
>>> that windDir is N in the n-th data set, I want to use it in the next
>>> iteration, the following minute. Is it possible?
>>>
>>> --
>>> 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.
>>
>>
>>> 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.
>
-- 
-tk

-- 
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] save a value for next iteration

[paolobenve]

No, really what I want is to save a value in order to use it, if I need it, 
in one of the next iteration...

Il giorno lunedì 1 aprile 2019 22:47:36 UTC+2, Thomas Keffer ha scritto:
>
> You would be "making up" data, which is very much against the philosophy 
> of WeeWX. Nevertheless, if you really want to do this, it is possible. 
> Basically, you do a database look up for the previous record. If you are 
> using a 60 second archive period (very short, BTW), it would look something 
> like this (NOT TESTED):
>
> #set $now = $current.dateTime.raw
> #set $then = $now - 60
>
> The temperature now is $current.outTemp; for the previous record it was 
> $current(timestamp=$then).outTemp 
>
> On Mon, Apr 1, 2019 at 1:02 PM > wrote:
>
>> My vantage vue station and weewx are set that they save the meteo values 
>> every minute.
>>
>> I there a way to "remember" a value from a previous iteration? e.g., say 
>> that windDir is N in the n-th data set, I want to use it in the next 
>> iteration, the following minute. Is it possible?
>>
>> -- 
>> 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 .
>> 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] save a value for next iteration

[Thomas Keffer]

You would be "making up" data, which is very much against the philosophy of
WeeWX. Nevertheless, if you really want to do this, it is possible.
Basically, you do a database look up for the previous record. If you are
using a 60 second archive period (very short, BTW), it would look something
like this (NOT TESTED):

#set $now = $current.dateTime.raw
#set $then = $now - 60

The temperature now is $current.outTemp; for the previous record it was
$current(timestamp=$then).outTemp 

On Mon, Apr 1, 2019 at 1:02 PM  wrote:

> My vantage vue station and weewx are set that they save the meteo values
> every minute.
>
> I there a way to "remember" a value from a previous iteration? e.g., say
> that windDir is N in the n-th data set, I want to use it in the next
> iteration, the following minute. Is it possible?
>
> --
> 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] Using wlink driver

[Sofia]

Hi, I have the same problem.
WeeWX upload new data once an hour, but tried to download every 5 minutes 
resulting this error.
Does it depend from the archive interval?? 

-- 
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] windDir.ordinal_compass N/A value when winGust is low

[Thomas Keffer]

>
> $current.windGust.km_per_hour.formatted
> $current.windDir.ordinal_compass
>
> However, when the first is low (< 2), the latter is N/A. I understand the
> logic behind this behaviour, but is there a way to get a numeric value,
> e.g. 0 ?
>
>
In weewx.conf, change this

Ordinates

# Ordinal directions. The last one is for no wind direction

directions = N, NNE, NE, ENE, E, ESE, SE, SSE, S, SSW, SW, WSW, W, WNW,
NW, NNW, N/A

to this
Ordinates


# Ordinal directions. The last one is for no wind direction
directions = N, NNE, NE, ENE, E, ESE, SE, SSE, S, SSW, SW, WSW, W,
WNW, NW, NNW, 0



Alternatively, is there a way to change the second line to something like
>
> if ($current.windGust.km_per_hour.formatted > 2):
>$current.windDir.ordinal_compass
> else:
>   0
>
>
If you don't like option 1, yes, this is possible. It would look something
like (NOT TESTED):

#if $current.windGust.km_per_hour.raw > 2
$current.windDir.orginal_compass
#else
0
#end if

Depending on how your HTML is formatted, you may need a #slurp directive in
there. See the chapter *Language Overview
* in the Cheetah
documentation.

-tk

-- 
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] save a value for next iteration

[paolobenve]

My vantage vue station and weewx are set that they save the meteo values 
every minute.

I there a way to "remember" a value from a previous iteration? e.g., say 
that windDir is N in the n-th data set, I want to use it in the next 
iteration, the following minute. Is it possible?

-- 
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] error in winDir value?

[paolobenve]

A template of mine has

$current.windGust.km_per_hour.formatted
$current.windDir.ordinal_compass

I found that sometimes the values are

2
N/A

Ok, that windDir is N/A when windGust is 0, but why is it N/A with 
windGust=2? is it a bug?

My station is a vantage Vue

-- 
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] windDir.ordinal_compass N/A value when winGust is low

[paolobenve]

I'm using weewx on a raspberrypi, debian.

In the directory /etc/weewx/skins/Standard/ I added a file because I need a 
resumen of meteo data for a meteo network

For the wind I have two lines:

$current.windGust.km_per_hour.formatted
$current.windDir.ordinal_compass

However, when the first is low (< 2), the latter is N/A. I understand the 
logic behind this behaviour, but is there a way to get a numeric value, 
e.g. 0 ?

Alternatively, is there a way to change the second line to something like

if ($current.windGust.km_per_hour.formatted > 2):
   $current.windDir.ordinal_compass
else:
  0

?

-- 
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: Proper way to set time formats for Belchertown skin

[HoracioDos]

Thanks for the tip! It's getting more interesting everytime!

On Monday, April 1, 2019 at 2:56:35 PM UTC-3, Pat wrote:
>
> Also, if you want to force a locale for moment.js, you could edit 
> bin/user/belchertown.py at line 85 
> 
>  
> and set it to system_locale_js = "en-US". Restart weewx and see
>
>
> On Monday, April 1, 2019 at 1:41:05 PM UTC-4, HoracioDos wrote:
>>
>> Hello Pat.
>> I gave me the hint to start with. I started to replace some formats from 
>> "" to "L, LTS" and "LL" to "L" inside index and records templates. I 
>> usualy set system locale to "en_US" and in very few occasions to "es_AR", 
>> because I don't like spanish long date format. Acording to moments.js docs, 
>> there are a lot of options to play with.
>> Thanks!
>>
>> On Monday, April 1, 2019 at 10:07:42 AM UTC-3, Pat wrote:
>>>
>>> Belchertown skin uses moment.js for a "pretty" and consistent time and 
>>> date representation across all locales. Please open an issue on GitHub so I 
>>> can understand what you are looking for and to track this better. 
>>>
>>> On Monday, April 1, 2019 at 8:36:29 AM UTC-4, HoracioDos wrote:

 Hello.
 I can't find a way to set time formats for Belchertown skin without 
 changing system locale. It seems it doesn't honour time formats in 
 weewx.conf or I'm doing it wrong. Seasons skin works fine.

 Current system locale
 LANG=C.UTF-8
 LANGUAGE=
 LC_CTYPE="C.UTF-8"
 LC_NUMERIC=es_AR.UTF-8
 LC_TIME="C.UTF-8"
 LC_COLLATE="C.UTF-8"
 LC_MONETARY=es_AR.UTF-8
 LC_MESSAGES="C.UTF-8"
 LC_PAPER=es_AR.UTF-8
 LC_NAME=es_AR.UTF-8
 LC_ADDRESS=es_AR.UTF-8
 LC_TELEPHONE=es_AR.UTF-8
 LC_MEASUREMENT=es_AR.UTF-8
 LC_IDENTIFICATION=es_AR.UTF-8
 LC_ALL=

 I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside 
 Belchertown skin section and skin.conf too.
 hour   = %H:%M
 day= %H:%M
 week   = %H:%M on %A
 month  = %d/%m/%y %H:%M
 year   = %d/%m/%y %H:%M
 rainyear   = %d/%m/%y %H:%M
 current= %d/%m/%y %H:%M
 ephem_day  = %H:%M
 ephem_year = %d/%m/%y %H:%M

 Thanks!!



-- 
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: Proper way to set time formats for Belchertown skin

[HoracioDos]

I agree with pros and cons. It seems very hard to allow some customization 
from skin.conf. Once user knows where and how to change date time formats, 
it's not too difficult. Perhaps with a little mention in READMEmd this 
issue could be addressed.

On Monday, April 1, 2019 at 2:52:11 PM UTC-3, Pat wrote:
>
> Sounds good and I'm glad you found a way to customize it. 
>
> I had to use moment.js because of the background updates and the various 
> time formats that update with it (header, forecast, earthquake, charts). 
> The pro is that all the dates will look consistent, the con is that it 
> doesn't allow for much user customization. I've thought about moving all of 
> the "", "LLL", and others to some variables to try and make it easier 
> to change from skin.conf or something, but there's so many dates that not 
> all may fall into that standard grouping. It's a small challenge to keep it 
> all looking consistent.
>
> On Monday, April 1, 2019 at 1:41:05 PM UTC-4, HoracioDos wrote:
>>
>> Hello Pat.
>> I gave me the hint to start with. I started to replace some formats from 
>> "" to "L, LTS" and "LL" to "L" inside index and records templates. I 
>> usualy set system locale to "en_US" and in very few occasions to "es_AR", 
>> because I don't like spanish long date format. Acording to moments.js docs, 
>> there are a lot of options to play with.
>> Thanks!
>>
>> On Monday, April 1, 2019 at 10:07:42 AM UTC-3, Pat wrote:
>>>
>>> Belchertown skin uses moment.js for a "pretty" and consistent time and 
>>> date representation across all locales. Please open an issue on GitHub so I 
>>> can understand what you are looking for and to track this better. 
>>>
>>> On Monday, April 1, 2019 at 8:36:29 AM UTC-4, HoracioDos wrote:

 Hello.
 I can't find a way to set time formats for Belchertown skin without 
 changing system locale. It seems it doesn't honour time formats in 
 weewx.conf or I'm doing it wrong. Seasons skin works fine.

 Current system locale
 LANG=C.UTF-8
 LANGUAGE=
 LC_CTYPE="C.UTF-8"
 LC_NUMERIC=es_AR.UTF-8
 LC_TIME="C.UTF-8"
 LC_COLLATE="C.UTF-8"
 LC_MONETARY=es_AR.UTF-8
 LC_MESSAGES="C.UTF-8"
 LC_PAPER=es_AR.UTF-8
 LC_NAME=es_AR.UTF-8
 LC_ADDRESS=es_AR.UTF-8
 LC_TELEPHONE=es_AR.UTF-8
 LC_MEASUREMENT=es_AR.UTF-8
 LC_IDENTIFICATION=es_AR.UTF-8
 LC_ALL=

 I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside 
 Belchertown skin section and skin.conf too.
 hour   = %H:%M
 day= %H:%M
 week   = %H:%M on %A
 month  = %d/%m/%y %H:%M
 year   = %d/%m/%y %H:%M
 rainyear   = %d/%m/%y %H:%M
 current= %d/%m/%y %H:%M
 ephem_day  = %H:%M
 ephem_year = %d/%m/%y %H:%M

 Thanks!!



-- 
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: Proper way to set time formats for Belchertown skin

[Pat]

Also, if you want to force a locale for moment.js, you could edit 
bin/user/belchertown.py at line 85 

 
and set it to system_locale_js = "en-US". Restart weewx and see


On Monday, April 1, 2019 at 1:41:05 PM UTC-4, HoracioDos wrote:
>
> Hello Pat.
> I gave me the hint to start with. I started to replace some formats from 
> "" to "L, LTS" and "LL" to "L" inside index and records templates. I 
> usualy set system locale to "en_US" and in very few occasions to "es_AR", 
> because I don't like spanish long date format. Acording to moments.js docs, 
> there are a lot of options to play with.
> Thanks!
>
> On Monday, April 1, 2019 at 10:07:42 AM UTC-3, Pat wrote:
>>
>> Belchertown skin uses moment.js for a "pretty" and consistent time and 
>> date representation across all locales. Please open an issue on GitHub so I 
>> can understand what you are looking for and to track this better. 
>>
>> On Monday, April 1, 2019 at 8:36:29 AM UTC-4, HoracioDos wrote:
>>>
>>> Hello.
>>> I can't find a way to set time formats for Belchertown skin without 
>>> changing system locale. It seems it doesn't honour time formats in 
>>> weewx.conf or I'm doing it wrong. Seasons skin works fine.
>>>
>>> Current system locale
>>> LANG=C.UTF-8
>>> LANGUAGE=
>>> LC_CTYPE="C.UTF-8"
>>> LC_NUMERIC=es_AR.UTF-8
>>> LC_TIME="C.UTF-8"
>>> LC_COLLATE="C.UTF-8"
>>> LC_MONETARY=es_AR.UTF-8
>>> LC_MESSAGES="C.UTF-8"
>>> LC_PAPER=es_AR.UTF-8
>>> LC_NAME=es_AR.UTF-8
>>> LC_ADDRESS=es_AR.UTF-8
>>> LC_TELEPHONE=es_AR.UTF-8
>>> LC_MEASUREMENT=es_AR.UTF-8
>>> LC_IDENTIFICATION=es_AR.UTF-8
>>> LC_ALL=
>>>
>>> I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside 
>>> Belchertown skin section and skin.conf too.
>>> hour   = %H:%M
>>> day= %H:%M
>>> week   = %H:%M on %A
>>> month  = %d/%m/%y %H:%M
>>> year   = %d/%m/%y %H:%M
>>> rainyear   = %d/%m/%y %H:%M
>>> current= %d/%m/%y %H:%M
>>> ephem_day  = %H:%M
>>> ephem_year = %d/%m/%y %H:%M
>>>
>>> Thanks!!
>>>
>>>

-- 
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: Proper way to set time formats for Belchertown skin

[Pat]

Sounds good and I'm glad you found a way to customize it. 

I had to use moment.js because of the background updates and the various 
time formats that update with it (header, forecast, earthquake, charts). 
The pro is that all the dates will look consistent, the con is that it 
doesn't allow for much user customization. I've thought about moving all of 
the "", "LLL", and others to some variables to try and make it easier 
to change from skin.conf or something, but there's so many dates that not 
all may fall into that standard grouping. It's a small challenge to keep it 
all looking consistent.

On Monday, April 1, 2019 at 1:41:05 PM UTC-4, HoracioDos wrote:
>
> Hello Pat.
> I gave me the hint to start with. I started to replace some formats from 
> "" to "L, LTS" and "LL" to "L" inside index and records templates. I 
> usualy set system locale to "en_US" and in very few occasions to "es_AR", 
> because I don't like spanish long date format. Acording to moments.js docs, 
> there are a lot of options to play with.
> Thanks!
>
> On Monday, April 1, 2019 at 10:07:42 AM UTC-3, Pat wrote:
>>
>> Belchertown skin uses moment.js for a "pretty" and consistent time and 
>> date representation across all locales. Please open an issue on GitHub so I 
>> can understand what you are looking for and to track this better. 
>>
>> On Monday, April 1, 2019 at 8:36:29 AM UTC-4, HoracioDos wrote:
>>>
>>> Hello.
>>> I can't find a way to set time formats for Belchertown skin without 
>>> changing system locale. It seems it doesn't honour time formats in 
>>> weewx.conf or I'm doing it wrong. Seasons skin works fine.
>>>
>>> Current system locale
>>> LANG=C.UTF-8
>>> LANGUAGE=
>>> LC_CTYPE="C.UTF-8"
>>> LC_NUMERIC=es_AR.UTF-8
>>> LC_TIME="C.UTF-8"
>>> LC_COLLATE="C.UTF-8"
>>> LC_MONETARY=es_AR.UTF-8
>>> LC_MESSAGES="C.UTF-8"
>>> LC_PAPER=es_AR.UTF-8
>>> LC_NAME=es_AR.UTF-8
>>> LC_ADDRESS=es_AR.UTF-8
>>> LC_TELEPHONE=es_AR.UTF-8
>>> LC_MEASUREMENT=es_AR.UTF-8
>>> LC_IDENTIFICATION=es_AR.UTF-8
>>> LC_ALL=
>>>
>>> I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside 
>>> Belchertown skin section and skin.conf too.
>>> hour   = %H:%M
>>> day= %H:%M
>>> week   = %H:%M on %A
>>> month  = %d/%m/%y %H:%M
>>> year   = %d/%m/%y %H:%M
>>> rainyear   = %d/%m/%y %H:%M
>>> current= %d/%m/%y %H:%M
>>> ephem_day  = %H:%M
>>> ephem_year = %d/%m/%y %H:%M
>>>
>>> Thanks!!
>>>
>>>

-- 
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: Proper way to set time formats for Belchertown skin

[HoracioDos]

Hello Pat.
I gave me the hint to start with. I started to replace some formats from 
"" to "L, LTS" and "LL" to "L" inside index and records templates. I 
usualy set system locale to "en_US" and in very few occasions to "es_AR", 
because I don't like spanish long date format. Acording to moments.js docs, 
there are a lot of options to play with.
Thanks!

On Monday, April 1, 2019 at 10:07:42 AM UTC-3, Pat wrote:
>
> Belchertown skin uses moment.js for a "pretty" and consistent time and 
> date representation across all locales. Please open an issue on GitHub so I 
> can understand what you are looking for and to track this better. 
>
> On Monday, April 1, 2019 at 8:36:29 AM UTC-4, HoracioDos wrote:
>>
>> Hello.
>> I can't find a way to set time formats for Belchertown skin without 
>> changing system locale. It seems it doesn't honour time formats in 
>> weewx.conf or I'm doing it wrong. Seasons skin works fine.
>>
>> Current system locale
>> LANG=C.UTF-8
>> LANGUAGE=
>> LC_CTYPE="C.UTF-8"
>> LC_NUMERIC=es_AR.UTF-8
>> LC_TIME="C.UTF-8"
>> LC_COLLATE="C.UTF-8"
>> LC_MONETARY=es_AR.UTF-8
>> LC_MESSAGES="C.UTF-8"
>> LC_PAPER=es_AR.UTF-8
>> LC_NAME=es_AR.UTF-8
>> LC_ADDRESS=es_AR.UTF-8
>> LC_TELEPHONE=es_AR.UTF-8
>> LC_MEASUREMENT=es_AR.UTF-8
>> LC_IDENTIFICATION=es_AR.UTF-8
>> LC_ALL=
>>
>> I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside 
>> Belchertown skin section and skin.conf too.
>> hour   = %H:%M
>> day= %H:%M
>> week   = %H:%M on %A
>> month  = %d/%m/%y %H:%M
>> year   = %d/%m/%y %H:%M
>> rainyear   = %d/%m/%y %H:%M
>> current= %d/%m/%y %H:%M
>> ephem_day  = %H:%M
>> ephem_year = %d/%m/%y %H:%M
>>
>> Thanks!!
>>
>>

-- 
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: weewx aqi extension

[parallelsys]

Really people sleep? LOL
Relax, I am just bumping so I my post does not get buried...

On Monday, April 1, 2019 at 9:39:28 AM UTC-5, vince wrote:
>
> On Monday, April 1, 2019 at 2:39:35 AM UTC-7, parallelsys wrote:
>>
>> Anybody? :)
>>
>>
> I know it's shocking, but some of us sleep occasionally, and might not be 
> in your timezone.
>
>
> On Sunday, March 31, 2019 at 5:18:40 PM UTC-5, parallelsys wrote:
>>>
>>> Hello... How can I get the weewx aqi extension to display the ozone 
>>> readings?
>>>
>>> Right now its displaying data from my Purpleair and works fine but I the 
>>> ozone is not working.
>>>
>>>
>>>
>
> I'm not aware that the PA measures ozone.The AQI extension needs a 
> data source.
>
>

-- 
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: No updates since 2am start of British Summer Time

[Geoff Cusick]

As I said, belt-and-braces!

17 Westcroft Road Holsworthy, EX22 6BY
Phone: +44 (0)1409 254330
Mobile: +44 (0)7976 285950
Web: http://www.cusick.org.uk

> On 1 Apr 2019, at 17:56, Jeff A. D.  wrote:
> 
> Personally, I've never had to clear memory after the dump.  Once I've dumped 
> the memory everything seems to sych back up to normal.
> 
>> On Monday, April 1, 2019 at 10:01:18 AM UTC-6, Geoff Cusick wrote:
>> The —clear-memory command does just that - it deletes all the data held in 
>> the logger. That means that any data that has not been collected by weewx 
>> would be lost.  The —dump option downloads everything in the logger to 
>> weewx, which will (should, does, at least with MySQL) reject any records 
>> that have already been downloaded, but retain all new records, thus losing 
>> no data.  The sequence has to be —dump followed by —clear-memory. 
>> 
>> Geoff 
>> 
>> 17 Westcroft Road Holsworthy, EX22 6BY 
>> Phone: +44 (0)1409 254330 
>> Mobile: +44 (0)7976 285950 
>> Web: http://www.cusick.org.uk 
>> 
>> > On 1 Apr 2019, at 16:55, Phil Green  wrote: 
>> > 
>> > Hi 
>> > Why do you need to do a ‘dump’ command when you do the clear-memory? 
>> > 
>> > Yes would be interested in a cron script. 
>> > I presume the same one to be run twice a year when the clocks change 
>> > forwards & backwards? 
>> > Regards 
>> > Phil 
>> > 
>> > -- 
>> > 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/F4w4LutBHLk/unsubscribe. 
>> > To unsubscribe from this group and all its topics, send an email to 
>> > weewx...@googlegroups.com. 
>> > For more options, visit https://groups.google.com/d/optout. 
>> 
> 
> -- 
> 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/F4w4LutBHLk/unsubscribe.
> To unsubscribe from this group and all its topics, 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: No updates since 2am start of British Summer Time

[Jeff A. D.]

Personally, I've never had to clear memory after the dump.  Once I've 
dumped the memory everything seems to sych back up to normal.

On Monday, April 1, 2019 at 10:01:18 AM UTC-6, Geoff Cusick wrote:
>
> The —clear-memory command does just that - it deletes all the data held in 
> the logger. That means that any data that has not been collected by weewx 
> would be lost.  The —dump option downloads everything in the logger to 
> weewx, which will (should, does, at least with MySQL) reject any records 
> that have already been downloaded, but retain all new records, thus losing 
> no data.  The sequence has to be —dump followed by —clear-memory. 
>
> Geoff 
>
> 17 Westcroft Road Holsworthy, EX22 6BY 
> Phone: +44 (0)1409 254330 
> Mobile: +44 (0)7976 285950 
> Web: http://www.cusick.org.uk 
>
> > On 1 Apr 2019, at 16:55, Phil Green > 
> wrote: 
> > 
> > Hi 
> > Why do you need to do a ‘dump’ command when you do the clear-memory? 
> > 
> > Yes would be interested in a cron script. 
> > I presume the same one to be run twice a year when the clocks change 
> forwards & backwards? 
> > Regards 
> > Phil 
> > 
> > -- 
> > 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/F4w4LutBHLk/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> weewx...@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] whew-forecast-3.3.2

[ABZ]

lancet.mit.edu times out when I try to download the most recent version of 
whew-forecast.

Is there another source?

-- 
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: No updates since 2am start of British Summer Time

[Geoff Cusick]

The —clear-memory command does just that - it deletes all the data held in the 
logger. That means that any data that has not been collected by weewx would be 
lost.  The —dump option downloads everything in the logger to weewx, which will 
(should, does, at least with MySQL) reject any records that have already been 
downloaded, but retain all new records, thus losing no data.  The sequence has 
to be —dump followed by —clear-memory.

Geoff

17 Westcroft Road Holsworthy, EX22 6BY
Phone: +44 (0)1409 254330
Mobile: +44 (0)7976 285950
Web: http://www.cusick.org.uk

> On 1 Apr 2019, at 16:55, Phil Green  wrote:
> 
> Hi
> Why do you need to do a ‘dump’ command when you do the clear-memory?
> 
> Yes would be interested in a cron script. 
> I presume the same one to be run twice a year when the clocks change forwards 
> & backwards?
> Regards
> Phil
> 
> -- 
> 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/F4w4LutBHLk/unsubscribe.
> To unsubscribe from this group and all its topics, 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: No updates since 2am start of British Summer Time

[Phil Green]

Hi
Why do you need to do a ‘dump’ command when you do the clear-memory?

Yes would be interested in a cron script. 
I presume the same one to be run twice a year when the clocks change forwards & 
backwards?
Regards
Phil

-- 
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: No updates since 2am start of British Summer Time

[geoff]

The solution that Phil G posted certainly works for me, though I’ve done 
belt-and-braces with:

sudo su # become super-user for now
service weewx stop # stop weewx (same effect as Phil’s /etc/init.d..step
wee_device —dump # (Note the double hyphen) Download all the logger’s stored 
records - may take a while
wee_device —clear-memory # (Again, note the double hyphen) Clear the logger 
memory
service weewx start # Restart weewx
exit # Stop being super-user

I keep meaning to put this into a shell script, and invoke it with cron soon 
after the BST change. 

-- 
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: weewx aqi extension

[vince]

On Monday, April 1, 2019 at 2:39:35 AM UTC-7, parallelsys wrote:
>
> Anybody? :)
>
>
I know it's shocking, but some of us sleep occasionally, and might not be 
in your timezone.


On Sunday, March 31, 2019 at 5:18:40 PM UTC-5, parallelsys wrote:
>>
>> Hello... How can I get the weewx aqi extension to display the ozone 
>> readings?
>>
>> Right now its displaying data from my Purpleair and works fine but I the 
>> ozone is not working.
>>
>>
>>

I'm not aware that the PA measures ozone.The AQI extension needs a data 
source.

-- 
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] Davis wlink download failed attempt..

[Sofia]

Could someone help me? 

-- 
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: Prevent unreal Values for Rain and RainRate on the WS3083

['Johannes Ebner' via weewx-user]

I was reading some threads, where it was statet that this might not work 
for the FineOffsetusb driver.

Am Sonntag, 31. März 2019 13:33:34 UTC+2 schrieb Andrew Milner:
>
> why can't you use qc for rain and/or rainrate??
>
>
>
> On Sunday, 31 March 2019 09:47:55 UTC+3, Johannes Ebner wrote:
>>
>> Hi, 
>>
>> I have now a WS3083 via FineOffsetUSB running on Weewx since January.
>>
>> Last week I got a strange hugh entry for Rain and RainRate. I was now 
>> googeling and noticed that StdQC cannot be easily used for Rain and 
>> RainRate for such stations.
>>
>> How could I prevent this? The value I got was somewhere more then 5.000 
>> mm.
>>
>> Br,
>> Johannes
>>
>

-- 
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: No Moon rise & set on Seasons skin even with pyephem installed

[Ha Ba]

Hello,

Because I also have no moonrise-data displayed, I tried to install pyphem 
and I get this message:

$ sudo pip install pyephem
The directory '/home/haba/.cache/pip/http' or its parent directory is not 
owned by the current user and the cache has been disabled. Please check the 
permissions and owner of that directory. If executing pip with sudo, you 
may want sudo's -H flag.
The directory '/home/haba/.cache/pip' or its parent directory is not owned 
by the current user and caching wheels has been disabled. check the 
permissions and owner of that directory. If executing pip with sudo, you 
may want sudo's -H flag.
Requirement already satisfied: pyephem in 
/usr/local/lib/python2.7/dist-packages

Now I am not sure if everything is ok or if this is an error to fix.

Actually I installed weewx with the setup.py. But there was also an 
installation from the Debian-Packetges on my computer that I removed before 
installing with setup.py.

Kind regards, 
Hans


Am Samstag, 30. März 2019 17:10:31 UTC+1 schrieb Lloyd Brown:
>
> Fixed
> I must have done pip install pyephem without the sudo because the ephem 
> got put in the my home directory.  Did the sudo pip install pyephem and 
> stopped and started WeeWX and I have Moon rise and set.
>
>
>
>>

-- 
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: Proper way to set time formats for Belchertown skin

[Pat]

Belchertown skin uses moment.js for a "pretty" and consistent time and date 
representation across all locales. Please open an issue on GitHub so I can 
understand what you are looking for and to track this better. 

On Monday, April 1, 2019 at 8:36:29 AM UTC-4, HoracioDos wrote:
>
> Hello.
> I can't find a way to set time formats for Belchertown skin without 
> changing system locale. It seems it doesn't honour time formats in 
> weewx.conf or I'm doing it wrong. Seasons skin works fine.
>
> Current system locale
> LANG=C.UTF-8
> LANGUAGE=
> LC_CTYPE="C.UTF-8"
> LC_NUMERIC=es_AR.UTF-8
> LC_TIME="C.UTF-8"
> LC_COLLATE="C.UTF-8"
> LC_MONETARY=es_AR.UTF-8
> LC_MESSAGES="C.UTF-8"
> LC_PAPER=es_AR.UTF-8
> LC_NAME=es_AR.UTF-8
> LC_ADDRESS=es_AR.UTF-8
> LC_TELEPHONE=es_AR.UTF-8
> LC_MEASUREMENT=es_AR.UTF-8
> LC_IDENTIFICATION=es_AR.UTF-8
> LC_ALL=
>
> I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside 
> Belchertown skin section and skin.conf too.
> hour   = %H:%M
> day= %H:%M
> week   = %H:%M on %A
> month  = %d/%m/%y %H:%M
> year   = %d/%m/%y %H:%M
> rainyear   = %d/%m/%y %H:%M
> current= %d/%m/%y %H:%M
> ephem_day  = %H:%M
> ephem_year = %d/%m/%y %H:%M
>
> Thanks!!
>
>

-- 
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] Proper way to set time formats for Belchertown skin

[HoracioDos]

Hello.
I can't find a way to set time formats for Belchertown skin without 
changing system locale. It seems it doesn't honour time formats in 
weewx.conf or I'm doing it wrong. Seasons skin works fine.

Current system locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC=es_AR.UTF-8
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY=es_AR.UTF-8
LC_MESSAGES="C.UTF-8"
LC_PAPER=es_AR.UTF-8
LC_NAME=es_AR.UTF-8
LC_ADDRESS=es_AR.UTF-8
LC_TELEPHONE=es_AR.UTF-8
LC_MEASUREMENT=es_AR.UTF-8
LC_IDENTIFICATION=es_AR.UTF-8
LC_ALL=

I changed weewx.conf in  [[Defaults]] -> [[[Units]]] and inside Belchertown 
skin section and skin.conf too.
hour   = %H:%M
day= %H:%M
week   = %H:%M on %A
month  = %d/%m/%y %H:%M
year   = %d/%m/%y %H:%M
rainyear   = %d/%m/%y %H:%M
current= %d/%m/%y %H:%M
ephem_day  = %H:%M
ephem_year = %d/%m/%y %H:%M

Thanks!!

-- 
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] Is this a PATH-problem?

[Ha Ba]

Hi Thomas,

Wow!!! that works :))

Next time I don't spend hours of time and ask directly an expert ;)

Many thanks,
Hans

BTW: Are you german?

Am Montag, 1. April 2019 13:57:31 UTC+2 schrieb Thomas Keffer:
>
> Most likely you just forgot to install the python usb module.
>
> *sudo apt-get install python-usb*
>
> -tk
>
> On Mon, Apr 1, 2019 at 4:47 AM Ha Ba > 
> wrote:
>
>> HI everybody,
>>
>> When I start weewx, I get this error:
>>
>> l@20:~$ sudo /home/weewx/bin/weewxd /home/weewx/weewx.conf
>>
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/home/weewx/bin/weewx/engine.py", line 884, in main
>> engine = engine_class(config_dict)
>>   File "/home/weewx/bin/weewx/engine.py", line 72, in __init__
>> self.setupStation(config_dict)
>>   File "/home/weewx/bin/weewx/engine.py", line 96, in setupStation
>> __import__(driver)
>>   File "/home/weewx/bin/weewx/drivers/te923.py", line 441, in 
>> import usb
>> ImportError: No module named usb
>>
>> Is it possible, that an installation from eclipse I made yesterday has 
>> changed anything in the PATH-settings?
>>
>> If so, how can I see my actual settings and how can I fix this problem?
>>
>> regards, Hans
>>
>>
>> -- 
>> 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 .
>> 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] Is this a PATH-problem?

[Thomas Keffer]

Most likely you just forgot to install the python usb module.

*sudo apt-get install python-usb*

-tk

On Mon, Apr 1, 2019 at 4:47 AM Ha Ba  wrote:

> HI everybody,
>
> When I start weewx, I get this error:
>
> l@20:~$ sudo /home/weewx/bin/weewxd /home/weewx/weewx.conf
>
> Traceback (most recent call last):
>   File "/home/weewx/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/home/weewx/bin/weewx/engine.py", line 884, in main
> engine = engine_class(config_dict)
>   File "/home/weewx/bin/weewx/engine.py", line 72, in __init__
> self.setupStation(config_dict)
>   File "/home/weewx/bin/weewx/engine.py", line 96, in setupStation
> __import__(driver)
>   File "/home/weewx/bin/weewx/drivers/te923.py", line 441, in 
> import usb
> ImportError: No module named usb
>
> Is it possible, that an installation from eclipse I made yesterday has
> changed anything in the PATH-settings?
>
> If so, how can I see my actual settings and how can I fix this problem?
>
> regards, Hans
>
>
> --
> 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] Is this a PATH-problem?

[Ha Ba]

HI everybody,

When I start weewx, I get this error:

l@20:~$ sudo /home/weewx/bin/weewxd /home/weewx/weewx.conf

Traceback (most recent call last):
  File "/home/weewx/bin/weewxd", line 64, in 
weewx.engine.main(options, args)
  File "/home/weewx/bin/weewx/engine.py", line 884, in main
engine = engine_class(config_dict)
  File "/home/weewx/bin/weewx/engine.py", line 72, in __init__
self.setupStation(config_dict)
  File "/home/weewx/bin/weewx/engine.py", line 96, in setupStation
__import__(driver)
  File "/home/weewx/bin/weewx/drivers/te923.py", line 441, in 
import usb
ImportError: No module named usb

Is it possible, that an installation from eclipse I made yesterday has 
changed anything in the PATH-settings?

If so, how can I see my actual settings and how can I fix this problem?

regards, Hans


-- 
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] wlink download failed attempt..

[Sofia]

Dear all, 

I have a problem downloading data from my Davis Vantage Pro 2 Plus equipped 
by the Weatherlink IP datalogger.

I installed Weewx on a debian server using the python istallation 
procedure. 
Firstly, I configure Weewx to download data directly from my IP datalogger 
but, this blocks the datalogger uploading to weatherlink.com, thus I 
decided to dowload from weatherlink.com by the installation of the wlink 
driver.

Then comes the issue: the on-line report and the mysql database are updated 
once an hour (not a problem), but the log file shows continuously the 
error: "wlink: download failed attempt 1 of 5: HTTP Error 403: Forbidden".
I attached the log file and the configuration file of Weewx. 
What did I do wrong?

Thanks in advance,

Sofia

-- 
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 CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

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

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

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

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

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

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Campus DIEF, Modena"

# Latitude and longitude in decimal degrees
latitude = 44.63
longitude = 10.95

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 40, meter# Choose 'foot' or 'meter' for unit

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

# If you have a website, you may specify an URL
#station_url = http://www.example.com

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

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

##

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

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

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

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

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

# Serial baud rate (usually 19200)
baudrate = 19200

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

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

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

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

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

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

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

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

##

[WeatherLink]

username = 
password = ***
driver = user.wlink



##
#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this 

[weewx-user] Re: Installing WeatherCloud Extension - Error

[Dave McCreath]

Has anyone got a copy of the tarball?

Just asking, you never know.

Dave

On Monday, 1 April 2019 10:29:31 UTC+1, Dave McCreath wrote:
>
> Thanks for getting back to me.  Looks like the link is down so unable to 
> download it!
>
> Regards
>
> Dave
>
> On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>>
>> Hi,
>>
>> You need to replace x.y in the command you are using to install with the 
>> version number in the install file you downloaded. The current version 
>> appears to be 0.11 so try:
>>
>> $ wee_extension --install weewx-wcloud-0.11.tgz
>>
>> Using x.y or x.y.z is a common shorthand used to indicate you need to 
>> replace the letters with the version you are using. Saves a bit of work 
>> continually updating (and may be getting them out of date) instructions.
>>
>> 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: weewx aqi extension

[parallelsys]

Anybody? :)

On Sunday, March 31, 2019 at 5:18:40 PM UTC-5, parallelsys wrote:
>
> Hello... How can I get the weewx aqi extension to display the ozone 
> readings?
>
> Right now its displaying data from my Purpleair and works fine but I the 
> ozone is not working.
>
> Thanks again!
>

-- 
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: Installing WeatherCloud Extension - Error

[Dave McCreath]

Thanks for getting back to me.  Looks like the link is down so unable to 
download it!

Regards

Dave

On Monday, 1 April 2019 09:50:00 UTC+1, gjr80 wrote:
>
> Hi,
>
> You need to replace x.y in the command you are using to install with the 
> version number in the install file you downloaded. The current version 
> appears to be 0.11 so try:
>
> $ wee_extension --install weewx-wcloud-0.11.tgz
>
> Using x.y or x.y.z is a common shorthand used to indicate you need to 
> replace the letters with the version you are using. Saves a bit of work 
> continually updating (and may be getting them out of date) instructions.
>
> 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: Prevent unreal Values for Rain and RainRate on the WS3083

[Greg from Oz]

Hi,
I got some strange rain readings as well. I put this in my weewx.conf.
[StdQC]

[[MinMax]]
barometer = 26, 32.5, inHg
outTemp = -40, 60, degree_C
inTemp = -10, 80, degree_C
outHumidity = 0, 100
inHumidity = 0, 100
windSpeed = 0, 100, km_per_hour
pressure = 24, 34.5, inHg
rainRate = 0, 150, mm_per_hour
rain = 0, 2.9, mm
I sometimes get a strange reading but not as often as I used to.

On Sunday, 31 March 2019 17:47:55 UTC+11, Johannes Ebner wrote:
>
> Hi, 
>
> I have now a WS3083 via FineOffsetUSB running on Weewx since January.
>
> Last week I got a strange hugh entry for Rain and RainRate. I was now 
> googeling and noticed that StdQC cannot be easily used for Rain and 
> RainRate for such stations.
>
> How could I prevent this? The value I got was somewhere more then 5.000 mm.
>
> Br,
> Johannes
>

-- 
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] Installing WeatherCloud Extension - Error

[gjr80]

Hi,

You need to replace x.y in the command you are using to install with the 
version number in the install file you downloaded. The current version appears 
to be 0.11 so try:

$ wee_extension --install weewx-wcloud-0.11.tgz

Using x.y or x.y.z is a common shorthand used to indicate you need to replace 
the letters with the version you are using. Saves a bit of work continually 
updating (and may be getting them out of date) instructions.

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] Installing WeatherCloud Extension - Error

[Dave McCreath]

Getting a tad fed up with Wunderground and trying to move over to 
WeatherCloud.

I have weeWX installed and running and updated on a Raspberry Pi currently 
uploading to Wunderground, no issues.

I followed the instructions on the WeatherCloud site to install alongside 
weeWX (here ) but after trying to 
install the file on my RPi I get the following error:

pi@weewx:~ $ wee_extension --install weewx-wcloud-x.y.tgz
Request to install 'weewx-wcloud-x.y.tgz'
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 124, in 
install_extension
raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension 'weewx-wcloud-x.y.tgz' not found.

Anyone got an idea of how to overcome the installation error, I am no 
expert on 'things' LINUX?

Dave

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