HomeCAN I VIBECODE
Home Assistant Cloud?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Home Assistant Cloud is an optional subscription service run by Nabu Casa, the company behind the open-source Home Assistant project. It adds cloud-dependent conveniences: secure remote access from anywhere with encrypted traffic (Nabu Casa states it cannot view users' smart-home data); cloud voice bridges for Amazon Alexa and Google Assistant; cloud speech-to-text and text-to-speech for the Assist assistant (speech is never stored or used for training); encrypted cloud backup of the latest Home Assistant backup, restorable on first boot of new hardware; webhooks for triggering automations; and improved WebRTC camera streaming. Home Assistant works fully without it; subscriptions fund Home Assistant development. The cloud integration ships enabled by default (configurable in configuration.yaml) and is used by a large share of active installs. Setup: start a 31-day trial, then log in from
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build 'SelfHost Reach', an original open-source replacement for the core Home Assistant Cloud workflow: secure remote access to a local smart-home hub, encrypted offsite backup, webhook forwarding, and an Assist voice bridge. Workflow: an agent installed on the hub registers once with your server, receives a per-device token and subdomain, and opens a persistent WebSocket tunnel with mTLS; the owner then reaches the hub at https://<subdomain>.<your-domain> from any browser, with no local ports opened and no LAN IPs exposed. The server keeps a device registry (SQLite), terminates TLS via Let's Encrypt, forwards HTTP webhooks into local automations, stores client-side-encrypted daily backups to S3-compatible storage (server holds ciphertext only; the key stays with the owner), and exposes a REST API plus a minimal dashboard for devices, backups, and webhooks. User-facing requirements: one-command agent (Docker image plus a Python or Go binary), dashboard with an audit log, backup restore-on-first-boot flow, rate limiting, and a setup guide for Nginx/Caddy. Implementation: model tunneling on Cloudflare Tunnel / Tailscale patterns; Go or Node server; agent encrypts backups with an owner-held key before upload; optional WebRTC relay for camera streaming. Do not copy Nabu Casa's name, 'Home Assistant Cloud' branding, logo, colors, or any proprietary UI/assets; build an original minimal interface. Out of scope: billing/payments, mobile apps, Google/Alexa cloud certification, hosted STT/TTS (use local or pluggable providers). Deliver a repo with a README covering setup, architecture, security model, and important limitations: single-server tunnel bottleneck, domain+TLS requirement, tunnel latency, backup retention, and a note that this is unaffiliated with Home Assistant and Nabu Casa.