# How to display historic Time-of-Use-Tariff prices in OpenEMS or InfluxDB? **URL:** \ **Category:** English Forum\ **Created:** [June 18, 2026, 2:46pm UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879 "2026-06-18T14:46:28Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sjjh](https://community.openems.io/user_avatar/community.openems.io/sjjh/32/2296_2.png) [@sjjh](https://community.openems.io/u/sjjh)\ **Post date:** [June 18, 2026, 2:46pm UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/1 "2026-06-18T14:46:28Z")
We are using the [ENTSO-E Time-of-Use-Tariff component](https://openems.github.io/openems.io/openems/latest/edge/tariff.d/io.openems.edge.tieofusetariff.entsoe.html) which provides the current price in the channel `_sum/GridBuyPrice`. For debugging reasons I’d now like to display the historic prices. As I couldn’t find a possibility inside OpenEMS, I was trying to get it from the influxDB. But there I did not find th right field: ![image](https://community.openems.io/uploads/default/original/2X/c/c5d92467e406af45974ffcf57a2b9058606f6b50.png) Can someone help me how to get/display the historical values? ---
**Author:** ![Howaner](https://community.openems.io/letter_avatar_proxy/v4/letter/h/87869e/32.png) [@Howaner](https://community.openems.io/u/Howaner)\ **Post date:** [June 22, 2026, 12:03pm UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/2 "2026-06-22T12:03:29Z")
Have you checked that the channel really holds a value? What is your persistentPriority configuration in the influxdb component? ---
**Author:** ![s\_h](https://community.openems.io/letter_avatar_proxy/v4/letter/s/85e7bf/32.png) [@s\_h](https://community.openems.io/u/s_h)\ **Post date:** [June 27, 2026, 11:58am UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/3 "2026-06-27T11:58:36Z")
> [@Howaner](#): > > What is your persistentPriority configuration in the influxdb component? If the persistence priority is set to low the values are written into the InfluxDB. Here are my historic prices from the channel \_sum/GridBuyPrice: ![Bildschirmfoto 2026-06-27 um 13.58.17](https://community.openems.io/uploads/default/original/2X/b/bc0c2d9feec9f56d66e536ce8971d214699a2db6.png) ---
**Author:** ![sjjh](https://community.openems.io/user_avatar/community.openems.io/sjjh/32/2296_2.png) [@sjjh](https://community.openems.io/u/sjjh)\ **Post date:** [June 28, 2026, 8:39am UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/4 "2026-06-28T08:39:44Z")
> [@Howaner](#): > > What is your persistentPriority configuration in the influxdb component? _very low_ ![grafik](https://community.openems.io/uploads/default/original/2X/f/f15e7e2e574bb185049fb4b54343170a670d1318.png) > [@s\_h](#): > > If the persistence priority is set to low the values are written into the InfluxDB. I assume that _very low_ includes _low_, doesn’t it? Can you post the query you used in influxdb? With [above posted approach](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879) I did not find it. ---
**Author:** ![s\_h](https://community.openems.io/letter_avatar_proxy/v4/letter/s/85e7bf/32.png) [@s\_h](https://community.openems.io/u/s_h)\ **Post date:** [June 28, 2026, 11:01am UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/5 "2026-06-28T11:01:18Z")
![Bildschirmfoto 2026-06-28 um 12.57.50](https://community.openems.io/uploads/default/original/2X/b/bfdef6db666cace9767f1448195cbbcb2651b891.png) ---
**Author:** ![s\_h](https://community.openems.io/letter_avatar_proxy/v4/letter/s/85e7bf/32.png) [@s\_h](https://community.openems.io/u/s_h)\ **Post date:** [June 28, 2026, 11:24am UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/6 "2026-06-28T11:24:27Z")
Try a much higher value for the cycles. maybe 1 is too short for very low priority, since there are many values that are written to the InfluxDB. ---
**Author:** ![sjjh](https://community.openems.io/user_avatar/community.openems.io/sjjh/32/2296_2.png) [@sjjh](https://community.openems.io/u/sjjh)\ **Post date:** [June 28, 2026, 12:13pm UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/7 "2026-06-28T12:13:20Z")
Stupid me, human error. I was looking at the test-system (and not productive system). There I had disabled the component earlier. Thus no data… 😑 Looking at the productive installation, I can see data (with cycle of 1). No I got a follow-up question. 😃 Where do I see the future prices? The upcoming prices of the next 1 - 3 days are known, but the table seems to only show the historic prices until now. ---
**Author:** ![Howaner](https://community.openems.io/letter_avatar_proxy/v4/letter/h/87869e/32.png) [@Howaner](https://community.openems.io/u/Howaner)\ **Post date:** [July 1, 2026, 12:47pm UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/8 "2026-07-01T12:47:26Z")
OpenEMS takes a snapshot of all channel values and stores them in influxdb. The future prices are not stored in a channel, so they are not written to influxdb. Currently they are only available in memory. You can theoreticly fetch them via a jsonrpc request and store them somewhere yourself. ---
**Author:** ![sjjh](https://community.openems.io/user_avatar/community.openems.io/sjjh/32/2296_2.png) [@sjjh](https://community.openems.io/u/sjjh)\ **Post date:** [July 6, 2026, 6:11pm UTC](https://community.openems.io/t/how-to-display-historic-time-of-use-tariff-prices-in-openems-or-influxdb/10879/9 "2026-07-06T18:11:22Z")
> [@Howaner](#): > > The future prices are not stored in a channel, so they are not written to influxdb. Maybe I misunderstand it. To me it seems to make sense to store them in a channel as well, to e.g. display them on the dashboard and to use them for controller.