MMM-WunderGround

[nhl]

I’m having the same problems.

[ostfilinchen]

@nhl: i have start the mirror with npm start dev and there was an error for the WU. It says, that there is an origin for the api. So i change the Company Website on the Website of the WU API in http://localhost:8080

After this, i restart the mirror with npm start dev and there is no error yet. I will check this over the Weekend. I hope, this will fix the none-updating-error. :-)

[d3r]

I also have the same problem

[getsarcasm]

Same here. npm dev console log produces the following at the time things go south:

[my_wunderground_api_key]/conditions/hourly/forecast10day/astronomy/alerts/lang:EN/q/pws:[my_selected_PWS].json
[Object, Object, Object, Object]
Uncaught TypeError: Cannot read property ‘hour’ of undefined

Sadly, I’m not familiar enough with NPM or node to work this bug myself.

[ostfilinchen]

@getsarcasm: please update the Module with git pull. @RedNax has updated this

[getsarcasm]

@ostfilinchen Yep, found that mere moments after I sent my message - thanks!

If anyone else happens down this path, the update thread is here:
https://forum.magicmirror.builders/topic/943/mmm-wunderground-not-updating-after-a-few-hours

[RedNax]

Now that the scheduling of teh updates takes place in node_helper.js (server side) and not in the browser it hasn’t missed a beat in a couple days now.
What did however started showing up are estimated’ forecasts due to “These are estimated conditions. There are no weather stations nearby.” conditions. These estimations seem to be made by consulting a potato because (for me) they’re wildly off (more than 10 degrees C).

I’ve just pushed a commit which ignores these estimated forecasts. Also there’s a dramatic level of logging being generated now to pin down any issues you may run in to.

[ostfilinchen]

@RedNax: Now I always get the message that the key does not exist. If i open the URL in the Browser i get the full Response.

[RedNax]

@ostfilinchen Could you pm me the url directly from the pm2 logs so i can investigate this further?

[Steff]

@RedNax
I just updated the module via git pull to its latest version. Reason was not a freeze, but too high temperature values (impression was that I had 10°C too high values, but only after some time). After an initial reboot I got the same error message like ostfilinchen:

2016-11-16T21:55:25+01:00 5 MMM-WunderGround:
{
  "response": {
  "version":"0.1",
  "termsofService":"http://www.wunderground.com/weather/api/d/terms.html",
  "features": {
  }
                ,
        "error": {
                "type": "missingkey"
                ,"description": "you must supply a key"
        }
        }
}

Nevertheless after a restart of MM the problem disappeared, the module does show now the correct termperature. Will keep an eye on it …