Did you use docker for this add-on? I don’t see any add-on directorys, and what I’ve read says they need to run in their own container.
MZorzy
September 6, 2022, 7:15am
42
1 Like
Still waiting for GET requests to use my Akuvox doorbell. I found this PR and hope to see this feature soon:
home-assistant:dev ← esev:webhook_trigger_opts
opened 01:20AM - 14 Feb 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
Two new Webhook trigger options have been added that limit how a webhook can be used to trigger an automation. A new _allowed_methods_ option can be used to control which HTTP request methods can activate the trigger (GET, HEAD, POST, PUT). And the _local_only_ option is used allow devices outside your local network to activate the trigger.
Previously all webhook triggers could be activated by HEAD, POST, and PUT methods from any device (local or on the internet). With the new options, only POST and PUT are enabled by default.
**In Home Assistant version 2023.1.0 any webhook trigger that does not set _local_only_ to false can only be activated by devices on the same network as Home Assistant.**
To update your webhook triggers, click the gear/cog icon beside the Webhook ID. Then select an appropriate value for _Only accessible from the local network_. It is necessary to deselect the option for the 'Save' button to appear. Then reselect the option if it should be enabled. This will make the repair warning go away.
See the [webhook trigger documentation](https://www.home-assistant.io/docs/automation/trigger/#webhook-trigger) for a description of the new options. And please review the new the [Webhook Security](https://www.home-assistant.io/docs/automation/trigger/#webhook-security) section for best practices when using webhook triggers.
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This PR adds two new options for webhook triggers:
1. __allowed_methods__: Controls which methods can be used with a webhook trigger. Allowed methods include GET, HEAD, POST, and PUT. By default only POST and PUT are enabled. Methods that are not enabled will return 200 OK to the caller, but will not trigger the webhook; they will cause a log message to be generated though.
2. __local_only__: Controls whether the webhook trigger can be accessed by devices on the internet. A log message will be generated for access attempts from the internet when this option is enabled. This option is ignored for webhook triggers that are activated via Nabu Casa Cloud or via the websocket API.
See #56446 & #65928 for a discussion on the security implications of this change.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [x] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example entry for `configuration.yaml`:
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR. Furthermore, for new integrations, it gives an impression of how
the configuration would look like.
Note: Remove this section if this PR does not have an example entry.
-->
```yaml
automation:
trigger:
- platform: webhook
webhook_id: "some_hook_id"
allowed_methods:
- POST
- PUT
local_only: true
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #65348
- This PR is related to issue: #56446
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/21637
- Link to the frontend pull request: https://github.com/home-assistant/frontend/pull/11680
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Boroda
December 13, 2022, 2:06am
44
+1 to have get as a webhook natively as it open while world of automation that you can trigger from any device like oen / close turn on /off for example guest access to device
koehntopp
December 31, 2022, 2:34pm
46
+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?
+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.
ExZylan
January 23, 2023, 7:33pm
49
+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.
1 Like
MZorzy
March 6, 2023, 7:35am
53
No, but look like is ready
home-assistant:dev ← swiergot:webhook_get2
opened 08:37AM - 20 Sep 21 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Accept HTTP GET method in webhook triggers. So far only POST, PUT and HEAD have been allowed, but many devices which can be configured to send HTTP commands support only GET.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Holland
March 6, 2023, 10:42am
54
Hopefully this will be merged soon. Working on an automation with a Mobotix doorstation. Problem is, Mobotix only supports GET.
2 Likes
mucki
March 29, 2023, 4:44pm
55
Is there any alternative method to get “GET” besides of the mentioned reverse proxy?
mrli868
June 15, 2023, 2:47pm
57
Anyone use the New get method successfully? Mine still not funtion.
Alderete
June 15, 2023, 3:54pm
58
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
June 16, 2023, 5:35am
59
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
June 16, 2023, 6:49am
60
try manual “run” your automation, under tree dot menu.
but it “opengate” or “light” up ?
