Re: MMM-HomeAssistant-Sensors (Development) - Show your HA Sensors on your Mirror
Hello all
looking for some help with Home assistant sensor
I’m getting “Error Fetching Stats” on the Magic Mirror
My Config is below
{
module: 'MMM-homeassistant-sensors',
position: 'bottom_left',
config: {
host: "10.10.28.134",
port: "8123",
https: false,
token: "My Token"
values: [
{
sensor: "status.14928_acurite_00275rm_14928_t1",
},
{
sensor: "status.14928_acurite_00275rm_14928_b",
},
]
}
I have tried using a host name instead of the IP address same issue
If anyone has any thoughts please let me know
Thanks
Hello!
I am having a strange issue where all of the modules are loading onto the first page and not rotating through pages while using the MMM-Pages module. I’ve worked through the suggested uninstall/reinstalling the module process outlined in the issue brought up here, but it hasn’t resolved it.
Magic Mirror version: 2.33.0
The pages config is below. Thanks for the help!
module: "MMM-pages", // flip between pages - goal was to set full page calendar on one page, rest on other
config: {
timings: {
default: 10000, // rotate every 10 seconds
0: 20000 // page 0 rotates every 20 seconds
},
animationTime: 2000,
modules: [
[ // page 0
'weather',
'alert',
'clock'
],
[
'MMM-CalendarExt3'
], // page 1
],
fixed: [
['MMM-page-indicator'], // what to show on every page
],
hiddenPages:{ // modules to not show, or to hide in specific pages
"hidden": [
'calendar',
'updatenotification'
], //calendar module only needed to feed into MMM-CalendarExt3 and associated modules, but setting "disable = true" breaks this connection
}
}
I’ve migrated my MagigMirror installation on a RPI 4 from Bullseye to Trixie, running now MM V2.33.0 and node v24.11.1.
After solving some smaller issues with the NetworkManager configuration, everything is now running fine, except that I observe sometimes timeouts on requests to the internet. Fetching Goggle calendar entries or access to Spotify endpoints sometimes end up in timeouts, particularly visible at startup of MagicMirror. (and no, it’s not related to any wrong URL )
The same MM config is running under Bullseye, MM v2.26.0 and node v20.18.0 without any network issues. It also not a problem of wayland, as I get the same error messages running the config under x11. It seems that this behaviour is related to node V24. Is this a known issue? Is there someone who is fighting with similar issues? Has someone a sustainable solution for that problem?
[2025-12-01 11:52:18.102] [LOG] Launching application.
[2025-12-01 11:52:22.644] [INFO]
#### System Information ####
- SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.1; virtual: false; MM: 2.33.0
- OS: platform: linux; distro: Debian GNU/Linux; release: 13; arch: arm64; kernel: 6.12.47+rpt-rpi-v8
- VERSIONS: electron: 39.2.3; used node: 22.21.1; installed node: 24.11.1; npm: 11.6.2; pm2: 6.0.13
- ENV: XDG_SESSION_TYPE: tty; MM_CONFIG_FILE: undefined
WAYLAND_DISPLAY: wayland-0; DISPLAY: undefined; ELECTRON_ENABLE_GPU: undefined
- RAM: total: 905.64 MB; free: 397.65 MB; used: 507.99 MB
- OTHERS: uptime: 23 minutes; timeZone: Europe/Berlin
[2025-12-01 11:52:23.927] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%40group.calendar.google.com/private-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/basic.ics - Interval: 5400000
[2025-12-01 11:52:24.132] [LOG] Create new calendarfetcher for url: https://www.schulferien.org/media/ical/deutschland/ferien_nordrhein-westfalen_2025.ics?k=wMVRLvKrstqVXYv0MZJF9BwhEW4cGfQFjuutfjiALP5Hj700di6oEuYaFGd4tDTvYrLNzQgB7m-GlFC60I4jasaxLk6nJd_OY70AeBteoOU - Interval: 900000
[2025-12-01 11:52:24.136] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/de.german%23holiday%40group.v.calendar.google.com/public/basic.ics - Interval: 900000
[2025-12-01 11:52:24.788] [ERROR] Calendar Error. Could not fetch calendar: https://calendar.google.com/calendar/ical/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%40group.calendar.google.com/private-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/basic.ics TypeError: fetch failed
at node:internal/deps/undici/undici:14900:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at runNextTicks (node:internal/process/task_queues:69:3)
at process.processTimers (node:internal/timers:520:9) {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1134:18)
at internalConnectMultiple (node:net:1210:5)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'ETIMEDOUT',
[errors]: [ [Error], [Error] ]
}
}
Description
Hi guys. I`d like to introduce a seasonal addition to my Celtic FC man cave mirror. This is a fork of @Chris1976 original “MMM-Adventskalander” module with the additions of audio/video and animations which will take you on a journey of some of the key moments and people in Celtics history as you each of the 24 doors in the lead up to Christmas . Although this module has been specifically tailored towards Glasgow Celtic FC and its fans, the module is highly customizable and it can easily be modified to suit other teams or non football related events ( e.g. favorate family Christmas memories down the years ) by simply replacing the image/audio/video media files.
** Features**
24-door interactive calendar with open/close animations and hidden image
Optional per-door audio & video surprises behind every door
Snowfall animations (dynamically generated, optimized for all devices)
Sleigh and animated footer image procession
Santa’s Trophy Drop/Gift System**: Trophies/Gifts drop sequentially when door 24 completes its sequence.
-Christmas Eve Special**: Automatic Santa’s message + background image change at 23:59:59 on December 24
Date Override Testing**: Test any date/time without waiting, including Christmas Eve features
Optimized for low-power devices** with ~92% reduction in DOM event listeners
17-Language Support - including Christmas Eve Santa message translations
Screenshots
| ![1]https://github.com/gitgitaway/MMM-MyTeams-Adventskalender/blob/main/screenshots/screenshot2.png |
| ![2]https://github.com/gitgitaway/MMM-MyTeams-Adventskalender/blob/main/screenshots/screenshot2.png |
| [image: screenshot4.png] |
Download
[https://github.com/gitgitaway/MMM-MyTeams-Adventskalendar]
Tlachd a ghabhail agus Nollaig Chridheil dhuibh
Re: MMM-DWD-WarnWeather - Wetterwarnungen
Hello everyone,
After my MagicMirror crashed and I reinstalled it, I recently downloaded and added the DWD-WarnWeather module.
Now I’m having trouble finding the town/city.
I’ve tried everything, but it just won’t work the way I did years ago!
Where do I need to put what?
Thanks for your help!
so i have gotten the default calendar to add my google family calendar, and it shows in the top left fine with the next 7 day events listed. but i want our family calendar in the top center in monthly view. was told this module is the one. i installed the module and all i see is the word NOVEMBER with nothing else. what am i missing?
thanks
The module does not want to rotate through the weather layers. Below is my config:
disabled: false,
module: "MMM-WindyV2",
position: 'fullscreen_above', // this must be set to 'fullscreen_above'
config: {
apiKey: 'XXXXXXX', // insert your free or paid API key here
initLoadDelay: 50, // optional, default is 50 milliseconds
latitude: 41.432717, // example: 69.123
longitude: -71.979947, // example: 17.123
zoomLevel: 10, // set your preferred zoom level
showLayer: 'rain', // wind, rain, clouds, temp, pressure, currents, waves
rotateLayers: true, // set to true to rotate layers
layersToRotate: ['wind','rain'], // layers to rotate
delayRotate: 5000, // delay between rotated layers, in milliseconds
wMinZoom: 3, // set minimum zoom level for WindyV2
wMaxZoom: 17, // set maximum zoom level for WindyV2
windyMetric: 'kt', // 'kt', 'bft', 'm/s', 'km/h' and 'mph'
updateTimer: 60 * 60 * 1000 * 6, // update per 6 hours
retainZoom: true // retain zoomlevel between changing overlays
}
Any ideas? Thanks.
Is it possible to create a new area? I’d like to create a center_middle_lr section. This should allow me that I have in the middle again a division left right. Background: In the middle on the right side I want to display the soccer results and to the left the soccer clubs table
How can I create this?
Bonjour,
L’un d’entre vous utilise t’il ce module?
Le mien est bloqué sur “Chargement…” bien qu’étant inscrit sur le site https://dashboard.stormglass.io/
Y a t’il une manip à faire dans le fichier nano config.js :
sur The StormGlass API base URL.
apiBase : Default value: ‘https://api.stormglass.io/’ ???
Mon fichier de config :
{
module: "MMM-MarineWeather",
position: "top_right",
header: "Conditions Marines",
config: {
latitude: XX.XXXXXX, // Latitude
longitude: -X.XXXXXXXX, // Longitude
appid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" // StormGlass API key (docs.stormglass.io)
}
},
Merci pour votre retour.
I am currently using the MMM-Pages module with 3 pages, one with weather, calendar list, datetime, another with what looks like a normal wall calendar, month view and a bird of the day photo, the 3rd page is just my wifi info via MMM-Wifi. I’ve setup the modulebar and it can turn items of via touch.
what I would like to do is have a touch button that pulls up the wifi info on demand and then automatically to back to the page rotation after some amount of time.
I’m not against writing something, but if something close exists…
This is my first attempt at writing a module for MagicMirror, or and JS! Any comments or feedback would be welcome.
This module uses the RCWL-0516 Microwave Radar Motion Sensor to turn the connected display on and off when a person approaches. All the hard work is done via some Python code that the module executes.
Some modification of the RCWL-0516 is needed to adjust the detection range to make it useable.
All the details can be found here:
MMM-MotionSensor
To install:
cd ~/MagicMirror
npm install winston
cd modules
git clone https://github.com/Scottie-M/MMM-MotionSensor.git
Re : MMM-MarineWeather
Bonjour,
Je rencontre actuellement un problème sur ce module.
Je me suis bien enregistré avec la version 3.0 pour obtenir l’API Key, mais malgré cela, j’ai le message chargement ou Please set the correct Storm Glass appid in the config for module : MMM-MarineWeather.
Voici mon code :
{
module: "MMM-MarineWeather",
position: "top_right",
header: "Conditions Marines",
config: {
// --- OpenWeather 3.0 ---
provider: "openweathermap", // "openweathermap" ou "openweather" selon ta version
apiKey: "XXxXXXXXxxxXxXXXcXXXXXXXxXXXxxx",
// Coordonnées de ta zone
latitude: XX.390394,
longitude: -X.XX390394,
// Unitée & langue
units: "metric", // metric pour °C, m/s, mètres
lang: "fr",
// --- Rafraîchissement ---
updateInterval: 10 * 60 * 1000, // 10 minutes
retryDelay: 2 * 60 * 1000,
// --- Affichage principal ---
showHeader: false,
showWeather: true,
showTemperature: true,
showFeelsLike: true,
showHumidity: true,
showPressure: true,
showDewPoint: false,
// --- VENT ---
showWind: true,
windUnit: "km/h", // km/h, m/s, knots
windGust: true,
// --- MER / HOULE (si données disponibles par OpenWeather Marine API) ---
showWaves: true,
showSwell: true,
showSeaState: true,
// --- Prévisions ---
showForecast: true,
forecastLimit: 5, // nombre de jours affichés
forecastWind: true,
forecastSea: true,
// --- Storm Glass ---
showStormGlass: true,
stormglassStyle: "crystal", // default, simple, crystal
stormglassSize: 150, // taille en pixels
stormglassAlign: "center",
// --- Mise en forme visuelle ---
iconTheme: "marine", // marine, default, dark, light
showSunrise: true,
showSunset: true,
// --- Options avancées ---
animationSpeed: 1000,
timeFormat: 24,
decimalSymbol: ",",
}
},
Code généré via Chat GPT.
J’avoue que je tourne en rond.
MERCI pour votre retour.
Currently I migrate from Magicmirror v2.26.0 to v2.33.0. One issue , the weather module does not start. The module provide me from the provider openweathermap the message:
{"cod":401, "message": "Please note that using One Call 3.0 requires a separate subscription to the One Call by Call plan. Learn more here https://openweathermap.org/price. If you have a valid subscription to the One Call by Call plan, but still receive this error, then please see https://openweathermap.org/faq#error401 for more info."}
I don’t have a supscription for the ‘One Call by Call’ plan. But, if I copy the weather module (complete directory) from MM v2.26 to v2.33 I get the forecast weather data from openweathermap without any difficulty and everything is working fine. So there must be a modification in the weather module which leads to the described issue.
For the moment I’ve a workaround by overriting the wether module with the old version, but it would be nice and helpful if an expert could do a deeper analysis for the cause and understanding of the issue.
Thanks!
Here is my configuration for the module:
module: 'weather',
position: 'top_right',
header: 'Wetter Vorhersage für ',
config: {
weatherProvider: "openweathermap",
type: "forecast",
tableClass: 'small',
locationID: "2879315",
apiKey: "2xxxxxxxxx...xxxxxxxxxd", //apiKey from http://www.openweathermap.org
tempUnits: "metric",
roundTemp: true,
onlyTemp: true,
colored: true,
maxNumberOfDays: 4,
ignoreToday: true,
updateInterval: 3600000, // every hour
initialLoadDelay: 3000,
}
Per https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-Party-Modules, I am presenting the two modules that I added to the list.
One provides a message if there are system apt packages available for install. The other does a similar thing for MagicMirror module updates.
Freely admit that I used AI for some of the scripting.
Hi folks, I have a pretty vanilla config of MagicMirror running in a container stack on Portainer and have suddenly started to get the following error when starting the container:
[21.11.2025 10:52.25.515] [ERROR] Error: Cannot find module 'node:fs'
Require stack:
- /opt/magic_mirror/modules/MMM-MyScoreboard/node_helper.js
- /opt/magic_mirror/js/app.js
- /opt/magic_mirror/serveronly/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
at Function.Module._resolveFilename (/opt/magic_mirror/node_modules/module-alias/index.js:49:29)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/opt/magic_mirror/modules/MMM-MyScoreboard/node_helper.js:4:12)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/opt/magic_mirror/modules/MMM-MyScoreboard/node_helper.js',
'/opt/magic_mirror/js/app.js',
'/opt/magic_mirror/serveronly/index.js'
]
}
I’ve not made any intentional changes to the environment (I know, I know) and this suddenly began yesterday. I’ve not modified anything in the modules or config directories. I haven’t touched this env in 3 weeks and its been running fine.
Here is my docker compose:
version: '1'
services:
magicmirror:
container_name: magicmirror
image: bastilimbach/docker-magicmirror
#restart: unless-stopped
environment:
- PUID=1035 # magicmirror user on Synology
- PGID=100
- TZ=America/Toronto
volumes:
- /volume1/docker/magicmirror/config:/opt/magic_mirror/config
- /volume1/docker/magicmirror/modules:/opt/magic_mirror/modules
ports:
- 8888:8080
I have watchtower running, but there haven’t been any updates to this image since it was deployed a couple of months ago.
I’ve done a new installation on a RPI 4. Everthing is running fine, independant of a error message at start time where I don’t have any idea which module or core function produce the message.
Here is my configuration:
MM v2.33.0
node 22.21.0
trixie: Linux devpi 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
Maybe, there is someone who has already fixed that problem. How to proceed to identify this issue?
Nov 21 15:18:47 devpi mm[2438]: [2025-11-21 15:18:47.026] [LOG] Starting MagicMirror: v2.33.0
Nov 21 15:18:47 devpi mm[2438]: [2025-11-21 15:18:47.034] [LOG] Loading config ...
...
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.059] [LOG] MMM-NotificationBoard helper started ...
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.060] [LOG] Connecting socket for: MMM-RTSPphas
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.060] [LOG] MMM-RTSPphas helper started ...
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.060] [LOG] Connecting socket for: MMM-EnergyMonitor
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.131] [LOG] Connecting socket for: MMM-Spotify
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.133] [LOG] Connecting socket for: MMM-SpeechToCommand
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.134] [LOG] MMM-SpeechToCommand helper started ...
Nov 21 15:18:55 devpi mm[2438]: [2025-11-21 15:18:55.135] [LOG] Sockets connected & modules started ...
Nov 21 15:18:56 devpi mm[2438]: [2025-11-21 15:18:56.117] [ERROR] Error: write EFAULT
Nov 21 15:18:56 devpi mm[2438]: at afterWriteDispatched (node:internal/stream_base_commons:159:15)
Nov 21 15:18:56 devpi mm[2438]: at writeGeneric (node:internal/stream_base_commons:150:3)
Nov 21 15:18:56 devpi mm[2438]: at Socket._writeGeneric (node:net:966:11)
Nov 21 15:18:56 devpi mm[2438]: at Socket._write (node:net:978:8)
Nov 21 15:18:56 devpi mm[2438]: at writeOrBuffer (node:internal/streams/writable:572:12)
Nov 21 15:18:56 devpi mm[2438]: at _write (node:internal/streams/writable:501:10)
Nov 21 15:18:56 devpi mm[2438]: at Writable.write (node:internal/streams/writable:510:10)
Nov 21 15:18:56 devpi mm[2438]: at execSync (node:child_process:999:20)
Nov 21 15:18:56 devpi mm[2438]: at node:electron/js2c/node_init:2:17346
Nov 21 15:18:56 devpi mm[2438]: at /home/pi/MagicMirror/node_modules/systeminformation/lib/system.js:175:28
Nov 21 15:18:56 devpi mm[2438]: at ChildProcess.exithandler (node:child_process:410:7)
Nov 21 15:18:56 devpi mm[2438]: at ChildProcess.emit (node:events:519:28)
Nov 21 15:18:56 devpi mm[2438]: at maybeClose (node:internal/child_process:1101:16)
Nov 21 15:18:56 devpi mm[2438]: at Socket.<anonymous> (node:internal/child_process:456:11)
Nov 21 15:18:56 devpi mm[2438]: at Socket.emit (node:events:519:28)
Nov 21 15:18:56 devpi mm[2438]: at Pipe.<anonymous> (node:net:346:12)
Nov 21 15:18:56 devpi mm[2438]: [2025-11-21 15:18:56.118] [LOG] Node NOT Exiting...
Nov 21 15:18:56 devpi mm[2438]: [2025-11-21 15:18:56.283] [LOG] Launching application.
📷 Screenshot (Platzhalter)
![alt text]https://github.com/wiiare/MMM-Solarwatt/blob/main/screenshots/solarblock.jpg?raw=true)
⚡ Features
Anzeige von Live-Daten der Solarwatt PV-Anlage
Batteriestatus inkl. Ladezustand und Lade-/Entladeleistung
Tageswerte persistent in dailyData.json gespeichert
Reset der Tageswerte automatisch um Mitternacht
Intervallgesteuerte Updates, konfigurierbar
Responsive Darstellung passend zu MagicMirror²
📦 Installation
Wechsle ins modules Verzeichnis von MagicMirror:
cd ~/MagicMirror/modules
Repository klonen:
git clone https://github.com/wiiare/MMM-Solarwatt.git
Abhängigkeiten installieren:
cd MMM-Solarwatt
npm install
(Optional) Leere dailyData.json erstellen (wird automatisch angelegt):
touch dailyData.json
⚙️ Konfiguration
Füge das Modul in config/config.js ein:
{
module: “MMM-Solarwatt”,
position: “top_right”,
config: {
ip: “Deine_IP”,
password: “”,
batteryIp: “Deine_IP”,
updateInterval: 30000
}
}
📊 Anzeige
🔆 Solar Block
Erzeugung (W)
Verbrauch (W)
Einspeisung (W)
Netzbezug (W)
🔋 Batterie Block
Ladezustand (%)
Lade-/Entladeleistung (W)
Visualisierung als Balken
📅 Tageswerte Block
Kumulierte kWh für: - Produktion - Verbrauch - Einspeisung - Netzbezug
⚡ Hinweise
Tageswerte starten nach MagicMirror-Neustart bei 0 kWh
Werte werden automatisch kumuliert basierend auf dem Updateintervall
dailyData.json wird automatisch im Modulordner angelegt und persistent gespeichert
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.
-
-
-
-
-
-
