Show dynamic geolocation events (USGS earthquakes) on Lovelace frontend

Configuration Frontend
1

I’ve added the usgs_earthquakes_feed platform to my configurationa.yaml file which, produced several dynamic “geo_location” entities. I can view them in a Lovelace entity card by manually adding each one but, this is temporary as these entities are destroyed and created regularly.

I’ve already tried adding all the entities using the group.all_geo_location_events entity with no success. Is there anyway to display dynamic geo_location enties in a Lovelace card?

2

The next version (0.85) will have the ability to configure a geolocation source for a map in the lovelace UI that then automatically shows all entities from that integration.

3

HA version 0.85 now shows the geo_location entities in a map card. Now, I’m trying to create an notification automation when a new geo_location entity is automatically created in my home zone. I selected the “ZONE” trigger type from the automation UI however, the required geo trigger fields listed in the HA documentation aren’t supported. I manually entered them in my config file and when I view it in the automation UI, I get

Unsupported platform: geo_location
{
“event”: “enter”,
“platform”: “geo_location”,
“source”: “usgs_earthquakes_feed”,
“zone”: “zone.home”
}

Here’s my automation
alias: Earthquake Alert
trigger:

  • event: enter
    platform: geo_location
    source: usgs_earthquakes_feed
    zone: zone.home
    condition: []
    action:
  • data:
    entity_id: media_player.family_room
    message: Earthquake detected nearby.
    service: tts.google_say
  • data:
    message: Earthquake detected nearby
    target:
    • home_owners
      service: notify.home_owners
4

Could you please format the yaml configuration as code (see note at the very top of this page). Otherwise it’s almost impossible to spot any mistakes with the syntax or indentation.

I have to admit that I haven’t used the UI to create automations, but the geo_location trigger does indeed exist and I can confirm that it is working fine for me (currently on 0.85.1).

5

Now I see what the issue is - the UI to create automations is just missing the option to create a geo_location trigger. So, if you create such an automation manually and then try to edit it via the UI, it will probably just fail because it still doesn’t have that option.

6

That’s right. The ZONE trigger type in the automation UI only support:

  1. Entity 2. Event (“enter”) and 3: Zone (zone.home)

The documentation for the geo_location trigger requires:

  1. Event 2. Zone 3. PLatform and 4, Source (usgs_earthquakes_feed)

I forced the required geo_location trigger parameters into the automation.yaml file but, I get the “unsupported error” in the automation UI.

7

Sorry about that, I haven’t paid enough attention on usability from the UI for the geolocation platforms yet.

I am in the process of fixing an issue with group memberships of gelocation entities at the moment. Once this is done I’ll take a look at UI support for the geolocation trigger.

8

Quick update: I just submitted a PR for adding UI support for the geolocation trigger:

1 Like