D230S1 not sending doorbell ringcall / video calling notifications on multiple uses of the doorbell
I have been trying to set up a new Tapo Doorbell (D230S1) for a family member which they purchased last week.
I have been struggling with doorbell video calling / ringcall notifications to their iphone. Initially I could not get any notifications. However, now I am able to get a notificatiom, which is like a phone call. The problem is that if following the call (regardless of whether it is answered or dismissed), if the doorbell is pressed again within a couple of minutes of the first press / call notification, there is no new notification sent to the phone that the doorbell has been pressed. After about two have passed since the initial pressing of the doorbell, if the doorbell is pressed again, then a video call notification is sent to the phone.
I have spent several hours checking these forums and the tapo app, and the iphone settings of the family member. I have also tried setting up on another iphone to check there was not some sort of call suppression occurring due to a setting on their phone, but the issue is the same - once a video call notification has been sent, further pressing of the doorbell within a couple of minutes of the first pressing of the doorbell does not cause any further video call notifications to be sent to the phone.
I was hoping this might be a known problem, but have found no other threads on this subject - the threads which already exist are for not receiving any video call notifications, which is not the issue here, it is that repeat or secondary video call notifications are not being sent to the phone if the doorbell is pressed (activated) again shortly after having been pressed.
Does anyone have any advice they can provide ? It appears to be a software issue with the app / doorbell / hub, rather than the settings on the iphone as I have followed the instructions with the doorbell and the advice on these forums about settings for notifications. I have also set up the app on two iphones and the problems is the same on both.
If this is a bug, can it be fixed, and fixed urgently, as otherwise the doorbell will likely soon end up being returned to the retailer as not fit for purpose.
thanks