Put geo_events on a map instead of an entities card.

[thomasloven]

... With the default solution, geo_events are added to a static list - i.e. it doesn't update as new geo_events are added or they are resolved.

This was the best way I could come up with to fix things. Had to add a new magic value to the geo_event_sources list for the map card (needs documentation).

Unfortunately the distance to the event is lost.

Before:

After:

[thomasloven]

Zones and location trackers could also be put on a map, perhaps?

[balloob]

Nice!

I think that we could consider adding the device trackers to it too. Or maybe that should be a separate one? I think that we can wait with that because we currently already have them as a badge. I hope that we can get to implement our "Person" implementation soon, which should be preferred over device trackers.

[thomasloven]

Yeah. This was kind of urgent because it looked ugly by default (is there anything using geo_location?) - device trackers aren't.

[balloob]

geo location is a different category than device trackers. Geo location is for feeds that have time-based location events, like fires, storms, etc. Things that come and go.

[thomasloven]

Yes. My question is if there are any components that actually use them (besides demo).

... rtfm, Thomas. The docs tells me that yes, there are.