Kevin Townsend

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...

Hi @fribse, sorry to hear about the difficulty updating. I have a few questions for you: * after updating did you reinstall all of the `node_modules` for MMM-Screencast (pretty much...

Hey @qashaza! Huh odd, do you happen to know if/what ports `MMM-AlexaControl` is running on? I haven't looked into this module, but if it is running on port 8569 this...

Hey @dnwnd16561 this looks like a config issue. Can you paste your config.js in here (with all of the api keys removed). Thanks!

@pandora0309 this seems to be off topic for this issue. Can you please open a new issue with the logs of you starting up the app, trying to connect, and...

@IngveBoe this is a config issue, you most likely used the positioning args for MM and not MMM-Screencast. You can double check this on the [readme](https://github.com/kevinatown/MMM-Screencast/blob/master/README.md) If you are still...

What do you see? Can you send any logs or the config? thanks

Huh, @Mert4531 this is an odd one. - Do you have any more info/logs? - Can you reconnect to the Cast after "Closing" and close again? If you can get...

Hey @kr1st4ps sorry that it’s not working for ya. Can you paste your MM’s config in here (please remove all keys first :) Thanks, Kevin

So nothing looks out of the ordinary with that config (besides the commented out config). When you have the MMM-Screencast into the config are there any logs/errors in the terminal?...