TL-WPA8730KIT issues

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-WPA8730KIT issues

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WPA8730KIT issues
TL-WPA8730KIT issues
2018-07-03 18:11:26
Model :

Hardware Version :

Firmware Version :

ISP :

Hello. I have just installed a TL-WPA8730KIT and have some issues I would like some help with.

1. The units have been installed on a 3-phase infrastructure, and the remote unit is installed on a power strip. I am aware of the issues that may arise, however I notice that the 'Home' LED sometimes goes red and then back to green. Speed is very low but I am not concerned with it right now as there are going to be some electrical improvements during the week. My question is, what is the meaning of the LED going red at regular intervals.

2. I notice that there is a potential bug in the web interface. Under no circumstances was I able to set a static IP. The unit accepts it, and after a few seconds it reverts to a random IP at 10.1.1.0/24 subnet. A DHCP server is present at 192.168.1.0/24. Same behaviour occurs if I choose the IP to be dynamic. It gets an IP from the DHCP and after a few seconds reverts back to something like 10.1.1.23 or similar. No other DHCP is present, and no 10.1.1.0 subnet is present.

I would appreciate some guidance.
Thank you
  0      
  0      
#1
Options
2 Reply
Re:TL-WPA8730KIT issues
2018-07-05 11:07:39
If the LED goes red, it means powerline network is in poor condition. It's recommendtrying another wall socket.

Why do you need to set static IP on the powerline device?

The powerline devices has no DHCP function and it will obtain ip address from main router.

Where did you see the 10.1.1.X network?

Generally speaking, there is no need to set any static IP address on powerline units also.
  0  
  0  
#2
Options
Re:TL-WPA8730KIT issues
2018-07-05 16:55:53
Thank you for your response.
I am talking about the management interface. Since my initial post I double-checked it. It definitely does not work as expected. Same behaviour.

To illustrate:

Main router subnet: 192.168.1.0/24
DHCP range (main router): 192.168.1.70 - 192.168.1.90
No other DHCP servers running

TP-link management interface:

Set static IP -> 192.168.1.240
Works for 3 seconds, then changes to 10.1.1.73

Obtain IP from DHCP:
Gets IP 192.168.1.71
Works for 3 seconds, then changes to 10.1.1.22

Set static IP -> 10.1.1.22 or 10.1.1.73
Works for 3 seconds, then changes to 10.1.1.54

and so on.
  0  
  0  
#3
Options