Wwlln working?

Pure intuition, or alot of trial and error :stuck_out_tongue:

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 :scream: 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

You need to use code blocks to post code. You use three backticks on the line before and after the code and it will post correctly.

1 Like

Exact same behaviour for me. Lightnings from yesterday (16 hours ago) plotted on map. What am I doing wrong. Using integrations with everything default exept zoom value. Lovelace map.

well, there’s progress here!
I’ve deleted the entries in the configuration/integrations, restarted, and have edited my yaml entry. Of course restarted again (changing yaml still requires that)

I now see a map with many lighting strikes! finally. The entry in the configuration/integration tab is back though. Still saying no devices.

all in all this feels a bit flakey, not to say flawed…

The whole idea of the configuration/integration would be no manual editing is needed any more? While in this case, it only worked the other way round.

btw, now I have states, I wonder what the state is expressing. Attributes are clear, but the state is a number I do not yet understand?

The number is the distance in kilometres or miles from your location to that event.

Ha! Of course… thx.

Having set a radius of 200 doesn’t work though( now i see in the frontend: sorry for my question above…)

Yes the Radius part seams broken?

broken or not, it kills my instance…

24

Look in the GUI under "Configurations --> “Integrations”

Make sure you dont have multiple lines of WWLLN, i had 3 i think, one for each change in the long-lat config.

I removed the 2 old ones. Maybe that helps?

have only one now. A no lightning :wink: never know if its alright or not… somehow a ‘mother’ señor indicating setup is correct would really be very nice.

Woke up to 1 lightning strike on my map… from 8 hours earlier. I think the “window” is broken too.

Had a pretty good storm roll through last night. My map is filled with strikes… more than 12 hours after the storm has passed (see map).

I don’t think my integrations is purging the strikes…

1 Like

yep, same here. 5 and 6 hour old lightning strikes…
file an issue?

btw, I deleted the yaml entry wwlln: and now have 2 integrations configured on 2 lat/longs, which seems to work for now in HA 97.2.

made a conditional Map to only show when strikes are actually there. see Conditional Map?

@MandM78 can you share your config? …you’re configured for the area I need :slight_smile:

I would but I don’t have an actual config… I set it up using configuration -> integrations and let it use the default location that’s in my regular config.yaml.

(I basically clicked 2 buttons and let it be.)

If it helps though, the (general) location I have setup in my config is: 41.10XXXX, -74.17XXXX

I still have strikes from yesterday on my map.

I’ve found a bug in how the integration manages its entities which leads to lightning strikes remaining in the system forever (or until the next restart). This has already been fixed, but I assume that the fix will only be integrated in version 0.99.

2 Likes

thank you very much! had over 400 strikes today :wink:

Noticed you updated the icons in the NSW Fire Warnings… nice… I notice when I have a Lovelace card with a list of WWLLN (auto-entities) that I think if I remember correctly (no lightning here for a few weeks) that the icon was just the ‘eye’ icon and I had customised the WWLLN events via customize_glob.yaml with a lightning bolt… has there been an icon change for WWLLN so I don’t need to customize the icon now?

It seems with WWLLN that the assumption is purely that you show them on a map.

I just looked at the code, and the WWLLN integration is already using the flash icon since its first release.

Either that, or use in automations. With other geolocation integrations we are usually dealing with fairly isolated events, while with the WWLLN integration I would imagine that the intensity of events matters, or maybe the trend of events getting closer to your home or moving away from your home.