Problem on uplink devices

Viewed 18

Good evening,
We use a V3 server and for a few days we have been noticing an anomalous situation.
For about 20 days we have been witnessing a loss of uplink of various devices.
The devices are configured to send measured values daily.

We are a company that uses "sontex, zenner, bmeters" devices for heat and water metering.
Our infrastructure includes a Linux server:

  • Ubuntu 22.04.5 LTS.
  • Gateway milesight ug63 and 65 whit 1nce sim.
    Currently, approximately 20,000 devices are registered on the server.

I'm afraid that redis will reject the keys even if they are still active from the web portal (DeviceAddress populated)

Is there a method to test if the message is rejected by the server or if the problem is infrastructure?
What information do you need to get help?

Thank you

1 Answers

Things you can try:

  • Inspect the logs for errors
  • Inspect if there is a difference in messages received through your gateways vs messages handled. E.g. ChirpStack will show all uplinks on the gateway page, but it will only show uplinks on the device page when the session-keys are matching.
  • If you think the issue is with ChirpStack, then you can look at the number of MQTT messages published by your gateways vs messages handled by ChirpStack.

Just to let you know, ChirpStack v3 is very outdated and I would recommend upgrading to ChirpStack v4.