Thank you so much for taking the time to look through the files and your suggestions. I have modified the [[MQTT]] stanza in [StdRESTful] - I understood that the Belchertown 'mqtt_websockets_topic' should match the StdRESTful entry - is that correct? I have been keeping them the same in my attempts so far, but I'll try both options.
Now to check out the ACL file and MQTT Explorer as well - presumably MQTT Explorer should be looking for 'weather/#' like the ACL file? I did use the Mathew Wall MQTT extension - presumably he only has one version, and I haven't missed another one? On Tuesday, 5 August 2025 at 16:50:32 UTC+10 [email protected] wrote: > Hello, > > I see one minor problem : in your weewx.conf file, the MQTT topic used by > weewx to publish its data should be weather and not weather/loop : > [[MQTT]] > server_url = mqtts://user:[email protected]:8883/ > <http://user:[email protected]:8883/> > *topic = weather* > The loop subtopic will be automatically created by the mqtt extension. > > Also check your mosquitto acl file to be sure that the mqtt user > configured in weewx.conf is allowed to publish data on the weather topic : > user XXXXX > topic readwrite weather/# > > Finally, some other users had similar problems because they were using a > weewx MQTT extension that was not creating the loop subtopic needed by the > Belchertown skin. . The extension to be used with Belchertown is this one : > https://github.com/matthewwall/weewx-mqtt/tree/master > Le lundi 4 août 2025 à 16:30:36 UTC+2, Peter Schmelitschek a écrit : > >> I apologise to the Gurus who will sigh 'not this again!" >> >> I have been working on getting WeeWx to work with Belchertown for several >> weeks and admit defeat. My head is spinning from days going in circles with >> ChatGPT on multiple related issues (TLS, MQTT over TCP yada yada). >> >> Summary of my setup that I feel is relevant: >> >> Local DNS record on Pi-Hole (with unbound) points broker ( >> mqtt.dreamwoodestate.net) to the Traefik IP. >> >> Mikrotik router has dst-nat pointing 8883 and 9011 to those ports on the >> Traefik VM. >> There are also Input rules to allow those ports. >> >> Cloudflare has a proxied A record for the broker, pointing to my static >> IP which resolves to my HomeLab domain (dreamwoodestate.net) >> >> Traefik (in own VM) supplies Letsencrypt certificate for use by browser >> wanting to securely access my website with Belchertown. >> >> MQTT broker (Mosquitto 2.0.18) is running on its own VM also. >> >> WeeWx also has its own VM. >> >> So far, MQTT Explorer on my LM PC can see the broker, SSYS, broker - and >> all the groups below broker. >> >> WeeWx appears to be outputting MQTT data, with rows like: >> DEBUG user.mqtt: data: {'dateTime': '1754316352.0', 'barometer_mbar'.... >> INFO weewx.restx: MQTT: Published record 2025-08-05 00:05:52 AEST >> (1754316352) >> >> However, MQTT Explorer is not displaying any 'weather' messages from the >> WeeWx MQTT client (I think this is the way to describe it). >> It is subscribed to topic=weather/loop >> >> BTW, I have chosen port '9011' for websockets as Portainer Agent is using >> '9001' traditionally used around WeeWx/MQTT >> >> weexw.log is empty - don't know if that is good or bad >> >> Browsing to my weather data is 'working' in all respects except for the >> MQTT driven 2 second updates (and that strange appearance of 'current temp' >> at the top of graphs and reports - minor problem I'm sure). >> Using '?debug=true' in browser shows 'MQTT: MQTT Connected. Subscribing.' >> as the last entry. >> >> Hopefully there are sufficient clues and suitable obfuscation in the >> attached. >> Please let me know what other info I can provide. >> >> -- 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/953199b0-3fa1-4739-95a2-882fa0e27707n%40googlegroups.com.
