[Help]: Omada controller via docker doesn't autofind/adopt EAP115, while tplink's discovery utility for macos does. Banging my head!

[hellolearnr]

Controller Version

v 5.15.24.19-latest as on 12sep2025

Describe Your Issue or Question

I've installed mbentley's omada in local macbook m4 via docker desktop, however it neither auto find's omada EAP115 nor it adopts it if i manually add the device key. It is in preconfigure status .Suprisingly the same device gets auto detecs in my tplink's discovery tool for macos, but it doesn't get adopted. what's the solution pls.

note: i'm using router tplink WR850N which is connected to EAP115 via ethernet and i can connect to wifi from both router and eap. My macbook is connected to my router wifi's allthrough.Updated creds post factory reset of eap115 and changed eap's inform url to 192.168.0.108:29810.added same creds in manual device add details.

Controller Hostname/IP changed from (172.17.0.2) to (192.168.0.108) Topology: ISP → WR850 Router (192.168.0.1) =>a) EAP115 (Ethernet) => IP 192.168.0.101 b) MacBook (WiFi) => 192.168.0.108 (Docker Host)
used below to run docker-omada in terminal

docker run -d \ --name omada-controller \ -v /etc/localtime:/etc/localtime:ro \ -p 8043:8043 -p 8088:8088 -p 8843:8843 -p 8880:8880 \ -p 27001:27001/udp -p 27002:27002 \ -p 29810:29810/udp -p 29811:29811 -p 29812:29812 -p 29813:29813 -p 29814:29814 \ -e SHOW_SERVER_LOGS=true \ -v ~/omada_docker//opt/tplink/EAPController/data \ -v ~/omada_docker/work:/opt/tplink/EAPController/work \ -v ~/omada_docker/logs:/opt/tplink/EAPController/logs \ mbentley/omada-controller:latest

<

Expected Behavior

Expected controller to autofind and adopt the eap

Steps to Reproduce

1)install omada controller. on docker desktop -mac
2)Controller Hostname/IP changed from (172.17.0.2) to (192.168.0.108)
3)Topology: ISP → WR850 Router (192.168.0.1) =>a) EAP115 (Ethernet) => IP 192.168.0.101 b) MacBook (WiFi) => 192.168.0.108 (Docker Host)
4)router tplink WR850N which is connected to EAP115 via ethernet and i can able to connect to wifi from both router and eap. My macbook is connected to my router wifi's allthrough. Updated creds post factory reset of eap115 and changed eap's inform url to 192.168.0.108:29810.added same creds in manual device add details.
5)try to autofind eap115 from controller

How You're Launching the Container

# Directory structure
mkdir -p ~/omada_docker/{data,work,logs,properties}

# Docker container with correct ports
docker run -d \
  --name omada-controller \
  -v /etc/localtime:/etc/localtime:ro \
  -p 8043:8043 -p 8088:8088 -p 8843:8843 -p 8880:8880 \
  -p 27001:27001/udp -p 27002:27002 \
  -p 29810:29810/udp -p 29811:29811 -p 29812:29812 -p 29813:29813 -p 29814:29814 \
  -e SHOW_SERVER_LOGS=true \
  -v ~/omada_docker//opt/tplink/EAPController/data \
  -v ~/omada_docker/work:/opt/tplink/EAPController/work \
  -v ~/omada_docker/logs:/opt/tplink/EAPController/logs \
  mbentley/omada-controller:latest

Container Logs

09-12-2025 19:31:03.750 INFO [comm-pool-15] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 19:31:08.048 INFO [https-jsse-nio-8043-exec-13] [] c.t.s.o.m.c.k(): call cloud resp:{"errorCode":0,"result":{"status":[{"deviceMac":"3C-64-CF-90-53-14","status":0}]}}

09-12-2025 19:36:03.746 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 19:36:03.748 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 19:37:08.761 INFO [https-jsse-nio-8043-exec-9] [] c.t.s.o.m.c.k(): call cloud resp:{"errorCode":0,"result":{"status":[{"deviceMac":"3C-64-CF-90-53-14","status":0}]}}

09-12-2025 19:41:03.749 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 19:41:03.752 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 19:43:45.028 INFO [monitor-common-block-pool-10] [] c.t.s.o.m.d.c.a.a(): no msp history data found.

09-12-2025 19:46:03.747 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 19:46:03.751 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 19:51:03.748 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 19:51:03.751 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 19:56:03.749 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 19:56:03.760 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 20:00:00.017 INFO [omada_manager_ipc_detect_pool-0] [] c.t.s.o.m.h.b.a.a.g(): handle IpcDetectSchedule, partition:0

09-12-2025 20:00:00.023 INFO [omada_manager_ipc_detect_pool-0] [] c.t.s.o.m.h.b.a.a.i(): run autoIpcDetectTask, local time:2025-09-12T20:00:00.023654261Z[Etc/UTC]

09-12-2025 20:00:00.025 INFO [omada_manager_ipc_detect_pool-0] [] c.t.s.o.m.h.b.a.a.i(): autoIpcDetectTask, empty activeSiteMap! partition:0

09-12-2025 20:00:15.008 INFO [hotspot-voucher-group-traffic-statistic-pool-0] [] c.t.s.o.p.d.m.v.s.t.m(): No omadacIds when handle VoucherTrafficStatisticTaskService.

09-12-2025 20:00:15.010 INFO [hotspot-voucher-group-traffic-statistic-pool-0] [] c.t.s.o.p.p.s.t(): Handle VoucherGroupTrafficStatisticTask with shardingSize:1, shardingIndex:0, cost 2 ms

09-12-2025 20:00:31.622 INFO [scheduled-pool-2] [] c.t.s.o.c.p.c.i(): Scheduling executed, set updateOmadacCacheEnable: false

09-12-2025 20:01:03.747 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 20:01:03.749 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

09-12-2025 20:04:00.008 INFO [client-schedule-statistic-task-0] [] c.t.s.o.c.d.a.u(): [STAT] {"wiredClients":0,"statName":"ClientStatInfo","authedClients":0,"wirelessClients":0}

09-12-2025 20:06:03.746 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run

09-12-2025 20:06:03.749 INFO [comm-pool-12] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade

MongoDB Logs

No response

Additional Context

No response

[mbentley]

A few things:

• You're missing ports. Check out https://github.com/mbentley/docker-omada-controller?tab=readme-ov-file#using-port-mapping
• Have you tried to just set the inform URL to 192.168.0.108?
• Your bind mount for data is messed up. You have: -v ~/omada_docker//opt/tplink/EAPController/data \
• Made sure the EAP's firmware is up to date?
• You don't need a volume for the work directory as of 5.x
• Don't use latest. At least use the 5 tag.

Here's a basic run command with your volumes and just update the TZ variable as appropriate instead of bind mounting localtime:

docker run -d \
  --name omada-controller \
  --stop-timeout 60 \
  --restart unless-stopped \
  --ulimit nofile=4096:8192 \
  -p 8088:8088 \
  -p 8043:8043 \
  -p 8843:8843 \
  -p 19810:19810/udp \
  -p 27001:27001/udp \
  -p 29810:29810/udp \
  -p 29811-29817:29811-29817 \
  -e TZ=Etc/UTC \
  -v ~/omada_docker/data:/opt/tplink/EAPController/data \
  -v ~/omada_docker/logs:/opt/tplink/EAPController/logs \
  mbentley/omada-controller:5