@stephenmelody Next step is to run your mirror and make sure nothing has changed.

This thread should help: https://forum.magicmirror.builders/post/7634

@stephenmelody Empty responses are good. That usually means no problems. Once you have your command line back, you’re free to proceed.

@fox Did you try reinstalling electron via the instructions given? ie, delete /home/pi/MagicMirror/node_modules/electron and reinstalling?

This should be close:

cd /home/pi/MagicMirror/node_modules
sudo rm -rf electron
cd ..
npm install electron@1.4.15

After that, I suspect a npm install and then npm start.

@gshimself Can you post your config.js for us? Remember to use the markdown text and hide any API keys in your file.

@Sputnik Hrm. Try this one: comment out the PM2 command in your script. Reboot your mirror and let Alexa start up normally. Open up an VNC connection to your mirror and then run the PM2 command. Give it a minute or so and see if that kills your connection. VNC is a desktop sharing app, so it’s going to be kind of bandwidth intensive. If you can just use SSH, you might find the network performance acceptable.

@yawns Someone around here reported that they successfully used a microwave proximity sensor. I’ll probably go that route.

A friend of mine wants to make a magic mirror for his bathroom and he wants to replace the existing mirror. It’s elliptical, so he wants the monitor to fit within the circumference of the mirror glass and he’s going to set it into the wall a bit.

Does anyone have any experience with this? Is there anything I should be on the watch for? On the positive side, I should be able to mount the motion sensor behind the glass instead of drilling into the frame.

@Esinem It seems that you do not have Electron installed on your Pi. If you install electron, it should overcome that error.

First, go to your home directory: cd ~
Then install electron: npm install electron@1.4.15
Once that is complete, try starting the mirror again.

Good luck!

NOTE: This won’t work (see below). Instead cd ~/MagicMirror.

@TGBB No, it won’t work. The reflective coating on the back of your cheap mirror is an all-or-nothing thing. If you scrape it off, you’re basically turning your mirror into a window.

Do some searching for a glass manufacturer. I know there are several people on this forum from the UK. Surely they can point you in the right direction. Worst case scenario, you can talk to your local glass shop / glazier and ask them to broker the purchase for you. That way you can depend upon their expertise in the industry to source the mirror for you.

I think it’s definitely an ambitious dream! At the present time, the virtual fitting rooms are professional products sold to corporate clients. I’m not aware of anyone making a hobbyist version of the software to place images on top of reflections. I believe the closest thing we have around here to a commercial devices is one guy made a photo booth and he did a lot of the coding himself.

Don’t get discouraged! It’s not an impossible dream. Just understand that there are challenges. Around here, we can definitely help you with construction tips, parts sourcing and test & tuning. And you might find a genius looking for a challenge.

Heh. Love the recent update, @michmich. Thanks for the entertainment.

@henrikra The mirror application itself doesn’t connect to the internet. It uses your existing network connections as configured in the Raspbian operating system. The Raspbian installation already contains auto-reconnect out of the box. (this arrangement means that you can use a wireless connection, an ethernet connection or a bluetooth connection and the mirror will grab whatever is at hand).

The failure to connect to GitHub is most likely the Update module checking to see if the Magic Mirror application has been updated. It’s what pops up the “An update to XXX is available!” notification.

I don’t know how flaky your internet connection is, but it definitely seems like something you will have to account for in your coding. The update module seems to gracefully handle it and try again when the connection has been restored. Perhaps you can look to it for ideas.

In the meantime, I would suggest an sudo apt-get update & sudo apt-get upgrade to make sure that you have any improvements to the networking of your Raspbian installation.

IIRC, @michmich looked into offering this as a commercial product and he ran into patent and licensing problems. The laws of your country may vary, but the short version is you can’t offer a magic mirror as a commercial product without involving lawyers and giving the patent holders some sort of payment.

You may be able to make one for your friends as a favor, with them picking up the expense of the materials. But you won’t be able to turn this into a business without careful and professional legal advice.

Error: listen EADDRINUSE 127.0.0.1:8080 usually means that something is already using port 8080 when the mm process attempts to start. The magic mirror process is trying to start a web server on port 8080, but something is already using that port.

Usually, this occurs when you try to start the magic mirror again when it is already running. Sometimes this is because you’ve put the command to start MM in the init.d file to start upon boot and used pm2 to run a mm.sh script. Both can’t run, so one of them fails.

The could not resolve host sounds like a problem either with your internet connection or with your DNS server settings. Quick troubleshooting:

• SSH into your Magic Mirror (Or get a terminal on the mirror itself. Whatever.)
• Try to ping the Google DNS servers: ping 8.8.8.8. If you do not get a response back immediately, troubleshoot your internet connection.
• Test your DNS settings by typing curl www.abc.com. You should get a small amount of HTML text. If you get “Could not resolve host: www.abc.com” then you should probably troubleshoot your DNS nameserver settings. Start by typing cat /etc/resolv.conf and posting the results here.

Good luck!

@schlachtkreuzer6 Technically, they’re not error messages. They’re warnings. If they become serious, then they will be promoted to errors.

@richland007 If you just want to have a module in the upper left and another module in the upper right, you should probably assign one to the top_left and the other to the top_right regions in the config.js file.

See the Magic Mirror readme file for more information.

@Kugelfang It’s probably just date & time math. Today is probably being evaluated against 1200 (noon). If the event is after 1200 hrs, then it’s resolving as a past event and being removed from the list.

@yours.mukul Heh. All right, short version:

Magic Mirror is a modularized application that is written using NodeJS, the Electron application framework and a mix of Javascript and Python programming languages. It does not use a database for state information. Instead, the Magic Mirror application uses a configuration file that determines how the application loads and run a series of modules.

The Electron application framework is responsible for coordinating between the back-end NodeJS processes and the front-end Javascript processes. The electron application is also responsible for rendering the interface onto the screen via a built-in web browser (Chromium).

When a module starts up (as directed by the main application), that module returns a chunk of HTML code that the application will then render and place upon the interface. If the module needs information from another source (RSS feed, weather information, sports scores, whatever), the application framework has hooks that allow a node process to retrieve/generate that information and then present it to front-end module code. Any state information is stored in memory and is regularly replaced by the back end process.

I hope that clarifies things.

@schlachtkreuzer6 I had the same error when I downgraded. However, it did install and I am able to run the Magic Mirror process. I am getting a temperature warning. I’ll experiment a bit to see if I can narrow that down.