Recently I've noticed that I'm not recording any rain even though it is
being received:
Nov 1 05:12:46 weather-new weewx[3765] DEBUG user.sdr: packet={'windGust':
8.568, 'outTempBatteryStatus': 0, 'rain_total': 62.73, 'windSpeed': 4.896,
'windDir': 248.0, 'dateTime': 1667279561, 'usUnits': 16}
Nov
Thanks for spotting this. There is an issue is v0.5.5 that maps current
wind direction to both the 'bearing' and 'avgbearing' fields used by the
SteelSeries gauges. I should have a fix by tomorrow.
Gary
On Tuesday, 1 November 2022 at 05:34:05 UTC+10 marsha...@gmail.com wrote:
> Built a new sta
Use the MQTT driver which takes the data directly from your mosquitto
server.
Avoids all the middleware.
I use Rich's excellent package.
https://github.com/bellrichm/WeeWX-MQTTSubscribe
On Monday, October 31, 2022 at 3:34:05 PM UTC-4 marsha...@gmail.com wrote:
> Built a new station using an esp
Will do, thx.
On Monday, October 31, 2022 at 4:04:35 PM UTC-5 tke...@gmail.com wrote:
> If the problem is in the weewx-Weather34 repo, it would be best to file an
> issue there.
>
> On Mon, Oct 31, 2022 at 2:02 PM Brian Dowling wrote:
>
>> Spotted what looked like a typo, no go. Cloned the repo
If the problem is in the weewx-Weather34 repo, it would be best to file an
issue there.
On Mon, Oct 31, 2022 at 2:02 PM Brian Dowling
wrote:
> Spotted what looked like a typo, no go. Cloned the repo, that didn't go
> real smooth (could be me, try again?).
>
> Please advise.
>
> --
> You received
Spotted what looked like a typo, no go. Cloned the repo, that didn't go
real smooth (could be me, try again?).
Please advise.
--
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
Built a new station using an esp32 which mqtt’s data every second to a
Raspi. A python program converts this to a txt file which I then file parse
into weewx. All ok.
I have successfully installed the steelseries gauges and the rtgd
extension. All works fine and it is fantastic to see the gauges
For some reason your copy of pip3 is using packages in the Python 2
library. Somehow it got broken. Perhaps it has the wrong shebang at the
top?
Try reinstalling it.
On Mon, Oct 31, 2022 at 12:03 PM Steve wrote:
> I did try @rpi3:/home/weewx/bin# sudo pip3 install cheetah3
>
> Traceback (most r
Thanks Vince.
I will update the OS when I get a chance, the Pi does a few other things
besides Weewx. But like you mentioned, unless I get it current, I'll be
battling stuff like this forever. I rolled back to v4.3.0 as I saved the
image before playing with it.
On Tuesday, 1 November 2022 at 0
I did try @rpi3:/home/weewx/bin# sudo pip3 install cheetah3
Traceback (most recent call last):
File "/usr/local/bin/pip3", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line
3019, in
@_call_aside
File "/usr
On Monday, October 31, 2022 at 10:29:34 AM UTC-7 Steve wrote:
> @rpi3:~# pip install Cheetah3
> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020.
> Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0
> will drop support for Python 2.7 in January 202
I can think of two reasons why this might be happening.
1. You are using a Python 2 version of pip, which will install packages in
the Python 2 directory hierarchy. If you then run weewxd using Python 3, it
won't find it.
I almost never invoke Python as "python", nor pip as "pip". Instead, use
th
Posted as a wiki article:
https://github.com/weewx/weewx/wiki/Run-WeeWX-in-a-virtual-environment
On Mon, Oct 31, 2022 at 10:25 AM Tom Keffer wrote:
> Unfortunately, as you discovered, this is a little tricky. If you run
> setup.py from the virtual environment, things end up in funny places.
>
>
Probably the wrong forum to ask, but I'm at my wits end. I've always used
the setup.py method to update WeeWx.
I updated WeeWX to 4.9.1 from maybe 4.3.0? Followed the setup.py
instructions (in /usr there are python3 and python3.5 directories).
I get an error in the log file "No module named 'Ch
Unfortunately, as you discovered, this is a little tricky. If you run
setup.py from the virtual environment, things end up in funny places.
Instead, use the system's python to set things up using setup.py, then
switch to the virtual environment to install dependencies, then run weewxd.
But, first
I'd like to be able to install weewx and run it using a virtual environment
instead of using the system's interpreter.
When I run "sudo setup.py install" I get an error
about not being able to use both prefix and exec_prefix.
I commented out exec_prefix= in setup.py.
The install runs but a bunc
16 matches
Mail list logo
