thanks @sdetweil , right you are - I was not running npm from within the MagicMirror directory.

When I update ‘Display’ to 1 I still get an error when trying to manually run NPM, however when ‘Display’ is set to 0 and then I run NPM there are no errors with it. The error is:

pi@MagicMirrors:~/MagicMirror $ npm start

> magicmirror@2.10.1 start /home/pi/MagicMirror
> ./run-start.sh

(electron:11918): Gtk-WARNING **: 22:18:00.088: cannot open display: :1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.10.1 start: `./run-start.sh`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the magicmirror@2.10.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-02-04T22_18_00_154Z-debug.log
pi@MagicMirrors:~/MagicMirror $ 

@bhepler thanks for the link, it is a bit beyond my understanding at the moment. I will have to read up on it a bit more. I tried to run xrandr to see what kind of status it gives on the monitors but it currently comes back with ‘Can’t open display’, I assume it is because another service/application is utilising them?

Anyway, thanks for your help.

@sdetweil na, no joy. I did try this yesterday also but was not sure I was looking in the right place. For the sake of it I tried using numbers 0 to 9, all with the same result. This for example:

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/pi/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-02-04T21_33_32_894Z-debug.log

However if I reboot the RPI with run-start having the different value it will still display the MM on the first screen, this made me think that this script was not being used at the startup as I would expect it to fail and not display the MM - perhaps I am wrong.

does this help

pi@MagicMirrors:~ $ tvservice --list
2 attached device(s), display ID’s are :
Display Number 2, type HDMI 0
Display Number 7, type HDMI 1
pi@MagicMirrors:~ $

Thanks @sdetweil and @bhepler , could you point me in the direction of how I would display a seperate instance of MM each monitor? I know this would mean I would need to update/maintain two different MM’s but maybe that is a better option if I want to add various modules?

@sdetweil , it is seen as two separate monitors. There is not a setting to scretch one screen to the other with the settings. The closest is ‘Strectch to cover screen’ but that does not seem to help.

Thanks @sdetweil , I have just played with those settings again. These seem to only effect the desktop and the desktop background and not the MM site. Always appears on the first screen.

Hey @sdetweil , I started with stopping MM (pm2 stop all). This then allowed me to use VNC to change the screen settings, as in just rotate the screen’s display.

The screens are showing as two seperate desktops and from VNC the mouse smoothly goes from one display to the other.

When MM is started this completly fills the first screen and a raspbian windows desktop is seen on the 2nd screen.

I wondered if I needed to update the ‘mm.sh’ file within the ‘installers’ folder, I tried changing this from ‘0’ to ‘1’ - reboot the RPI but on reboot MM does not get started on either monitor.

pi@MagicMirrors:~/MagicMirror/installers $ tvservice --list
2 attached device(s), display ID’s are :
Display Number 2, type HDMI 0
Display Number 7, type HDMI 1

Hey @sdetweil and @chassain-0 , so my kit for my v2 project has arrived. I have two 21.5 inch (same model) monitors connected up to an RPI4.

I have had a look around the forum but not been able to see what the best method is for this. When we start pm2 or when the RPI reboots it will boot up with the MM on the first screen and the normal desktop seen on the 2nd screen.

I think I would prefer to have two MM’s installed (one for each monitor), I assume this is ok todo or is the best approach to have the one MM on both screens?

Thanks

Nathan

Hey @sdetweil,

Forgot I did not get back to you. After much testing it was not feasible to use an rpi zero. Actually the ram/memory was ok, the main limitation was the cpu.

I was using htop to monitor this during boot and normal usage, is was constantly at 100%. This caused really slow boot time and could not load the modules fully even if left for several hours.

As soon as I went back to my rpi3 with the same modules it started very quick in comparison with no boot issues.