@cr4z33 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
Can you please fix this?
Please post your PM2 logs when this happens so I can try and troubleshoot. (Run pm2 logs in an SSH terminal, or post the excerpt from the files in ~/.pm2/logs/).
@richland007 Yes, that’s correct about all the modules showing up as switches. I haven’t tested a maximum number of modules yet, so if you hit a limit let me know. You may have to re-run Discover a couple times if it takes longer than 20s to find all of your devices.
I feel your pain about MirrorMirrorOnTheWall, that’s why I made this one for myself.
@MoreLinux Glad you got it working!
@chassain-0 I’ll update the minimum version. I run V2.6-dev with no issues and didn’t test lower versions.
@j-e-f-f Thanks. I got it with the following. I was just wondering if you had a config option for it that I missed.
.MMM-DarkSkyForecast .forecast-container .wind-gusts,
.MMM-DarkSkyForecast .forecast-container .accumulation {
display: none !important;
}
@richland007 Yes, it can, in conjunction with another module like MMM-Remote-Control or MMM-OnScreenMenu.
Config section to do this with MMM-Remote-Control (see here for specifics on the module identifier needed):
{
module: 'MMM-AlexaOnOff',
config: {
devices: [{
name: "Clock Module",
on: {
notification: "REMOTE_ACTION",
payload: { action: "SHOW", module: "module_1_clock" }
},
off: {
notification: "REMOTE_ACTION",
payload: { action: "HIDE", module: "module_1_clock" }
},
}]
}
}
Config section to do this with MMM-OnScreenMenu:
{
module: 'MMM-AlexaOnOff',
config: {
devices: [{
name: "Clock Module",
on: {
notification: "ONSCREENMENU_PROCESS_ACTION",
payload: { actionName:'moduleShow1', name: 'clock' }
},
off: {
notification: "ONSCREENMENU_PROCESS_ACTION",
payload: { actionName:'moduleHide1', name: 'clock' }
},
}]
}
}
@j-e-f-f Awesome module! Great replacement for MMM-Wunderground.
Is there a way to turn off the total precipitation and max wind speed for the forecasts in the table, without turning it off for the current conditions?
Simple Mirror Control and module notifications from your existing (external) Home Assistant (Alexa/Google Home/HASS.io) with minimal setup using the Wemo protocol.
Yes, this is yet-another-Alexa-module; however, I hadn’t found one that did not require setting up some special Alexa skill or configuring an AWS account, etc.
This module uses the Belkin Wemo protocol (via fauxmojs) to receive on/off notifications from an Amazon Echo (or Google Home Hub, or anything that can discover and control a Wemo device). It creates “virtual” Wemo devices on your network that the home assistant can find, and then receives ON or OFF commands for those devices. The module simply takes these, and converts them to module notifications for other modules to work with.
Main Features:
Examples:
[card:shbatm/MMM-AlexaOnOff]
This is a simple module which extends the Node.js console logging capabilities of the MagicMirror² project through implementation of the tracer Node.js module, including adding timestamps, call sources, and stack traces.
By default, this module will intercept and format ALL console log messages from the MagicMirror instance once it is loaded so no additional changes need to be made to individual modules. If they log output using the standard console.log() or console.error() they will be reformatted and pretty printed.
Before MMM-Logging:
0|mm | Starting MagicMirror: v2.6.0-dev
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-Logging
0|mm | No helper found for module: alert.
After MMM-Logging:
0|mm | Starting MagicMirror: v2.6.0-dev
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | 2018-12-05T12:42:51 <log> Initializing new module helper ... (js/app.js:128 loadModule)
0|mm | 2018-12-05T12:42:51 <log> Module helper loaded: MMM-Logging (js/app.js:161 loadNextModule)
0|mm | 2018-12-05T12:42:51 <log> No helper found for module: alert. (js/app.js:163 )
[card:shbatm/MMM-Logging]
Current Version: 1.0.1 – CHANGELOG
@citizendevpi I started looking at VLC as an alternative to OMXPlayer but didn’t make it very far (honestly, just not enough time).
The most promising looked to be webchimera.js with VLC built for hardware acceleration, but the original repo for webchimera.js is marked abandoned. It looks like at least 1 fork is still active, but I didn’t get as far as testing anything.
If you have the capability to pursue it, I’d love some help. From what I have looked at, it should be a close-to-drop-in replacement for the FFMPEG version of this Module, and if that works, I could eliminate all of the OMXPlayer references (read: headaches).
References I’ve found:
https://thepi.io/how-to-compile-vlc-media-player-with-hardware-acceleration-for-the-raspberry-pi/
https://github.com/limoragni/WebChimera.js
@cr4z33 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
It is now offset compared to its module position.
Play with the moduleOffset and absPosition config options. Search this forum for those and check out the README on GitHub for details of what each one does.
@cr4z33 said in [MMM-RTSPStream] - Video Streaming from Live Feeds & Security Cameras:
I found out that the stream stops as soon as I ask something to Google Assistant (MMM-AssistantMk2 + MMM-Hotword by @Sean ) and it replies.
Please check the web browser console (ctrl+shift+i) and see if for some reason AssistantMk2 or Hotword are sending a pause/hide command to other modules. You would see something like: MMM-RTSPSTREAM is suspended.... Also, after the stream disappears, check the status of PM2 (pm2 status from ssh/terminal) and see if omx_streamX is still running. That will let me know if the module is telling the stream to stop or if omxplayer is giving up.
Regarding the border alignment, search this forum and/or the closed issues on GitHub, it’s been answered before. @evroom’s solution looks correct to hide the border, but I can’t remember for sure.
Mini-rant: OMXPLAYER is the lowest resource player I’ve found to use for playing video streams on a Pi, but frankly, it’s a finicky b***h and has terrible logging to inform you of the problem. 90% of the issues raised with this module are caused by omxplayer itself, which, unfortunately I don’t have any better way to solve than any other user. That’s why I use pm2 to manage the streams so it will at least attempt to restart when it crashes.
@evroom, regarding the streams not stopping… Last week I found a bug in PM2’s API, calling stop on a process from node doesn’t work. I will work on a workaround until the PM2 devs correct the issue.