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.
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?
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’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.
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.