multiple mqtt publishers and subscribers, wiki is confusing

[Greg Troxel]

I just realized there are two (at least) mqtt publishers:

https://github.com/weewx-mqtt/publish
https://github.com/matthewwall/weewx-mqtt

and my current belief is that these are totally independent efforts. I
tend to want this more than many, but it would be nice if each README
mentioned the other and stated that it was or was not related to or
derived from that other.

There are also two mqtt subscribers:

https://github.com/morrowwm/weewxMQTT
https://github.com/weewx-mqtt/subscribe

and these also seem independent.


At

https://github.com/weewx/weewx/wiki/

both subscribers are listed.

Under "uploaders" there is just "mqtt" and it's a link to the wiki:

https://github.com/weewx/weewx/wiki/mqtt

which is only about mwall's version.

[bell...@gmail.com]

Greg,
Not exactly sure what you are looking for. But here is some background from my perspective.

https://github.com/morrowwm/weewxMQTT and https://github.com/weewx-mqtt/subscribe were released at about the same time. At the time weewxMQTT was only a driver, so I added  mqttsubscribe to the wiki. Not sure how weewxMQTT has evolved.

https://github.com/weewx-mqtt/publish came to being because some MQTT client I was experimenting with had very specific data format requirements.  I started with a pull request to https://github.com/matthewwall/weewx-mqtt, but it was evolving to something that as I as repo owner would not want to accept. So, I decided to write an extension from scratch that served my needs. Since it seemed to replicate an existing WeeWX extension, I decided not to add it to the wiki.

[Vince Skahan]

On Monday, February 16, 2026 at 4:49:08 PM UTC-8 bell...@gmail.com wrote:

Since it seemed to replicate an existing WeeWX extension, I decided not to add it to the wiki.

I dunno - there are lots of places where there are multiple ways to do something (skins, drivers, etc.) and it 'is' nice to have a good current list in the wiki for one-stop-shopping...

Personally I'd recommend adding links for both your pub/sub extensions to the wiki as other options for folks since yours are in active development.  It's nice yours are named differently so folks will easily tell them apart.

[Greg Troxel]

Vince Skahan <vince...@gmail.com> writes:

> I dunno - there are lots of places where there are multiple ways to do
> something (skins, drivers, etc.) and it 'is' nice to have a good current
> list in the wiki for one-stop-shopping...
>
> Personally I'd recommend adding links for both your pub/sub extensions to
> the wiki as other options for folks since yours are in active development.
> It's nice yours are named differently so folks will easily tell them apart.

I just added a link to MQTTPublish (calling it to be parallel to the
existing link to MQTTSubscribe aka weewx-mqtt/subscribe).

I'm unclear on if https://github.com/morrowwm/weewxMQTT can be a service
or only a driver, but I've asked in the repo.

I think all mqtt driver/service/uploader/extension things I know about
are in the wiki.


This has been useful; I had no idea there was a 2nd publisher
implementation until this week.