On Wed, 3 Jan 2024 at 07:42, Kevin Crivelli
wrote:
> Not like "last 12 months" but "last year". I'd like to have a graph
> section for that. I'm sure it's very easy but I can't put my finger on it
>
I tried to do this for images, but my patch was rejected.
As for html that can be done:
>From that github site…
hostname - Set your IP or hostname of WLL module
So your snippet looks incorrect for hostname….
On Tuesday, January 2, 2024 at 8:21:37 PM UTC-8 Rich Strle wrote:
> From this link: https://www.wxforum.net/index.php?topic=41328.0
>
> I thought weatherlinklive-driver-weewx
>From this link: https://www.wxforum.net/index.php?topic=41328.0
I thought weatherlinklive-driver-weewx would be the
best: https://github.com/Drealine/weatherlinklive-driver-weewx
There are so many drivers with similar names it's easy to go in circles
looking.
On Tuesday, January 2, 2024 at
How did you install WeeWX; using setup.py or as a package using apt or
dpkg? The command you are using assumes a setup.py install, if you have a
package install you need to use:
PYTHONPATH=/usr/share/weewx python -m user.gw1000 --test-driver
Also, to make life easier for us (and to help you
I have upgraded to a Davis VantagePro2 (VP2) from a VantagePro1 (VP1).
I am trying to read my current data from weatherlink.com with the
WLLDriver. Has anyone else tried this? This is the driver section of
the whew.conf file. I'm concerned about the hostname for sure. Does someone
have a
On Tuesday 2 January 2024 at 01:06:04 UTC+10 deng...@cfl.rr.com wrote:
If I was not ALSO publishing what WeeWx was creating as a page, I don't
think I would have ever noticed. I have not figured out how/where image
files (except for daywindrose.png) generated by weewx-saratoga are used.
The
Some extensions use "StrictVersion" from distutils to test the version
number of weewx. It fails for anything with an "rc" in the version number.
You didn't show enough of the log to see what extension did this, but if
you comment out the version check, things will probably work.
On Tue, Jan 2,
Indeed, V5.0.0rc2 declines to start
Jan 03 08:03:09 boronia weewxd[236273]: CRITICAL __main__: if
StrictVersion(weewx.__version__) < StrictVersion(REQUIRED_WEEWX):
Jan 03 08:03:09 boronia weewxd[236273]: CRITICAL __main__:
Jan 03
I did find a debian:trixie docker image and gave the v5 beta a quick test.
The pip method seems to work. The rc2 dpkg looks like it has some issues
so I'd hold off on trying that.
Or do the v4 workaround in the thread I mentioned earlier.
On Tuesday, January 2, 2024 at 12:21:54 PM UTC-8
Not like "last 12 months" but "last year". I'd like to have a graph section
for that. I'm sure it's very easy but I can't put my finger on it
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving
Always always always search the forums for your AttributeError message.
Look at https://groups.google.com/g/weewx-user/c/XmKEPTN1L_g/m/GUWqcdaQCQAJ
and see if that helps any. You might also try using the v5 beta as well,
although it is still seemingly not finalized.
Running old software on a
On 1/1/24 I updated my Debian server to trixie, finishing the update
about 1620.
My last images on my Weewx web page are dated 1/1/24 1700.
I found a few errors in my logs, and looked for previous posts
concerning these but didn't find anything that fixed my errors.
Weewx v4.10.2
Debian Testing
Maybe not really helpful, but anyway:
- isn't the parameter --ip-address (you use "ip-addresse")
- Is there a reason why you use an outdated version of weewx for a clean
install?
Robert de Keijzer schrieb am Dienstag, 2. Januar 2024 um 07:43:13 UTC+1:
> Hi, I have a clean install
That’s fixed it Gary, many thanks!
Happy New Year,
Rory
> On 1 Jan 2024, at 19:54, gjr80 wrote:
>
> Rory,
>
> There is a bug in the realtime gauge extension windrun unit conversion, the
> net result was that when specifying wind speed in mile_per_hour windrun was
> left as the km value
14 matches
Mail list logo
