Off the top of my head I'd say remove Python 2, install Python 3. That
should be enough.
(My personal preference would be to then) remove weewx using sudo apt-get
remove weewx, then install using the setup.py. I find it much easier to
have the whole thing live in the 1 folder /home/weewx.
Ok, I'll try that. Is there a way to make it use python 3 instead? I
haven't done much research there, yet. Let's face it. Python 2 is about
done.
Maybe I'll go dig through the update section of the wiki before I start ;)
Thanks again for everything!
Ernie
On Mon, Jul 20, 2020 at 9:13 PM Pat
Take a backup of everything just in case, then run these commands and it
should upgrade to the latest version
sudo apt-get update
sudo apt-get upgrade weewx
On Monday, July 20, 2020 at 9:11:39 PM UTC-4, Ernest Jillson wrote:
>
> It's on raspbian, but I have the /etc/weewx, not /home/weewx. I
It's on raspbian, but I have the /etc/weewx, not /home/weewx. I think I'll
just save off the database and start fresh.
On Mon, Jul 20, 2020 at 8:59 PM Pat wrote:
> Glad it worked!
>
> Quick way to tell how you installed it, if you have a /home/weewx folder,
> it's from the setup.py option. If
Thanks. I’ll mess around and see if I can get the dev version working
--
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.
Yep! Aeris is only working in the development version right now. I'm
working on final clean up of the skin and will be publishing the
development as a release soon.
On Monday, July 20, 2020 at 8:32:14 PM UTC-4, Jamie Stephens wrote:
>
> do i need to be running the development version to use
Glad it worked!
Quick way to tell how you installed it, if you have a /home/weewx folder,
it's from the setup.py option. If you have an /etc/weewx folder, it's
probably from apt install weewx (if on ubuntu) or yum install weewx (if on
centos/redhat).
If none of those are true, then you may
You, sir, are a brilliant man! Worked like a charm on the first try!
Now to brave going to weewx 4.newest and latest Belchertown...
Problem is, I don't remember how I installed weewx the first time. Did I
use the setup program? Hmmm.
Thanks for all your help! Of all the skins I have seen on
do i need to be running the development version to use the forecast with
aeris? go easy on me i'm still learning linux and weewx
ERROR weewx.reportengine: Warning: Error downloading forecast
data. Check the URL in your configuration and try again. You are trying to
use URL:
No worries - I wasn't sure if you thought there was a problem with the
skin. So I have the same problem as you, where the Davis console sends
loops with the most accurate wind direction, but the archive packets are
generalized. I hate it, and (with Tom's help) made this quick extension.
First, let me apologize. I didn't mean to imply that the skin was the
issue. Thanks for your suggestion to look at the packets. So the loop
packets have the correct wind direction in them. The rec packets, however,
seem to be rounded to the nearest 22.5 degrees.
Obviously the Davis VP2 is
Run the command : which wunderfixer
That should give you the correct path. Mine is at /usr/bin/wunderfixer
On Mon, Jul 20, 2020 at 11:35 AM Dave McCreath
wrote:
> Hi All
>
> Bit of advice please for a noob.
>
> Running Weewx on an RPi 4, Raspian 10 (Buster) and recently upgraded to v4
> from
I'm not sure this is a problem with the skin, but rather your station
reporting the archive value of the wind direction. As you can see on my
site, my wind degrees aren't plotted to the nearest value. (e.g. 368
degrees, 334 degree, etc)
Before we blame the skin, run weewxd and post some loop
Hi All
Bit of advice please for a noob.
Running Weewx on an RPi 4, Raspian 10 (Buster) and recently upgraded to v4
from v3.
I was aware that Wunderfixer stopped working some time ago in v3 (unless
you were a Linux guru, which I'm not) due to api issues.
Now that I have upgraded to v4, all is
That slipped through in the upgrade section. Yes, you want
trend.barometer.formatted if you are looking if you don’t want a label. (Use
trend.barometer if you want a label.)
I’ll fix that in the upgrade section today (or just remove the upgrade section.)
> On Jul 20, 2020, at 12:23 AM,
Any Python expression can be used. It would look like:
inHumidity = inHumidity if inHumidity else 100.0
Basically, any value that is non-zero will be retained. Otherwise, it is
set to 100.0
-tk
On Mon, Jul 20, 2020 at 4:57 AM Praveen Chandrasekaran <
praveen.c...@gmail.com> wrote:
> Hi,
>
>
Hi,
My indoor humidity sensor has gone bad and it rolls from 99percent to 0 instead
of 100.
I tried adding a QC but that fills the log every loop data. Also graphs are
broken.
Can I put an expression like
Foo = (Foo == 0) ? 100 : foo
In StdCalibrate instead?
I know that I will never hit 0
Hi PAT, I have version 1.2rc2 since yesterday. So now "start_at_midnight =
true" also works. *Very important*, this is the only way that the daily
rain sums are correct.
geni08...@gmail.com schrieb am Sonntag, 12. Juli 2020 um 10:47:51 UTC+2:
> On 3 days we had rain of 9mm, 8.6mm and 0.6mm.
Hello Christian,
Many thanks to this solution.
I was looking for a solution for a Bresser Station (which uses only WIFI),
but I want to use weewx further.
Could you please explain your solution more in detail for a newbie? ;-)
Which steps do I have to implement in my actual weewx 4.0.
Hi John, since version 2.0.b8 the display works as expected. I have just
installed 2.0.b10 and see no difference on the fast.
What I don't understand is why the documented field
"trend.barometerRate.formatted" does not provide any information in the
loop-data.txt. Do I get my information from
20 matches
Mail list logo
