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-image-resized.jpeg] Different ways to display it MessageCenter can be used as: A compact list in a normal MagicMirror region A full-page message inbox A touch-friendly display with message controls A non-touch display that simply shows the newest messages It can show temporary alerts, retain message history, expire old messages, update existing messages by ID, and publish attention events for other integrations. It only says that something needs attention, leaving other modules and integrations free to decide what that means. Configuration, payload examples, and documentation: https://github.com/bwente/MMM-MessageCenter

BTW MMM-WeatherHero is a great module for this. It looks right at home. [image: 1786644793627-8fc94368-ebaa-4459-92e5-0601d10a8eff-image.jpeg]

MMM-MusicAssistant-Controller A compact, touch-friendly Music Assistant controller. It communicates directly with Music Assistant and does not require Home Assistant or embed the Music Assistant web application. [image: 1785625942507-mac-fullscreen.png] Features Album artwork, title, artist, progress, and duration Previous, play/pause, next, and volume controls Music Assistant player discovery and selection Configurable playlist launcher tiles Fullscreen touchscreen layout Compact layout for standard MagicMirror regions Persistent player selection MagicMirror notifications for automation and external controls When playerId is omitted, the module presents the available Music Assistant players for selection. A fixed player ID can be configured when the module should always control one player. Requirements MagicMirror² Music Assistant 2.9 or newer A Music Assistant long-lived access token Links Repository and documentation: https://github.com/bwente/MMM-MusicAssistant-Controller Latest stable release: https://github.com/bwente/MMM-MusicAssistant-Controller/releases/tag/v1.3.0

@Niggich you could subtract a fixed delay amount Basic Subtraction Code You can place this snippet inside a template condition, action, or template sensor. For more advanced examples, visit the official Home Assistant Templating Guide.jinja2{{ (states('sensor.first_number') | float(0)) - (states('sensor.second_number') | float(0)) }} Use code with caution. Important Rules for TemplatesStates are text: Home Assistant treats all sensor states as strings (words) by default. Adding | float forces it to act like a number. Prevent errors with defaults: Use float(0) instead of just float. If your sensor goes offline or shows unavailable, the 0 acts as a safety net so your automation does not crash. Use parentheses: Wrap each sensor and its filter in parentheses ( ) to ensure the math calculates in the correct order.

@BKeyport try the upgrade script again, with force instead of apply it will remove and and add the right version of node the right way, including on buster please advise your results

@emrah_asl said in Updating Compliments using a spreadsheet: fs.writeFile("modules/default/compliments/remotefile.json", compliments, function(err) { my code in node_helper.js (under compliments folder) are creating file on root normally when you start mm with npm start don’t make this node_helper.js as MM has a special use for that… make it createCompliments.js then the best thing is use the full path for the file fs.writeFile("/home/pi/MagicMirror/modules/default/compliments/remotefile.json", compliments, function(err) { how do you start MM? pm2 start 0 (and it starts on boot too…) If you used the automated install script u would have been prompted to set this up. (if u want to add it now, you can run the fixuppm2.sh script from here https://github.com/sdetweil/MagicMirror_scripts just one line to copy/paste ) now, if you use pm2, it launches MM by using the installers/mm.sh script. you can add your node modules/default/compliments/createCompliments.js to the mm.sh and all will continue as normal. The second problem , my magic mirror fires electron.js error when I try to create file. i don’t understand this. npm start fires electron.js npm reads the package,json file and looks for the command requested "scripts": { "start": "DISPLAY=\"${DISPLAY:=:0}\" ./node_modules/.bin/electron js/electron.js", the ‘start’ command executes that line.