@nowayto said:

what should I write inside the [] parenthesis to cycle through all the elements?

I just released version 0.1.5. With this update, all elements are used when the array is empty 🙂

@sdetweil said:

I think the first in the getTranslations list is the default.

Ah, yes the first is used as the fallback language. It was German, which is not the best choice :-)

I changed it to English and released a new version.

@nowayto Please update and check 🙂

@evroom Nice. Thanks for the feedback! 🙂

The only thing that I would like to additionally see, is the last 2 departures/arrivals in the past

Like the Hafas module it’s currently not possible to display past departures, sorry.

Hi 😃

I stumbled across Transitous, a thriving open community-driven project that aggregates public transport data from many regions through a shared API.

I have now built a new module based on it: MMM-PublicTransportHub.

The main advantage compared to previous public transport modules is the much broader geographic coverage. So for users who haven’t had a public transport module for their region until now, this module might change that - check out the sources list if your region is on it.

Setup details and more information are in the repo: https://github.com/KristjanESPERANTO/MMM-PublicTransportHub

I would be happy to hear your feedback.

@wswenson Nice! :-)

MMM-PeriodicTable is not on the module list. Where did you get it?

@Rags Nice! 👏 I also thought about something like this.

Just out of curiosity: Why are you using an very old version of axios instead of build-in fetch?

@Divis Looks like an action-name mismatch.

MMM-Buttons should send REMOTE_ACTION values such as MONITORON and MONITOROFF.
monitorOnCommand and monitorOffCommand are config keys in MMM-Remote-Control, not REMOTE_ACTION values.

So in MMM-Buttons, try:

• action: MONITORON
• action: MONITOROFF

@eprostko I’m glad it’s working. The configuration of MMM-CalendarExt2 and the documentation are quite complex, so I completely understand if you’re having a hard time with it.

Have fun with your project 😃

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

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

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

@Divis The color option should work, but it needs rgba() — hex values and named colors don’t support transparency:

color: 'rgba(255,255,255,0.3)',

@fred2nice That’s cool! I’ve been thinking about getting a laser cutter for a while. That would be one more reason to do so - even though I don’t even need a new frame now 😅

@Divis Thanks! 😃 There was some feedback with ideas in the repo. So not alone my achievement.

@British_Kiwi said:

https://github.com/sdetweil/MMM-pages

That is Sam’s fork. Please try the original module: https://github.com/edward-shen/MMM-pages.

@British_Kiwi Which version of MMM-pages have you installed? I wonder why MMM-pages isn’t in your list of updated modules. Current version is 1.4.0.

@JeanMichelC The markers are just visual pin icons on the map — they don’t define any area. A typical use case would be marking your home and workplace so you can easily spot them while watching the rain radar.

@rkorell Thank you very much for this feedback and appreciation 🙂 It’s interesting that you took a deeper look at the changes.

Hi @rkorell, thank you for the detailed bug report — the root cause analysis was spot on and made it straightforward to fix!

The fix is included in v4.2.4: when MMM-Remote-Control detects it’s running under pm2 (via PM2_HOME or pm_id environment variables), it now skips app.relaunch() and only calls app.quit(), letting pm2 handle the restart cleanly.

Would be great if you could confirm it works on your setup!

Hi @vtek, glad you figured it out! Just for reference: when secureEndpoints: true is set, the API key can be passed in two ways:

1. URL parameter: ?apiKey=YOUR_KEY
2. HTTP header: Authorization: apiKey YOUR_KEY

Also, starting with v4.2.4 the error message now directly hints at the solution, so the next person running into this should find it faster 🙂