Mastra agents can now respond to Ring doorbell events
Mastra has introduced Ring signals, allowing its agents to receive events from Ring doorbells and act on activity at a property. Agents can receive notifications, fetch snapshots or video clips through the Ring API, and decide whether an event needs attention.
- Ring signals bring Ring doorbell events into Mastra agent threads.
- Agents can receive snapshots by default and video when configured with a compatible model.
- Developers can set event priorities, summaries, attributes and repeat-event handling.
- Ring events can be routed to an existing channel thread, including an iMessage conversation.
- The integration requires a Ring developer app linked to a Ring account.
From doorbell events to agent actions
Each Ring event arrives in an agent's thread as a notification signal, with a priority that developers can configure. The agent can then use the Ring API to fetch a snapshot or video clip and determine what to do when someone approaches a door.
Mastra describes several possible uses. A home security agent could watch for human motion, view a snapshot, and flag visits that may need urgent attention. A delivery assistant could use package_delivery motion to notify someone that a parcel has arrived, while a driveway agent could log vehicle motion to track cars arriving at a property.
In the example shown by Mastra, a motion_detected clip shows a person walking toward a front door, followed by a button_press notification showing the person at the camera. The agent replies that the visit needs attention.
Snapshots, video and memory
Mastra says agents are typically configured to respond to software events from services such as Slack, Discord and iMessage. Ring signals extend that event model to activity in the physical world.
By default, an agent receives a snapshot image for each event. Developers can set visibleToModel: true on the clip tool and use a model that accepts video input, allowing the agent to watch event videos as well. The durationMs setting controls the clip length in milliseconds.
With memory enabled, an agent can be taught what it has seen, including people, vehicles and activity. Mastra's example uses observational memory, which the company says enables the agent to remember these details for future events. Developers can also set coalesce: true to merge repeated events into one notification.
Setup and shared alert threads
Ring signals require a Ring developer app linked to a Ring account. Mastra's example uses the @mastra/ring-signals, @mastra/libsql and @mastra/memory packages. The announcement says the integration requires @mastra/[email protected] and @mastra/[email protected] or later.
Developers can configure event priorities and summaries for events such as button_press, motion_detected and device_offline. By default, RingSignals sends events to its own thread. The target property can instead point to an existing channel thread, allowing Ring events to appear in an iMessage conversation or another supported channel.
A web application can follow the same thread with subscribeToThread() from the Mastra client SDK. This gives developers a way to connect Ring activity, agent responses and channel-based alerts within a shared thread, according to Mastra.
Mastra: Introducing Ring Signals for Mastra Agents | Mastra Blog
