Good morning,
Just an update: I was able to fix my problem.
I had mistakenly installed venv in a folder that was not a weewx folder.
So I installed the venv folder inside the weewx folder and activated venv
and then upgraded to 5.0 and then version 5.1. Now the upgrade worked .
BR Georg
Tom Ke
try "sudo ss -tupl" which should show which process is using port 1883
On Wednesday, August 7, 2024 at 7:49:16 PM UTC-7 M&M wrote:
> Thanks for looking into this for me. I feel like I've read a bunch of
> pages and that I'm really close to this. I've attached my weewx.conf,
> mosquitto.co
I have weewx-influx
(https://github.com/matthewwall/weewx-influx/tree/master) installed as well
as weewx-forecast (https://github.com/chaunceygardiner/weewx-forecast)
installed configured to use NWS. Both are working well, however i'm not
sure how to get the forecast data flowing into Influx fo
Looks like I have two mosquittos running on 1883 but they have the same
PID.
pi@raspberrypi:/etc/weewx/skins/Belchertown $ sudo ss -tupl
NetidState Recv-Q Send-Q Local
Address:Port Peer Address:PortProcess
udp UNCONN
(apologies for the long post below)
No - you have one process listening on two ports, which is correct.
I just did a full install to a clean pi4 it works for me. Here are the
config file snippets and some diagnostic information
Note - if you set log_success true in the MQTT section you can
Interesting. I changed log_success to true however my /var/log/weewx.log
file is empty.
On Thursday, August 8, 2024 at 11:12:37 PM UTC-4 vince wrote:
> (apologies for the long post below)
>
> No - you have one process listening on two ports, which is correct.
>
> I just did a full install to a
