Read the statement by Michael Teeuw here.
oneweathermap
-
@ray so, I asked you to edit your post to make it more readable
I have done it for you
-
@sdetweil thank you very much I appreciate that I’m learning so please be patient with me but I’m having a lot of fun doing it
please forgive my ignorance
-
If I’m correct, this means you’re pulling new data every minute:
“ updateInterval: 1, // minutes”
Since free is limited, I wonder if you’re pulling too frequently. You could change the pull to every 10 minutes to see if that changes anything.
-
@cheapdad @Ray It looks like you’ve updated the default values in MMM-OpenWeatherForecast.js rather than putting them into the config section of your config.js? Its generally recommended not doing that because that makes it harder to update the module in the future (you have to save your copy of the file elsewhere, update the module and put your changes back and hope you didn’t break anything by putting your changes back).
In this case, being on the free tier with openweathermap shouldn’t cause issues, as they limit that to 60 calls/minute or 1,000,000 calls/month and you’re only going to hit around 44,640. Unless you’re using multiple modules hitting openweathermap, at which point you could be hitting issues.
Can you try deleting that MMM-OpenWeatherForecast.js file (or at least rename it to not be that name) and do a git pull in that folder, which should pull it down again. Put your changes in the config.js instead and see if that fixes your issues?
-
@cheapdad well, you are correct. I did try doing one minute.
I have also gone as high as 240, which is roughly 4 hours with still the same results for one minute was only an experiment to see what has changed between one minute and 240 and like I said I still get the same results they seem to always be a hit and miss.
I’m new at programming, but I am learning -
@wenike thank you very much for your response.
That’s one thing I have not tried. I will take your recommendation and make all my changes in the config file instead. I have no problem with deleting the program and then reinstalling it is not an issue.I did not know that all changes are supposed to be done in the config file not the main file. I know it now, and I will fix it and let you know
-
Hello everyone, I thought I give everybody an update.
So I decided to wipe everything out and start over from scratch. I had a lot of fun doing it and learned a lot. Everything seems to be running much better. And all my changes are now in the config file. My email even gets retrieved faster than my phone, How funny is that.
onewhethermap though was doing perfectly with only a 1° and 2° off until it reached 81°. Then everything started going downhill. It is still 86° outside but it is displaying 79 so I don’t know what’s going on.
I change the updateInterval: from 10 to 20 and we’ll see how that works.I also wanted to thank everyone for helping me out . I did not know all changes were supposed to be in the config file only. So once again, thank you for that information.
-
@ray Hi Ray :)
Try changing your weather location in the config file. Instead of using the latitude and longitude, try using locationID and using the value from the Open Weather Map site for your area here (from the end of the url):
https://openweathermap.org/city/5406990
So in your case it would be
locationID: 5406990I found that this worked for me when the latitude and longitude didn’t :)
-
@tippon I have actually tried just that When I first installed it and use that exact same number along with the coordinates that onewhethermap suggested but since I upgraded to the newer version. The newer version doesn’t use that anymore. Not to say I can’t add it
I actually change the retrieval time from 10 to 20 so far it seems to be working. I’m getting anywhere between 1° and 2° off which I can accept that even the professionals who give us the weather are sometimes off by 1° and 2° from different stations. So keep your fingers crossed that that will be consistent throughout today.
Thanks for your suggestion though, since I’m new on here. I’m open to any kind of suggestion
-
@ray Try just using the location ID and see if it’s more accurate. I’m pretty sure I had problems when I tried to use both.
You can comment out the coordinate lines by putting // in front of them, so you don’t have to delete and retype them :)
