I quickly tried using the Ø to see if it would give any problems, but it just works fines. (Tested on both the Raspberry and my Mac).

Is it incorrect from the start? Or after a while? If it’s after a while (a day) is’t because it doesn’t get updated. (Maybe because of a connection problem)

Nice work! Feel free to add this to the wiki! :)

• Copy translations/en.json to translations/no.json.
• Modify the translations/no.json to Norwegian translations.
• Add your translation to translations/translations.js.

And don’t forget to send us a pull request so others can use it as well! :) (Do do this, you need to make a fork of the repository: https://help.github.com/articles/using-pull-requests/)

Interesting. Don’t know how much time you want to spent on building it, but is would be awesome if you can change the current weather modules in a way a user can configure the weather source. So make it configurable.

If you’re able to make a good stable solution for it (and built it in a way we can add other feeds as well), we could update the core modules.

Just curious: what’s the benefit of Wunderground?

If you wrap the text in a div, you can specify the width of the div using CSS.

Or, what you could do, is:

forecastString = forecastString.replace(". ", ".<br>");

This way the text will be wrapped after a period.

I did some tests:

MM.getModules().withClass('a_non_existing_class') // No issue.
MM.getModules().withClass('') // No issue.
MM.getModules().withClass()// No issue.

So no idea what is causing that problem.

Ok, I looked into it, and it really is pretty simple and obvious when I’ll explain you. So prepare for a “Doh!” moment … ;)

Right before you do the request to WunderList, you empty the items array:
https://github.com/paviro/MMM-Wunderlist/blob/master/fetcher.js#L38

Then if Wunderlist responds, you fill the items array with new items.

This means that as long as your fetcher is waiting for wunderlist to respond, the items array is empty. If in the meantime an other fetcher is finished fetching, it uses the items array to make a full list. But that array is then still empty, waiting to be filled after the wunderlust response.

The solution? Move line 38 (items = [];) to line 51 (above for (var i = 0; i < JSON.parse(body).length; i++) {).

Thats all! :)

Preferrable do this in custom.css. This way you can upgrade your mirror when you need to.

@paviro ah sorry. Throught you were talking about mm2 in general.

For the record: node 6.1.0 is supported.

Will fork your module tomorrow and give it a try.

@benjee yes please. :)

Interesting. Could You open an issue for this on GitHub?

@paviro try debugging the Fetchet on the same way. ;)

I’m on my phone now, so not really able to explain the callbacks. Will do that later.

Regarding the empty lists: try debugging by putting some log statements on places where You receive and send data.

@paviro Yeah, but try to understand what I did. Thats the best way to learn. Let me know what you don’t understand. I’ll explain.

Take a look at how I did this with the newsfeed.

There is a Fetcher object that gets instantiated for every newsfeed. As soon as this feed receives new data it stores it in an instance variable and calls a function of the node_helper (see line 52 of the node helper).

That function then retrieves the the values of all the Fetchers’ instance variables and combines the data. It then sends the socket notification with the combined data.

V2.0.0 is now released: https://forum.magicmirror.builders/topic/76/magicmirror-released