Is any cable bundle warm/hot, are jackets discolored or melted, or do you suspect line-voltage wiring is cross-connected to the data cabling?

Dense PoE bundles can heat up, and miswired line voltage on a data jack is a shock/fire hazard.

On the switch/injector, is the port a PoE-capable port and is PoE enabled for it (not administratively disabled)?

Not every port on a switch supplies PoE, and managed switches can have PoE turned off per port.

Is the switch's total PoE power budget exceeded (many powered devices already on it)?

A switch has a total PoE watt budget. Once exceeded, it stops powering additional or lower-priority ports.

Does the source's PoE standard meet the device's requirement — e.g. an 802.3bt (PoE++) device on an 802.3af source won't power up?

802.3af (PoE) ≈ 15W, 802.3at (PoE+) ≈ 30W, 802.3bt (PoE++) up to ~60-90W. The source must meet or exceed the device's class.

Is the cable run within 100m total, undamaged, and does a known-good patch cord / different PoE port power the device (swap test)?

Runs over 100m, a damaged/miswired pair, or a marginal cable can block PoE. Swap one variable at a time.

low-voltage troubleshooting

PoE device won't power up

Common symptoms: poe camera no power; poe device dead; no power over ethernet; ap won't boot; poe port not powering

Stop and call a pro if:

PoE is low-energy (Class 2) but a tightly bundled run of many PoE cables can overheat — check for warm/discolored cable jackets
never assume a jack is low-voltage; stop if you find line-voltage wiring cross-connected to data cabling
power down and unplug the device before reseating any connector

Step-by-step diagnostic flow

Step 1
Is any cable bundle warm/hot, are jackets discolored or melted, or do you suspect line-voltage wiring is cross-connected to the data cabling?
Dense PoE bundles can heat up, and miswired line voltage on a data jack is a shock/fire hazard.
Step 2
On the switch/injector, is the port a PoE-capable port and is PoE enabled for it (not administratively disabled)?
Not every port on a switch supplies PoE, and managed switches can have PoE turned off per port.
Step 3
Is the switch's total PoE power budget exceeded (many powered devices already on it)?
A switch has a total PoE watt budget. Once exceeded, it stops powering additional or lower-priority ports.
Step 4
Does the source's PoE standard meet the device's requirement — e.g. an 802.3bt (PoE++) device on an 802.3af source won't power up?
802.3af (PoE) ≈ 15W, 802.3at (PoE+) ≈ 30W, 802.3bt (PoE++) up to ~60-90W. The source must meet or exceed the device's class.
Step 5
Is the cable run within 100m total, undamaged, and does a known-good patch cord / different PoE port power the device (swap test)?
Runs over 100m, a damaged/miswired pair, or a marginal cable can block PoE. Swap one variable at a time.

Possible outcomes

Stop — heat or line-voltage hazard

high confidence

Overheating PoE bundles or line voltage cross-connected to data cabling are fire/shock hazards that must be addressed before troubleshooting.

Safe next steps

Unplug the affected run from the switch/injector
Do not energize the run again until a qualified installer inspects it
If line voltage is on the data cabling, call a licensed electrician

Overheating cable or line-voltage cross-contact

Port wasn't supplying PoE — now resolved

high confidence

A non-PoE port or per-port disabled PoE was the cause; enabling PoE / moving to a PoE port restored power.

Safe next steps

Confirm the device boots fully and stays up
Label which ports supply PoE for next time

Switch PoE budget exceeded

high confidence

The switch's total PoE watt budget is maxed, so it won't power an additional device.

Safe next steps

Remove or relocate lower-priority PoE devices, or
Add a single-port PoE injector for this device, or upgrade to a higher-budget switch
Re-check after freeing up budget

What to document for a pro

Switch model and total PoE budget
Count and class of PoE devices attached

PoE standard/class mismatch

high confidence

A source that delivers a lower PoE standard than the device requires won't bring it up.

Safe next steps

Match the source to the device's standard (af/at/bt) with a suitable switch or injector
Verify the device's required class on its spec sheet

What to document for a pro

Device PoE class / wattage requirement
Source switch/injector PoE standard

Original port or patch cord was the problem

high confidence

The device powered up on a known-good port/cable, isolating the fault to the original port or patch cord.

Safe next steps

Replace the suspect patch cord or use a different known-good PoE port
If a fixed port keeps failing, have the switch checked

Cable run too long or damaged

medium confidence

Runs beyond 100m total channel length or with a damaged/miswired pair can't reliably carry PoE.

Safe next steps

Keep total channel length within 100m
Re-terminate or replace the damaged section
Have the run certified after repair

What to document for a pro

Approximate run length
Where damage is visible
Cable category

Likely a failed device — verify or replace

medium confidence

Still dead on a known-good PoE port/cable with adequate budget and matching class points to the device itself.

Safe next steps

Test the device on another proven PoE source if possible
Check for a warranty/RMA
Confirm there's no separate hard reset needed per the device manual

What to document for a pro

Device make/model
Results of the swap tests you ran

Diagnostic guidance only. If unsure, stop and call a licensed professional — gas, electrical, and refrigerant work is hazardous to untrained users.

Pro launch updates

Get notified when Pro launches, plus a monthly code-change digest. Email only — no account required.