I have been setting general module position using a preset module location such as position: “top_left” in my config.js file and then resizing/minor adjustments in custom.css file via module specific transform (size) and position: relative with px adjustments of one or more sides. This process has worked just fine with the default clock and MMM-MktIndex perfectly.
However, now with MMM-OpenWeatherMapForcast module, it does not matter what changes I make in custom.css, that module will not move it’s position. I have tried both relative position changes and absolute position changes but it stays in the same location. Interestingly, in the same custom.css bracket for that particular module, the transform (0.75) has worked to make the module smaller, but the position changes do not take effect. Sometimes on launch, I will see the entire briefly in a different position, but it appears to snap back to the same location. I thought that settings in custom.css were highest in the hierarchy, so not sure why I cannot change the position.
Thanks in advance for any help.
In the recent past, when I sent the show article notification to my mirror, it would display the entire text of the article corresponding to the current headline in the newsfeed module. Now, when I do that, it displays a captcha and won’t let me see the full text of the article. Is there a workaround for this? Thanks!
Hi, this is just a little rant.
For someone like me who bought three different Raspberry Pi models (Pi 3 to Pi 5) complete with SSD and NVMe memory and different cameras, because each time it seemed that the hardware was the problem. After buying the hardware and following various tutorials, it seems that the problem is the software. Time passes and you have to switch to new hardware because the software has been updated. Here I am talking about OpenCV and the rpicam and picamera2 libraries. Then, even in the various mirror modules, I begin to see the complexity of installation, where the various developers tell you to go and look here without telling you how they did it, except to say “steak, frying pan, eat” instead of saying “buy steak, take a frying pan and put it on the stove, cook the steak, and when it’s done, you can put it on a plate and eat it.” Explaining the steps in detail makes it easier to understand and improve, but it seems to me that it is becoming increasingly difficult and does not help (search on Google, because even using various LLM leads you to make other mistakes or modify parts that should not be touched). I am talking about the most difficult modules; it would take more patience to write all the installation steps, especially if there are dependencies. I found it difficult even just to install node.js, and the steps should be clearly written in the MagicMirror wiki. So I ask for more patience from developers and, in technical matters such as node.js, opencv (referring to facial recognition), very complex modules, to use a language that is much easier to understand and more steps to guide users through the installation process step by step. Sorry for the rant, but after nine years of trying to install certain modules and spending a lot of money, I had to write this.
thank you
I want to make a 42 inch Magic Mirror using a Raspberry Pi.
I’m in the US and I was wondering if anyone else has any hardware recommendations for a mirror this large? I’d like to use all of the same hardware (monitor/TV, glass/mirror, etc) that someone has already built without issue.
Any help is greatly appreciated!
A MagicMirror² module that displays today’s school lunch menu from Matilda Platform for schools in Sweden.
✨ Features
Shows today’s main lunch and optional vegetarian option.
Configurable school (via ID from Matilda Platform).
Configurable module title.
Optional icon in the title.
Configurable update interval.
Customizable fallback text when no menu is available.
Fully styleable via custom.css.
It seems in the past few weeks Microsoft has started returning 400 and 500 errors on ics requests to tools with unrecognized User-Agent strings.
The response detail that comes back is that you are using an unsupported browser, probably due to the fact their ICS files are hosted under the /owa/ subsite of the full tool.
I manually changed my code to use the standard Chrome User-Agent which fixed the module, so adding a feature request to be able to provide a user-agent in the module config.
Hi everyone! I’ve been tinkering around with MM for a few years and just recently renewed my interest in it. I’m also into 3D printing, using a BambuLab printer, which is located in another room, while my MM is in the main living room. I thought it would be nice for MM to show me a notification when a print is finished or has an issue. So, I used ChatGTP to write my first module. Maybe someone else will find it useful
https://gitlab.com/LuckyDuckTx/MMM-BambuLabNotify
Hello,
I would like to install the multi-user facial recognition module on a Raspberry Pi 5, but so far I haven’t been able to do so.
Can anyone help me?
I work with people with disabilities who need guidance throughout the day, and I would like to display their daily activities when they stand in front of the Magic Mirror.
It seems to me that the MMM-Face-Multi-User-Recognition-SMAI module would be perfectly suited for this, right?
I have an RPI5, and I’ve tried many times, but I can’t get it to work. The best I’ve managed is to recognize a single person when I run the script in ssh. And the MM doesn’t do anything.
From what I’ve read, I get the impression that it’s a difficult installation and that there isn’t much activity around this topic.
Do you have any advice?
Thanks in advance,
Laurent
Hello,
I hope someone can provide some information on what I should check for what might be causing the errors shown below. The lines are from the Developer’s Window Console tab for the mmm-systemtemperature module. Magic Mirror 2 runs the same with or without this module active. The module itself seems to run because it puts the temperature on the Magic Mirror screen. But because of the errors I’m not sure the temperature is accurate though. The last error in the list “…Uncaught (in promise) TypeError:…” repeats every 5 seconds, which matches up to the “update Interval” configuration option fetch temperature value.
In case it matters, this module is listed before some of the other modules in my config file, but it is the last module to show up on the MM2 display when I start MM2.
Load script: modules/mmm-systemtemperature/mmm-systemtemperature.js
module.js:483 Module registered: mmm-systemtemperature
loader.js:137 Bootstrapping module: mmm-systemtemperature
loader.js:164 Load script: modules/mmm-systemtemperature/node_modules/lodash/lodash.js
:8080/modules/mmm-systemtemperature/node_modules/lodash/lodash.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
localhost/:1 Refused to execute script from ‘http://localhost:8080/modules/mmm-systemtemperature/node_modules/lodash/lodash.js’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.
loader.js:172 Error on loading script: modules/mmm-systemtemperature/node_modules/lodash/lodash.js
loader.js:27 Error when starting node_helper for module mmm-systemtemperature:
startModules @ loader.js:27
loader.js:28 ReferenceError: _ is not defined
at Class.getCommandExecutor (mmm-systemtemperature.js:76:3)
at Class.start (mmm-systemtemperature.js:23:31)
at startModules (loader.js:25:32)
at loadNextModule (loader.js:220:12)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
5mmm-systemtemperature.js:31 Uncaught (in promise) TypeError: this.commandExecutor is not a function
at Class.socketNotificationReceived (mmm-systemtemperature.js:31:9)
at module.js:234:9
at Socket. (socketclient.js:38:4)
at Emitter.emit (index.mjs:136:20)
at Socket.emitEvent (socket.js:498:20)
at Socket.onevent (socket.js:485:18)
at MMSocket.socket.onevent (socketclient.js:32:11)
at Socket.onpacket (socket.js:455:22)
at Emitter.emit (index.mjs:136:20)
at manager.js:204:18
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
Categories
-
Announcements
Announcements regarding the MagicMirror software and forum.
-
Core System
Discuss the MagicMirror² core framework.
-
-
-
-
-
-
