Closed mirrormonark closed 9 months ago
I noticed that the old form called "Onecall" no longer exists and was used for this module it seems to me. It is a 2-3 year old module but there is nothing left.. neither dev nor module... I have the folder
Where did you get that module: "onecall/loader"
? I have never seen such a module.
Try this:
{
module: "MMM-OneCallWeather",
position: "top_right",
pages: {"daily":"top_right"},
disabled: false,
config: {
latitude: "XXXXX",
longitude: "XXXXX",
apikey: "XXXXX",
apiVersion: "3.0"
}
},
Of course you have to replace the XXXXX parts :slightly_smiling_face:
When did you create your apikey?
apikey with openweather... apikey only free not buy.
The OneCall module was a module to take the API is use it more than once but making the call look like only once. That was how it worked.
The OneCall module contained the possibility of having APIs per hour, daily, in anticipation,
it doesn't work.. :(
The OneCall module was a module to take the API is use it more than once but making the call look like only once.
Sounds nice. Where did you get it?
it doesn't work.. :(
I think we will figure it out. What does npm run config:check
say? (you have to run it in the MagicMirror folder)
When did you create your apikey? I'm asking this to find out if it's a key for apiVersion 2.5 or 3.0.
npm run config:check say "Your configuration file doesn't contain syntax errors :)"
I found this guy who forked the dev... That doesn't work either. Try . https://github.com/handwrittenjello/onecall
maybe you could implement it in your fork
I own 2 apikeys. one made this year (2 days ago) while the other was made in 2020 I think so it should be 2.5
I found this guy who forked the dev...
This is definitely interesting. I'll take a look. I don't have the time for new functions at the moment. But some troubleshooting is okay.
I own 2 apikeys. one made this year (2 days ago) while the other was made in 2020 I think so it should be 2.5
Please try the following: Remove all modules from your config and add only this module with the new apikey:
{
module: "MMM-OneCallWeather",
position: "top_right",
pages: {"daily":"top_right"},
disabled: false,
config: {
latitude: "XXXXX",
longitude: "XXXXX",
apikey: "XXXXX",
apiVersion: "3.0"
}
},
If that doesn't work: Which node version (node -v
) and which npm version (npm -v
) do you have?
I did what you asked (delete all modules) but it always tells me "upload". As for the versions here it is: node version: v16.19.1 npm version: 8.19.3
hey i see this.. [MMM-OneCallWeather] 14-Mar-23 00:05 ERROR AxiosError: Request failed with status code 401
Okay, this is an indication that something is wrong with the key.
Can you create a third key and send it to me in a private message via the forum? After the test you can delete it again. I would test how the correct setting must be for your keys.
But I'm going to sleep soon. So I won't answer anymore today.
goodnight :)
Something is wrong with the key you sent me. I always get the following error message: "Invalid API key. Please see https://openweathermap.org/faq#error401 for more info."
(with the onecall endpoint in version 2.5 and 3.0). But the weather endpoint, on the other hand, works with your key. That's strange.
I also created a new key for myself and it works with that - I have only the Free plan. I'm running out of ideas 😕
Is it possible that the free plan provides that only one API can be created? because I didn't delete the others. Can we prove this? Did you sir have a API created or do you have more than one for testing?
I currently have two keys in my OpenWeatherMap account. One that I use productively and one for testing. Both work fine.
I apologize, I can ask you all the steps you do on the OpenWeather site... I think to me that I did not enable the OneCall then..
On the My services page, the following should be in the "Price Plan" column: "Free Plan".
On the API Key page you can generate new keys.
the weather modules I use are: MMM-WEATHERBACKGROUND MMM-OPENMAPWHEATHER MMM-NOAA3 MMM-PLACEINFO
I use them on separate pages so not all together. Could it be that one of these gives problems to the module?
i try.. OFF all this module but nothing
API calls return an error 401
You can get the error 401 in the following cases:
You did not specify your API key in API request. Your API key is not activated yet. Within the next couple of hours, it will be activated and ready to use. You are using wrong API key in API request. Please, check your right API key in personal account. You are using a Free subscription and try requesting data available in other subscriptions . For example, 16 days/daily forecast API, any historical weather data, Weather maps 2.0, etc). Please, check your subscription in your personal account
MMM-weatherforecast this is only work for forecast for me
Hourly forecast: unavailable Daily forecast: unavailable Calls per minute: 60 3 hour forecast: 5 days
i believe is this the problem. with free api and i believe i have api 2.5 e not 3.0
Hourly forecast: unavailable Daily forecast: unavailable Calls per minute: 60 3 hour forecast: 5 days
I have the same.
but for you working??
Yes, it works perfectly.
maybe the problem is because use 4-5 modules with openmap
hi how are you? let me inform you that i figured out the problem on this form...i simply paid the site subscription for the plan and everything works. i had not entered any card before.
Interesting. Then new free API keys might not work anymore? 😮
i don't think so. simply i did the api onecall plan... i put in my cash card and i have like 1000 free calls if i exceed i pay.
@KristjanESPERANTO hello I installed your MMM-OneCallWeather
module thanks to
@sdetweil, he helped me with this module and many other things and I have a question in the readme he wrote there:
"colored If set 'colored' to true the min-temp get a blue tone and the max-temp get a red tone.
Default value: true" I added this to my js.config but the values remain white am I doing something wrong?
@Manu85340 Please open a new issue and show there your config (without API key) :slightly_smiling_face:
I'm closing this issue because mirrormonark was able to solve the issue by switching to a paid key.
My config:
I'm using the modules "page-indicator" and "page-selector" in my mirror