-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weather Module not loading since MM update #3574
Comments
I'm getting the same with OpenWeatherMap:
and
Doesn't seem right to switch providers to fix this. |
@JHenzi can you post the module info for weather from config.js xxx out your apikey |
They switched the default API version to 3.0, don't know why I doens't work anymore. But when you add |
The addition of
|
Closed the Issue as fixed with adding the apiVersion: „2.5“ |
This isn't fixed! API Version 2.5 is deprecated. It was supposed to be retired in June of 2024. This needs a real fix, everyone has to migrate to version 3.0. Your default weather service is going to stop working and does NOT work without a code change already. |
@JHenzi we changed because of their notice. 3.0 is the only official api |
ReOpened due to request for an update to api 3.0 |
Nothing needs to be fixed with the code. You need to get a new V3 API key at openweathermap.com |
I have an API 3.0 account and the weather is not loading. The same API is working with other modules for weather (/scottcl88/MMM-DynamicWeather) but the default weather module is not working after the update. If you setup a payment method you can limit it to 1000 per day so you never have to pay. I've had it setup for months and have yet to get a bill from them or see anything. It's just like the free account but API 3.0. |
before 2.29 (yesterday) the default weather module used 2.5 in the url |
Oh thank you, @JHenzi this was driving me crazy before I thought to look here. I have three magic mirrors running. 1000 is probably still enough, but still. I kinda think the default option for a standard model probably shouldn't be to an API service that even just MIGHT require a fee. To much danger for an unsuspecting user who just accidentally does something wrong. |
@chrismaverick we provide different providers |
@sdetweil yes, I know. But the module defaults to openweathermap, so I am presuming that's the most likely to be used by those who are least able to understand what is happening. |
we did that because it gave the best results now so long ago, and was free. still is under most circumstances |
MM doesnt start when i was adding apiVersion: "2.5" to the config.js But when i change apiVersion: "3.0" here ~/MagicMirror/modules/default/weather/providers/openweathermap.js- to "2.5" it solved the problem and weather was working again |
so you missed a comma after and maybe before 2.5 WILL end sometime. was supposed to be june don't edit our files. all config changes go in config.js |
I recieved this yesterday via email: "We would like to inform you that we started One Call 2.5 deprecation, and your access to the product will be stopped on October 14, 2024." |
thanks, i did not receive that notice |
I think i did it right. It looked like the post above. But it didnt worked. Sorry i am a beginner dont know so much about MM. I also subscribbed to API 3.0 on openweather but i dont know what to do now. I dont get any special "3.0" API. They only send me this UPDATE: Ok i think it was the comma. Will try it when i am home |
many posters don't post the 'exact' text, so you have to know. sometimes they don't post it correctly and the forum software changes the quote marks too. you need to know how to discover and fix it the 3.0 api also requires an additional config parm
|
Hello TeaMM, I just discover the OpenWeather API issue... 👎 Just a quick question: I have a Netatmo weather station, could you please make it an official data provider for the module ? I am not a developer, but if necessary, I can provide API keys to help you... And make an official request for change... It would be so "magic" 😇 |
since API 3.0 is default, weatherEndpoint should be set to "/onecall" Fixes #3574 ATTENTION: since lat / lon defaults to 0 / 0, the weather plugins works after this patch, but shows the weather from https://de.wikipedia.org/wiki/Null_Island if lat / lon is not manually set. --------- Co-authored-by: Karsten Hassel <[email protected]> Co-authored-by: Pedro Lamas <[email protected]>
Hello, Thanks for a fix in advance =) |
@AWSW-de not what we want, but what we get. OW has changed their business model and api to match . you MUST supply a credit card to get access to the new api, ( w an uncharged count so far of 1000 requests per day) and you must change the parameters to our weather module, as location and locationID no longer work. the api requires latitude and longitude now. you must also supply a new parm as they only provide one now as they told us in emails, this transition has been going on for 2 years , and they are making it final. |
Thanks. Should have read the complete post before. |
possible |
If someone comes here and is just looking for it, here is How to Update to a OpenWeatherMap 3.0 KeyYou will need a credit card to do this, but you can limit your calls to the free limit and theoretically you will never be charged.
I use two modules, and my new config looks like this [
{
module: "weather",
position: "top_left",
config: {
weatherProvider: "openweathermap",
weatherEndpoint:"/onecall",
type: "current",
lat: 40.748440,
lon: -73.985664,
apiKey: "$WEATHER_API_KEY"
}
},
{
module: "weather",
position: "top_left",
header: "Weather Forecast",
config: {
weatherProvider: "openweathermap",
weatherEndpoint:"/onecall",
type: "forecast",
lat: 40.748440,
lon: -73.985664,
apiKey: "$WEATHER_API_KEY"
}
},
] Sub out your Key and your lat/lon (these are not mine) The api key at first was getting 401 errors, but after a bit it started working, the same key I was using before. Their FAQ mentions it can take a few hours I am not worried about usage. The default If I'm wrong or missed something let me know and I can edit this. edited: the old 2.5 api returned the location name from the location/locationID parms.. the new api uses lat/lon and does NOT header: "somestring to show above the module output", // as you wish for this module AND appendLocationNameToHeader:false, in the config section |
@JHWelch works so far. But how do I get the name of the city back into the header? I now have the name of the city from the corresponding time zone or the capital, i.e. Berlin/Europe. |
@z-master42 you need to change the config set whatever you want in the module header, above the config:{ |
Damn. I must have gone through the documentary five times. Either I always missed it, or I just didn't realise the function of Thank you! |
Hi all,
i did the MM Update few days ago (Notifikation in the bottom bar) via git pull. Until the Update everything worked fine, but since the Update was done, the Weather Module is not loading any more. All other modules are fine after the update. I dont see anything in the logs. Would be great if someone could help me figuring out whats going on.
System: Raspi Zero 2W with PoE LAN Hat
Node: v22.9.0
OS: Debian 12 Bookworm latest update/upgrade
Electron: v32.1.2
MagicMirror Version: 2.29.0
Weather Module API is OpenWeather Map
API Key is valid and checked.
Config-Part of Weather:
Log output if restarting MM:
I dont even see the weather module loading in the log-File? But to be honest, i didnt compeared if it was listed before the update in the log... Unfortunatly i didnt stored any older log files.
The Display shows endless "loading". Can someone have a look on this or maybe guide me into deeper analysis?
The text was updated successfully, but these errors were encountered: