[weewx-user] How to use the .years iterator

[gjr80]

Hi,

With an out of the box weeWX install there is no ability to iterate over all of 
the years of data in your archive (well you should be able to do something with 
$span but that would be limited to the last x years rather than all data). 
However, if you install the xstats example included with weeWX, you then have 
access to the tag $alltime which gives you access to stats on all your data. 
You should then be able to do something like (untested):

#for $year in $alltime.years
$year.outTemp.max
#end for

The examples directory should have been included when weeWX was installed, you 
might find it in /home/weewx for a setup.py install. Alternatively you can find 
it on github (https://github.com/weewx/weewx/tree/master/examples/xstats). I 
suggest you install xstats manually rather than using wee_extension as all you 
need is the xstats.py file not the whole skin that the extension installer 
would install. The readme included with xstats has instructions for 
installation and use.

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] Weewx-aprs

[Liz]

I'm running this code https://github.com/cavedon/weewx-aprs
and it is putting some output in /dev/shm/aprx.pkt

The output isn't what is actually needed
I'm getting
/050455z3415.98S/14606.85E_203/...g019t028r000h26b342985

when a suitable output would be
@050455z3415.98S/14606.85E_214/006g012t082r000p000P000b10130h26L720.weewx-3.8.0-Vantage

Has anyone got this working properly?

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] How to use the .years iterator

[Louis De Lange]

In a template  am trying to create a table showing the average temperature 
for the month to date and then a historical list of the avg temp for all 
months in the datebase.

I tried doing this with the iterators and I note the following example in 
the customization guide

#for $month in $year.months
$month.dateTime.format("%B"): Min, max temperatures: $month.outTemp.min 
$month.outTemp.max#end for


This intuitively makes sense, but lets say I want to iterate this same 
iteration loop over all the years in the database.  I can quite figure out 
how to use the .years iteration loop

#for $year in .years

What would replace the 

-- 
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] New VP2 setup, rain cups and calibration

[tomnykds]

The light isn't on, so that's not it.  I am seeing the same numbers between 
the console and weewx now, which is nice.  Offsetting the temp
didn't change the humidity delta, but it sounds like I need to get ahold of 
Davis next.
Thx, Chris

On Sunday, March 4, 2018 at 4:25:38 PM UTC-8, Dave Webb wrote:
>
> Chris,
>
>  Is the inside temp higher than the outside temp? If it is, is the console 
> light on? I found a 2-3 degree difference with console light on because it 
> generates heat inside the console. 
>
>
>
> Dave-KB1PVH
>
>
> Sent from my Galaxy S7
>
> On Mar 4, 2018 6:03 PM,  wrote:
>
>> I sprung for Vantage Pro 2 with aspiration.  I have it hooked up to an 
>> RPi with the serial logger.  That part seems to work OK so far.
>> My question is about which wind cups (large or small) is included in the 
>> standard kit these days?  The Davis site is woefully lacking
>> in detail, and even the specs in the books are missing that one.  The 
>> other question is about calibration.  I have the console and ISS
>> sitting in the same place, and the temp and humidity don't match (off a 
>> couple of degrees and few percent).  I found where to offset
>> the values in the console, but not sure if either are correct.  Is this a 
>> matter of averaging the values of a bunch of thermometers
>> and adjusting?  I found two more temp/hum units, and I've adjusted the 
>> console as needed, but does setting calibration change
>> the values that the data-logger sees?  It doesn't seem like it, meaning I 
>> need to duplicate the offsets in the weewx.conf.
>>
>> Thx, 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+...@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] New VP2 setup, rain cups and calibration

[Dave Webb KB1PVH]

Chris,

 Is the inside temp higher than the outside temp? If it is, is the console
light on? I found a 2-3 degree difference with console light on because it
generates heat inside the console.



Dave-KB1PVH


Sent from my Galaxy S7

On Mar 4, 2018 6:03 PM,  wrote:

> I sprung for Vantage Pro 2 with aspiration.  I have it hooked up to an RPi
> with the serial logger.  That part seems to work OK so far.
> My question is about which wind cups (large or small) is included in the
> standard kit these days?  The Davis site is woefully lacking
> in detail, and even the specs in the books are missing that one.  The
> other question is about calibration.  I have the console and ISS
> sitting in the same place, and the temp and humidity don't match (off a
> couple of degrees and few percent).  I found where to offset
> the values in the console, but not sure if either are correct.  Is this a
> matter of averaging the values of a bunch of thermometers
> and adjusting?  I found two more temp/hum units, and I've adjusted the
> console as needed, but does setting calibration change
> the values that the data-logger sees?  It doesn't seem like it, meaning I
> need to duplicate the offsets in the weewx.conf.
>
> Thx, 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.
>

-- 
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] New VP2 setup, rain cups and calibration

[Thomas Keffer]

These are really questions for Davis tech support (which is actually quite
good).

Generally, the console and wind cups are matched, so you should not have to
do anything, but I would ask Davis how to tell them apart.

Davis does a good job of calibrating their temperature sensors, so I'm
surprised you would find such a big discrepancy. Again, ask Davis.

Changing the offset within the console should affect what the logger sees,
so you should not need to add a calibration to weewx.conf.

-tk

On Sun, Mar 4, 2018 at 3:03 PM,  wrote:

> I sprung for Vantage Pro 2 with aspiration.  I have it hooked up to an RPi
> with the serial logger.  That part seems to work OK so far.
> My question is about which wind cups (large or small) is included in the
> standard kit these days?  The Davis site is woefully lacking
> in detail, and even the specs in the books are missing that one.  The
> other question is about calibration.  I have the console and ISS
> sitting in the same place, and the temp and humidity don't match (off a
> couple of degrees and few percent).  I found where to offset
> the values in the console, but not sure if either are correct.  Is this a
> matter of averaging the values of a bunch of thermometers
> and adjusting?  I found two more temp/hum units, and I've adjusted the
> console as needed, but does setting calibration change
> the values that the data-logger sees?  It doesn't seem like it, meaning I
> need to duplicate the offsets in the weewx.conf.
>
> Thx, 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.
>

-- 
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] New VP2 setup, rain cups and calibration

[tomnykds]

I sprung for Vantage Pro 2 with aspiration.  I have it hooked up to an RPi 
with the serial logger.  That part seems to work OK so far.
My question is about which wind cups (large or small) is included in the 
standard kit these days?  The Davis site is woefully lacking
in detail, and even the specs in the books are missing that one.  The other 
question is about calibration.  I have the console and ISS
sitting in the same place, and the temp and humidity don't match (off a 
couple of degrees and few percent).  I found where to offset
the values in the console, but not sure if either are correct.  Is this a 
matter of averaging the values of a bunch of thermometers
and adjusting?  I found two more temp/hum units, and I've adjusted the 
console as needed, but does setting calibration change
the values that the data-logger sees?  It doesn't seem like it, meaning I 
need to duplicate the offsets in the weewx.conf.

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

Re: [weewx-user] Re: Adding archive data to daily report

[Chris Alemany]

Hi Thomas! 

This is a great addition, love how you presented it on your website too.

Do you have the extensions you made available to download anywhere?

Thanks!
Chris

On Sunday, February 5, 2017 at 10:58:11 AM UTC-8, Thomas Carlin wrote:
>
> That did the trick.  Thanks again 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] Storm rain

[Chris Alemany]

Hi Tom,

Following up on this, are we still required to add another slot in the 
database for the stormRain value? When I try $current.stormRain or 
$last.stormRain I don't get anything.

Is there a way to just spit out everything in the $current.?? or $last.?? 
domain?

Cheers,
Chris

On Sunday, May 21, 2017 at 1:43:21 PM UTC-7, Tom Keffer wrote:
>
> The Vantage protocol reports storm rain in the LOOP packets. If you are 
> running V3.7 (or later), these will be used to augment the archive records, 
> so values should already be in there. Look for observation type stormRain. 
> All you have to do is add a slot in the database for the value. The 
> Customizing 
> Guide  tells you 
> how to do this.
>
> However, looking through the code, I see one subtle problem: the code uses 
> the *average* value of stormRain over the archive interval, when what you 
> want is the *last* value. So, you would need to add the following to 
> weewx.conf (NOT TESTED):
>
> [Accumulator]
>   [[stormRain]]
> extractor = last
>
> We'll fix this bug in the next release.
>
> Hope this helps.
>
> -tk
>
> On Sun, May 21, 2017 at 1:29 PM, Den S  
> wrote:
>
>> Davis Weatherlink reported 'Rain Storm':
>>
>> "Rain Storm displays the rain total of the last rain event. It takes two 
>> tips of the rain bucket to begin a storm event and 24 hours without rain to 
>> end a storm event."
>>
>> I miss this output now that I am using WeeWX. Any way it can be reported 
>> or calculated with WeeWx? Before I look into doing the calculation, if it 
>> already exists, why reinvent the wheel?
>>
>> Great stuff, really like my new WeeWX weather display...
>>
>> Thanks
>> Den
>>
>> -- 
>> 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: producing values with no units

[Chris Alemany]

haha!  

Where I come from trolling and trawling are still both fishing! (I worked 
on my dad's salmon *troller* for quite a few years... trawling is the big 
bad dudes who drag a net through the water. Yuk).

RAW! Thank you! I scrolled through that page a thousand times and didn't 
see it.

thanks again for the quick reply!
Chris

On Sunday, March 4, 2018 at 1:18:57 PM UTC-8, gjr80 wrote:
>
> Hi,
>
> Ah, there is your problem, you were trolling, probably should have been 
> trawling :)
>
> Try $current.outTemp.formatted (or .nolabel if you want to specify your 
> own format directly). Refer to 
> http://weewx.com/docs/customizing.htm#formatting_options.
>
> Note these will return strings, if you want a numeric then .raw is your 
> friend.
>
> 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] producing values with no units

[gjr80]

Hi,

Ah, there is your problem, you were trolling, probably should have been 
trawling :)

Try $current.outTemp.formatted (or .nolabel if you want to specify your own 
format directly). Refer to 
http://weewx.com/docs/customizing.htm#formatting_options.

Note these will return strings, if you want a numeric then .raw is your friend.

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] producing values with no units

[Chris Alemany]

This seems like a simple question but I've been trolling through the docs 
for what seems like weeks and haven't been able to figure it out.  I just 
want to have a simple way to use a tag like $current.outTemp; and have it 
produce just the raw value without the unit.  So, 4.2 not 4.2ºC.

Help! :)

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: Maplins N23DQ Weather Station

['Season Ticket' via weewx-user]

yes I think fine offset is the closest match and so I've configured by 
weewx to use fine offset observer configuration.  But for some reason when 
I change the console configuration to point to my weewx installation rather 
than www.wunderground.com   I don't see any traffic arriving.
So I setup a webserver (apache httpd) listening on port 80 on my laptop.  I 
then changed the console config to point to my apache server,  and ran 
wireshark to trace the traffic.   

I don't see any traffic at all.

I can run a http client on my phone and connect to the webserver ok,  and 
wireshark shows that traffic.

Any ideas on why the weatherstation doesn't seen to even connect to the 
webserver?

On Sunday, 4 March 2018 18:03:37 UTC, mwall wrote:
>
> On Sunday, March 4, 2018 at 11:47:42 AM UTC-5, Season Ticket wrote:
>>
>> I have a N23DQ but I'm unable to capture a wireshark trace from it or 
>> redirect to my weewx installation. Has anyone else had success using this 
>> weatherstation with weewx?
>>
>>>
>>>
> i think the N23DQ is a fine offset HP1000
>
> this weewx wiki page might help:
>
> https://github.com/weewx/weewx/wiki/observer
>
> m 
>

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

[weewx-user] Re: Maplins N23DQ Weather Station

[mwall]

On Sunday, March 4, 2018 at 11:47:42 AM UTC-5, Season Ticket wrote:
>
> I have a N23DQ but I'm unable to capture a wireshark trace from it or 
> redirect to my weewx installation. Has anyone else had success using this 
> weatherstation with weewx?
>
>>
>>
i think the N23DQ is a fine offset HP1000

this weewx wiki page might help:

https://github.com/weewx/weewx/wiki/observer

m 

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

[weewx-user] Re: Testing changes to index.html.tmpl

[WindnFog]

Thanks, Andrew.  That's exactly what I was looking for.

- Paul VE1DX

On Friday, March 2, 2018 at 10:48:20 AM UTC-4, WindnFog wrote:
>
> Is there an easy way to force weewx to generate a new index.html and put 
> it somewhere on your system where it can be read by a browser?  My current 
> development cycle consists of changing index.html.tmpl and waiting 5 
> minutes for weewx to upload it to my web site.  Surely there must be a 
> faster way to see what a 1-2 character change does.  I'm not running apache 
> or hosting it on my own computer . . . I have a remote web hosting site 
> that weewx rcync's to every 5 minutes.
>
> - Paul VE1DX
>

-- 
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: $station.uptime

[Andrew Milner]

We  have a few paracetomols to help you 
out!!!

Go on – a few deep breaths and a fresh sd card and a new install ...

As long as you are on a fresh sd card you should be ok as you rebuild.
But yes, a list of the addons is a prerequisite and a good excuse for a few 
beers as you exercise the memory cells 



Sent from Mail for Windows 10

From: Robin
Sent: 04 March 2018 18:00
To: weewx-user
Subject: [weewx-user] Re: $station.uptime

Andrew,

I'm going to sit in the 'stupid' corner for a while!

A fresh install is going to take courage. I have a lot of bits and bobs that I 
have added in, some of which I can only just remember! My knowledge and skill 
level give me major worries that I won't get everything back together again.

I think I need to start with building a list of my added 'stuff' and then 
making a plan to get it all back into a new install.

I already have a headache.

Robin
-- 
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/oNaUk2ENIzc/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: $station.uptime

[Robin]

Andrew,

I'm going to sit in the 'stupid' corner for a while!

A fresh install is going to take courage. I have a lot of bits and bobs 
that I have added in, some of which I can only just remember! My knowledge 
and skill level give me major worries that I won't get everything back 
together again.

I think I need to start with building a list of my added 'stuff' and then 
making a plan to get it all back into a new install.

I already have a headache.

Robin

-- 
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: $station.uptime

[Andrew Milner]

Robin
Unless you have a good reason I would recommend a fresh install of stretch 
since you are already deep in the proverbial anyway

The only rpi I have still on wheezy is one no longer in live production use 
- all my others (for weewx, touch display and soil moisture sensors) are 
now on Jessie and one is on stretch for my sprinkler watering!!  

But yes, you sound as bad as me for following good advice!!

Andrew
PS - OK - I'll stop looking around, but I suspect the likely cause is a 
wheezy/weewx mismatch rather than weewx itself

On Sunday, 4 March 2018 16:59:45 UTC+2, Robin wrote:

> Andrew,
>
> Correct, I am running Wheezy.
>
> Please stop trying to solve this (for now).
>
> I decided to update to 3.8 and all hell has broken loose. Typically I 
> ignored all the good advice to backup the SD card. Now pulling my hair out 
> (not much left to work with).
>
> Gone back to old conf file and made a couple of hacks to get it running.
>
> Robin
>
> 3.6.1 was working fine - *if 
>  it 
>  ain’t 
>  broke 
> , don’t 
>  fix 
>  it 
> *
>
>
> *sigh*
> On Sunday, 4 March 2018 15:43:19 UTC+2, Andrew Milner wrote:
>>
>> getting closer .
>>
>> Having checked 5 different RPis . Jessie and Stretch respond like I 
>> posted originally
>>
>> Wheezy responds like yours, and does not appear to accept the -p option
>>
>> whether there is any significance in this I do not know!!!  It could be 
>> that the proc info is different in wheezy
>>
>>  
>>
>>
>>
>> On Sunday, 4 March 2018 15:27:56 UTC+2, Andrew Milner wrote:
>>
>>> then i'm well baffled as so am i - running raspbian, yet my uptime -p 
>>> command gave a very different result to yours!!  I also use the bootstrap 
>>> skin
>>>
>>> the answer must lie in your skin/weewx.conf or the log .
>>>
>>> have you tried gary's suggestion yet??
>>>
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 14:48:16 UTC+2, Robin wrote:
>>>
 I'm running a Raspberry Pi.


 On Sunday, 4 March 2018 11:12:43 UTC+2, Andrew Milner wrote:
>
> are you on a MAC by any chance??  seems like weewx has implemented 
> pretty much the method outlined here for os uptime:
>
> http://planzero.org/blog/2012/01/26/system_uptime_in_python,_a_better_way
>
>
>
> On Sunday, 4 March 2018 11:07:39 UTC+2, Andrew Milner wrote:
>
>> the format must vary with the operating system then as mine says
>> up 1 week, 3 hours, 51 minutes!!
>>
>> not too sure why your uptime should give be giving any info about 
>> users or load averages though!!
>>
>>
>>
>> On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote:
>>
>>> up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21
>>>
>>> On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:

 if you do uptime -p what result do you get??



 On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:

> and the log??
>
>
>
> On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:
>
>> OK the page is now updating (not the images, I'm only interested 
>> in the uptime).
>>
>> http://www.weather.molyvos.eu/Bootstrap/
>>
>> It still shows
>>
>> Station uptime: 0 days, 0 Hours, 0 minutes
>> Server uptime: 0 days, 0 Hours, 6 minutes
>>
>>
>>
>> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:
>>>
>>> Andrew, 
>>>
>>> my bad, just noticed that myself and was about to post. I will 
>>> get /bootstrap/index running again and see what happens
>>>
>>> Robin
>>>
>>> On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:

 the bootstrap skin has totally the wrong date and time of lasdt 
 update though!  It is saying November 2015



 On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:

> Hi Gary,
>
> I don't think it is the template or skin config as I also have 
> a Bootstrap skin running.
>
> http://www.weather.molyvos.eu/Bootstrap/index.html
>
> Since I did a Weewx stop/start it now shows 
>
> Weewx uptime: 0 days, 0 hours, 0 minutes
> Server uptime: 0 days, 0 hours, 6 minutes
>
>
>  
>
>
> On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:
>>

[weewx-user] Re: $station.uptime

[Robin]

Andrew,

Correct, I am running Wheezy.

Please stop trying to solve this (for now).

I decided to update to 3.8 and all hell has broken loose. Typically I 
ignored all the good advice to backup the SD card. Now pulling my hair out 
(not much left to work with).

Gone back to old conf file and made a couple of hacks to get it running.

Robin

3.6.1 was working fine - *if  it 
 ain’t 
 broke 
, don’t 
 fix 
 it 
*


*sigh*
On Sunday, 4 March 2018 15:43:19 UTC+2, Andrew Milner wrote:
>
> getting closer .
>
> Having checked 5 different RPis . Jessie and Stretch respond like I 
> posted originally
>
> Wheezy responds like yours, and does not appear to accept the -p option
>
> whether there is any significance in this I do not know!!!  It could be 
> that the proc info is different in wheezy
>
>  
>
>
>
> On Sunday, 4 March 2018 15:27:56 UTC+2, Andrew Milner wrote:
>
>> then i'm well baffled as so am i - running raspbian, yet my uptime -p 
>> command gave a very different result to yours!!  I also use the bootstrap 
>> skin
>>
>> the answer must lie in your skin/weewx.conf or the log .
>>
>> have you tried gary's suggestion yet??
>>
>>
>>
>>
>> On Sunday, 4 March 2018 14:48:16 UTC+2, Robin wrote:
>>
>>> I'm running a Raspberry Pi.
>>>
>>>
>>> On Sunday, 4 March 2018 11:12:43 UTC+2, Andrew Milner wrote:

 are you on a MAC by any chance??  seems like weewx has implemented 
 pretty much the method outlined here for os uptime:

 http://planzero.org/blog/2012/01/26/system_uptime_in_python,_a_better_way



 On Sunday, 4 March 2018 11:07:39 UTC+2, Andrew Milner wrote:

> the format must vary with the operating system then as mine says
> up 1 week, 3 hours, 51 minutes!!
>
> not too sure why your uptime should give be giving any info about 
> users or load averages though!!
>
>
>
> On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote:
>
>> up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21
>>
>> On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:
>>>
>>> if you do uptime -p what result do you get??
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:
>>>
 and the log??



 On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:

> OK the page is now updating (not the images, I'm only interested 
> in the uptime).
>
> http://www.weather.molyvos.eu/Bootstrap/
>
> It still shows
>
> Station uptime: 0 days, 0 Hours, 0 minutes
> Server uptime: 0 days, 0 Hours, 6 minutes
>
>
>
> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:
>>
>> Andrew, 
>>
>> my bad, just noticed that myself and was about to post. I will 
>> get /bootstrap/index running again and see what happens
>>
>> Robin
>>
>> On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:
>>>
>>> the bootstrap skin has totally the wrong date and time of lasdt 
>>> update though!  It is saying November 2015
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:
>>>
 Hi Gary,

 I don't think it is the template or skin config as I also have 
 a Bootstrap skin running.

 http://www.weather.molyvos.eu/Bootstrap/index.html

 Since I did a Weewx stop/start it now shows 

 Weewx uptime: 0 days, 0 hours, 0 minutes
 Server uptime: 0 days, 0 hours, 6 minutes


  


 On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:
>
> $station.uptime by itself should format just fine, though it 
> will/may depend on the contents of skin.conf. In your case it 
> appears to be 
> formatting as it should. Given we are talking about a custom page 
> (ie not 
> one included in a default weeWX install) it would be worth 
> posting the 
> template file (.tmpl) and skin config file being used.
>
> 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 

[weewx-user] Re: $station.uptime

[Andrew Milner]

then i'm well baffled as so am i - running raspbian, yet my uptime -p 
command gave a very different result to yours!!  I also use the bootstrap 
skin

the answer must lie in your skin/weewx.conf or the log .

have you tried gary's suggestion yet??




On Sunday, 4 March 2018 14:48:16 UTC+2, Robin wrote:

> I'm running a Raspberry Pi.
>
>
> On Sunday, 4 March 2018 11:12:43 UTC+2, Andrew Milner wrote:
>>
>> are you on a MAC by any chance??  seems like weewx has implemented pretty 
>> much the method outlined here for os uptime:
>> http://planzero.org/blog/2012/01/26/system_uptime_in_python,_a_better_way
>>
>>
>>
>> On Sunday, 4 March 2018 11:07:39 UTC+2, Andrew Milner wrote:
>>
>>> the format must vary with the operating system then as mine says
>>> up 1 week, 3 hours, 51 minutes!!
>>>
>>> not too sure why your uptime should give be giving any info about users 
>>> or load averages though!!
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote:
>>>
 up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21

 On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:
>
> if you do uptime -p what result do you get??
>
>
>
> On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:
>
>> and the log??
>>
>>
>>
>> On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:
>>
>>> OK the page is now updating (not the images, I'm only interested in 
>>> the uptime).
>>>
>>> http://www.weather.molyvos.eu/Bootstrap/
>>>
>>> It still shows
>>>
>>> Station uptime: 0 days, 0 Hours, 0 minutes
>>> Server uptime: 0 days, 0 Hours, 6 minutes
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:

 Andrew, 

 my bad, just noticed that myself and was about to post. I will get 
 /bootstrap/index running again and see what happens

 Robin

 On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:
>
> the bootstrap skin has totally the wrong date and time of lasdt 
> update though!  It is saying November 2015
>
>
>
> On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:
>
>> Hi Gary,
>>
>> I don't think it is the template or skin config as I also have a 
>> Bootstrap skin running.
>>
>> http://www.weather.molyvos.eu/Bootstrap/index.html
>>
>> Since I did a Weewx stop/start it now shows 
>>
>> Weewx uptime: 0 days, 0 hours, 0 minutes
>> Server uptime: 0 days, 0 hours, 6 minutes
>>
>>
>>  
>>
>>
>> On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:
>>>
>>> $station.uptime by itself should format just fine, though it 
>>> will/may depend on the contents of skin.conf. In your case it 
>>> appears to be 
>>> formatting as it should. Given we are talking about a custom page 
>>> (ie not 
>>> one included in a default weeWX install) it would be worth posting 
>>> the 
>>> template file (.tmpl) and skin config file being used.
>>>
>>> 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: WMR300 - Ubuntu Weather Undergroud wind direction

[mwall]

On Sunday, March 4, 2018 at 5:08:18 AM UTC-5, Sam Walton wrote:
>
> Hi Guys
>
> I've noticed that WU is not displaying wind direction. It seems to be 
> displaying on the weewx local site but not WU. I did not have this problem 
> running Weewx on Raspbian before and I'm guessing its a driver issue.  I've 
> run: sudo wget 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py
>  
> and downloaded the latest driver.
>
> Attached is some debug logs and I've noticed that rapid fire isn't sending 
> the direction logs all the time.
>

sam,

that log output smells funny.  could you verify that you've got the 
correct, unedited output?

m


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

[weewx-user] Re: $station.uptime

[Robin]

I'm running a Raspberry Pi.


On Sunday, 4 March 2018 11:12:43 UTC+2, Andrew Milner wrote:
>
> are you on a MAC by any chance??  seems like weewx has implemented pretty 
> much the method outlined here for os uptime:
> http://planzero.org/blog/2012/01/26/system_uptime_in_python,_a_better_way
>
>
>
> On Sunday, 4 March 2018 11:07:39 UTC+2, Andrew Milner wrote:
>
>> the format must vary with the operating system then as mine says
>> up 1 week, 3 hours, 51 minutes!!
>>
>> not too sure why your uptime should give be giving any info about users 
>> or load averages though!!
>>
>>
>>
>> On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote:
>>
>>> up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21
>>>
>>> On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:

 if you do uptime -p what result do you get??



 On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:

> and the log??
>
>
>
> On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:
>
>> OK the page is now updating (not the images, I'm only interested in 
>> the uptime).
>>
>> http://www.weather.molyvos.eu/Bootstrap/
>>
>> It still shows
>>
>> Station uptime: 0 days, 0 Hours, 0 minutes
>> Server uptime: 0 days, 0 Hours, 6 minutes
>>
>>
>>
>> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:
>>>
>>> Andrew, 
>>>
>>> my bad, just noticed that myself and was about to post. I will get 
>>> /bootstrap/index running again and see what happens
>>>
>>> Robin
>>>
>>> On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:

 the bootstrap skin has totally the wrong date and time of lasdt 
 update though!  It is saying November 2015



 On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:

> Hi Gary,
>
> I don't think it is the template or skin config as I also have a 
> Bootstrap skin running.
>
> http://www.weather.molyvos.eu/Bootstrap/index.html
>
> Since I did a Weewx stop/start it now shows 
>
> Weewx uptime: 0 days, 0 hours, 0 minutes
> Server uptime: 0 days, 0 hours, 6 minutes
>
>
>  
>
>
> On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:
>>
>> $station.uptime by itself should format just fine, though it 
>> will/may depend on the contents of skin.conf. In your case it 
>> appears to be 
>> formatting as it should. Given we are talking about a custom page 
>> (ie not 
>> one included in a default weeWX install) it would be worth posting 
>> the 
>> template file (.tmpl) and skin config file being used.
>>
>> 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] WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

Hi Guys

I've noticed that WU is not displaying wind direction. It seems to be 
displaying on the weewx local site but not WU. I did not have this problem 
running Weewx on Raspbian before and I'm guessing its a driver issue.  I've 
run: sudo wget 
https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py
 
and downloaded the latest driver.

Attached is some debug logs and I've noticed that rapid fire isn't sending 
the direction logs all the time.

PI: Ubuntu 16.04.4 LTS (GNU/Linux 4.4.38-v7+ armv7l)
The Weatherstation is: Oregon Scientific WMR300
WU Link: 
https://www.wunderground.com/personal-weather-station/dashboard?ID=INEWSOUT1234 

Thanks again

Sam

-- 
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.
Feb 26 22:08:03 weather-station systemd
Feb 26 22:31:13 weather-station systemd[1]: Starting LSB: weewx weather 
system...
Feb 26 22:31:13 weather-station weewx[2196]:  * Starting weewx weather system 
weewx
Feb 26 22:31:13 weather-station weewx[2208]: engine: Initializing weewx version 
3.8.0
Feb 26 22:31:13 weather-station weewx[2208]: engine: Using Python 2.7.12 
(default, Dec  4 2017, 14:50:18) #012[GCC 5.4.0 20160609]
Feb 26 22:31:13 weather-station weewx[2208]: engine: Platform 
Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
Feb 26 22:31:13 weather-station weewx[2208]: engine: Locale is 'en_AU.UTF-8'
Feb 26 22:31:13 weather-station weewx[2208]: engine: pid file is 
/var/run/weewx.pid
Feb 26 22:31:13 weather-station weewx[2212]: engine: Using configuration file 
/etc/weewx/weewx.conf
Feb 26 22:31:13 weather-station weewx[2212]: engine: debug is 2
Feb 26 22:31:13 weather-station weewx[2212]: engine: Initializing engine
Feb 26 22:31:13 weather-station weewx[2212]: engine: Loading station type 
WMR300 (weewx.drivers.wmr300rc3)
Feb 26 22:31:13 weather-station weewx[2196]:...done.
Feb 26 22:31:13 weather-station systemd[1]: Started LSB: weewx weather system.
Feb 26 22:31:13 weather-station weewx[2212]: wmr300: driver version is 0.19rc3
Feb 26 22:31:13 weather-station weewx[2212]: wmr300: usb info: 
pyusb_version=1.0.0b2
Feb 26 22:31:13 weather-station weewx[2212]: wmr300: sensor map is 
{'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 'hea', 
'inTemp': 'temperature_0', 'windGustDir': 'wind_gust_dir', 'extraDewpoint2': 
'dewpoint_3', 'extraDewpoint3': 'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 
'barometer': 'barometer', 'extraDewpoint7': 'dewpoint_8', _1', 
'extraDewpoint5': 'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 
'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 
'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumixtraTemp6': 
'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 'temperature_5', 
'extraTemp5': 'temperature_6', 'extraTemp2': 'temperature_3', 'extraTemp3': 
'temperature_4', 'extraTemp1': 'temperature_2', 'atindex_4', 'extraHeatindex2': 
'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
'heatindex_6', 'extraHumid7': 'humidity_8', 'extrdex_5', 'windDir': 'wind_dir', 
'outTemp': 'temperature_1', 'windSpeed': 'wind_avg', 'inHumidity': 
'humidity_0', 'windGust': 'wind_gust'}
Feb 26 22:31:13 weather-station weewx[2212]: wmr300: history limit is 20%
Feb 26 22:31:13 weather-station weewx[2212]: wmr300: Found station at bus= 
device=
Feb 26 22:31:13 weather-station kernel: [ 1088.247613] usb 1-1.3: reset 
full-speed USB device number 9 using dwc_otg
Feb 26 22:31:13 weather-station weewx[2212]: wmr300: communication established: 
{'station_model': 'A004', 'latest_index': 65, 'station_type': 'WMR300', 
'mystery1': 44, 'mystery0': 82, 'history_cleared': False, 'magic6, 
'packet_type': 87}
Feb 26 22:31:13 weather-station weewx[2212]: engine: Loading service 
weewx.engine.StdTimeSynch
Feb 26 22:31:13 weather-station weewx[2212]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Feb 26 22:31:13 weather-station weewx[2212]: engine: Loading service 
weewx.engine.StdConvert
Feb 26 22:31:13 weather-station weewx[2212]: engine: StdConvert target unit is 
0x1
Feb 26 22:31:13 weather-station weewx[2212]: engine: Finished loading service 
weewx.engine.StdConvert
Feb 26 22:31:13 weather-station weewx[2212]: engine: Loading service 
weewx.engine.StdCalibrate
Feb 26 22:31:13 weather-station weewx[2212]: engine: Finished loading service 
weewx.engine.StdCalibrate
Feb 26 22:31:13 weather-station weewx[2212]: engine: Loading service 
weewx.engine.StdQC
Feb 26 22:31:13 weather-station weewx[2212]: engine: Finished loading service 
weewx.engine.StdQC
Feb 26 22:31:13 weather-station weewx[2212]: engine: 

[weewx-user] Re: $station.uptime

[Andrew Milner]

are you on a MAC by any chance??  seems like weewx has implemented pretty 
much the method outlined here for os uptime:
http://planzero.org/blog/2012/01/26/system_uptime_in_python,_a_better_way



On Sunday, 4 March 2018 11:07:39 UTC+2, Andrew Milner wrote:

> the format must vary with the operating system then as mine says
> up 1 week, 3 hours, 51 minutes!!
>
> not too sure why your uptime should give be giving any info about users or 
> load averages though!!
>
>
>
> On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote:
>
>> up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21
>>
>> On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:
>>>
>>> if you do uptime -p what result do you get??
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:
>>>
 and the log??



 On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:

> OK the page is now updating (not the images, I'm only interested in 
> the uptime).
>
> http://www.weather.molyvos.eu/Bootstrap/
>
> It still shows
>
> Station uptime: 0 days, 0 Hours, 0 minutes
> Server uptime: 0 days, 0 Hours, 6 minutes
>
>
>
> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:
>>
>> Andrew, 
>>
>> my bad, just noticed that myself and was about to post. I will get 
>> /bootstrap/index running again and see what happens
>>
>> Robin
>>
>> On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:
>>>
>>> the bootstrap skin has totally the wrong date and time of lasdt 
>>> update though!  It is saying November 2015
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:
>>>
 Hi Gary,

 I don't think it is the template or skin config as I also have a 
 Bootstrap skin running.

 http://www.weather.molyvos.eu/Bootstrap/index.html

 Since I did a Weewx stop/start it now shows 

 Weewx uptime: 0 days, 0 hours, 0 minutes
 Server uptime: 0 days, 0 hours, 6 minutes


  


 On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:
>
> $station.uptime by itself should format just fine, though it 
> will/may depend on the contents of skin.conf. In your case it appears 
> to be 
> formatting as it should. Given we are talking about a custom page (ie 
> not 
> one included in a default weeWX install) it would be worth posting 
> the 
> template file (.tmpl) and skin config file being used.
>
> 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: $station.uptime

[Andrew Milner]

the format must vary with the operating system then as mine says
up 1 week, 3 hours, 51 minutes!!

not too sure why your uptime should give be giving any info about users or 
load averages though!!



On Sunday, 4 March 2018 10:14:51 UTC+2, Robin wrote:

> up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21
>
> On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:
>>
>> if you do uptime -p what result do you get??
>>
>>
>>
>> On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:
>>
>>> and the log??
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:
>>>
 OK the page is now updating (not the images, I'm only interested in the 
 uptime).

 http://www.weather.molyvos.eu/Bootstrap/

 It still shows

 Station uptime: 0 days, 0 Hours, 0 minutes
 Server uptime: 0 days, 0 Hours, 6 minutes



 On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:
>
> Andrew, 
>
> my bad, just noticed that myself and was about to post. I will get 
> /bootstrap/index running again and see what happens
>
> Robin
>
> On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:
>>
>> the bootstrap skin has totally the wrong date and time of lasdt 
>> update though!  It is saying November 2015
>>
>>
>>
>> On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:
>>
>>> Hi Gary,
>>>
>>> I don't think it is the template or skin config as I also have a 
>>> Bootstrap skin running.
>>>
>>> http://www.weather.molyvos.eu/Bootstrap/index.html
>>>
>>> Since I did a Weewx stop/start it now shows 
>>>
>>> Weewx uptime: 0 days, 0 hours, 0 minutes
>>> Server uptime: 0 days, 0 hours, 6 minutes
>>>
>>>
>>>  
>>>
>>>
>>> On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:

 $station.uptime by itself should format just fine, though it 
 will/may depend on the contents of skin.conf. In your case it appears 
 to be 
 formatting as it should. Given we are talking about a custom page (ie 
 not 
 one included in a default weeWX install) it would be worth posting the 
 template file (.tmpl) and skin config file being used.

 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: $station.uptime

[Robin]

up 16 days, 18:57,  1 user,  load average: 0.14, 0.19, 0.21

On Sunday, 4 March 2018 09:30:10 UTC+2, Andrew Milner wrote:
>
> if you do uptime -p what result do you get??
>
>
>
> On Sunday, 4 March 2018 09:15:11 UTC+2, Andrew Milner wrote:
>
>> and the log??
>>
>>
>>
>> On Sunday, 4 March 2018 08:40:23 UTC+2, Robin wrote:
>>
>>> OK the page is now updating (not the images, I'm only interested in the 
>>> uptime).
>>>
>>> http://www.weather.molyvos.eu/Bootstrap/
>>>
>>> It still shows
>>>
>>> Station uptime: 0 days, 0 Hours, 0 minutes
>>> Server uptime: 0 days, 0 Hours, 6 minutes
>>>
>>>
>>>
>>> On Sunday, 4 March 2018 08:27:31 UTC+2, Robin wrote:

 Andrew, 

 my bad, just noticed that myself and was about to post. I will get 
 /bootstrap/index running again and see what happens

 Robin

 On Sunday, 4 March 2018 08:11:47 UTC+2, Andrew Milner wrote:
>
> the bootstrap skin has totally the wrong date and time of lasdt update 
> though!  It is saying November 2015
>
>
>
> On Sunday, 4 March 2018 08:07:30 UTC+2, Robin wrote:
>
>> Hi Gary,
>>
>> I don't think it is the template or skin config as I also have a 
>> Bootstrap skin running.
>>
>> http://www.weather.molyvos.eu/Bootstrap/index.html
>>
>> Since I did a Weewx stop/start it now shows 
>>
>> Weewx uptime: 0 days, 0 hours, 0 minutes
>> Server uptime: 0 days, 0 hours, 6 minutes
>>
>>
>>  
>>
>>
>> On Saturday, 3 March 2018 20:41:38 UTC+2, gjr80 wrote:
>>>
>>> $station.uptime by itself should format just fine, though it 
>>> will/may depend on the contents of skin.conf. In your case it appears 
>>> to be 
>>> formatting as it should. Given we are talking about a custom page (ie 
>>> not 
>>> one included in a default weeWX install) it would be worth posting the 
>>> template file (.tmpl) and skin config file being used.
>>>
>>> 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.