ES216G wired clients not displaying IP addresses in Omada controller — what's the mechanism?
I'm troubleshooting an issue with my Omada setup where most wired clients on an ES216G show CONNECTED status but have blank IP addresses in the controller UI. I'd like to understand whether this is expected behavior or a defect.
Setup:
- Omada Software Controller 6.2.14.11 (self-hosted)
- ER605 v2.2 (fw 2.4.5) + ES216G (fw 1.0.1) + ES206GP
- DHCP pool: 192.168.1.2–.99
Displays IP correctly:
- Wireless clients on EAP225 (connected to ES216G)
- All wired clients on ES206GP
- VIGI NVR at .200 (static, outside pool, no reservation)
Blank IP (–):
- pve1–3 at .101–103 (static, Debian Linux, have default gateway, continuous outbound traffic)
- 7 VIGI cameras at .201–207 (static)
- NGTeco TC2 access controller (static)
All devices are reachable and functioning normally — ARP scan confirms they're all on 192.168.1.0/24. Rolled back ES216G firmware 1.0.0, no change. Enabled ARP Detection, no change.
TP-Link support's explanation: Device discovery mechanisms (ONVIF, etc.). "Easy Managed switches rely on device discovery to obtain and display IP addresses. Devices that support these protocols display correctly; others may not."
The issue with that explanation: Wireless clients (phones, laptops) don't support ONVIF and display fine. Linux servers with a default gateway and continuous traffic don't display. The inconsistency makes me think there's something else going on.
Has anyone else seen this? If so, how'd you resolve it? And does anyone know the actual mechanism the controller uses to populate the wired client IP field - ARP table, DHCP leases, switch-observed traffic, or protocol discovery?
Thanks