It’s awesome that you’re stepping in, but isn’t this just a cat and mouse game? They’ll plug this option when they see the increase in traffic.
I added a (virtual) credit card and simply set my API limit to 1000. The limit they impose is very liberal and it’s not unreasonable to charge for a service at some point. Google and many other vendors do the same thing: requiring a credit card in case you exceed the limit.
I’m sure we (the community) can and will react when the time comes.
For now, there’s no need to speculate whether or when. I asked, and OWM said:
At least for now, I hope that’s good enough.
I wonder if anyone can help. I’ve upgraded my OpenWeatherMap from 2.5 to 3.0, having entered credit card details on the OWM site. The API works, and in HA I can now see the current weather again. However, all the “forecast” entities are now showing as Unavailable (see screenshots)
You apparently missed that part. Different change. This should help.
Perfect, all sorted. Thanks Nathan!
