On Wednesday, August 7, 2019 at 8:11:01 AM UTC-5, mwall wrote:
>
>
> hello scott,
>
> please post the complete driver here. i will do the diffs and merge it.
>
>
Matthew, was there anything else you needed from me? I posted the driver
to the list back in Sept...?
Thanks,
Scott
--
You
I am setting up a test station with WeeWx version 4 on a Rpi. I have three
sensors publishing MQTT and I want to test the wxMesh driver. Can this be
run as a service with the Simulator driver running?
Thanks, Ralph
--
You received this message because you are subscribed to the Google Groups
I was replying to a post on an earlier page. I just found Rich's
MQTTSubscribe.py and have started to experiment with it as a service.
I managed to get to this:
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL weewx.engine: Caught
unrecoverable exception:
Jan 14 11:23:16 TestPi weewx[4983] CRITICAL
Ralph,
What version of WeeWX and MQTTSubscribe? Did you install via wee_extension?
If you post a copy of your config (making sure to remove any sensitive
information), I’d be happy to take a look.
We should probably move this out of the wxMesh thread...
Rich
On Tuesday, 14 January 2020 14:48:03
I am using WeeWx 4.0.0.b8 (latest development version) and I copied
MQTTSubscribe from your GitHub. I did not install via wee_extension.
My plan was to replace my standalone python program which subscribes to
MQTT and writes a file for the filepile.py extension. I converted it to
Python3 so
I have been working on getting *MQTTSubscribe* working on my development
station (RPi3 with Buster) running WeeWx 4.0.0.b8. I think I have managed
to get Python3 versions of all of the prerequisites for WeeWx and
MQTTSubscribe. I am using the Simulator as the driver, MQTTSubscribe as a
Ralph,
My first guess is that it doesn’t like the comma in the config for the
delimiter. This is based on this line the log.
Jan 14 15:39:40 TestPi weewx[5256] INFO user.MQTTSubscribe: Message
callback config is {'type': 'keyword', 'keyword_delimiter': [],
'keyword_separator': ':', 'label_map':
Great news!
Your memory is correct. But, in this case I am logging the exact payload -
before I decode it when running under python 3.
Since you are getting data, I will assume all is good until I hear
otherwise. And thank you for taking the leap and giving this a try.
Rich
On Tuesday, 14
Or since a comma is the default, comment it out for now.
Rich
On Tuesday, 14 January 2020 19:37:56 UTC-5, Rich Bell wrote:
>
> Ralph,
> My first guess is that it doesn’t like the comma in the config for the
> delimiter. This is based on this line the log.
> Jan 14 15:39:40 TestPi weewx[5256]
