Also took a quick look and found this:
https://aa.usno.navy.mil/data/docs/api.php#soleclipse

Welcome to the magic mirror world!

1. I built one mostly because it was a fun project that is both useful and makes you learn new things at the same time.

2. Much more than I though it would do! My whole family uses it, especially to check the family calendar. I don’t know how we could keep track of all dates before. The second most used thing are the soccer training calenders for my kids. The team provides ical links, so those are updated automatically. Third most used module is the lunch menu for my kid’s shool. Then I have a bunch of other modules that I don’t look at that much. But for example it’s nice to be able to quickly get an overview of the days of the month and see the week number.

3. Maybe not norm, but very common. The release of google hub and similar hints that a home display might be the future.

4. If I would build one again, I might opt for just a screen without the mirror glass. I never use it as a mirror as I prefer the full body mirror that we already had from before. A regular mirror will always have a bit better reflection (unless you buy a crazy expesive OLED screen). This is because the back-light of the screen lights up the entire mirror from behind, even if the screen is black. You notice this the most when it’s dark where the mirror is. Also I want to fill up the entire screen with useful info, so there’s no space left for the actual mirror. :) Altough it has a certain wow factor. So my tips would be…

• First think about if you want a mirror or just a display.
• If you go the mirror route, go with real mirror glass like Pilkington or similar. Investigate carefully on what to buy, there are several different models which lets through different amounts of light.
• Don’t make the mirror larger than the screen. I regret building the frame bigger, as you can see where the screen is due to the back-light.
• Also investigate which screen to buy… I just bought the cheapest one, but I think screen with more contrast will be better behind a mirror (?). Other people can probably contribute more on how much this affects your result. If you use an old screen, it might also be thicker.
• Plan where you want to put the mirror in your home. I think a well-lit area is better. Also close to your socket. And where there’s good wi-fi.

Where are you located? Depending on where, there might be open API’s that gives you access to local services like which day the trash is emptied etc.

@Henrik I had a quick look now and the exception seems to indicate that Parser cannot be found. Perhaps rss-parser package isn’t properly installed. Just to make sure: did you run “npm install” in the MMM-Skolmaten folder? Can you check if rss-parser is installed on your mirror?

…or soccer if you prefer :)

Description

Allsvenskan is the top league in Sweden. I tested all other existing modules, but there were no that included free access to Allsvenskan. So I made my own module.

There is no direct API for Allsvenskan, so this module uses the open Text TV API and scrapes the HTML it generates. Not ideal, but it works (for now).

Screenshot

Download

https://github.com/retroflex/MMM-AllsvenskanStandings

Description

Shows stats (score, matches played and kills) for a set of Fortnite players.
The stats shown are from all seasons and platforms, but you can choose which game modes to show.

Screenshot

Download

https://github.com/retroflex/MMM-Fortnite

I have a problem after the latest update (v 2.2.2). After a few hours (7h one day, 12h another day etc.) my mirror goes completely black. I can show the mirror from other devices though and I can access MMM-RemoteControl. If restarting MM, all modules reappear again, only to fail a few hours again.

I have checked the logs (.pm2/logs/*.log) and nothing is reported about this.
I’m running a pi3 with Jessie 8.0.
The mirror has been running ok for several months before this and all previous updates have gone ok.

My update procedure was this:

1. MagicMirror/> git pull && npm install
2. Got error “Electron failed to install correctly, please delete node_modules/electron and try installing again”
3. Deleted electron folder.
4. Updated npm (sudo npm install -g npm) just to make sure.
5. MagicMirror/> npm install (electron was reinstalled).
6. No errors while updating or running.

I’m running these modules:

• default/alert
• default/updatenotification
• default/clock
• default/calendar
• MMM-MyCommute
• MMM-RemoteControl
• MMM-SkolMaten (x2)
• MMM-ResRobot

Any ideas?

@erq @Henrik Thanks for the tip! I have made a quick solution for now… changed package.json to have dependency to rss-parser v2.12.0.

Checked the rss-parser readme and the latest version (3) has changed it’s interface (“A few minor breaking changes were made in v3…”). If I find the time, I will update my code to support the latest version.

@bimalnair Have you tried to find out which module is causing problems for you yet?

I have finally got a dev log file from the error… As it’s not timestamped, it’s hard to draw any conclusions. But this is one of the lasts logs, which presumably is when the mirror goes black:

[5966:0125/191204:FATAL:memory_linux.cc(35)] Out of memory.
#0 0x0000012a3bb0 
#1 0x0000012b4406 
#2 0x0000012c8ae6 
#3 0x000000d8bb1c 
#4 0x000000d8ba9e operator new()
#5 0x0000012b9ee0 
#6 0x0000012b94ce 
#7 0x0000012ba204 
#8 0x0000012cb2c6 
#9 0x0000012b89f6 
#10 0x000000b58d18 
#11 0x000000a34c38 
#12 0x000000a35a80 
#13 0x000000a349c2 
#14 0x00000221e2fa main
#15 0x000074c0f294 __libc_start_main

I did not check which process is eating all the memory though. That will be the next step.

Other than that I can see in the log that I lost internet connection a couple of times:

fatal: unable to access 'https://github.com/MichMich/MagicMirror.git/': Could not resolve host: github.com

Whoops! There was an uncaught exception...
TypeError: Cannot read property 'feed' of undefined
    at ClientRequest. (/home/pi/MagicMirror/modules/MMM-Skolmaten/node_helper.js:45:20)

And a lot of these logs, which I guess is ok:

Reusing 14 cached departure(s) for module: MMM-ResRobot

Any bright ideas? :)

@Henrik From what I’ve read, a collaborator has write access directly to the repo. You can push code directly as if you are the owner.

My problem was MMM-ResRobot. I deactivated it and kept all other modules and now CPU is at 2% and memory stable over time at around 10%. Not sure if the MM/electron/ResRobot update caused the problem, but it worked ok before. Strange…