ESP_DIAG_EVENT received and acknowledged by backend but event count remains 0 in Node Report UI

[steindlmedia]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

The event uploaded in the payload should appear in the Node Report events list, and the Events counter should reflect at least 1 event.

Actual behavior (suspected bug)

The Node Report page shows Events: 0. The event is not listed.

Payload evidence

The uploaded payload clearly contains the event:

{
  "events": [
    {
      "tag": "test",
      "av": "EV (6407) test: auth.ok expires_in=345599"
    }
  ]
}

Error logs or terminal output

Steps to reproduce the behavior

1. Flash firmware with esp_diag_event logging enabled. Confirm the event fires on the device.
2. Allow the node to upload a diagnostics payload to the ESP Insights backend.
3. Confirm the upload succeeds (HTTP 200 / backend acknowledgement).
4. Open the Node Report page.
5. Observe the Events counter and the events list.

Project release version

1.3.3

System architecture

other (details in Additional context)

Operating system

Linux

Operating system version

ESP32-C6

Shell

ZSH

Additional context

A node is successfully uploading diagnostics payloads that include an ESP_DIAG_EVENT entry (tag: test). The backend acknowledges receipt, and the event is present in the submitted JSON. However, the Node Report page in the ESP Insights dashboard shows Events: 0 for the same node and date. The event is never surfaced in the UI.

The upload path and event encoding are both confirmed working. The issue appears to be in the backend storage/indexing → dashboard rendering pipeline:

• ✓ Device is sending ESP_DIAG_EVENT correctly.
• ✓ Backend receives and acknowledges the payload.
• ✓ Event is present in the submitted JSON under traces.events.