What the sensors note says does not phone home

What the note says shipped

The field note on dldeploy in the wild says the site ships cameras, microphones, and presence sensors as a smart-home mesh, on the owner's LAN, without a vendor phone-home. This page files that scope and does not paste the note. The dependency is the path of the sensor data: it ends on the LAN, or it does not. The note picks the LAN. The note is the sensors field note.

What the design note already listed

The companion note on a home without a vendor cloud lists Matter and other stacks as non-goals and says a camera page without a token answers 403. That is the design. This note says the sensors are what shipped. A design can exist without a shipment, and a shipment claim can be checked against the design it names. Local control is what local control requires.

What the chip guide does not say

Cameras, microphones, and presence sensors are the devices the note names. The path it claims for their readings is the LAN, without a vendor account. A similar chip in a camera that uploads to a vendor is a different product, even if the silicon manual is the same document. The design note supplies the non-goals and the 403. The chip guide supplies the part and stays silent on whether anyone shipped the mesh. This page adds no city and no install count, because the sentence it is filing does not contain them. A required vendor login, if the note is later revised to include one, would falsify the shipment sentence. Today the design note and the in-the-wild note point the same way. The manual does not point either way. That is why three sources are filed and only one of them is allowed to say the sensors shipped. Phone-home is the dependency, not the brand of the chip. Two cameras can share a vendor guide and still differ on where the picture goes. This note says the picture stays. The design note says how a token gates the page. Neither sentence is a sales count, and this brief does not become one. A reader who wants a city-by-city map will not find it in these three documents. Espressif's guide describes the chip. It does not say a particular mesh is in houses, and it does not promise that a camera stays off a vendor cloud. The guide is necessary for the hardware and silent on the deployment claim. The desk is Smart Homes.

Why it matters on this desk

The dependency is phone-home. A presence sensor that reports to a vendor account is a different product from a presence sensor the note says stays on the LAN, even if both use a similar chip. The brief exists so a reader can tell a shipping claim from a chip manual. The camera-example alternative is a third document, what a Rust camera note is an alternative to.

What this page will not add

A figure that is not in those pages is not in this brief. No house count, no city, and no uptime percentage is in the sentence this brief is using. Adding them would be fiction. The identity note's relay caution also stays there: this page does not upgrade a LAN shipment into a worldwide remote-control claim. The mobile desk is Mobile.

Where the documents split

The in-the-wild note says shipped, on the LAN, no vendor phone-home. The design note says how a device is supposed to behave, including the 403. The chip guide says what the silicon can do. Only one of them is a deployment sentence. The other two explain the words around it. The dependency stays the one those sources actually support, including the limit they state. The front of the paper is Futureweb.

What to watch next

A report that the shipped sensors require a vendor login would falsify the sentence. A count of installs, if the note publishes one, would be a new fact rather than a correction. The chip guide will not be the document that settles the phone-home question. Read together, the filed pages are the record, and a later paraphrase would not replace them.

What would change the record

If the in-the-wild note is revised, the shipment sentence moves. If the design note adds a required cloud account, the two notes would contradict and this page would have to say so. Today they point the same direction: the device, the LAN, not a vendor account. That agreement is the file. Another telling of the same documents would not create a new fact.

What stays on the house LAN

What stays specific is a field note that cameras, microphones, and presence sensors ship as a mesh on the LAN and do not phone a vendor. The design note supplies the non-goals and the token gate. The chip guide supplies the silicon and not the deployment. This page does not invent an install base, does not paste a setup, and does not treat a similar chip in a cloud camera as the same product. The dependency is the path of the reading. If the reading leaves the house for a vendor account, the note is wrong and the brief is wrong with it. If the reading stays, the chip manual was never the document that proved it. The note was. That is the whole distinction this desk is filing.