The calendar module has a config setting fetchInterval. Please see calendar documentation for details.

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

First thing I’d try is logging HTTP request and response into a file to collect some more details to reason on. Don’t forget to log timestamps and all headers.

Having said that, I think @NateDee’s explanation makes a lot of sense to me.

I’ve had a look at the node-web-scraper in the Git you reference above.

Line 7 of server.js binds the web scraping functionality to a HTTP Get endpoint http://localhost/scrape . It uses the Express framework to do so, see var app = require('express') and then app.get(...). You find a nice introduction to Express on the project’s website.

app.get('/scrape', function(req, res){
...
  request(url, function(error, response, html){
  ...
  })
})

You may want to extract the essential functionality and then put it into the module. This essential functionality is in the request call in lines 11-33. Maybe make a method getNameByLookup(caller) in node_helper.js of the MMM-Fritz-Box-Callmonitor. This should do the request to the online phone book page, use cheerio for scraping, and extract the relevant information.

Once you have this method, call it inside getName(caller)as described in my previous post. Because you are taking the request out of the callback of app.get you get rid of this hosting on localhost. The express hosting is great for testing scraping functionality, but not so beneficial for a MM module.

I think you’ve solved the tricky part already, i.e. finding the correct data source on the web and scraping the relevant information. Moving this into the module should be comparably easy.

You may want to fork the Git of MMM-Fritz-Box-Callmonitor, make a new branch (e.g. reverseLookup) and work there. This also allows you to channel back your change into the original module by sending a pull request (PR) to the module author. I’m happy to help if you tell me where your Git repo is.

I like this idea! @paviro, the developer of MMM-FR´TZ-Box-Callmonitor is certainly the better person to explain, but the idea intrigues me and I had a look at the module’s code on GitHub.

The relevant code for name resolution is in node_helper.js, line 150:

var callInfo = {
    "time": moment(call.Date[0], "DD.MM.YY HH:mm"), 
    "caller": self.getName(call.Caller[0])
};

if (call.Name[0])
{
    callInfo.caller = call.Name[0];
}

When going through the list of callers, the modle calls getName(caller) which is responsible for resolving the caller. This method does in essence this (node_helper.js, line 33):

if (number_formatted in this.AddressBook) {
    return this.AddressBook[number_formatted];
} else {
    //Not in AdressBook return original number
    return number;
}

So it basically checks if the number is in the preloaded address book and if not it returns the original number.

I would put your reverse lookup here. In case the reverse lookup fails simply return the original number as is.

Try to condense the essence of the reverse lookup into a single method (potentially located in its own module), so that it does not require calling the localhost address in browser. Once this runs, I’d cache all numbers that were successfully resolved so that you don’t have to do the lookup again and again for the same number.

Sorry, it is hard to tell more as I know too little about your reverse lookup code.

Cool, nice idea :)

Ich kann nur emfehlen, sich Backups der laufenden config.js zu machen. Details siehe oben.

In der Regel fehlt nur eine Klammer oder ein Komma. Probiere mal folgendes Kommando npm run config:check. Es checkt deine config.js und zeigt Dir Syntaxfehler in der Datei. Du musst dafür im Verzeichnis ~/MagicMirror stehen.

Oops, ihr wollt den Browser beenden. Mein Kommentar bezieht sich auf die Shell, sorry.

Nice module, indeed. Just an idea: Raspberry Pi 3 has Bluetooth. Would be cool to connect BT speakers and play the radio.

We could also use it for remote audio notification". Say, the mirror is linked to a BT speaker in the next room and it plays a sound when certain notification is received, e.g. new mail …

Anybody tried this?

@35110 Strg+C bricht den aktuellen Prozess ab.

Praktisch ist auch Strg+Z. Das pausiert den Prozess. Anschließend kannst Du ihn mit bg in den Hintergrund verbannen und im gleichen Putty-Fenster etwas anderes machen. Mit fg holt man Hintergrundprozesse wieder in den Vordergrund.