@MarkV It’s documented how to do it. I (re)wrote that documentation personally. Feel free to read https://docs.magicmirror.builders/configuration/introduction.html#advanced-configuration-and-frequently-asked-how-to-configure-examples and ask here if you have any questions, I’ll be more than happy to help.

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

:)

@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.

So, the forum now wants to do this every time I have a notice on any followed thread.

This is not theme dependent.

Thought I’d let y’all know so it could be passed up the chain.

@Cliff365 Usually the APIs change season to season in all sports.

Just the way it is.

@dcazman Clearly, HDMI.

Seriously though

1. one that exposes the ports to the bottom of the case, not out the back. This will make it easier to mount regardless of use.

2. one with a bezel around the front - makes it easier to de-case if you decide to do that. The “zero bezel/minimum bezel” front cases have nasty fronts that make it difficult to use behind custom glass.

3. look through the showcase for other recommendations - they have a LOT of teardown examples.

@KristjanESPERANTO Encoded lines? Oh hell no.

Don’t care if it’s fully documented, if I’m not able to at least look at the code, then it’s a hell no for me.

@clakkentt Yeah – I get that… Sadly, I don’t think there’s a way to get around “Stupid video driver tricks” in this case, sadly.

@juli2709 most everything on the config is.

@clakkentt FWIW, the same thing happens on the PI - I’ve got a dual monitor set up, and when I turn off the monitors, they not only smash onto one screen, but shrink WAY down.

@juli2709

two slashes before whatever you want to comment (//):

			module: "calendar", // Built in
			//position: "top_center",  // Currently hidden 
			config: {
...

Or, simply don’t include the position item.

		module: "calendar", // Built in
			config: {
    ...

As a side note, if you want to comment out more than one line in the config, you can use the alternate syntax (/* comment */):

/*	IRS Dropped		{
						url: "webcal://www.tax.gov/calendar/employer/calendar.ics",
						name: "IRS",
						symbol: "dollar-sign",
						color: green,
					}, */

this will work with any module.

@brentmatthews

I have three:
Built in Calendar module - While it’s normally a display module, I use it in the background to handle the calendar retrieval for MMM-CalendarExt3 (Day mode), MMM-CalendarExt3Agenda (Agenda), and MMM-Multimonth (My own module for month mode because I didn’t like MMM-CX3’s month mode)

MMM-CommandToNotification - Enables display of various features, including data for an non-published module I wrote to handle display of my local weather data from my weather station.

MMM-NotificationToCommand - Much like the previous - it will take a notification and issue a command to the system - I use it to adjust a set of LEDs I have rigged in to match the mode of my mirror.

@bradley1982 so, just for clarification, the missing API was the mapbox, and disabling it worked?

Glad it’s fixed.

@sdetweil I know what the plugin states, I’m saying the tronity website isn’t providing documentation outside the login system. ;)

@sdetweil @bradley1982 If google’s translation is even half good from german, the API is available through their login - there’s no documentation outside of the account system.

As such, I’d recommend reviewing their steps to get API key/Auth token from there, and do that - it appears that’s what’s missing.

@sdetweil yeah, doing it that way just throws headers with “Undefined” until it triggers. I’m not gonna go down that rabbit hole. It seems to work as is, so I’m gonna release for now.

@sdetweil Actually, I went around it - found one of my old temp units and wired it up and did a bad thing™ according to the python docs now.

Same effect, across the room.

@sdetweil said in Not updating at midnight...:

DOM_OBJECTS_CREATED - All dom objects are created. The system is now ready to perform visual changes

start: function () {
    function scheduleMidnightUpdate() {
        const now = new Date();
        const nextMidnight = new Date(now);

        // Set the time to midnight
        nextMidnight.setHours(24, 0, 0, 0);

        // Calculate the time remaining until the next midnight
        const timeUntilMidnight = nextMidnight - now;

        // Schedule the updateDom method to be called at midnight
        setTimeout(() => {
            this.updateDom();

            // Reschedule the update for the next midnight
            scheduleMidnightUpdate.call(this);
        }, timeUntilMidnight);
    }
},

    notificationReceived: function (notification, payload, sender) {
        if (notification === 'CALENDAR_EVENTS') {
            this.storedEvents = JSON.parse(JSON.stringify(payload))
            this.updateDom();
        } else if (notification === 'DOM_OBJECTS_CREATED') {
            // Call the function to start the first schedule
              scheduleMidnightUpdate.call(this);  
        }

This is the only source I see in the docs of that - a notification. Is that correct?

Thanks for the patience after the double misunderstanding.

@sdetweil @MMRIZE so, should I move the initial call somewhere else?

@bradley1982

Let’s do some basic checks.

When you cloned the module, did you go to the module directory and run npm install ?

If not, do that now, and report back.

Did you get the API keys installed in your config, per the readme?

There may be a dependency missing from the core that it uses, I’m invoking @sdetweil to take a quick look see, and if so, instruct you how to install it.

the documentation is very poor, so really, I can’t do much more, and I doubt anyone else can, the module is 2 years old at this point, and may just be zombieware.

Good luck!