I just gave the forum a little kick and restarted it. Does it solve the issue?

Awesome work!

Would be great if you could configure keywords which show/hide certain modules and configure notifications … something like this:

keywords: {
    'HIDE WEATHER': {
        hide: ['weather']
    }
    'SHOW WEATHER': {
        show: ['weather']
    },
    'SIMPLE MODE': {
        hide: ['default','foo','bar'],
        show: ['simple'] 
    },
    'RESTART': {
        notification: 'RESTART'
    }
}

It might be good to know that I’ll probably be implementing this in the coming weeks: https://forum.magicmirror.builders/topic/241/revising-the-show-hide-mechanism

An other small suggestion: delay all show effects with the a delay equal to the animation time. This way all Modules that will need to hide will nicely hide before any new modules fade in.

The PR was just merged into the develop branch. I’ve added a translation for Dutch as well.

It works perfectly fine on a Mac. To be honest: this was one of the goals during the development (because of this project: http://michaelteeuw.nl/post/150349424992/mirror-mirror-on-the-wall-who-has-the-biggest-of).

To install it, make sure you have the latest version of node installed. You can download the installer here: https://nodejs.org/dist/v6.8.0/node-v6.8.0.pkg

Next, open your terminal, and clone the MagicMirror² repository:

git clone https://github.com/MichMich/MagicMirror.git

Then, go to the MagicMirror folder and run the installer.

cd MagicMirror
npm install

Make a copy of the sample config to your custom config:

cp config/config.js.sample config/config.js

Run MagicMirror to see if it works:

npm start

If everything works fine, you can modify your config to match your preferences …
If you want to run it full screen on a mac, you might want to enable the kiosk mode in the config. (See documentation: https://github.com/MichMich/MagicMirror#configuration)

Enjoy!

You can modify the styling of your mirror using css/custom.css.

Starting from MagicMirror² v2.1.0 (currently in develop stage) the default calendar module will broadcast all the events to all other modules with the notification message: CALENDAR_EVENTS. The event objects are stored in an array and contain the following fields: title, startDate, endDate, fullDayEvent, location and geo.

Since this feature is still in the develop branch, it’s not final and might change. Suggestions are welcome.

I’ve just finished the translation system which now includes core translations files and a solid fallback mechanism. This way your modules can benefit from existing translations (in the core translations files).

All the translations used by the default modules are defined in the core translation files, making is easy to translate the core of the system. Of course, 3rd party modules should use their own translation files.

The translation files can be found in /translations . Pull request with new or improved translations are more than welcome!

Note: although comments are officially not supported in JSON files, MagicMirror allows it by stripping the comments before parsing the JSON file. Comments in translation files could help other translators.

If you built your own module, and you run into translation strings from which the core system could benefit (generic texts), feel free to send a PR with updated translation files.

Please note that the guide you followed is ⚠︎EXTREMELY OUTDATED⚠︎. Please check this guide:
https://forum.magicmirror.builders/topic/236/complete-setup-tutorial

Just curious, why would you modify any file other than the config.js and the custom.css file?

If a module currently hides an other module (let’s say, for example by using the facial recognition module) and an other modules hides and shows the modules (for example my mqtt-alarm-welcome module), stuff get messed up. The second module shows modules that still needs to be hidden …

I’m thinking about changing this behavior, by letting modules take a hidden lock on a module. This means the module will not appear as long as that module does not say it should be shown. This could be done by using a lock identifier (which could simply be the module’s identifier).

To explain it a bit better, here is the scenario with a 3-module mirror (all code below is just as an example, not real code):

Module B asks module A to hide:

moduleA.hide(lockString: "module_b_identifier");

Module A is now hidden, and has an lock array with the following strings:

moduleA.locks = [
    "module_b_identifier"
]

Module C asks module A to hide:

moduleA.hide(lockString: "module_c_identifier");

Module A is now hidden, and has an lock array with the following string:

moduleA.locks == [
    "module_b_identifier",
    "module_c_identifier"
]
moduleA.hidden == true

Module B asks module A to show:

moduleA.show(lockString: "module_b_identifier");

The lockString will be removed from moduleA’s locks array, but since there still is an other lock string available, the module remains hidden:

moduleA.locks == [
    "module_c_identifier"
]
moduleA.hidden == true

Module C asks module A to show:

moduleA.show(lockString: "module_c_identifier");

The lockString will be removed from moduleA’s locks array, and since this will result in an empty lock array, the module will be visible:

moduleA.locks = []
moduleA.hidden = false

Does this make sense to you guys? Is there an other scenario I should take into account? Let me know your feedback so we can work towards a more stable show/hide mechanism.

Yeah, probably gonna move current master to 1.0, move v2-beta to master, and create a develop branch. Agree?

I pushed an update to the develop branch. Please give it a try.

@yawns Thanks! 😂

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! :)

Since I open sourced MagicMirror², I have received many awesome pull requests adding a lot of nice features to the Magic Mirror core. I am very grateful for that! Unfortunately, this comes with a downside: the application gets a lot more complicated.

I started an issue on GitHub to discuss the idea of simplifying the core of MagicMirror². Please let me know what you think! (Preferably in that issue).

https://github.com/MichMich/MagicMirror/issues/1860

Thanks!

I’ve recently reinstalled my Pi and installed the latest built of the develop branch.
I have a small update script which eventually restarts MagicMirror using pm2 restart mm.
Unfortunately, it won’t restart because it says port 8080 is already in use.

The only solution is rebooting the Pi.

Before I spend some time on solving this, I’m curious: does restarting work on your pi? And are you running the latest develop branch as well?

@KrawallKurt I know, but this is an article in which I collaborated with MagPi.

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.

Please only submit reproducible issues to GitHub.

If you’re not sure if it’s a real bug or if it’s just you, please open a topic on the forum: https://forum.magicmirror.builders/category/15/bug-hunt - Problems installing or configuring your MagicMirror? Check out: https://forum.magicmirror.builders/category/10/troubleshooting

When submitting a new issue, please supply the following information:

Platform [ Raspberry Pi 2/3, Windows, Mac OS X, Linux, Etc … ]:

Node Version [ 0.12.13 or later ]:

MagicMirror Version [ V1 / V2-Beta ]:

Description: Provide a detailed description about the issue and include specific details to help us understand the problem. Adding screenshots will help describing the problem.

Steps to Reproduce: List the step by step process to reproduce the issue.

Expected Results: Describe what you expected to see.

Actual Results: Describe what you actually saw.

Configuration: What does the used config.js file look like? (Don’t forget to remove any sensitive information.)

Additional Notes: Provide any other relevant notes not previously mentioned (optional)