Do modules stop requesting API data when monitor is off or module is hidden?

[BKeyport]

@DDE12
If simply turning off the monitor. No it does not stop MM or modules.

If stopped with Module Scheduler, maybe. Module Scheduler has to announce that it’s hiding a module, and the module being hidden has to process that announcement.

What I do, is have an external routine to turn off my monitor(s), and then stop the MM process completely upon leaving where my MM is. When I return, another routine turns on my monitors and restarts my MM install.

[sdetweil]

@BKeyport if a module wishes to participate in the show/hide process

there are functions it can override to get notifcation

resume()

and

suspend()

carousel, pages, modulescheduler, call the MM functions hide() and show() on the module instance. they do NOT know if the called module participates

I think we ought to make weather suspend, as there are calls made which count against the total , which are wasted if not visible

[DDE12]

@sdetweil
Thank you! So, probably the thing to do is set up PM2 and use MMM-AlexaControl to auto start and stop it? If I have MM on a RPi and then two browser windows displaying MM, does that increase the number of API calls to 3 or is it still just one? I’m thinking about this transition to OneCall 3.0 and how to be the most efficient with the calls.

[sdetweil]

@DDE12 weather is done all in browser, so every window TAB adds calls ( 5 tabs in the same browser is 5 times the calls) and multiple instances add calls too (current and forecast for example )

calendar is done once on the server , and just presented in the browser

[BKeyport]

@sdetweil I simplifed out the details on purpose… Trying to keep it simple, Stupid (KISS)

:)