InfluxDB v2 Integration Silently Stops Writing

Environment

• ChirpStack Version: 4.12
• InfluxDB Version: v2
• Integration: InfluxDB v2 (enabled at application level)
• Device Type: LoRaWAN water meter (daily transmissions)
• Device EUI: 8cf957200016a072

Problem Summary

We are looking at a device that stopped writing data to InfluxDB after October 16, 2025 at 17:46:17 UTC, despite:

• The device continuing to send uplinks successfully
• ChirpStack receiving and processing the uplinks normally

Observations from Logs

Last Successful Write (October 16, 2025 17:46:17 UTC)

The device had one successful uplink with the following log entry:

2025-10-16T17:46:17.409100Z  INFO chirpstack::integration::influxdb: Uplink measurements sent to InfluxDB dev_eui=8cf957200016a072

However, this uplink also generated a warning:

2025-10-16T17:46:17.396365Z  WARN chirpstack::maccommand: Handle mac-command error dev_eui=8cf957200016a072 cid=LinkADRAns error=Expected pending LinkADRReq mac-command

Next Uplink (October 23, 2025 17:46:27 UTC - 7 days later)

The device sent another uplink exactly 7 days later, which ChirpStack processed normally:

• ✅ Uplink received and decoded
• ✅ Metrics saved to Redis (instantaneous_flow_m3ph, reverse_cumulative_flow_m3, positive_cumulative_flow_m3)
• ✅ MQTT integration published event to topic
• ✅ Downlink frame sent (LinkADRReq)
• ❌ NO "Uplink measurements sent to InfluxDB" log entry

InfluxDB Evidence

Direct inspection of InfluxDB logs shows:

• Zero write attempts (POST /api/v2/write) for this device after October 16th
• Only query operations (POST /api/v2/query) for reading existing data
• Two write errors from ChirpStack on October 24th (different time, likely different device):

  status_code=400 error=invalid error_code=invalid
  

Key Details from CSV Analysis

The attached CSV shows the complete log sequence for both uplinks:

October 16 uplink (lines 5-118):

• MAC command warning present
• Full metrics processing chain executed
• InfluxDB write logged successfully

October 23 uplink (lines 119-266):

• No MAC command warnings
• Full metrics processing chain executed
• MQTT event published
• InfluxDB write NOT logged (silent failure)

What We've Verified

1. ✅ Device is transmitting regularly (7-day interval)
2. ✅ ChirpStack receives and processes uplinks
3. ✅ Payload decoder executes (metrics are saved to Redis)
4. ✅ InfluxDB integration is enabled for the application
5. ✅ InfluxDB is running and accepting queries
6. ✅ Other devices in same application write successfully
7. ❌ This specific device stopped writing with no error logs

Additional Context

• ChirpStack service restarted on October 23rd at 18:18 UTC (after the 17:46 uplink)
• InfluxDB has been running continuously since September 25th
• The device's last successful data point in InfluxDB shows positive_cumulative_flow_m3 = 0.752 on October 16th at 18:00 UTC
• All subsequent uplinks are processed by ChirpStack but never reach InfluxDB

Attached: Complete log CSV showing both uplinks with timestamps and all processing steps for the above device.
https://limewire.com/d/fQ3Ft#pA0zMNZTkU

just captured errors for multiple devices
https://limewire.com/d/qNO6p#fxkpaJZn6z

all of them show the same behaviour I can see the measurements in chirsptack UI (redis) but not in influxdb