Hi. There is a way to call, i.e, module controls/carousel/next slide from url?

but MMM_AlexaControl works, same concept… I use it for 4 Mirror devices (with alexa devices, not goggle home or GA)

Updated to version [1.0.1] - now includes browser methods for formatting the DevTools console (disabled by default) and ability to echo Module Notifications and Errors from the web browser back to the Node (back-end) console and logs.

great job,is there a way for the stream to go left or right of the printer info?

@j.e.f.f That could be, I wonder if when Electron starts it somehow removes any SIGINT listeners already created. With respect to running stop() during a MM crash – the main function in js/app.js is still attaching to process.on("SIGINT", ...) just upstream of the individual node_helper files. If MM crashes I think it should still call the stop() functions unless the node_helper array gets corrupted. An advantage to cycling through each node_helper would be that you don’t have multiple individual SIGINT listeners that are trying to call a process.exit before the other is done.

@looolz my install script sets up to monitor config.js. does sometimes…

It is possible to disable menu items area when mouse is not over main button or to create the items when the mouse is over then? The items are active even if hidden and it is possible to press them unintentionally.

Hi I just get a white border when my MM starts. I´m using VLC and in the player I can see the stream. Here are the error codes. [17.06.2021 08:31.58.706] [LOG] Starting stream stream1 using VLC with args --width 352 --height 242 -I dummy --video-on-top --no-video-deco --no-embedded-video --video-title=stream1 http://admin:password@192.168.1.79/video.cgi… [17.06.2021 08:31.58.728] [ERROR] Failed to start subprocess: [object Object]. [17.06.2021 08:31.58.751] [LOG] DP2: Config File Saved! [17.06.2021 08:31.58.752] [INFO] DP2: Running window resizers… [17.06.2021 08:31.58.768] [ERROR] DP2: Failed to start. [17.06.2021 08:32.05.769] [INFO] DP2: Running window resizers… [17.06.2021 08:32.05.779] [ERROR] DP2: Failed to start. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! magicmirror@2.15.0 start: electron js/electron.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the magicmirror@2.15.0 start script.

Description: MMM-JSONStatusChecker will periodically call a URL and display a “true / false” (or “connected / disconnected”) status based on the results of a value in a JSON response from the API call. Multiple instances of the module can be used to call different URLs/APIs using the same background helper. Each instance has it’s own configuration and refresh time. See the config options on GitHub for full details, but everything can be customized; including: the key/value in the response being evaluated, the icon displayed, the CSS classes applied for true/false, the text for each status, and even whether or not to show an alert on status change. Screenshots: [image: screenshot.png] Download: [card:shbatm/MMM-JSONStatusChecker] Version 1.0.0 Initial Release; Please let me know if you find this useful. leave any comments or issues here or in the GitHub Repo Issues.

Description: Inspired by the MMM-OpenHABFloorplan module, this is a module for the MagicMirror² to connect to an ISY device from Universal Devices (http://www.universal-devices.com) using a WebSocket. It will display a floor plan showing live updates of which Insteon, Z-Wave, or ISYv5 Node Server devices are turned on/off (including dimming levels), which alarm zones are tripped, and the status of the thermostats. Setup takes a little while as you have to create your own floorplan in SVG (Scalable Vector Graphics) format using something like Inkscape or Adobe Illustrator. It can be as simple or as complex as you want it to be, the most important thing is the tagging. Whatever style you make your lights, lamps, outlets, or devices–as long as you tag them with the correct ISY address format–they will be picked up by the module automatically and their status updated on the graphic. The screenshots above are an “extreme” example SVG image which was created from an AutoCAD blueprint originally, with icons from various sources dropped in to represent the devices. The config options for the module give you even more advanced control, by letting you set custom display options for the different devices. New in version [1.0.7]+ – Control popups can now be enabled for various devices, to directly control your home automation from a touchscreen or any web browser with the MagicMirror page loaded. Screenshots: Live view: [image: floorplan_animated.gif] [image: floorplan_preview.png] Download: [card:shbatm/MMM-ISY] Version 1.0.7 - Initial Controls Implementation Added: Initial implementation of a control system using Bootstrap 4 to display tooltip style popups when devices are clicked. Version 1.0.0 Initial Release [EDITED 27-APR-18 WITH NEW VERSION]

@mr-gysy I‘ve got a similar issue with a similar remote Did you solve your problem? In my case the keys (KEY_PAGEUP & DOWN & BACKSPACE) don‘t work. I changed the evdev path. I added them to „handleKeys“. I added them to „keyMap“. I can see them in „evtest“ working- KeyCode 104 & 109 & 14 But in „viewnotifications“ they are not displayed The other keys are working with keybindings & carousel. But i need two more keys xD

Hello, I installed your fork and it works just fine. That was what I was looking for with a touchscreen: D But now I have a problem. If I take the comment to activate other pages and check to a widget, the reference to page 3 is not displayed and the points to touch are just two. Is there anything else to modify in the main.js file? Thank you, Alberto