@wtidwell Nope, I don’t think so. I have not had any keyboard nor mouse connected since I installed it. :)

@wtidwell Nah, I’m running the “lite” version of Jessie… So it’s not that… I did not do a separate install of electron actually. I used the “install-script” from MM at the beginning… It’s goning to be interesting to see if you get any better results with another SD card…

@Mykle1 Thank you! :) You can actually get all three on the same “screen”. :) But what matters is that your CPU is hovering around 5% and mine (ours) are hovering around 20%x2… That is strange.

@wtidwell Are you rinnung a “lite” version or a full version of the OS?

@Mykle1 Can you do a screenshot from a terminal running nmon?
If you are ok with that… Here is how to do it.

1. Open a terminal (or log in via SSH).
2. Install nmon (sudo apt-get install nmon).
3. Open nmon by just typing “nmon”. :)
4. Press “t”, “l” and “m” to get “task list”, “longer term CPU averages” and “Memory & Swap stats”.
5. Press + to increase the update rate.
6. Let nmon fill the “CPU” meter and take a screenshot. :)
   Press “q” to quit nmon.
   Good thing about nmon is that you can use it from ssh (via putty). :)

Thank you!

Hmm… I always thought this was a normal behavior? Electron always runs pretty high on my RPI Mirror. This is my “task-list” using nmon on the RPi (via SSH) with basically nothing on the Mirror Screen but as you can see Electron is pretty active. :)

I do have quite a lot of active plugins of course…

Just to add some depth to this… If you really want to go “crazy” with animations, I’m recommending Bibliopixel and PixelWeb. Then you can “animate” lot’s and trigger them with a curl “command”. Plus you get a nice Web-interface to test the animations in. :)

@devtech8 Ok…
So, first I have a normal RPi with a Jessie Lite installation (just to keep everything to a minimal).
Then I followed this guide to get it running. When that guide is done. You have a fully working MM on the RPi (local installation). The config and all other information of my build you can find here.

Then after that I’m running a normal Ubuntu server 16.04 (in a container (a sort of VM)) with two instances of MM running om two different ports, I followed this guide (manual installation) and in server mode two times and just put them in different folders.
Here you can find my dev and server config. The server config is basically the same as my RPi config. I’m just using it for testing before adding stuff to the RPi.

To display a page in Electron that resides on another server (not the RPi) I’m not sure how to do. I have not done that. When I displayed my MM from the server on the RPi, I used Chromium in “Kiosk-mode” (as mentioned before).

This forum is full of GREAT people you can ask anything! I scavenged the forum (and tested stuff on a dev mirror) for moths before I actually built my mirror. :)

pm2 is used in this case to start and stop and troubleshoot the mirror. Otherwise it’s an extremely powerful tool in a “node” environment. I will go so far as to say that it is almost mandatory to use if you want to have control of you node apps. :)

@devtech8 Hmm… It’s two different things. Either you run the mirror as a “local” mirror = The picture come out via the HDMI port on the RPi using Electron. Or you can run the mirror on “any” server (computer in your network) then start is as a “server” = The you can open the mirror on any machine on your network. Even if you run the fist way, you can also open the mirror on any other machine in you network (depending on the access rules in your config of course). However, a RPi is not a powerful machine, so it will be fairly slow if you want it both on your “local” screen and on a networked machine at the same time.
To start as a “server” you run node serveronly instead of npm start.
Then I recommend you to use pm2 as the “manager” for your mirror. It’s easier to troubleshoot then. :)

Not sure if I answered your question. :)

I myself is running 3 different mirrors. One on a RPi (local display), one on a server with the same config as the RPi and one more on the same server on another port for development. :)

Hi @devtech8 Yes, its definitely possible. I had mine running like that for a while.
Take a look at this thread: https://raspberrypi.stackexchange.com/questions/38515/auto-start-chromium-on-raspbian-jessie-11-2015
I don’t remember what script I used in the end. But that’s the way to do it. :)
You will have to “kill” chromium from time to time. It tends to “hang”. Don’t know why…

Nice build!