module: 'MMM-AlexaControl',
            position: 'middle_center',
            config: {
            image: false,
            pm2ProcessName: "mm",
            monitorToggle: true,
            vcgencmd: "vcgencmd",
            deviceName: "Spiegel",
	    pages: '2'
            }
        }, 
	{
        module: 'MMM-pages',
        config: {
                modules:
                    [[ "MMM-OpenmapWeather","weatherforecast","newsfeed","calendar", "compliments"],
                     [ "MMM-OpenmapWeather","calendar", "compliments" ]],
                fixed: ["clock", "currentweather", "MMM-AlexaControl", "MMM-page-indicator"],
                }
        },
        {
        module: 'MMM-page-indicator',
        position: 'bottom_bar',
        config: {
            pages: 2,
                }
        },

    {
      module: 'MMM-AlexaControl',
      position: 'middle_center',
      config:{
        image: false,
        pm2ProcessName: "MagicMirror",
        vcgencmd: "vcgencmd",
      }
    },

and my google home mini is unable to detect the magic mirror

if(action === 1){
            exec('/home/pi/monitor_on.sh');
            }if(action === 0){
            exec('/home/pi/monitor_off.sh');                         

forgot to put the path :confounded_face:

Thanks buds!

now, you CAN execute a script directly as long as it contains the processor name at the front
#!/bin/sh or #!/bin/bash

exec(“/home/pi/MagicMirror/modules/MMM-AlexaControl/scriptname”)

or the script has to be in the path environment varible.
(unlike windows, the ‘current directory’ is NOT included in the path (for security reasons))

if the script does NOT contain the processor path&name
then you have to launch the shell

exec(“/bin/bash -c "command string with pipe and logic chars"”)

 device.handler = function(action) {     
    if(action === 1){
        exec("vcgencmd display_power 1 && echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/bind", opts, (error, stdout, stderr) => {
            _this.checkForExecError(error, stdout, stderr); 
        });
    }if(action === 0){
        exec("vcgencmd display_power 0 && echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/unbind", opts, (error, stdout, stderr) => {
            _this.checkForExecError(error, stdout, stderr); 
        });
    }
}

where are the scripts? they MUST be on the path, or have the full path specified in the command too

Thanks!

I’ve seen on line 199 of node_helper.js the following:

 exec("vcgencmd display_power 0", opts, (error, stdout, stderr) =>

Tried to add the command: echo ‘1-1’ |sudo tee /sys/bus/usb/drivers/usb/unbind (cut power from usb ports)
like that:

 exec("vcgencmd display_power 0 && echo '1-1' |sudo tee /sys/bus/usb/drivers/usb/unbind", opts, (error, stdout, stderr) =>

Command does not work (I think theres a syntax error) monitor powers off but usb power still on.
Command works from commandline.
Also tried to put it on a separate exec function without succeed.

Can you give me a hand with this @JoChef2

Thanks!

Thanks so much, I’ve been in touch with MMM-Page developer but yours it has been the best indication indeed.
I’ve been playing with MMM-Notification-Trigger as I needed for interact with a groove sensor to fire QUERY_PAGE_NUMBER and got it working too. Very productive weekened indeed :face_savouring_delicious_food:

So now pages rotates by itself ; I can change them by AlexaControl and with a gesture too!!! Lovely
Thats what I wanted; reverting back calendar as private!!!

Thanks so much @JoChef2 I owe you a beer:clinking_beer_mugs:

So pretty good news if I make it to work.

Many thanks!!!

{
  module: 'MMM-CalendarExt2',
  position: "middle_center",
  config: {
    rotateInterval: 0,
    updateInterval: 1000 * 60 * 60,
    calendars : [
      {
        name: "Family",
        url: "mycalendar.ics",        //obviously my correct ics address here
      },
    ],
    views: [
      {
        name: "VIEW1",
        mode: "month",
		position: "middle_center",
		locale: "es_ES",
        slotCount: 1,
        calendars: ["Family"],
      },
    ],
    scenes: [
      {
        name: "PAGE1",
        views:["VIEW1"],
        className: "fakeScene"
      },
	  {
        name: "PAGE2",
        views:["VIEW1"],
      },
      {
        name: "PAGE3",
        views:["VIEW1"],
        className: "fakeScene"
      },
	  {
        name: "PAGE4",
        views:["VIEW1"],
        className: "fakeScene"
      },
	  {
        name: "PAGE5",
        views:["VIEW1"],
        className: "fakeScene"
      },
    ],
    notifications: {
      "PAGE_INCREMENT" : {
        exec: "sceneNext",
      },
      "PAGE_DECREMENT" : {
        exec: "scenePrevious",
      },
      "PAGE_CHANGED" : {
        exec: "changeSceneById",
        payload: (payload) => {return payload}
      } 
    },
  },
},

I just looked inside MMM-Pages(edward-shen/MMM-pages) shortly, It has no feature to emit notifications about current page sequence to other modules. It has PAGE_NUMBER_IS but it is only as the response of QUERY_PAGE_NUMBER. So there is no way to recognize which page at that moment. So CalendarExt2 cannot know what scene to show.

And this from MMM-pages doc:

This module sends one notification, MAX_PAGES_CHANGED to assist display modules with how many pages they should display. However, this module does not enforce what page other modules should indicate. This is intentional, because any other module that needs a page change notification should be receiving from the notification system.

Finally, if you want to know what page you're currently on, send a QUERY_PAGE_NUMBER notification. The module will respond with a PAGE_NUMBER_IS notification, with the payload of the current page number.

So will leave it for now unless @edward-shen can point me to the right direction here (or somebody else of course)

So thanks @JoChef2 nothing to do with AlexaControl.

il leave config and putting Calext2 in the first page in order to make that little trick I commented on earliers post…(refresh MM when changing page to Calendar’s one ) :face_with_cold_sweat:

If I put the Calendarext2 on page0 on MMM-Pages (with no notifications) I can call the calendar from Alexa by stating an Alexa Routine to actually refresh the mirror (as it restarts it shows the first page which is the calendar) --> Tried that already and it works but would love to make it working the way I want to. So many test (try-error) coming :fearful_face:

If anyone think of something I can try would be really appreciated :thumbs_up_light_skin_tone:

@Sean can you throw any word here? Thanks so much; I’m quite confused…

There’s obviously something wrong in my config and Im starting to suspect that its the interaction with AlexaControl module (I don’t know for sure yet). Anyway, If I leave the MMM-Pages rotate itself everythings works as expected; 60 second rotation and every single pages shows as it should as per my config (CalendarExt2 on page 2 too).
The only “problem” its when I change to the second page from Alexa (page that must be showing the calendarExt2 module view). It switches to page & shows the scene but it duplicates the calendar & then after that it shows the calendar overlapped on Pages below.
It does not happen with any other page; I can change to them with no problems at all and there’s no overlapping over any module after I call them with AlexaControl. It must be something easy but cannot find it at my own…

Help here will be much appreciated; any thoughts @Sean @JoChef2 ?

Config MMM-Pages:

	 {
            module: "MMM-pages",
            config: {
             modules:
                    [["clock", "currentweather", "calendar", "weatherforecast", "MMM-MoonPhase", "MMM-LocalTemperature", "MMM-AirQuality", "MMM-CoinMarketCap", "MMM-EARTH", "nagios", "newsfeed"],
                    [ "clock", "currentweather", "MMM-MoonPhase"],
                    [ "MMM-PlexSlideshow"],
                    [ "clock", "currentweather", "MMM-AirQuality", "MMM-TomTomTraffic"],
                    [ "clock", "currentweather", "MMM-MoonPhase", "MMM-GmailFeed", "MMM-Covid19"]
                    ],
                fixed: ["MMM-page-indicator", "MMM-CalendarExt2", "MMM-Remote-Control", "MMM-Admin-Interface", "MMM-Alexa-Control"],
                rotationTime: "60000",

            }
            },
{
            module: "MMM-AlexaControl",
            position: "top_center",
            config:{
            image: "true",
	    height: "35",
            width:   "35",
            pm2ProcessName: "mm",
            vcgencmd: true,
            pages:'5',
            }
            },

config MMM-CalendarExt2:

{
  module: 'MMM-CalendarExt2',
  position: "middle_center",
  config: {
    rotateInterval: 0,
    updateInterval: 1000 * 60 * 60,
    calendars : [
      {
        name: "Family",
        url: "mycalendar.ics",        //obviously my correct ics address here
      },
    ],
    views: [
      {
        name: "VIEW1",
        mode: "month",
		position: "middle_center",
		locale: "es_ES",
        slotCount: 1,
        calendars: ["Family"],
      },
    ],
    scenes: [
      {
        name: "PAGE1",
        views:["VIEW1"],
        className: "fakeScene"
      },
	  {
        name: "PAGE2",
        views:["VIEW1"],
      },
      {
        name: "PAGE3",
        views:["VIEW1"],
        className: "fakeScene"
      },
	  {
        name: "PAGE4",
        views:["VIEW1"],
        className: "fakeScene"
      },
	  {
        name: "PAGE5",
        views:["VIEW1"],
        className: "fakeScene"
      },
    ],
    notifications: {
      "PAGE_INCREMENT" : {
        exec: "sceneNext",
      },
      "PAGE_DECREMENT" : {
        exec: "scenePrevious",
      }
    },
  },
},

Added on my custom css as per @Sean indications:

.CX2.fakeScene {
  display:none;
}

It must be easy as I only want to show one calendar in one view (nothing complicated), isn’t it?
These are my three beauties for MM and would be nice to get them working together as per my needs:

MMM-Pages
MMM-CalendarExt2
MMM-AlexaControl
MMM-page-indicator

sorry 4 actually :smiling_face_with_open_mouth_cold_sweat: :smiling_face_with_open_mouth_cold_sweat:
Thanks in advance!