Camera PoE Switch Configuration in Brookshire, TX 77423

What ‘configuring the switch’ actually covers on a camera job

Plugging cameras into a powered switch usually produces a picture, which is why so many systems are left exactly there. Configuration is the difference between a system that works in week one and one that still works in year four.

It covers six things: the power budget against real draw, each port’s power mode, separation of cameras from the rest of the network, uplink sizing against recorded bitrate, automatic recovery on ports whose cameras lock up, and documentation. None of it is exotic — it is the part skipped when a system is priced to the hardware and not the work.

Doing the power arithmetic before anyone buys the switch

Two numbers matter and they are routinely confused. Per-port power is what one camera can draw. Total budget is what the power supply delivers across all ports at once, and it is almost always far less than ports multiplied by the per-port maximum.

The gap between the two middle columns is the cable turning delivered power into heat over its length — worst on long runs and on undersized or copper-clad-aluminum cable.

The rule we work to: add the peak draw of every camera, not the idle draw, and specify a switch whose total budget leaves real headroom above that figure. A budget run at its limit has nothing left for the night every camera needs maximum power at once.

Why a budget that works at noon fails at three in the morning

This is the most common configuration failure we are called out to, and it has an obvious signature: perfect all day, then cameras dropping and rejoining in rotation through the small hours.

A camera’s daytime draw is not its real draw. After dark the infrared illuminators come on and a camera that idled at a few watts can approach double that. Multiply across sixteen cameras and a budget that looked comfortable at noon is exceeded after sunset.

What the switch does next is the second half of the problem. It sheds load by priority or port order, cutting power to some cameras. Those drop, the budget recovers, the switch restores them, and they push it over again. The system oscillates all night and settles at sunrise.

The same happens on cold nights with any heated housing, because a heater can draw more than the camera ever does.

Long driveways, gate cameras, and the 328-foot wall

Ethernet over copper is specified to 100 meters — about 328 feet — and that is the complete channel including the patch cords at both ends, not just the long piece between them. Beyond it you do not get gradual decline; you get a link that works on a mild day and fails on a hot one.

That limit is the defining constraint on Brookshire properties, where the gate at the county road can sit several hundred feet from the shop. Four ways past it, in the order we prefer:

• Fiber to a small switch at the far end. The most reliable answer: distance stops being a constraint, and glass carries no electrical energy.
• A mid-point enclosure. A weatherproof cabinet partway out with its own power, restarting the 100-meter clock.
• PoE extenders. Workable, but each is another powered device in the weather, consumes power budget, and adds a failure point.
• Extended-reach mode. Many switches have a long-distance mode that pushes past 100 meters on a port. Read the specification: it typically caps that port at 10 Mbps, which is fine for one camera and not for several.

That last one gets enabled by accident as often as on purpose, and a technician who does not know it is on will spend a long time wondering why one channel stutters.

Segmenting cameras without breaking the view you want

Cameras should not sit on the same flat network as office computers or the house. They are appliances with long service lives and infrequent updates, and they should be treated that way.

We put the cameras and the recorder on their own segment with their own address range, no route out to the internet from the cameras themselves, and one controlled path letting the people who need video reach the recorder rather than the cameras directly.

Two benefits follow: a compromised camera reaches nothing worth reaching, and camera traffic stops competing with everything else on the property. Remote viewing still works, because the recorder is the only device needing a path outward — one device to secure rather than sixteen.

Bitrate math so the recorder never drops frames

Cameras are constant producers: each streams continuously to the recorder, and most stream a second time when someone is watching live. That total has to fit through whatever connects the switch to the recorder.

A single gigabit uplink handles most small and mid-size systems easily. Problems appear when camera count, resolution, frame rate and simultaneous viewers stack up, or when the port feeding the recorder is limited to 100 Mbps. Dropped frames and recording gaps are the symptom, and cameras get the blame. We size uplinks against real settings.

Copper between two buildings is a lightning path

Nearly every property out here has more than one structure: a house and a shop, a shop and a barn, an office and a yard, plus a gate out front. The instinct is to run a network cable between them because it is cheap and it works.

It works right up until it does not. Two structures do not sit at exactly the same electrical potential, and on flat open Waller County land a nearby strike can put a very large difference between them for an instant. Copper strung between the two is the path that difference takes, and it destroys equipment at both ends.

Fiber does not have this problem: glass carries light, conducts nothing, and isolates the buildings completely. For any run between separate structures we quote fiber with a small switch at the far end as the default, not the upgrade. Where copper must be used, protection where it enters each building and a correctly bonded ground are not optional — and metal buildings need particular care, because the shell is itself a large conductor.

When an unmanaged switch is the honest answer

We do not upsell managed hardware on jobs that do not need it. Four cameras on one building, one recorder, nobody else on the network: an unmanaged switch with an adequate power budget is a good answer, and the money is better spent on cable done properly. Managed hardware earns its place when one of these is true:

• The cameras share infrastructure with a business network that must stay separated from them.
• There are enough cameras that per-port power control and priority matter.
• Cameras lock up occasionally and the switch should power-cycle that port instead of somebody driving out.
• Multiple buildings, fiber links or several switches are involved and loops become a real risk.
• You want to see which port draws what, turning a guessing game into a reading.

That automatic power-cycle feature matters most on rural properties: a camera that hangs once a month is an annoyance when the switch resets it and an expense when it needs a truck.

How EVOTECH commissions a camera switch in Waller County

1. Inventory the cameras and record each one’s peak draw, not its idle figure, then total it.
2. Measure every run including patch cords, flagging anything near the 100-meter limit before it is built.
3. Specify the switch against that total with headroom, and set each port’s power standard.
4. Design segmentation and addressing, using reservations rather than addresses typed into cameras.
5. Calculate recorded and live bitrate and size the uplink to it.
6. Build the physical side properly: ventilated enclosure, entry protection, bonded ground, fiber between structures.
7. Enable loop protection and per-port automatic recovery, and set power priority so key cameras are shed last.
8. Load-test after dark with all illumination active, because that is the condition that finds budget errors.
9. Document the port map, addresses, power settings and credentials, and hand it to you in writing.

What drives the cost of a switch build

We put no figure on this before seeing the property, because distance decides most of it:

• Camera count and real power class, which sets the switch and its power supply.
• Distances — specifically whether any run exceeds the copper limit and needs fiber or an enclosure.
• How many separate structures are involved, since each needs its own termination and protection.
• Whether existing cable can be certified and reused or has to be replaced.
• Battery backup sizing, and how long the system must stay up without utility power.
• Enclosures for equipment that will live in a shop or barn rather than an office.

The on-site estimate is free and the quote is itemized, so equipment, cable and labor are visible separately.

Configuration mistakes that put us in the truck

1. Sizing the budget on daytime draw. The system passes every test on install day and starts shedding cameras the first full night.
2. A second switch daisy-chained on to add ports. It adds a shared bottleneck and a second thing to fail, usually in the worst-ventilated spot on the property.
3. Extended-reach mode left on across the board. Every port capped at a tenth of its speed to solve one long run.
4. Copper to the barn. It works for two seasons, then one storm takes out equipment at both ends.
5. Nothing written down. No port map, no addresses, default credentials. Every future visit starts with an hour of archaeology, and that hour is billable.

Related services

Frequently asked questions