@sdetweil No - I need to click on the “play” button on the stream.

@sdetweil Thanks for the idea. This does not seem to cause the problem. Autoplay still refuses to cooperate…

@sdetweil said in No autoplay for videos in v2.14 & v2.15:

@rudibarani well, we moved from electron 8 to 11

I do to keep up with the latest version of electron via

npm install electron@latest

as I otherwise get a message saying something like “your browser is outdated” hovering above the ISS stream. The current electron version does autoplay with MagicMirror v2.13 - but not with a newer version of MagicMirror.

@sdetweil said in No autoplay for videos in v2.14 & v2.15:

so change electron.js like this
function createWindow() {
let electronOptionsDefaults = {
width: 800,
height: 600,
x: 0,
y: 0,
darkTheme: true,
webPreferences: {
contextIsolation: true,
nodeIntegration: false,
zoomFactor: config.zoom,
autoplayPolicy: “no-user-gesture-required” // < — moved to here
},
backgroundColor: “#000000”
}

Thank your for the suggestion, Sam. I tried it - but unfortunately without success. Autoplay of the ISS Livestream not starting with any of the modules. It works fine, when I go back to v2.13, though.

http://www.ustream.tv/embed/17074538?html5ui&initial-quality=high&volume=0&autoplay=1

Any additional thoughts would be much appreciated!

Dear all,

my MagicMirror ist running on a Mac Mini and I don’t have any problems when running on v2.13. If I upgrade to v2.14 or v2.15, autoplay of embedded videos is not working anymore. For the curious among you: I like playing a livestream of the ISS on my nighttime-mirror.

The problem occurs with the electron versions that install with each release and are not resolved, if I upgrade electron to its latest version. Adding this line to electron.js did not have a positive effect as well:

app.commandLine.appendSwitch(‘autoplay-policy’, ‘no-user-gesture-required’);

Every module I have tried is affected, e.g. MMM-SmartWebDisplay, MMM-EARTH-Live, yframe, iFrame-Ping…

Did someone else have this problem or does somebody have an idea what I could try do except staying on v2.13?

Thanks!
Phillip

@scottcl88 Cool 🤓 Thanks for sharing your work! 👍

@grena
Thanks for your quick help. The new update solved the issue with the position of the description. The size topic was an error of my side. Had a duplicate entry for the maximum width cancelling our the “0”.
Have a nice weekend!

@grena Thanks for this nice module!
I just wanted to include the APOD description and it seems that the total module size is defined by the image and the image is scaled down, when I add the description. In addition, the description is shown on the left whereas the image was set to middle_center.

Would it be possible

• that the image maintains its defined size when the description is displayed and
• that the position and width of the description could be defined (e.g. centered below the image and with the same width as the image)?

Thank you very much for considering this.
Best,
Phillip

This looks very interesting! Thanks a lot for the effort to create this module. I look forward to trying it :)

Hi Nox,
did you find a solution for this?
Best,
Phillip

Hi @Vauxdvihl,
I had the same problem with another module. You can find what worked for me here: https://forum.magicmirror.builders/topic/11185/electron-browser-outdated
Good luck!

@sdetweil: I only updated electron without changing npm and node - so I am still using Node v11.6.0 and npm 6.9.0 on my Mac Mini (24/7 since 2009 :slightly_smiling_face:)

Thanks @sdetweil - changing the electron to latest works fine for me on a Mac Mini. I tested all my modules and did not find glitch so far.
@MichMich: Is there a special reading why you stick to version 3.0.13?

Dear all,
I am using this page at night including a module (MMM-SmartWebDisplay from @AgP42) which used to show a livestream from the ISS until the ISS camera payload unfortunately reached its end of live a few weeks ago:

Now I noticed a message in the bottom corner of the livestream, claiming that the browser is outdated.

The link redirects to this website: https://support.video.ibm.com/hc/en-us/articles/360000403129-Supported-Browsers-for-IBM-Watson-Media

I am using MagicMirror² v2.8.0, Node v11.6.0 and npm 6.9.0.
How do I update the electron browser accordingly?

Thanks for your support!

Dear @j-e-f-f,

thanks for your feedback. I don’t have much coding skills (yet) - but I will try :slightly_smiling_face:

Best,
Phillip

Dear @j-e-f-f ,
thank you for this great module. I enjoy looking at it every morning :grinning_face:

I would like to use real world data from a temperature sensor at our house instead of the “current temperature” data from the weather service.

Would it be possible to optionally add an URL to the config that returns the temperature as plain value (e.g. 15.76) and replace the corresponding value from the weather service?

Thanks for considering this,
Phillip

@veldrovive
OK - thanks for the reply anyway!

@veldrovive
Thanks again for implementing the current page as “dynamic” class. If I get it right, you had to code procedures to add and remove the page class when switching pages.

Ok, the development branch now has support for the new class name changes. When a module is shown on a page, it will be given the class page_{Current Page} and then the class will be removed when the module is hidden.

Would it be possible to make these procedures accessible via notifications? I am still looking for a way to add and remove classes based on external triggers. A scheme could be like this:

Notification: "MMM_Page-Selector_Update_Class"
Payload: {"add":["Module_1_Name:ClassA_to_add", "Module_2_Name:ClassB_to_add"], "remove":["Module_3_Name:ClassC_to_remove", "Module_4_Name:ClassD_to_remove"]}

Dear @agp42,
I am finally getting back at my mirror and get some time to incorporate your updated module. Thanks again for making dynamic URLs possible!

Would you mind changing this.urlToDisplay = payload.url; to this.urlToDisplay = payload; in your code? Thus, one could send a plain url as payload without the need to process it to be in the format{"url":"http://..."}.
This would make things easier and as the payload will only contain a URL if the notification is iFrame_Ping_URL, this should not cause any problems with other possible content.

Fantastic news!! Thanks a lot!
Will you be keeping the “temporary fix” as additional option to visualize the moon? It worked well and has a quality of its own. Maybe it would be possible to rotate it according to the users location and time.