oneweathermap

Ray

Hello everyone.
First off I want to let you know I am new to all this and I’m learning a lot from everyone and having a lot of fun doing it.
I recently installed oneweathermap, The newer version where you just use your coordinates as well as your apikey. I did sign up and got my free key, but my problem is is always a hit and miss. Some days it’s very accurate and other days it’s off as much as 4 to 3°. What I have noticed when it gets to 68, It stops working. All other weather stations say it’s in the 70s am I doing something wrong here.the Coordinates that I’m using are Walnut Creek, California 37.9101,-122.0652 , which I got from Google search the original coordinates from oneweathermap showed the same response

from:config.js

{
			module: "MMM-OpenWeatherForecast",
			position: "top_right",
			header: "Forecast",
			config: {
				apikey: "Mykey", //only string here
				latitude: 37.9101,            //number works here
				longitude: -122.0652          //so does a string
		}

from: MMM-OpenWeatherForecast.js

defaults: {
    apikey: "",
    latitude: "",
    longitude: "",
    updateInterval: 1, // minutes
    requestDelay: 0,
    language: config.language,
    units: "imperial",
    displayKmhForWind: false,
    concise: true,
    iconset: "3c",
    colored: true,
    useAnimatedIcons: true,
    animateMainIconOnly: true,
    animatedIconStartDelay: 1000,
    mainIconSize: 100,
    forecastIconSize: 70,
    updateFadeSpeed: 500,
    showFeelsLikeTemp: false,
    showSummary: false,

    showCurrentConditions: true,
    showExtraCurrentConditions: true,
    extraCurrentConditions: {
      highLowTemp: true,
      precipitation: true,
      sunrise: true,
      sunset: true,
      wind: true,
      barometricPressure: false,
      humidity: true,
      dewPoint: false,
      uvIndex: true,
      visibility: false
    },

    forecastHeaderText: "Forecast",
    forecastLayout: "tiled",

    showHourlyForecast: false,
    showHourlyTableHeaderRow: false,
    hourlyForecastTableHeaderText: "Hourly",
    hourlyForecastInterval: 3,
    maxHourliesToShow: 3,
    hourlyExtras: {
      precipitation: true,
      wind: true,
      barometricPressure: false,
      humidity: false,
      dewPoint: false,
      uvIndex: false,
      visibility: false
    },

    showDailyForecast: false,
    showDailyTableHeaderRow: false,
    dailyForecastTableHeaderText: "Daily",
    maxDailiesToShow: 3,
    dailyExtras: {
      precipitation: true,
      sunrise: false,
      sunset: false,
      wind: true,
      barometricPressure: false,
      humidity: false,
      dewPoint: false,
      uvIndex: false
    },

I’m thinking it’s because it’s a free subscription and is limited
Hope you can help
Ray

sdetweil

@ray please wrap text from config.js in the code block…

mark the text, and then hit the icon above the editor that looks like </>

Ray

@sdetweil I’m not sure what it is that you’re talking about.
I put in from:config.js just so everybody knows where I got my information from

I’m new at all this so please excuse my ignorance

sdetweil

@ray so, I asked you to edit your post to make it more readable

I have done it for you

Ray

@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

CheapDad

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.

Wenike

@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?

Ray

@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

Ray

@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

Ray

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.