MMM-AlexaControl or MMM-AlexaOn/Off setup

[sdetweil]

i redid my discovery and notice this

[2020-08-10 10:25:05.522] [LOG]    << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 15
ST: urn:Belkin:device:**

 from 192.168.2.244:50000 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:93 Socket.<anonymous>)
[2020-08-10 10:25:05.523] [LOG]    Search request from { address: '192.168.2.244', family: 'IPv4', port: 50000, size: 107 } (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:94 Socket.<anonymous>)
[2020-08-10 10:25:05.524] [LOG]    192.168.2.0 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:95 Socket.<anonymous>)
[2020-08-10 10:25:05.525] [LOG]    responding for port=16000 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:18 response)
[2020-08-10 10:25:05.526] [LOG]    responding for port=16001 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:18 response)
[2020-08-10 10:25:05.527] [LOG]    responding for port=16002 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:18 response)
[2020-08-10 10:25:05.528] [LOG]    responding for port=16003 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:18 response)
[2020-08-10 10:25:05.528] [LOG]    responding for port=16004 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:18 response)
[2020-08-10 10:25:05.529] [LOG]    responding for port=16005 (/home/sam/MagicMirror.2.11/modules/MMM-AlexaControl/node_modules/node-fauxmo/src/SSDPService.js:18 response)

[Michael Schw.]

@sdetweil i did try to find it on my phone…and it worked but it cant do a thing.
i found : restart Spiegel pm2
spiegel refresh
Spiegel Monitor
stop Spiegel pm2

which one does what?
and can i speak german to alexa and can rename these names?
everytime i tried Spiegel Monitor, what i believe is the toggle function it says:please configure the option vcgencmd.
so do i have to put in this option vcgencmd instead of true?
this is all i got:

magicmirror@2.12.0 start /home/pi/MagicMirror

DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[2020-08-10 17:26:01.656] [LOG] Starting MagicMirror: v2.12.0
[2020-08-10 17:26:01.702] [LOG] Loading config …
[2020-08-10 17:26:01.725] [LOG] Loading module helpers …
[2020-08-10 17:26:01.729] [LOG] No helper found for module: clock.
[2020-08-10 17:26:01.859] [LOG] Initializing new module helper …
[2020-08-10 17:26:01.861] [LOG] Module helper loaded: updatenotification
[2020-08-10 17:26:01.863] [LOG] No helper found for module: currentweather.
[2020-08-10 17:26:01.865] [LOG] No helper found for module: weatherforecast.
[2020-08-10 17:26:02.802] [LOG] Initializing new module helper …
[2020-08-10 17:26:02.803] [LOG] Module helper loaded: MMM-AlexaControl
[2020-08-10 17:26:02.810] [LOG] Initializing new module helper …
[2020-08-10 17:26:02.811] [LOG] Module helper loaded: MMM-OnScreenMenu
[2020-08-10 17:26:02.812] [LOG] All module helpers loaded.
[2020-08-10 17:26:03.178] [LOG] Starting server on port 8080 …
[2020-08-10 17:26:03.207] [INFO] You’re using a full whitelist configuration to allow for all IPs
[2020-08-10 17:26:03.222] [LOG] Server started …
[2020-08-10 17:26:03.224] [LOG] Connecting socket for: updatenotification
[2020-08-10 17:26:03.226] [LOG] Connecting socket for: MMM-AlexaControl
[2020-08-10 17:26:03.227] [LOG] MMM-AlexaControl helper, started…
[2020-08-10 17:26:03.229] [LOG] Connecting socket for: MMM-OnScreenMenu
[2020-08-10 17:26:03.230] [LOG] Sockets connected & modules started …
[2020-08-10 17:26:03.806] [LOG] Launching application.
[2020-08-10 17:26:07.569] [LOG] monitorToggle requested
[2020-08-10 17:26:07.593] [LOG] Adding multicast membership for 127.0.0.1
[2020-08-10 17:26:07.595] [LOG] Adding multicast membership for 10.0.0.2
[2020-08-10 17:26:07.598] [LOG] server is listening on 11000
[2020-08-10 17:26:07.600] [LOG] server is listening on 11001
[2020-08-10 17:26:07.602] [LOG] server is listening on 11002
[2020-08-10 17:26:07.603] [LOG] server is listening on 11005
[2020-08-10 17:26:07.738] [INFO] Checking git for module: MMM-AlexaControl
[2020-08-10 17:26:07.787] [INFO] Checking git for module: MMM-OnScreenMenu
[2020-08-10 17:26:50.497] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: “ssdp:discover”
MX: 3

from 10.0.0.7:50000
[2020-08-10 17:26:50.513] [LOG] Search request from { address: ‘10.0.0.7’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.563] [LOG] 10.0.0.0
[2020-08-10 17:26:50.572] [LOG] responding for port=11000
[2020-08-10 17:26:50.586] [LOG] responding for port=11001
[2020-08-10 17:26:50.589] [LOG] responding for port=11002
[2020-08-10 17:26:50.591] [LOG] responding for port=11005
[2020-08-10 17:26:50.597] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: “ssdp:discover”
MX: 3

from 10.0.0.7:50000
[2020-08-10 17:26:50.599] [LOG] Search request from { address: ‘10.0.0.7’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.600] [LOG] 10.0.0.0
[2020-08-10 17:26:50.605] [LOG] responding for port=11000
[2020-08-10 17:26:50.607] [LOG] responding for port=11001
[2020-08-10 17:26:50.608] [LOG] responding for port=11002
[2020-08-10 17:26:50.610] [LOG] responding for port=11005
[2020-08-10 17:26:50.614] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: “ssdp:discover”
MX: 3

from 10.0.0.7:50000
[2020-08-10 17:26:50.615] [LOG] Search request from { address: ‘10.0.0.7’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.618] [LOG] 10.0.0.0
[2020-08-10 17:26:50.624] [LOG] responding for port=11000
[2020-08-10 17:26:50.627] [LOG] responding for port=11001
[2020-08-10 17:26:50.628] [LOG] responding for port=11002
[2020-08-10 17:26:50.631] [LOG] responding for port=11005
[2020-08-10 17:26:50.634] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: “ssdp:discover”
MX: 3

from 10.0.0.7:50000
[2020-08-10 17:26:50.636] [LOG] Search request from { address: ‘10.0.0.7’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.638] [LOG] 10.0.0.0
[2020-08-10 17:26:50.644] [LOG] responding for port=11000
[2020-08-10 17:26:50.646] [LOG] responding for port=11001
[2020-08-10 17:26:50.647] [LOG] responding for port=11002
[2020-08-10 17:26:50.649] [LOG] responding for port=11005
[2020-08-10 17:26:50.652] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: “ssdp:discover”
MX: 3

from 10.0.0.7:50000
[2020-08-10 17:26:50.653] [LOG] Search request from { address: ‘10.0.0.7’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.654] [LOG] 10.0.0.0
[2020-08-10 17:26:50.657] [LOG] responding for port=11000
[2020-08-10 17:26:50.659] [LOG] responding for port=11001
[2020-08-10 17:26:50.660] [LOG] responding for port=11002
[2020-08-10 17:26:50.661] [LOG] responding for port=11005
[2020-08-10 17:26:50.663] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: “ssdp:discover”
MX: 3

from 10.0.0.7:50000
[2020-08-10 17:26:50.664] [LOG] Search request from { address: ‘10.0.0.7’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.665] [LOG] 10.0.0.0
[2020-08-10 17:26:50.668] [LOG] responding for port=11000
[2020-08-10 17:26:50.670] [LOG] responding for port=11001
[2020-08-10 17:26:50.672] [LOG] responding for port=11002
[2020-08-10 17:26:50.674] [LOG] responding for port=11005
[2020-08-10 17:26:50.680] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: “ssdp:discover”
MX: 3

from 10.0.0.5:50000
[2020-08-10 17:26:50.682] [LOG] Search request from { address: ‘10.0.0.5’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.683] [LOG] 10.0.0.0
[2020-08-10 17:26:50.686] [LOG] responding for port=11000
[2020-08-10 17:26:50.688] [LOG] responding for port=11001
[2020-08-10 17:26:50.689] [LOG] responding for port=11002
[2020-08-10 17:26:50.690] [LOG] responding for port=11005
[2020-08-10 17:26:50.692] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: “ssdp:discover”
MX: 3

from 10.0.0.5:50000
[2020-08-10 17:26:50.693] [LOG] Search request from { address: ‘10.0.0.5’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.694] [LOG] 10.0.0.0
[2020-08-10 17:26:50.697] [LOG] responding for port=11000
[2020-08-10 17:26:50.699] [LOG] responding for port=11001
[2020-08-10 17:26:50.700] [LOG] responding for port=11002
[2020-08-10 17:26:50.701] [LOG] responding for port=11005
[2020-08-10 17:26:50.704] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: “ssdp:discover”
MX: 3

from 10.0.0.5:50000
[2020-08-10 17:26:50.705] [LOG] Search request from { address: ‘10.0.0.5’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.708] [LOG] 10.0.0.0
[2020-08-10 17:26:50.713] [LOG] responding for port=11000
[2020-08-10 17:26:50.715] [LOG] responding for port=11001
[2020-08-10 17:26:50.716] [LOG] responding for port=11002
[2020-08-10 17:26:50.717] [LOG] responding for port=11005
[2020-08-10 17:26:50.719] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: “ssdp:discover”
MX: 3

from 10.0.0.5:50000
[2020-08-10 17:26:50.720] [LOG] Search request from { address: ‘10.0.0.5’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.721] [LOG] 10.0.0.0
[2020-08-10 17:26:50.724] [LOG] responding for port=11000
[2020-08-10 17:26:50.726] [LOG] responding for port=11001
[2020-08-10 17:26:50.727] [LOG] responding for port=11002
[2020-08-10 17:26:50.728] [LOG] responding for port=11005
[2020-08-10 17:26:50.730] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: ssdp:all
MAN: “ssdp:discover”
MX: 3

from 10.0.0.5:50000
[2020-08-10 17:26:50.731] [LOG] Search request from { address: ‘10.0.0.5’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.732] [LOG] 10.0.0.0
[2020-08-10 17:26:50.735] [LOG] responding for port=11000
[2020-08-10 17:26:50.737] [LOG] responding for port=11001
[2020-08-10 17:26:50.738] [LOG] responding for port=11002
[2020-08-10 17:26:50.740] [LOG] responding for port=11005
[2020-08-10 17:26:50.744] [LOG] << server got: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST: upnp:rootdevice
MAN: “ssdp:discover”
MX: 3

from 10.0.0.5:50000
[2020-08-10 17:26:50.745] [LOG] Search request from { address: ‘10.0.0.5’, family: ‘IPv4’, port: 50000, size: 1024 }
[2020-08-10 17:26:50.747] [LOG] 10.0.0.0
[2020-08-10 17:26:50.751] [LOG] responding for port=11000
[2020-08-10 17:26:50.753] [LOG] responding for port=11001
[2020-08-10 17:26:50.754] [LOG] responding for port=11002
[2020-08-10 17:26:50.755] [LOG] responding for port=11005
[2020-08-10 17:29:59.025] [LOG] Please configure the option vcgencmd
[2020-08-10 17:31:37.427] [LOG] Please configure the option vcgencmd
[2020-08-10 17:31:42.434] [LOG] Please configure the option vcgencmd
[2020-08-10 17:32:02.023] [LOG] Stopping PM2 process: mm
[2020-08-10 17:32:02.080] [LOG] Error: process or namespace not found
at /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2/lib/API.js:1538:28
at /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2/lib/Client.js:734:12
at /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2-axon-rpc/lib/client.js:45:10
at Parser. (/home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2-axon/lib/sockets/req.js:67:8)
at Parser.emit (events.js:200:13)
at Parser._write (/home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/amp/lib/stream.js:91:16)
at doWrite (_stream_writable.js:417:12)
at writeOrBuffer (_stream_writable.js:401:5)
at Parser.Writable.write (_stream_writable.js:301:11)
at Socket.ondata (_stream_readable.js:713:22)
[2020-08-10 17:32:11.797] [LOG] Stopping PM2 process: mm
[2020-08-10 17:32:11.831] [LOG] Error: process or namespace not found
at /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2/lib/API.js:1538:28
at /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2/lib/Client.js:734:12
at /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2-axon-rpc/lib/client.js:45:10
at Parser. (/home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/pm2-axon/lib/sockets/req.js:67:8)
at Parser.emit (events.js:200:13)
at Parser._write (/home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/amp/lib/stream.js:91:16)
at doWrite (_stream_writable.js:417:12)
at writeOrBuffer (_stream_writable.js:401:5)
at Parser.Writable.write (_stream_writable.js:301:11)
at Socket.ondata (_stream_readable.js:713:22)
[2020-08-10 17:32:31.117] [LOG] Shutting down server…
[2020-08-10 17:32:31.119] [LOG] Stopping module helper: updatenotification
[2020-08-10 17:32:31.120] [LOG] Stopping module helper: MMM-AlexaControl
[2020-08-10 17:32:31.121] [LOG] Stopping module helper: MMM-OnScreenMenu

[sdetweil]

@Michael-Schw said in MMM-AlexaControl or MMM-AlexaOn/Off setup:

restart Spiegel pm2
spiegel refresh
Spiegel Monitor
stop Spiegel pm2

these names are device names.

remember these are plugs, so the command is alex turn on (device name) , or alexa turn off (device name)

there is a file in the translations directory for changing the device names… and language

mine looks like

{
    "PAGE": "page ",
    "REFRESH": "refresh mirror",
    "RESTART": "restart mirror",
    "STOP": "stop mirror",
    "REBOOT": "reboot mirror",
    "SHUTDOWN": "shutdown mirror",
    "MONITOR": "mirror"
}

my extension to this was to put the name between any 2 words
reboot mirror = reboot [name] mirror

my mirrors are named,
office, hall, desk, desktop, catalina, nano

I changed Monitor to Mirror
(and also provided deviceName:??? in config)

so I can say

alexa turn off hall mirror

U would say (unless u change the translations file, and redo disocvery, I think u have to delete the devices to get new name used)
alexa turn off spiegel monitor

alexa turn on spiegel refresh

some of the verbiage is hard, but best u can do with on/off switches

[sdetweil]

@Michael-Schw said in MMM-AlexaControl or MMM-AlexaOn/Off setup:

[2020-08-10 17:29:59.025] [LOG] Please configure the option vcgencmd
[2020-08-10 17:31:37.427] [LOG] Please configure the option vcgencmd
[2020-08-10 17:31:42.434] [LOG] Please configure the option vcgencmd
[2020-08-10 17:32:02.023] [LOG] Stopping PM2 process: mm

do pm2 status
the name there is the name of the pm2ProcessName: config option

my config , on mirror system ‘desk’

		{
			module: "MMM-AlexaControl",
			disabled: false,
			position: "bottom_left",
			config: {
				deviceName: "desk",
				image: false,
				pm2ProcessName: "MagicMirror",
				vcgencmd: "hide",
				monitorToggle: true,
				startPort: 16000,
				reboot: true,
				shutdown: true,
				stop: true,
			},
		},

[sdetweil]

from the README.md

### Control devices
These are configured devices you can use. If you want to change their name you must edit the translation file inside `/translations/en.json`. You can also add languages. 

| Option            | Description
| ----------------- | -----------
| `refresh`         | This refreshs your Mirror. <br> ***Default value:*** `true` <br> ***Possible value:*** `true` and `false`
| `restart`         | This restarts your Mirror with PM2. So make sure the `pm2ProcessName` is right. <br> ***Default value:*** `true` <br> ***Possible values:*** `true` and `false`
| `stop`            | This stops your Mirror with PM2. So make sure the `pm2ProcessName` is right. <br> ***Default value:*** `true` <br> ***Possible values:*** `true` and `false`
| `reboot`          | This reboots your Pi. <br> ***Default value:*** `false` <br> ***Possible values:*** `true` and `false`
| `shutdown`        | This shutdowns your Pi. ***Note:*** When you shutdown the Pi your devices aren't available. So you must start your Pi manually. <br> ***Default value:*** `false` <br> ***Possible values:*** `true` and `false`
| `monitorToggle`   | This can switch your monitor on and off. Make sure the used command work for you. Look at the option `vcgencmd` <br> ***Default value:*** `true` <br> ***Possible values:*** `true` and `false`

devices not found

1. Devices not found: <br>
    * Make sure that your Alexa and Pi are in the same Wifi. I had also the problem that my Pi was in the 2.4GHz Wifi and my Alexa in the 5GHz Wifi. It's only a problem when you discover the devices. To solve the problem disable one of the Wifis for a moment or turn the Wifi on your Pi on and off till it works.

    * Have you used the port before? Try every devices from the mirror. Probably the name is wrong. If that happen delete the device and discover for new devices. Define yourself ports for notification and custom devices to prevent this problem.

NOT in the readme

the startPort MUST BE different for each MagicMirror device

the discovery records the ip address and port for each device, when an action is required, alexa send a web request to that ip and port. (which the module handles)

[Michael Schw.]

@sdetweil thank you for the help btw!!!

ok i figured out that my tv which i use as the display (Samsung LE-32 C530) has HDMI-CEC so i tried it with that and it works after i installed the cec module.
its just a shame that the tv needs 15 seconds to boot (EVERYTIME!!) and i cant disable the pop up on start which shows the source and the hdmi port used.

How can i stop the standby mode for the raspberry pi? because if the screen is off for a certain time and i turn it on again it shows me a blank black screen until i press a button or mouve the mouse (which i don want to have connected later on).

How can i make the mirror to autostart on booting the raspberry?

I have no shutdown command. Can i safley turn off the pi with this? and if yes, how do i get it?

I really wanna make this thing work perfectly. i even thinking of adding an ir frame to make it touchscreen =)

[sdetweil]

@Michael-Schw if you don’t use pm2 you should, it will start at boot… if you didn’t install it with my scripted install, then use the fixuppm2.sh script from here
https://github.com/sdetweil/MagicMirror_scripts

just cut/paste that one line to run that script.

shutdown and reboot are commands built in to linux

sudo shutdown now (-r | -h, -r means reboot, -h means halt)
sudo reboot , is the same as sudo shutdown -r

turn off the pi screen saver, also see my screensaveroff script…
(again if you had run my script as part of install, it would have prompted and done all this for you.
my script is listed in the alternative install section of the MM doc)…

none of my tvs support cec, so I created my own module for sleep (using a webcam for wakeup), it just hides all the modules,
alexaControl supports that too (vgencmd:‘hide’)
MMM-SleepWake

my pis & tvs run 24x7

[Michael Schw.]

@sdetweil thank you…you are a genius😁

I installed that automated update now but how do i excactly turn the screensaver off…i cant find your script…do you have a link for that?

And how can i start the mirror automaticly on boot of the raspberry? And is there any posibillity that the pi reboots itself if he needs it or should i just say it sometimes to alexa? Because if i let it run 24/7 it will at some time become really slow i think.

So what do i have to add in the option pm2processname for the alexa module?
Because refresh and monitor toggle are working but stop and restart isnt.
And i dont have shutdown at my alexa devices for the mirror.

[sdetweil]

@Michael-Schw i’m sorry, I do not understand…

you do NOT ‘install’ anything from my scripts repo. you just execute the commands I have documented.

to turn off the screensaver you copy/paste this one line to a terminal window on the pi

bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/screensaveroff.sh)"

to setup for start at boot, you run the pm2 script, the same way

bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/fixuppm2.sh)"

then you can also stop/restart the process
pm2 status will tell u it anything is running

pm2 start number| name
will start that named process

pm2 restart, stop, show, list, are other commands

pm2 logs --lines=?? will show the terminal window output of the processes (?? is a number)

pm2 --help will give u the syntax

the alexaControl module needs the NAME of the pm2 process definition

 pm2 status
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ MagicMirror        │ fork     │ 8    │ stopped   │ 0%       │ 0b       │
│ 1  │ smart-mirror       │ fork     │ 35   │ stopped   │ 0%       │ 0b       │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘

so for MM it would be whatever is listed for the name

to change the name, u need to delete the entry (see the pm2 help for the syntax here)
and create it again, after modifying the ~/MagicMirror/installers/pm2_MagicMirror.json file

then rerun my fixuppm2.sh script again.

the devices added by AlexaControl are defined in the translations/??.json file, here is the default en.json

{
        "PAGE": "page ",
        "REFRESH": "refresh",
        "RESTART": "restart pm2",
        "STOP": "stop pm2",
        "REBOOT": "reboot pi",
        "SHUTDOWN": "shutdown pi",
        "MONITOR": "monitor",
        "USB": "USB"
    }

so the devices are

 "refresh",
 "restart pm2",
 "stop pm2",
"reboot pi",
 "shutdown pi",
 "monitor"

remember these are electric outlet type devices, they can be on or off… that is all

so the alexa voice syntax is

alexa turn on (or off) device

alexa turn on refresh
alexa turn off monitor
alexa turn on restart pm2

etc