Aqara G5 Pro PoE – one camera not receiving DHCP IP while others work normally

Hello,

I’m having an issue with one of my Aqara G5 Pro PoE cameras not receiving an IP address via DHCP, while the other cameras in the same setup work perfectly.

Setup
• 4 × Aqara G5 Pro PoE cameras
• PoE switch: TP-Link TL-SG1210MP
• Router with DHCP enabled
• All cameras connected via Ethernet PoE from the same switch

Current behavior

Out of the four cameras:
• 3 cameras receive an IP address from DHCP and work normally
• 1 camera never appears in the DHCP client list

The switch detects the device and provides power, but the camera never obtains an IP address.

Switch indicators

On the switch port used by the problematic camera:
• Green link LED is on
• Orange activity LED only blinks occasionally

On the working cameras the activity LED is constantly active.

Camera LED

The camera shows different states depending on restart/reset:
• previously blinking yellow
• after reset sometimes solid white

However, it still never appears in the DHCP table.

Troubleshooting performed

I have already tried:
• rebooting the camera
• performing multiple factory resets
• rebooting the switch
• testing with a different Ethernet cable
• confirming that DHCP works normally (other cameras receive IP addresses)
• checking the switch port configuration

The camera clearly receives PoE power and establishes link, but it never requests or receives a DHCP address.

Additional context

Since the other three cameras work normally on the same switch and network, the issue seems isolated to this single unit.

Questions
• Is there any way to discover the camera locally if it doesn’t obtain DHCP?
• Is there a default fallback IP address for the G5 Pro PoE?
• Is there any recovery procedure if the network stack fails to initialize?

Any suggestions or troubleshooting steps would be greatly appreciated.

Hello Matt,

That is a very detailed troubleshooting list you’ve already completed. Based on the behavior of the LEDs and the fact that your other three cameras work perfectly, here are a few additional steps and technical insights that might help isolate the root cause:

1. The “Cross-Check” (Port Swap)

While you mentioned checking the switch configuration, have you physically swapped the ports between the non-working camera and a working one?

Goal: If the problematic camera works on a “known good” port (where another camera was just working), the issue is the original port or cable.

2. Test with a Short Patch Cable

Since you’ve tried a different cable, was it a short one (1–2 meters)?

Reason: PoE devices can sometimes suffer from voltage drops or signal degradation on longer or lower-quality runs (like CCA cables). Testing the camera with a short, high-quality patch cable directly at the switch eliminates any hidden wiring issues that might allow for power but prevent a stable data handshake.

3. Forced Factory Reset

Ensure you are doing a full factory reset rather than just a network reset.
Press the reset button 10 times quickly in succession. This forces the camera to re-initialize its entire operating system, which is often more effective than a simple reboot if the software is hung.

4. Power via USB-C

The G5 Pro supports USB-C power. Try powering the camera via a USB-C adapter and connecting it to a non-PoE port on your router or switch. This bypasses the PoE negotiation logic entirely. If it gets an IP this way, there is a handshake compatibility issue between that specific unit and the TP-Link PoE controller.

I hope my suggestions help you.

1 Like