@cr4z33

You’ll want the following settings which should give you 1 blank video box that does not show anything until you press play.

autoStart: false,
rotateStreams: true,
rotateStreamTimeout: 0,
localPlayer: 'omxplayer',
remotePlayer: 'none',
showSnapWhenPaused: false,
remoteSnaps: false,

I’m assuming you’re seeing the same glitch that is plaguing the last OMXPlayer version of this module. I’m working on it today to try and find what I broke. In the meantime, try reverting back and seeing if that fixes the issue. I just tested the following notification on the VLC version and it worked as expected, so it’s got to be something with omxplayer.

{
notification: "RTSP-PLAY",
payload: "stream3"
}

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

Also your new VLC based module sounds great.
But i guess, you maybe should create a whole new module for it?

The plan right now was to just leave it as another option for the localPlayer. OMXPlayer will still be an option for now as well. I don’t know if I’ll have time to split it out completely, but that would be much cleaner.

@mwoodage said in Unsuccessful video streaming - help please :):

Is it because the camera is 5MP and therefore there’s too much data for the VLC player to process?

That may be the case. Most cameras offer a second, lower-resolution stream that you could use for something like the mirror.

@citizendevpi Try adding debugMode: true, to the config and see if you get any useful information in the logs. I can’t remember if they’ll show up in the console or DevTools. Also, it’s been a while since I’ve used the module, but it will only show data when it’s actually printing too.

@djsunrise19

Please check the same things:

1. Check your MagicMirror version, if it’s lower than v2.5.0 and you don’t want to upgrade, you can try changing line 21 in MMM-AlexaOnOff.js to match your version.
2. You should see FauxMo service started. Listening on 192.168.x.x:21900 in your log file if the service started.
3. You can try testing with the example:

    cd ~/MagicMirror/modules/MMM-AlexaOnOff/node_modules/fauxmojs/example
    node example.js

You should see: started.. and then be able to discover ‘office light’ and ‘office fan’ on your Alexa.
4. Make sure you try discovery from alexa.amazon.com, not just your Echo.

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

from my local echo it would not find anything.

I just found this setting up some smart plugs last week – is your echo on a different account in your “Amazon Household” by any chance?

“Mirror” utilizing MMM-Remote-Control, that on On will send the command MONITORON and on Off with send the command MONITOROFF So will this work…I have no clue but just by dissecting your code???

Yes, that should work. Here’s mine verbatim:

        {
            module: 'MMM-AlexaOnOff',
            config: {
                devices: [{
                    name: "Bookcase Screen",
                    on: {
                        notification: "REMOTE_ACTION",
                        payload: { action: 'MONITORON' }
                    },
                    off: {
                        notification: "REMOTE_ACTION",
                        payload: { action: 'MONITOROFF' }
                    },
                },
                //{ add your other devices here },
                ]
            }
        },

Do you think i will have any issues with 37 modules??

I haven’t stress tested it like that yet. You can certainly try it… From the FauxMo notes, you may have to run Discover a few times to find them all. Just make sure you don’t have anything running on the block of 37 ports.

You can also try doing them in groups (you can send multiple notifications for each device’s on and off command, see earlier in this thread). Or use Profile Switcher or MMM-Carousel w/ Navigation (shbatm fork) to use “slides” of modules.

@anthony6608 The last error was my fault… it’s an issue with linking the PM2 module. I put a sudo where I didn’t need one, that’s been updated on Github.

I’m sorry it’s been frustrating–trust me, I (and I’m sure several other’s on here) know the feeling. I was going to say that I thought it was the module getting moved around by the other modules when they load that was causing the issues, but not if it’s happening with only this module loaded. It should be resizing itself to fit. I sent you a chat with an e-mail address–if you can, send me a short video or picture of what you’re seeing and I’ll see if I can diagnose.

Also–for the forums, when pasting logs, configs, or any other chunk of code, use three back-ticks (`) on their own line at the start and finish to make it pretty (you can add “shell” or “javascript” for syntax highlighting.

   ```javascript
   Your code here
   ```                   -

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

I’m fairly new to this so I am not sure what could be causing it?

I probably should have explained better above what the sed command was for. The current version of MagicMirror uses Electron version 2.0.16–this is defined in the package.json file in the MM directory. The sed command updates package.json to use Electron version 3.0.13 instead. It’s probably best to remove the node_modules directory first and reinstall (cleaner). I updated the steps above.

The problem with updating Electron is there is a reason MM still uses the lower version–it was working–we don’t know what else the new version is going to break. On mine, I had to update Node to v10.15 from v8.15 to get one of my other modules to work.

MMM-GoogleMapsTraffic module

I have a love-hate relationship with this module. I use it, but seems to break my other modules too (KeyBindings, OnScreenMenu)… I’ll look into the cause of this one, but if I had to guess-- The VLC window is just that, another window setting on top of the browser page that is MM. If something causes the browser to get focus (as simple as clicking the black background), the VLC window falls behind it. If you have a keyboard hooked up, try Alt + Tab and see if it comes back. I’m already looking for a way to make the VLC windows modal so they stay on top.

@aries1984 said in MMM-KeyBindings: Control your mirror with Amazon Fire Stick Remote and Generic Keyboard Inputs:

you talk about “KeyCode” being a part of the payload

Thanks for catching this. There must have been some remnants from the first version when that’s what I used. It’s been fixed now.

ANNOUNCEMENT: Version 1.3.0 - Updated 3-Jan-2019 - [BREAKING CHANGES] Remove server controls in favor of External Modules, Remove Python script in favor of Native Node.JS modules

Here are the highlights from this major change:

• This update had the overall goal of simplifying this module. I made a major philosophy change with this update, shifting from the original goal of this module performing a lot of its own sever-side functions and also relying on other modules to implement listeners to handle key presses-to this module being focused on listening to keys and letting other modules handle the heavy lifting.
• Removed all server-side controls from this module (monitor toggle, external interupts) in favor of declaring actions and sending notifications to other modules instead.
  • Instead of this module trying to figure out if it should do something like turn on the screen, before it sent the action out–now it just gets the action and sends it. If you want to control the screen, use a module made to do that, like MMM-Remote-Control.
• Removed Notify Server in favor of extensible REST API being developed for MMM-Remote-Control
  • The “notify” server was cumbersome and difficult to properly format. It was only really required as a way for the python script to send notifications back. The new REST API is much simpler and the bluetooth monitoring is now done within Node, so that makes this redundant.
• Added Actions to send notifications on a keypress rather than rely on other modules to actively listen for them.
  • Instead of requiring other modules to listen for specific “KEY_PRESSED” notifications, you can now translate key presses to notifications that other modules already understand.
  • The module is still extensible by other modules, and in fact, it has been made easier now. Rather than incorporate all of the code into your module, you can get a KeyHandler instance and add a few small functions to handle the key press notifications. The heavy lifting to validate a key press is done in the background. See this wiki page for updated instructions.