Thanks for the persistent pages. I can try them today or tomorrow.

Regarding showing one module multiple times: I do not want to put e.g. “clock” multiple times into the config.js and show it in different places on the screen.

My idea was - and I hope that I got the concept right - that if the same module (which is implemented only once in the config.js and calls the API only once) could be shown multiple times on one page. Then I could set multiple name-tags for that module and address each representation of this module separately via the name-tag in the custom.css file and show/hide/scale different parts of the module at different locations on the screen. This could be of general use for other people as well.

My next step after this would be to learn how to inject css info dynamically - e.g. to keep infos about my upcoming trains/flights, the traffic-map to the station and weather info at my destination at the same visual size as I move throughout the room. This I would like to achieve with a distance measurement via PIR or doppler-microwave-sensor.

I hope this helps to explain the idea I had.

@Veldrovive If I got your new pages-implementation right, we define a name for a module which is later used to organize the page layout. Is that correct? Would it be possible to give multiple names to the same module (not have on module configured and shown multiple times via different names)?

It would be helpful for modules with rate-limited APIs, if different parts of one module should be shown at different locations on the same page. I would like to achieve this via a custom css which addresses your name-tag.

If this where possible, I would like to take this one step further in the future and implement a distance based layout which keeps the information most important to me readable throughout the room, when I prepare for my way to work. Changing the layout via css could be dynamic and would not involve a whole page refresh as it occurs when switching between pages.

@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.

@agp42 Thanks for the quick help!

@AgP42 Thank you for this version of iFrame. Works well for me :)
I do get a white line around the embedded iFrame. Could you please tell me, how to get rid of it?

@veldrovive That would be great - thanks a lot!!!
You could implement it as an option for the config part - maybe there are people out there that like to have a fallback to the standard page.

@Mykle1: Thank you for this nice module!

Dear @Veldrovive,

would it be possible to add an option to make the current page persistent until the next page change?

I have to use cases where this would help:

• if the Pi restarts, the Mirror always shows the standard page - no matter what page was active before the restart.
• if you open the Mirror on a browser (e.g. mobile phone), you always see the standard page until the next page change happens.

In both cases, if would be great to see the currently “active” page. Maybe there is a way to store and restore the current page?

Thanks a lot for your active development of the module!

@veldrovive Thank you very much for the quick fix! Now everything works like magic :man_mage:

I am putting a working example here for others, if they want to use MMM-Remote-Control with MMM-Page-Selector as well:

http://192.0.0.60:8080/remote?action=NOTIFICATION& notification=SELECT_PAGE&payload="test"

Dear @Veldrovive,

thank you very much for this fantastic module! I am trying to use MMM-Remote-Control to control the currently shown page through notifications which are sent via HTTP from my home automation (FHEM), depending on who is in the bathroom.

These two calls work fine with MMM-Page-Selector: (I had to insert a space into the URL when pasting it here as “&n” is replaced with a newline character by this website")

http://192.0.0.60:8080/remote?action=NOTIFICATION& notification=PAGE_UP

http://192.0.0.60:8080/remote?action=NOTIFICATION& notification=PAGE_DOWN

But i am struggling to use SELECT_PAGE to go directly to a desired page.

http://192.0.0.60:8080/remote?action=NOTIFICATION& notification=SELECT_PAGE&payload={"test"}

This call returns {"status":"success"}, but does not show the page “test”. Do you have an idea, what I am doing wrong?