The server to use for our MQTT global message gateway feature. If not set, the default server will be used
If a meshtastic node is able to reach the internet it will normally attempt to gateway any channels that are marked as is_uplink_enabled or is_downlink_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
Whether to send / consume json packets on MQTT
If true, we will periodically report unencrypted information about our node to a map via MQTT
Optional
mapSettings for reporting information about our node to a map via MQTT
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
If true, we can use the connected phone / client to proxy messages to MQTT instead of a direct connection
The root topic to use for MQTT messages. Default is "msh". This is useful if you want to use a single MQTT server for multiple meshtastic networks and separate them via ACLs
If true, we attempt to establish a secure connection using TLS
MQTT 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 server, this will only be honoured if set, otherwise the device will use the default username
MQTT Client Config