I just upgraded to 2024.6 beta and it showed a repair activity with the request to upgrade.
It appears one needs to provide credit card information on order to continue to use API 3.0. I assume nobody would voluntarily hand out their credit card information to random businesses unless one intends to pay for a service.
Since I have no intention of paying for free weather informatie or handing out my credit card info, does this mean OpenWeatherMap is no longer usable?
If so, I think it would be fair to mention this in the documentation that OpenWeatherMap is now a payed service (even if no actual costs are involved).
You are correct. To use the 3.x API you have to provide a credit card. Without it, the updated Open Weather Map service won’t work. Looking at the limits before billing actually kicks in, I think most people will never have to pay anything. And there is a way in your account to set usage limits so you never have to pay (i.e. you can set it so that the API will stop working when you reach a certain number of calls). But I agree that the docs should probably be updated to indicate you have to provide a credit card so people can make their own choices.
FWIW - you can use Privacy.com to create a virtual credit card number, and set the limit on the card to one use only or max 50cents per day or whatever, effectively preventing you from being accidentally charged.
This is crazy, I really don’t want to provide my credit card information for this.
With all the sites getting hacked I’m really thinking twice about handing over my credit card information to anyone - especially in this case where my goal would be to never exceed the daily limit for a free account anyway.
If OpenWeatherMap wants to do good, then imho they should keep there free service free without asking for credit card info.
Asking for credit card data is only going to lead to situations where: 1. people are being charged for unintentionally misconfiguring there systems, getting charged and then having to opening up charge back complaints, or 2. people having their accounts hacked and then bad actors using their api keys or even worse their credit card info with the real owner only finding out too late and after the damage has been done.
Why open the doors to such nonsense, openweather map please reconsider.
I’m not sure what to make of openweathermaps actual pricing. The “pricing” page says 1000 API calls per day for free. When I go to the “subscribe” page I see “One Call 3.0 API subscription, Base plan, 0.15 USD per 100 calls (VAT is not included)”.
I made a comparison of alternatives here: Weather integration comparison 😎
Hopefully, it will be expended to become a complete overview of all weather integration.
As the overview shows, OpenWeatherMap has a few advantages, but nothing which is worth leaking your credit card information. Plenty of choices to switch to.
For online purchases, I use a rechargeable card. I don’t think it’s a problem to share your card details to have a service that is basically free. Also, if the card is not confirmed for future orders, it should not be meorized. I have yet to quantify how many are 1000 free requests per day, but I think it’s enough. I think I’m going to have to do some control so that I don’t go any further. It’s just my idea, but I think I’ll use this service without any major worries
ps:
I imagine that having servers running 24 hours a day 365 d has a cost, and that not putting any limits on API requests exposes you to reckless use of the service.
Then bye bye openweathermap.
It’s ok to have a paid service, but you dont offer free queries asking for a credit card.
I love it when a provider gets a name and a reputation based on their free services and all the users trusting them and one day they just force all old and new users to a paid subscription.
So long, OWM! And thanks for all the fish
Thanks, @AJediIAm, for the comparison. Great resource!
About billing, I put my credit card down at OpenWeatherMap and set a daily limit to 999. I still have no idea which API I’m using but I checked yesterday and OWM created two invoices for me for $0.00 so it seems to be OK.
Based on @AJediIAm’s work - I may change provider though.
No way! Im not entering my creditcard for a free service, which I barely use in HA.
What if OWM is hacked? Do they have a EU data processing agreement? In a non EU country?
If this “free” service stops working in june I guess I will have to remove the Integration. I have no automations which are dependend of the OMW integration and I look at my phone anyway.
Thank you @AJediIAm’s for making a alternative providerlist
You should read the Privacy Policy before entering your credit cards
And remember to Opt Out so they dont sell you data!
7.DATA SECURITY
We have put in place appropriate security measures to prevent your personal data from being accidentally lost, used or accessed in an unauthorised way, altered or disclosed. In addition, we limit access to your personal data to those employees, agents, contractors and other third parties who have a business need to know. They will only process your personal data on our instructions and they are subject to a duty of confidentiality.
You will have trust that “appropriate security” is good enough. I cant find a IT Auditor report.
Does anyone have a recommendation for an alternative service to OpenweatherMap?
I used it to provide an hourly weather forecast (nothing else) so I have a lovelace card that’s broken.
I’m not going to provide any credit card details for what was / should be a free service, so any recommendations to provide the above functionality is welcomed.
Thanks in advance.
I am also confused. Is OWM turning off API 2.5 sometime in June?
Is API 3.0 operational now?
Is the OWM Integration working with either API, or is there an upgrade to the integration supposed to happen sometime in June?
It’s been a few years since I signed up for OpenWeatherMap, but I am pretty certain that providing a credit card has always been necessary for OWM access.
Yesterday I upgraded to Core 2024.6.0 / Supervisor 2024.06.0. Upon restart I was told that I had an integration which no longer worked, and it was the older OpenWeatherMap integration I had. So I deleted it, since I have the newer one working.
The page for the integration says “OpenWeatherMap API V2.5 will be closed in June 2024. After this date, you will need to use API V3.0.”