Dear team,
I have upgraded my monitor and so I could use a higher resolution for the screen.
Coming from 1.920x1.080 I’ve tried 2.560x1.440 which really looks great.

Unfortunately MMM-CalendarExt3Agenda (which I use for calendar representation) disappears after every single restart of the mirror.
This is true for the display itself as well as for a headless (remote) VNC session.
Interesting enough the webbrowser SHOWS the module!

After some time has passed calender appears suddenly (not sure which event this triggers).

Currently I’m clueless.
(It happens earlier that MMM-CalendarExt3Agenda disappeared after a Raspberry-Reboot but a restart of MagigMirror corrects this)

Any idea/hint from the experts?

Thanks a LOT!
Regards,
Ralf

Hi Mirror Enthusiasts,

Status update:
I’ve decided NOT to use a mirror.

As some others here I will implement this as a signage monitor and mount this in our living room at a convenient wall.

Reason for this: Our mirrors are mounted in our hallways - where we are present really seldom…

And the “mirror” is a really beauty and in addition all of the showed information is that useful that we “need” this more frequently.
So I’ve ordered a 32’’ display today and will mount this in a wooden (may baroque’esce) frame with a passepartout.
Will keep you posted.

Warmest regards,
Ralf

Addition: I forgot to mention that in the meantime the PIR sensor is here and is working after some “trouble”.
Ininitially this tiny bastard demolites my WLAN on the Raspi so I have bought a new one (Raspi).
It’s possible that there is no causality and the raspi broke for other reasons. But initially when I took power away from PIR WLAN recovers…
Today the new Raspi and PIR are living together without trouble.

Second tricky part was the justification of the sensor - there are two adjusments screws: one of them for the sensitivity and the other one for the length of signal.

First lesson: SMALL adaptions, LONG break to see the “real” behaviour.
Second lesson: Build a housing for the naked sensor.
I Printed a tiny box with a kind of funnel, housing the fresnel lens so the overall sensitivity (viewing angel) becomes lower…

Now it works reliably like a charm…

Regards,
Ralf

Hi all,
work in progress :-)
I’ve played around, tried a lot and have found a couple of additional information, worth to show up on our mirror.
I’m really happy that one of the additions is an idea of my wife - this seems like a sign of “acceptance” …
Today in the morning she states “we are looking at earth… - The moon is missing”.

Voilá -

(screenshot, not photo)

Modified: strava (less disciplines).

Added:
fuel prices (MMM-Fuel) ,
moon (MMM-MoonPhase),
a countdown to event (MMM-EventHorizon) and a
custom background (MMM-Profilepicture).

Warmest regards and much fun with your own mirror,
Ralf

Dear @wyovino ,
my shame, you are right.
To be honest, acrylic or foil are no variant for me.
In my first approach I’was thinking about 120x60cm, in the meantime I have found two existing mirrors in household - 190x80 and 150x90.
All three possible dimensions - at least for me - are candidates for glass for sure.
I’ve ordered a sample package and currently I’m figuring out which one ist the right.
For sure it will be 6mm, not sure is the brand.
I’ve sapmles from Mirropane Chrome spy which is referenced quite often in this forum.
Alternatively I have a local brand “Mirastar” which looks nice as well (nicer, to be honest :-) ).
Marketing wise (from website) Mirropane sounds “better”, but we tend (from eye’s perspective) to Mirastar.
Next step is talking to vendor - the online ordering form doesn’t allow my bigger dimensions -120x60 is maximum.

But anyway: Thanks a lot for your kind hint!

Regards,
Ralf

@sdetweil from your perspective :-)
Just had a deeper look into code and I didn’t understand that much…

@sdetweil O.K.,
if I have to change modules, I can do this at the “root” - which is the MMM-Pir …
I will at least have a closer look to the MMM-Notification module - maybe a good starting point to develop a completely new (forked) module…

Thanks for your engagement anyway!

Warm regards,
Ralf

@sdetweil Yes, sounds like a brillant idea.
But if I assign a value to this.config.ScreenStatus within the trigerPayloadFilter section the fire section isn’t working - so your thought is great but I cannot try this …

Any idea why the fire section is skipped?

THANKS for your effort!!
Ralf

@sdetweil , thanks!!!

Sounds plausible but doesn’t work :-(
I can reference this.config.ScreenStatus in the TriggerPayloadFilter.
But when I do this, the fire isn’t working (no notification broadcast appears).
In addition referencing of this.config.ScreenStatus in the fire block causes an error “Cannot read properties of undefined (reading ‘ScreenStatus’)”…
Any direct reference in the fire block in an IF statement creates an "unecpected ‘this’ " error message …

you can see my dumb trials commented in this snippet:

		{
		  module: 'MMM-NotificationTrigger',
		  disabled: false,
		  
		  config: {
		    ScreenStatus:"INIT",

		    useWebhook: false, // If you want to activate webhook as Notification emitter, set true. (eg. IFTTT)
		    triggers:[ // Array of triggers.
		      {
		        trigger: "MMM_PIR-SCREEN_POWERSTATUS", //REQUIRED
		        triggerPayloadFilter: (payload) => { //OPTIONAL should return true or false
		          if (payload.value == 'true' ) {
		            //this.config.ScreenStatus = "on"
		            return true
		          }
		          //this.config.ScreenStatus = "off"
		            return true
		        },
		        fires: [ // Array of fires. You can enable multi-firing with one trigger.
		          {
			         /* if (this.config.ScreenStatus == 'on') {
            		  	fire: "SCREEN_IS_ON",
          			  	} else {
            			fire: "SCREEN_IS_OFF",
          			  }*/
          			//fire: this.config.ScreenStatus,
          			fire: "BROADCAST",

		          },
		        ],
		      },
		    ]
		  },
		},

I’m SO sorry…
Ralf

@sdetweil , as expected :-( I’m not able to figure this out…
I’m in the fog of instances and .this / not .this…
Can somebody guid me, please?
I’m trying to configure MMM-NotificationTrigger to send two different notifications depending on the payload.
So my idea is to evaluate payload in given payload filter, store the result in a variable and decide with this variable which fire statement is the correct one.
But I’m stuck in referencing this variable which seems to be unknown outside the trigger-evaluation part.

This currently is my (non working) approach in my config.js file:

		{
		  module: 'MMM-NotificationTrigger',
		  disabled: false,
		  config: {
		    useWebhook: false, // If you want to activate webhook as Notification emitter, set true. (eg. IFTTT)
		    triggers:[ // Array of triggers.
		      {
		        trigger: "MMM_PIR-SCREEN_POWERSTATUS", //REQUIRED
		        triggerPayloadFilter: (payload) => { //OPTIONAL should return true or false
		          if (payload.value == 'true' ) {
		            this.ScreenStatus = "on"
		            return true
		          }
		          this.ScreenStatus = "off"
		          return true
		        },
		        fires: [ // Array of fires. You can enable multi-firing with one trigger.
		          {
			         if (ScreenStatus == 'on') {
            			fire: "SCREEN_IS_ON",
          				} else {
            			fire: "SCREEN_IS_OFF",
          			}

		          },
		        ],
		      },
		    ]
		  },
		},

I’ve tried to reference Screenstatus with “payload.ScreenStatus” as well as “triggerPayloadFilter.screenstatus”, but the dot is rejected as config error in both cases.

Any tip is highly appreciated.
Sorry for being this stupid…

Warm regards,
Ralf