@cruunnerr said in I messed up: i think the process of pm2 is called MagicMirror Ahhh, thanks for putting me straight. I don’t do automatic installations anymore. I’ve only installed PM2 manually and use the commands that I stated. Good catch @cruunnerr! :-)

@nh_790 Wow!! Thank you very much for that two tricks! Working just perfectly. I think this monitor is now the perfect one for my mirror. Although this will take some time… :)

@Sean with Chromium I believe you can make to work all modules I did some modules to work with Chromium https://forum.magicmirror.builders/post/32731

@tbbear said in Additional Info for each module: So what do u all think about this idea??? I like this idea and I will comply with all future modules. :-) My recent Hello-Lucy enhancement for MMM-voice does make mention of the cpu it was developed on and the expected latency when using a non-integrated USB microphone. :-)

The lights WOULD create a glare…you’d have to test one to see how badly. But those vanities look dynamite…my daughter would love one!

A backup of a running system is a good idea. Keep in mind how often we have trouble with new Raspbian versions. It still seems to run best on Jessi, so at least keep an image of that Raspbian version at hand that works for you (but then again, why not a complete backup image?). My Mirror crashed with data loss and corrupted sd card and for weeks, evening after evening I couldn’t get WiFi to run on my RasPi with the new card and latest Raspbian. Finally found my old Jessi image and it worked immediately. If only I had made a backup, it would have been a 10 minute thing.

When you close the browser, MM is still running as a server/process in the background. If you stop and start it or directly restart it, there is no need to restart the Pi. What restarting the Pi does is just a very complicated way to stop the MM process. ;) Do you use PM2 to start MM on boot? Use pm2 restart mm See here: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror Or with npm, stop the package and start it again. Btw.: what text box? The console?

@navyvette87 In the body of your custom.css file: body { margin: 5px; height: calc(100% - 10px); width: calc(100% - 10px); } Adjust accordingly.

@cowboysdude Yes, a happy and healthy new year to all. Peace!

MERRY CHRISTMAS Peace to all

@carltonb said in 7" touchscreen as a Non-alarm clock?: At what point is the Ctrl+Shift= used. In the config.js file? No sir, not in the config. You simply press the corresponding key commands while the mirror is running, as stated in the link that I provided. Thank you so much. After reading the forum pretty well the link you sent was the first time I had ever seen these codes mentioned. You are welcome, mate. I took it upon myself to write that tutorial for key commands for that very reason.

@Mykle1 Who you kidding you’ll give it to me anyway LOL

OK i retried it with all the ’ replaced with ", still nothing. When i restart it after saving the config, it startes with a disk chk, then continues. When I replaced with the ", it restarts, but when I try to run node serveronly, it says syntax error.

@TGBB said in Info....?: I was asking if anyone has links to what they used etc. Not just giving me Amazon / Ebay etc link to home page and telling me to search on those for it. Don’t get your panties in a bunch, little sister. I gave you a link (to amazon) where I bought my acrylic, two way mirror. :-)

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.

@strawberry-3.141 said in 7" touchscreen as a alarm clock?: @wizz you could try body { transform: scale(0.5); } which should make everything half the original size Thank´s will try that and see how it looks.

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.

I know that it does not control the mirror. That’s why I said “evaluate and act” Use the IFTTT module, change it so it sends broadcast messages and make sure the modules of your interest react on these broadcast messages. The same with Alexa. You have to make sure Alexa has skills to interact with other modules on your magic mirror.

@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.