MMM-AlexaControl or MMM-AlexaOn/Off setup

[Stoffbeuteluwe]

@dave_ MMM-AlexaControl works well and MMM-AlexaOnOff does not work.
Can you post the config of the module, maybe somebody can help you?

[dave_]

@Stoffbeuteluwe sure

[dave_]

@Stoffbeuteluwe

//{
// module: ‘MMM-AlexaControl’,
// position: ‘middle_center’,
// config:{
// image: true,
// pm2ProcessName: “PM2”,
// vcgencmd: “vcgencmd”,
// }
// },

ignore the // brackets.

[sdetweil]

@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

[sdetweil]

@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

[dave_]

@sdetweil hmm so should i stop the Spotify and try again? Or what port range Should i specify it to?

[sdetweil]

@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 …

[dave_]

@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

[sdetweil]

@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?

[dave_]

@sdetweil it’s finally showing on screen like the mm is working but still had no luck with discovery and Spotify is off

[sdetweil]

@dave_ did u see the startup messages from the module like i posted?

[dave_]

@sdetweil

I am not quite sure which line to look at but check the image

Just out of curiosity does it have to be alexa echo device like can’t a i use for a soundbar or speaker with built in alexa or maybe even the mobile app?

[sdetweil]

@dave_ u got the eaddressinuse error. something is using port 1900, this the the port we stopped Spotify to get access to

stop mm, then do

sudo netstat -a | grep 1900

in there is a response then something is still using the port.

I havent tried discovery from my Alexa app in a long time. since they made it possible via voice command

[dave_]

@sdetweil that’s what it says

[sdetweil]

@dave_
ok do this

sudo netstat -a -p | grep 1900

mine shows this when MM is running

sudo netstat -a -p | grep 1900
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           11153/electron.js 

[dave_]

@sdetweil ohh shit i had installed jellyfin media server ages ago and that’s what it’s saying how do i uninstall that 😂

[sdetweil]

@dave_ sorry, no idea… google might help

[dave_]

@sdetweil lemme see and I’ll let u know

[dave_]

@sdetweil can i just Change the ports? And then make ot work if yes what should i change it to

[sdetweil]

@dave_ no ssdp discovery only supports port 1900