Hi Vince, Did you have to do any customisation at all? I am using MQTTSubscribe and it is now working, but I had to write an external python script to subscribe to the Ecowitt topic, parse the payload and re-publish it in JSON format to another topic, which WeeWx then subscribes to.
Before I did that it was trying to convert the whole string (including &s) to a value, even in 'individual' mode. Cheers James On Friday, 25 July 2025 at 17:07:21 UTC+1 vince wrote: > Yes. You still will need the ecowitt gateway to publish to a MQTT broker > in the middle. I just run a little docker container on my LAN for that. > > In my case I have two weewx instances that both publish to MQTT as > ecowitt/loop and vp2/loop (via Matthew's MQTT extension, to later feed > influxdb), but the VP2 weewx instance subscribes to the ecowitt data (via > Rich's MQTTSubscribe as a service) to add data to a few extraTempNNN > elements so that I can show data from both in my main skin. > > Rich's MQTTSubscribe works great. I didn't know until now that it can be > run as a driver. Very cool. > > On Friday, July 25, 2025 at 7:17:20 AM UTC-7 Steeple Ian wrote: > >> @Michael >> I have not looked at MQTT in any depth before so forgive me if my >> question is naive. Using WeeWX-MQTTSubcribe with the Ecowitt MQTT protocol, >> is there still a requirement for a-man-in-the middle server? >> Thanks, >> Ian >> >> On Friday, July 25, 2025 at 2:33:52 PM UTC+1 [email protected] wrote: >> >>> Take a look into https://github.com/bellrichm/WeeWX-MQTTSubscribe >>> >>> James Pattinson schrieb am Freitag, 25. Juli 2025 um 13:57:21 UTC+2: >>> >>>> Hi All! >>>> >>>> I am setting up a WeeWx system in a remote location where they do have >>>> WiFi but nowhere to actually install the software. Since I have WeeWx >>>> running elsewhere, I'd like to be able to feed into a new instance of >>>> WeeWx >>>> under my control. >>>> >>>> I am used to using Davis stuff, but as these guys are on a budget, we >>>> went for EcoWitt. We have a WS69 with LCD display, and a GW3000. >>>> >>>> This is my first time using a GW3000, and I was quite happy to see that >>>> it supports MQTT so it can push data out in almost real time (down to 8 >>>> seconds). I have this working and I can see the updates coming into my >>>> MQTT >>>> server, albeit in a weird HTTP POST style: >>>> >>>> >>>> PASSKEY=xxx&stationtype=GW3000A_V1.0.9&runtime=1124&heap=68736&dateutc=2025-07-25%2011%3A50%3A12&dns_err_cnt=0&cdnflg=1&tempinf=74.12&humidityin=56&baromrelin=29.483&baromabsin=29.483&tempf=72.86&humidity=55&vpd=0.367&winddir=294&windspeedmph=0.00&windgustmph=0.00&maxdailygust=0.00&solarradiation=4.96&uv=0&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=0.000&yearlyrainin=0.000&wh65batt=0&freq=868M&model=GW3000A&interval=60 >>>> >>>> If there was a way of having this MQTT message feed directly into the >>>> LOOP of WeeWx, it would make my life SO much easier, as I can have the >>>> GW3000 publish this out to an external MQTT server and connect WeeWx to >>>> the >>>> same server. Has anyone got a WeeWx driver to do this? >>>> >>>> Without this, I think I am looking at the GW1000 API polling driver, >>>> which appears to have become unmaintained quite recently. For that to work >>>> I'd need to arrange things such that WeeWx can connect to the GW3000 over >>>> the Internet, which might be challenging without a VPN. >>>> >>>> Plan B is to tell them they need to buy a Pi or something and do it all >>>> locally, but I would really like to be able to get some semi real-time >>>> push >>>> method doing for this use case. >>>> >>>> Any other ideas would be appreciated! >>>> >>>> Cheers >>>> James >>>> >>> -- 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/68590d7a-3555-4f92-9c14-cf78d67c15c6n%40googlegroups.com.
