@MarioRuck 

Found this:

05-07-2026 22:36:16.748 INFO [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.a.a(): receive adopt watch result of OmadacId(ad1e7c6e77b7621b07f0fda4a60f7323) DeviceMac(VPnujNKdTJVHVRgrZ3BozoMEo5EaxpQUcg4yzTD4Htc=) BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7), response:4
05-07-2026 22:36:16.748 WARN [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.a.a(): timeout wait adopt watch result of OmadacId(ad1e7c6e77b7621b07f0fda4a60f7323) DeviceMac(VPnujNKdTJVHVRgrZ3BozoMEo5EaxpQUcg4yzTD4Htc=) BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7), response:OperationResponse(errorCode=-39002, msg=Device adoption failed because the device does not respond to adopt commands., result=AdoptOneDeviceStatusResultVO(mac=34-60-F9-5D-26-6E, status=22, statusCategory=2, specificationNote=null, adoptFailType=-1, waitTime=null, retryChances=null, adoptTip=null), auditLogReturn=null, auditLogReturnList=null)
05-07-2026 22:36:16.749 WARN [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.d.RunTimeAdoptInfo(): errorMsg:null is invalid!
05-07-2026 22:36:16.750 WARN [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.a.a(): Adopt device OmadacId(ad1e7c6e77b7621b07f0fda4a60f7323) DeviceMac(VPnujNKdTJVHVRgrZ3BozoMEo5EaxpQUcg4yzTD4Htc=) Timeout, errorCode 7
05-07-2026 22:36:16.752 WARN [async-business-timeout-pool-2] [] c.t.s.o.a.b.a(): DeferredResponse of BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7) is time out, remove from timeout holder
05-07-2026 22:36:16.752 WARN [async-business-timeout-pool-2] [] c.t.s.o.a.b.a(): DeferredResponse of BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7) is time out, remove from response holder

Can anyone let me know what this means: errorCode=-39002

Thanks,

Mario

  @Vincent-TP 

Hello Vincent,

thanks for your hints.

I did update the controller and the EAP to the latest versions (6.2.10.17 and 1.3.7). Unfortunately the issue remains unchanged.

 The log shows:

 "adoption failed because the device does not respond to adopt commands"

Is there a hard change in the firmware of the EAP for access/connectivity to version 5.x? 

  @Vincent-TP

Hello Vincent,

did get the EAP adopted. But it seems there are changes in the EAP behavior. My recent configuaration is to run all EAP and also Interswitch connections based on 802.1 Q Tagging. The IP address aquisition for the VLAN has been managed via the PVID. Worked well since years.

Now the EAP seems not to receive an IP address via this setup on the expected VLAN.

I did change the VLAN for the adress aquisition on the port to untagged. Then it works. Can you please check if this is the expected behavior? I think even via a Q-tagged connection the IP address aquisition should work.

Thanks in advance,

Mario