What the no-cloud note says the device keeps

What the note claims

The dldeploy note on a smart home without the cloud says an ESP32 can hold its own cryptographic identity, be adopted by its owner with a signed record, and stream over a local peer-to-peer mesh. It says nothing in that loop needs a vendor account or a remote server. It lists Matter, RainMaker, and Home Assistant core as non-goals. It says a camera page without the token derived from the device identity answers 403. The note is the dldeploy field note.

What is written and not yet measured

The same note says boards with PSRAM can use a relay so a short ticket works from another network, and that this path is written and not yet measured on a board. Boards without PSRAM are described as LAN-direct, with the relay off. A claim that the phone works from anywhere is ahead of the measurement the note itself withholds. Local control, as this desk uses the phrase, is what local control requires.

What Matter still is

The signed adoption is how the note says an owner takes the device. The token is how the note says a camera page decides. A visitor on the Wi-Fi who lacks the token is, on this account, a stranger, and the page answers 403. Matter remains a published standard. Listing it as a non-goal does not withdraw it, and this page will not pretend the Connectivity Standards Alliance changed its document because a field note declined the target. RainMaker and Home Assistant core are the other names on that list. The relay that would answer from another network is written for the PSRAM tier and, the note says, not measured on a board. The LAN-direct tier is the claim the note is willing to make as a design. Packet counts from the companion board note stay in that note. The checkable lines here are the identity, the non-goals, the 403, and the withheld measurement. A vendor account that is optional in a brochure and required at boot is not the design this note describes. The note's loop is identity, adoption, and a local stream. The Connectivity Standards Alliance publishes Matter as an application-layer standard for smart-home devices. The field note does not say Matter is withdrawn. It says this stack does not target it. A buyer comparing a Matter accessory with this note is comparing two different bets. The desk is Smart Homes.

Why it matters on this desk

The dependency is who can open the device when the vendor's cloud is absent. The note's answer is the owner, with a signed adoption and a token, on a local mesh. The 403 is the sentence that separates being on the Wi-Fi from being allowed in. A guest network is not, on this account, a key. An app sandbox on a phone, a different boundary, is what an app sandbox stops.

What this page will not paste

The note includes timings from a board that also appear in a companion note about the mesh stack. This page leaves the packet counts with that companion and keeps, here, the identity, the non-goals, and the 403. Espressif's own Wi-Fi documentation is the vendor interface underneath, not a review of this firmware. The hardware desk is Hardware.

Where the documents split

The field note is a design with an explicit list of things it will not be. The Matter page is the standard it declines. Espressif's documentation is the chip vendor's Wi-Fi interface, which neither of those pages replaces. They overlap only at the device. They do not overlap in a single protocol a reader can assume. The front of the paper is Futureweb.

What to watch next

A measurement of the relay path on a board would replace the not-yet-measured sentence. A note that adds Matter as a target would replace the non-goal list. A camera page that answers 200 without a token would falsify the 403 claim. Another summary of the same note would not. Read together, the filed pages are the record, and a later paraphrase would not replace them.

What would change the record

If the note drops the vendor-account sentence, the cloud-free claim has to drop. If the CSA changes Matter, the standard moves and the non-goal list may stay. The two documents are allowed to change independently, which is why a decline is not a deletion. This page will not treat a non-goal as a criticism of the standard.

What stays on the LAN

What stays specific is a field note that an ESP32 can hold its own identity, be adopted with a signed record, and stream on a local mesh without a vendor account. Matter, RainMaker, and Home Assistant core are named non-goals. A camera page without the token answers 403, and presence on the Wi-Fi is not permission. The relay that would serve a short ticket from another network is written, and the note says it is not yet measured on a board. The LAN-direct tier is the one the note is willing to call a design rather than a plan. The Matter specification continues to exist for devices that make the other bet. This brief does not paste the note and does not import packet counts that belong to the companion measurement. The checkable line is the 403, the non-goal list, and the withheld relay measurement.