NCO3
(Nco3)
May 4, 2023, 1:55pm
1
Hi everyone,
I just upgraded to 2023.5 and found out, that my webhook triggers don’t work anymore.
I am using a webhook to be called from my alarm system when a motion sensor of this system is triggered. This should then set a binary_sensor accordingly:
- trigger:
- platform: webhook
webhook_id: HollaDieWaldfee
binary_sensor:
- name: "Bewegung (Wohnzimmer)"
unique_id: bewegung_wohnzimmer_webhook_lupus
state: "on"
device_class: motion
auto_off: 0:00:05
as this is not a webhook used in an automation I cannot uncheck the local network only flag:
So, is there any option to make it accessible again?
NCO3
(Nco3)
May 4, 2023, 2:32pm
2
Got it!
Just some minor changes:
- trigger:
- platform: webhook
webhook_id: HollaDieWaldfee
allowed_methods: GET
binary_sensor:
- name: "Bewegung (Wohnzimmer)"
unique_id: bewegung_wohnzimmer_webhook_lupus
state: "on"
device_class: motion
auto_off: 0:00:05
Now I can call it using an internal URL:
https://192.168.68.70:8123/api/webhook/HollaDieWaldfee
aceindy
(Aceindy)
May 4, 2023, 4:05pm
3
There is a new field local_only
trigger:
- platform: webhook
webhook_id: AlarmArmed
allowed_methods:
- POST
- PUT
local_only: false
NCO3
(Nco3)
May 5, 2023, 6:33am
4
Thank you, @aceindy
However, it was a good trigger to think about using the webhook locally only
aceindy
(Aceindy)
May 5, 2023, 6:55am
5
I noted I had to reload trhe page before the cogwheel turned up.
And yeah, I should have used your lines…