@thartley – Follow Sam’s instructions.
I am traveling so didn’t get to finish mine. I got to a point where I got a message that the action was in progress, but it would never finish. After some research I’m pretty sure I have a permission problem and will check it out when I get home in a couple of weeks.
@sdetweil --Hi Sam
That was a while ago and my memory is foggy, but the issue was mapping a share on my NAS to the Raspberry Pi on which the MM is running…
As best I recall, I tried following directions to map the drive, but it didn’t work. I seem to recall being left with the sense that the process [a] had changed over time due to changes in distributions, and/or [b] that there was something left out of the directions that were likely too obvious to mention for someone who already knew, but was non-obvious to someone out of the know. At that point I gave up.
Fast forward to today - I’m happy to invest the time to learn and get it done if you’re willing to help!! I appreciate it. I sent you an email regarding how to best proceed.
@sdetweil – Well, I’m not surprised. I have the pictures on a USB drive attached to the raspberry pi, and the more pictures on the drive the worse it gets. It does feel like the software is loading up memory with the pictures.
I tried some time ago pulling the pictures from a share on my NAS, (you had advised someone to do that on another thread) but I never got that to work.
Thanks for letting us know about the memory issue.
@wyovino – Ok, good to know.
One of my magic mirrors stops every few days. There is only one module running on that mirror, MMM-BackgroundSlideshow, so it’s obvious when it happens.
Bill, I’m glad you found what you were looking for.
I’m curious - what issue are you addressing by restarting the MagicMirror daily?
I read this thread with interest because I too have thought about resorting to daily restarts on one of my mirrors. [I’ve figured out that daily restarts won’t meet my needs / fix my problem - so I haven’t gone down that road (yet). I guess I could design a cron schedule that staggers the restart enough that the photo display doesn’t show the same pictures every day, but not yet…]
@plainbroke – Thanks. I have used FEH in the past. I used it as a dedicated picture display on a Raspberry Pi, but had issues with it being stable. I am now using Magic Mirror running a single module now for the same purpose. It stopps displaying pictures every few days, so I suspect I have too many pictures loaded on the USB mounted there. I may give FEH a try again…
Thanks again
@plainbroke – Just out of curiosity, what picture display program do you use?
@MikeTheYeti – Yes, I recall having the same or similar issues way back when…
I liked the idea of special effects for holidays, birthdays, scheduled vacation trips, etc - but couldn’t get it to work properly.
I eventually just gave up.
@Exndfan – Interesting!
Query: The original question was in regards to seeing data collected by a PiAware receiver. It looks like Plane Finder and PiAware both run dump1090, but beyond that I don’t know how they work, or how the data gets passed.
Will this module also display data received by a PiAware?
@sdetweil
AHA - I see. It looks like that module is/was quite involved! I’m not sure I can add much to answer the original question, but i did note that the OP described the data as being/like JSON, but the module difers:
Bugs and Warnings
ℹ️ The data provided by the flightradar24-client, is not JSON, even if it resembles it.
It is actually an Array of JavaScript objects.
For an example of the raw data, look at the demo.json file.
Maybe the best way to move this forward is to tell us what module you are referring to when you say something used to work but went dark some time ago.
If we can see or reference what you are talking about, you have a better chance of getting help.
@UncleRoger – +1 on having a separate Magic Mirror instance for development (“dev instance”)! I have a small virtual machine running Magic Mirror where I can try out changes or new modules without disturbing my main instance. I don’t bother with a monitor, just display it on my desktop.
@BKeyport – Sorry to hear that, but thanks for the module while you maintained it.
And a big thanks for directing us to another module, and not just leaving it hanging out there!
@PierreGode – OK, thanks. I was just wondering what it is estimating, and what it is supposed to do with the estimates.
@sdetweil – That’s what I thought. Just did that and it’s working now…
Thanks, as always!
@BKeyport, @ulrichwisser and all: Please let me know if the following questions would be better served under a new topic, but since my issues originated with this older module, and the new module shares the same name I thought it appropriate to post under this topic…
Issue: the old module is no longer supported by the developer, who suggests using a newer module which uses the same module name. After cloning the new module, the instructions call for doing an ‘npm ci’ command, which fails due to a lack of an existing package-lock,json file.
Question: Is there something different I should be doing, o si this something the developer needs to fix?
Old module: https://github.com/BKeyport/MMM-Worldclock
New module: https://github.com/ulrichwisser/MMM-Worldclock
Error Message:
pi@mirror1:~/MagicMirror/modules $ cd MMM-Worldclock
pi@mirror1:~/MagicMirror/modules/MMM-Worldclock $ npm ci
npm ERR! code EUSAGE
npm ERR!
npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm ERR! later to generate a package-lock.json file, then try again.
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm ERR! [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm ERR! [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info
npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-05T17_16_59_150Z-debug-0.log
pi@mirror1:~/MagicMirror/modules/MMM-Worldclock $
@PierreGode – What does the ‘Chores per Week Estimate’ do?
What is it estimating, and what does it do with the estimate?
@mischag – Are you using the port described in the documentation [5003]?
See:
Admin Interface
Go to http://yourmirrorIP:5003/ #page will be reachable within same network.
Caution
DO NOT expose application with portforward
@PierreGode – OK, good to know. Thanks for the quick response.