@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",

Well, I got it working, sort off.

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.

I have to use http://MMIP:8090/remote?action=NOTIFICATION&notification=SOMEONE_AT_THE_DOOR for it to work.

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

You are absolutely correct. Thanks for pointing it out.

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.

@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",

Well, I got it working, sort off.

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.

I have to use http://MMIP:8090/remote?action=NOTIFICATION&notification=SOMEONE_AT_THE_DOOR for it to work.

{
        module: "MMM-NotificationTrigger",
        config: {
                useWebhook: true,
                triggers: [
                        {
                                trigger: "SOMEONE_AT_THE_DOOR",
                                fires: [
                                        {
                                                fire: "SHOW_ALERT",
                                                exec: "vcgencmd display_power 1",
                                                payload: {
                                                        title: "PORTEN",
                                                        message: "Der er nogen ved porten!",
                                                        timer: "20000",
                                                }
                                        }
                                ]
                        }

                ]
        }
},

Last thing to do is to also play the doorbell. I need to configure the speaker on the rasp4 first.

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",

I though it would be like this:

{
        module: "MMM-NotificationTrigger",
        config: {
                useWebhook: true,
                triggers: [
                        {
                                trigger: "SOMEONE_AT_THE_DOOR",
                                fires: [
                                        {
                                                fire: "SHOW_ALERT",
                                                exec: "home/Kragh/monitor_on.sh",
                                                payload: {
                                                        title: "PORTEN",
                                                        message: "Der er nogen ved porten!",
                                                        timer: "10000",
                                                }
                                        }
                                ]
                        }
                ]
        }
}

monitor_on.sh is set as executionable.

https://www.doorbird.com/downloads/manual_d10x_en_de.pdf

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

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

That is sweet. Now I need to exec a shell script also.

@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",
						}
					}
				]
			}
		]
	}
},

Thanks man! I will try that out. I think the doorbird appliance is using application/json POST requests, even though that is hard to find in the documentation.

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

It is just a webhook that is meant to get cached by MMM-NotificationTrigger module, that in turn should be able to send notifications to the Alert module.