On 29/08/2025 16:27, vince wrote:
Yep I reoroganized everything into categories. Just start at my name
and you will see a pinned repo called weewx. It’s in the list of stuff
in there
On Friday, August 29, 2025 at 7:38:25 AM UTC-7 Mark Fraser wrote:
Vince,
I've just started following this thread as I'm also having MQTT
issues.
My old installation of Weewx 4.10.2 on Buster is running OK and
MQTT is working. I've had to create a new installation on a
different Pi running Bookworm and Weewx 5.1.0 as the USB stick is
failing and going through the same process that worked previously
isn't working.
All I get when running
mosquitto_sub -d -t weather/# -h 192.168.2.108
on a different device is:
Client mosqsub|15572-weather sending CONNECT
Client mosqsub|15572-weather received CONNACK (0)
Client mosqsub|15572-weather sending SUBSCRIBE (Mid: 1, Topic:
weather/#, QoS: 0)
Client mosqsub|15572-weather received SUBACK
Subscribed (mid: 1): 0
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
Client mosqsub|15572-weather sending PINGREQ
Client mosqsub|15572-weather received PINGRESP
In the message below the URL doesn't work, have you renamed your
github repo?
https://github.com/vinceskahan/weewx/blob/main/weewx-odds-and-ends/weewx-belchertown-websockets.txt
On Wednesday, 6 August 2025 at 01:13:34 UTC+1 Peter Schmelitschek
wrote:
Thanks Vince.
Good idea.
On Wednesday, 6 August 2025 at 03:43:17 UTC+10 vince wrote:
Your setup is very complicated - Traefik, Cloudflare,
Portainer, etc. etc. etc. plus trying to get
weewx/mosquitto working to begin with.
FWIW, my working LAN only setup is at
https://github.com/vinceskahan/weewx-odds-and-ends/blob/master/weewx-belchertown-websockets.txt
if you want to take a look at settings that used to work
here. I'm LAN-only, no proxies, ssl disabled, user/pass
disabled so it's the simplest setup that should work
LAN-only.
My hazy recollection is that you also need to be
consistent between http/https, and ssl enabled/disabled,
but with all the complicated things you're trying to
align, wow.....
I would suggest you start over, step by step, doing one
thing at a time as you build up the complexity....
* get everything working LAN-only 'without' SSL
* then get it working LAN-only with SSL
* then get it working proxied without SSL
* then lastly get it working proxied with SSL
or....
* LAN-only without SSL
* proxied without SSL
* proxied with SSL
Or the like. Tiny steps. Minimize moving parts. Build
up to the (to me) messy setup you're trying to build.
I managed to fix my issue and was it my own mistake. I'd commented out
the restful_services line trying to fix something else which of course
meant that user.mqtt.MQTT would never run!
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/6938811f-4002-4ba9-8b48-b047a6dceaa9%40gmail.com.
