@Mykle1 May I butt in here. I was the one who started the question. I had to change the “start:” string in the package.json file to:
“start”:“node_modules/.bin/electron js/electron.js”
As Sam instructed. Once I did that, the “npm start” command got my MM2 running.
Thanks, BTW, for creating the walkthrough. I’m thrilled to have MM2 running on my old Acer laptop!
I stumbled onto MM2.5 10 days ago with little background in JS. I’ve had a blast getting my mirror set-up and am in awe of its capabilities and the developers contributing time and energy to this FREE project. Complaining about anything just seems misplaced to me. Instead, dig in a little and “learn the ropes”. Don’t know if I’ll dig in myself, but it sure looks like fun!
I may have given you the wrong impression…I really don’t know my way around Linux/Ubuntu. However, I was able to run your fixuppm2 script and I now see what you mean about not having to do anything else. I’m getting the behavior I want. When I reboot my machine MM2 starts right up. I’m getting ready to make another MM2 on a mini PC running Ubuntu. This time, I’m going to use your install script!
Looks like I should have looked closer to home than all over the web! I watched more closely at the boot-up procedure of my RPi and noticed a FAILED step involving dhcpcd. I looked that up on the web and found that newer distros don’t want you to edit the file /etc/network/interfaces. See this link for more information:
https://www.raspberrypi.org/forums/viewtopic.php?t=203530
I followed the directions there and then went back Raspberrypi.org to follow the directions for properly (and easily) setting up my wifi. Once I did all that the dhcpcd error was gone and my MM2.5 reboot issues were resolved.
Case closed.
I’ve finally gotten a video stream that’s stable on my MM2 using MMM-RTSPStream. I thought I’d share the set-up to give back to this community that has been so helpful to me!
Webcam - Reolink E1 Pro (https://www.amazon.com/gp/product/B07THQDSBD/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1)
Raspberry Pi 4 Model B
OS - Raspberry Pi OS 32-bit
Magic MIrror 2.13.0 (installed using sdetweil scripts at https://github.com/sdetweil/MagicMirror_scripts
Followed instructions for camera set-up
Installed MMM_RTSPStream following instructions and config.html link to start
Could not use vlc, used omxplayer instead
Install omxplayer if necessary (using Snapcraft at https://snapcraft.io/install/omxplayer-pi/debian)
Final, working configuration:
{
module: "MMM-RTSPStream",
position: "bottom_right",
config: {
autoStart: true,
rotateStreams: false,
rotateStreamTimeout: 10,
moduleWidth: 308,
moduleHeight: 231,
localPlayer: 'omxplayer',
remotePlayer: 'vlc',
showSnapWhenPaused: false,
remoteSnaps: false,
shutdownDelay: 12,
stream1: {
name: 'Your Own Label',
url: 'rtsp://admin:[Your Password]@[Your IP address]:554/h264Preview_01_sub',
frameRate: '7',
hdUrl: 'rtsp://admin:[Your Password]@[Your IP address]:554/h264Preview_01_sub',
snapshotType: 'url',
snapshotRefresh: 10,
width: 400,
height: 350,
absPosition:{
top: 700,
right: 1910,
bottom: 1050,
left: 1310,
},
},
}
},
The “moduleWidth” and moduleHeight" are irrelevant. What sets the size and position of the video window are the “width” and “height” values along with the “absPosition” values for “stream1”. The values that worked for me may not work for you so some trial error will be involved. Unless, of course, you completely understand the screen geometry for your MM2. I don’t so I had to go through a trial and error process to get the position just right. Part of my challenge was a body “zoom” value in my custom.css that added a level of complexity I never quite figured out. No matter, my step-by-step process resulted in a video stream the size I wanted and in the place I wanted. I also set the border width to 0 in MMM-RTSPStream.css file as follows:
.MMM-RTSPStream .innerWrapper {
position: relative;
width: 352px; /* Video width + 2*border + 2*padding */
height: 242px;
border: 0px solid white;
The bottom-line is a stable video feed from my Reolink webcam in the lower-right corner of my MM2. Hope this helps!
I’d like to use MMM-RTSPStream to display a snapshot of my Wyze camera’s RTSP stream every 5 minutes. I can manually generate a .jpg snapshot using the following console command:
ffmpeg -y -i rtsp://#myUsername#:#myPassword#@192.168.1.117:554/live -vframes 1 /home/pi/image.jpg
However, I can’t get this file created or displayed on my MM2 screen using MMM-RTSPStream. All I see on my MM2 screen is a dark-gray area surrounded by a white frame in the bottom-right corner of the screen. Based on my reading of the module’s instructions, I should be able to do this. Below is the MMM-RTSPStream section of my MM2 config.js file. Maybe someone can spot my error(s) that’s keeping this from working properly??? Thanks for any help provided.
{
module: "MMM-RTSPStream",
position: "bottom_right",
config: {
autoStart: true,
rotateStreams: false,
rotateStreamTimeout: 10,
moduleWidth: 354,
moduleHeight: 250,
localPlayer: 'ffmpeg',
remotePlayer: 'ffmpeg',
showSnapWhenPaused: true,
remoteSnaps: true,
shutdownDelay: 12,
stream1: {
name: 'DWBPanCam',
url: 'rtsp://#myUsername#:#myPassword#@192.168.1.117/live',
frameRate: '15',
hdUrl: 'rtsp://#myUsername#:#myPassword#@192.168.1.117/live',
snapshotUrl: '/home/pi',
snapshotType: 'file',
snapshotRefresh: 60,
protocol: 'tcp',
width: undefined,
height: undefined,
ffmpegPort: 554,
},
}
},
My RPi loses wifi connection often so I set up a daily reboot (using crontab). It works most of the time, but often enough Magic Mirror won’t start after the reboot using PM2. Sometimes MM starts, but the fonts are all very small. Sometimes it takes 3-4 manual reboots of the RPi to get MM up and running again. Just wondering whether anyone else has observed this in their own MM and found a fix and/or if anyone has suggestions on how to approach this problem. Thanks in advance for any help!
Sometimes when I reboot (sudo reboot now), the MM (autostarting with PM2) starts up with fonts that are way too small. I’ll go through the reboot procedure again and it often, but not always, starts with the correct fonts. Every once in a while I’ll have to reboot a third time. Once the MM is up and running it’s very stable. Has anyone experienced this and solved the problem? Can anyone suggest a place to start to diagnose and solve this problem? Thanks!
@bhepler Well…the WebView works, but MMM-RAIN-MAP works better. Thanks for the recommendation!
I found an alternative to the Dark Sky radar. I decided to install the MMM-WebView module and place a National Weather Service radar feed inside (https://radar.weather.gov/region/pacsouthwest/standard). Since I have my Magic Mirror set to refresh every 5 minutes it’s possible to update the radar image often. So far, things are working well. The MMM-Webview module is well-documented and I was able to get it up and running in just few minutes. I’m NOT a power user of the Magic Mirror so the module documentation was handy. Congrats to the developer!
@sdetweil I must have made a mistake when using your script command to upgrade:
bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)”
After I backed-up altered files and modules, I used the command:
git pull && npm install
and the MMM-AQI module works again. Thanks for pointing me in the right direction!
@sdetweil said in MMM-AQI stopped working:
pm2 log --lines=100
OK…now I get it. I used:
pm2 log --lines=100
to view the log. Lots of red text having to do with the RTSP MM module. I’ll keep looking for errors having to do with expired certificates.
@sdetweil Thanks so much for the reply! Unfortunately, I only understood the first part. OK…“request” still works. How do I view mm messages? I used your script to update to the latest version earlier. How do I go about determining whether 2.17.1 was installed properly?
In recent days, the MMM-AQI module on my MM2 has stopped working. I’ve checked my token on the World AQI website and it delivers the correct data so that part’s OK. Can anyone suggest other things to check? The module depends on “request” that’s been deprecated. Could that be an issue? Thanks for any suggestions provided!
This is an update to my post detailing my experience with the WWW-RTSPStream module. My implementation of the module in my MM2 was working OK, but I still had some interruptions when the video stream I was displaying would go black. Things got worse when I introduced a new WiFi router to improve coverage in my home. I had been depending on my OEM Uverse modem/router. I disabled the modem’s WiFi and added a Netgear RAX70 router to handle the WiFi duties in my home. For reasons beyond my understanding, this caused my MMM-RTSPStream module to be less stable. So, I decided to try a new IP camera. I chose a Wansview 1080 outdoor wireless IP camera that emphasized its use of the RTSP protocol. It’s this one:
https://www.amazon.com/gp/product/B08C4YXV51/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
At only $40 I wasn’t really expecting much, but I was pleasantly surprised. Their installation process was about as simple as it gets and the RTSP URLs they supply in their app were easy to copy/paste into the MMM-RTSPStream config.sys section of the MM2. I’ve had it up and running for 2 days now and haven’t had any down time. For the first time, I can actually depend on the MMM-RTSPStream module to show me a video stream that’s current. For what it’s worth, I’ve pasted my config.sys section for the MMM-RTSPStream below.
{
module: "MMM-RTSPStream",
position: "bottom_right",
config: {
autoStart: true,
rotateStreams: false,
rotateStreamTimeout: 10,
moduleWidth: 308,
moduleHeight: 231,
localPlayer: 'omxplayer',
remotePlayer: 'vlc',
showSnapWhenPaused: false,
remoteSnaps: false,
shutdownDelay: 12,
omxRestart: 1,
debug: true,
stream1: {
name: 'Garage',
url: 'USE RTSP URL FROM WANSVIEW APP',
frameRate: '30',
hdUrl: 'USE RTSP URL FROM WANSVIEW APP',
protocol: 'tcp',
timeout: 20,
snapshotType: 'url',
snapshotRefresh: 10,
width: 400,
height: 350,
absPosition:{
top: 700,
right: 1910,
bottom: 1050,
left: 1310,
},
},
}
},
@sdetweil Yes…when I open the URL I’m trying to display, it resizes nicely so all the information (in this case, data from a local weather station) is displayed to fit whatever screen size I choose. In other words, it’s responsive. I wonder if there are parameters I can add to the URL that will affect it’s display size??? I suppose I’ll need to experiment with that a bit.
I’m able to display web content using WWW-iframe-ping, but the content is too large so I’m only getting a sub-section of the webpage. How do I go about reducing the size of the web content to fit inside the frame I’ve created in the top_right region of my MM2? Thanks!
