Defaults to no-user-gesture-required.

it would be interesting if you used chromium instead , if your config says

address:"0.0.0.0",

then try from any other system

http://pi_address:MM_port

try this one thing, (I don’t think it will help but)
clear the Electron config folder, will be recreated on next electron startup
(zoom setting is saved here somewhere)

stop MagicMirror
rm .rf ~/.config/Electron
start MagicMirror

in JavaScript

the thing to the left of : does not need quotes
if the thing to the right is a number or true/false
no quotes
if the thing to the right is a symbol { or [ no quotes
otherwise
if it contains letters, it needs quotes.

single or double does matter as long as they are the same on both ends

C&P to eliminate typos!

So now the whole webpreferences entry reads: -

            webPreferences: {
                    autoplayPolicy: no-user-gesture-required,
                    contextIsolation: true,
                    nodeIntegration: false,
                    zoomFactor: config.zoom
            },

But MM doesn’t start!

look at the doc link for autoplay, to get the right syntax/spelling

and add the key and value to the WebPreferences object

in general they are stopping autoplay because customers are screaming at them (I hate it too in general purpose use)…

https://www.electronjs.org/docs/latest/api/browser-window

but, I have heard others say this setting also doesn’t work

(I did the change request to set it as it is now)

also, your electron should be 13.5.1 (on MM version 2.17.1)

function createWindow() {
app.commandLine.appendSwitch(‘autoplay-policy’, ‘no-user-gesture-required’);
let electronSwitchesDefaults = [“autoplay-policy”, “no-user-gesture-required”];
app.commandLine.appendSwitch(…new Set(electronSwitchesDefaults, config.electronSwitches));
let electronOptionsDefaults = {

I also had some issues with the autostart but upgrading my electron seems to have fixed the issue with both modules. As long and you followed the “workaround” directions in the readme. it should work.

Please try letting the modules run and see if they eventually start. I have seen this behavior. It may have to do with the feed being blacked out for periods of time at the source.

So, please verify the workaround was done and that you are running the newest electron. My electron is at 11.3.

Peace!

I have already tried adding :
app.commandLine.appendSwitch(‘autoplay-policy’, ‘no-user-gesture-required’); //< -------- added

to the recommended place in MagicMirror/js/electron.js but without any results. Further I have tried to update to the latest version of the electron browser with “npm install electron@latest” but that has also not helped me with the autoplay problem.

Is there further thins that I can try or any possibility that I did something wrong above?

Thanks for any help!

The module is showing red or the entire MM?

In the meantime, if you have the ability to click the close box that is also present, you can close the message and the module will work as expected until you restart MM again. That message does not always reappear after restart but it can.

on one system here *pi 0" I got ‘could not update chrome’ but there was a button

normally one would apply updates

open a terminal or ssh window , do

sudo apt-get update
sudo apt-get upgrade

Cheers

Pete.