The hide behaviour is not perfect - takes a few seconds to hide the module - this is because we issue the hide command in case of ‘pfls’ [play flush] and ‘pend’ [play end] metadata commands. Unfortunately, the ‘pfls’ command is followed up with fresh metadata and it takes a few seconds for the ‘pend’ to come from the iPhone.

Tested with playing and pausing repeatedly.

• hide the module if no airplay device is connected / no song playing
• align text & image on left/right depending on the module position (currently both centered in its container)

Its my first attempt at writing anything in node.js so I basically wrote a python script to translate the XML from shairport-sync into json objects.
The module manages a child process which pipes the XML to the Py script and reads the json and displays it.

How did you ever make out with your module? I’ve started down the same path, I’m also using shairport-sync but in conjunction with forked-daapd (an airplay server for Raspbian).

As forked-daapd can also use mpd commands I’ve been trying to use komponist, which I’ve managed to make return the playing song, album, etc. print out to the console but as I’ve never really done any javascript before am trying to piece together building a module for MM.

If you’ve made any progress on your module, I’d love to see it as it may help me finish mine.

The shairport metadata reader is a compiled C program which uses printf to return the metadata to the console:

pi@raspberrypi:~/fifo-js $ ~/shairport-sync-metadata-reader/shairport-sync-metadata-reader < /tmp/shairport-sync-metadata

Artist: "Sohn".
Title: "Tremors".

^C
pi@raspberrypi:~/fifo-js $ 

But I dont’ seem to be able to parse what’s being sent to stdout from my javascript

If anyone has any examples that work, I’d be grateful.

The fifo-js approach works with a fifo file that I echo things into to test, but doesn’t return anything while the Shairport service has it open for some reason?

There is a metadata reader script which I could use to read the metadata and parse it. I’ve compiled the executable and it runs fine. I should be able to call that from my javascript module through child process, right?

const FIFO = require('fifo-js')

let fifo = new FIFO('fifo-testfile')

var count = 1
while (count == 1)
    {
    let text = fifo.readSync(fifo)
    console.log(text)
    }
fifo.close()

I’m getting there. I have an IN and I have an OUT in javascript. Now the hard work of joining the two together - interpreting and the decoding the appropriate metadata begins!

var fs = require('fs')
var fifo = fs.createReadStream('shairport-sync-metadata')
fifo.on('data', function(fifoHexBuffer) {
    fifoHexBuffer = fifoHexBuffer.toString();
    console.log(fifoHexBuffer)    
})

At the moment, the code runs once and stops once it reads. My next task is to have it continue, then I’ll have to make it into a node-helper script, to interact with my base64 decoder/display

So parenthesis are needed to call the function and explicitly not pass it a parameter. Is that right?

this.frombase64();

/* global Module */
/* Magic Mirror
* Module: base64
*
* By Michael Teeuw http://michaelteeuw.nl
* MIT Licensed.
*/

Module.register("base64",{

    // Default module config.
    defaults: {
            text: "Hello World!"
    },


  frombase64: function() {
    var string = 'RGFycmVu';
    var decodedString = atob(string);
    return decodedString;
    },

    // Override dom generator.
    getDom: function() {
            var wrapper = document.createElement("div");
            var decstr = this.frombase64
            var msgstr = document.createTextNode(decstr);
            wrapper.appendChild(msgstr);
            return wrapper;
    }
});

It seems like it should work, but I get a literal string rather than a value returned…