Maddem wrote

  @Wayne-TP Thank you for the reply, in the end I got a 1TB drive and it lasts about 6–7 days of continuous recording.

However, now I have a serious problem. I bought these cameras and the hub because I find the line-crossing event feature excellent, and today I realized that if a camera is connected to the H500, the line crossing doesn’t work, while without the hub it works.

I don’t know what to do. I can’t tell if this is intentional or a bug. Because if it doesn’t work, all this equipment I received is useless to me.

  @Maddem 

Which connection are you referring to? Is it that line‑crossing detection doesn’t work when the storage path is set to the hub, but does work when storage is set to the microSD card installed in the camera?

Also, is the detection completely disabled, or does it simply not trigger? Is this something you can consistently reproduce?

Maddem wrote

  @Wayne-TP 

Yes, line crossing does not work when the camera is connected to the H500 hub. However, when it is disconnected from the hub, it works.

Yes, I can reproduce this issue. I also sent an email to support.it@tp-link.com, but I have not received a reply yet.

I ran further tests and came to the conclusion that when the camera is connected to the hub but the storage is not set to the hub, line crossing works.

I do not have a microSD card available at the moment, but I set the storage to the device.

However, should line crossing work when storage on the hub is enabled?

  @Maddem 

Line crossing detection should work regardless of the video storage location, at least, I’m not aware of any dependency between storage location and this feature.

Keep us posted if there is any update on your case!

Maddem wrote

  @Wayne-TP 

Today I woke up to a nice surprise! New update! yeeeee!

I’m testing everything and, for now, it seems to be working well. I’ll keep you updated while monitoring the hub and the C560WS cameras.

The only thing I’d like to understand is this: when I used line crossing with the C520WS, the line crossing detection interval was shorter than on the C560WS, which seems to be around one minute. I’m wondering whether there is a setting for this or not, because I’ve been looking for it but I can’t find it.

  @Maddem 

I wasn’t aware that the trigger logic for this feature might vary across models. Does this difference occur consistently on your devices? Specifically, is the re‑trigger interval for line‑crossing detection always about one minute on C560WS, while C520WS has shorter intervals (and have you timed the difference)?