@Hank21 

Are you using a camera from a manufacturer other than VIGI? Could you please tell me the model?

VIGI C540W

 

Could you please tell me the network topology?

 

 

 

Have you checked the connection between the camera and the EAP610 ("Lock to AP")?

Lock to AP is not working.

 

Please check if the camera only supports 2.4 GHz and place it closer to the EAP, as the signal seems to be weak.

The EAP is located 10 meters from the camera. The signal cannot be too weak there.

 

If the problem persists, please contact local support and provide the forum ID. Sincerely!

TP-Link should also be working on the support, but thanks for the heads-up.

 

 

 

The stupid camera locks itself out of the system after a restart.

The camera is paired with the EAP610, but after a restart, it connects to an EAP115 Wall, which is simply too far away for a stable connection, and therefore goes offline.

This is a glaring system failure that TP-Link either doesn't want to fix or can't fix. The third-party Instar camera connects to the EAP610 without any problems after a restart.

 

 

The classic statement, "You're using a device from a third-party manufacturer, so we can't help you," doesn't apply in this case. Unfortunately, there's still no help available.

I had already clearly explained the Wi-Fi behavior and its consequences to support. So what?

 

 

 

 

  @Hank21 

Hello,

thanks for the links.

All access points always have the latest firmware. I update regularly because I always hope that something will finally improve. I'm now certain that it's a fundamental problem that TP-Link can't or won't change. This is already evident from the fact that a VIGI camera can't connect to its assigned access point. IP addresses are assigned to Wi-Fi clients over long distances, even though the signal strength doesn't allow for a stable connection and there are access points with stronger signals nearby. TP-Link seems unable to handle the entire process in a segmented network with multiple access points. The router also seems to be contributing to these shortcomings.

If the problem were solvable, a support employee would solve it.

  @Vincent-TP 

 

 

Hi Vincent, thank you for your feedback.

Yes, the EAP610 also transmits on 2.4 GHz.

 

The internal system problems are characterized by the fact that binding a client (C540) to the EAP 610 doesn't work if the products are from TP-Link (Omada-Vigi).

My Instar camera always connects to the assigned access point (Omada-Instar).

It's also not due to a possible defect in a C540, as a second one behaves exactly the same way.

Furthermore:

I'm now convinced that TP-Link can't manage a multi-AP environment where each access point broadcasts the same SSID. I don't understand why this is the case, but practical experience confirms it. I tested this again today because I was having problems with a wired Zigbee hub, and its system check diagnosed an unstable/missing internet connection for its clients.

 

The problem is even more apparent with my phone.

It's assigned an IP address from the allocated VLAN, but it can't access the internet. See screenshots.

 

 

 

 

I removed this access point (EAP115Wall) from the Wi-Fi group as a test.

Then I created a new group specifically for this access point

 

and a separate SSID for it.

 

Both the mobile phone and the Zigbee hub were able to access the internet without any problems.

I've always shied away from the effort, but I'm now going to create a separate group for each access point and assign each one its own SSID. Luckily, Omada can manage at least the number of groups I need, at least in theory.

I hope this will solve the connection problems.

I had hoped the manufacturer would address this. But that was in vain.

 

FYI:

A new problem has arisen.

I can no longer reach all devices on the network via the Omada app. This affects both switches and access points.

However, all devices are accessible via the cloud.

 

 

 

The connection problems are obviously not related to the phone. The error message makes no sense.

 

Omada Controller:

Currently, my controllers indicate every time I access them that an update is available, but it cannot be successfully installed. The hotline's strange response—that the updates haven't been rolled out yet—is quite surprising.

I would have expected an apology for the inconvenience and an immediate fix for the error of offering updates for installation even before they've been rolled out.

OMADA is an online management system.

Support should be able to help immediately.

But apparently, they can't.

 

Despite everything, Happy Easter!