Did you add a card and make it the free subcription plan? If you did not, it will not work and give that same error message.
See OpenWeatherMap-Alerts-Weather-Driver - #721 by syepes
and the follow on here: OpenWeatherMap-Alerts-Weather-Driver - #722 by Matthew
Thank you Tray_e and all. I'm not keen on given them a card detail for now. I'll try WSM4 for now and see if I can get that to work. Hopefully it will be accurate for the UK. The support and reponsiveness of people since I started using hubitat is amazing. Thank you all!
The current version of the OWM API won’t work without your credit card info.
If it helps, quite a few people in this thread have done the same thing, and no one’s been charged since it’s easy to stay below their daily limit for free API calls. It’s also possible to set a cap on the total number of daily calls to further protect yourself from an unexpected charge.
Thank you Mark. I'll try WSM4 for now and if I can't get the data I'll need, I'll default back to the OpenWeatherMap. I could also register a less important credit card ;-). Happy new year.
@Matthew my device preferences don't look like what you have. I installed 08/31/23 version and on the device page there is only a very limited set of Preferences. No API Key Version Slider, no 3 day forecast sliders, or Display all Optional Attributes. Am I missing something?
The IconLocation https://tinyurl.com/icnqz/ returns 400: Invalid Request
Sounds like your virtual device is NOT using this driver, but is using the integrated driver. When you select the driver make sure you scroll all the way to the bottom to the 'User' driver section and select OpenWeatherMap-Alerts Weather Driver
Going to https://tinyurl.com/icnqz/ will give you an error without a specific file listed. Try adding 1.png (https://tinyurl.com/icnqz/1.png) and you should see this:
I had the same issue but reinstalled the driver after subscribing to the api3.0 on their website and it worked for me. Basically I was trying to use a key with no privileges
I see in detailed logging that moonrise, moonset, and moon_phase are part of the data received, but not available even in the set of optional attributes.
Could they be added easily, or is my best bet to use some other available device driver that specializes in sun/moon data?
[UPDATED V0.6.9 04/17/2024]
If using HPM do an Update or a Repair. Otherwise open the driver code and re-import the code. Thanks.
Also received it, is this driver using API2.5 or 3.0 at the moment?
Either: User select-able:
It works for me? What error are you receiving?
Also anyone that’s started using this integration in the last couple years has been using a onecall 3.0 API key, since that’s all that’s been available for new users.
Thanks @Matthew for the heads up re: the need to update, I haven’t seen a similar email from OWM even though I’m still using the 2.5 API.
here is no error in the logs.. the way the code is written if there is an error it ignores it.. but it is not working.. if you print out the url and manually call it.. it works with 2.5 in the url but 3.0 gives an error
same.
To all using 2.5, besides changing the 2.5/3.0 select button to 3.0, I needed to go to the subscriptions page to subscribe to One Call 3.0. You have to enter a CC but you get 1000 free queries. After subscribing I set my maximum number of queries to 999 to make sure I stay free.
logs complain about /find? being 404 after you change to 3.0 and save the device. but it doesn't seem to affect anything- all seems to work fine.
here you go.. from what i see this call will no longer be supported and you need to use the
/geo call but i dont see it returning an id..
the only similiar call i see documented is this
https://api.openweathermap.org/geo/1.0/reverse?lat=' + (String)altLat + '&lon=' +
etc.. but it doesnt return an id.. only the city name etc
Do you have an active 3.0 API key in addition to a 2.5 key?
yes i had an older 2.5 key .. that is still working.. it is strange that the url works with the 2.5 mnemonic but with my 3.0 key.
Download the Hubitat app
