@costascontis Interesting… I have the same issue with the RTSP feed cutting out as soon as I activate the Google Assistant (MMM-AssistantMk2). Not sure whether it’s triggered by the mic, my guess is that it’s related to the screen output part of the MMM-AssistantMk2 module.

@mirko3000 Thanks! And agreed, I’ve opted for the regular temperature sensor instead.

@mirko3000 This looks like a great module, and can’t wait to try it! Just ordered the gateway, and will be ordering some temperature sensors soon.

Will the Smart Air Pressure Temperature Humidity Environment Sensor work with this module as well? Like this one on: Aliexpress

Thanks!

@Johans I had a similar issue, and was able to resolve it by re-installing the module.

I just realized that I also added the cam’s ip to the IP whitelist and moved this module to the top of the config; not sure if that did anything, but mine is working now, so it might be worth a shot.

@shbatm I did a fresh install of the module, and am pleased to inform you that it’s working fine now. Thanks for your help!

@shbatm I’ve tried changing the moduleOffset to 0.5, as well as some other experimental values, but unfortunately that didn’t do the trick.

The configuration itself should work, as I had it working with a different RTSP cam previously.

@shbatm Thanks for clarifying. I’ve removed protocol: 'tcp' from the config.

When executing the default command in Terminal, the video displays properly on my screen.

The MM logs indicate that the stream is started accordingly as well (see below), but unfortunately still nothing is visible on my Mirror.

0|mm       | Starting stream stream1 with args: [
0|mm       |     "--avdict rtsp_transport:tcp",
0|mm       |     "--win",
0|mm       |     "379.5, 841.5, 731.5, 1083.5",
0|mm       |     "--live",
0|mm       |     "--video_queue",
0|mm       |     "4",
0|mm       |     "--fps",
0|mm       |     "30",
0|mm       |     "rtsp://admin:admin@192.168.0.130:10554/tcp/av0_1"
0|mm       | ]

Hello,

@shbatm thanks for the great module!

In order to make my camera work in omxplayer, I need to enter the following command before the RTSP streaming URL in Terminal:

omxplayer --avdict rtsp_transport:tcp 

The RTSP stream works fine with the added command in omxplayer. Full working command for reference:

omxplayer --avdict rtsp_transport:tcp rtsp://admin:admin@192.168.0.130:10554/tcp/av0_1

Is there a way to add the command to the config in order for the camera to work?

When looking at node helper.js I see the following reference:

    if (this.config[payload.name].protocol !== "udp") {
        args.unshift("--avdict", "rtsp_transport:tcp");

I’ve tried to switch the protocol in the config to ‘udp’ (as well as ‘tcp’) to no avail. I hope you could point me in the right direction in order to solve this issue.

Full config below for reference:

   {
            module: 'MMM-RTSPStream',
            position: 'middle_center',
            config: {
                autoStart: true,
                rotateStreams: false,
                rotateStreamTimeout: 10,
                showSnapWhenPaused: false,
                moduleWidth: 354,
                moduleHeight: 240,
                moduleOffset: 0,
                localPlayer: 'omxplayer',    
                stream1: {
                    name: '360 Cam',
                    url: 'rtsp://admin:admin@192.168.0.130:10554/tcp/av0_1',
                    protocol: 'udp',
                    snapshotUrl: '',
                    snapshotRefresh: 10, // Seconds
                    frameRate: "5",
                    port: 9999,
                }
            }  

Thanks in advance!

@j-e-f-f The issue was resolved after a git pull - thanks for the quick fix!

@j-e-f-f Thanks for your module - it works great! I have one question: one of my trips involves using the light rail, however, the module list this as “(undefined)” opposed to the actual method of transportation. Do you have any suggestions how I could fix this?