But I get an "TypeError: format() got an unexpected keyword argument
'None_string'' error.
On Thursday, February 28, 2019 at 10:15:31 PM UTC-5, rich T wrote:
>
> Pat
>
> Installed without any issues.
>
> Rich
>
> On Thursday, February 28, 2019 at 7:50:34 PM UTC-5, Pat wrote:
>
>> I've just
Thanks Pat appreciate all the hard work you do. I'll upgrade either tonight
or first thing tomorrow.
Cheers
Colin
On Fri, 1 Mar 2019, 13:50 Pat, wrote:
> I've just released Belchertown skin 0.9. You can read the updates and
> download it here:
I've just released Belchertown skin 0.9. You can read the updates and
download it here: https://github.com/poblabs/weewx-belchertown/releases
A lot of work went into this release. I've learned a lot through feedback
on the skin.
This release fixes a major bug with the rain charts which were
So the visible % is now 26% for both the new and old versions of
almanac.py/Moon.py and the new version now lists the phase as Waning
Crescent (as does the old version and WU).
Phil
On Thursday, February 28, 2019 at 11:29:28 AM UTC-5, kutz...@gmail.com
wrote:
>
> Here's an interesting piece
Tom: I will let it run as is, and report back tomorrow with 48 hour stats.
--
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
5% is way better than before, no?
I would expect occasional buffer errors with this version. The serial port
is constantly getting opened and closed. If a new packet comes in at the
wrong time, parts of it could get missed.
On Thu, Feb 28, 2019 at 10:22 AM Steve2Q wrote:
> Tom; at 25 hours top
Tom; at 25 hours top shows 5.0% v 4.4% at 24 hours for 11rc3 and is still
going up.
Also 0.25 is throwing off sporadic buffer errors as follows.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving
Steve, progress report? Is version 0.25 holding steady?
On Wed, Feb 27, 2019 at 9:33 AM Thomas Keffer wrote:
> Well, that's the current kernel version. Let's see how it goes with the
> new Ultimeter driver.
>
> -tk
>
> On Wed, Feb 27, 2019 at 8:58 AM Steve2Q wrote:
>
>> I am going to try .25
Here's an interesting piece of data. I'm using Tom's new almanac.py and
Moon.py on a testbed version of WeeWX. On my "production" instance of
WeeWX, I have the versions of those files originally installed with WeeWX
3.9.1.
On my production instance the moon is listed as 29% visible and is
Pull its power supply, then plug it back in. That's as good a test as any.
On Thu, Feb 28, 2019 at 6:40 AM David Hindley wrote:
> Thanks for your reply, Tom - much appreciated.
>
> I have removed the fake clock (pending purchase of a RTC) and made the
> change to the file in init.d and
Do a google search of this group for "non-positive" and you'll find a
number of *very* recent threads for other folks with this message..
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving
Thanks for your reply, Tom - much appreciated.
I have removed the fake clock (pending purchase of a RTC) and made the
change to the file in init.d and restarted weewx with a working network and
all seems OK, but I guess I won't know fully until the Pi crashes again.
David.
On Thu, 28 Feb 2019
1. It looks like you're using the WeatherLinkIP logger in your Vantage.
These are generally not as reliable as the serial and USB versions and, as
you discovered, depend on the network being up before the Vantage is useful.
I am not a boot expert, but try this: go into /etc/init.d/weewx and
Many Thanks.
1. I will do as you suggest re separate log files.
3. The cron task was something I had to add after installing the
belchertown skin, just to copy some files from one directory to another, on
the Rpi, before then using sftp to upload to my website. It seems to work
most of the
1. I recommend you put weewx log messages in their own log file - see wiki
for a) separate logfile and also logrotation.
2. The ^@ rubbish looks like possible corruption whilst executing a cron
task
3. What cron task was it trying to execute
4. I see the clock has gone backwards around the
Thanks. I agree that it is probably the Raspberry Pi, rather than weewx.
My syslog file around the relevant time that it stopped working yesterday
is as follows. Does anyone have any idea how to interpret this? The "^@"
is very puzzling to a linux novice such as me!
David.
Feb 27 15:30:28
The best tip I can give you is to identify why the site is crashing by
looking at the weewx and webserver logs.
Weewx should never crash per se. If it encounters an irrecpoverable
situation it should restart. If it is not restarting Tom would require, I
am pretty sure, to see the log of the
I use weewx on a Raspberry pi and post my results to my own public weather
station website (www.ashteadweather.com) with the excellent belchertown
skin. It all works very nicely most of the time, but now and again,
something goes wrong and the Raspberry pi crashes and weewx stops working -
18 matches
Mail list logo
