EAP620HD goes from Adopting to Connected to Adopting
I'm on Omada Controller 5.15.24.19 and my EAP is stuck on Adopting.
It's able to get from Adopting -> Provisioning -> Configuring -> Connected but then it goes back to Adopting state again after a few seconds and then it resets to IP 192.168.0.254 again.
[Click and drag to move]
The Site settings (SSID, etc.) are correctly applied but it's not connected to the Omada Controller so I don't have other featuers such sa Fast Roaming and mDNS rebroadcast.
Here's the logs from OmadaC:
I've tried multiple things already:
- Reset device
- Use same VLAN as controller
- Revert back to old firmware
- Tried firmwares 1.2.6, 1.3.6, 1.4.3
- Reset omada controller
One thing I noticed odd is my firmware region is now US. Maybe omada controller auto updated the firmware. I'm from PH, and from the support page, I see that the firmware region is EU. I tried to flash the latest EU firmware from the support page, and it got installed successfully. In status page of EAP, it shows the correct model number but the region is still US. I have 3 EAP620HDs that have the same issue. I have 1 though that is still connected to the controller, it's firmware is:
Model
EAP620 HD(US) v3.0
Firmware Version
1.3.6 Build 20250228 Rel. 67519
I don't know what's different with that EAP. I tried flashing that firmware version on the others but they still can''t stay Connected to the controller.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Vincent-TP wrote
Hi @kingp0
May I ask what type of VLAN you have configured? Are the different VLANs each on separate subnets, or is this a Layer 2 VLAN configuration?
Please share the config page of the VLAN you configured.
Also, please share a screenshot of the Device page of the controller, so that we can know the model number and firmware version of the devices you are using.
Regarding the management VLAN, do you have this requirement?
How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)
the VLAN is on the same subnet .99
I was trying other configs yesterday and suddenly it worked. This is what worked:
- in switch, i set PVID to 99 (before it was set to default 1)
- reason why i set it to 1 is so untagged won't get 99 by default
- since EAP should send tagged 99 (through Management VLAN), it shouldn't need a PVID
Now my theory is after Configuration from OC, the Management VLAN setting gets reset, so it can't get IP in VLAN 99 anymore.
- Copy Link
- Report Inappropriate Content
Here's the omada controller logs :
omada-controller | 09-09-2025 18:05:47.000 INFO [discovery-work-group-0] [] c.t.s.o.m.d.d.m.e.a(): auto forget factory device OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) 68aad57cbd0a5e55adebb802 DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=)
omada-controller | 09-09-2025 18:05:47.001 INFO [discovery-work-group-0] [] c.t.s.o.m.d.d.m.e.a(): NO_MANAGED Device 60-83-E7-83-54-44 on omadac cdcaaa0d9279ce1a54e481cfc8a124ff is discovered.
omada-controller | 09-09-2025 18:07:56.068 INFO [server-comm-pool-3] [] c.t.s.e.s.c.h.EcspV2DeviceContextHelper(): pending device 60-83-E7-83-54-44 time out, remove device context
omada-controller | 09-09-2025 18:07:58.905 INFO [device-timeout-workgroup-3] [] c.t.s.o.m.d.d.m.j.b(): timeoutWiredPending, OmadacId OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) Device DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=).
omada-controller | 09-09-2025 18:08:55.403 INFO [discovery-work-group-1] [] c.t.s.o.m.d.d.m.e.a(): NO_MANAGED Device 60-83-E7-83-54-44 on omadac cdcaaa0d9279ce1a54e481cfc8a124ff is discovered.
omada-controller | 09-09-2025 18:09:45.213 INFO [comm-pool-14] [] c.t.s.o.m.d.a.u.f.d(): Target firmware check task run
omada-controller | 09-09-2025 18:09:45.213 INFO [comm-pool-14] [] c.t.s.o.m.d.a.u.f.d(): no omadac need handle target firmware upgrade
omada-controller | 09-09-2025 18:10:47.352 WARN [ htp_s-jsse-nio-8043-exec-5] [] c.t.s.o.m.d.d.m.s.i(): OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) device host not enable
omada-controller | 09-09-2025 18:10:47.352 WARN [ htp_s-jsse-nio-8043-exec-5] [] c.t.s.o.m.c.a.a.e(): omadac OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) not exist, can't get device host
omada-controller | 09-09-2025 18:12:47.625 INFO [netty-tcp-server-worker-17-3] [] c.t.s.e.s.a.b.c(): valid device_verify auth for 60-83-E7-83-54-44 failed, adopt info is wrong!
omada-controller | 09-09-2025 18:12:47.627 WARN [adopt-work-group-4] [] c.t.s.o.m.d.d.m.a.a(): Adopt device OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=) failed, errorCode 5
omada-controller | 09-09-2025 18:13:07.977 INFO [adopt-work-group-1] [] c.t.s.o.m.d.d.m.a.a(): start watching full adopt result of omadacId:OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) mac:DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=), businessId:BusinessId(topic=smb_omada_business_b33521b7-169c-4bb5-88e7-2509c6831e3b, id=a4f93a6c-9dec-485e-a5de-54d3e2589415)
omada-controller | 09-09-2025 18:13:07.992 INFO [adopt-work-group-0] [] c.t.s.o.m.d.d.m.d.a.ac(): Ap OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) SiteId(68aad57cbd0a5e55adebb802) DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=) adopt[auto=true] ok
omada-controller | 09-09-2025 18:13:07.997 INFO [manage-work-group-8] [] c.t.s.o.m.d.a.u.f.b.c(): receive adopt success event for TargetFirmwareOnDeviceAdoptSuccessSubscriber: TargetFirmwareEvent(super=AbstractDomainEvent(id=eb9f108ca3294082851f53b13995c952, createTime=Tue Sep 09 18:13:07 PST 2025, type=null), omadacId=OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff), siteId=SiteId(68aad57cbd0a5e55adebb802), deviceMac=DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=), compoundModel=EAP620 HD(US) v3.0, version=1.2.6, timeStamp=1757412787997)
omada-controller | 09-09-2025 18:13:07.997 INFO [adopt-work-group-0] [] c.t.s.o.m.d.d.m.a.e(): send mini setting to OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=)
omada-controller | 09-09-2025 18:13:12.596 INFO [manage-work-group-10] [] c.t.s.o.m.d.p.t.b(): [stat] {"device":"xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=","omadacId":"OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff)","status":"CONNECTED"}
omada-controller | 09-09-2025 18:13:12.596 INFO [manage-work-group-10] [] c.t.s.o.m.d.p.t.b(): Device xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0= OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) changed to status CONNECTED, which don't need to handle.
omada-controller | 09-09-2025 18:13:12.607 INFO [gateway-dev-inform-pool-1] [] c.t.s.o.m.d.d.m.i.a(): got first inform of OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=)
omada-controller | 09-09-2025 18:13:12.619 INFO [manage-work-group-11] [] c.t.s.o.m.d.d.m.i.i(): first inform send full config to OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=)
omada-controller | 09-09-2025 18:13:12.671 INFO [manage-work-group-11] [] c.t.s.o.m.d.d.m.d.d(): add configuring set request seq id, mac DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=), seqId 2
omada-controller | 09-09-2025 18:13:12.706 INFO [setMsgThreadPool-5] [] c.t.s.o.m.d.d.m.c.du(): need clearConfigHistory when send full config, remove all component for omadac OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) site SiteId(68aad57cbd0a5e55adebb802) device DeviceMac(xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=)
omada-controller | 09-09-2025 18:14:13.676 INFO [manage-work-group-13] [] c.t.s.o.m.d.p.t.b(): [stat] {"device":"xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0=","omadacId":"OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff)","status":"CONNECTED_ERROR"}
omada-controller | 09-09-2025 18:14:13.677 INFO [manage-work-group-13] [] c.t.s.o.m.d.p.t.b(): Device xKEEVnTMeIKspYZQRdG2bRGHjsP+nign+njsjq0Mid0= OmadacId(cdcaaa0d9279ce1a54e481cfc8a124ff) changed to status CONNECTED_ERROR, which don't need to handle.
omada-controller | 09-09-2025 18:14:13.677 INFO [discovery-work-group-1] [] c.t.s.o.m.d.d.m.e.a(): MANAGED_BY_OWN Device 60-83-E7-83-54-44 on omadac cdcaaa0d9279ce1a54e481cfc8a124ff is discovered.
- Copy Link
- Report Inappropriate Content
additional info:
my OC and EAP are on VLAN 99. These are what I do when adopting:
- reset EAP
- set inform URL to the IP of my OC
- change Management VLAN to 99
Now the OC can see the EAP and it can adopt it successfully.
- EAP gets to Adopting > Provisioning > Configuring > Connected
- But then after a few seconds, it goes back to > Adopting
- then it gets an IP of 192.168.0.254
I'm starting to think that this has got to do with VLAN. Do i need to set somewhere in OC something for VLAN 99?
BTW, I tried to Adopt the same EAP in a test VM with no VLAN, and it gets to Connected with no issues and did not go back to Adopting.
- Copy Link
- Report Inappropriate Content
Hi @kingp0
Thanks for posting here.
It appears your controller configuration is preventing the EAP from obtaining a valid IP from your router, causing it to default to a fallback IP after connected.
This is most likely due to your configuration, mainly the VLAN config or the firewall.
What's the model number of the router you are using? Is it TP-Link?
To find out the reason, please share the following info:
1. The complete topology of your network.
2. The VLAN config of the controller;
3. A screenshot of the Device page
- Copy Link
- Report Inappropriate Content
kingp0 wrote
additional info:
my OC and EAP are on VLAN 99. These are what I do when adopting:
- reset EAP
- set inform URL to the IP of my OC
- change Management VLAN to 99
Now the OC can see the EAP and it can adopt it successfully.
- EAP gets to Adopting > Provisioning > Configuring > Connected
- But then after a few seconds, it goes back to > Adopting
- then it gets an IP of 192.168.0.254
>>>> What will happen after this? Will the EAP turn to Disconnected?
I'm starting to think that this has got to do with VLAN. Do i need to set somewhere in OC something for VLAN 99?
BTW, I tried to Adopt the same EAP in a test VM with no VLAN, and it gets to Connected with no issues and did not go back to Adopting.
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
kingp0 wrote
additional info:
my OC and EAP are on VLAN 99. These are what I do when adopting:
- reset EAP
- set inform URL to the IP of my OC
- change Management VLAN to 99
Now the OC can see the EAP and it can adopt it successfully.
- EAP gets to Adopting > Provisioning > Configuring > Connected
- But then after a few seconds, it goes back to > Adopting
- then it gets an IP of 192.168.0.254
>>>> What will happen after this? Will the EAP turn to Disconnected?
I'm starting to think that this has got to do with VLAN. Do i need to set somewhere in OC something for VLAN 99?
BTW, I tried to Adopt the same EAP in a test VM with no VLAN, and it gets to Connected with no issues and did not go back to Adopting.
wow thanks for the quick response.
What happens after that is it just stay at "Adopting" state. The EAP works normally, the configuration settings (SSID, etc.) are applied to it. However, it's not "Connected" to the OC, hence no other features such as mDNS broadcast or Fast Roaming (I'm assuming the EAP needs to be in Connected state for those to work).
The router is mikrotik but the switch is tplink.
OC: port untagged VLAN 99
EAP: port tagged VLAN 99, 10, 20
if I connect a PC on EAP's port (just to test), I get an IP in VLAN 99 and can ping the OC with no issues.
I don't know if this is incorrect: after i reset the EAP, should I change the Management VLAN to 99? Or that's unnecessary?
- Copy Link
- Report Inappropriate Content
Hi @kingp0
May I ask what type of VLAN you have configured? Are the different VLANs each on separate subnets, or is this a Layer 2 VLAN configuration?
Please share the config page of the VLAN you configured.
Also, please share a screenshot of the Device page of the controller, so that we can know the model number and firmware version of the devices you are using.
Regarding the management VLAN, do you have this requirement?
How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
Hi @kingp0
May I ask what type of VLAN you have configured? Are the different VLANs each on separate subnets, or is this a Layer 2 VLAN configuration?
Please share the config page of the VLAN you configured.
Also, please share a screenshot of the Device page of the controller, so that we can know the model number and firmware version of the devices you are using.
Regarding the management VLAN, do you have this requirement?
How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)
the VLAN is on the same subnet .99
I was trying other configs yesterday and suddenly it worked. This is what worked:
- in switch, i set PVID to 99 (before it was set to default 1)
- reason why i set it to 1 is so untagged won't get 99 by default
- since EAP should send tagged 99 (through Management VLAN), it shouldn't need a PVID
Now my theory is after Configuration from OC, the Management VLAN setting gets reset, so it can't get IP in VLAN 99 anymore.
- Copy Link
- Report Inappropriate Content
Hi @kingp0
Glad to hear that you finally found a solution.
The switch that EAP is plugged to is not an SDN switch, right?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 141
Replies: 8
Voters 1