Auto-entities: template lightning strikes of last hour?

Configuration
1

hi,
using the auto-entities card I’d like to template the lightning strikes of let’s say the last hour (if they exist in the first place). The integration wwlln creates strikes and although we are supposed to be able to set radius and window, I haven’t been able to see that in effect, and now use the integration via the configuration settings, which doesn’t have that option.

So I now have 80 95 strikes in my states, most of them old…I’d like to only show the most recent.

49
using this:

  - type: custom:auto-entities
    show_empty: false
    card:
      type: entities
      show_header_toggle: false
      title: Lightning strikes
    filter:
      include:
        - entity_id: sensor.count_lightning_strikes
        - attributes:
            source: 'wwlln'
          state: "< 50"

where the state filter at least narrows it down somewhat.

as an example the strikes are formatted like this:

{{states.geo_location.lightning_strike_1643410}}

and have these attributes

<template state geo_location.lightning_strike_1643410=60.2; latitude=51.86, longitude=5.16, source=wwlln, external_id=1643410, attribution=Data provided by the WWLLN, publication_date=2019-08-27T18:25:08+02:00, unit_of_measurement=km, friendly_name=Lightning Strike: 1643410, icon=mdi:flash, custom_ui_state_card=state-card-custom-ui @ 2019-08-27T19:01:37.077341+02:00>

and as last_changed:

05
05909×200 24.5 KB

need some help finding the correct template, and way to write that in the format of the auto-entities card.

Please have a look.

2

You could have done this if you had taken everyones advice in learning code! I think this is my 10th or 11th time saying that you should try to pick up python/jinja. This is a very easy loop.

{%- set t = as_timestamp(now()) - 60 * 60 %}
{%- set n = namespace(count=0) %}
{%- for s in states.sensor %}
{%- if s.entity_id.startswith('lightning_strike_') and s.last_updated != None and as_timestamp(s.last_updated) > t %}
{%- set n.count = n.count + 1 %}
{%- endif %}
{%- endfor %}
{{ n.count }}
3

trust me, I am trying. And am, aamof. But this is not that simple as you say.
I am hoping to find a way to have the auto-entities card show the lightning strikes of the last hour.

I cant check right now, because no strikes are registered, but your template counts the strikes.

next to that, the format of the filter of the auto-entities card requires yet another different syntax. Have only made a few of these, relying on a simple state (as posted above) makes me want to seek help of the community…

4

I don’t think you can do what you want to do with auto-entities. It doesn’t appear as if you can match state object properties with this card. @thomasloven would know for certain if there is a way to match against last_updated property (which is not an attribute). I doubt it because they are datetime objects.

5

You may be able to make an automation that updates minutely and dynamically changes the entities inside a group. Then use auto-entities match group as a card.

Using the service: group.set

6

Yes, feared as much on the last updated. But maybe the attribute publication_date could come to the rescue? compare that to now and have set of states built on that?

7

How? Templating isn’t available in auto-entities.

8

bummer. you’re right…I’ve mistaken

  • supports Regular Expressions.
  • supports comparison operators
    for templating…

so need a feature request before I can build it than :wink:

as discussed here Jinja / Template Sensor Question - #11 by Mariusthvdb I would have hoped to create a template likewise for the last hour end have auto entities show them.

{% set km = states('input_number.lightning_strikes_near') %}
          {{ states.geo_location|selectattr('attributes.source','eq','wwlln')
             |selectattr('state','lessthan',km)|list}}
9

Or make a dynamic group with an automation. Then use said dynamic group as the match group for auto-entities.

10

I’ll have a look at that, as said, theses are only my first auto-entities cards.

This all wouldn’t be necessary if the integration wwlln: would simply work as described of course. window and radius not really effective, and seems the UI integration only uses window, which doesn’t work (yet, dev’s are working on that)

11

…yet…
 

2 Likes
12

I agree. Personally, I don’t know why the lightning strikes were added as separate sensors. I would expect these to be attributes which would allow easy templating.

13

While Thomas is adding templating (yeah) I had a look at my domains sensor, and that would translate to something like this:

{%- set t = as_timestamp(now()) - 60 * 60 %}
{%- for s in states.geo_location %}
{%- if s.entity_id.attributes.source == 'wwnnl' and s.last_updated != None and as_timestamp(s.last_updated) > t %}
{%- endif %}- {{s}}
{%- endfor %}

cant test it now, because no lightnings are around, but am not sure of the {{s}}.
Would that show the full entity, thuis building the list I require?

14 
{{ s.entity_id }}{{ ',' if not loop.last else ''}}{%- endif %}
1 Like
15

think it also needs to be:

{%- if s.attributes.source == 'wwlln' and s.last_updated != None and as_timestamp(s.last_updated) > t %}

instead of

{%- if s.entity_id.attributes.source == 'wwllln' and s.last_updated != None and as_timestamp(s.last_updated) > t %}

making it

{%- set t = as_timestamp(now()) - 60 * 60 %}
{%- for s in states.geo_location %}
{%- if s.attributes.source == 'wwlln and s.last_updated != None and as_timestamp(s.last_updated) > t %}
{{ s.entity_id }}{{ ',' if not loop.last else ''}}{%- endif %}
{%- endfor %}

now wait for the strikes to happen and test.

16

I didn’t notice the entity_id in there.

That template should just create a list of entity_id’s. Where are you using it?

17

but only of the domain geo_location and source wwnnl. Which get created if and when lightning is registered. Currently they aren’t there, so no list is created.

not yet using it, but as said, hope to be able to use it somehow in the Lovelace frontend. Will use it with source usgs_earthquakes_feed also.

most likely use it for Map, because I need an entity list there. If I can get the Maps card to be templated, and then replace this:

  - type: conditional
    conditions:
      - entity: binary_sensor.lightning_active
        state: 'on'
    card:
      type: map
#      dark_mode: true
      title: Lightning strikes conditional map
      geo_location_sources:
        - wwlln
18

marked your post as solution, it shows fine after the discussed edits above!

this is it:

{%- set t = as_timestamp(now()) - 60 * 60 %}
{%- for s in states.geo_location %}
{%- if s.attributes.source == 'wwlln' and s.last_updated != None and as_timestamp(s.last_updated) > t %}
{{ s.entity_id }}{{ ',' if not loop.last else ''}}{%- endif %}
{%- endfor %}
19

just a bit more variation:

trying this:

          {% set hour = states('input_number.strikes_period')|float %}
          {%- set t = as_timestamp(now()) - hour*(60 * 60) %}
          {%- for s in states.geo_location %}
          {%- if s.attributes.source == 'wwlln' and s.last_updated != None and as_timestamp(s.last_updated) > t %}
          {{ s.entity_id }}{{ ',' if not loop.last else ''}}{%- endif %}
          {%- endfor %}

to create an option to have an input_number in the front-end allow me to see the when most of the strikes happened.

first I tried it without the |float on hour, but then I realized even an input_number isnt a number, but a string…

what I hadn’t noticed before at all, is that all input_numbers have a state with a decimal number. Even if the minimum step is an int. And still are strings…
confusing.

secondly, and most importantly, it adds the , even after loop.last with makes the full template fail in the frontend.

somehow is doesnt see the last as last, because no matter what I enter in the else clause, is isnt displayed, instead a , is used.

55
55810×569 89.8 KB

20

print loop.last out and see what it’s value is