From ca2365b6509d25e486b3bc0937b07d3739b7c10b Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Tue, 25 Jul 2023 20:57:58 +0200 Subject: [PATCH] MeshPacket is encapsulated in a ServiceEnvelope --- docs/software/mqtt/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/software/mqtt/index.mdx b/docs/software/mqtt/index.mdx index b3d8d3ed..70a88b25 100644 --- a/docs/software/mqtt/index.mdx +++ b/docs/software/mqtt/index.mdx @@ -17,7 +17,7 @@ You can find the settings available for MQTT [here](/docs/settings/moduleconfig/ Using or emitting packets directly in/from smart home control software such as Home Assistant or other consumers that can work with JSON messages. -When MQTT is enabled, the Meshtastic device simply uplinks and/or downlinks every raw protobuf packet that it sees to the MQTT broker. In addition, some packet types are serialized or deserialized from/to JSON messages for easier use in consumers. All packets are sent to the broker, whether they originate from another device on the mesh, or the gateway node itself. +When MQTT is enabled, the Meshtastic device simply uplinks and/or downlinks every raw protobuf MeshPacket that it sees to the MQTT broker, encapsulated in a [ServiceEnvelope protobuf](https://buf.build/meshtastic/protobufs/docs/main:meshtastic#meshtastic.ServiceEnvelope). In addition, some packet types are serialized or deserialized from/to JSON messages for easier use in consumers. All packets are sent to the broker, whether they originate from another device on the mesh, or the gateway node itself. Packets may be encrypted. If you use the default meshtastic MQTT server, packets are always encrypted. If you use a custom MQTT broker (ie set `mqtt.address`), the `mqtt.encryption_enabled` setting applies, which by default is false.