ok god thx it is working again
--> new driver version v.1.1.4:
thanks for your support :)
● weewx.service - WeeWX
Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor
preset: enabled)
Active: active (running) since Fri 2024-03-01 19:31:46 CET; 14s ago
Docs: https://weewx
If you're python 3.7 on the raspi os, you are running an old debian-10
based system which although it's as patched up as it can be, it's not
really current. I have an old pi running that os and my python3 is 3.7.3
FWIW. But the underlying problem is you likely didn't get something quite
right
Yeah I even had problems creating the venv environment with 3.9 and that
worked in the past with other software on 3.7.
But I have a Debian Package installation and don't want to lose all my
changes so I am hoping that I will get it to work with python 3.7 and new
driver version.
Or is venv a mu
Hi vince,
no not really, it is an up to date Raspberry Pi which was running 4.10.2
and Python 3.7 without issues.
Problems started with weewx 5. First I did the update to 5.0.1 and it
worked as well. Then I saw that there is another update to 5.0.2 and also
changed weatherlink_live driver to ne
Not sure what's going on there, but it may have something to do with
attempting to install as root. Try installing as an unprivileged user, say
"pi".
$ *su - pi*
$ *whoami*
pi
$ *cd*
$ *python3.9 -m venv weewx-venv*
$ *source weewx-venv/bin/activate*
$ *python3.9 -m pip install weewx*
$ *weectl st
That's very odd. Are you running a very unusual or very ancient os on your
pi ?
I don't think I've ever seen lsb_release 'fail' but I recall some os didn't
have that command years ago
What do the following commands return when you run them from the shell ?
- lsb_release -a
- cat /etc
Author of the driver suggested to use Python 3.9 which I installed and now
I get a different error:
Feb 29 19:57:12 loxberry systemd[1]: Started WeeWX.
Feb 29 19:57:12 loxberry weewxd[30842]: Traceback (most recent call last):
Feb 29 19:57:12 loxberry weewxd[30842]: File "/usr/share/weewx/weewxd.
I think the problem is in the typing suggestions used by the driver. They
can be tricky to get right. For example, in file mappers.py, line 137, reads
def map_table(self) -> Dict[str, Union[str, list[str]]]:
when it should probably be
def map_table(self) -> Dict[str, Union[str, List[str]
ok funny, after a reboot, v.5.0.2 is getting loaded.
Error is now:
-- Logs begin at Thu 2024-02-29 00:06:39 CET, end at Thu 2024-02-29
08:06:40 CET. --
Feb 29 00:06:53 loxberry systemd[1]: Started WeeWX.
Feb 29 00:06:56 loxberry weewxd[932]: INFO __main__: Initializing weewxd
version 5.0.2
Feb
yeah basicaly driver is not running and therefore Data from weatherlink
Live cannot be read.
But question is, athough 5.0.2 is installed and driver v1.1.3, why are
those not used and instead, 5.0.1 is being loaded?
Tom Keffer schrieb am Donnerstag, 29. Februar 2024 um 01:31:38 UTC+1:
> I hate t
I hate to "pass the buck," but this looks like an issue with the new
WeatherLink Live driver.
The log entry gets cut off with the phrase "Caus", which I suspect would
give you the "cause." Take a look in your log.
On Wed, Feb 28, 2024 at 3:03 PM fLsh wrote:
> Hi folks,
>
> I was happily run
Hi folks,
I was happily running 4.10.2 on my Raspberry Pi 4 with many changes to
skins, drivers and templates.
Today I did an upgrade to 5.0.1 which was running too. Then I so in apt
update that there is a public key missing which I resolved with the
documentation. After that, 5.0.2 was availab
12 matches
Mail list logo
