Which version of MMM-Carousel are you using? If you use this one: MMM-Carousel w/ Slide Navigation you can navigate left and right or jump to a particular slide by sending a notification from another module.
Just pushed an update to make this even easier. See the details at the bottom of the README
@imdickie If you were on the Master branch it makes sense now why you were getting duplicate views, it was using ffmpeg and looking at only the first port for both cameras. The work-in-progress branch does not use websockets/ports for local playback since OMXPlayer just draws directly on top of the MM’s browser window.
For the black screen: I forgot the wip branch has an additional node package required. This should take care of your problem:
cd ~/MagicMirror/modules/MMM-RTSPStream
git checkout wip
git pull
npm install
You may or may not need to also add a moduleOffset config option: see the posts above for pictures, if the video doesn’t line up with the border, you can add moduleOffset: X to shift the video over (where X is a number of pixels).
For more information about the wip branch, there is an updated README on the Github page: https://github.com/shbatm/MMM-RTSPStream/tree/wip
For pm2: it’s definitely not a requirement, but I find it’s nice to have; I included in the note above just in case you were already using it. It will automatically run the MM script for you on startup. See this page if you want more information.
To all using the module: Thanks for bearing with me, I haven’t had a lot of time this past month to finish out the hardware-accelerated version (wip/development branch) but I hope to get it done in the next month or so. I really do appreciate any feedback / issues you have to help me improve this module.
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]
You may want to take a look at the MMM-PIR-Sensor module and see if you can adapt it for your needs. It includes the ability to control a relay for turning on/off the monitor.
@Johans Which other modules are you using? It looks like you may be using something like MMM-ProfileSwitcher, there may be a conflict between these modules or it may be because of the % symbol in the password.
Also, when you switched to the wip branch, did you remember to re-run npm install in that folder? There are some additional dependencies for the wip branch.
@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' }
},
}]
}
}
@strawberry-3-141 @Anhalter42 – Wanted to thank you both for the suggestions.
I was able to fork and tweak @barnabycolby’s MMM-Carousel to manually switch between slides and show the page dots and navigation arrows without touching any core code. I also added the ability to move or change appearances of each module on a per-slide basis.
If anyone is interested my fork w/ navigation enabled is here: MMM-Carousel w/ Navigation & Moveable Modules – the navigation uses my module MMM-KeyBindings, which isn’t necessary if you just want to use a mouse or touchscreen.
@bhepler said in Library error after full reinstallation (full version Raspbian and MagicMirror version 2.5.0):
I would advise against using the Magic Mirror installation script at this time. It hasn’t been tested as well as the rest of the system. Perform a manual installation for better results.
Second this.
For anyone who comes across this error:
/home/pi/MagicMirror/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.27’ not found (required by /home/pi/MagicMirror/node_modules/electron/dist/electron) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR!
It may be caused by npm trying to install electron v4.0.0, this version has some reference errors on the Pi: https://github.com/electron/electron/issues/16205 and a lower version (v3.0.13) should be used.
See the installation instructions on the README.
(Only necessary if you want to, the ‘wip’ and ‘master’ are the same currently, but I will update the ‘wip’ with new features and bug-fixes first for testing. If you want to beta test, stay on ‘wip’)
cd ~/MagicMirror/modules/MMM-RSTPStream
git checkout master
git pull
npm install
http-server -p 9999
# From a web browser, navigate to http://mirror-ip:9999/config.html
# Once your config is made, press Ctrl+C to exit the config builder
# Restart your mirror and test!