@plainbroke The module got an update which shout fix the issue :)

@fischi87 Thanks :)

And don’t forget to add your module to the module list.

@fischi87 Looks nice!

I noticed you marked it as UNLICENSED.

I’m not a lawyer, but in my understaning, this means ‘All Rights Reserved’ by default, so others cannot legally clone, use, or modify your code, even though it’s public.

@rkorell Cool! Would be nice if you would switch on “Issues” in your repos.

Awesome! 👏

One nitpick: MMM-Remote-Control doesn’t need MMM-Remote-Control-Repository anymore.

@msimon360 Maybe add the URL to the repo here :)

@rkorell Good work! Would be nice if you could add a screenshot :)

@MyMirror We have calendar issues in v2.36.0. These have been fixed in the development branch. The new release, v2.37.0, will be released today. I would recommend waiting for it and then trying it out :)

@johnster000 Great! Now all your modules are displayed with screenshots and tags :)

@johnster000 Nice! You could check the “Hints For Devs” for your modules on the modules list. Some of these are just nitpicks; you can decide for yourself whether to fix them or not :)

@HeikoGr The repository (https://github.com/HeikoGr/MMM-LibraryMonitor) is not available :(

@sdetweil Yes, but not in this thread :)

My module is MMM-AtomVisualizer.

@plainbroke You have to ask @wswenson not me :)

@Qthulhu It would be great if you could create a PR so it can be included in the module README :)

@eddiebrok

This minimal config works for me:

let config = {
  address: "0.0.0.0",
  port: 8080,
  ipWhitelist: [],

  modules: [
    {
      module: "MMM-Remote-Control",
      position: "top_left",
    },
    {
      module: "MMM-JukeBox",
      position: "top_left",
    }
  ]
};

/*************** DO NOT EDIT THE LINE BELOW ***************/
if (typeof module !== "undefined") { module.exports = config; }

@tommyk Update MMM-JukeBox and it should work now :)

@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.

I tracked this down to a likely root cause: after the HTTPFetcher 304 change, some consumers were trying to process empty responses. In PR #4180, I fixed that for calendar and other consumers.

@rkorell That should already be fixed in the develop branch by https://github.com/MagicMirrorOrg/MagicMirror/pull/4161 and will be in the next release. It would be great if you could switch to the develop branch and test it before the release :) Good analysis, by the way!

@wimthoelke
Please update to the new version (v4.4.3). Your stationID works for me.
If this doesn’t work: use the profile dbweb.
If this doesn’t work, checkout this module: MMM-PublicTransportHub