Anyone have any new information on this?
I have the same question- am using OpenWeather with PVO and received the same alert. I’m not tied to them- it’s a nice to have, so I’m open to changing to another PVO supported provider, or if special changes are needed, following that process. Any help is greatly appreciated.
You will need to subscribe to their 3.0 onecall plan, otherwise the existing api key will not work.
The 3.0 subscription has a 1000 daily limit, excess calls will automatically be billed to your credit card.
The limit can be set after subscribing to 3.0, suggest this to be set to below 1000 to keep it in the free range -
https://home.openweathermap.org/subscriptions
e.g.
3 Likes
OK. I think max calls would be 288 anyway if you by chance got data from here at the time also from Enphase iteration of say at worst case every 5 minutes which is what Enphase tracks my system by as grand fathered in which will be well below 1000 a day.
I presume when I enroll in the API 3.0 its obvious on what to update in our PVOUTPUT profiles to make it work ok.
PVOutput will switch to openweather 3.0 onecall on May 31st 2024.
Subscribe to openweather 3.0 onecall before May 31st and reduce the default limit from 2000 to 1000 or less if you do not wish to be charged by openweather for accidentally going over the limit.
The existing openweather API key used for 2.5 will work with 3.0.
The “Test” link for openweather on PVOutput settings is now testing against openweather 3.0.
Note it takes 30 minutes or longer for the 3.0 access to register after activating the subscription on openweather.
3 Likes
OK Thanks. Is there any other free options that you know of? Trying to avoid having a profile on their web site with my CCard unnecessarily which up to now was not required. Thanks for any info.
I have ‘paid’ via Link.com. " When you place an order using Link, we do not share your full card number, or CVV code with the business."
Of course you have to share that data with Link.com.
I would prefer to provide nothing as it seemst his outfit ha another agenda to have ones credit card on profile just to use the free portion when they can easily just disallow the feature once the max free calls are allowed and if no CC is on file. So I guess I will not be collecting this data of simple temperature. But if anyone finds another site that provides that basic information that is fine. I am surprised that BBloke has not found and implemented a universal site for each part of the world that would provide that basic information that is on the standard view of PVOUTPUT and so usefull for all and not unique by region. If one has a zip code or area notation that weather info should be easily found assuming a mainstream weather site allows for such simple calls. Thanks.
Just to make the @bankstownbloke developer aware…
For the Netherlands (only unfortunately) there is an alternative that provides free data for the whole country at once.
Just one query for all 40 buienradar weather stations: https://data.buienradar.nl/2.0/feed/json
It is free without an account needed, you do need to give credit to https://www.buienradar.nl
Example that I use to query outdoor humidity (I just statically point to the second weather station in the list):
def get_humidity_buienradar():
url = 'https://data.buienradar.nl/2.0/feed/json'
#Call API
try:
response = requests.request("GET", url)
response = response.json()
except Exception as e:
#print("ErrorType : {}, Error : {}".format(type(e).__name__, e))
return None
else:
try:
humidity = str(response['actual']['stationmeasurements'][1]['humidity'])
return humidity
except Exception as e:
return NonePVOutput has migrated from openweather 2.5 to 3.0.
Note openweathermap feeds will no longer work unless your openweathermap account is a 3.0 subscriber.
Seems to be working, thanks @bankstownbloke 
| Date (UTC) | Total calls | Paid calls | Total to pay (EUR) |
|---|---|---|---|
| May 31, 2024 | 88 | 0 | 0.0 |
I bit the bullet and signed up for the free plan and seems to be working with old key and a newly generated key.
1 Like
I noticed that my temperature had stopped updating on the 31 of May and I I went to my settings on PVOutput and clicked on test and the JSON showed the target was OneCall 3.0, so I contacted OpenWeather to see if it was an issue with my account. They responded that my temperature queries were now polling OneCall 3.0 instead of OpenWeather 2.5. I then checked the PVOutput forums and saw this.
I have now subscribed to the “free” account with my CC details and will see how it goes, but as of 15 minutes after subscribing, my temperature is now populating again. The good thing is I can see the number of calls that have been made with my account, and so far it is only polling once every 5 minutes, so should be well under the 1000 free calls per month target.
I tested this by checking the counts after 30 minutes (6) then went into my settings in PVOutput and clicked on the “test” option by my Weather API, and OpenWeather showed the call count had increased by 1
Usage over the past three days:
Im the same.
I just used an old prepaid credit card that had a $0 balance on it that hadn’t expired. seemed to work 
Hi guys, below is the code as it is sent with a click on “TEST” next to the Openweathermap API key, but on the Pvoutput graph I do not see anything. 
Thanks for any help
{
“lat”: 45,
“lon”: 11,
“timezone”: “Europe/Rome”,
“timezone_offset”: 7200,
“current”: {
“dt”: 1718556691,
“sunrise”: 1718508474,
“sunset”: 1718564676,
“temp”: 25.79,
“feels_like”: 25.78,
“pressure”: 1010,
“humidity”: 52,
“dew_point”: 15.2,
“uvi”: 0.72,
“clouds”: 8,
“visibility”: 10000,
“wind_speed”: 1.95,
“wind_deg”: 331,
“wind_gust”: 2.04,
“weather”: [
{
“id”: 800,
“main”: “Clear”,
“description”: “clear sky”,
“icon”: “01d”
}
]
}
}
Seems strange.
I have 2 systems using the same api and location. One works one doesn’t 
Both show enabled on v5
edit:
disabled save and re-enabled the temp on v5 and it started working
Do you say disable, save, then enable, save? It did not work for me unfortunately
Are you using the one call 3.0 api?
Im using 3.0. It didnt work for a day. Started working suddenly. 
I do have Main temp enabled under Weather Device api key
I also remove all extended data entries for temp.