Omada SDN with EAP225 not assigning IPs to TP-Link Kasa Devices
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have an EAP225 that was working fine, until one night on a routine reboot it would not reconnect/re-adopt into the OC200. The network router is a TL-R605 - This is also the DHCP. I forgot the EAP225 in the system and then re-adopted the EAP225.
Since I readopted the EAP225 it allows my Kasa switches and my garage door opener (GDO) to attach but the Kasa devices and GDO device are not assigned IP addresses by the DHCP. I have tried both reservations and no reservations. I have tried to have them reconnect. I have reset them. Nothing seems to work. The Kasa devices are different models. (HS200, HS210, HS220). It is infuriating, because one HS200 connects and gets an IP address without any issue.
I think this is an Omada Controller issue. If you look at the Host Name in the list it is changed, but when you look at the client details there is a "--" where the host name is shown for other devices. The controller (OC200) is on version 4.3.5
My laptops connect to the same AP and get a DHCP assigned IP address without issue along with the one HS200. Does anyone have ideas what might be going on?
