Roadmap

Proposed features and integration pathways for future development. We welcome community input. If you're interested in working on any of these, open an issue to discuss your approach.

Home Assistant Webhook Triggers ✅

Status: Implemented

Rules can now be triggered via POST /api/v1/webhooks/{rule_id} with an X-Webhook-Secret header. Secrets are generated per-rule via POST /api/v1/webhooks/{rule_id}/generate-secret and validated with HMAC constant-time comparison. The JSON request body becomes pipeline_data["trigger_input"] for downstream steps.

See API Reference: Webhooks for details.

Enhanced Pipeline Triggers with Input Parameters ✅

Status: Implemented

TriggerContext now includes a webhook_payload field. Webhook payloads and manual trigger parameters are available in pipeline_data["trigger_input"] for downstream steps to reference.

Gemini Live Tool Calling ✅

Status: Implemented

The voice companion supports function calling via the Gemini Live session. Tool definitions are built from the MCP registry and a configurable subset is passed to GeminiLiveProvider at startup. When Gemini emits a FunctionCall part, the audio handler routes it to the matching MCP tool handler and sends a FunctionResponse back. The voice agent can now answer questions like "Where is grandma?" or "What happened today?" using real system data.

Configure which tools are available to the voice companion via mcp.gemini_tools in settings.yaml. See MCP Integration for the full tool list.

Pipeline Templates / Presets

Status: Proposed

Problem: Creating pipelines from scratch is complex for new users. Each of the 14 step types has its own configuration, and choosing the right combination requires understanding the system.

Design: Ship JSON fixtures with preset pipeline definitions:

Template	Steps
Camera Alert	person_identification → llm_call (vision) → llm_call (reasoning) → notification
Periodic Check	llm_call (vision) → llm_call (reasoning) → condition → notification
Medication Reminder	activity_detection → wait → verification → notification
Door Monitor	person_identification → condition → notification → ha_action

A GET /rules/templates endpoint lists presets, and POST /rules/from-template creates a rule from one. A "Use Template" button in the rule creation dialog would allow one-click setup.

Impact: Dramatically lowers the barrier to entry for new users.

Activity Timeline

Status: Proposed

Problem: PersonActivity records exist but there is no timeline visualization. Caregivers must manually correlate activities, sightings, and alerts.

Design:

• Backend: GET /persons/{id}/timeline?date=YYYY-MM-DD endpoint merging activities, sightings, and alerts into a unified chronological view
• Frontend: Vuetify v-timeline component in the person detail drawer showing the day's events with icons, timestamps, and room information

Use cases:

• Caregiver reviews grandma's day at a glance
• Identify patterns (always in kitchen at noon, late medication on Tuesdays)
• Spot anomalies (no activity detected for an unusual period)

Impact: Provides the "daily story" that caregivers need to feel confident about their family member's wellbeing.

---

Contributing to the Roadmap

Have an idea that's not listed here? We'd love to hear it. The best way to propose a new feature is to open a GitHub issue with:

1. Problem statement: what limitation does this address?
2. Proposed design: how would you implement it?
3. Use cases: who benefits and how?
4. Impact: what does this unlock for the project?

We prioritize features that maintain the project's core values: privacy-first, on-premise, composable, and accessible to multigenerational households.