Allow GET requests to trigger webhooks

[kelemenarpi]

+1 for GET webhooks

[koehntopp (Frank)]

+1

Pleeease…? I really would like to use GET requests from my Shelly switches without bothering with NGINX.

Why is this such a big deal?

[adyannu]

+1

Also have devices that GET requests are the only way to integrate them. There is a PR ready to be merged to add this feature.

[mckay87 (mckay)]

+1 for GET

[ExZylan]

+1 for GET please!

I´m using Shelly devices to manage the lamps in my house. Mi fathers are deaf people and I want to control the lights to flash depending on the door they are knocking on and the native integration is too slow for this.

[muenze96 (Sebastian Meinke)]

Were did u add this?

[dtalens]

+1 for GET Webhooks

[jatgm1]

Is this available yet?

[MZorzy (Marco)]

No, but look like is ready

Allow GET in webhook triggers

[Holland]

Hopefully this will be merged soon. Working on an automation with a Mobotix doorstation. Problem is, Mobotix only supports GET.

[mucki]

Is there any alternative method to get “GET” besides of the mentioned reverse proxy?
This ist the last thing to use HA only.

[MZorzy (Marco)]

aaaand we got it

2023.5: Let's talk!

[mrli868 (P LI)]

Anyone use the New get method successfully? Mine still not funtion.

[Alderete (Michael Alderete)]

Yes, I’ve used it. It works exactly as documented, to the extent that I’ve set up webhooks with GET access (two hooks).

If you’re looking for assistance, you’ll have to provide more details.

[mrli868 (P LI)]

here is my webhook yaml

alias: WebhookOpenGate
description: https://ha.vcbc.com/api/webhook/-G-aED6JrUqHSMYPAne5AM5l0
trigger:
  - platform: event
    event_type: webhook_received
    event_data:
      webhook_id: "-G-aED6JrUqHSMYPAne5AM5l0"
      method: get
condition: []
action:
  - service: cover.open_cover
    data: {}
    target:
      entity_id: cover.msg100_b768_garage_door
    enabled: false
  - type: toggle
    device_id: 2feb92e1a059563631468d82c06d1b97
    entity_id: light.toilet
    domain: light
mode: single

AND my /config/configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

frontend:
  themes: !include_dir_merge_named themes

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 192.168.1.0/24
  webhook_id: -G-aED6JrUqHSMYPAne5AM5l0

thank you

[MZorzy (Marco)]

try manual “run” your automation, under tree dot menu.
if don’t work there is problem before webhook triggering by url

but it “opengate” or “light” up ?

[Alderete (Michael Alderete)]

It’s possible that your proxy configuration is interfering; I don’t know anything about proxies. And it’s possible that your way can work, using the event platform, but I haven’t used that.

Here’s how I have a (working) webhook set up:

automation:
  - id: action_toggle_living_room_swag_light
    alias: "[WEBHOOK] Toggle Living Room swag light"
    trigger:
      - platform: webhook
        webhook_id: the_secret_webhook_string
        allowed_methods: 
          - POST
          - GET
        local_only: true
      - platform: event
        event_type: ios.action_fired
        event_data:
          actionName: Toggle Swag Light
    action:
      - service: script.toggle_switched_light
        data:
          which: light.smart_switch_2_living_room

[mrli868 (P LI)]

thank for your replay,

Finally, I get it working now,

What I did: Just follow the normal webhook setup process

alias: webhook test
description: ""
trigger:
  - platform: webhook
    allowed_methods:
      - POST
      - PUT
      - GET
    local_only: false
    webhook_id: "-9l451In8r-VszsOd5ewvM"
condition: []
action:
  - service: light.toggle
    data: {}
    target:
      entity_id: light.toilet
mode: single

My environment :
NGINX Reverse Proxy (https://homeassistant.example.com) → Home assistant IP:port
After setup as above, I can click https://homeassistant.example.com/api/webhook/-9l451In8r-VszsOd5ewvM to trigger the action.

[Nimrod_Dolev (Nim)]

If it is still relevant, I developed an integration which brings Akuvox SmartPlus door camera feeds and door relay buttons into Home Assistant. With the integration you should have a button which will trigger the door relay to open:

Akuvox SmartPlus - View door camera feeds, open doors and manage temporary keys

Akuvox SmartPlus Integration for Home Assistant Link to GitHub View your Akuvox SmartPlus door camera feeds, open doors, and view your temporary keys. Support for adding temporary keys coming soon! Features Door Camera Feeds: Access live camera feeds from your Akuvox SmartPlus Door Intercom. Relay Button Control: Open doors remotely from within Home Assistant. Temporary Keys: View your temporary access keys. Door Open Events: Whenever a door is opened, the akuvox_door_update event…

[Faecon (Jo)]

Did you manage to get this working ?