@costascontis As far as I know there is no module available which picks a specific item from a given webpage…
So your way could be to use Sam’s (@sdetweil) tip above or create a module at your own which extracts the widget from your webpage.
The latter should be doable if you use some of the given modules as starting point and asking ChatGPT to help you …
Regards,
Ralf
@costascontis , If I got you right, this seems to be a web page. So i can imagine, this could be a candidate for MMM-SmartWebDisplay.
Check it out.
Good luck!
Ralf
@_V_ My module MMM-PresenceScreenControl Offers a comfortable way to switch on or off during defined times - as much as you like per day as much days as you like.
Regards,
Ralf
@viktorzonix again 404 … Yesterday it was visible - for a short time.
Unfortunately I’ve missed to clone :-(
@LuckyDucker - something is really strange with your github …
Regards,
Ralf
Dear @Peter,
Yes fully understood…
Without context - and may an answer regarding my questions - It‘s really hard to help.
Warmest regards,
Ralf
Dear @Peter,
I can imagine that this is a restriction of your hardware.
I’m not THAT system specialist but as far as I remember there are some limitations regarding environment and software versions on Pi2b …
Because the “actuality” of used libgpiod this may doesn’t work on this specific hardware.
I can imagine Sam (@sdetweil ) can deliver a more precise statement on this.
On pi4/5 with “current” MM versions this works - and yesterday I got feedback regarding a successful installation.
Is there any log-entry which can be useful here?
Is the right GPIO configured for PIR?
Is the PIR sensor functional / calibrated?
Is power/ground connected to PIR?
Is power supply sufficient and working?
Regards,
Ralf
Don‘t forget to go to the target module directory before installing!
cd MMM-Tronity
Ralf
@bradley1982 this is easy :-)
Your terminal states the error.
You have to issue:
npm install
The „run“ produces the error .
Good luck!
Warm regards,
Ralf
@schlomm
This is really cool.
Awesome that it works as designed…
(Was a little bit afraid that especially postinstall will fail and module doesn‘t work as expected…)
So thanks for (first !) confirmation for working module!
Warmest regards,
Ralf
Dear MagicMirror-ians
As may already known I was a real fan of MMM-Pir.
For also good known reasons this nice module is not longer maintained.
I have a local clone which runs OK but in the meantime I had switched to MMM-MQTTScreenOnOff wich attaches a “better” (radar-) sensor to my mirror. But I’ve missed the progress bar, the dimming and cron-like functionality. In addition the radar sensor is much slower than PIR- caused by a 5 second update intervall as minimum.
After plenty of tinkering and testing, and above all torturing AI heavily I’m excited to announce: MMM-PresenceScreenControl is finally out! 🎉
This module brings together the best of both worlds:
• The beloved timer bar and auto-dimming from MMM-Pir,
• The reliability, MQTT support, and simplicity of MMM-MQTTScreenOnOff,
• All cleaned up, without unnecessary complexity, cryptic cron strings, or weird build tricks.
A few highlights:
• Presence detection with PIR, MQTT, or both (whichever triggers first wins)
• A visual timer bar so you always know how long the screen will stay on
• Straightforward “ignore” and newly introduced “always-on” time windows using plain times and days—no cryptic cron needed
• Customizable screen on/off commands—works on Pi, PC, X11, Wayland, CEC, and more
• Touch mode for remote or manual override (yes, you can poke your mirror awake remotely!)
If you’re after spinning circles or relay magic, this isn’t your thing (yet 😉).
But if you want a solid, readable, and maintainable presence module that just works—even (hopefully) after updates—this is for you.
Give it a try, share your feedback, open pull requests, or ask questions right here or on GitHub:
Happy mirroring!
Ralf
@sdetweil Dear Sam,
I was able to get this done - to my big surprise …
As announced, I just have pushed it to git and will post a corresponding message tomorrow.
Do I get it right that it is recommended to edit the modules page as well?
And the 3rd Party Modules page then will populate by itself, right?
Thanks!
Warmest regards,
Ralf
@schlomm I’m absolute beginner …
Had HEAVILY used AI to get this done and have recycled a LOT.
GPIO part is from old (discontinued) module MMM-Pir from Bugsounet.
This is reflected in pirLib.js - sliightly modified for my purposes.
I do have a repository - pushed literally minutes ago …
Feel free to have a look.
Buttons should work with some modification. Essentiall for my purposes I simply query state of a single GPIO pin - to which a PIR sensor is connected. Code must be enhanced to handle more than one pin - if you are talking about “butons” - which signals plural…
As mentioned such modification should be doable with AI as well.
[ EDIT : My system is a raspi5 / bookworm as well - this is main reason for some difficulties. Some procedures simply doesn’t work anymore with new libraries and I had to change implementation…]
Good luck!
Warm regards,
Ralf
@sdetweil Dear Sam,
just FYI: I’ve just identified that my main problem is NOT the version mismatch but a major change in node-libgpiod’s handling of GPIO-ressources.
This was the main reason for mal-function of PIR sensor detection. “Version” was a side effect, not root-cause.
I’m nearly done with this and it seems that it will work as intended…
Thanks again for your support!
Regards,
Ralf
@sdetweil OK; thanks.
I will stop to handle these mismatches.
Will try to get the MM-Module runnable .
Console/terminal runs with node may not be necessary …
Thanks anyway for your kind support!
Ralf
@sdetweil Dear Sam,
thanks again for this long explanation!
My versions (if I interpret correctly) doesn’t mismatch :-(
0|MagicMir | ### SYSTEM: manufacturer: ; model: ; virtual: false
0|MagicMir | ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.20+rpt-rpi-2712
0|MagicMir | ### VERSIONS: electron: 32.2.7; used node: 20.18.1; installed node: 20.18.1; npm: 10.8.2; pm2: 5.4.3
0|MagicMir | ### OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined
So I’m not sure at all, what to do.
pi@MagicMirrorPi5:~ $ n list
node/20.18.1
Does show up exact this version, as well.
Where are my problems from ???
Thanks a LOT for any idea!
Ralf
@sdetweil
Dear Sam, OK, thanks for this.
Not fully understood…
How can I
Thanks for further advise!
Warmest regards,
Ralf
@sdetweil said
you should know if you run
node serveronly, then the bytecode has to match the nodejs standalone engine version
OK, thanks.
It seems that rebuild have corrected the error for the module.
When I try to run a node-command in the shell (terminal) then I get an similar error message as above.
Is this caused by your explanation part above?
Different versions needed for either terminal or inside mirror?
Can you tell me HOW the magic mirror is started (when I have used your install script)?
Is there a way to test something which had to run in the mirror (like the module) on commandline?
To illustrate what I mean:
I have a very short test-script test-gpiod.js
// test-gpiod.js , Aug 2025, Dr. Ralf Korell
const { Chip } = require("node-libgpiod");
try {
const chip = new Chip(0);
console.log("Chip label:", chip.getChipLabel());
} catch (err) {
console.error("Error loading chip:", err);
}
which I try to run with
node test-gpiod.js
But this produces error message:
/home/pi/MagicMirror/modules/MMM-PresenceScreenControl/node_modules/bindings/bindings.js:121
throw e;
^
Error: The module '/home/pi/MagicMirror/modules/MMM-PresenceScreenControl/node_modules/node-libgpiod/build/Release/node-libgpiod.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 128. This version of Node.js requires
NODE_MODULE_VERSION 115. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Module._extensions..node (node:internal/modules/cjs/loader:1586:18)
at Module.load (node:internal/modules/cjs/loader:1288:32)
at Module._load (node:internal/modules/cjs/loader:1104:12)
at Module.require (node:internal/modules/cjs/loader:1311:19)
at require (node:internal/modules/helpers:179:18)
at bindings (/home/pi/MagicMirror/modules/MMM-PresenceScreenControl/node_modules/bindings/bindings.js:112:48)
at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-PresenceScreenControl/node_modules/node-libgpiod/lib/misc.js:1:37)
at Module._compile (node:internal/modules/cjs/loader:1469:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
at Module.load (node:internal/modules/cjs/loader:1288:32) {
code: 'ERR_DLOPEN_FAILED'
}
Node.js v20.18.1
Thanks for any help!
Warmest regards,
Ralf
@sdetweil Dear Sam,
thanks for this information.
Can you please enlighten me?
I can read what you wrote and I got a light idea - but didn’t understand …
I definitely have used your install script.
what is @electron and
what correlation is between node-libgpiod and @electron ? and what will this
../../node_modules/.bin/electron-rebuild
do?
Sorry for these questions - I would like to understand, what happens.
If this is “neccessary” I will try to automate this for others with a postinstall script.
Thanks for your effort!
warmest regards,
Ralf