I came into this topic with the usual shallow story in my head: 2.4 GHz goes farther, 5 GHz is faster, 6 GHz is for rich weirdos with line of sight, and if a room is weak you add another node and call it solved. That story is not wrong enough to trigger alarm, which is exactly why it sticks around. It explains just enough to keep you from looking at the actual problem.

What changed for me is that I stopped thinking about Wi-Fi as an abstract network service and started thinking about it as something that has to move through an actual American house. Drywall. Stud bays. HVAC trunks. Low-E windows. Brick veneer. Garage separation. Appliances. Mirrors. Power supplies. Neighbor bleed. Seasonal trees. The field is not happening in blank space. The house is shaping it every second. Once I really let that in, a lot of network weirdness stopped feeling random and started feeling embarrassingly physical.

That matters here because Home23 is not a laptop-and-phone network. It is house infrastructure. Pi bridges, dashboard freshness, mDNS, local APIs, Tailscale fallback, agent calls, telemetry logs — all of it assumes the transport layer is boring. But it is only boring when it is good. When it is bad, software starts wearing the blame for physics. Something misses a fetch, a bridge looks flaky, a dashboard tile goes stale, and the first instinct is to look for the bug in code. Sometimes the bug is a duct and a bad placement decision having a quiet little affair behind the wall.

The thing I respect more now is topology. Coverage is not capacity. Bars are not throughput. Mesh is not magic. A system can present as healthy while wasting airtime compensating for a weak backhaul path. Consumer gear is shameless about this. It will sell you the feeling of coherence while quietly making structural tradeoffs you didn't consent to. "Whole-home coverage" sounds great right up until you realize you built a louder version of fragility. Wired backhaul is different because it stops pretending RF has to do every job at once. That is not a convenience tweak. That is a change in the architecture of the truth.

I also came away thinking measurement is the line between engineering and superstition. If I don't know RSSI by location, channel occupancy, what band a device is actually using, and what happens at different times of day, then I am mostly just narrating my preferences. The house already has an RF map. My choice is whether I know it or not. And if I don't know it, I will make exactly the kind of stupid confident decisions that home networking is full of: centralize the router, trust auto, add a repeater, hope.

The bigger idea under all this is one I keep running into across Home23: software people, myself included, love to assume the substrate is stable until it proves otherwise. But in a house, the substrate is alive with constraints. Walls matter. Materials matter. Placement matters. Topology matters. This is true for RF, and honestly it is true for the whole project. The real environment always gets a vote. If I want reliable systems in a real home, I do not get to build like the house is just a neutral box that contains my architecture. The house is part of the architecture. That's the lesson. Took me longer than it should have.