Consumer

Two-way audio for home security and doorbell systems

Porchline · Talk through any camera or doorbell from your Home Assistant, even over local http

WatchingDraft scoreMature market · since 2013 · AI estimate

37PWAS score

Confidence

Based on 9 of 9 factors

Overview

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem: Home automation users with video doorbells, security cameras, and baby monitors cannot use two-way audio within their home automation platform and must fall back to manufacturers' proprietary apps, fragmenting their experience and compromising local-first operation. Supporting audio interaction across multiple device brands and camera protocols requires platform-level implementation.
Solution concept: A unified, protocol-agnostic two-way audio capability built into the Home Assistant platform (web frontend and mobile apps for iOS and Android) that works with any compatible camera or doorbell integration, eliminating the need to leave the Home Assistant ecosystem for audio features.
Who has it: Home automation enthusiasts and households running Home Assistant with compatible video doorbells, security cameras, or baby monitors.
How they handle it today: Users currently use Home Assistant for video monitoring but must switch to separate manufacturer apps to use two-way audio features with their cameras and doorbells, creating fragmentation across multiple interfaces.
Why now: WebRTC support maturation in mobile platforms now enables microphone access over local http connections in native apps, removing the previous technical blocker. A growing installed base of compatible devices (video doorbells, security cameras with two-way audio capabilities) in the smart home market increases demand for this integration.
How it could charge: Inference: Home Assistant core is open-source and free, but monetization could occur through Home Assistant Cloud subscriptions (for remote access and advanced features), or companion app premium features. Alternatively, manufacturers of compatible devices benefit from deeper ecosystem integration, reducing friction for their customers and increasing lock-in.

Score breakdown

A model sorted each factor into a rubric bucket; code turned buckets into numbers. Unknown factors are left out of the score and lower confidence instead.

Market validation

Confidence 95 · 2 evidence · Clear demand shown by 32 reactions and 23 comments on a GitHub issue, indicating multiple users actively requesting two-way audio support.

Revenue evidence

Confidence 30 · Judged from the description · No evidence that users currently pay for two-way audio functionality; Home Assistant core is free and open-source.

Growth

Confidence 70 · 1 evidence · Home Assistant has 2.7 million households, indicating a large and active user base with sustained growth in the smart home category.

Problem severity

Confidence 70 · 2 evidence · Users must leave the Home Assistant platform to access two-way audio on compatible devices, creating repeated friction and platform fragmentation that costs time and usability.

Economic proximity

Confidence 30 · Judged from the description · This feature improves the Home Assistant platform itself but does not directly sit at a transaction point; monetization would likely be through subscriptions or indirect device sales.

Distribution

Confidence 30 · Judged from the description · Two-way audio would require Home Assistant to be installed on a shared system or mobile app used by household members, creating collaboration incentives across multiple users.

Buildability

Confidence 70 · 1 evidence · Implementation requires protocol-agnostic audio handling across multiple device types and platforms (web, iOS, Android), plus WebRTC integration—complex but feasible with existing technologies.

Differentiation

Confidence 70 · 1 evidence · Home Assistant currently lacks this feature while competitors' devices and manufacturer apps have it; filling this gap would eliminate a specific reason users leave the platform.

Retention and timing

Confidence 30 · Judged from the description · Two-way audio with doorbells and security cameras is a recurring use case (answering visitors, checking on children), and smart home adoption is currently accelerating.

Risk penalties

Heavy regulationTwo-way audio systems handling home security and surveillance involve privacy and wiretapping laws that vary by jurisdiction, particularly around consent to recording and data storage.−9
Depends on one platformThe solution is conceptually dependent on Home Assistant as the host platform; building outside Home Assistant would duplicate infrastructure and lose the ecosystem advantage.−6

Score history

37 · confidence 55 · config v1First score · 17 Oct 2026

Two-way audio for home security and doorbell systems

Overview

Build this business

Verdict

Score breakdown

Risk penalties

Score history

Validation gate

Evidence · 5 items

Market validation

Revenue evidence

Problem severity

Differentiation

Market

Existing products

Build

Legal reconstruction check

Community