I am running 0.9r6. Working fine after removing the 2 skin directories and
installing Belchertown fresh.
On Sat, Feb 23, 2019 at 9:27 PM Pat wrote:
> Hi all, in Belchertown skin version 0.8.2 and older, the about.inc
> inclusion did not allow for weewx variables (at least I don't think so). I
>
Ah yes, hadn't thought of that.
On Sun, 24 Feb 2019, 15:27 Pat, wrote:
> Hi all, in Belchertown skin version 0.8.2 and older, the about.inc
> inclusion did not allow for weewx variables (at least I don't think so). I
> was over-thinking it which made it complicated. Oops :)
>
> In 0.9 (which is
Hi all, in Belchertown skin version 0.8.2 and older, the about.inc
inclusion did not allow for weewx variables (at least I don't think so). I
was over-thinking it which made it complicated. Oops :)
In 0.9 (which is in beta now) I changed a lot, and the about.inc was one of
the changes to
Hi,
Have a look at the install command you used, you need to change
weewx-forecast-x.y.tgz to weewx-forecast-3.3.2.tgz
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
kelly,
you downloaded weewx-forecast-3.3.2.tgz, and it looks like you are running
on a debian installation, so you should run this:
sudo wee_extension --install weewx-forecast-3.3.2.tgz
the 'sudo' is necessary since debian installs require root privileges to
modify the weewx configuration.
m
On Saturday, February 23, 2019 at 12:52:29 PM UTC-5, steepleian wrote:
>
>
>1. The WH-650 clone is an 868Mhz version and I have been able to map
>the the outdoor sensor (WH65B). However the internal sensor (WH32B or
>WH31- not sure) which is also 868Mhz does not show at all.
>
On Saturday, February 23, 2019 at 10:36:45 AM UTC-5, Mark Jenks wrote:
>
> I've been running this for a few years now, and once and awhile weewx just
> falls over for no good reason. To deal with this, I wrote a script that I
> run in cron to check to make sure it's running, and if not, start
WeeWX is designed to recover from hardware issues. Now, if the operating
system crashes, there isn't much you can do about that. But, your restart
script isn't going to help that either.
Please pass on the system log of any WeeWX crash.
On Sat, Feb 23, 2019 at 12:57 PM Mark Jenks wrote:
> It
I've had my WMR for 8-9 years. It looks horrid. lol
On Saturday, February 23, 2019 at 12:57:27 PM UTC-6, vince wrote:
>
> On Saturday, February 23, 2019 at 9:37:41 AM UTC-8, rich T wrote:
>>
>> Might to check here:
>>
>>
>>
It doesn't do it often, but I think it had a hardware issue with the usb.
It could be the OS that I'm on also..
Better
On Saturday, February 23, 2019 at 10:00:49 AM UTC-6, Thomas Keffer wrote:
>
> Mark,
>
> WeeWX should not crash. If it does, it's a bug. I have successfully run it
> for 2
Go for a Davis VUE ISS and receive it with a Moteino.
Price Lower than 300$ and excellent quality.
El sábado, 23 de febrero de 2019, 16:39:50 (UTC+1), Mark Jenks escribió:
>
> Currently, I have a WMR200, but it originally started out as a WMR100.
> The console died and I found a good used 200
On Saturday, February 23, 2019 at 9:37:41 AM UTC-8, rich T wrote:
>
> Might to check here:
>
>
> https://www.scaledinstruments.com/product-category/davis-instruments/complete-weather-stations/
>
>>
>>
Yup - they're the other great 3rd party seller. I bought my replacement
VP2 anemometer there.
RE: https://github.com/weewx/weewx/wiki/forecasting
Hello,
Following the installation instructions,
[image: forecast installation instructions.PNG]
I've tried to install the *forecast* extension for weewx running on my RPi
3B+ running Raspbian Linux 9 (stretch) [4.14.98-v7+], but have run
I am currently searching for a replacement wifi receiver for my FO WH-2650
European clone. I decided in the interim that I would have a play around
with a SDR USB dongle.
Followed the instructions to install rtl_sdr and rtl_433 along with the sdr
extension.
1. The WH-650 clone is an
Might to check here:
https://www.scaledinstruments.com/product-category/davis-instruments/complete-weather-stations/
On Saturday, February 23, 2019 at 10:39:50 AM UTC-5, Mark Jenks wrote:
> Currently, I have a WMR200, but it originally started out as a WMR100.
> The console died and I found a
On Saturday, February 23, 2019 at 7:39:50 AM UTC-8, Mark Jenks wrote:
>
> What does everyone recommend? I'd like to keep it under $300 if possible.
>
>
>
You might want to poke around the forums at wxforum.net for details on all
the mainstream stations.
History seems to prove that if you can go
Mark,
WeeWX should not crash. If it does, it's a bug. I have successfully run it
for 2 years at a time.
The next time it does, please post the system log. Far better to engineer
out the point of failure.
-tk
On Sat, Feb 23, 2019 at 7:36 AM Mark Jenks wrote:
> I've been running this for a few
I have 'solved' the issue.
I deleted the skin directories for Belchertown, installed the skin again,
cycled WeeWX, run wee_reports.
All is well with variables and about.inc.
Something indeed was missing in the skin directories.
Thanks all.
--
You received this message because you are
I've been running this for a few years now, and once and awhile weewx just
falls over for no good reason. To deal with this, I wrote a script that I
run in cron to check to make sure it's running, and if not, start it over
again.
Here it is for everyone to use
-Mark
[root@server bin]#
I have followed the outlined steps, about.inc, etc.
I enabled debug logging and started weewx, ran wee_reports, stopped weewx.
I've attached the resulting logs.
There are errors, but they seem to relate to the sdr driver.
--
You received this message because you are subscribed to the Google
weewx requires rain during archive interval for storing in the database
archive records. A driver may have to convert whatever it receives (eg
running total) so as to obtain the value for the interval. Daily is
accumulated by weewx from the archive interval values and weekly and
monthly are
Had another look at what had gone on and checked what I had done in the
WeeWx, Skin and Index files and what I ended up doing is commenting out the
forecast api sections for those I didnt have APIs for and that seemed to
have worked...
So, I had step 2 correction to make.
Thanks, Matt, for
Hello community,
I would like to add an additional rain gauge as additional source described
in the customization guide.
Can you give me any hints how to do this the easiest way, to get the daily,
weekly and monthly percipation.
Can I use any modules or calculations that are already done
Thanks Thomas,
Clean data and all OK again.
Great work!
El viernes, 22 de febrero de 2019, 21:38:32 (UTC+1), Thomas Keffer escribió:
>
> The bad data point has probably been there all along --- it's just that
> WeeWX is a little more strict about it.
>
> Try this on your database. *Boldface*
Ok, let's see if we can get that 1st para to make a bit of sense:
This part of your log extract shows two different processes (1393 and 1338)
trying to communicate with your station, it happens if you start WeeWX again
without stopping it first or doing a restart:
Gary
--
You received this
25 matches
Mail list logo
