From 707ec7e43bac4870790d5a37cbb4bf87b6b0a726 Mon Sep 17 00:00:00 2001
From: Garth Vander Houwen <garthvh@yahoo.com>
Date: Wed, 31 Aug 2022 20:12:29 -0700
Subject: [PATCH] Start of MQTT 1.3 page

---
 docs/settings/moduleconfig/mqtt.mdx | 89 +++++++++++++++++++++++++++++
 1 file changed, 89 insertions(+)
 create mode 100644 docs/settings/moduleconfig/mqtt.mdx

diff --git a/docs/settings/moduleconfig/mqtt.mdx b/docs/settings/moduleconfig/mqtt.mdx
new file mode 100644
index 00000000..64a85414
--- /dev/null
+++ b/docs/settings/moduleconfig/mqtt.mdx
@@ -0,0 +1,89 @@
+---
+id: mqtt
+title: MQTT Module Configuration
+sidebar_label: MQTT
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+If your device is connected to WiFi you can enable it to forward packets along to an MQTT server. This allows users on the local mesh to communicate with users on the internet.
+
+The canned message module config options are: Enabled, Server Address, Username, Password and Encryption Enabled. MQTT Module config uses an admin message sending a `ConfigModule.MQTT` protobuf.
+
+## Settings
+
+ ## MQTT Module Config Values
+
+### Enabled
+
+Enables the MQTT module.
+
+### Server Address
+
+The server to use for MQTT. If not set, the default server public will be used.
+
+### Username
+
+MQTT Server username to use (most useful for a custom MQTT server). If using a custom server, this will be honoured even if empty. If using the default public server, this will only be honoured if set, otherwise the device will use the default username.
+
+### Password
+
+MQTT password to use (most useful for a custom MQTT server). If using a custom server, this will be honoured even if empty. If using the default server, this will only be honoured if set, otherwise the device will use the default password
+
+### Encryption Enabled
+
+Whether to send encrypted or decrypted packets to MQTT. This parameter is only honoured if you also set server (the default official mqtt.meshtastic.org server can handle encrypted packets) Decrypted packets may be useful for external systems that want to consume meshtastic packets.
+
+## MQTT Module Config Client Availability
+
+<Tabs
+groupId="settings"
+defaultValue="apple"
+values={[
+{label: 'Android', value: 'android'},
+{label: 'Apple', value: 'apple'},
+{label: 'CLI', value: 'cli'},
+{label: 'Flasher', value: 'flasher'},
+{label: 'Web', value: 'web'},
+]}>
+<TabItem value="android">
+
+:::info
+MQTT module config is not available for Android.
+:::
+
+</TabItem>
+<TabItem value="apple">
+
+:::info
+MQTT module config is not available for Apple.
+:::
+
+</TabItem>
+<TabItem value="cli">
+
+All MQTT module config options are available in the python CLI. Example commands are below:
+
+|     Setting                  |    Acceptable Values     | Default |
+| :--------------------------: | :----------------------: | :-----: |
+|    mqtt.enabled              |     `true`, `false`      | `false` |
+|    mqtt.address              |     `string`             |         |
+|    mqtt.username             |     `string`             |         |
+|    mqtt.password             |     `string`             |         |
+|    mqtt.encryption_enabled   |     `string`             |         |
+
+```shell title="Enable/Disable MQTT Module"
+meshtastic --set mqtt.enabled true
+meshtastic --set mqtt.enabled false
+```
+
+  </TabItem>
+  <TabItem value="web">
+
+:::info
+All MQTT module config options are available for the Web UI.
+:::
+    
+  </TabItem>
+</Tabs>
\ No newline at end of file