Read the statement by Michael Teeuw here.
MMM-AlexaControl or MMM-AlexaOn/Off setup
-
I have been trying to setup any of the 2 modules the installation and config goes well but when i reach the stage where i to discover devices on my alexa app it just doesn’t work!
-
@dave_ MMM-AlexaControl works well and MMM-AlexaOnOff does not work.
Can you post the config of the module, maybe somebody can help you? -
@Stoffbeuteluwe sure
-
//{
// module: ‘MMM-AlexaControl’,
// position: ‘middle_center’,
// config:{
// image: true,
// pm2ProcessName: “PM2”,
// vcgencmd: “vcgencmd”,
// }
// },ignore the // brackets.
-
@dave_ what port range did u specify? you need to set a unique port range for each mirror on your network.
I see it defaults. never mind.
if u are running a Spotify player on this machine, the two things fight over the discovery port, 1900. so u have to stop the Spotify client while Alexa does Discovery
-
@dave_ you should see messages like this on MM startup for alexacontrol
[2020-08-02 16:47:29.642] [INFO] Checking git for module: MMM-AlexaControl
[2020-08-02 16:47:29.675] [LOG] Adding multicast membership for 127.0.0.1
[2020-08-02 16:47:29.676] [LOG] Adding multicast membership for 192.168.2.11
[2020-08-02 16:47:29.677] [LOG] server is listening on 11000
[2020-08-02 16:47:29.679] [LOG] server is listening on 11001
[2020-08-02 16:47:29.679] [LOG] server is listening on 11002
[2020-08-02 16:47:29.680] [LOG] server is listening on 11005 -
@sdetweil hmm so should i stop the Spotify and try again? Or what port range Should i specify it to?
-
@dave_ you MUST stop the spotify thing , then restart MM, see those messages and then do alexa discover devices (using real echo device)…
once the devices are added, you can turn on the spotify tool …
-
@sdetweil so i did turn of the Spotify and when i launched the magic mirror it is not showing up anything it’s blank screen Like usually when there’s something with config it says a message but in this case it’s blank
-
@dave_ look at the console where u started mm.
pm2 logs --lines=100
or
in the window where u did npm start.black screen usually means missing library
u did npm install in the AlexaControl folder, right?
