Webhook trigger appears to ignore allowed_methods

Configuration
1

I am trying to create an automation triggered by a webhook using HTTP GET. I can’t use POST or PUT because the doorbell cam that is creating the request doesn’t have curl or another way to send anything except GET. Despite specifying the allowed_methods as GET, POST the log shows the requests are being ignored because the webhook only allows PUT, POST. If I run the same curl test command using POST it works as expected.

Edited to add I am running Home Assistant Container 2026.5.2.

Hopefully someone can point out where I’m going wrong. Thanks!

Here is the automation:

alias: Doorbell
description: ""
triggers:
  - trigger: webhook
    allowed_methods:
      - GET
      - POST
    local_only: true
    webhook_id: doorbell-entry
conditions: []
actions:
  - action: shell_command.announce_message
    metadata: {}
    data:
      message_id: doorbell
  - action: persistent_notification.create
    metadata: {}
    data:
      message: Doorbell Webhook Received
      notification_id: Doorbell_Entry_ID
mode: single

This is the curl command used for testing:

curl -X GET http://rpi5-home.local:8123/api/webhook/doorbell-entry

And here is the log entry:

Webhook doorbell-entry only supports PUT,POST methods but GET was received
2

I cut & pasted your triggers section into my own automation and it works fine for me.

Core: 2026.4.1

The only thing I can think of, is that you have more than one automation that has the same webhook_id (doorbell-entry)

3

Thanks for checking. Probably not a duplicate issue since the webhook works if I use POST, but I did verify that I only have the one automation that uses Webhook.

4

I just had the same issue… Simple restart of HA fixed it for me.

I think it might be caused by this line: core/homeassistant/components/webhook/trigger.py at 0b8fb3652506e3b01c61ddaa3ec15f0395f076d7 · home-assistant/core · GitHub
e.g. creating it first as PUT,POST (lets say via UI as this is the default) and then changing it to something else causes the methods to be ignored since the web hook was already registered and this is not called anymore.. But I am not 100% sure..

5

I believe you are correct. I haven’t tested adding GET to an existing webhook and restarting HA, but I created a new webhook with GET enabled and it worked. If I get time I will test to confirm and open an issue. Thanks for the follow-up.

6

I think webhooks have to be installed like new integrations do, so restart if you add a new one. Maybe the reload function will work as well, not sure. You would have to test. But a webhook is a back end thing, so it would have to be running all the time at some level.