Pressing doorbell stops recording after about 10s while 60s is set


Ever since the Homebase update of August 11th I have some weird behaviour.

I have these settings:


Recordings are set tot 60 seconds.
But when someone presses the doorbell it stops recording around 10 seconds after pressing. If there is still something in view moving… it will start a new recording which is 60s. Between those I’m missing a few seconds of recondings.
If it’s just the motion trigger it records for the full 60 seconds. This behaviour happend after the homebase update of 13th of August. Before that it would always record 60s.

What I did find out is when I turn on “End clip early if motion stops” it wont stop after +/- 10 seconds when the doorbell is pressed. It will record (as it should) as long something is in view.

To be clear. It happens when I’m -not- using the app and/or viewing the doorbell.

Can anybody reproduce this? Or has a fix?
Support can’t find anything wrong and thinks it’s something wong on my end. Either reset or return the doorbell… Not really feeling to do that.
I’m 99% sure it is the update of the homebase which changed the behaviour. Exactly after the update it happend. I can see that in my history recordings.

On the 8th when it still worked:

On the 13th after update it broke:


Since you are using custom 60 second clips, what happens if you use optimal surveillance mode after a door bell press?

There has been some merging of working modes, some users see 4 modes, some see 3, could be related.

‘Optimal’ doest have the 10s cut problem as it uses the ‘End clip early’. ‘Optimal’ also probably has a longer interval.
So that 10s cut only happens with the ‘custom’ profile with ‘end clip early’ off…

To give some detail… If someone is standing for 25s in front of my door before pressing the doorbell the recording will be around 35s.

But I’m curious about that 4th mode you say that some people have. Got an example?


I’ve noticed the same thing. Getting 6 second clip when someone presses the bell vs just motion which is 40 seconds (what I’ve set)

1 Like

Somehow glad I’m not the only one.
Did it happen around the same time? After August 11th?
Have you reported it to eufy support?

An update about this:

Support set me back to the older Homebase firmware and its working flawless again.

I hope they can fix the issue now so I can get the new updates again.

Update: They send me a new Homebase2 after months and this issue is still present. But they still can’t replicate it on their side. They do confirm it.
With adjusted firmware v2.1.0.9h they can downgrade me and it works normal…
Aren’t others having this problem? Or know why it happens?
If you got this issue… Please report it to support so they can trouble shoot and fix it.

I have exactly the same problem. My homebase is running on v2.1.5.0h. I will open a seperate case. Thanks.

Please let me know if you got an update about this!

Hi Maus,
support is still trying to help but still no luck here.
Are you still running on work around using an old firmware ?

Sorry for the late reply. Because I got a new unit they needed to build the old firmware again for my unit.
Not sure why that would take so long but that should be done this week. I’m now in the latest firmware still.

I got the old firmware again yesterday. Which solves it for now. I really hope they can fix it in the current firmwares. I don’t like staying behind.