[2.33.0] - 2025-10-01

Thanks to: @Crazylegstoo, @dathbe, @m-idler, @plebcity, @khassel, @KristjanESPERANTO, @rejas and @sdetweil!

⚠️ This release needs nodejs version v22.18.0 or higher

Added

• Add configuration option for User-Agent, used by calendar & news module (#3255)
• [linter] Add prettier plugin for nunjuck templates (#3887)
• [core] Add clear log for occupied port at startup (#3890)

Changed

• [clock] Add CSS to prevent line breaking of sunset/sunrise time display (#3816)
• [core] Enhance system information logging format and include additional env and RAM details (#3839, #3843)
• [refactor] Add new file js/module_functions.js to move code used in several modules to one place (#3837)
• [refactor] Use global.root_path where possible and add tests for config:check (#3883, #3885, #3886, #3889)
• [tests] refactor: simplify jest config file (#3844)
• [tests] refactor: extract constants for weather electron tests (#3845)
• [tests] refactor: add setupDOMEnvironment helper function to eliminate repetitive JSDOM setup code (#3860)
• [tests] replace console with Log in calendar debug.js to avoid exception in eslint config (#3846)
• [tests] speed up e2e tests, cleanup and stabilize weather e2e tests, update snapshot url (#3847, #3848, #3861)
• [tests] refactor translation tests (#3866)
  • Remove sinon dependency in favor of Jest native mocking
  • Unify test helper functions across translation test suites
  • Rename setupDOMEnvironment to createTranslationTestEnvironment for consistency
  • Simplify DOM setup by removing unnecessary Promise/async patterns
  • Avoid potential port conflicts by using port 3001 for translator unit tests
  • Improve test reliability and maintainability
• [tests] add alert module tests for different welcome_message configurations (#3867)
• [lint-staged] use prettier --write --ignore-unknown in lint-staged to avoid errors on unsupported files (#3888)

Updated

• [calendar] Update defaultSymbol name and also the link to the icon search site (#3879)
• [core] Update dependencies including electron to v38 as well as github actions (#3831, #3849, #3857, #3858, #3872, #3876, #3882, #3891, #3896)
• [weather] Update feels_like temperature calculation formula (#3869)
• [weather] Update null value handling for weather type (#3892)
• [layout] Update styles for weather and calendar (#3894)

Fixed

• [calendar] Fixed broken unittest that only broke on the 1st of July and 1st of january (#3830)
• [clock] Fixed missing icons when no other modules with icons is loaded (#3834)
• [weather] Fixed handling of empty values in weathergov providers handling of precipitationAmount (#3859)
• [calendar] Fix regression handling of limit days (#3840)
• [calendar] Fixed regression of calendarfetcherutils.shouldEventBeExcluded (#3841)
• [core] Fixed socket.io timeout when server is slow to send notification, notification lost at client (#3380)
• [tests] refactor AnimateCSS tests after jsdom 27 upgrade (#3891)
• [weather] Use apparent_temperature data from openmeteo’s hourly weather for current feelsLikeTemp (#3868).
• [weather] Updated envcanada Provider to use new database/URL schema for accessing weather data (#3878).

@sletrabf With your config and the changes to the custom.css file, the module works on my system.

Please show us the system information provided in the terminal when you start MM. It looks like this:

[2025-05-18 11:54:32.378] [INFO]  System information:
### SYSTEM:   manufacturer: Notebook; model: N650DU; virtual: false
### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: x64; kernel: 5.10.0-20-amd64
### VERSIONS: electron: 35.1.2; used node: 24.0.1; installed node: 24.0.1; npm: 10.9.0; pm2: 5.4.3
### OTHER:    timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined 

@eprostko And it would be great if you could format your code snippets a bit more clearly in the future like proper indentation and quotation marks. The way you wrote the config part is really hard to read and analyze 🙂

Nice! I think the real-time clock is a useful new feature for the MM. With that we should be able to wake up the Raspberry Pi automatically without any external device.

@MMRIZE Okay 😀 I just added it to the list.

@sankum said in MMM-Wallpaper - wrong path:

[WARN] No /home/sankum/MagicMirror/modules/MMM-WallPaper/MMM-WallPaper.js found for module: MMM-WallPaper.

There is no module “MMM-WallPaper” (with a P instead of a p) on the module list. Please show what git remote -v outputs when you are in the module’s directory. Did you spell it right in your config file?

@eprostko The issue is that modeOptions is not a valid configuration field in MMM-CalenderExt2. Where did you get that?

weekStart needs to be set directly inside the view object:

views: [
  {
    position: "top_bar",
    mode: "week",
    type: "row",
    weekStart: 0,        // ← here, at the top level of the view
    slotMaxHeight: "150px",
    slotCount: 3,
    // ...
  }
]

The top-level weekStart: 0 in your config has no effect either - there’s no such top-level option, only the per-view (or defaultSet.view) one.

I’ve done it! 🥳 Checkout https://forum.magicmirror.builders/topic/19133/mmm-forum.

For accessing the read(-only) api you can use a cookie from your browser, e.g.

@karsten13 Thank you! That was the hint that led me to the solution 🙏

@OliWer Thanks for reporting. Please check https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/issues/401.

@sdetweil said:

Don’t know why node 24 causes so much trouble.

There is an issue with the newest versions of node v24 and v26. Here is our related issue: https://github.com/MagicMirrorOrg/MagicMirror/issues/4150

@karsten13 implemented a workaround in the develop branch, so our next release will be working with these new node versions. It’s a frustrating situation for new users, but it was caused externally.

@mumblebaj Just an idea: Maybe the node version used in Cron could be to old. When you run a script manually in your terminal, your full user environment (including things like .bashrc or .zshrc) is loaded. Cron runs in a much more minimal environment — it often doesn’t load your shell config files, so tools like nvm (Node Version Manager) might not be available.

How to fix it:

• Use the full path to Node: Find it with which node and use that path in your cron job.
• Set the environment manually in cron: You can define your PATH at the top of the cron file.
• Source nvm in your script: If you use nvm, add source ~/.nvm/nvm.sh and nvm use <version> before calling node.

@mvrlogins said in [MMM-Remote-Control] Cannot GET /remote.html:

0|MagicMir | [2025-09-21 16:44:59.284] [ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.

To make it clear here as well: “require() of ES Module ... not supported” shows that you are using a very old (unsupported) Node version. Like I said in the GitHub issue, you have to update Node.

I recommend using NVM to update Node (like recommended on the Node website).

Thanks for sharing your experience! As Node.js and Electron evolve, their hardware requirements increase over time, and older or less powerful devices may eventually struggle.

Staying on older versions is unfortunately not a sustainable solution because of missing security fixes, bug fixes and new features.

There, HAFAS displayed important delays for each departure.

The module supports this, but Transitous apparently does not receive real-time data for your station. The open-source community is doing impressive work trying to collect real-time data wherever possible, but this is unfortunately difficult in some regions.

HAFAS interfaces were never really intended for the kind of free use we make of them, and access is becoming more and more restricted. You could contact your local transport association and ask why they do not provide real-time data through an open API, preferably GTFS-RT. This would allow projects like Transitous, and therefore MMM-PublicTransportHub, to use it.

The train and clock icons in the timetable looked very nice.

That was already on my to-do list. I have now added a similar header to MMM-PublicTransportHub, so you only need to update the module.

Station IDs were easier to find with the HAFAS module.

Those IDs come from the provider, so there is not much I can change about their format. I actually prefer the Transitous IDs because they are real DHIDs and work globally.

The display problem with umlauts is still a bit mysterious. The query scripts of both modules are not fundamentally very different, so I currently do not have a reliable explanation for why it only happens on your machine with the new query tool.

@wyovino I’m working on a new release for MMM-Jast. I think today or tomorrow it will be out 🙂

@chrisfr1976 Nice! Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules 🎄

@rkorell I fixed it. The false positive git clone hint doesn’t appear anymore :)

@wyovino Okay, I’m glad we were able to improve the situation 🙂 Can this thread marked as solved?

@bwente Nice :D Don’t forget to add it to the module list: https://github.com/MagicMirrorOrg/MagicMirror/wiki/3rd-party-modules

@potts-mike I recommend opening an issue in the repository; not all module developers hang out here on the forum 🙂