@richland007 in the log is it showing all of the ports in the range open? (e.g. 21900-21936)?

My best bit of advice is always look for an easy starting point and don’t reinvent the wheel if you don’t have to…

Some possible inspiration… https://ourcodeworld.com/articles/read/55/top-5-best-jquery-scheduler-and-events-calendar-for-web-applications

Look at Todoist and MMM-Todoist. It has some integration/synchronization with Alexa’s lists.

https://get.todoist.help/hc/en-us/articles/212798949-How-can-I-use-Todoist-with-Amazon-Echo-

@djsunrise19 said in [MMM-AlexaOnOff] Simple Mirror Control from External Home Assistant (Alexa/Google Home/HASS.io):

Or should it work with “enp3s0”?

As long as the line in the log is returning your computers’ correct IP Address, enp3s0 appears to be working…

Check netstat tulpn | grep 21900 and make sure the port is open. Otherwise check that your Alexa is on the same network/WiFi/account as you expect. If you’re getting the port open, then it’s something with the network or Alexa causing the problems.

@djuscha, @Cr4z33 @barnosch @anthony6608 @bhepler @evroom, and anyone else using this module:

I just pushed a bunch of bug fixes for OMX Player to the develop branch. Please test and let me know if you are still seeing the same issues.

Fixes include:

• App closing now spawns a new process to actually kill the OMX streams, it was getting cut off in the middle of closing everything due to it being an async process and leaving streams open.
• Wait for DOM to be shown before calling to start the streams–this was causing the Fullscreen on Resume problems.
• Only start one stream at a time if we’re in RotateStreams mode
• Can jump to a specific stream in RotateStreams mode using notifications
• Fixed and cleaned up all notifications and control from other modules
• Fixed broken key bindings after MMM-KeyBindings upgrade
• Fixed issue where module was trying to connect to PM2 while it was already connected (e.g. stop stream 1 and start stream 2 back to back).

To switch branches:

cd ~/MagicMirror/modules/MMM-RTSPStream
sudo rm -R node_modules/
git fetch --al
git checkout develop
git pull
npm install

@cr4z33 Added something that might help. Please use the develop branch and update your change channel commands to :

{
notification: “RTSP-PLAY”,
payload: { stream:“stream1”, stopOthers: true }
}

EDIT: Nevermind, don’t do that. I fixed the glitch on the develop channel that was starting more than one stream when rotateStreams: true was set. Please try that and see if it works now.

@djuscha I’ve reverted the changes that I think broke the master channel. Please try updating your module to the current master branch and test.

@cr4z33 Still looking into it, but I just thought of something… it doesn’t look like you’re calling RTSP-STOP on the old stream anywhere when changing channels so right now it’s going to keep starting streams every time–there’s no “1 at a time” method when controlling it from notifications… yet.

@citizendevpi

Just confirming: you are using my version https://github.com/shbatm/octomirror-module not the original, correct?

@michael24h said in [octomirror-module] Monitor & Control an OctoPrint 3D Printer Server:

Looks like link isn’t complete. Should looks like this http://ip_address/webcam/?action=stream

Nope, that shouldn’t be it. He said his stream was working and the url parameter is just for the octopi instance, not the stream. The module assumes it needs to add /webcam/?action=stream” unless streamUrl is provided.