@evroom
In node_helper.js you could change line 67.
Change $4 into $7.
Then observe if you see the same behavior.

@fribse said in Hmm, a lot of modules are putting up a fight for me :-(:

But now the MM is not showing anything

Hi,

Due to questions in another threat I installed that module myself.
I found out that this repository works (not the paphko version):
git clone https://github.com/szech/mmm-weatherchart.git

Try this:

$ cd ~/MagicMirror/modules/
$ mv mmm-weatherchart mmm-weatherchart.saved
$ git clone https://github.com/szech/mmm-weatherchart.git
$ cd ~/MagicMirror/modules/mmm-weatherchart
$ npm install

When it works:

$ cd ~/MagicMirror/modules/
$ rm -rf mmm-weatherchart.saved

This event:

BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20240104T180000
DTEND;TZID=Europe/Berlin:20240104T200000
RRULE:FREQ=WEEKLY;WKST=MO;COUNT=10;BYDAY=TH
DTSTAMP:20240102T212443Z
UID:63c23cpe0h356vgjl0o4tsnjbi@google.com
CREATED:20240102T212139Z
LAST-MODIFIED:20240102T212139Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:#:SingleEventRepeating
TRANSP:OPAQUE
END:VEVENT

Leads to this:

0|MagicMirror  | [02.01.2024 22:22.25.197] [DEBUG] Title: #:SingleEventRepeating, with dates: ["2024-01-04T17:00:00.000Z","2024-01-11T17:00:00.000Z",null,null,"2024-02-01T17:00:00.000Z","2024-02-08T17:00:00.000Z",null,null,null,"2024-03-07T17:00:00.000Z"]
0|MagicMirror  | [02.01.2024 22:22.25.197] [DEBUG] event.recurrences: undefined

So:

[
    "2024-01-04T17:00:00.000Z",
    "2024-01-11T17:00:00.000Z",
    null,
    null,
    "2024-02-01T17:00:00.000Z",
    "2024-02-08T17:00:00.000Z",
    null,
    null,
    null,
    "2024-03-07T17:00:00.000Z"
]

Resulting in MM showing only 5 of the 10 events.

I would like to know where to look for the RRULE processing; cannot find anything in the calendar code.
As there are some other issues that I found, I could perhaps learn something from it.

Otherwise I will open an issue for it.

@sdetweil

$ cd ~/MagicMirror/modules/MMM-PublicTransportHafas

Possible work-around.
Needs travelling via Austria :-)

To check if your station is available:

$ cd ~/MagicMirror/modules/MMM-PublicTransportHafas
$ npm run query oebb

> mmm-publictransporthafas@2.1.13 query
> node ./convenience/query_stations.mjs oebb

Using hafas-client profile: oebb

Enter an address or station name:

This will give you a station Id.

Update config.js:

$ vi ~/MagicMirror/config/config.js
:
:
      hafasProfile: "oebb",
      stationID: "<ID>",
      stationName: "<Stop>",
:
:

For me the list appears again, although I do not see the real-time times, meaning it shows the ⚠ symbol (as set in noRealtimeDelayString: "⚠",).

One can try different hafas-client profiles, listed in:

https://github.com/public-transport/hafas-client/blob/main/p/readme.md

When you are lucky there is a good alternative to db.

@othomys said in MMM-PublicTransportHafas: Service Temporarily Unavailable:

Georg-Schwarz-Str./Merseburger-Str.

For you I found this one:

$ npm run query insa

Enter an address or station name: Georg-Schwarz

Stops found for 'Georg-Schwarz':

 > Stop: Leipzig, Georg-Schwarz-/Merseburger Str.
   ID: 12555
   Transport product(s): Tram, Bus

So your config will be:

      hafasProfile: "insa",
      stationID: "12555",
      stationName: "Georg-Schwarz-Str./Merseburger-Str.",

@p1lspeda said in MMM-PublicTransportHafas: Service Temporarily Unavailable:

Höfchen/Listmann

For you, try this:

$ npm run query rmv

Using hafas-client profile: rmv

Enter an address or station name: Höfchen/Listmann

Stops found for 'Höfchen/Listmann':

 > Stop: MZ Höfchen/Listmann
   ID: 3029051
   Transport product(s): Bus

Config:

     hafasProfile: "rmv",
     stationID: "3029051",
     stationName: "Höfchen/Listmann",