@karsten13

thanks again. The magic mirror now runs smoothly and without any errors :)

l@karsten13

hi, im running now in the recommended electron and a newer node version

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; raspberry: [object Object]; virtual: false
OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+
VERSIONS: electron: 31.1.0; used node: 20.14.0; installed node: 22.5.1; npm: 10.8.2; pm2: 5.4.1
OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined

The MM now starts very fast and without rebooting the raspberry. I’ll keep you updated.
Thanks in advance :)

@karsten13

here is the information:

[2024-07-22 07:54:19.741] [INFO] System information:

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 3 Model A Plus Rev 1.0; raspberry: [object Object]; virtual: false

OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v7+

VERSIONS: electron: 29.1.6; used node: 20.9.0; installed node: 21.7.3; npm: 10.5.0; pm2: 5.3.1

OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined

@sdetweil
I updated from 2.27.0 to 2.28.0 by script.
Sounds like 2.28.0 isn’t the newest release anymore? Or will it be fixed in the unreleased version?

What do you mean with the calendar entry? The config?

{
module: “calendar”,
header: “Müllkalender”,
position: “bottom_left”,
config: {
customEvents: [{keyword: ‘bio’, symbol: ‘recycle’, color: ‘green’},{keyword: ‘müll’, symbol: ‘trash’, color: ‘Green’}],
fetchInterval: 1200000,
fadePoint: 0.75,
calendars: [
{
symbol: “calendar-check”,
maximumEntries: 3,
url: “https://xxx”
}
]
}
},

thank you!

Hi,

after upgrading to the second community release Im stuck with these errors:

0|mm | [4143:0719/155732.710554:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=512

0|mm | [2024-07-19 15:58:46.475] [ERROR] Calendar Error. Could not fetch calendar: MY-iCLOUD-CALENDAR-ADRESS TypeError: fetch failed
0|mm | at Object.fetch (node:internal/deps/undici/undici:12293:11)
0|mm | at processTicksAndRejections (node:internal/process/task_queues:95:5)
0|mm | at runNextTicks (node:internal/process/task_queues:64:3)
0|mm | at process.processImmediate (node:internal/timers:449:9) {
0|mm | cause: ConnectTimeoutError: Connect Timeout Error
0|mm | at onConnectTimeout (node:internal/deps/undici/undici:7434:28)
0|mm | at node:internal/deps/undici/undici:7390:50
0|mm | at Immediate._onImmediate (node:internal/deps/undici/undici:7422:13)
0|mm | at process.processImmediate (node:internal/timers:478:21) {
0|mm | code: ‘UND_ERR_CONNECT_TIMEOUT’
0|mm | }

Im running on a raspberry pi 2B+ with the node version v21.7.3

Any ideas or known problems? I don’t find any in combination of these two errors.
Thanks in advance :)