@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
Dear Sam, (@sdetweil ),
as always (!) Great.
this worked - thanks a LOT!
With this little “sniffer” I was able to figure out, what happens…
It is just a rumour that MMM-Pir sends a “USER_PRESENCE” notification.
In fact there is one and only one notification “MMM_PIR-SCREEN_POWERSTATUS”.
With a little bit trial & error I was able to identify that the payload is true / false for the events “screen on” / “screen off”.
With further searches today I found @MMRIZE’s module MMM-NotificationTrigger which seems to do what I’m looking for - Tranlating SCREENPOWERSTATUS-true to FRAMELIGHT_ON and opposite.
Hopefully I can figure out how to use MMRize’s module in right manner.
Warmest regards,
Ralf
(I have to wait for LED strip - they are shipping currently)
Keep you posted.
@sdetweil awesome…
I’ve missed that, I’m so sorry!
Thanks for your effort in tutoring!
Highly appreciated!
Just another quick question - fiddling with the developer console in Chrome:
I’ve found the Application tab and there is a recorder for “notifications” but there is no notification shown up.
Any chance to debug the notifications in my config (I would like to see “sender” and “payload” …
Thanks again for your kind support!
Warmest regards,
Ralf
@sdetweil OK, thanks for this.
Any chance that there is a module around that handles “intermodule communication” - like an application broker?
If not and I got you right than my way must be to adjust a given source code which leads me in trouble with updates.
Any other idea how I can solve my problem “How can I synchronize on/off switching of a LED strip with MMM-Pir’s on/off switching of monitor”?
Thanks for any suggestion.
Ralf
Hi folks,
I’ve searched a long while and found several (some of them really old) posts regarding the “easy” question:
“How can I synchronize on/off switching of a LED strip with MMM-Pir’s on/off switching of monitor”?
None of them are “answered” to a final solution - so I currently stuck…
I’ve seen that in module MMM-Pir seems to be a notification ‘USER_PRESENCE’.
(on and off, I assume).
What I cannot figure out: Where and how I can use this?
I’ve found a LED-strip module (MMM-FrameLight) which can handle notifications but is awaiting notifications in an own format e.g. “FRAMELIGHT_ON”.
How can I fetch the PIR “event” = notification for user presens/absence (from WWW-Pir) and how can I overhand this in changed format to an other module (WWW-FrameLight)?
Or is this simple not possible or do I even make an error in my approach - will this be solved in a completely other manner?
I would like to avoid to write own code to do the same work as already given modules.
For sure there is something obvious which I currently cannot see …
(To be honest I’m FAR away from real understanding what happens inside MM and I’m an absolute beginner in JavaScript - so the above mentioned “writing code at my own” would be really hard).
Thanks for any guidance.
Ralf
For Your Information:
as per Sam’s tip I will ignore the “not prepared” message.
For the described problem I’ve chosen the “hard” (not nice) approach:
I’ve eliminated the “intelligent” approach to set color and symbol with a functional design and have “hard” coded evere single condition.
.CX3A .event .title {
color: var(--calendarColor);
}
.CX3A .event .time {
color: var(--calendarColor);
}
as the appropriate items to set the color for singl events to the icon color.
The “hard” variant of my X3A module is now as folelows:
{
module: "MMM-CalendarExt3Agenda",
position: "top_left",
//header: "Wichtige Termine",
config: {
eventTransformer: (ev) => {
if (ev.title.search("Restmüll") !== -1) {ev.isFullday = [true], ev.color = "grey" }
if (ev.title.search("Papier") !== -1) {ev.isFullday = [true], ev.color = "blue"}
if (ev.title.search("Gelber Sack") !== -1) {ev.isFullday = [true],ev.color = "yellow"}
if (ev.title.search("Biomüll") !== -1) {ev.isFullday = [true],ev.color = "black"}
if (ev.title.search("Restmüll & Papier & Gelber Sack") !== -1) {ev.isFullday = [true],ev.title = "Alle Tonnen",ev.color = "fuchsia"}
if (ev.title.search("Reise") !== -1) {ev.symbol = [ "fa-solid fa-briefcase" ],ev.color = "cyan" }
if (ev.title.search("Arzt") !== -1) { ev.symbol = [ "fa-solid fa-user-doctor" ], ev.color = "red" }
if (ev.title.search("Grillen") !== -1) { ev.symbol = [ "fa-solid fa-grill-hot" ], ev.color = "red" }
if (ev.title.search("Flug") !== -1) { ev.symbol = [ "fa-solid fa-plane" ], ev.color = "Gold" }
if (ev.title.search("Urlaub") !== -1) { ev.symbol = [ "fa-solid fa-plane" ], ev.color = "Gold" }
if (ev.title.search("Krankenhaus") !== -1) { ev.symbol = [ "fa-solid fa-hospital" ], ev.color = "red" }
if (ev.title.search("Fahrt") !== -1) { ev.symbol = [ "fa-solid fa-car" ], ev.color = "cyan" }
if (ev.title.search("Auto") !== -1) { ev.symbol = [ "fa-solid fa-car" ], ev.color = "cyan" }
if (ev.title.search("Hochzeit") !== -1) { ev.symbol = [ "fa-solid fa-heart" ], ev.color = "Gold" }
if (ev.title.search("Hochzeitstag") !== -1) { ev.isFullday = [true], ev.symbol = [ "fa-solid fa-heart" ], ev.color = "Gold" }
if (ev.title.search("Abendessen") !== -1) { ev.symbol = [ "fa-solid fa-utensils" ], ev.color = "yellow" }
if (ev.title.search("Restaurant") !== -1) { ev.symbol = [ "fa-solid fa-utensils" ], ev.color = "yellow" }
if (ev.title.search("Geburtstag") !== -1) { ev.isFullday = [true], ev.symbol = [ "fa-solid fa-birthday-cake" ], ev.color = "green" }
if (ev.title.search("Workshop") !== -1) { ev.symbol = [ "fa-solid fa-screwdriver-wrench" ], ev.color = "white" }
if (ev.title.search("Service") !== -1) { ev.symbol = [ "fa-solid fa-screwdriver-wrench" ], ev.color = "green" }
if (ev.title.search("Friseur") !== -1) { ev.symbol = [ "fa-solid fa-scissors" ], ev.color = "white" }
if (ev.title.search("Rad") !== -1) { ev.symbol = [ "fa-solid fa-biking" ], ev.color = "red" }
if (ev.title.search("Fahrrad") !== -1) { ev.symbol = [ "fa-solid fa-biking" ], ev.color = "red" }
if (ev.title.search("Zahnarzt") !== -1) { ev.symbol = [ "fa-solid fa-fa-tooth" ], ev.color = "red" }
if (ev.title.search("Arzt") !== -1) { ev.symbol = [ "fa-solid fa-stethoscope" ], ev.color = "red" }
if (ev.title.search("Kino") !== -1) { ev.symbol = [ "fa-solid fa-film" ], ev.color = "blue" }
if (ev.title.search("Film") !== -1) { ev.symbol = [ "fa-solid fa-film" ], ev.color = "blue" }
if (ev.title.search("Training") !== -1) { ev.symbol = [ "fa-solid fa-book" ], ev.color = "cyan" }
if (ev.title.search("Party") !== -1) { ev.symbol = [ "fa-solid fa-ticket-simple" ], ev.color = "green" }
if (ev.title.search("Theater") !== -1) { ev.symbol = [ "fa-solid fa-ticket-simple" ], ev.color = "green" }
return ev
}, // end Eventtransformer
// useWeather: false ,
showMiniMonthCalendar: false,
//onlyEventDays: 10 -- Nur Tage mit terminen anzeigen ist in der custom.css eingetragen, DAS funktioniert...
endDayIndex: 30,
} // end config CalenderExt3Agenda
}, // End module CalenderExt3Agenda
It would be nice if I can get some information regarding background of the errors described above…
Regards,
Ralf