default calendar fetching issues

[nowayto]

I’m using default calendar with calendarExt3
Actually I’m using 2 .ics, one for holidays and one for private, both are Google cals and sometimes module has fetching issues.
I can’t figure what the problem is because behaviour is strange.

These are the cases that happened to me, everytimes on startup:

• no default calendar events, no ext3 events
• default and ext3 shows only holiday events
• default shows nothing, ext3 shows some events

[sdetweil]

@nowayto have you installed the broadcast fix?

https://forum.magicmirror.builders/topic/19282/version-2-30-0-calendar-fix-for-clipping-broadcast-events

[sdetweil]

@nowayto default calendar NEVER displays past events

[sdetweil]

@nowayto other thing is how ext3 processes broadcasts

it doesn’t want to flash the screen on every update
calendar module procceses each calendar independently, do events arrive at different times

there are two settings
waitFetch how long to wait for All events (5 seconds)
update cycle??? how often to redraw. (30 mjns)

[nowayto]

@sdetweil I though I applied the fix in the past, although I’m not 100% sure.
But I don’t think the issue is ext3 related.

In my opinion sometimes default calendar don’t fetch the calendars, especially at the morning.
When it happen I don’t see any lines and a error message appear.
I don’t remember the message and now it’s working.
In the last one hour I tried to restart MM some times but now seems working, everything ok, no error message.
If it will appear, I’ll write it here

[sdetweil]

@nowayto to check on the fix

git branch

in the MagicMirror folder

[nowayto]

@sdetweil

git branch

• _fix_clipping
  master

Error appeared now:
" Error in the calendar module. Check logs for more detail."

I don’t know where to find calendar logs but with “pm2 logs”
I don’t see any errors information about calendar issue, just something about another module.

/home/MYUSER/.pm2/logs/mm-error.log last 15 lines:
0|mm | socket: {
0|mm | localAddress: 'MMIPADDRESS,
0|mm | localPort: MMPORT,
0|mm | remoteAddress: undefined,
0|mm | remotePort: undefined,
0|mm | remoteFamily: undefined,
0|mm | timeout: undefined,
0|mm | bytesWritten: 322,
0|mm | bytesRead: 0
0|mm | }
0|mm | }
0|mm | }
0|mm | [2025-03-19 13:30:59.574] [ERROR] Failed to retrieve repo info for MMM-Growatt: Error: Command failed: cd /home/MYUSER/MagicMirror/modules/MMM-Growatt && git fetch -n --dry-run
0|mm | fatal: unable to access ‘https://github.com/dekinet/MMM-Growatt.git/’: Empty reply from server
0|mm |

I don’t think this could be related to calendar issue

[sdetweil]

@nowayto

ok, on the right branch

yes, when run with pm2, then pm2 logs is the way…

there are two sections of the output

the .error(stderr) and .out(stdout)

can you look in the .out?

the folder for the pm2 logs is

~/.pm2/logs

note the leading dot on .pm2

[nowayto]

@sdetweil

It’s very long.

I checked the end paragraph ad I saw just errors from growatt module.
Do I have to search something in particular?

[sdetweil]

@nowayto said in default calendar fetching issues:

Do I have to search something in particular?

I do not know

can you recreate this if un restart MagicMirror? does it always fail in the morning?

pm2 is really for production use,

if you can repeat it

pm2 stop all
cd ~/MagicMirror
npm start &>somefile.txt

wait til failure
ctrl-q on MagicMirror screen
then examine the somefile.txt