@Pavel-T They gave me c260 to replace c225v2. I'm not using autotracking and cameras were cheap so I stopped bothering now hah. But be ready that it won't be fixed for your camera, due to hardware limitations.

  @Solla-topee 

It makes absolutely no difference whether the camera is recording to a local card or to the cloud, or whether local recording is turned off or there isn’t a card in it at all. When tracking is enabled, it drops frames. The problem persists. Imagine a bike with handlebars, but you can only ride it straight ahead on flat ground—you can’t turn, go downhill, or uphill because you’ll tip over, crash into a tree, or lose air from the inner tube. That’s the kind of problem it is.... This camera is like that bike—don’t ask me if it has a water bottle holder.

Solla-topee wrote

  @Stuy 

Hi,
Please double-check if your outdoor cameras are powered by the original power adapter and cable that came with the cameras in the package. If not, please power the cameras with the original power adapter and cord, then check whether they work properly.
Best Regards

c530ws  1.3.3 Build 250923 Rel.51794n

I’m experiencing the exact same issue with the C530WS. In fact, I’ve purchased three separate units, and every single one of them behaves this way. Even when tested in completely different environments and locations, the problem persists. It’s baffling that this product has been on the market for quite some time now, yet such a fundamental issue still remains.

  @Solla-topee @u17 

This is a very serious issue that needs to be addressed by TP-Link engineers, designers, and perhaps software developers. As you can see, the problem is broader and doesn’t just affect me; it likely requires a complete redesign and re-engineering of the approach to this issue at its source. I have a second camera that I received from TP-Link—the exact same model. I’ve now installed the recommended cards in both, which are supposedly tested, compatible, and even recommended for Tapo cameras, but not much has changed. I can only add that I’ve noticed that after a long period of inactivity (zero motion), when an event is detected and tracking starts, the cameras freeze frames and the image jumps (the moving object is already, for example, a meter further away) right at the beginning. They simply lack memory, and the processor can’t keep up. Maybe the software that strains resources at the start of the process needs improvement? This is crucial and critical—if someone buys such a camera to detect sudden events, like an intrusion into a monitored area, the camera is useless. So the issue is well-known; in my opinion, there’s no point in repeating the same thing a hundred times in a new thread. 

Solla-topee wrote

  @u17 

Hi,
Different camera models may show similar symptoms while having different root causes. For the phenomenon you reported, it's recommended to start a new thread here to follow up on it. In the new thread, please describe the phenomenon you are experiencing in detail and list the troubleshooting steps you've already taken so we can provide further assistance.
Best Regards