@czabel
I need your config and custom.css to guess what happened.

@MilkShake said in Receive a HTTP request and subsequently wake up display and display alert/notification:

I cannot get http://192.168.1.100:8090/webhook?action=notification=SOMEONE_AT_THE_DOOR to work. It returns a 200:OK but nothing is displayed.

http://MMIP:8090/webhook?notification=SOMEONE_AT_THE_DOOR

read carefully.

@bassin12
Updated. There was a logical bug in the code. Sorry.

@MilkShake said in Receive a HTTP request and subsequently wake up display and display alert/notification:

It works when I include the notification in the URL like this:

http://MMIP:8090/remote?action=NOTIFICATION&notification=SOMEONE_AT_THE_DOOR

Simply, you can use this.

http://MMIP:8090/webhook?notification=SOMEONE_AT_THE_DOOR

That is the GET method.

for the shellscript, your trial seems right, but you should take care for the path and the permission.
I think this would be right. (It depends on your environment)

exec: "bash /home/Kragh/monitor_on.sh",
// OR
exec: ". /home/Kragh/monitor_on.sh",

@MilkShake
Could you share the doc? Let’s look inside together.

@bassin12
I’ll look inside; maybe it was my mistake.

@MilkShake

First, What request method and body is emitted from the gate?
It should be something like;

• endpoint : http://MYMM:8090/webhook
• requestMethod : "POST"
• requestHeader: "Content-type: application/json"
• requestBody : (

{
  notification: "SOMEONE_AT_THE_DOOR"
}

If you select “GET” as requestMethod, you may need to deliver the notification as parameter instead of requestBody JSON

Then you can configure like this.

{
	module: "MMM-NotificationTrigger",
	config: {
		useWebhook: true,
		triggers: [
			{
				trigger: "SOMEONE_AT_THE_DOOR",
				fires: [
					{
						fire: "SHOW_ALERT",
						payload: {
							title: "Someone arrives home",
							message: "Welcome back home!",
							timer: "10000",
						}
					}
				]
			}
		]
	}
},

@MilkShake
What is the request body from the gate? “SHOW_ALERT”? I think it would be better to emit other dedicated custom notification other than “SHOW_ALERT”.

@natmash @sdetweil
It seems a bug on the default calendar module. One of my CX3 user also reported it so I looked inside.
https://github.com/MMRIZE/MMM-CalendarExt3/discussions/146#discussioncomment-9380307

UPDATE 1.9.0 (2024-09-25)

• customHeader available,.
  Now you can add customHeader for the calendar view instead of module’s default header.

• variable maxEventLines by number of rows
  Every month has a different number of weeks in its calendar, so it was hard to adjust the height of the month view. Now, you can assign the variable maxEventLines by the number of rows. (And additional CSS Selectors related to it was added.)