@Wayne-TP 

 

Sorry, but the stops written there are not the solution to the problem for me. There is still no recording. I have followed the steps but the problem is still there.

  @TapoD230 I had a similar problem after the firmware update.

Just got around to investigating.

I found I had to redefine a Detection Zone, in the Doorbell Detection settings. 

Don't remember setting it for the old firmware, seems the old version MIGHT have assumed the whole view as the active zone whereas the new version assumes no zone unless you actually define one!!

Strange thing is it was still giving event detection notifications, it just wasn't recording anything!

 

  @Wayne-TP 

 

Yes, I do have a D230S1.

 

Everything was working fine prior to the firmware update ( on both the D230S1 and the H200 Hub ).

I have the D230 set up for person and motion detection and local storage via an SD Card in the H200.

Prior to the update I was getting detection notifications to the Tapo app and, during the schedule period set for recording, I was getting recordings saved to the SD card.

I normally have the recording schedule set to only record outside of 07:00 to 21:00 and we don't get many callers during the night!.

So it wasn't until we were away from home for a few days, and changed the schedule to record at all times, that I noticed it wasn't recording any more!

I was still getting detection notifications in the app but no recordings!

I finally got around to looking into it yesterday. I rechecked all the settings mentioned in the link but all were correct. I tried a H200 reset and a format sd card to no avail.

I then noticed that the detection zone was not defined i.e it was presumably the default, so I defined a zone and bingo, now I get recordings!

 

 

  @Wayne-TP 

 

Thanks for the reply.

 

As I said , I dont recall setting a specific detection area when I initially setup the D230 some months ago. That, I assume, would mean that the detection area was the whole of the camera viewport. It seems that the firmware update changed something in this functionality such that a specific detection area had to now be defined.

 

As to ' We haven't encountered any feedback with the same situation so far ', hopefully the original poster will provide further feedback.

 

facing the same problem after my initial day (presumably due to a firmware update) receiving detection notification but no recordings.

  @EY8888 

 

Did you try setting the detection zone ? Mine has been recording fine since I did that.