Hello Michael, Many thanks - all a bit above my pay grade, I am afraid so excuse any silly questions.
When you say there is a client running in the browser, is this something I need to install (I haven't), or would it be there already, I am assuming the latter. Regarding your comment about the no-go with the WAN site, is this fixable with a public broker or just not at all? I've run some tests and updated that document here <https://docmost.thecobwebs.uk/s/weewx/p/enable-live-data-8Zo6w86w7W#ozrzxcvfwnpq> . Thanks again, Nick. On Friday, February 6, 2026 at 5:46:05 PM UTC [email protected] wrote: > The live updates are receive by a MQTT client in the browser. You need to > set up WeeWX to publish your live data to a MQTT broker, which you can > connect to from: > > a) WeeWX for publishing > b) The client running in the Browser for subscribing > > You also need to be aware that modern browsers block connectung to > insecure MQTT from secure (https) sites. > > A quick glance on your documentation let's me guess you're not too far > away from getting live updates when you browse your site from the same > network your WeeWX machine and your MQTT broker is running. > > It should be possible to browse the page from your 192.168.1.x client at > htttp://192.168.1.{weewx-machine}/weewx/belchertown with live updates. > > What's not going to work is https://mydomain.co/weewx/belchertown with > live updates. > > Check: > - WeeWX logs for MQTT related messages > - mosquitto logs if WeeWX is connecting to the broker > - mosquitto logs if the mqtt client in the browser is connecting to the > broker (will only work locally) > - the browser's console for error/info messages. > > Getting everything to work with https://mydomain.co/weewx/belchertown is > another topic, you might want to get yourself an account for a public > broker or setup the cloudflare tunnel for MQTT (I tried once but failed, so > tell me what you did if you'll succeed). > > > > O S schrieb am Freitag, 6. Februar 2026 um 18:05:43 UTC+1: > >> Hello all, >> >> I have resisted installing and configuring MQTT for live data in case I >> totally mess things up, but, in a fit of positivity, I decided to have a go >> today, and it doesn't work. >> >> I've used a mix of search engine (AI) advice, this post >> <https://www.wxforum.net/index.php?topic=43377.0;wap> and the >> instructions on the Belchertown skin page >> <https://github.com/poblabs/weewx-belchertown?tab=readme-ov-file#mqtt-and-mqtt-websockets-optional> >> . >> >> I have documented what I did >> <https://docmost.thecobwebs.uk/share/moessylnhf/p/enable-live-data-8Zo6w86w7W>, >> >> and my settings, can someone take a look and see if anything is glaringly >> wrong? >> >> For information, I am running this locally at http://192.168... and >> publicly through https://mydomain.co/weewx/belchertown using a >> cloudflared tunnel. >> >> Live updates don't appear to be happening in either scenario though >> (local or via https), ultimately, I'd like them working ion the public site >> (if it needs to be one or the other). >> >> Thank you, >> Nick. >> > -- 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/bb5af216-0094-423e-b9b2-4217a2be5849n%40googlegroups.com.
