@HellishVictor I assume it's the same for all the cameras : https://github.com/nervous-inhuman/tplink-tapo-c200-re/issues/4#issuecomment-1030056785
But be aware I did not test it myself, and if you break your camera I can't be responsible of it ~~

  @Solla-topee 
Thanks for this answer but it is not a real answer neither a work around.

I can confirm events where objects/animals are moving in the frame and the camera stop recording did not record them, neither the motion and consider it is not necessary to record. I will try to give you an example of today's event later

A solution would be to propose a functionnality to adapt the time frame of recording after no movement registered.
A workaround would be to explain to people how to downgrade to the previous firmware version to keep the behavior they were pleased with. I understand that you have core development, but I can't accept an answer in which you explain you downgrade functionnality in order to resolve a problem on another hardware. More over you should have adjust the time frame only for people using cloud or hubs.

How can we further move on this subject and resolve what is for us an issue ? In my case I can confirm missing records of motion and too short videos which make me impossible to trace events (a vehicule stopping and then restarting, the cameras did not record it anymore). I also can confirm that this happens many times per day / hours ( tracking animal activity for example)

Waiting for your response, and wishes you nice holidays/happy new year

@Solla-topee

I appreciate you getting back to me. However, like @Takoman, I also feel this answer to the latest firmware solution isn't satisfactory. There have been occasions during since the firmware was updated last week when the camera HAS cut off when the subject was still in its focus and moving, and then missed a bit of the activity before switching itself back on again. Although it was only seconds, it is not the point, as it misses activity that could prove vital. 

I also feel the experience puts me off making further firmware updates.

I love the cameras but this interfering with the recording settings has made me downbeat.

Alf

  @Takoman Thank you very much for the link, man!

There should be an option that allow the user to set the time to record after movement detection or for downgrade easily.

  @HellishVictor you are welcome.
If you did it and you succeed, could you please tell us inform about it. I could help other people who want to recover the previous behavior in case Tapo/TP-Link do not want to make a move or help people.

I do not actually have the time to give it a try because it involves taking down cameras who were put outside, and it's actually a pain with the weather x)

one of the problem with this update is this scenario for example : before a recording, the cameras register 2 to 5 sec before the event happening. Now with the new implementation it generates micro-cuts during the recording, and the cameras are now unable to buffer this previous 3/5 seconds because during this time frame, it was already recording.

so before we had this behavior

--- represents buffer which was recording before a motion

____ represent the actual recording

so before : |---- _________________|

now: |---- __| |__| |__|

and that's the real problem. we now have missing frames which can be crucial. Moreover animals are now badly detected and it became difficult to track there movements

  @Alf-63 Sorry folks - I have now changed my opinion.

After carrying out a lot of tests between one camera with the older firmware and another camera with the new firmware, the new firmware seems to be working OK.   

As far as I can see, the only change which has been made is that, after detection stops, the continuation of recording has been reduced from 60 seconds to 10 seconds.

I actually now find that these shorter clips are much better when searching for a specific event since now there is usually only one event per clip.

For longer continuous  events, the new firmware will still record for 3:00 minutes before immediately starting a new clip, all as before.

I have found that, in most cases, the continuation between these clips is almost undetectable during playback.

One of the things that was confusing me before is related to the fact that I was using 'zone detection'.   With the new firmware, when movement went outside the

zone for more that 10 seconds, obviously, recording stopped and when movement came back into the zone, a new clip started recording.   

During playback, it appeared that some movement had been lost, when in fact, this movement was ouside the zone.   This issue was not so apparent with the older firmware.

I'm still testing stuff and will report back if I find any issues.   

cheers

  @Alf-63  

Thank you for posting your experiments.

However, I would like the old settings back before the recent firmware update, which is a backwards step. 

I do not like what the camera has become, cutting off long-range shots after 15 seconds despite the still ongoing activity that alerted it to record in the first place moving just a few feet away.

It misses what could be vital movements while the person is still actually in focus and moving. I have lost confidence in it.

My three cameras remain on maximum detection; I haven't changed a thing. This latest firmware is the problem that's changed things. It has been a  bad move, and I regret accepting it on two of my cameras. 

Luckily, after finding the problems with the update, I did not accept it on the third camera and kept the old firmware, and it still records everything as before.

Rest assured, I will not be updating this new firmware on that one.