Offline
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
thats my config.js
So it means you were able to get the RTSP config to open?
And when you entered the URL for your cam, did it show you a video stream from your cam?
I forgot if it does do that, or just builds the config part for config.js.
@sdetweil said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
he did that
Sorry, then I misread.
I read:
url: ‘rtsp://admin:roland!?1971@192.168.2.140.2.108:554/cam/realmonitor?channel=2&subtype=0’,
So now I am confused :-)
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
yes, thats correct, querry follows after confirmation the url. then the stream follows
Then we might have a parsing issue with your URL.
I think your password may cause a problem.
The ! an ? may cause a problem as they have meaning for your bash shell.
Have to think on that …
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
User, passwot from camera, id from raspberry, port as suggested,
I suggested to NOT use a port, so to ditch the :80 or :554.
And when using the omxplayer command, you will need to supply the cam IP.
Does your spelling check change the word IP in id??
I know it can be confusing, but you will need to read things right in order for us (the community) to be able to help you. He says in a friendly tone and manner :-)
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
- query answered
Did vlc player come with this query for user and password?
The reason for supplying it in the URL is to not have to supply user and password.
So, perhaps omxplayer has the same issue, but it will not ask for user and password like vlc player does.
When vlc did not ask for the user and password, then we know the URL is correct, or at least can be parsed correct.
One more thing to try. Just leave out the port altogether.
I use it without specifying the port.
omxplayer --genlog --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://admin:roland!?1971@192.168.2.108/cam/realmonitor?channel=2&subtype=0'
When you run MM locally on your Pi, then your MM IP is your Pi IP.
IP being the IP address, not an id.
When you are able to open the RTSPStream configurator using 0.0.0.0.8080/MMM-rtspStream, then that’s fine.
Continue with step 2 from this post:
https://forum.magicmirror.builders/topic/2743/mmm-rtspstream-video-streaming-from-live-feeds-security-cameras/379
@Number_5
Try with port 554, see previous post.
And see
https://github.com/shbatm/MMM-RTSPStream
“Using the module” on the config.html part I was referring to.
The IP there, is the MM IP, or localhost, not your cam IP.
Can you try with another port number (554 iso 80) ?
omxplayer --genlog --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://admin:roland!?1971@192.168.2.108:554/cam/realmonitor?channel=2&subtype=0'
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
ERROR: COMXPlayer::OpenFile - avformat_open_input
Okay, without getting rid of this error, omxplayer and therefore MMM-RTSPStream using omxplayer will not work for you.
I have an Axis cam and there it did not work because to the resolution I used, had to use one of the resolutions that is supported by the cam.
Where you able to open
http://your-mirror-ip:8080/MMM-RTSPStream/config.html
and see the cam there ?
Could try ffmpeg, but there I have to pass.
What camera are we talking about ?
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
ok sorry,
Nothing to be sorry for; you are learning as you go :-)
Could you please post commands and output using the </> tag ?
So, select the command or output and click on the </> symbol.
Does the log say anything useful ?
more omxplayer.log
Pleas do not post the complete log, unless small.
30 lines tops.
head -30 omxplayer.log
Better to stop MM temporarily or disable the module with disabled: true, and a restart of MM.
Also make sure omx_stream1 process is not running.
pm2 status
pm2 stop omx_stream1
pm2 delete omx_stream1
pm2 status
Then do the single quoted command, with logging enabled.
omxplayer --genlog --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://admin:roland!?1971@192.168.2.108:80/cam/realmonitor?channel=2&subtype=0'
Can you try with quotes (single, double) ?
omxplayer --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd "rtsp://admin:roland!?1971@192.168.2.108:80/cam/realmonitor?channel=2&subtype=0"
omxplayer --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://admin:roland!?1971@192.168.2.108:80/cam/realmonitor?channel=2&subtype=0'
when the command works, but still no video, then add --genlog
omxplayer --genlog --avdict rtsp_transport:tcp --win 786,424,1138,666 --live --video_queue 4 --fps 30 --no-osd 'rtsp://admin:roland!?1971@192.168.2.108:80/cam/realmonitor?channel=2&subtype=0'
This will creat a log file called omxplayer.log under the directory where you started omxplayer.
@Number_5
Command-line.
Better deactivate the module before (this in the config.js):
module: "MMM-RTSPStream",
disabled: true,
etc
@Number_5 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
If I see it correctly, then you have 2 MMM-RTSPStream modules active in your config and 2 stream1 defined, and therefore are trying to start 2 omx_stream1 processes.
I would concentrate on 1 config with 1 stream1.
To see if things works, try it with the BucksBunny config first.
Then give the other one a try (with the bunny removed).
I also would give the rtsp stream a go without MM, so standalone.
Somewhere in this thread there should be a description on how to do this; would need to search my notes for it.
@rjansy
Hi,
do you want to rotate your monitor clockwise or counter-clockwise?
See my response above on how I clockwise rotate my monitor.
Make sure you do not rotate via /boot/config.txt when using the css solution.
Set it to zero and reboot to activate.
Now in config.css, you have to counter-rotate, so -90 degrees, to have your MM displaying horizontal again.
So, you turn your screen +90 degrees, therefore you make it up again by rotating the contents of your screen -90 degrees.
When rotating your screen counter-clockwise, the opposite applies.
Good luck !
@Clubjack and others,
I noticed this problem too.
For instance my birthday lasted 2 days ( only got presents once though) and my wedding-day is one day forward (which will upset my wife).
The entries were made using Google Calendar (so not a calendar app that synchronizes with Google).
I notice this since 2020, but that does not mean it did not happen before, could have overlooked it.
When I ran a test with a dummy entry, it worked fine.
When I toggle a „faulty“ entry from repeating to not repeating and then back to repeating, the entry is shown correct.
I collected some data and will post it when I sorted it out a bit.
You can try this config for testing:
{
module: "MMM-RTSPStream",
position: "middle_center",
header: "MMM-RTSPStream Test",
config: {
autoStart: true,
rotateStreams: false,
rotateStreamTimeout: 10,
moduleWidth: 640,
moduleHeight: 360,
localPlayer: 'omxplayer',
remotePlayer: 'none',
showSnapWhenPaused: true,
remoteSnaps: true,
stream1: {
name: 'Buck Bunny',
url: 'rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov',
frameRate: 'undefined',
snapshotType: 'url',
snapshotRefresh: 10,
width: 640,
height: 360,
},
}
},