MMM-Screencast icon indicating copy to clipboard operation
MMM-Screencast copied to clipboard

Port error: 1900 MMM-AlexaControl with MMM-Screencast.

Open vicarcmirror opened this issue 4 years ago • 4 comments

Hello, I hope you can guide me with the following problem. I am using the MMM-AlexaControl module together with your MMM-Screencast module. It turns out that when I want to run the 2 modules it sends me the following error

[2020-07-28 18: 50: 38.635] [ERROR] Error: EADDRINUSE link 0.0.0.0:1900 at dgram.js: 321: 18 in processTicksAndRejections (internal / process / task_queues.js: 84: 9) { errno: 'EADDRINUSE', code: 'EADDRINUSE', syscall: 'bind', address: '0.0.0.0', port: 1900

I think the problem is in the port, but I have not found the solution, and that's why I dare, to ask for your help. It's worth mentioning that I'm just getting started on this.

I am currently using a Raspberry pi 4, with node.js v12.18.3

Note: Dispense my English. I am using the google transducer. and many congratulations on your Module. Thank you.

vicarcmirror avatar Jul 29 '20 01:07 vicarcmirror

Hi @vicarcmirror,

Sorry about the issues you are having. MMM-Screencast uses port 8569 by default, but there is an optional config that you can use to change the port (use the port config option). I would recommend looking into MMM-AlexaControl and see what ports they use and choose another one for MMM-Screencast.

Also looking quickly through MMM-AlexaControl's code and readme, it seems that MMM-AlexaControl uses a whole range of ports (I believe starting 11000 or the startPort config). I'd recommend bumping that higher or using the default.

Finally, the port 1900 is an odd one? Did you set this somewhere for MMM-Screencast or MMM-AlexaControl to use? If so bump it up, i believe 1900 might be a reserved port for TCP.

Good luck!

kevinatown avatar Aug 26 '20 16:08 kevinatown

go the node_module of alexacontrol and change the port on line 141 on SSDPServices.js file

udpServer.bind(2900, ipaddress, function()

it works for me

bimbim2401 avatar Nov 29 '20 15:11 bimbim2401

Hi I wanted to confirm the screencast module problem with alexa-control. And thanks to bimbim2401 I solved the problem by changing the port on line 141 on SSDPServices.js file. This file is located in the path: /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/node-fauxmo/src. Replacing port 1900 with 2900 solved the problem: udpServer.bind(2900, ipaddress, function()

Thanks to kevinatown for the splendid module and to bimbim2401 for resolving this incompatibility

Simone7000 avatar Feb 14 '21 21:02 Simone7000

Hola Kevinatown/Mmm-Screencast.

Disculpa la tardanza con la contestación, la verdad es que no había tocado ya el proyecto..

Resulta excelente tu aportación con esta corrección funciona perfecto . Estoy trabajando con los siguientes módulos y no he tenido problemas; MMM-Remote-Control MMM-SmartWebDisplay MMM-Screencast MMM-AlexaControl

Y haciendo pruebas no me aparece ningun error funciona a la perfeccion. Indicame si necesitas alguna aportación y en donde lo puedo hacer..., no esperes mucho ok.

Muchisimas Gracias . Saludos.

.

El dom, 14 feb 2021 a las 15:38, Simone7000 @.***>) escribió:

Hi I wanted to confirm the screencast module problem with alexa-control. And thanks to bimbim2401 I solved the problem by changing the port on line 141 on SSDPServices.js file. This file is located in the path: /home/pi/MagicMirror/modules/MMM-AlexaControl/node_modules/node-fauxmo/src. Replacing port 1900 with 2900 solved the problem: udpServer.bind(2900, ipaddress, function()

Thanks to vicarcmirror for the splendid module and to bimbim2401 for resolving this incompatibility

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kevinatown/MMM-Screencast/issues/81#issuecomment-778845817, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOR5ZWPLVLKXH77RQ5YYWHDS7A7EFANCNFSM4PLDCFYA .

vicarcmirror avatar Mar 25 '21 22:03 vicarcmirror