Skip to content

[BUG] Can't access any device details #155

Closed

Description

@parasiteoflife

Describe the bug
When I try to access the details of any device I get error on console and nothing is shown.

Log

time="2026-01-26T00:19:02Z" level=error msg="xxx.xxx.xxx.xxx - something [26/Jan/2026:00:19:02 +0000] \"GET /api/device/0x5000cca099e4286d/details\" 500 17 \"https://scrutiny.test.com/web/dashboard\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:148.0) Gecko/20100101 Firefox/148.0\" (12ms)" clientIP=xxx.xxx.xxx.xxx hostname=something latency=12 method=GET path=/api/device/0x5000cca099e4286d/details referer="https://scrutiny.test.com/web/dashboard" respLength=17 statusCode=500 type=web userAgent="Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:148.0) Gecko/20100101 Firefox/148.0"
time="2026-01-26T00:19:05Z" level=info msg="import \"influxdata/influxdb/schema\"\nweekData = from(bucket: \"metrics\")\n|> range(start: -1w, stop: now())\n|> filter(fn: (r) => r[\"_measurement\"] == \"smart\" )\n|> filter(fn: (r) => r[\"device_wwn\"] == params.wwn )\n|> aggregateWindow(every: 1d, fn: last, createEmpty: false)\n|> schema.fieldsAsCols()\nmonthData = from(bucket: \"metrics_weekly\")\n|> range(start: -1mo, stop: -1w)\n|> filter(fn: (r) => r[\"_measurement\"] == \"smart\" )\n|> filter(fn: (r) => r[\"device_wwn\"] == params.wwn )\n|> aggregateWindow(every: 1d, fn: last, createEmpty: false)\n|> schema.fieldsAsCols()\nyearData = from(bucket: \"metrics_monthly\")\n|> range(start: -1y, stop: -1mo)\n|> filter(fn: (r) => r[\"_measurement\"] == \"smart\" )\n|> filter(fn: (r) => r[\"device_wwn\"] == params.wwn )\n|> aggregateWindow(every: 1d, fn: last, createEmpty: false)\n|> schema.fieldsAsCols()\nforeverData = from(bucket: \"metrics_yearly\")\n|> range(start: -10y, stop: -1y)\n|> filter(fn: (r) => r[\"_measurement\"] == \"smart\" )\n|> filter(fn: (r) => r[\"device_wwn\"] == params.wwn )\n|> aggregateWindow(every: 1d, fn: last, createEmpty: false)\n|> schema.fieldsAsCols()\nunion(tables: [weekData, monthData, yearData, foreverData])\n|> group()\n|> sort(columns: [\"_time\"], desc: true)\n|> yield(name: \"last\")"
time="2026-01-26T00:19:05Z" level=error msg="An error occurred while retrieving device smart results invalid: error @5:41-5:47: undefined identifier params\n\nerror @11:41-11:47: undefined identifier params\n\nerror @17:41-17:47: undefined identifier params\n\nerror @23:41-23:47: undefined identifier params" type=web

Btw I've just migrated from the original project to the fork.

Activity

  1. added a commit that references this issue on Jan 26, 2026
    fd98f70
  2. Starosdev commented on Jan 26, 2026

    @Starosdev
    Owner

    Thank you for reporting this issue. We apologize for the inconvenience.

    This was a regression introduced in the recent security fix. The parameterized query feature (params.wwn) used in that fix is only supported by InfluxDB Cloud, not InfluxDB OSS which is what Scrutiny users run in self-hosted deployments.

    A fix has been submitted in PR #157 and will be available in the next release shortly.

    In the meantime, if you need an immediate workaround, you can roll back to v1.15.7 which does not have this issue.

  3. added a commit that references this issue on Jan 26, 2026
    6deb0bc
  4. added a commit that references this issue on Jan 26, 2026
  5. ntimo commented on Jan 26, 2026

    @ntimo

    Even with the new version, accessing devices is not working for me.

  6. Starosdev commented on Jan 26, 2026

    @Starosdev
    Owner

    Let me take a look @ntimo

  7. Starosdev commented on Jan 26, 2026

    @Starosdev
    Owner

    @ntimo Could you help us troubleshoot by providing the following information?

    1. What version of Scrutiny are you currently running? You can check this in the web UI footer or by running docker inspect on your container.

    2. If you are using Docker, have you pulled the latest image after v1.16.3 was released? The fix was included in v1.16.3, which was published at 02:47 UTC today.

    3. Are you still seeing the same undefined identifier params error in your logs? If so, please share the current error output so we can confirm.

    The fix for this issue landed in v1.16.3, so we want to make sure you have that version before investigating further.

  8. ntimo commented on Jan 27, 2026

    @ntimo

    @Starosdev

    I just updated to v1.17.0 and now the error is gone, and I can access the devices again.

  9. Starosdev commented on Jan 28, 2026

    @Starosdev
    Owner

    Perfect!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions