[Help]: username is marked non-null but is null

[kingp0dd]

Controller Version

5.15.24.19

Describe the Bug

omada-controller  | 08-08-2025 21:20:39.604 ERROR [adopt-work-group-1] [] c.t.s.o.m.d.d.m.a.e(): handle adopt device event failed, omadacId: OmadacId(6e163f646d5a3aa9ebbf8849aee6ff17), siteId:SiteId(6895e9ef1aabd742668b0c38), mac:NDfQoXubGdDGfl/wR+GWsiWZ/A4yr6bgfg05jdXRBS0=
omada-controller  | java.lang.NullPointerException: username is marked non-null but is null
omada-controller  | 	at com.tplink.smb.omada.manager.configuration.domain.model.site.component.a.a.a$a.a(SourceFile:27) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.port.mongo.configuration.site.component.common.h.a(SourceFile:32) ~[manager-port-mongo-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.port.mongo.configuration.site.component.common.d.a(SourceFile:81) ~[manager-port-mongo-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at java.base/java.util.Optional.map(Optional.java:260) ~[?:?]
omada-controller  | 	at com.tplink.smb.omada.manager.port.mongo.configuration.site.component.common.c.a(SourceFile:60) ~[manager-port-mongo-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.configuration.domain.model.site.component.a.h.a(SourceFile:30) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:431) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:347) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:262) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.b(SourceFile:219) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:159) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:91) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.a(SourceFile:294) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.b(SourceFile:179) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.c(SourceFile:120) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.component.lock.api.AbstractReadWriteLockService.doWithTryLockWrite(AbstractReadWriteLockService.java:116) ~[solution-components-lock-api-1.3.8.jar:1.3.8]
omada-controller  | 	at com.tplink.smb.omada.manager.common.c.a.a(SourceFile:101) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.a(SourceFile:117) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.component.lock.api.AbstractReadWriteLockService.doWithTryLockRead(AbstractReadWriteLockService.java:68) ~[solution-components-lock-api-1.3.8.jar:1.3.8]
omada-controller  | 	at com.tplink.smb.omada.lock.a.c.a(SourceFile:53) ~[omada-lock-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.lock.a.c.a(SourceFile:71) ~[omada-lock-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.a(SourceFile:114) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.a.l.a(SourceFile:106) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.eventcenter.domain.DefaultDomainEventBus.tryHandle(DefaultDomainEventBus.java:222) ~[eventcenter.domain-1.5.0.jar:1.5.0]
omada-controller  | 	at com.tplink.smb.eventcenter.domain.DefaultDomainEventBus.lambda$callSubscribersAsync$2(DefaultDomainEventBus.java:189) ~[eventcenter.domain-1.5.0.jar:1.5.0]
omada-controller  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
omada-controller  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]

my mongo db got corrupted, so i restored off a fresh container. now i can't adopt my eap which was working before

Expected Behavior

Should adopt as before

Steps to Reproduce

Reset EAP
Adopt

How You're Launching the Container

omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:latest
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    ports:
      - 8043:8043
      - 8843:8843
      - 27001:27001
      - 29811:29811
      - 29812:29812
      - 29813:29813
      - 29814:29814
      - 29810:29810/udp
      - 29815:29815
      - 29816:29816
    environment:
      - PUID=508
      - PGID=508
      - ROOTLESS=false
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - PORT_APP_DISCOVERY=27001
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V1=29811
      - PORT_MANAGER_V2=29814
      - PORT_DISCOVERY=29810
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Asia/Manila
      # - EAP_MONGOD_URI=mongodb://127.0.0.1:27218/omada
      # - EAP_MONGOD_PORT=27218
    volumes:
      - ./omada/data:/opt/tplink/EAPController/data
      - ./omada/logs:/opt/tplink/EAPController/logs

Container Logs

omada-controller  | 08-08-2025 21:20:39.604 ERROR [adopt-work-group-1] [] c.t.s.o.m.d.d.m.a.e(): handle adopt device event failed, omadacId: OmadacId(6e163f646d5a3aa9ebbf8849aee6ff17), siteId:SiteId(6895e9ef1aabd742668b0c38), mac:NDfQoXubGdDGfl/wR+GWsiWZ/A4yr6bgfg05jdXRBS0=
omada-controller  | java.lang.NullPointerException: username is marked non-null but is null
omada-controller  | 	at com.tplink.smb.omada.manager.configuration.domain.model.site.component.a.a.a$a.a(SourceFile:27) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.port.mongo.configuration.site.component.common.h.a(SourceFile:32) ~[manager-port-mongo-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.port.mongo.configuration.site.component.common.d.a(SourceFile:81) ~[manager-port-mongo-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at java.base/java.util.Optional.map(Optional.java:260) ~[?:?]
omada-controller  | 	at com.tplink.smb.omada.manager.port.mongo.configuration.site.component.common.c.a(SourceFile:60) ~[manager-port-mongo-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.configuration.domain.model.site.component.a.h.a(SourceFile:30) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:431) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:347) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:262) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.b(SourceFile:219) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:159) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.device.ap.ac.a(SourceFile:91) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.a(SourceFile:294) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.b(SourceFile:179) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.c(SourceFile:120) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.component.lock.api.AbstractReadWriteLockService.doWithTryLockWrite(AbstractReadWriteLockService.java:116) ~[solution-components-lock-api-1.3.8.jar:1.3.8]
omada-controller  | 	at com.tplink.smb.omada.manager.common.c.a.a(SourceFile:101) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.a(SourceFile:117) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.component.lock.api.AbstractReadWriteLockService.doWithTryLockRead(AbstractReadWriteLockService.java:68) ~[solution-components-lock-api-1.3.8.jar:1.3.8]
omada-controller  | 	at com.tplink.smb.omada.lock.a.c.a(SourceFile:53) ~[omada-lock-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.lock.a.c.a(SourceFile:71) ~[omada-lock-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.e.a(SourceFile:114) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.omada.manager.device.domain.model.adopt.a.l.a(SourceFile:106) ~[manager-core-5.15.24.19.jar:5.15.24.19]
omada-controller  | 	at com.tplink.smb.eventcenter.domain.DefaultDomainEventBus.tryHandle(DefaultDomainEventBus.java:222) ~[eventcenter.domain-1.5.0.jar:1.5.0]
omada-controller  | 	at com.tplink.smb.eventcenter.domain.DefaultDomainEventBus.lambda$callSubscribersAsync$2(DefaultDomainEventBus.java:189) ~[eventcenter.domain-1.5.0.jar:1.5.0]
omada-controller  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
omada-controller  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]

MongoDB Logs

Additional Context

No response

[mbentley]

This doesn't look like an issue with the containerization of the software so I converted this to a discussion. Did you try to reset the EAP back to factory settings again before attempting to adopt it?

[kingp0dd]

Yes i tried to reset it twice already. What i tried so far is

Remove /data of container to reset db

Set capwap to IP of controller

Reset EAP to default, set a new password, change VLAN to 99, set controller
URL to ip of controller, change admin password

Adopt in controller

Adopt fail, retry

Input the new admin password

EAP goes to Adopting then Provisioning state

Adopt fails

Then i get the logs in first post

What's weird here is the same EAP successfully Adopted and has state Connected in the omada controller docker container before my mongo db got corrupted. I restored from a working config backup then did the steps above to try to reconnect this previosuly-working EAP

[kingp0dd]

an update on this, which might help others that might get into this in the future

when mongo db got corrupted, i only deleted the mounted /data dir of the container.
i tried to remove all the persisted data (whole omada mounted volume) and started from scratch, now the EAP adopted successfully with no errors i encountered previosuly in the logs

[mbentley]

Strange but glad it's working again for you.