Add support for Ring Intercom call accept / “Talk” action (to stop handset ringing)

[marcodipasqua]

Description

Summary

I’m using a Ring Intercom together with software relying on ring-client-api.
Unlocking the door works correctly, but the intercom keeps ringing on the physical handset until it times out.

In the official Ring app, when an intercom call comes in, two distinct actions appear:

• Talk (accepts the call and stops the ringing)
• Unlock Door

Pressing Talk immediately stops the ringing, while Unlock Door only opens the door but does not stop the ringtone.
ring-client-api currently exposes no method that matches this “Talk” / call-accept action.

Ring’s own support documentation confirms that, during a call (especially in ring-to-open systems), the app displays Talk and Unlock Door.

Expected behavior

It should be possible to:

• either accept/answer the intercom call programmatically (equivalent to the app’s Talk button), which stops ringing, or
• expose an API method so that client libraries (ring-mqtt / Home Assistant bridges / custom apps) can do so.

Actual behavior

• Unlock Door works (door opens)
• Physical intercom handset keeps ringing until timeout
• Only the Ring app’s Talk button stops the ringing

Additional context

ring-client-api appears not to provide any Intercom-specific call-control functions. Intercom is also not listed among the supported device categories in the documentation.

My environment includes a dual-line intercom handset (two physical buttons). Functionally, unlock works whether or not I select the line on the handset, but ringing never stops unless the Ring app accepts the call.

Feature request / question

Does the underlying Ring API expose a call-accept or “Talk” action for Ring Intercom?

If such an action exists:

• Could ring-client-api expose it?
  If not:
• Is this a limitation on Ring’s side (Intercom not yet supported in the API), and should this be tracked as a feature request?

Happy to provide logs, device info or help test any experimental implementation.

Thanks!

Proposed solution

No response

Alternatives

No response

Device data

No response