want to add 3 buttons. reset/power/change page

sdetweil

@captheavenger mmm-buttons and mmm-remotecontrol (reboot and restart)
buttons can talk to pages.

calext3, I’d fix that in config, change the refresh delay

captheavenger

so it’s weird…when magic mirror starts the just the US Holidays in that calendar module are filled out. i have 2 gmail calendars that literally take me refreshing the MM to fully populate. (Ctrl-R)

What i probably didnt make clear in my original post was does anyone have any recommendations or experience on ATXRasPi3 or WittyPi and how exactly to accomplish what i am looking to do with 3 physical buttons?

sdetweil

@captheavenger SO… I answered all those questions

use MMM-Buttons for the physical connection to MM…

this module sends notifications

now to reboot or restart MM, the MMM-RemoteControl module does that , (with notifications)
so wire those up from MMM-Buttons

and MMM-Buttons can send the notifications to MMM-Pages

all as you requested.

not hard, all the config is in MMM-Buttons… the others just respond

3 buttons, or 10, its the same.

buttons are momentary… whatever you like… connected to the pi GPIO pins

CalExt3… the calendars are big, the main calendar sends a notification , which the EXT3 modules expect… and then fill in from there…
BUT. he doesn’t KNOW when to expect the cal data to arrive, and doesn’t want to flash the screen every second…

SO… he has a timeout… if they don’t come in the first 5 seconds, he WAITS 10 MINUTES… and THEN draws all the data he has… EVEN THO
the data might have arrived at 3 MINUTES…

SO… change the timeout to 2 minutes, look at the output of npm start (pm2 logs --line=100 if you use pm2)
and calculate how long it takes and make the timeout just longer than that

captheavenger

@sdetweil
ok, just so i am clear. in the js there are these values
refreshInterval: 1000 * 60 * 10
waitFetch: 1000 * 5,
glanceTime: 1000 * 60
popoverTimeout: 1000 * 30

so are you saying when MM starts, the initial calendar population is controlled by the popover timeout? it seems like the interval of fetching calendar data is about 5 mins.

for reference,
npm start at [27.04.2024 22:49.21.737]

[27.04.2024 22:50.39.725] [LOG] Create new calendarfetcher for url: http://www.xxxxxxxx.ics - Interval: 300000
[27.04.2024 22:50.49.003] [INFO] Calendar-Fetcher: Broadcasting 21 events from http://www.xxxxxxxx

then it happens again 5 mins later and then 5 mins later again

sdetweil

@captheavenger the ext3 modules fo not read the ics data at all. they let the default(or other) calendar modules do that.

the calendar module then broadcasts the data to whoever might be interested.
ext3

so wait fetch is the number.

but if it takes 5 minutes …

captheavenger

@sdetweil ok hopefully last question and thanks for the help

that wait fetch is that just the first time it checks for calendar info or every time?
and bonus question, what if i set it to 2 minutes…is there any downside to checking more often?

3 calendars in total
28 events
27 events
1404 events (thats the primary calendar)