Grafana v11.6.0:
See screenshot, all the fieldnames from my sql-query which feeds this diagramm show up with “aus” at the end. The query itself did not change, it is a simple sql-query without renaming of the fieldnames…
Any idea ?
Grafana v11.6.0:
See screenshot, all the fieldnames from my sql-query which feeds this diagramm show up with “aus” at the end. The query itself did not change, it is a simple sql-query without renaming of the fieldnames…
Any idea ?
Please share query
sorry for late answer… did not receive any notification…
SELECT
ts as time,
Therm_hc1_designtemp,
WP_dhw_curtemp,
WP_dhw_curtemp2,
WP_outdoortemp,
WP_curflowtemp,
WP_selflowtemp,
WP_rettemp,
WP_auxheaterstatus,
WP_hptc0,
WP_hptc1
FROM climatecontrol.CS6800iData
WHERE ts >= $__unixEpochFrom() * 1000 AND ts <= $__unixEpochTo() * 1000
Hi @noplayback
Grafana requires a specific time/timestamp column for proper time series visualization. This is a key requirement for Grafana’s time series panels (try switching to Table visualization and see if the problem persists).
For SQL-based data sources in Grafana, you need:
ts AS time
. The column named “time” is typically recognized automatically by Grafana as the timestamp field.The “aus” suffix issue is likely unrelated to the time column and more about how field names are being processed or transformed. It could be related to:
This should work:
SELECT
ts AS time,
Therm_hc1_designtemp AS Therm_hc1,
WP_dhw_curtemp AS DHW_Temp,
WP_dhw_curtemp2 AS DHW_Temp2,
WP_outdoortemp AS Outdoor_Temp,
WP_curflowtemp AS Current_Flow_Temp,
WP_selflowtemp AS Set_Flow_Temp,
WP_rettemp AS Return_Temp,
WP_auxheaterstatus AS Aux_Heater_Status,
WP_hptc0 AS HPTC0,
WP_hptc1 AS HPTC1
FROM climatecontrol.CS6800iData
WHERE ts >= $__unixEpochFrom() * 1000 AND ts <= $__unixEpochTo() * 1000
unbelievable…
have used “as” in the first datafield. And yes i would have expected that this overwrites whatever creates that “off”…
Still off (aus) is written behind the fieldname, and the tableview shows that as well.
I have on this same page several timeseries from the same datasource, via the same datasource-plugin.
I would guess i did something unintentional on that one timeseries…
Did some more testing… and now found out that disabling “WP_auxheaterstatus” does solve that problem. Disabling others does not help.
WP_auxheaterstatus is a text field and has this “aus” or “an” in text…
So… how that text is now added at the end of each column… i have no idea. On the other hand it is for sure wrong to add a text field to a time series… but it is a funny effect