@mmmmh OK, Here’s what I did: I can control everything else with Scenes2 and for CalendarExt I use Remote-Control’s REST API.

@MMRIZE said in MMM-Touch or similar without visible module: @mmmmh useDisplay: false, Yes. I think this does it. In the beginning I thought it just disabled visual feedback but it seems it actually hides the module. I’ll test it some more and will come back.

Thanks for the quick reply. I looked at the file details and the creation date. It’s from a while back and knowing now that its a core dump I’ll delete it.

The official Raspberry Pi touchscreen activates a screensaver without documented settings. The screen wakes up when touched. Generally, I would like to keep it that way but I also want to be able to wake up the screen programmatically. If possible, I would also like to tweak the activation time. I know how to turn the backlight on and off and how to dim the screen but does anyone know how to manage this screensaver?

OK, for posterity, here’s what I did. I used MMM-Remote-Control and created a button element that calls a function that issues a get request. Interestingly, when I put the URL in the button code the request was rejected (no cross-origin request allowed) but when after I put the URL in the function it worked. function toggleCal() { var myUrl = "http://mypi.local:8080/remote?action=TOGGLE&module=MMM-CalendarExt"; console.log("getting " + myUrl) var xmlHttp = new XMLHttpRequest(); xmlHttp.open("GET", myUrl, false); // false for synchronous request xmlHttp.send(null); return xmlHttp.responseText; }; The button code gets mangled here. I had to add spaces < button onclick="toggleCal()">Calender on/off< /button>

@Sean I checked again, you are right, polling is the only option. Thanks for your cool module!

My mirror fetches minimal web pages with images that change in content but keep the same file name. The URLs include basics authentication credentials (I don’t know if that matters). Both, MMM-iFrame and MMM-iFrameReload show missing image icons unless I delete Electron’s cache. How can I fix this?

Maybe it is too obvious and I cannot see the wood for the trees, but I don’t know how to serve different layouts/content to two different clients. I understand that assigning classes to individual modules in the settings is one way to differentiate what gets displayed, but how is the class determined on the client-side? I run MMM as server-only and plan to use two different Raspberry Pis to display its specific layout. Can I pass an identifying string with the URL? Or is running two separate instances from different directories the better way?

@Sean Awsome. This looks very promising, thank you. There’s so much to configure, it’ll keep me busy for the next days.