edit MagicMirror/js/server.js

add these two lines

				allowEIO3: true,   // line 45
				pingInterval: 120000,  // server → client ping every 2 mins   //add
				pingTimeout:  120000   // wait up to 2 mins for client pong   //add	

edit MagicMirror/js/socketclient.js

add these two lines

    this.socket = io(`/${this.moduleName}`, {  // line 15
                path: `${base}socket.io`,
                pingInterval: 120000,  // send pings every 2 mins     // add
                pingTimeout: 120000    // wait up to 2 mins for a pong  // add

edit MagicMirror/js/server.js

add these two lines

				allowEIO3: true,   // line 45
				pingInterval: 120000,  // server → client ping every 2 mins   //add
				pingTimeout:  120000   // wait up to 2 mins for client pong   //add	

edit MagicMirror/js/socketclient.js

add these two lines

    this.socket = io(`/${this.moduleName}`, {  // line 15
                path: `${base}socket.io`,
                pingInterval: 120000,  // send pings every 2 mins     // add
                pingTimeout: 120000    // wait up to 2 mins for a pong  // add

franks. i dont know either
but ill have something for you in the morning

ViewNotification doesn’t show anything…

When I load the mirror in chrome/brave I get this in console:

what os, and this is 2.32, right?

can you install MMM-ViewNotifications on the second screen instance and see if the events are broadcast.
or look in the output of npm run server to see the broadcast message from the parser…

Calendar-Fetcher: Broadcasting 19 events from https://calendar.google.com/calendar/ical

I’m running two instances now and they behave as expected…

I only have 1 calendar

Browser is whatever node uses - same problem occurs on other sessions through chrome like browser on my Main PC (Brave)

One magic mirror folder - all configs in MM/Config just numbered.
Refresh does nothing. (Via Chrome/Brave).

Start MM using this:

export MM_CONFIG_FILE=config/config2.js
export MM_PORT=8081
export ELECTRON_DISABLE_GPU=1
DISPLAY=:0 node clientonly --address mirrorserv.local --port 8081

we had/have bug where the socket send of the events from calendar module is not received at the client
see
https://github.com/MagicMirrorOrg/MagicMirror/issues/3380

manual refresh works

see this for a possible workaround

https://github.com/MMM-CalendarExt2/MMM-CalendarExt2/issues/393#issuecomment-3075487788

do you have one MagicMirror folder or two?
two sep config files, so if one instance you use the MM_CONFIG_FILE env to launch the second

just trying to get detail so i can repeat this

Multi-screen: https://docs.magicmirror.builders/configuration/introduction.html#a-couple-of-real-world-examples (remember, I re-wrote this?)

Client/Server: https://docs.magicmirror.builders/getting-started/installation.html#server-only

Calendar = default calendar module.

Most of the calendars are in fact local, so timing don’t matter. The only problem I’m having is that this exact configuration works on the screen running as main monitor, but not on the screen running as secondary. Main monitor’s header info is this:

var config = {
	address: "0.0.0.0",
	port: 8080,
	ipWhitelist: [],
	language: "en",
	timeFormat: 12,
	units: "imperial",
	//logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],

multi screen

client server

calendar

MagicMirror is a browser, it runs on a logical screen

on a desktop, multiple displays are all one screen

so are you saying you are vnc’d in with two sessions? two displays?

multiple web browsers to same MagicMirror server/port will get the same stuff

multiple web browsers to same server/ different ports will get different stuff ( as configured)

multiple browsers will appear on the remote system per the system design

1 minute refresh might not be enough time to get all the entries processed