Hi there, I’ve made a module MMM-WeeklySchedule to show weekly recurring schedules, such as the kids’ school classes, student’s timetable, teacher’s teaching schedule, your gym training classes, or recurring housekeeping tasks. It is made for static information with fine to change manually if necessary.

The request for such module was triggered by @AxLed over at the Modules/Request category. As newbie in this forum I figured that here is the right place to announce new modules.

It is my first mirror module. Your feedback is most welcome.

Below is a screenshot for a pupil’s timetable:

Awesome idea!

And while we are at it, I think that @Mykle1’s excellent step-by-step guides should also have a home in the wiki. The forum is the right place to work them out, but once the instruction have matured they should become part of the project itself.

Thanks, @raywo Works like a charm. Well done also w.r.t documentation, the convenience script for retrieving stationID, and customization! Awesome work.

@AxLed, I also wanted to show today’s class schedules on my magic mirror. Those weekly schedules, e.g. at school or sports clubs, are very reliable and update only with a low frequency. So it is no big deal to change the config every now and then.

I’ve created a module MMM-WeeklySchedule to solve this for me. Feel free to give it a try. Feedback is most welcome.

Cheers.

Du kannst zum Lernen auch erstmal ganz ohne Spiegel arbeiten, d.h. nur mit Raspberry und angeschlossenem Monitor. Wenn du feststellst, dass gut zurecht kommst, machst Du dich an den Spiegel und die handwerklichen Arbeiten.

Hier im Forum findest du eine Reihe sehr guter Schritt für Schritt Anleitungen. Richtig programmieren musst du nicht unbedingt, sondern eher Konfigurationsdateien anpassen und Linux-Befehle (nach Anleitung) ausführen.

Ich würde ebenfalls sagen, nimm es als sportliche Herausforderung …

A good starting point might be the module MMM-dht by @nebulx29. It executes a custom shell command to read data from a sensor. You’ll find the invocation of the script in file node_helper.js. NB: it makes three calls, because it needs three values from the sensor.

In your use case, you’d call Python with your script name instead.

Cool, nice idea

… and thanks to Gene Roddenberry (and others), who invented the Universal Translator.

Yes, you are right about the spirit of this forum. And I fully agree that discussions should be in English, so that everybody can participate and benefit from them. In this thread, however, the user asked explicitly for setup instruction in German. As long as language-specific threads don’t become the norm, I think such request are totally OK, because we should also not exclude people who are not fluent in English.

PS: The EN-DE translation of your post is really good. I’m surprised.

@jorgeg73 said in New to MM:

5 verbose stack Error: ENOENT: no such file or directory, open '/home/pi/package.json’

I’m wondering, why node is expecting the file package.json in the home directory /home/piand not in /home/pi/MagicMirror?!

Are you running npm start from within the MagicMirror directory, i.e. did you do cd ~/MagicMirror first?

Want to show something special for Valentine’s Day on your MagicMirror?

The MMM-Snow module by @MichMich now supports themes. The love theme floods your mirror with ascending hearts.

If you have MMM-Snow module installed already then just add the line for the theme setting like below.

{
    module: 'MMM-Snow',
    position: 'fullscreen_above',
    config: {
        flakeCount: 100,
        theme: "love"
    }
},

Besides the love theme the module features themes winter (original snow flakes) and water (ascending bubbles). Maybe you have ideas for other themes? See also module’s documentation for details on how to add new ones.

Really nice mirror, indeed!

I’ve the same question as @barnosch. Can you share the name of the mirror supplier? You are in Hungary, right? Do they ship to other EU countries?

One syntax error I spot is in uptimeroot module. The curly bracket of config: is not matched. @Mykle1 writes there is even more which I don’t spot immediately.

  {
  	module: 'uptimerobot',
  	position: 'top_right',
        		config: {
  	useColors: true
  	api_key:'u505342-b40737465f0eada9bb8a',
  },

In such cases it is good to do a syntax check of the config. Please run npm check:config to do so. You’ll get a detailed statement of what is wrong where syntactically. The reference @Mykle1 gives above is a must read. It shows an example of what the syntax check provides you.

If a syntax check does not solve the issue, I’d comment out all modules but one and start the mirror. Use /* commented out module */ to make multi-line comments. If start-up works, you add the next module and restart. Repeat this until start-up fails which means you’ve found a(!) module that causes the issue. Please note that there might be more than one wrong module.

If you have the module, copy the desired config elsewhere and redo the module’s configuration with the simplest possible config, which you often find in the ReadMe file of the same module.

Good hunt.

What is an auto feeder machine? Can you please describe in more detail?

Hey @AxLed, sorry for the late reply. I’ve had a look at your code. It looks very good. Well done, man! Functionality is there. Certainly, you can do some cleanup as you say, but that is secondary. It is great that you have extended this module with such nice magic.

One suggestion I made earlier is putting the lookup at the online phone book (dasoertliche.de) & parsing into its own module. This would allow others to write phonebook lookup modules for their own country. I’m happy to do this change on your code base.

You did all the (sometimes confusing) Git stuff right: you forked from the original repository, checked out your repository, made changes, committed and pushed them back into your repository. There was just one step too much, which is the pull request. You typically make a pull request in the person’s repository that you have forked from to tell the original author ‘hey, here is cool new stuff that you may want to have in the original repository’. I would suggest that you accept or remove your own pull request.

If you want me to extract a module for the phonebook lookup & parsing, I can work on the latest version of your repository and either push directly to your repo (if you grant me write access) or I send my own pull request to you.

@zack949, could you report back after you got it solved? I think this is an interesting use case, which might be relevant for more people.

If you start your mirror with pm2 as suggested in documentation, then you can use commands like pm2 stop mm, pm2 restart mm, pm2 start mm to control your mirror.

I would make three different start scripts, e.g. mm1.sh, mm2.sh, and mm3.sh, where each one starts one specific instance. This is in line with @ninjabreadman’s suggestion to have three install directories.

A good starting point might be the module MMM-dht by @nebulx29. It executes a custom shell command to read data from a sensor. You’ll find the invocation of the script in file node_helper.js. NB: it makes three calls, because it needs three values from the sensor.

In your use case, you’d call Python with your script name instead.

Any updates on this? I have the same problems as @DocVooDoo and others, i.e. Adafruit code works like a charm, dht_var not.

Difference I noticed is that dht_var uses wiringpi library and Adafruit not?! I tried a reinstall of wiringpi package without success.

Next, I compared the implementations of dht_var and the Adafruit driver for DHT22.

The essence of the Adafruit code is in file Adafruit_Python_DHT/source/Raspberry_Pi_2/pi_2_dht_read.c. It is meant for Pi2 and Pi3, implemented in C, and defines a function int pi_2_dht_read(int type, int pin, float* humidity, float* temperature). It implements the communication with the sensor using a 1-wire bus. The rest of the Adafruit package is mostly (well-done) sugar-coating for Python usage and selecting the right driver for any given platform.

We could simply rewrite dht_var by using this driver code. What do you think?

Very nice. Well done!

I’m also thinking about controlling LED stripes, but wanted to do this more low-level like in this Adafruit project. What components are you using for controlling them via USB?

… and thanks to Gene Roddenberry (and others), who invented the Universal Translator.

Yes, you are right about the spirit of this forum. And I fully agree that discussions should be in English, so that everybody can participate and benefit from them. In this thread, however, the user asked explicitly for setup instruction in German. As long as language-specific threads don’t become the norm, I think such request are totally OK, because we should also not exclude people who are not fluent in English.

PS: The EN-DE translation of your post is really good. I’m surprised.

Das ändert man im Stylesheet (*.css). Im Code des Compliments Moduls wird beim Aufbau des DOM drei Klassen thin xlarge bright gesetzt, siehe hier.

Viele Module bringen ihre eigene CSS Datei mit, doch Compliments verwendet das CSS main.css. Die Definition von xlarge ist für die Schriftgröße zuständig, siehe hier.

Du kannst jetzt beispielsweise so vorgehen:

• kopiere main.css nach mystyle.css im Verzeichnis MagicMirror/css
• benutze die Konfiguration customCss um dein mystyle.css anzuwenden, siehe README
• füge in mystyle.css eine eigene Größenklasse mysize ein, orientiere dich zunächst an xlarge
• ändere die Konfiguration von Compliments so, dass dort statt xlarge deine Klasse mysize benutzt wird. Dafür gibt es ein Setting namens classes, siehe README von Compliments.

Alternativ, d.h. ganz ohne eigenes CSS, kannst Du auch nur den letzten Punkt anwenden, wenn Du mit einer der in main.css bereits vorhandenen Größen-Klassen large, medium, small und xsmall zufrieden bist.