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.

@sdetweil thanks.

I found it had to get cheaper monitors that are both slim and gave small bezel. Not sure how will look with about 3-4cm of bezel in the middle.

Has anyone tried building a MM with an rpi4 and attaching two monitors?

I wanted two hook up to 21.5 inch monitors as it would be cheaper than getting a slim 30+ inch monitor.

Thanks @sdetweil , after a couple of reboots this is now working as expected. Not sure what the issue was, I will have to keep an eye on it. Thanks for the link on swap space, I will also look in that direction if I have any more of the same issues.

Hey sam (@sdetweil ),

Thanks for this, made my life a lot easier.

So, I just did a new build with Buster on a RPI Zero W. All looked good and I have configured mm2 to start on reboot of the Pi. I am start/stop/restart and check the status of mm2 and is looks to be working, the mm2 logs are also good with no error logs.

The problem I am facing is that the magicMirror page via chromium seems to try and load (white screen which changes to a pure black screen) however seems to fail/crash and go back to the Raspbian desktop.

This happens when I reboot the pi and also when I manually try to start/restart the mm2 service.

Anything you think I am missing?

Thanks

Hey @Sean ,

Thank you for your quite reply, you are correct the token.josn file was missing. Looks like I needed to run ‘node auth_and_test’ as sudo for this file to be created. Once I did this the photos started to appear :) just need to configure the size and position now.

Thank you again.

Regards

Nathan

Hi Sean,

Firstly thank you for this, it has great potential and is something that has been missing for such a long time compared to the alternative dakboard that I was forced to use to get photos displayed.

I have an issue though, I believe I have been through the steps correctly but can not get it to work. When I reboot my RPI2 it looks like the ‘auth_and_test.js’ is ran and this brings up the browser with googlin login and if I follow this through it gives me the code which is the same experience I have when running ‘auth_and_test.js’ in order to get the album id.

This then repeats itself every 5mins or so…

I have added the album id in the config.js but it does not seem to matter if I put a correct or incorrect one in here the same happens. It does not look like it trys to put images on the desktop so I don’t think the module is getting that far.

Any idea what I have done wrong?

Thanks

Nathan

@Kimzer Thanks for your quick replies. I deleted the Wunderlist and the enhanced Wunderlist folders/modules. Then created the Wunderlist folder again, then did npm install and this seems to have resolved the issue, must of been a problem with the Module.

@Kimzer Hmmmm, maybe. From the times I have missed/messed up config if normally comes up with something like …missing config.js

Hey,

I am having issues with the ‘MMM-Wunderlist’ and the enhanced version, when I add this in as a modules, then reboot the rpi. All I get is a blank screen? When I ssh in and then remove the module from the config.js, reboot then everything is back again. It does not seem to matter what I add the module config I get the same results.

Thanks

Nathan

Thanks @cowboysdude and @strawberry-3-141, will start looking at those.