From 94a753c8970eea85b3395ac64cac07c8ac65ec2b Mon Sep 17 00:00:00 2001 From: Ian McEwen Date: Wed, 13 Mar 2024 17:52:46 -0700 Subject: [PATCH] Update MQTT docs for the topic containing 'e' --- docs/software/integrations/mqtt/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/software/integrations/mqtt/index.mdx b/docs/software/integrations/mqtt/index.mdx index 8bded5fe..0e6d398a 100644 --- a/docs/software/integrations/mqtt/index.mdx +++ b/docs/software/integrations/mqtt/index.mdx @@ -40,9 +40,9 @@ For each channel where uplink and/or downlink is enabled, two other topics might #### Protobufs topic A gateway node will uplink and/or downlink raw ([protobuf](https://developers.google.com/protocol-buffers)) MeshPackets to the topic: -`msh/2/c/CHANNELNAME/USERID`, where `CHANNELNAME` is the name of the channel. +`msh/2/e/CHANNELNAME/USERID`, where `CHANNELNAME` is the name of the channel (firmware versions prior to 2.3.0 will publish to a topic with `/c/` in the place of `/e/`). -For example: `msh/2/c/LongFast/!abcd1234` +For example: `msh/2/e/LongFast/!abcd1234` The payload is a raw protobuf, whose definitions for Meshtastic can be found [here](https://github.com/meshtastic/protobufs/blob/master/meshtastic). Reference guides for working with protobufs in several popular programming languages can be found [here](https://protobuf.dev/reference/). Looking at the MQTT traffic with a program like `mosquitto_sub` will tell you it's working, but you won't get much useful information out of it. For example: