User norecord has made changes to wxMesh so that it should work with
python 3 and weewx 4.x. I have merged in their changes and pushed it to the
master branch.
I've also changed my implementation so that the data is in JSON format.
I'll likely push that up too, but need to make the switch to
Sorry for the late reply. I don't have much time to work on my original
wxMesh driver.
>From what I have seen of MQTTSubscribe, it's a much more complete
implementation of an MQTT subscriber, and offers the features I was
planning on adding some day. When I get a chance, I plan on switching
Great to hear. Just give a shout if you run into any other difficulties.
rich
On Wednesday, 24 June 2020 16:50:26 UTC-4, Christian Peters wrote:
>
> Hi Rich,
>
> thank you very much.
> It works like a charm! :-)
>
> I set up a temporary mapping to values already available in the databae.
> For
I should say that in the first test, I saw the disconnect and reconnect and
processing pick back up.
I did a couple more tests. First, just stop publishing. No disconnect,
MQTTSubscribe waited until the next message. No surprise there. Next I shut
the broker down. Again, I saw MQTTSubscribe
Hi Rich,
thank you very much.
It works like a charm! :-)
I set up a temporary mapping to values already available in the databae.
For the temp and humid values it works out of the box, for CPM, CPS and
radiation I have to setup unit groups later.
This is my working setup - just to have
Christian,
What are the symptoms that cause you to have to restart WeeWX when MQTT
connection is lost with wxmesh? The reason I ask, I tried just
disconnection the MQTTSubscribe client from the network and then
reconnecting. It seemed to behave correctly. I am hesitant to stop the
broker, but
Well, I haven't heard of having to restart WeeWX when the connection is
lost, and if that happens I would certainly want to look into fixing that.
I'll do some experiments to see if I can recreate.
Sounds like picking the service might be the best long term choice, with
the caveat about the
Rich,
that's great. I'm not sure whether I should stay on the driver version or
switch to the service versionwhich could make it maybe more easy.
But if the MQTTSubscribe as service lost connection and wouldn't reconnect
I have to restart the main weewx prog to get it up again!? So maybe a
Christian,
MQTTSubscribe should be able to meet your needs. I know the documentation
is a bit sparse, but I can help get you up and running.
The first question you need to answer is whether to run as a service or
driver? From what I am understanding. If you ran as a driver it would
