Skip to content

[BUG] Error fetching telemetry: SqliteError: no such column: source_id #2631

Description

@paulo-serrao

Describe the bug
After a fresh Baremetal install, I get this error when opening any page with telemetry graphs

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Device Information & Configuration'
  2. Scroll down to 'Local Node Telemetry'
  3. See error: "Error: Failed to fetch telemetry: 500 Internal Server Error"

Expected behavior
See the telemetry graphs

Screenshots
https://i.postimg.cc/Hkx9PJPg/Screenshot.png

Environment (please complete the following information):

  • Host OS: [Linux (Raspberry PI)]
  • Deployment type: Baremetal
    • NPM commit a964e40 (HEAD -> main, origin/main, origin/HEAD)
  • Database backend: SQLite
  • Node type: Heltec V3
  • Node Connection Type: Wifi

Additional context
[ERROR] Error fetching telemetry: SqliteError: no such column: source_id at Database.prepare (/home/pi/meshmonitor/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) at DatabaseService.getTelemetryByNodeAveraged (file:///home/pi/meshmonitor/dist/services/database.js:3964:39) at DatabaseService.getTelemetryByNodeAveragedAsync (file:///home/pi/meshmonitor/dist/services/database.js:8932:21) at file:///home/pi/meshmonitor/dist/server/server.js:3467:47 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { code: 'SQLITE_ERROR' }

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions