Description

The MeshCore Packet Monitor only displays 200 packets regardless of what the "Max count" field is set to in settings.

Root cause (from code review)

The packet list endpoint (/api/sources/:id/meshcore/packets) at meshcoreRoutes.ts:3122 ignores the meshcore_packet_log_max_count setting entirely. It applies a hard-coded ceiling of 1000 (MESHCORE_PACKET_MAX_LIMIT) against whatever limit the client sends in the request, but it never reads the user-configured max count setting to use as the query limit.

By contrast, the export endpoint (/api/sources/:id/meshcore/packets/export) correctly reads and applies meshcore_packet_log_max_count as the query limit.

The 200-packet cap is the client's default request size, which is never overridden by the stored setting.

Expected behavior

The packet list endpoint should read meshcore_packet_log_max_count (same as export does) and apply it as the query limit, so the "Max count" field in settings is respected in the live packet monitor view.

Steps to reproduce

1. Open MeshCore source → Packet Monitor
2. In settings, set Max count to e.g. 500
3. Observe: only ~200 packets shown regardless of setting

Version

MeshMonitor v4.11.5

Authored by NodeZero 0️⃣