From f090db3d333c552b19ec93c4852f04ffb835a9a4 Mon Sep 17 00:00:00 2001 From: Jeremiah K <17190268+jeremiah-k@users.noreply.github.com> Date: Wed, 11 Jan 2023 01:01:00 -0600 Subject: [PATCH] Update index.mdx Fix two typos. MQQT -> MQTT --- docs/software/mqtt/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/software/mqtt/index.mdx b/docs/software/mqtt/index.mdx index b6042410..450d2f83 100644 --- a/docs/software/mqtt/index.mdx +++ b/docs/software/mqtt/index.mdx @@ -252,7 +252,7 @@ meshtastic --ch-index 0 --ch-set downlink_enabled true Step two: if you don't want to depend on JSON decoding on the device, you can decode the protobuf messages off-device. To do that you will need to get the .proto files from https://github.com/meshtastic/protobufs. They function as a schema and are required for decoding in Node-RED. Save the files where the node-RED application can access them and note the file path of the "mqtt.proto" file. -Step three: install Node-RED plug-ins to your node-RED application for an embedded MQQT server and a protobuf decoder. +Step three: install Node-RED plug-ins to your node-RED application for an embedded MQTT server and a protobuf decoder. https://flows.nodered.org/node/node-red-contrib-aedes https://flows.nodered.org/node/node-red-contrib-protobuf @@ -264,7 +264,7 @@ Drag, drop, and wire the nodes like this. For this example, I ran node-RED on a The aedes broker must be set up on the same flow as the other nodes. By activating the Publish debug node, you can see all the published messages. [](/documents/mqtt/Broker1.jpg) -Receiving a json mqqt message is very simple. +Receiving a json mqtt message is very simple. [](/documents/mqtt/Consume.jpg) Injecting a json message to be sent by a device is also very simple. You do need the correct envelope. [](/documents/mqtt/Inject.jpg)