Can you please post your config section? Have you enabled the API and provided an API key?

@richland007 it sounds like something simple has to be missing and the module isn’t loading, otherwise you would be seeing an error.

1. Please post your config anyways (or send to me in a chat if you prefer). It may be something simple missing.
2. Confirm you are using a Raspberry Pi, on WiFi, using IPv4 (not IPv6 or ethernet–those are supported but require additional config options).
3. Confirm there are no errors from the module in the logs. You can run pm2 restart mm && pm2 logs to follow the logs through the whole restart process.
4. You can also add some console.log(...) statements in the initialize function in node_helper.js to see if you can diagnose any issues with it loading. Again, if it was making it that far and not loading you should have seen an error.

MODULE UPDATED

This module has been updated to Version 0.2.1 in the develop channel.

Major Changes:

• Removed all of the server-side functions in favor of using MMM-Remote-Control pending PR#104. When using this version, you will need to also have MMM-Remote-Control Version 2.0.0 or above installed for all functions to work. This is a strategic move to allow simplification of this module and focus on the front-end, while MMMRC handles the heavy lifting on the back-end.
• You can now use MMMRC as a menu item, or the whole menu:
  

Once the pull request is accepted for MMM-Remote-Control, this will be merged into the master branch.

Additional Features Added:

• Dynamic Module Control menu – uses the new API to create a Module Control menu on the remote page to control other modules via notifications.
• Custom Menu – ability to specify your own custom menu items from a file (for advanced users)
• Use PM2 API to control restarts/stops of MM. Can also support starting/stopping other PM2 scripts by passing processName: “scriptToUse” in the query payload.

Example Dynamic Menu for MMM-Carousel w/ Navigation

@barnosch said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:

the delay between the switch is useless.

I agree, unfortunately this is a an OMXPlayer problem – it takes anywhere from 5-10s to actually open and play a stream, so rotating the streams with OMXPlayer is limited unless you’re willing to accept the delay. I’ve played with everything I can think of to leave a stream open in the background–but nothing worked. The shutdown delay option only affects FFMPEG.

@djuscha For some reason only 1 stream is being started (the PM2 status is showing STOPPED for the other stream). I think I must have broken something in one of the last releases, try reverting back to an old version and see if it works:

cd ~/MagicMirror/modules/MMM-RTSPStream
git checkout f583553

I will work on troubleshooting and see what I broke.

@richland007

First, as requested, here is an example config section:

{
   module: 'MMM-AlexaOnOff',
   config: {
      devices: [{
         name: "Magic Mirror",
         on: {
            notification: "ONSCREENMENU_PROCESS_ACTION",
            payload: {
               actionName: 'monitorOn'
            }
         },
         off: {
            notification: "ONSCREENMENU_PROCESS_ACTION",
            payload: {
               actionName: 'monitorOff'
            }
         },
      }]
   }
},

When you start MagicMirror, you should see a line like this in your log file. If you don’t, then it’s a problem with the module installation. Make sure you’ve run npm install from inside the MMM-AlexaOnOff folder.

FauxMo service started. Listening on 192.168.1.100:21900

And netstat -tulpn | grep electron should show something like this:

tcp        0      0 0.0.0.0:21900           0.0.0.0:*               LISTEN      3554/electron
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      3554/electron

Make sure your mirror and Alexa are on the same Wi-Fi. Make sure you delete any duplicate devices in your Alexa app or at https://alexa.amazon.com/spa/index.html#appliances then restart Discovery.

@djuscha Try 256, and make sure you restart the Pi after each adjustment.

Also, please check the MM logs and post if you see any errors. You should be seeing two calls to start omxplayer. You can also do pm2 status to make sure both streams are running.

@djuscha If you switch the order, does the opposite one show up? You may need to change the CPU/GPU memory split in your Pi – sudo raspi-config find the “Memory Split” option and increase from 64 to 128.

@xela I’m very glad you could get it working, and I wish you a speedy recovery as well!

You can use a Node.js module like this one: https://www.npmjs.com/package/excel-as-json to save the data in a convenient format (JSON) and then use a MM module like https://github.com/timdows/MMM-JsonTable to display it.