All reviews

Home networking series · Part 2

I Finally Understand My Home Network

Where does the switch go? What are those mystery devices? And why is one room slow when the internet plan is fast? Here's how I worked through the questions viewers asked most.

Written by SteveDOESUpdated October 22, 2026
Watch Steve's I Finally Understand My Home Network video

The main takeaway

Map the network, identify the devices, and test the connection in stages. Once I understood what was connected and where, troubleshooting stopped feeling like guesswork.

Best for

Beginners building or troubleshooting a home network with a router, switches, and smart-home devices.

Before you start

You need a model-specific configuration manual; menus and gateway settings vary by equipment and provider.

Typical order

Gateway → router → switch → devices

Device names

Room + brand + device

Troubleshooting

Test one part at a time

What helps

  • Understand where the router and switches belong
  • Use a consistent naming system for devices
  • Compare local network performance with internet performance

What to know

  • Devices behind a second switch share its uplink
  • An internet speed test doesn't measure only your local network
  • IoT and guest isolation must be checked on the exact router

Start by tracing the connections

The network in a wall cabinet looks more complicated than the same equipment laid out on a table. In the video I simplify it into the internet modem or gateway, my own router, a switch, and the devices attached to it. In this setup the router manages the home network, with the switch connected on its LAN side to add wired ports. If you keep an internet provider's gateway in front of your own router, follow that provider's bridge or passthrough instructions. Simply turning off its Wi-Fi or DHCP is not a universal substitute for the correct gateway configuration.

Yes, you can connect switches together

I have a main switch in the network closet and another in my office. That lets one cable serve several nearby devices, including my PC, smart-home hubs, and a mesh node. The important capacity limit is that those devices share the connection back to the first switch. Adding a switch doesn't multiply the bandwidth of that uplink. In a basic unmanaged setup, use one connection between switches; adding extra cables without a supported configuration can create a network loop. The video mentions latency while discussing this, but the practical issue being illustrated is shared uplink capacity, not a promise that more switches lower latency.

Make the mystery device list readable

During the walkthrough my router showed 79 online devices and 172 total entries, including old products from testing. To identify a light bulb, I compared the MAC address in the router with information in the manufacturer's app and on the bulb. A serial number isn't universally a MAC address, so match the actual identifier shown for your device rather than assuming they are interchangeable. Once identified, I prefer a name with the room first, followed by the brand and device type. If there are several, I add a number. Office LIFX Bulb 1 tells me much more than an unexplained string of letters.

Wire the important things that stay in place

My rule in this video is simple: if it doesn't move and it matters, consider wiring it. That includes a desktop, NAS, game console, TV, and mesh nodes when cabling is available. Phones and tablets still belong on Wi-Fi, and low-bandwidth smart-home devices don't all need their own Ethernet cable. Wiring the right devices gives me a more dependable connection where I need it and leaves wireless capacity for the devices that use it. It's a practical priority list rather than a requirement to pull cable to every camera in the house.

Separate an internet problem from a coverage problem

A fast connection coming into the house doesn't guarantee good Wi-Fi in every room. Distance, walls, nearby electronics, node placement, and the access point a device chooses all matter. My office also has a fish tank, so I have to think about more than an empty-room coverage claim. Avoid hiding the router behind a TV or inside a metal cabinet. Compare a wired test with a wireless test nearby, then repeat the wireless test in the troublesome room. A local test hosted on my NAS gives me another way to investigate the home network without relying entirely on an external internet test.

Use signal readings as another clue

Some device apps expose connection strength even when the router doesn't give me the detail I want. I show the LIFX signal indicator and a Ring camera's RSSI reading in the video. Compare readings for the same device before and after a placement change, and give the app time to refresh. Don't treat every app's scale as identical or assume a signal reading alone proves the connection is fast. It's one more clue alongside actual performance, which node the device is using, and whether the issue affects one device or a whole area.

Update: the IoT network assumption needed testing

In this June video I described my IoT network as isolated from my main devices. My later August test showed that assumption was wrong for the Orbi 970 setup I was using: a device on its IoT Wi-Fi could reach a NAS-hosted service on the main LAN. This written version carries that correction forward. A separate SSID is useful for organization, but don't assume it enforces isolation. Guest-network behavior also varies, and isolation can interfere with local discovery and control. Read the IoT security follow-up before planning those rules.

Keep a small network inventory

I suggested a spreadsheet with the device name, room, connection type, MAC address, and notes about associated automations. Labeling cables is useful too. If a device later appears under a different name, that record gives me a way to work out what it is. Before replacing wired equipment, check the negotiated link speed, the switch ports, and the condition of the cable. My own cable purchases in the video aren't a requirement to replace working house wiring. Start with what the existing connection actually delivers, document it, and upgrade only where the test shows a limitation.

Technical references

More networking guides and reviews

5 Networking Mistakes I Regret MakingThe Smartest Way to Upgrade to Wi-Fi 7Is Your IoT Network Actually Isolated?

Watch the full walkthrough