MQTT Notifications

Overview

• Source: https://mqtt.org/
• Image Support: No
• Attachment Support: No
• Message Character Limits:
  • Body: 32768

Account Setup

MQTT Support requires paho-mqtt (a version less then v2) to work:

pip install "paho-mqtt<2.0"

Syntax

Valid syntax is as follows:

• mqtt://{host}/{topic}
• mqtt://{host}:{port}/{topic}
• mqtt://{user}@{host}:{port}/{topic}
• mqtt://{user}:{password}@{host}:{port}/{topic}

For a secure connection, just use mqtts instead.

• mqtts://{host}/{topic}
• mqtts://{host}:{port}/{topic}
• mqtts://{user}@{host}:{port}/{topic}
• mqtts://{user}:{password}@{host}:{port}/{topic}

Secure connections should be referenced using mqtts:// where as insecure connections should be referenced via mqtt://.

Parameter Breakdown

Variable	Required	Description
user	no	The user associated with your MQTT server.
password	no	The password associated with your MQTT server.
hostname	Yes	The MQTT server you’re sending your notification to.
port	No	The port the MQTT server is listening on. By default the port is 1883 for mqtt:// and 8883 for all mqtts:// references.
qos	No	The MQTT Quality of Service (Qos) setting. By default this is set to 0 (zero).
version	No	The MQTT Protocol Version to use. By default this is set to v3.1.1. The other possible values are v3.1 and v5.
client_id	No	The MQTT client identifier to use when establishing a connection with the server. By default this is not set and a unique ID is generated per message.
session	No	The MQTT session to maintain (associated with the client_id). If no client_id is specified, then this value is not considered. By default there is no session established and each connection made by apprise is unique. If you wish to enforce a session (associated with a provided client_id) then set this value to True.
retain	No	The MQTT publisher retain flag. By default this is set to no, but you may optionally over-ride it and set it to yes

Global Parameters

Variable	Description
overflow	This parameter can be set to either split, truncate, or upstream. This determines how Apprise delivers the message you pass it. By default this is set to upstream 👉 upstream: Do nothing at all; pass the message exactly as you received it to the service. 👉 truncate: Ensure that the message will fit within the service’s documented upstream message limit. If more information was passed then the defined limit, the overhead information is truncated. 👉 split: similar to truncate except if the message doesn’t fit within the service’s documented upstream message limit, it is split into smaller chunks and they are all delivered sequentially there-after.
format	This parameter can be set to either text, html, or markdown. Some services support the ability to post content by several different means. The default of this varies (it can be one of the 3 mentioned at any time depending on which service you choose). You can optionally force this setting to stray from the defaults if you wish. If the service doesn’t support different types of transmission formats, then this field is ignored.
verify	External requests made to secure locations (such as through the use of https) will have certificates associated with them. By default, Apprise will verify that these certificates are valid; if they are not then no notification will be sent to the source. In some occasions, a user might not have a certificate authority to verify the key against or they trust the source; in this case you will want to set this flag to no. By default it is set to yes.
cto	This stands for Socket Connect Timeout. This is the number of seconds Requests will wait for your client to establish a connection to a remote machine (corresponding to the connect()) call on the socket. The default value is 4.0 seconds.
rto	This stands for Socket Read Timeout. This is the number of seconds the client will wait for the server to send a response. The default value is 4.0 seconds.
emojis	Enable Emoji support (such as providing :+1: would translate to 👍). By default this is set to no. Note: Depending on server side settings, the administrator has the power to disable emoji support at a global level; but default this is not the case.
tz	Identify the IANA Time Zone Database you wish to operate as. By default this is detected based on the configuration the server hosting Apprise is running on. You can set this to things like America/Toronto, or any other properly formated Timezone describing your area.

Examples

# Assuming we're just running an MQTT Server locally on your box
# Assuming we want to post our message to the topic: `my/topic`
apprise -vvv -b "whatever-payload-want" "mqtt://localhost/my/topic"

Testing

I did the following to test this service locally (using docker):

# Pull in Mosquitto (v2.x at the time) - 2021 Sept 16th
docker pull eclipse-mosquitto

# Set up a spot for our configuration
mkdir mosquitto
cd mosquitto
cat << _EOF > mosquitto.conf
persistence false
allow_anonymous true
connection_messages true
log_type all
listener 1883
_EOF

# Now spin up an instance (we can Ctrl-C out of when we're done):
docker run --name mosquitto -p 1883:1883 \
   --rm -v $(pwd)/mosquitto.conf:/mosquitto/config/mosquitto.conf \
   eclipse-mosquitto

# All apprise testing can be done against this systems IP such as:
apprise -vvv -b "my=payload" "mqtt://localhost/a/simple/topic"

# Here is an example where the 'retain' flag is set:
apprise -vvv -b "my=payload" "mqtt://localhost/a/simple/topic?retain=yes"