# Reolink doorbell finally supports webhooks

**URL:** <https://discourse.nodered.org/t/reolink-doorbell-finally-supports-webhooks/93834>\
**Category:** Share Your Projects\
**Tags:** doorbell\
**Created:** [10 December 2024 22:40 UTC](https://discourse.nodered.org/t/reolink-doorbell-finally-supports-webhooks/93834 "2024-12-10T22:40:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [11 December 2024 06:09 UTC](https://discourse.nodered.org/t/reolink-doorbell-finally-supports-webhooks/93834/3 "2024-12-11T06:09:07Z")

</div>

A note for users that secured their setup with [Tailcale](https://discourse.nodered.org/t/tutorial-secure-your-home-automation-with-tailscale/92849) like me: obviously you need to enter the physical ip address of the device (where Node-RED is running) in the webhook input field, and _ **not** _ the virtual hostname of that device. Because the doorbell cannot resolve that hostname to an io address, since the doorbell is not part of your tailnet. Because you cannot install a Tailscale agent on it.

Which is a pitty because I wanted to close down all traffic to my port 1880 directly (via iptables). And that is now not possible anymore...

---

_[View the full topic](https://discourse.nodered.org/t/reolink-doorbell-finally-supports-webhooks/93834)._