I have an on-prem omada controller v 5.8.4. I have a large amount of ER605's that stay connected to the controller without issue, but I have about 20% that keep looping. They connect for a second and then get stuck in a configuring loop before finally disconnecting after a few weeks.

Checking the logs on my controller I find the following messages over and over for the devices, (error messages are bolded) (I removed the Omada ID, Site ID, and Device MAC address and changed the number the hexadecimal after TransResult for security.) (Had to remove @ after TransResult for it to let me post) Has anyone else encountered this or this error message? All my devices have the same config, so I am not sure why a chunk of them have this issue when everything is the same.

05-02-2023 11:51:11.621 INFO [server-comm-pool-2] [] c.t.s.o.m.d.d.m.i.a(): got first inform of OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS)
05-02-2023 11:51:11.623 INFO [manage-work-group-11] [] c.t.s.o.m.d.d.m.i.e(): first inform send full config to OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS)
05-02-2023 11:56:41.187 WARN [manage-work-group-0] [] c.t.s.o.m.d.p.t.h.a(): send set request to OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS) fail, com.tplink.smb.ecsp.common.TransResult5d711227[errCode=2600,msg=ERR_DEVICE_SEND_TCP_TIMEOUT,result=<null>,addressDTO=<null>]
05-02-2023 12:01:11.669 WARN [manage-work-group-1] [] c.t.s.o.m.d.p.t.h.a(): send set request to OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS) fail, com.tplink.smb.ecsp.common.TransResult44b2a657[errCode=2600,msg=ERR_DEVICE_SEND_TCP_TIMEOUT,result=<null>,addressDTO=<null>]
05-02-2023 12:01:11.670 INFO [manage-work-group-1] [] c.t.s.o.m.d.d.m.d.b.A(): syncFullConfiguration to OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS) rebuild[false], result:SendDeviceMsgResult(success=false, deviceResponse=null)
05-02-2023 12:01:16.946 INFO [server-comm-pool-3] [] c.t.s.e.s.c.h.EcspV2DeviceContextHelper(): device of status CONNECTED time out for DUMMY MAC ADDRESS
05-02-2023 12:01:16.946 INFO [manage-work-group-4] [] c.t.s.o.m.d.p.t.c(): Device: <DUMMY MAC ADDRESS DUMMMY OMADA ID> is Disconnected.
05-02-2023 12:01:16.946 INFO [tcp-message-executor-17-1] [] c.t.s.e.s.c.c(): device context is null, can not subject CONNECTED_ERROR for device DUMMY MAC ADDRESS
05-02-2023 12:10:49.037 INFO [discovery-work-group-0] [] c.t.s.o.m.d.d.m.c.a(): MANAGED_BY_OWN Device DUMMY MAC ADDRESS on omadac DUMMMY OMADA ID is discoveried.
05-02-2023 12:11:01.231 INFO [adopt-work-group-3] [] c.t.s.o.m.d.d.m.d.b.c(): Gateway OmadacId(DUMMMY OMADA ID) SiteId(DUMMY SITE ID) DeviceMac(DUMMY MAC ADDRESS) adopt[auto=true] ok
05-02-2023 12:11:01.250 INFO [adopt-work-group-3] [] c.t.s.o.m.d.d.m.a.c(): send mini setting to OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS)
05-02-2023 12:11:08.873 INFO [manage-work-group-2] [] c.t.s.o.m.d.p.t.c(): Device DUMMY MAC ADDRESS OmadacId(DUMMMY OMADA ID) changed to status CONNECTED, which don't need to handle.
05-02-2023 12:11:12.604 INFO [server-comm-pool-0] [] c.t.s.o.m.d.d.m.i.a(): got first inform of OmadacId(DUMMMY OMADA ID) DeviceMac(DUMMY MAC ADDRESS)