In the readme you should really give the thanks to @sdetweil

Ahh, him again? :-)

Done!

In the readme you should really give the thanks to sdetweil , he’s the one who basically gave me the answer.

And Sam, my thanks, again. :-)

Here is the fix:

I added your fix for Chromium to the readme. Many thanks, Mate. :thumbsup:

https://github.com/mykle1/MMM-EasyBack/blob/master/README.md

all in one(all in one application) , uses electron, npm start.
we’ve solved the pi 0 problem… my installer handles it

split mode (two applications)
start serverOnly
then view with some other browser (chrome, firefox, ie, …) either locally or from another machine/phone…

is was a pi0, and that you were running split mode…

what is split mode? If I am I didn’t mean to, I have it directly connected to a TV that I am using as a Bulletin board.

Here is the link:

http://emmanuelcontreras.com/how-to/how-to-create-a-magic-mirror-2-with-pi-zero-w/

Here is the fix:

I edited the file chromium_start.sh found here:

pi@raspberrypi:~ $ ls
chromium_start.sh  MagicMirror  mmstart.sh  node-v10.16.0-linux-armv6l  package-lock.json

and added

--autoplay-policy=no-user-gesture-required

Example:

  GNU nano 3.2                          chromium_start.sh                                                                         

#!/bin/sh
unclutter &
xset -dpms # disable DPMS (Energy Star) features.
xset s off # disable screen saver
xset s noblank # don’t blank the video device
matchbox-window-manager &
#midori -e Fullscreen -a http://localhost:8080
chromium-browser --autoplay-policy=no-user-gesture-required --incognito --kiosk http://localhost:8080/

the MagicMirror start script is ~/MagicMirror/installers/mm.sh

it does not run serveronly… it assumes you are running the mirror user experience ON the same machine.

i don’t know if EasyBack works on the remote client of serveronly… THAT browser would have to enable autoplay… our fix was for the electron browser running ON the same machine

edit:
ok, i see what you are doing… using chromium for the browser for some reason…

so u have to disable the autoplay blocker there , from
https://developers.google.com/web/updates/2017/09/autoplay-policy-changes

You can decide to disable entirely the autoplay policy by setting the 
Chrome flag "Autoplay Policy" to "No user gesture is required" at chrome://flags/#autoplay-policy. 
This allows you to test your website as if user were strongly engaged with your site and playback autoplay would be always allowed.

is this the start file you are talking about?

pi@raspberrypi:~ $ ls
chromium_start.sh  mmstart.sh                  package-lock.json
MagicMirror        node-v10.16.0-linux-armv6l
pi@raspberrypi:~ $ 

mmstart.sh?

pi@raspberrypi:~ $ sudo nano mmstart.sh

  GNU nano 3.2                       mmstart.sh                                 

#!/bin/bash
cd ~/MagicMirror
node serveronly &
sleep 30
xinit /home/pi/chromium_start.sh

npm start dev

Is that where it goes?

Man doing this project makes me feel so dumb I need to learn more, any suggestions?

I am trying a clean install now

I’m not sure what else I can do.

instead it’s ctrl shift i

My Keyboard is connected and working because I can quit magic mirror with the keyboard.

Humm… ctrl shift i doesn’t seem to work. may be it is just slow, I’m rebooting now and am going to try again. I’m using a raspberry pi zero.

and scroll up to see any info, or errors…
u can also filter for just messages from a single module by putting part of the module name in the filter entryfield

Sure, I can do that, but is there a way to do that through the console? To physically access the pi I have to climb a ladder. I’m going to do that now but it would be awesome if I don’t have to next time.