RE: [weewx-user] Re: $station.uptime

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

[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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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,

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

Re: [weewx-user] Re: $station.uptime

sorry gary - we seem to have crossposted!! On Sunday, 4 March 2018 09:28:19 UTC+2, Andrew Milner wrote: > if you search for uptime in /bin/weewx/station.py you will see how weewx > and server uptimes are derived!! > > may offer some clues > > > > On Sunday, 4 March 2018 09:18:41 UTC+2, Erwin

Re: [weewx-user] Re: $station.uptime

if you search for uptime in /bin/weewx/station.py you will see how weewx and server uptimes are derived!! may offer some clues On Sunday, 4 March 2018 09:18:41 UTC+2, Erwin Heger wrote: > The data from this example webpage are all totally outdated, all from 2015. > > Did you switch the

[weewx-user] Re: $station.uptime

You might want to upgrade to a later weeWX version, at least 3.7.0, as there have been a number of changes to bin/weewx/station.py (the module that handles station uptime and server uptime) since your 3.6.1 version. I had a quick look at station.py just now and cannot see any one change that

Re: [weewx-user] Re: $station.uptime

The data from this example webpage are all totally outdated, all from 2015. Did you switch the database or is it all static? Better put the uptime-variable into a live page than driving us nuts with something, that doesn’t work at all. > > http://www.weather.molyvos.eu/Bootstrap/ >

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

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

[weewx-user] Re: $station.uptime

$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

[weewx-user] Re: $station.uptime

One other reason is that the about page is not, for some reason, being regenerated every report cycle - or is not being copied/ftpd every cycle. Is it perhaps included in the 'copy once only' list?? As gary says, looking at the site may help and the logs certainly would be valuable and should

[weewx-user] Re: $station.uptime

Maybe time is standing still ... Seriously though - do the other variables like system time change with only station uptime appearing to be stuck in a spacetime distortion?? On Saturday, 3 March 2018 10:45:48 UTC+2, Robin wrote: > I have this feeling in my water that I am missing

Re: [weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

I suppose we could include a check in the templates that if uptime is None, don't render the days, hours, and seconds at all. -tk On Sun, Oct 30, 2016 at 11:36 PM, gjr80 wrote: > Hi, > > I wouldn't go so far as to say this is expected behaviour (well it is > expected in

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

You can also use wee_reports to see your 'quick' changes in the templates etc immediately (not waiting for the next report cycle) without reloading or restarting weewx. http://www.weewx.com/docs/utilities.htm#wee_reports_utility Regards, Steve. On Friday, 14 October 2016 20:18:31 UTC+11,

[weewx-user] Re: $station.uptime should not reset to Zero when weewx is only doing a reload

On Friday, October 14, 2016 at 2:35:24 AM UTC-7, gjr80 wrote: > > - A reload (or a restart if you really want to) is required if you make > changes to weewx.conf. > yup - that was the case I had a few times in the past. I think I had forgotten to enable the station registry, but didn't want