@cyberphox After downloading the registry “bastilimbach/docker-magicmirror:latest”

• Name the container “MagicMirror”
• I prefer setting a cpu limit to have a safeguard against rouge processes
• Limiting it to max 4 GB of RAM works fine for me
• Activate automatic restart
• If you like, add a link to the MagicMirror on your Synology Desktop by adding “:8080” the url provided
• Port: Make sure, 8080 is written on both sides of the table. If port 8080 is already in use, you can use another port on the left side.
• Volume: I have added a screenshot for the folders I am linking in from my Synology. Make sure, you finish the setup before starting MagicMirror for the first time.
  
• If you use the firewall (you should!), make sure, the rule “Docker MagicMirror” is active. It should have been generated from Docker automatically.

When everything is ready, fire up the MagicMirror Docker image and follow the instructions for a regular setup.

@Mykle1: Thank you for this nice module!

@veldrovive PS: I tried following your workaround and just wanted to let you know that it works Now I am able to use your new config option for pages which makes it so much easier to set them up! Great idea to implement it!

Maybe you could tweak mmm-suncalc to send notifications at these events. That should be easy and useful for many others as well

@olexs
The delay calculation and sorting issue seems to be even stranger. Now I have three upcoming ICE connections to Berlin. This is how they are shown:

• 22:01 +20 //actual: 21:59 + 2 min
• 23:01 +20 //actual: 22:59 + 2 min
• 20:15 +40 //actual: 19:59 + 15 min

The hafas output is:

Parsing: ICE 276 nach Berlin Hbf (tief) um Mon Jun 26 2017 20:14:00 GMT+0200 (CEST)
{"name":"ICE 276","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T18:14:00.000Z,
  delay: 900000,
  line: 'ICE 276',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 274 nach Berlin Hbf (tief) um Mon Jun 26 2017 22:01:00 GMT+0200 (CEST)
{"name":"ICE 274","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T20:01:00.000Z,
  delay: 120000,
  line: 'ICE 274',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }
Parsing: ICE 592 nach Berlin Hbf (tief) um Mon Jun 26 2017 23:01:00 GMT+0200 (CEST)
{"name":"ICE 592","class":1,"productCode":0,"productName":"ICE"}
{ when: 2017-06-26T21:01:00.000Z,
  delay: 120000,
  line: 'ICE 592',
  nr: undefined,
  type: 'ICE',
  color: '#006F35',
  direction: 'Berlin Hbf (tief)' }

Any idea how to fix this?

Dear @delightedcrow,

thank you very much for this beautiful theme. I really like using WallberryTheme to beautify the background of my screen.
What strikes me is that the images do not seem to be truly random. I have linked it up to a bigger collection and keep seeing the same images over and over although statistically, this should not be the case. Did you experienced this as well?

Thanks!

I would suggest to force a captacha for the first XX number of posts of a user. Once the user seems credible, you can most certainly leave it out for this person.

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 )

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

Best,
Phillip

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

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"]}