Read the statement by Michael Teeuw here.
MMM-PublicTransportHafas: Service Temporarily Unavailable
-
@KristjanESPERANTO said in MMM-PublicTransportHafas: Service Temporarily Unavailable:
I just released version 3.0.1 to fix this 😀
At this moment I see an entry in the past with +0.5.
Also saw +0.6.
When turning on debug, I only seedelay
values of 0, 60 and null, so I wonder where the current 0.5 comes from.
The values forwhen
andplannedWhen
all have a difference of 0 or 1 minute.It seems that it only affects the first entry in the list, which in my case is the first unreachable in the past.
And it does not really bother me, but it still is odd. -
I did the update
cd ~/MagicMirror/modules/MMM-PublicTransportHafas
git pull
npm cibut it still does not work.
Any idea??
-
pi@magicmirror-buero:~/MagicMirror/modules/MMM-PublicTransportHafas $ npm ci
npm warn deprecated vbb-translate-ids@3.1.0: Deprecated. Use vbb-translate-ids@latest.
npm warn deprecated hafas-client@2.10.4: Deprecated. Use hafas-client@latest. -
@Volkae Looks like you don’t use my fork. I recommend deleting the module and install this: https://github.com/KristjanESPERANTO/MMM-PublicTransportHafas
-
@KristjanESPERANTO said in MMM-PublicTransportHafas: Service Temporarily Unavailable:
deleting the module and install
I think to be more clear, deleting the module folder
-
-
@KristjanESPERANTO
Thank you for your support. I hope to find some time this weekend to implement your suggestion. -
@KristjanESPERANTO , it works. Thanks a lot. :-)
-
Hi, thanks for your update.
I installed your git version and I had to install undici additionally. Is that correct?The MM works but ended starting up again and agin:
0|mm | <— Last few GCs —>
0|mm | [17870:0x2a530000] 119266 ms: Mark-Compact (reduce) 126.9 (128.6) -> 126.4 (128.1) MB, pooled: 0 MB, 791.61 / 0.00 ms (+ 0.9 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 816 ms) (average mu = 0.190, current[17870:0x2a530000] 120521 ms: Mark-Compact 126.9 (128.1) -> 126.5 (128.6) MB, pooled: 0 MB, 1201.60 / 0.00 ms (average mu = 0.113, current mu = 0.043) allocation failure; scavenge might not succeed
0|mm | <— JS stacktrace —>
0|mm | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
0|mm | ----- Native stack trace -----
0|mm | /home/mirror/MagicMirror/node_modules/electron/dist/electron exited with signal SIGABRTIm using a raspberry pi zero with 512 MB RAM which worked fine in the past.
Also some system information:
0|mm | [2025-02-03 08:57:53.254] [INFO] System information:
0|mm | ### SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; virtual: false
0|mm | ### OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+
0|mm | ### VERSIONS: electron: 32.2.7; used node: 22.13.1; installed node: 22.13.1; npm: 10.9.2; pm2: 5.4.3
0|mm | ### OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefinedAnyone have the same problem?
-