Mqtt integration don't send all events

Applications
1

I have 4 devices conected on a gateway.
They are comunicating with my Chirpstark , but the MQTT integrations don’t send all events.

One device is set to send information every 5 minutes, the chirpstack receive the UP event, but he don’t send all mensages through MQTT, something like every 4 or 5 events.

I need to get all events through MQTT

I’m using the MQTT integration.

My chirpstack.toml file :

[integration]
enabled=[“mqtt”]

MQTT integration configuration.

[integration.mqtt]

# Event topic template.
event_topic="application/{{application_id}}/device/{{dev_eui}}/event/{{event}}"

# Command topic.
#
# This is the topic on which the MQTT subscribes for receiving (enqueue) commands.
command_topic="application/{{application_id}}/device/{{dev_eui}}/command/{{command}}"

# Use JSON encoding instead of Protobuf (binary).
json=true

# MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
server="tcp://{MY-SERVER}:1883"

# Connect with the given username (optional)
username="test"

# Connect with the given password (optional)
password="123"

# Quality of service level
#
# 0: at most once
# 1: at least once
# 2: exactly once
#
# Note: an increase of this value will decrease the performance.
# For more information: https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels
qos=0

# Clean session
#
# Set the "clean session" flag in the connect message when this client
# connects to an MQTT broker. By setting this flag you are indicating
# that no messages saved by the broker for this client should be delivered.
clean_session=false

# Client ID
#
# Set the client id to be used by this client when connecting to the MQTT
# broker. A client id must be no longer than 23 characters. If left blank,
# a random id will be generated by ChirpStack.
client_id=""

# CA certificate file (optional)
#
# Use this when setting up a secure connection (when server uses ssl://...)
# but the certificate used by the server is not trusted by any CA certificate
# on the server (e.g. when self generated).
ca_cert=""

# TLS certificate file (optional)
tls_cert=""

# TLS key file (optional)
tls_key=""
2

Hi @Gregorio_G_Lombardi ,

Could you please describe how you are testing that not all messages are transmitted to MQTT?

I guess you are subscribed somehow to topic application/… In MQTT broker.

You should check that messages published on that topics are the same as Uplinks received on devices Live Data tab.

Regards

3

Yes, I checked on the Live Data tab and they dont match.

I’m saving and logging all MQTT messages recived on ‘application/#’ topic.
and they don’t match with Chirpstack events on the plataform.

The plataform recives each 5 minutes, but the MQTT topic application/# dosen’t.