Skip to content

Commit 9baf48b

Browse files
authored
Merge pull request #782 from 3735943886/patch-1
Rearrange placement of the encoding argument description in documenta…
2 parents 41b543b + 6ec01d8 commit 9baf48b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/reference.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -816,9 +816,6 @@ An optional ``str_expr`` can be used to match the MQTT message data, and the tri
816816
if that expression evaluates to ``True`` or non-zero. This expression has available these
817817
variables:
818818

819-
An optional ``encoding`` argument specifies the character encoding used to decode the MQTT payload
820-
(default is **"utf-8"**). It can be explicitly set to other encodings if necessary.
821-
822819
- ``trigger_type`` is set to "mqtt".
823820
- ``topic`` is set to the topic the message was received on.
824821
- ``qos`` is set to the message QoS.
@@ -828,6 +825,9 @@ An optional ``encoding`` argument specifies the character encoding used to decod
828825
required function argument an exception will be thrown, use payload_obj=None.
829826
- ``retain`` is set to the message retain flag. True if the message was retained, False otherwise.
830827

828+
An optional ``encoding`` argument specifies the character encoding used to decode the MQTT payload
829+
(default is **"utf-8"**). It can be explicitly set to other encodings if necessary.
830+
831831
When the ``@mqtt_trigger`` occurs, those same variables are passed as keyword arguments to the
832832
function in case it needs them. Additional keyword parameters can be specified by setting the
833833
optional ``kwargs`` argument to a ``dict`` with the keywords and values.

0 commit comments

Comments
 (0)