i, and others also, have the Problem, that the module works for a few hours and then stops updating with no error in pm2 logs or on the mirror.
Is there an Problem with the updatedom or what can i do?
I’m having the same problems.
@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. :-)
I also have the same problem
Same here. npm dev console log produces the following at the time things go south:
[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 Yep, found that mere moments after I sent my message - thanks!
If anyone else happens down this path, the update thread is here:
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.
@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.
@ostfilinchen Could you pm me the url directly from the pm2 logs so i can investigate this further?