Calendar does not run on secondary screen

BKeyport

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

sdetweil

@BKeyport ok, just fyi, node doesnt have a browser clientOnly uses electron same as full

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

BKeyport

@sdetweil

ViewNotification doesn’t show anything…

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

BKeyport

If the answer appears to be frank’s solution in that other thread, I don’t understand what to do or how to fix it. without knowledge of where he’s working I have no idea where to touch.

sdetweil

@BKeyport those look like browser side messages not server side

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

sdetweil

@BKeyport

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

BKeyport

@sdetweil Yep. that fixed it.

sdetweil

@BKeyport awesome!!!

sdetweil

This fix is in the next release , Oct 1