Hi,

I’am pleased with the module as it is, I just can’t seem to get the keepAlive working.

Part of my config:

{
			module: 'MMM-NetworkScanner',
			position: 'bottom_left',
			config: {
				devices: [
					{macAddress: "xx:xx:xx:xx:xx:xx", name: "Kleine iPad", icon:"mobile"},
					{macAddress: " xx:xx:xx:xx:xx:xx ", name: "Telefoon Hein-Jan", icon:"android"},
					{macAddress: " xx:xx:xx:xx:xx:xx ", name: "iPhone Nicole", icon:"phone"},
					{macAddress: " xx:xx:xx:xx:xx:xx ", name: "iPad Nicole werk", icon:"apple"},
					{macAddress: " xx:xx:xx:xx:xx:xx ", name: "Tesla", icon:"car"},
					{macAddress: " xx:xx:xx:xx:xx:xx ", name: "Grote iPad", icon:"tablet"},
					{macAddress: " xx:xx:xx:xx:xx:xx ", name: "iPhone Hein-Jan", icon:"phone-square"},
				],
				showUnknown: false,
				keepAlive: 300,
				showLastSeen: false
			}
		}

The keepAlive is in there, but if a device is detected (highlighted), it also “disappears” (un-highlighted) in aprox 5 seconds.
I was under the impression that the keep alive would keep it highlighted (alive) for at least 300 seconds (5 minutes).
Is my understanding wrong?

Kind regards,

Hein-Jan

Adding

address: “0.0.0.0”,

to the config.js also did the trick for me.

Thanks!

Same problem here. ipWhitelist worked in 2.1.2. 2.1.3. no more.
VNC works, Putty works. MMM-Remote-Control cannot be accessed.

Hein-Jan

@Mar

I had similar problems. A search on the forum revealed that a daily reboot acts as a work-around. I am using the MMM-Remote-Control in combination with the MMM-ModuleScheduler for the nightly reboots.
It works like a dream ever since.

@morozgrafix & @ianperrin

On scheduling and Cron Jobs.

To my regret the Schedule did not work out the way that had I planned it. My mirror did not show cute, drifting Valentine icons on Valentines Day. Some further experimentation today has shown that MMM-ModuleScheduler does not work with either an 02 or a 2 but does work with a “feb”.

Mine was running at aprox 70°C. My mirror is vertically orientated. The Pi is in a casing but al the sides of the casing have been removed. I have fitted the CPU and the memory with heatsinks.
The Pi was mounted near the top of my mirror (I could slide it under the piece of board that is being used to mount the mirror on the wall.) My mirror case does have some ventilation holes at the top, but no fan.
Being slightly worried about the 70°C (I expect it to go up to 80°C in summer) I decided to change the postion of the Pi in my mirror from the top of the frame to the bottom, so it was no longer in the monitors pre-heated air.
At the bottom of the case my Pi is now running at aprox 55°C. A drop of 15°C by simply relocating within the mirror frame.

I’ll take that over running a fan for my mirror.

I’m with cowboysdude,

MMM-ModuleScheduler combined with MMM-Remote-Control.

Scheduler sends MonitorOn and Off’s to Remote.

Works like a dream!

I also have problems with the default calendar module and repeating or recurring events. Especially when editing a specific event that is part of a repeating event.
I deleted one episode of a series of events. My Google calendar (app on phone) no longer shows the event, but my Mirror still shows the event. I have tried a restart and a reboot, but the calendar module persists in showing the event.
I have modified yet one other episode of a different series (changed the duration). Again Google calendar on Phone shows updated results, the mirror persists in showing the none-updated version.

This is annoying as I am using the Mirror as a family board, it has all the musical classes, sports trainings, chores-schedules etc. on it. These are of course recurring events, but some of them also tend to be edited to fit that week’s specific schedule.
It feels to me that the default calendar module has a problem with handling exceptions to recurring events.

Any ideas / solutions?

@morozgrafix

Yep, alreay did that.

This is my config included is the scheduling part.

{
                        module: 'MMM-Valentine',
                        position: 'fullscreen_above',
                        classes: 'scheduler',
                        config: {
                                // display the module only on the 14th of february
                                module_schedule: {from: '0 7 14 02 *', to: '30 23 14 02 *' },
                                valentinesCount: 25,
                                valentinesSize: 2.00,
                        }
                },

I have been struggling with the 2 asterixes behind the “minutes and hours” values but before the “day of the week” value. Cron revealed that they probably are “Day of the month” and “month of the year”.
I am a Noob, and all of the scheduling examples had wildcards there. I feel fairly confident this is going to work.

Can it be combined with MMM-Scheduler to only (and automatically) show up on the 14th of Feb?