Am Mittwoch, 7. August 2019 21:11:04 UTC+2 schrieb gjr80:
>
>
> Remember that an archive record value is an average over a period of say 5
> minutes so the need for 1 degree precision in the case of wind direction
> seems somewhat less important.
>
> Gary
I wouldn't consider it import in a sta
The rsync skin is really a special kind of skin just for external
transfers. The instructions for using it are in the form of comments
within weewx.conf . If you change nothing after doing a standard install
then weewx will use the seasons skin for creating web pages and the rsync
skin for ou
Just Google "WeeWx Skins", you will find a bunch of them and most are
fairly simple to install. Good ones will have easy directions. I use Pat
O'Briens excellent Belchertown Skin and it had great instructions
On Wednesday, August 7, 2019 at 8:59:02 PM UTC-5, Anthony Fandino wrote:
>
> I have
I have begun a small project of putting a remote weather station on my
farm.
I am using RSYNC to transfer data to my webserver. My question is how can I
use another skin on my webserver other than the rsync skin. I see that in
the Rsync skin.conf file there is a hook into
weewx.reportengine.R
On Tuesday, August 6, 2019 at 10:36:07 AM UTC-4, Greg Troxel wrote:
>
>
> I realize I can set the name, but perhaps the name should be ge from the used units rather than the database or standard units.
>
i would consider this a bug in the extension; when 'append_units_label' is
True, the label t
Sounds good! I noticed that about your site that the non-www did not work.
Hopefully you have found the fix.
On Wednesday, August 7, 2019 at 9:26:27 AM UTC-4, Brezentrager wrote:
>
> Pat,
> I think I know the reason for this issue. It seems to be caused by a
> missing .htaccess file on my serv
Hi Greg, here's some of my thoughts on your thoughts.
> One of the things I find hard about MQTT is that while it's somewhat like
(being fuzzy) TCP/UDP/IP as a transport layer, there don't seem to be
specifications that lay out what subtopic names to use and what the
contents should be. It see
Should re-install the OS and have a look at these links:
https://github.com/merbanan/rtl_433
https://github.com/matthewwall/weewx-sdr
https://github.com/weewx/weewx/wiki/sdr-rpi-recipe
On Wednesday, August 7, 2019 at 3:13:06 PM UTC-4, Steve London wrote:
> Trying to install weewx on Raspbian.
Error is gone looks like they fixed their certificate.
Thanks!
-pmb-
On Tuesday, August 6, 2019 at 4:42:13 PM UTC-6, paul bennett wrote:
>
> Have been running weewx 3.9.2 for a while now without trouble ... until
> this morning. Suddenly cannot post RF updates to WU.
>
> Relevant log entri
Thomas,
Thank you for sharing your experience I keep it on then. But if rapid fire
will make my data/pws look unreliable then maybe I will stick with the
regular PWS protocol.
TY
Bill
On Wednesday, August 7, 2019 at 12:19:04 PM UTC-4, Thomas Keffer wrote:
>
> It's absolutely powerful enough.
Thank you thank you Leon! That's what I could not find for the life of me!
Regards
Bill
On Wednesday, August 7, 2019 at 12:58:46 PM UTC-4, Leon Shaner wrote:
>
> I have an example wunderfixer_wrapper script and corresponding crontab
> example, here:
>
> https://github.com/UberEclectic/weewx/
I'm sorry, but you're on your own for that!
It might be easier to just re-install the operating system.
-tk
On Wed, Aug 7, 2019 at 1:40 PM Steve London wrote:
> Too late. I removed python2.7. Now I get this when I try to install it:
>
> Setting up python2.7 (2.7.13-2+deb9u3) ...
> Sorry: TypeE
That proves nothing: the configuration file in the distribution does not
come with a driver declared. Hence the "unspecified" driver.
Humor me and run weewx again, this time posting the log (/var/log/syslog).
*sudo systemctl start weewx*
-tk
On Wed, Aug 7, 2019 at 1:26 PM Steve London wrote:
On Monday, August 5, 2019 at 10:48:45 PM UTC+2, Thomas Keffer wrote:
>
> Yup. That’s the issue fixed by 3.9.2
>
Thanks !
-- Axelle
--
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,
Didn’t pickup on that. The ws28xx driver has no genArchiveRecords method, there
is a comment in the driver to the effect that hardware record generation should
not be implemented until archive records can be read at a faster rate than they
are currently.
Gary
--
You received this message beca
It does look like you have a problem with your Python installation. Try the
following:
*python -c "print('hello world!')"*
If it creates an error, your Python is broken.
-tk
On Wed, Aug 7, 2019 at 12:14 PM Steve London wrote:
> Trying to install weewx on Raspbian. Python has never (successfu
Just a clarification: on startup, weewx does indeed call the
genStartRecords() method on the driver. However, the default implementation
is to just call genArchiveRecords() with the last good timestamp in the
database as an argument. If the driver supports it, this effectively means
a "catch up" is
Trying to install weewx on Raspbian. Python has never (successfully) been
installed on this rPi. Here's the errors. Suggestions ?
Thanks !
pi@raspberrypi:~ $ sudo apt-get install weewx
Reading package lists... Done
Building dependency tree
Reading state information... Done
weewx is alread
Not sure the WeeWX engine behaviour (backfill only requested during WeeWX
startup/restart) will change, you probably have more chance of changing the
driver behaviour.
Regarding your loop data question. Unfortunately there is little that can be
done if the station does not maintain the same lev
Thank you for the explanation, Gary, everything now seems perfectly logical
to me. Being a software developer myself I have a feeling that it probably
isn't an easy change task to let weewx backfill values under such
circumstances, nevertheless I'll write that on my christmas wishlist ;)
Maybe
Thank you for the explanation, Gary, everything now seems perfectly logical
to me. Being a software developer myself I have a feeling that it probably
isn't an easy change task to let weewx backfill values under such
circumstances, nevertheless I'll write that on my christmas wishlist ;)
@Gary:
I have an example wunderfixer_wrapper script and corresponding crontab example,
here:
https://github.com/UberEclectic/weewx/tree/watchdog/examples/watchdog
You can ignore the watchdog if you want, because they're independent (but
complimentary) utilities.
If you want only the wunderfixer_wrappe
Are you still getting this error? It looks like they moved things to AWS.
$ nslookup rtupdate.wunderground.com
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
rtupdate.wunderground.com canonical name =
prod-pws-ng-ingest-368531364.us-west-2.elb.amazonaws.com.
Name: prod
It's absolutely powerful enough. It could easily handle the reports as well.
Nevertheless, if you don't want to do report generation, just remove
weewx.engine.StdReport from the list of services to be run.
Still, I think you'll find the reports useful, even on your Pi2, especially
for debugging a
Do you believe the Pi2 is powerful enough to do 2.5 second or 5 second RF?
I do not know how the performance is. I would like to have weewx also stop
generation cheetahgenerator and imgegenderator as I do not use the website
features. this may give her some more head room. Again these are questi
OTBE. Looks like WU fixed their certificate. All is well.
On Tuesday, August 6, 2019 at 4:42:13 PM UTC-6, paul bennett wrote:
>
> Have been running weewx 3.9.2 for a while now without trouble ... until
> this morning. Suddenly cannot post RF updates to WU.
>
> Relevant log entries:
>
> ...
> *
OK great for the past 24 hours.
Is there anything to choose between (e.g.) '$span($week_delta=1)' and '$week',
given I'm not offering max/min etc. for the past 2 weeks for example?
On Wednesday, 7 August 2019 09:09:20 UTC+1, Andrew Milner wrote:
>
> have you tried $span with $hour_delta
> eg
> $
If you call the ‘top of the hour’ archive records rogue records then yes they
had a hand in preventing backfill, provided a restart occurred only those
archive records stored in the station after the most recent ‘top of the hour’
archive record would be downloaded. Arguably though the reason the
Gary - thanks for that good description of when backfilling occurs although
I have a feeling that the original poster had to restore an old copy of the
database in order for backfilling to occur - hence my suspicion about a
rogue dateTime in the database which would not backfill.
On Wednesday
Good Day,
I have searched the forums but I have not found the proper flags to run
with Wunderfix on my Cron job.
Nor could I locate the best practices for times and tweaks to use on a Pi2.
If anyone can point me to a github doc or such. I haven't even downloaded
it yes as I am doing research f
Pat,
I think I know the reason for this issue. It seems to be caused by a
missing .htaccess file on my server. The non-www requests don‘t get
redirected to www.domain.de. The skin then cannot find the highchart
resources nor does it connect to the MQTT broker correctly.
Should be an easy fix t
Hi,
The backfill behaviour you are seeing is expected behaviour for the current
codebase, in a nutshell WeeWX only attempts to download historical records when
WeeWX starts.
Explanation. Drivers for stations that have the ability to store archive
records may implement a genStartupRecords metho
be sure that you have a reliable usb connection.
try using a powered usb hub instead of plugging directly into the rpi. try
using a bigger power supply on the rpi. try removing all other usb devices
from the rpi.
m
--
You received this message because you are subscribed to the Google Groups
Am Mittwoch, 7. August 2019 13:49:00 UTC+2 schrieb Andrew Milner:
>
> You never said that it recovered by itself after 0100 - in fact you gave
> the impression that it only started working again after you stopped weewx,
> restored an old database and restarted weew and that then it did the
> b
You never said that it recovered by itself after 0100 - in fact you gave
the impression that it only started working again after you stopped weewx,
restored an old database and restarted weew and that then it did the
backfill and recovered. Well that is how I understood your posts anyway.
On
Am Mittwoch, 7. August 2019 09:20:27 UTC+2 schrieb Andrew Milner:
>
> do you have a rogue dateTime in the database?
>
>
Not that I'm aware of.
> The log you posted ONLY has database records added at 22:00, 23:00, 24:00
> and a message every 10 minutes saying there is no new data - press SET t
hello,
i dont know why, but my weewx crashed sometimes. works after weewx start,
and after some minutes or hours the connection is lost
Aug 07 08:07:53 raspberrypi weewx[446]: te923: Found device on USB bus=
device=
Aug 07 08:07:53 raspberrypi weewx[446]: te923: Failed attempt 1 of 5 to
re
Thanks will try that.
On Wednesday, 7 August 2019 09:09:20 UTC+1, Andrew Milner wrote:
>
> have you tried $span with $hour_delta
> eg
> $span($day_delta=1).outTemp.max for the max temp in the previus 24 hours
>
>
>
> On Wednesday, 7 August 2019 10:11:51 UTC+3, Auchtermuchty Weather wrote:
>>
>> A
have you tried $span with $hour_delta
eg
$span($day_delta=1).outTemp.max for the max temp in the previus 24 hours
On Wednesday, 7 August 2019 10:11:51 UTC+3, Auchtermuchty Weather wrote:
>
> Apologies if this is the wrong place to ask.
>
> I'd like 24-hour aggregates / max / min rather than toda
do you have a rogue dateTime in the database?
The log you posted ONLY has database records added at 22:00, 23:00, 24:00
and a message every 10 minutes saying there is no new data - press SET to
resynch. I repeat - how do you know that it has reconnected?? No new data
implies that it has NOT co
Apologies if this is the wrong place to ask.
I'd like 24-hour aggregates / max / min rather than today or yesterday. Is
this something that might come along?
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and sto
41 matches
Mail list logo
