Mine’s still not working.
My config
wwlln:
latitude: 40.9
longitude: -74.1
window: 3600
radius: 200
There’s a storm right over my house, lots of strikes on wwlln’s map and still nothing on my lovelace map.
My map is setup like yours except I also have the USGS geo sevice active on the same map. (That has showed quakes correctly over the past week, just no lightning.) And my map is 16:9. I actually made the map using the UI, not yaml in the raw config.
I believe the map automatically tries to zoom in/out to show all entities that it is supposed to display. I am not aware of any option where you would for example define map coordinates. If there are no entities to show that map will center around your home.
You can either define specific entities to display on the map, e.g. device trackers, or you can define a geolocation source which then automatically finds relevant entities to display. entities: [] just means that there are no specific entities defined.
As earlier mentioned in this thread, the currently released version of this integration defines a “window” of only 10 minutes which means that it could miss events.
Some fixes have been made in the meantime, but they haven’t been part of any minor releases, and you would need to wait for 0.97.
Very sorry - I just realised that the change from 10 minutes to 1 hour has not been released and is only part of the development version. I expect that version 0.97 will contain all fixes.
Sorry… I missed that part. Thanks!
ok, thanks. So we set the parameters for the component/integration in the config, and on the map card we set the entities. which makes more than one map possible, albeit with the same parameters .
Which is in fact a bit a pity, because it would be good to be able to set window and radius per map. don’t need the same granularity on each entity after all.
How does that figure out what to show when a long/lat is set in the wwlln: config, and an entity in the map, and these are totally different locations?
of course! it is plain yaml…
just like I always use condition: [] in my automations eg. just never saw it being used in the configs, and mine just dont have the key entity: where I don’t need these. Hope thats alright?
In the geolocation world, each integration only supports a single value as “source”. That is, you could set up two separate wwlln integrations with different lat/long values and different radius, but on the map you can only define the source, i.e. any geolocation entity with that source will show up. If the two general locations are very far apart from each other, the map will zoom out to show all entities at once.
Originally the source attribute was built for triggering an automation, and then you would use conditions to further filter entities. But the map does not support such conditions.
Maybe the map needs more configuration options? For your use-case I could imagine two options: Fix the zoom factor of a map, i.e. turn off auto-zoom to fit all entities. Or, change the geolocation source parameter to something that is configurable.
Not a solution, but a little trick that I use: In addition to the geolocation source you can add a zone to the map (e.g. your home zone) and you can define the default zoom, so that the map always shows that zone in the center and a certain radius (the zoom factor relates to distance) if no geolocation entities are active at a time.
yes! that is exactly what I am looking for, but I dont know how to do that.
Ive done something like that with the earthquakes like this:
- platform: usgs_earthquakes_feed
# url: https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson
feed_type: 'past_day_all_earthquakes'
radius: 300
minimum_magnitude: 2.0
latitude: -7.redacted
longitude: 110.redacted
- platform: usgs_earthquakes_feed
feed_type: 'past_day_all_earthquakes'
radius: 500
minimum_magnitude: 3.0
to have the top one show a specific lat/lon while the bottom one simply centers around my HA instance.
can’t figure out how to do so with wwlln: though …
having all on one map is no solution since the locations are at opposite sides of the world, and the map would be far to wide and needed zooming always…
Well, in the UI you can add as many wwlln integrations as you want, and each can define its own lat/long and radius.
The wwlln integration does not let you define multiple entries in a YAML configuration file.
The usgs_earthquakes_feed is (still) implemented as a platform and that’s why you can have multiple entries in YAML.
thanks, I see, and will try to setup accordingly.
1 more thing please: can we have the regular Map in the left side menu bar, not show all these geo_location entities? Id like to have these on dedicated maps/cards in some dedicated views, and keep the ‘main’ map tidy, eg only with my device_trackers and zones.
Ive just found out that especially the (enormous amount of) earth quakes keep HA from responding swiftly, and had to turn down the radius a lot… having them only show on a Quake card would be better…if possible.
I see what you mean. My understanding is that that map just shows any entity with longitude/latitude.
Not really a solution, but a workaround: You could remove the main map and only use custom Lovelace maps. That would give you more control over what appears where.
When i limited my longitude and latitude from many to only 2 decimals it started to work 
I’m going to give that a try right now and will report back soon. (There is another storm in my radius right now.)
Edit: It DOES work if you set your lat/long to 2 decimal places! Lightning strikes started reporting on the map immediately.
Martin… you’re a genius! 
Will try when I get back to my system… but how on earth did you figure this out? Is there any clue in the docs/source to limit decimals at all?
btw, how did you set it up? i have wwlln: in my config like this:
##########################################################################################
# Geolocation
##########################################################################################
wwlln:
radius: 1000
window: 3600
so no lat/lon at all, suppose it using the default for my config.
also have an integration setup, and that has the default units it showed automatically…
not sure I I need these both?
for the sake of experiment have now setup an integration using only 2 decimals, and a wide km range… 
Still seeing nothing, (which might be correct, since it is very nice weather over here)
update
deleted the wwlln: entry and rely solely on the integration, to which I added a heavily struck region (again with only 2 decimals), to be sure lightning would show… Unfortunately the map remains empty.
I deleted the wwlln integration that had my config.yaml lat/long… and only kept the integration that had the 2 decimals. And that seemed to work.
Do you have a radius or window set in your config? (I’m just wondering, because I do… and that part seems to be causing some troubles.)
Right now I have a set radius of 50 (miles), and a window of 3600 (seconds)… but I currently am showing lightning strikes on my map that are 200-300 miles away and from 3-4 hours ago. So something there seems to be broken too. I’m going to pull all the extra config attributes and reboot and see what happens. Keep you posted!
UPDATE: I only kept the lat/long with 2 decimals in my config, and removed the radius and window settings. While I seem to have gotten rid of the strikes from hours ago… I have a question on the radius. I thought the default radius was 25 units set in config… so I was expecting to see a radius of 25 miles. I’m currently showing strikes from a minute or so ago… that are 75 - 115 miles from my location.
as you can see above, I indeed had the radius and window set. No long/lat. Hoping it would default to the config long/lat. Ive now taken out the window and radius altogether, (have these set in the integration settings) and restarted… Nothing:-(
Oddly enough, the only thing I kept is the lat long. (Only 2 decimal places) that does work…
But the radius and window changes have zero effect. I’m showing strikes from 40 minutes ago over 90 miles away. (I thought the default in this version was 25 miles and 10 minutes.)
just to be 100% sure: you use the integrations wwlln setup
wwlln:
?
I had initially set it up using “integrations”. But that used the default lat/long from my config.yaml.
So then I went into config.yaml yesterday and shortened the lat/long to 2 decimal places, and rebooted. Strikes finally started showing, BUT then I had 2 WWLLN integrations 1 with the default lat/long from my config and 1 with the shortened lat/long. I then deleted the one with the default lat/long and left the other.
UPDATE: Completely removed all wwlln integrations. rebooted. Added WWLLN using integrations. When creating the integration I truncated the lat/long to 2 decimals and extended radius to 50. Rebooted. Big t-storm currently within 15 miles of my location… results… nothing… no strikes on map. Will continue to monitor.
Update 2: removed all wwlln integrations, rebooted. Added new wwlln integration, did not change any settings, rebooted again. Big storm overhead for past hour and still going strong. Nothing showing on map.
Update 3: upgraded to HA 0.97. Wwlln working as it should be!
Woke up this morning to a map full of lightning strikes, so wwlln and HA 0.97 play nice together.
But the problem is that the storm ended 8 hours ago. I thought the default was 1 hour and then I assumed they would clear out?
Pure intuition, or alot of trial and error 
Had problems also with the “window” keeping lightning strikes on the map forever, swaped to
window:
__minutes: 30
seams to work, the distance never changes from 149.9km though, whatever i put in it keeps showing me data from my specified long-lat and everything within 149.9 km 
ill try update now to 0.97 and wait for next thunderstorm.
my current config…
wwlln:
__latitude: 59.07
__longitude: 15.54
__window:
____minutes: 30
__radius: 20
EDIT: “__” is not underscore, just blank spaces, this forum truncates spaces in begining of lines
