Smart Home Access on Your Home Computer
Smart home access on your home computer keeps the live view, the listen, and the presence reading with a machine you own. The vendor app is not the holder.

Can my home computer give me the smart home access I already use?
Yes, for the access that already runs in the house. Smart home access on your home computer means the live page, the listen, and the presence reading stay with a machine you own, on the LAN. The media controller on that computer is not wired to a Janus stream yet, and reach from outside the house is not measured.
Smart home access on your home computer is the access a vendor app usually keeps: open the camera, hear the room, know whether someone is there. The difference is who holds it. The bytes stay in the house, and the computer that shows them is one you own. This page is the shelf. Later notes hang one real job on it at a time, starting from what already runs on the LAN. The argument for refusing a vendor server is a smart home without the cloud. The first device still goes in through deploy an ESP32 at home in an afternoon.
What the vendor app was holding
A normal smart home app is a window onto someone else's computer. The camera uploads, the app downloads, and a policy you did not write decides who else can look. That window is familiar. People do not want to lose the window. They want the window to stop sending the house away.
The access people already use
Three jobs cover most of what a household actually opens. A porch or hallway camera. A microphone in a room. A reading that says the room is occupied without a picture. Smart home access on your home computer is those three jobs, named one by one as this series grows. The camera page that already runs is rusty_esp_video. The microphone path is rusty_esp_audio. Presence without a lens is rusty_esp_sense.
What still leaves if you keep their app
The picture, the recording, and the fact that someone walked through. A vendor account is what claims the device and what can revoke it. rusty_esp_mid is the identity that stays on the board instead: a key the device mints, and an adoption the household signs. Smart home access on your home computer does not start by inventing a new app. It starts by moving the holder.
Where that access sits instead
The mesh dials devices by public key. That mesh is iroh, and the ESP32 side is rusty_esp_iroh. Nothing in the measured path uploads the stream to a vendor. The comparison with the usual server path is a pure Rust alternative to the cloud.
The computer you own
The home computer is the machine in the house that is supposed to hold the window. In this family that computer is MATA, and the crates are Remade With Rust. Smart home access on your home computer means MATA is the holder the vendor app used to be, not a second copy of the same upload. The media controller that would receive a Janus stream on that computer is not wired yet. This series will not pretend the picture already lands there.
What already runs on the LAN
On a board that has been measured, you can open a camera page on the local network, count whether packets were lost, and adopt the device so a stranger is refused. That is the access. It is not a phone app on a cell tower. Smart home access on your home computer, today, is that LAN page plus the identity that decides who may open it. Choosing an ESP32 board is where the flash size and the PSRAM tier come from, because a 4 MB board never runs the mesh itself.
What this series will add
Each later page is one job, with the same promise in the title: a porch camera on your home computer, a baby monitor on your home computer, knowing who is home on your home computer. The slug keeps on-your-home-computer so the shelf stays one series. A page ships only when the job's access can be described as measured or plainly marked as not. The Own vision is the identity half of the same promise. The Learn index is the list of what is proven.
Honest limits
- The home computer's media controller is not wired to a Janus stream.
- Reach from outside the house is written for the PSRAM tier and not timed on a board.
- Dev firmware still keeps the identity key in a plaintext partition. The identity field note says so.
- There is no C in our crates. Track A still builds on Espressif's ESP-IDF, and the radio blob stays Espressif's.
Smart home access on your home computer is a smaller claim than a vendor brochure, and that is the point. The brochure offers the window, the account, and the remote view as one product. This series splits them. The window that already exists is the page on your LAN. The account is replaced by a key you hold. The remote view is a row we have not measured, so it is not in the title of any use case until a board has done it. Smart home access on your home computer that promised the missing row would be the brochure again.
Where to start
Put the first device in with the afternoon guide, then read the camera, microphone, or presence note for the job you actually want. Smart home access on your home computer grows by those jobs, not by a second essay. The Flash vision is the tool end of the same afternoon.
The computer that should hold the window is MATA, the home computer. The crates that speak to the devices are Remade With Rust. Smart home access on your home computer is those two, plus the LAN page you can open today.
FAQ
Quick answers for builders evaluating this technology.
What access does this series mean?
The jobs a vendor app usually holds: opening a camera, hearing a room, and knowing whether someone is home. Each job becomes its own page. This page is the shelf they hang on.
Does the home computer already show a Janus camera?
Not yet. The camera page runs on the LAN. The home computer's media controller is not wired to receive that stream. Saying the picture already lands on that computer would be false.
Can I open it from outside the house?
Not as a measured path. A relay for the PSRAM tier is written and has not been timed on a board. Boards with 4 MB of flash never run the mesh themselves and use a bridge.
Who is the home computer?
The machine in the house that holds the access, instead of a vendor server. In this family that computer is MATA. The crates that speak to it are Remade With Rust.
What do I give up compared with a vendor app?
Their phone app, voice-assistant skills, and badges such as Matter, RainMaker, and Home Assistant core. Those are non-goals. You also give up a company running remote access for you.