mrk-its / homeassistant-blitzortung

Custom Component for fetching lightning data from blitzortung.org

MIT License

210 stars 41 forks source link

[homeassistant.components.geo_location] Entity id already exists - ignoring: geo_location.lightning_strike #17

Closed papo-o closed 3 years ago

papo-o commented 4 years ago

hello , i have a lot of this error in my log when thunderstorm is near my house any idea?

mrk-its commented 4 years ago

This is likely due to how the entity IDs are created - currently they are based only on lat / lon coordinates and it seems it is not enough. Adding timestamp should help, maybe I'll need to hash it (because it is quite long already). I'll fix it soon, stay tuned!

locorotondo-gitter commented 3 years ago

Hi. First of all; thank you for this piece of programming! I really like it.

Is there any update on this buglet (it does not seem to impact the functionality as far as I can tell)? Yesterday we had a bunch of thunderstorms nearby and the logfiles were swamped with thousands of the messages that @papo-o mentioned. (at the end of the evening there were well over 18k registered lightning strikes in the area ;-)).

LIke I said; it does not seem to impact functionality (unless I miss something), so if you leave it "as is" I can totally be happy with that. :-)

Stay safe, stay healthy!

attila123456 commented 3 years ago

Same here, 800+ occurrences of the above error after a thunderstorm. Any chance of reopening the issue? Thanks!

umrath commented 3 years ago

9ef18f7 does not fix the issue, @mrk-its.

AdmiralStipe commented 2 years ago

Issue still present, please re-open!

Bob-Technicien-pro commented 2 years ago

Issue still present, please re-open!

for me too