Flux Query with range(start: -1d) works, with range(start: -30d) works not, with new measurement

Grafana InfluxDB
1

Hello i use Grafana 12.1.0 and Influx 2.8.0,
today i have create a measurement Regenzaehler,

and with a Flux Query

from(bucket: “iobroker”)
|> range(start: -1d)
|> filter(fn: (r) => r._measurement == “0_userdata.0.Wetter.Regenzaehler”)

i get a table with

Time, ack, from, q, value
2026-06-11 16:29:55, true, system.adapter.influxdb.0, 0, 1
2026-06-11 16:34:38, true, system.adapter.node-red.0, 0, 1
2026-06-11 16:34:46, true, system.adapter.node-red.0, 0, 2

if i change the range to -30d

i got the same table without value

Time, ack, from, q
2026-06-11 16:29:55, true, system.adapter.influxdb.0, 0
2026-06-11 16:34:38, true, system.adapter.node-red.0, 0
2026-06-11 16:34:46, true, system.adapter.node-red.0, 0

What is wrong?

2

welcome to community @yettiz
The missing value column when changing from -1d to -30d is caused by a field type conflict → your value field was written with different data types at different points in time. InfluxDB silently drops the column when a query spans records with conflicting types.

1 → Confirm the root cause:

flux

from(bucket: "iobroker")
  |> range(start: -30d)
  |> filter(fn: (r) => r._measurement == "0_userdata.0.Wetter.Regenzaehler")
  |> map(fn: (r) => ({r with dataType: display(v: r._value)}))

If you see mixed types (integer and string) in the dataType column → this is your problem.

  1. Use this to fix the issue

flux

from(bucket: "iobroker")
  |> range(start: -30d)
  |> filter(fn: (r) => r._measurement == "0_userdata.0.Wetter.Regenzaehler")
  |> filter(fn: (r) => r._field == "value")
  |> toFloat()

If toFloat() doesn’t work (older data written as string), try:

flux

  |> toString()

The InfluxDB community forum thread describes the exact same problem:

3

With range(start: -1) i get
_time, value {_field=“value”, start= "2026-06… dataType{_field=“value”, start="2026-06…
2026-06-12 15:01:25 1 1

with -30d i get nothing

I think the measurement is corrupt; I tried using a new measurement, and it works.

I also tried deleting this measurement, but the problem persists.

Thanks for the help.