forum.magicmirror.builders

@1a2a3a not my intent to DO … was trying to get him to help…

@Beginner_123 what was the ‘fix’ ? open a new window?

Would MMM-EmbedURL do what you need?

@trnitz Pretty cool little module, Do you have a way to enlarge it x2.

@msimon360 imagesphotos should refresh its list of images every 60 seconds by default I use it linked to a file share on my nas Because there are so many pics no idea when the new pic will appear, add random on to that and it’s worse for predictably

Withdrawn. The MagicMirror maintainer kindly pointed out that this is already covered by the built-in per-module animationSpeed: 0 config option — it gives an instant, blink-free content swap for any module that passes it through. Where a module hardcodes its fade duration, the correct fix is in that module (expose animationSpeed), not a separate global module. I’ve corrected that in my own modules and withdrawn MMM-NoFade. TL;DR: to stop a module from fading on updates, just set animationSpeed: 0 in that module’s config.

All, not sure if this was just me but after upgrading my Pi 5B to OS 13.6 my fan stopped working. The fix was to add the following line in /boot/firmware/config.txt. I put it near the top. dtoverlay=cooling_fan

@bwente You gave me a great idea. I decided o create a a tiny “launcher” page for switching between multiple displays on one kiosk device. A TV in my study. I wanted the same Android TV to also show a security camera dashboard (Frigate NVR on my home network), not just MagicMirror. The kiosk browser only points at one URL at a time. Rather than build a full app switcher, I just added a tiny extra route to the small reverse-proxy Node server I already had running for the MM display one page, two big buttons: ![image: 1787665021862-71b33a61-9e17-4e0c-abfa-eefe00741f27-image.jpeg] The two buttons just link out to http://192.168.0.16:8088 (MM-Docker) and http://192.168.x.x:5000 (Frigate NVR) Point the kiosk browser’s start URL at 192.168.x.x:8080/launcher(MM- with Physical Monitor) instead of either destination directly, no JavaScript needed for the actual navigation, and they’re natively D-pad-focusable on a TV, so the remote just moves focus between them and select jumps straight there (the green focus ring makes the current selection obvious from across the room). One thing worth flagging for anyone doing the same on an Android TV specifically: not every “kiosk browser” app renders a page like this correctly. I initially used one built more for single-photo slideshow display, and it auto-detected and fullscreened the first video element it found instead of showing the actual page layout, fine for MagicMirror (mostly text/widgets) but broke a multi-camera grid dashboard that us

I submitted a pull request to the original repo you can try my fork in the meantime stop mm cd ~/MagicMirror/modules -rename the existing module folder to some other name git clone https://github.com/sdetweil/MMM-TomTomCalculateRouteTraffic git checkout withsuspend then restart mm then if you use ModuleScheduler or pages, carousel, or other modules that support hiding and showing you could validate that no api calls are made during the hidden time

Thank you for putting me on the right track! The issue was all due to me messing up git. All fixed now.

Got it working. MMM-iCloudPhotos Still testing with MMM-ImagesPhotos to see what update interval works for me.

I’ve been working on MMM-MessageCenter, a module that gives notifications from different sources one consistent place on the mirror. The idea came from a pretty simple problem: a notification appears, disappears, and nobody knows whether anyone actually saw it. Different modules and services also handle alerts differently, so important information can easily get lost. MessageCenter adds a small notification history with clear unread, viewed, acknowledged, dismissed, and expired states. What can send messages? Everything: Other MagicMirror modules MagicMirror’s bundled Weather module MMM-Remote-Control Home Assistant REST webhooks MQTT Local Unix-socket scripts and system monitors It intentionally doesn’t collect every internal MagicMirror event. Modules either use the MessageCenter API or an explicitly enabled adapter, which keeps refresh, navigation, and module-control traffic out of the inbox. A few examples A dishwasher notification can briefly appear as an alert and then remain in history until someone views it. A doorbell message can include a camera snapshot captured when the event happened, so the image doesn’t change before somebody checks it. The standard MagicMirror Weather module can add a “Rain approaching” message without requiring a separate weather service. A local monitoring script can report low disk space, high temperature, network trouble, or another condition that should be visible on the mirror. [image: 1787288172343-489bf62b-9edb-44bc-b4d7-6252e6a60b70-i