Template to find information based on lowest entity

Configuration
1

I read a lot the last day, but i am stuck in my mind. So i am asking for some help or at least a push in the right direction.

Here is my problem. I use the tankekoenig integration to get fuel prices from gas stations around my home. Each station give me a price entity and a status entity if the station is open.

With the auto entities card i build a sorted list that show the prices and everything is fine.

image
image864×688 45.7 KB

Noe my wife has made a request: Please diskplay the lowest price and the according station name on a mushroom template card (OK - she did not say something about mushroom cards, but the start is true)

Based on this request i tought about how to get the values i need to display. SHould be easy was my first tought: Get sensors, sort them reverse, get values from first element.

But …

It seems that there is no way to select the price sensors by using wildcards. The integration_entities give me the status sensors to and i did not find a way to exclude them to start sorting.

That is the point at the moment.

So please give me a hint.

2

Be aware that there are more than 1000 integrations. Plenty of people on here are willing to help, but might not have access to the integration you are using. It would be helpful if you would post the details for at least one entity from the States tool.

1 Like
3

I tough in a more genric way, but providing information should be the easiest thing.

This is the information about the status. If a ga station is open or not

image
image2080×274 34.7 KB

And this is the information about a price entity

image
image1971×580 67.6 KB

For each gas station i get these two entities. Staring to develop a template to get the lowest price and according friedly name i started with

{% set station = integration_entities('tankerkoenig') %}
{{ station }}

which brings the following as result

[
  "binary_sensor.net_gas_station_nordoel_hamburger_str_100_status",
  "binary_sensor.net_gas_station_jet_hamburger_str_110_status",
  "binary_sensor.svc_gas_station_star_hamburger_strasse_141_status",
  "binary_sensor.net_gas_station_hem_ramskamp_67_status",
  "binary_sensor.net_gas_station_nordoel_reuterstr_90_status",
  "binary_sensor.net_gas_station_tanklager_baack_kiebitzreiher_chaussee_4_status",
  "sensor.net_gas_station_nordoel_hamburger_str_100_super_e10",
  "sensor.net_gas_station_jet_hamburger_str_110_super_e10",
  "sensor.svc_gas_station_star_hamburger_strasse_141_super_e10",
  "sensor.net_gas_station_hem_ramskamp_67_super_e10",
  "sensor.net_gas_station_nordoel_reuterstr_90_super_e10",
  "sensor.net_gas_station_tanklager_baack_kiebitzreiher_chaussee_4_super_e10"
]
4

As long as prices don’t reach 9-10€ the following should work.

{% set lowest =  expand( integration_entities('tankerkoenig')
| reject('search', 'binary_sensor') 
| select('has_value'))
| sort(attribute='state') | first %}
 
{{ lowest.name }}: {{ lowest.state }} €

The above achieves the basic goal, it might be improved by starting with the binary sensors so you only include price data from stations that are open…

{% set open = integration_entities('tankerkoenig')
|select('is_state', 'on')
| map('replace', 'binary_', '')
| map('replace', 'status', 'super_e10') | list %}

{% set lowest =  open | select('has_value'))
| sort(attribute='state') | first %}
 
{{ lowest.name }}: {{ lowest.state }} €
5

@Didgeridrew Thanks a lot. That is far more than i expected. At first sight it seam clear and very easy.

Thanks a lot. :slight_smile:

6

After digging into the template code some questions come to my mind.

The expand expands the entities - Check
The reject filters the binary sensors out - Check
The select selects only entities with a value - Check
The sort does the sort - Check
And the first selects the first element - Check

The result is as follows

<template TemplateState(<state sensor.net_gas_station_nordoel_reuterstr_90_super_e10=1.779; state_class=measurement, brand=NORDOEL, fuel_type=e10, station_name=Eyes Tankstellen GmbH, street=Reuterstr., house_number=90, postcode=25436, city=Uetersen, latitude=53.6932879, longitude=9.6546212, unit_of_measurement=€, attribution=Data provided by https://www.tankerkoenig.de, icon=mdi:gas-station, friendly_name=NET - Gas Station - NORDOEL Reuterstr. 90 Super E10 @ 2023-04-21T20:02:49.182037+02:00>)>

Now i coud acces the state and the name but no other attribute. What did i miss?

7

state and name are properties of the state object so they can be accessed directly from lowest. To access attributes you would use lowest.attributes, for example lowest.attributes.postcode

8

Thanks for your help again. I think i need to dig deeper into the obket and so on.