MMM-TouchNavigation

well, I gave it a try and the opacity approach works

rename your MMM-TouchNavigation folder and get mine
https://github.com/sdetweil/MMM-TouchNavigation

two new config parms

fadeButtons: true (default is false, buttons on screen all the time)
fadeDelay: milliseconds , default 15000… how long til u want them to fade out
if u touch a button the timer is restarted
once faded (to 20%, just barely visible, so u know where to touch), then they are surfaced, but the specific button notification was not sent… have to push button when not faded to send profile switch

and some styles for the fade out/in transition, and the timing logic for fade out (after 5 minutes, or 1 or…)
and config for this support hideAfter: true/false (default false) might be able to do it with a number (the delay time, default 0)

I don’t know which approach works… (or works better) create another div and toggle active
or opacity only

so the trick will be to hide the existing buttons and replace with a transparent button, which clicked reverses the process.

if u hide a module or an html element (style display: none), then it is not active anymore, and can’t be clicked

one might be able to change the opaqueness to 0 and have the buttons active but invisible.
then each button click handler will need to check if it’s invisible and change that vs doing it’s normal assignment.

Hello, yes I can of course create a new profile and change the time. I would like the buttons to hide and be there again when they are touched. So I could create a clean design.

PS: I hope google translated it well.

so this module doesn’t do much… but its SO close…

MM can only show or hide modules. when u switch profiles and a module disappears, its because it is hidden, (but still running)

SO, you could make another profile with whatever module you want to hide from THIS profile
and cause a switch to that profile

are these hardware buttons or on screen?