Add a conversational workspace to Home Assistant
Pi Agent runs as a Home Assistant add-on and connects to OpenRouter or another AI provider that you configure. It can help plan automations, examine available data, and draft household workflows. What it can do, what data leaves your home, and what it costs depend on the tools, permissions, provider, and model you choose.
Why add Pi Agent to a smart home?
A conventional smart home follows rules that someone has already created: turn on a light at a set time or adjust cooling when occupancy is detected. When you need a new workflow—or an existing one fails—you still need someone to investigate and update the configuration.
Pi Agent adds a conversational workspace for describing goals, examining available Home Assistant data, and preparing changes. With approved tools and permissions, it can also run scheduled checks and report conditions that match criteria you define.
What Pi Agent is
Pi Agent is an add-on installed in a supported Home Assistant environment. It provides:
- A conversational workspace: Describe goals, ask questions, and refine requirements in plain language.
- Configuration assistance: Draft automations, dashboards, scripts, and local information workflows for review.
- Repeatable checks: With the necessary access, inspect selected device states and history, then report results under rules you approve.
Core capabilities
These English examples illustrate possible workflows. Actual execution requires the relevant Home Assistant entities, integrations, tools, and permissions, plus any confirmation rules you establish.
Describe the workflow you want
State the outcome, scope, and exceptions in plain language. Pi Agent can draft an automation, scene, or dashboard, but you should inspect and test it before enabling it.
Analyze the data you choose to provide
When configured with appropriate access, it can help analyze temperature, humidity, energy, and device-history data. Treat its findings as proposals to verify, not guaranteed savings or autonomous conclusions.
Build around local and public services
Where a documented data source is available, Pi Agent can help draft a local integration or dashboard. Confirm the source, license, reliability, and security implications before deployment.
Search household manuals and notes
Organize appliance manuals, warranty details, service contacts, renovation records, and recipes in an approved storage location. Pi Agent can help retrieve that information, subject to the access controls you configure.
Support maintenance without surrendering control
Smart-home failures can go unnoticed until a routine stops working. With explicitly configured access, Pi Agent can run defined checks and report anomalies. Automatic repairs should be limited to preapproved, tested actions.
Run scheduled checks
Check selected battery levels, unavailable entities, and automation traces on a schedule. Notify an approved recipient when criteria are met; require confirmation before making unplanned repairs.
Test before changing production
Review dependencies, validate syntax, and test in a nonproduction environment where possible. A test cannot prove that every real-world condition is safe, so keep backups and a rollback plan.
Document why each setting exists
Record the reason for thresholds and schedules alongside the configuration. That context helps you or a future operator understand why a setting exists.
Use model judgment carefully
Conventional automations evaluate explicit conditions. An AI model can help classify less-structured input, but its output can be wrong. Use confidence thresholds, privacy controls, and a safe fallback.
Classify a situation with safeguards
If you intentionally provide camera or sensor data to a compatible model, it may classify a doorstep event. Do not treat identity or intent as certain; minimize transmitted data and choose a conservative notification fallback.
| Observed event | Possible classification | Configured response |
|---|---|---|
| A known household member arrives | Likely known person | Record locally; notification optional |
| A person leaves an item and departs | Possible delivery | Routine notification: “An item may have been left at the door.” |
| An unknown person remains for more than 5 minutes | Unrecognized prolonged presence | Priority notification with a user-opened camera view |
Explore energy-use patterns
Provide your utility’s current tariff and the relevant sensor history. Pi Agent can help compare peak and off-peak operation, explain assumptions, and propose schedules for you to verify. It cannot guarantee a bill reduction.
Create a weekly household report
Send a scheduled summary through your configured notification service: energy trends, device status, automation failures, and approved changes. Define the recipients and exclude sensitive details they do not need.
Connect suitable local data sources
Fill a gap with a documented integration
Pi Agent can help draft an integration for transit, waste collection, emergency alerts, or local announcements when an authoritative, legally usable data source exists. Availability and reliability vary by location; unsupported services remain unsupported until verified.
Track consumables and warranties
Store operating hours, replacement dates, and warranty dates in a location you approve, then notify selected recipients at defined thresholds.
Design conservative emergency routines
Emergency routines require careful design, testing, and a safe fallback. Use authoritative alerts and device capabilities; do not let an AI model improvise safety-critical actions.
Make access understandable and accountable
Use plain language
Household members can describe a problem in ordinary language, but each user should have appropriate permissions. Pi Agent should explain what it found and distinguish a suggestion from an executed action.
Support supervised learning projects
A learner can use Pi Agent to plan a small sensor or lighting project. An adult should supervise electrical work, credentials, purchases, and any change to the live home.
A day with Pi Agent
Here is one possible day after the household has configured the required integrations, permissions, and notification rules.
-
07:10 · Before leaving
Entryway display: transit arrival in 3 minutes; rain is forecast this afternoon
The display combines your approved local transit and weather sources.
-
10:30 · No one is home
“An item may have been left at the door.”
A privacy-reviewed workflow sends a qualified notification instead of asserting the visitor’s identity or intent.
-
14:00 · Afternoon
Review the dehumidifier schedule
Recent humidity history and the supplied tariff suggest a later schedule to review; comfort and cost results are not guaranteed.
-
17:40 · Evening
“Local waste collection is expected in 10 minutes.”
Your configured notification service uses an authoritative local feed, where one is available.
-
19:30 · After dinner
“How do I connect the printer for this worksheet?”
Pi Agent retrieves the saved manual and explains the documented steps under the user’s access level.
-
22:00 · Before going to bed
“Tomorrow’s chance of rain is 90%. Bring in anything drying outside.”
The reminder cites your configured weather source and forecast time.
-
23:30 · The whole family falls asleep
Night check: 2 batteries below threshold; monitored doors and windows report closed
The check reports configured states; it does not replace physical verification or a security system.
-
Monday 08:00
The weekly household report arrives
The report summarizes measured energy use, device status, failures, and approved changes through your configured notification service.
Compare three approaches
| Cloud smart speaker | Conventional smart home | Pi Agent | |
|---|---|---|---|
| Adding a workflow | Limited to features provided by the vendor | Configure it yourself or engage an integrator | Describe the goal; review and test the proposed implementation |
| Finding failures | Depends on vendor diagnostics | Depends on configured monitoring | Can summarize defined checks; repairs require approved guardrails |
| Decision model | Interprets supported commands | Evaluates explicit rules | Can analyze and suggest, but model output requires verification |
| Data handling | Vendor cloud under its terms | Varies by deployment and integration | Local Pi Agent files; request content goes to the configured AI provider |
| User experience | Use supported commands | Learn dashboards and controls | Use plain language, within each user’s permissions |
FAQ
Can I use Pi Agent without programming experience?
Can I add Pi Agent to an existing smart home?
What happens when the internet connection is unavailable?
Does household data leave my home?
What does each delivery option include and cost?
Can Pi Agent change my Home Assistant settings on its own?
Choose a delivery path
Option A (self-hosted) / Option B (managed by WoowTech)
Option A (self-hosted) means the customer operates the system; operating owner: [customer-designated owner]. Option B (managed by WoowTech) means WoowTech operates the documented, agreed service scope; service owner: [WoowTech-designated owner]. Approved availability, pricing, currency, regions, support terms, and contact route are pending.
Approved contact channel pending