Hi all,

Posting this as a feature request for TP-Link’s ONVIF implementation on doorbell devices.

Request:
Expose doorbell button press events via ONVIF (e.g. as a proper event/notification), not just motion events.

Current behaviour:
Right now, the ONVIF event stream appears to only include motion detection. This works fine for generic activity, but it means a physical doorbell press doesn’t generate any distinct event. From an integration point of view, a button press is effectively invisible.

Why this is an issue:
A doorbell press is a discrete, high-signal event and shouldn’t be conflated with motion. Many integrations depend on that distinction. For example, when using Scrypted as a bridge into HomeKit Secure Video (HKSV), only motion events can be mapped through — so pressing the doorbell button results in no notification or trigger at all.

What would help:
Ideally, the ONVIF event service would expose a dedicated doorbell press event (e.g. via the standard event/notification mechanisms — topic-based or similar to other binary events). Even a simple boolean/state change event for “button pressed” would be enough for downstream systems to hook into.

Use case:

• Map doorbell press → HomeKit doorbell event (via Scrypted)
• Trigger automations specifically on button press
• Avoid relying on motion as a workaround (which is unreliable and semantically wrong)

At the moment, the hardware is capable, but the lack of an exposed event limits integration quite a bit.

Would be great to know if this is on the roadmap, or if there’s any technical reason it can’t be surfaced via ONVIF.

Thanks