A Weewx service and driver that receives data from multiple MQTT topics.
Currently MQTT payloads of json, keyword (field1=value, field2=value..), and individual (each topic contains a single observation) are supported.
The driver captures the MQTT payload in a separate thread. Then in genLoopPackets, every element in the queue is turned into its own packet.
It is also possible to subscribe to a second topic. The MQTT payload from this topic is put into a separate queue. This queue is processed by the genArchiveRecords to create archive records (simulating hardware generation). With the combination of the two topics/queues, one can have a WeeWX instance gather the data and publish loop and archive data for other instances to receive.
When generating loop packets and the queue becomes empty, the option, wait_before_retry, controls how long before an attempt is made to get data from the queue.
The service can bind to either new loop packets or new archive records. In both cases a separate thread captures the MQTT payload and puts it on a queue. On new packets/records events, the main thread takes the elements from the queue and accumulates them into a single dictionary of data fields. If necessary, the data is converted to the units of the packet/record. The packet/record is then updated with the data.
The elements that are processed from the queue can be controlled by various configuration options. By default, if the MQTT datetime is less than the previous packet's datetime it is ignored. This check can be ignored by setting ignore_start_time to True. It can be controlled more granularly by setting adjust_start_time to the number of seconds prior to the previous packet's datetime is allowed. Also by default, when the MQTT datetime is greater than the packet's datetime, the pocessing of the queue for this packet stops. This check can be ignored by setting ignore_end_time to True. It can be controlled more granularly by setting adjust_end_time to the number of seconds after the packet's datetime is allowed to be processed.
To install version 2.x and prior see, Installing and Updating Version 2.X and Earlier.
To install version 3.x with WeeWX 4.x see, Installing and updating version 3.x with WeeWX 4.x
Note: It is rare that MQTTSubscribe should be configured to run as both a service and driver.
If you are augmenting an existing driver's data, run MQTTSubscribe as a service. Otherwise, run it as a driver.
Because there are multiple methods to install WeeWX V5, location of files can vary. See for the definitive information. The following symbolic names are used to define the various locations:
- $WEEWX_REPO - For git 'installs', the location of the repository (This is not typically in the WEEWX documentation)
- $WEEWX_ROOT - WeeWX root directory
- $BIN_ROOT - Executables
- $USER_ROOT - User directory
- $CONFIG_FILE - The WeeWX configuration file (This is not typically in the WEEWX documentation)
- $WEECTL - The
weectlprogram (This is not typically in the WEEWX documentation)
The notation vX.Y.Z designates the version of MQTTSubscribe being installed.
Prior to making any updates/changes, always make a backup.
- Python 3.7 or higher
- Paho MQTT Python client
Note, for package installs:
If you just installed WeeWX, you may need to create a new shell/terminal or logout/login
for the user that installed WeeWX to have permission to update WeeWX.
For more information see Understanding permissions
If running as a driver,
RUN_MODE=driver
If running as a service,
RUN_MODE=service
source ~/weewx-venv/bin/activate
WEEWX_ROOT=~/weewx-data
export USER_ROOT=$WEEWX_ROOT/bin/user
CONFIG_FILE=$WEEWX_ROOT/weewx.conf
WEECTL=weectl
WEEWX_ROOT=/etc/weewx/
export BIN_ROOT=/usr/share/weewx/
export USER_ROOT=$WEEWX_ROOT/bin/user
CONFIG_FILE=$WEEWX_ROOT/weewx.conf
WEECTL=weectl
WEEWX_REPO=~/weewx
WEEWX_ROOT=~/weewx-data
export BIN_ROOT=$WEEWX_REPO/src
export USER_ROOT=$WEEWX_ROOT/bin/user
CONFIG_FILE=$WEEWX_ROOT/weewx.conf
WEECTL=$WEEWX_REPO/bin/weectl
$WEECTL extension install https://github.com/bellrichm/WeeWX-MQTTSubscribe/archive/refs/tags/latest.zip
python3 $USER_ROOT/MQTTSubscribe.py configure --create-example mqttsubscribe.template.conf
Note, MQTTSubscribeDriver can also be configured and weewx.conf updated interactively via
weectl station.
Using weectl station a limited number of options that can be configured.
Edit the mqttsubscribe.template.conf file
For example,
```
nano mqttsubscribe.template.conf
```
```
python3 $USER_ROOT/MQTTSubscribe.py configure $RUN_MODE --validate --conf mqttsubscribe.template.conf
```
```
python3 $USER_ROOT/MQTTSubscribe.py simulate $RUN_MODE --conf mqttsubscribe.template.conf
```
Additional information on running MQTTSubscribe in configuration mode can be found at this wiki page.
Additional information on running MQTTSubscribe in simulation mode can be found at this wiki page.
$WEECTL station reconfigure --driver=user.MQTTSubscribe --no-prompt
python3 $USER_ROOT/MQTTSubscribe.py configure service --enable true --conf mqttsubscribe.template.conf
```
python3 $USER_ROOT/MQTTSubscribe.py configure $RUN_MODE --replace-with mqttsubscribe.template.conf --conf $CONFIG_FILE
```
-
Stop WeeWX
-
Validate and test the new against current configuration
python3 $USER_ROOT/MQTTSubscribe.py configure $RUN_MODE --validate --conf $CONFIG_FILEpython3 $USER_ROOT/MQTTSubscribe.py simulate $RUN_MODE --conf $CONFIG_FILE -
Restart WeeWX
-
Export the current configuration settings.
python3 $USER_ROOT/MQTTSubscribe.py configure $RUN_MODE --export mqttsubscribe.template.conf --conf $CONFIG_FILE -
Follow the diections to
-
Stop WeeWX
-
Restart WeeWX
See, debugging.
Feel free to open an issue, start a discussion in github, or post on WeeWX google group. When doing so, see Help! Posting to weewx user for information on capturing the log. And yes, capturing the log from WeeWX startup makes debugging much easeier.
