@Darkmx-6 i don’t know where mmstart.sh came from… it is not part of the base MagicMirror solution.

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.

@art212 see the two links in my signature

@joshwilsonvu

Maybe it could live on another branch so users could type git checkout experimental to opt into the new features.

certainly this would be a good approach

@chassain-0 did u get the updated googlemapstraffic from my GitHub repo?

@feleb i have a covid charting module

https://github.com/sdetweil/MyCovid19

I have reported this, hopefully someone from the website team will look into this

@BD0G said in Anyone want to try updated installer...:

XXABI_1.3.9’ not found (required by node) node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: versionGLIBCXX_3.4.21’

I have found a fix, allowing jessie to continue to work… added fix to latest installer…
thanks for your help

i run MM on an ODroid Xu4… I think C2 would be ok.
le Potato has an ubuntu image 18.04 at least…

so its seems reasonable… some supporting modules (speech reco mostly) might be lagging

@peterbarlow2000 the node_helper file gets executed on the server, (one instance for all clients)
and the file in the module folder that matches the module name (modulename.js we call it)
runs on the client (one instance for each client)

I would change this

code needs to be executed on the client (by electron?).

to

code needs to be executed on the client (in the browser?).

@RIKKO14 the update notification module does a git status for each module. if the module is linked to an upstream GitHub repo, git status will tell you if you are behind on changes.

so, if the messages aren’t being helpful, go to each non-default folder in ~/MagicMirror/modules
and do
git status

if I reports behind, then do
git pull
if the module has a package.json file, then also do
npm install