Smart Home Access on Your Home Computer
The camera view, the room listen and the presence reading a vendor app holds today, moved to a computer in your house. What already runs on the LAN, and what does not.

Can my home computer give me the smart home access I already use?
For access inside the house, partly today. A camera page, a microphone stream and an adoption that refuses strangers already run on the LAN from measured ESP32 boards. The home computer cannot yet display a Janus stream itself, and reach from outside the house is not measured.
Smart home access on your home computer means the camera view, the room listen and the "is anyone home" reading that a vendor app normally holds, kept instead by a machine in your own house. The devices stay the same kind of devices. What changes is where their data goes and who can open it. This page is the hub for a series: each later page takes one household job and says what already works on the LAN and what has not been measured. The case against a vendor server is in a smart home without the cloud, and the first board goes in through deploy an ESP32 at home in an afternoon.
What the vendor app holds today
A typical smart home app is a window onto a company's computer. The camera uploads, the app downloads, and the company's policy decides who else can look. People like the window. What they object to is the house leaving through it.
Three jobs that cover most use
Most households open three things:
- A camera, at the porch or in a hallway. The measured version is rusty_esp_video: an MJPEG page a browser on the LAN opens directly. On a XIAO ESP32-S3 Sense it ran at about 13.8 to 14.3 frames per second under a 15 fps cap.
- A microphone in a room. rusty_esp_audio streams 16 kHz PCM over UDP, and a ten-minute run over the board's own access point delivered 7,201 datagrams with none lost.
- Presence without a lens. rusty_esp_sense reads Wi-Fi channel state on the home computer and says whether a room is occupied. It is benchmarked on a public dataset and has not run against a live device.
The account is the real lock
What a vendor app keeps is not just the picture. The account claims the device, and the account can revoke it. Moving the access home starts by moving that claim. rusty_esp_mid has each board mint its own did:mata and accept a signed adoption from the household. On a real chip, a stranger replaying the owner's record and a superseded record were both refused.
Where the access sits instead
Devices are reached by public key over an iroh mesh. On the ESP32 side that is rusty_esp_iroh: on a XIAO the node was up 3.2 seconds after boot and delivered 721 camera packets in 60 seconds with none lost. Nothing in that measured path uploads a stream to a vendor. The point-by-point comparison with the usual server path is a pure Rust alternative to the cloud.
The computer you own
The machine meant to hold the window is MATA, and the device crates come from Remade With Rust. MATA is meant to take the place the vendor app held, not keep a second copy of the same upload. Its media controller does not receive a Janus stream yet, so this series does not claim the picture lands on that screen.
What already works on the LAN
From a measured board you can open the camera page on the local network, count packets to see whether any were lost, and adopt the device so a stranger is refused. The camera page answers 403 without a token tied to the device identity, so a guest on the Wi-Fi is not automatically a viewer. Today, smart home access on your home computer amounts to that page plus the identity that decides who opens it. Flash size and the PSRAM tier come from choosing an ESP32 board: a 4 MB board never runs the mesh itself.
The series so far, and the limits
Each page takes one job, keeps on-your-home-computer in its slug, and ships only when that job's access is measured or clearly marked as not.
Pages in the series
- A Rust HEVC decoder on your home computer:
rusty_h2650.7.0 as host software for HEVC files you already have. No camera path uses it. - A Rust object detector on your home computer: Diana 0.11 counted 34.6 percent fewer instructions per detect. It is untimed and not wired to a camera.
- Next jobs in the same shape: a porch camera, a baby monitor, knowing who is home.
The Own vision covers the identity half. The Learn index lists what is proven.
Limits that apply to every page
- The home computer's screen cannot show a Janus stream yet.
- 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, and the identity field note says so.
- There is no C in our crates, but Track A builds on Espressif's ESP-IDF and the radio blob is Espressif's.
A brochure sells the window, the account and the remote view as one product. This series splits them: the window is the page on your LAN, the account becomes a key you hold, and the remote view stays out of every title until a board has done it.
Where to start
Put the first device in with the afternoon guide, then read the camera, microphone or presence note for the job you want. Smart home access on your home computer grows one job at a time. The Flash vision covers the tooling end of that afternoon, and the machine that should end up holding it all is MATA, the home computer.
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 and a browser opens it directly. The media controller on the home computer does not receive that stream yet, so saying the picture lands there 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.