---
title: "MQTT (Netmore New)"
slug: "mqtt-netmore"
updated: 2024-12-19T08:20:15Z
published: 2024-12-19T08:20:15Z
canonical: "docs.connect.netmoregroup.com/mqtt-netmore"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connect.netmoregroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Export - MQTT (Netmore)

The following article describes how to connect and use Netmore's MQTT broker.

## Configuration

![](https://cdn.document360.io/58c1b868-b36b-492e-aea3-32180613f31f/Images/Documentation/Screenshot 2024-07-05 081033.png)

Change this value to from *Disabled* to *Netmore MQTT*.

You will notice there are some variations on this option. The raw payload is always included in the export, but the metadata varies. See [Export Format](/lora-portal/docs/export-format) to decide what fits you best, but in general no need to send more data than needed.

![](https://cdn.document360.io/58c1b868-b36b-492e-aea3-32180613f31f/Images/Documentation/image(3).png)

## Connect

**URL**: mqtts://mq.netmoregroup.com:8883 **ClientID**: user1-example

- The client must authenticate with a valid LoRaWAN Portal login. If you experience authentication issues, just try logging in in the portal first.
- SSL Protocol can be any of TLSv1.2 or TLSv1.3.
- The Client ID must be unique and should have the format <username>-<whatever you like>. The format is currently not enforced, but will be in the future. Reusing the client ID from another active client will steal the link.
- Durable subscribers have 2 hours to pick up their messages before they are discarded.
- Maximum QoS is 1.

## Default Sensor Topic structure

Sensor data is pushed using the topic described below. The topic is always in lower case.

The topic format has this format:

sensor/<service_provider>/<customer>/payload sensor/<service_provider>/<customer>/downlink-response

If no customer is set for a sensor, the value for customer in the topic name will be set to “unknown”:

sensor/<service_provider>/unknown/payload sensor/<service_provider>/unknown/downlink-response

When subscribing you may want to use wildcards like this:

sensor/<service_provider>/+/payload sensor/<service_provider>/# sensor/+/<customer>/#

## Extended Format Topic Structure

The topic format has this format:

sensor/<service_provider>/<customer>/<sensor_type>/payload sensor/<service_provider>/<customer>/<sensor_type>/downlink-response

if sensortype is OTHER then the topic sensor_type part will be:

sensor/<service_provider>/<customer>/<class>_<activation_method>/payload sensor/<service_provider>/<customer>/<class>_<activation_method>/downlink-response

See [Export Format - Sensor Data](/lora-portal/docs/export-format) how the received data will look like.

## Gateway Topic structure

If you are Network Provider you may also subscribe to get changes of your gateways. No configuration is needed in the portal.

The topic format has this format:

gateway/<network_provider>/change

When subscribing you may want to use wildcards like this:

gateway/<network_provider>/+ gateway/<network_provider>/#

See [Export Format - Gateway Change](/lora-portal/docs/export-format-gateway-change) how the received data will look like.