Basically I rebuilt our Magic Mirror monitor in a very similar way like @MichMich. I did order the same 24" monitor at Amazon (thanks to @MichMich for the great instruction). The installation of the software on the raspi3 was really simple and showed great results on a test monitor.

What I could not imagine that it was nearly a nightmare to get a spy glass at a local glacier in Munich, however after many mails and phone calls, I was able to find a local glacier. (More details on this part of the story here.

As promised in this separate thread here are some pictures of my MagicMirror.

Let us start with the final result, and I am more than happy with it, the wife acceptance factor is great as well and especially my nine year old boy loves it, since he helped to do a lot of the assembly stuff together with me :).

You can see at the right bottom a small IR sensor, since I do not have a 3D printer, I have sawn the casing yesterday manually, it still needs to be painted, currently I am testing it and trying to get the module running.
What I did differently is the way to mount the mirror. I am using two pieces of wood cut in 45° angle enforcing a direct fit and very reliable and stable mounting position of the MagicMirror. Details you can see in the following pictures. Note: If you are wondering about the power supply, I simply drilled a hole through the wall, since a power plug was much nearer that at the mounting position.



The interior looks like this:

There is one thing I am unsure about. I have noticed that the controller unit (inverter/ controller) of the monitor has slightly shifted. Maybe I “pressed” the HDMI cable too much and therefore it got dislocated. You can see this in the last picture.
Did anyone of you observe this as well ? I am considering to stabilize it again mechanically by construction something in wood.

In case you have questions do not hesitate :).

Regards
Stefan

@ramonbovenlander said in MMM-Remote-Control & MMM-webradio:
I love your idea, just had the same thought to extend the Remote Control with an option to play radio on demand.
Did you upload your module already somewhere in github ? If yes, could you please share the place ?

Description:

This is an extension for the MagicMirror. It can show/hide a webradio stream provided by Radio.de You can start and stop this web radio stream by hiding the module. It uses the suspend/ resume method of MagicMirror for this. Currently the setup is rather simple. Potential extensions for the future might be selection of the radio station via remote control plugin, tuning of volume. Currently I do use the module to start in the evening the favorite radio channel of my children and to stop it again once they do sleep.

Screenshots:

Download:

[card:SteffMUC/MMM-RadioDe]

Version 0.1.0

• First initial commit
• Feedback highly welcome!

@strawberry-3-141 Now I do have the similar problem for 1. FSV Mainz 05.
Adding this line in the .js file solved it:
“1. FSV Mainz 05”: “https://upload.wikimedia.org/wikipedia/commons/thumb/d/d6/FSV_Mainz_05_Logo.png/100px-FSV_Mainz_05_Logo.png”
Do you think it might make sense to include it as well on github ? Thanks

Kindly apologize, seems like the link was not really working:
http://www.pilkington.com/de-de/de/produkte/produktkategorien/spezialglaeser/pilkington-mirroview

Some enhancements done in the meanwhile:
a) The CPU temperature was always above 60°C so I added two heatsinks and one small ventilator. Since then my CPU temperature is always below 50°C (mostly around 40-44 °C).

b) I did ask in my first post whether someone had the problem that the inverter of the monitor did move. Well, in my case I did have this problem, so added some wooden holders to ensure that the inverter stays at the place intended to be.

c) In the area where I mounted the mirror on the wall it is even during daylight quite dark. So the mirror did not really show its intended mirror effect. In order to get more light directly in the area of the mirror I mounted 3 LED spots on top of the mirror. Now I do have extremely good conditions. :)
View of the 3 LED spots:

View with the LED spots in operation:

@johnnyboy Potentially you changed something in MMM-WunderGround.jsand you have forgotten about. I am writing potentially because I had a similar situation some month ago with compliments.js- I thought that I definitely have not changed anything, but I had done it and forgotten about it. An extremely simple way to come around this problem:

pi@papaspi:~/MagicMirror/modules/MMM-WunderGround $mv MMM-WunderGround.js MMM-WunderGround_mychangedfile.js
pi@papaspi:~/MagicMirror/modules/MMM-WunderGround $git pull

Now the update should work and if find some changes you still need from your file you can easily extract them from your backup copy MMM-WunderGround_mychangedfile.js.

@Steff Ordered mine today at http://www.glas-schaubeck.de/, 6mm thickness, could verify it beforehand with a sample, will get it next week, once done with it, will post it in the built mirror section.

Munich, Germany

Looks really really nice, I like especially how you integrated the PIR sensor :)

Encountering the same problem, however npm install throws an error message:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: magicmirror@2.26.0
npm ERR! notsup Not compatible with your version of node/npm: magicmirror@2.26.0
npm ERR! notsup Required: {"node":">=18"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v16.20.2"}

The “normal” update of my raspi via sudo apt- update & upgrade did not bring any changes, I had to update the node version manually:

Update node version
Please do not forget to log-off / log-on after nvm installation

This helped now the npm install did run through and my magic mirror start again.

Hope this is helpful for others who are encountering the same problem…

@mpires
Here is the configuration:

                {
                module: 'MMM-ModuleScheduler',
                config: {
                notification_schedule: [
                                // TURN THE MONITOR/SCREEN OFF AT 8:30 EVERY WEEK DAY
                                {notification: 'REMOTE_ACTION', schedule: '30 8 * * MON-FRI', payload: {action: "SHUTDOWN"}},
                                // TURN THE MONITOR/SCREEN OFF AT 23:30 EVERY DAY
                                {notification: 'REMOTE_ACTION', schedule: '30 23 * * *', payload: {action: "SHUTDOWN"}},
                            ]
                         }
                },

The clock timer is programmed to kill the power supply 15 min later than the shutdown time(s).

I am using a “dual” solution: I do use a PIR sensor together with the MMM-PIR module to switch the monitor to standby via HDMI off. Since the Raspi and the monitor are still consuming energy, I thought about when I do really use my MagicMirror. So I came to the conclusion that I never use and need my MM during night and during my working hours in the week. So I bought a rather cheap clock timer with the capability to program it per day. Every day the MM is switched completely off during night time and every work day during my work time. In order to prevent any potential SD card failure I do use the module MMM-Scheduler to shut down the Raspi well in advance before power is cut. If there is interest I can post the configuration of MMM-Scheduler.

@johnnyboy Potentially you changed something in MMM-WunderGround.jsand you have forgotten about. I am writing potentially because I had a similar situation some month ago with compliments.js- I thought that I definitely have not changed anything, but I had done it and forgotten about it. An extremely simple way to come around this problem:

pi@papaspi:~/MagicMirror/modules/MMM-WunderGround $mv MMM-WunderGround.js MMM-WunderGround_mychangedfile.js
pi@papaspi:~/MagicMirror/modules/MMM-WunderGround $git pull

Now the update should work and if find some changes you still need from your file you can easily extract them from your backup copy MMM-WunderGround_mychangedfile.js.

@Disturbx Wanted to post a reply already yesterday, but was too stupid to use git push…, I modified the behavior slightly, letting the module wait until the others are started, added as well some changes. I put them to the develop branch, so if you change your git to develop, you can try whether this helps.
How to do:
Enter local directory of module --> git checkout develop --> git pull
Why develop branch ? I did only test on my development platform, but not on the Raspi itself.
Feedback highly welcome

@Jopyth Thanks so much, you saved my day, I really had forgotten git push, stupid me. Thanks again !!

Hi all,
I have to admit that I am an absolute newbie for working with github. However after reading several forums, the online help and trying back and forth I still have not found a solution to my problem and I am really clueless.
I have released a couple of weeks ago my first basic module for MM on github.
I wanted to further develop the features of the module, but wanted to do it in a separate branch develop.
I create this branch via git branchand git checkout. I checked in my modifications to the develop branch with git commit -a.
A git check status shows:

On branch develop
Untracked files:
  (use "git add ..." to include in what will be committed)

	backup/

nothing added to commit but untracked files present (use "git add" to track)

I did not yet exclude the backup directory in gitignore.
If i call git logI can see:

commit ce4fca6491a4cd8facb44482ce2f17cbd335e7a4
Author: xxx
Date:   Wed Feb 22 20:42:56 2017 +0100

        modified:   CHANGELOG.md
        modified:   MMM-RadioDe.js
        modified:   README.md

commit db495c121e2dd8f38b1e2f67fd0101f918d11190
Author: xxx
Date:   Tue Feb 21 19:07:07 2017 +0100

    - requiresVersion: "2.1.0",
    - option to change playing radio station via notification
    
    - Added documentation for daily operation in [README.md](README.md# Daily operation)
    - Added check for all modules started, before starting radio player
    
    - Known problems: One user reported that player does not start, potentially fixed by starting player only once all modules started

My problem: I cannot see these changes online in the web interface of github, trying to see my changes in github it claims no differences between master and develop branch (identical).

I strongly hope that this is an absolute beginners error, nevertheless I am running out of ideas. Could you help me ?
Thanks
Steff

Hi all, since @Disturbx (Forum Link MMM-RadioDe) wrote that “my” MMM-RadioDe module does not operate on his mirror but in browser view, I started some more debugging by starting the MMM with npm start dev and I can see some warnings/ error messages I do not understand:

pascalprecht.translate.$translateSanitization: No sanitization strategy has been configured. This can have serious security implications. See http://angular-translate.github.io/docs/#/guide/19_security for details.
VM108 vendor.js:9 Error: Blocked a frame with origin "http://www.radio.de" from accessing a cross-origin frame.
    at Error (native)
    at http://www.radio.de/inc/microsite/js/app.js:2:5158
    at http://www.radio.de/inc/microsite/js/vendor.js:9:25272
    at o (http://www.radio.de/inc/microsite/js/vendor.js:8:4062)
    at http://www.radio.de/inc/microsite/js/vendor.js:8:6140(anonymous function) @ VM108 vendor.js:9(anonymous function) @ VM108 vendor.js:8(anonymous function) @ VM108 vendor.js:9o @ VM108 vendor.js:8(anonymous function) @ VM108 vendor.js:8
playlog:1 GET https://api.radio.de/info/v2/user/playlog?status=Trying%20to%20connect...&s…9h5&reconnect=0&waittime=0&apikey=df04ff67dd3339a6fc19c9b8be164d5b5245ae93 403 (Forbidden)
playlog:1 GET https://api.radio.de/info/v2/user/playlog?status=Stream%20started%20to%20pl…&reconnect=0&waittime=1002&apikey=df04ff67dd3339a6fc19c9b8be164d5b5245ae93 403 (Forbidden)
playlog:1 GET https://api.radio.de/info/v2/user/playlog?status=Heartbeat&station=antennek…reconnect=0&waittime=60751&apikey=df04ff67dd3339a6fc19c9b8be164d5b5245ae93 403 (Forbidden)
playlog:1 GET https://api.radio.de/info/v2/user/playlog?status=Heartbeat&station=antennek…econnect=0&waittime=120991&apikey=df04ff67dd3339a6fc19c9b8be164d5b5245ae93 403 (Forbidden)
playlog:1 GET https://api.radio.de/info/v2/user/playlog?status=Heartbeat&station=antennek…econnect=0&waittime=180995&apikey=df04ff67dd3339a6fc19c9b8be164d5b5245ae93 403 (Forbidden)

I do not understand the warning translateSanitization. Did anyone of encounter a similar warning in his module development and could point me in the correct direction ?

From the other error messages I do get the impression, that my invocation of the web radio player tries to open a frame, but I am not sure… Any hints appreciated.

Furthermore I thought about to start the webradio player only once after all modules are started:

Set a variable this.all_started to after ALL_MODULES_STARTED and start radio only once this is successful. Do you think this would be a good way ?

    notificationReceived: function (notification, payload, sender) {
      if(notification === "ALL_MODULES_STARTED"){
        this.all_started = true;
        Log.info("Received notification ALL_MODULES_STARTED setting all_started to  : " + this.all_started);
      }else if(notification === "RADIO_STATION"){
        Log.info("Received RADIO_STATION" + payload.title + "   "+ payload.type);
        this.config.station = payload.title;
        this.updateDom(300);
      }
    },

    getDom: function() {
      var wrapper = document.createElement("div");
      if (this.display && this.all_started) {

        var script = document.createElement("div");
        script.innerHTML = "<div></div>

@Disturbx Honestly I am completely clueless. I did some updates today to several modules and now my MMM crashes after some time. I am not sure whether it is related to the radio module. I am currently debugging this, potentially I get an idea from this. The only thing I can offer you is to post you a configuration how you could to the similar setup with the iFrame module, if you are interested in. (Without station select, start/ stop via hide mechanism)

Hm, Just tried it in my own MMM, with following config:

{
        module: 'MMM-RadioDe',
        position: 'top_right', // This can be any of the regions.
        classes: 'scheduler',
        config: {
                // PLAY RADIO BETWEEN 18:50 and 21:00 EVERY DAY
                //module_schedule: {from: '50 18 * * *', to: '00 21 * * *' },
                // See 'Configuration options' for more information.
                api_key: 'xxxxxxxx',
                station: 'slam'
                }
        },

In my case it immediately start on my magicmirror:

You mention that it does not start, did you set potentially the autoplay option to false ?

Could you please post your config ?