Has anyone upgraded to 3.0?
I have notifications 2.5 is being deprecated so I went to the URL and it seems it's still free for 1000 calls but you have to pull out the Visa now and register.
I assume I have to get a new key but not sure if that is linked to after the registration.
I see WebCore is fine with 3.0 but community driver? @Matthew
Just trying to avoid any stumbling blocks.
I did this a few weeks ago and IIRC, if you have an account for 2.5 then you can just 'subscribe' to the 3.0 and get the new key. I didn't have to re-enter a CC#.
@Matthew’s driver has supported the OneCall 3.0 API for some time now. I just updated from the 2.5 API key I used to use. Everything still seems to work fine.
I didn’t see any way to get a new API key without entering cc info .
I tried to subscribe to 3.0 and it popped up with the billing page.
When I first got the 2.5 key I don't remember ever entering billing info.
I probably never had it and not it need it whereas you already had it on file?
Unless one polls the API at an unreasonable rate, it’s easy to remain below the ceiling for free usage every month.
I registered and created a new key but I didn't see anywhere where it specifcally said 3.0
I get this now:
app:16682024-04-29 15:57:52.809errorOpenWeatherMap http Response Status: 401 error Message: Unauthorized
Maybe it takes a bit.
EDIT gave it a few minutes and tried again. No log error, device updated
It's certainly possible that I had an old CC on file, I registered for it quite some time ago so whatever CC i used is expired. I just remember not having to enter a number this time around.
Is there any way to know which version key you have? I think I have the 2.5 key since I keep getting the emails to move to 3.0. This is what I see under Services. And clicking on the view link takes me to the 3.0 pricing page. When I scroll down this page, I see the Free API option. However when I click on the Get Key button, it gives me an alert that I am already signed in. Do I need to go with one of the subscriptions instead?
What would be an unreasonable rate? I have 3 tablets showing weather. But as I am typing this out, I think I would be OK. The hub actually does the poling and the tablets just show what the hub knows. A default install of OW on HE should be well under the limit, correct?
EDIT: I am still on the 2.5 key. I toggled it to 3.0 and started getting warnings in my logs. I can also see the previous URL's include 2.5 in the string. Additionally, clicking on Billing shows me the "Base" subscription that allows 1,000 calls per day and $0.15 USD for each 100 calls above that, with a cap of 2,000 calls per day. Unless my hub goes nuts, I doubt I will exceed those totals. Time to make the switch.
When I upgraded on Monday after hesitations about billing I noticed you can limit the calls you make.
I changed the default 2000 per diem to 500 so I will never go over even if HE/WebCore goes wonky.
I poll the weather whenever I need an updated value for a piston so it's really only 10-20 times a day.
You can also limit the number of calls per day so that you make sure you never get billed.
Go to your profile and click on the billing plans on the second line from the top.
I set my plan to be limited to 999 calls per day, so if for some reason I go over, it will just stop serving me and start back the next day. No bills to worry about!
Nice. I noticed the ability to change the limit as well, but set it to 999. How long after the activation of the subscription did it take to not have the hub toss unauthorized warnings?
EDIT: Anyone know if a new key needs to be generated? I'm assuming I can continue to use my existing key.
I was worried I had the wrong "new" key as there is not a definitive 3.0 anywhere.
I only got the errors for about 5 minutes.
A new key does not need to be generated, if you have an existing key. If you are a current OW users, just subscribe to the new plan seen under "Billing". Edit your daily call limit, if you want. Put in a CC # and pay the $0 that you owe. Flip the 2.5 / 3.0 API toggle within your HE device and wait a few minutes. Good to go.
More than 1,000 API calls per day would be pretty unreasonable .