@hayman - Nope. Three pi, one for each monitor. One of them is acting as a gateway onto our secured network. It brokers the VPN connection and then provides DHCP and internet access to the other two. This way, all three Pi are connected to the internet via some VM in… Sydney, I think. It depends on how they have it configured this week.

The network is the company product, so the mirror is a constant demonstration. (not that you can tell on the two monitors just playing video, but it’s the thought that counts).

@steed said in i need help getting the dailybibleverse module set up.:

i pasted the MMM-DailyBibleVerse folder here ‘/home/pi/MagicMirror/modules/default/MMM-DailyBibleVerse’

This path is incorrect. Modules go in the /home/pi/MagicMirror/modules folder. That path is assumed when you add the module name to the config.js entry. So when you type module: 'MMM-DailyBibleVerse', it’s going to look in that path for a folder with that name.

@zdenek Did you delete all the stuff not used for a mirror? From the complete setup tutorial: sudo apt-get remove --purge idle3 java-common libreoffice* minecraft-pi scratch nuscratch penguinspuzzle python-minecraftpi python3-minecraftpi smartsim sonic-pi wolfram-engine

Great video! And your mirror looks awesome. You did a fabulous job on both.

@cr4z33 - I’m glad you got it figured out. Don’t forget to mark the topic as solved!

@RE_Magic_Mirror The best way to keep your mirror running is to install a screensaver and then configure the screensaver to never run. Yeah, it’s a bit weird.

Install the screensaver program: sudo apt-get install xscreensaver

Once you do, start your Pi and get to the desktop. If you have already configured your Pi to start the Magic Mirror interface, click ctrl+q to exit. Open the menu by clicking on the Raspberry start button with your mouse, or clicking the special/window key on your keyboard. Go to Preferences and there should be a new entry called “Screen Saver”. Click/Press enter to activate the screen saver configuration.

On the configuration screen, there is a drop-down box with options as to which screen saver you wish to run. I believe the default is “random screensaver”. Navigate to this drop down box and select “disable screensaver”. Close the screen saver configurations window.

That’s it. That should keep your Pi from going black.

The monitor stand is definitely unique. Good looking build.

@dazza120 - Please use the Markdown features of the forum when posting code.

@RE_Magic_Mirror I don’t think there is a problem, no. I haven’t done any research on the topic, but I believe the lightdm.conf file was deprecated around the time the Wheezy version of the Raspian operating system was released. At least… changes to that file on Wheezy didn’t seem to have the desired effect. That continued on Jessie.

Greetings! My first mirror project is destined to be a wedding present for a friend of my wife. It’s been a steep learning curve, but I’m happy with the result. However, this situation presents a challenge for me, the Linux novice.

I would like to be able to get the mirror to update without VPN access to the mirror itself. I’m not sure of their wireless network, but I don’t think I can reliably find its IP address and it’s unknown whether or not their home network will allow VPN connections anyway. So my thought was I could create a Git repository that would represent the installation of the mirror on their RPI. As I push code to master, I would like the Pi to update itself and install new modules, upgrade code and so forth.

I think this will do the trick, but Git and I have a mutually hostile relationship. If I fork Mich’s code to my own account, I can update it without interfering with the rest of you guys. If I then fork every module that I wish to install and clone from these forks, I can update any module in my repository. I am just now investigating submodules in Git and this may be the way to go. But I’m not sure.

Keeping the modules updated would be a simple cron job that I would run at 2 AM every day. It would do a pull from my forks and update to new code whenever I pushed to my fork.

Am I missing anything? Is there an easier solution? Is this actually a solution? Can anyone explain submodules to me in a way that 1) I can understand, and 2) I can implement?

Thanks!