Read the statement by Michael Teeuw here.
MMM-EARTH-Live & MMM-ISS-Live
-
@Egnos said in MMM-EARTH-Live & MMM-ISS-Live:
Do I have to enable the mouse pointer or do I have to be on t the module?
I used the mouse to click the close box on the message windows
-
@Mykle1
The problem is in the location of the form.
If the module is positioned in the “upper_third” region it is not possible to interact with the mouse.
To close the message I had to:-
temporarily change the position to the MM-Earth Live module,
-
close the message,
-
and finally reposition it in its original position.
Now it’s okay.
Could you also check if it is not possible to interact with the module in the “upper_third” region?
Thanks.
-
-
@Egnos said in MMM-EARTH-Live & MMM-ISS-Live:
Could you also check if it is not possible to interact with the module in the “upper_third” region?
I moved mine to the upper third position (both modules) and they both respond to mouse clicks
-
Hi all I have just installed this module on my MM and when I run it I have the following message on the screen “Your browser is out of date” how do i update this?
Cheers
Pete.
-
@Peter-Leemon what type hardware are u running on? pi 0?
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 -
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.
-
Thank you all yes I did that got it working now its showing a red screen?
-
The module is showing red or the entire MM?
-
was weird just he Module then after about 6 hours and a few reboots came good however the live feed on my mac was perfect atm its working fine, must have been a gremlin lol
-
Hello,
Currently I struggle with a problem that already seems to be know but I somehow can not fix it. MMM-EARTH-LIVE is not autoplaying for me.I have already tried adding :
app.commandLine.appendSwitch(‘autoplay-policy’, ‘no-user-gesture-required’); //< -------- addedto 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!
-
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!

-
Can anyone help please, I can’t get the feed to autoplay with Electron 15.3.0 even after adding the following
app.commandLine.appendSwitch(‘autoplay-policy’, ‘no-user-gesture-required’);
This is how the line looks in electron.jsfunction 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 = { -
@ruskythegreat autoplay is now part of the webPreferences config
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)
-
@sdetweil I did run npm install electron@latest but yes, I am running MM 2.17.1
-
@ruskythegreat we haven’t tested above 13.5.1
-
@sdetweil I just downgraded to 13.5.1 but still no auto play.
-
@ruskythegreat i understand… did u try to change the code to the new webPreferences object parm?
in general they are stopping autoplay because customers are screaming at them (I hate it too in general purpose use)…
-
@sdetweil No, Sorry, I’m not familiar with the webPreferences object param Can I trouble you to ELI5 :)
-
@ruskythegreat there is already a WebPreferences object in the electron.js file, just down a few lines from your change.
line 30look at the doc link for autoplay, to get the right syntax/spelling
and add the key and value to the WebPreferences object
-
@sdetweil Thanks for all your help with this.
It’s still not autoplaying :(
I tried with the autoplayPolicy with the no-user-gesture-required so: -
autoplayPolicy: no-user-gesture-required,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!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
