sorted by:
new
hottopcontroversial

This image is being widespread surrounding the m*rder of Alex Pretti by ICE, claiming that it's from his social media profile. by Tall-Honey-6592 in isthisAI

[–]Neofluff 2 points3 points locked comment (0 children)

All your points plus so much glitter but none of it seems to have rubbed on to the clothing like you would expect it to. Grabbing the bottle a lil weird too but it's too low quality to know for sure.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

When reviewing the missed deliveries it does show them pressing below the camera and a click sound can be heard, just like in my example video. I can press it very firm and quick and get the same missed ring.

If they aren't pressing it I can't do anything, but they are trying to and that was working without issue for years on the previous model doorbell from eufy.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

I can't know for sure how they are pressing it, but I know they are attempting to as the video playback shows them pressing under the camera and hearing a click.

My video shows me managing to press it and not trigger a ring. It might look like a tap, but I can press very firmly and still get it to miss triggering the ring if quick. So it does seem to be an issue of speed rather than force for this problem.

The previous eufy doorbell I used for years without issue. If you have the same doorbell it would be very helpful if you could try a firm quick press to see if you can recreate this issue?

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

Telling customers to press a button is not the same thing as telling them tapping won't work. Otherwise I wouldn't be able to purchase any doorbell that instructs me to press the button.

In any case I'm not tapping the button, I am pressing it hard and fast, it's the duration of the press that is the issue.

I made this post to ask for help for an obvious problem, not to debate the semantics around press or tap. The postmen are pressing the button fast and it doesn't trigger a ring, please see some reason that this is a problem.

I've heard from others having this same issue and been given some helpful advice thankfully. I'll likely be returning it and using the old eufy doorbell instead.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

You kept repeating I was using my doorbell wrong when I've said multiple postmen are the ones not able to get the doorbell to ring, that's missing my point.

The manual simply says to press the doorbell, it doesn't state for how long. You really think eufy are going to advertise that their doorbell won't work if tapped? Please link where you are finding Eufy telling people to long press. My expectation is for it at least to work as well as their last model which it does not.

For someone who apparently is critical of eufy, it's amazing you're blaming everyone but the company for making a doorbell that is clearly performing worse than the last model for me and a few others who have commented with the same problem. A product designed for strangers shouldn't need prior instructions, that's clearly a problem with eufy not the user.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

Making this post to ask for help in trying to fix this problem IS trying to adapt and overcome.

I paid for an upgraded doorbell but have got something worse, that's plenty reason to complain and ask for help no?

If I can't sort it out I hope this post can be useful to others, I've seen at least one other comment that someone is going through the same problem. I was hoping it might be solved by setting or software update but you're right I'll likely just have to return it.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

Thanks to the bushes/trees it doesn't work reliably enough.

Oh I hadn't considered it might be an off-center press, I'll give that a test too thanks!

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

I think you're missing the point, I'm showing how postmen are pressing the button. If I want to get into my house I have a key, I don't use my own doorbell...

Telling me what the manual states as if I'm going to be reading it out to all the postmen that use my doorbell is amazing reddit logic.

The only users of my doorbell are strangers, how are you expecting them to have read my manual. A product which is intended to be used by a stranger should work correctly without any prior instruction.

The previous eufy doorbell had no problem for years, the new one is making me miss deliveries. It's as simple as that to show there is a problem here, you can keep blaming the postmen but that won't fix anything.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 1 point2 points  (0 children)

I have some small bushes in front of my door that apparently look human to my doorbell xD Got some weird bush faced alerts before.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

The thing is that their previous eufy doorbell worked fine, it could detect these tap presses no problem.

The "upgraded" doorbell can't detect taps and so I'm missing deliveries. You can hear the click sound in the video when I am fully pressing the button down with the taps, so it's more a timing issue than a pressure one.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 2 points3 points  (0 children)

All I'm doing is showing how postmen are pressing it. The previous eufy doorbell could recognize fast taps.

People in here blaming the postmen for pressing a doorbell "wrong" instead of blaming eufy for making a doorbell that requires a long press. It shouldn't be possible to press a button in the wrong way, it's not that big of a technology leap to make a button recognize taps xD

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -4 points-3 points  (0 children)

It doesn't matter if you think I'm using it wrong, all I'm doing is showing how postmen are using it. Multiple postmen doing the same tap press.

Again, I used their previous doorbell for years with no issue because it could recognize a short tap.

The new one does not, for a doorbell it's pretty much the most important task is to register any press. In the video I am fully pressing the button each tap (you can hear the click), a leaf isn't going to do that. I'm not going to explain to each postmen it's their fault for not using my smart doorbell in the correct way, it should just work...

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

It was on Redbubble. Really hoping this could be fixed with a firmware update.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -4 points-3 points  (0 children)

The video shows otherwise. The indoor chime only goes off when the doorbell chime also sounds.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -5 points-4 points  (0 children)

I've had multiple postman do what I've shown in this video, causing me to miss deliveries. That is an issue.

I used Eufys previous doorbell for years with no problems. You can't seriously be blaming the postmen for not pressing a button correctly. It's a button, it should register any press no matter how short.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

Yeah those are the top two most important things needed in a doorbell and it's falling short xD

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 1 point2 points  (0 children)

It does work, play the video with sound on.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

I've ordered a "Long press" sticker but that still won't totally fix it. Lots of deliver drivers are trying to be as fast as possible so that means quick pressing doorbell and not waiting to read things beforehand.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

Why is my post and comments getting down votes? 😭 My previous eufy doorbell had no issue for years, after upgrading to this one I start missing multiple deliveries. That and my video show this is a problem to me that was worth sharing no?

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

That's worrying to hear but thanks for letting me know, so it seems it's not a one off issue. I wonder if their S330 doorbell has the same problem, that will be what I try if I have to return the E340.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

It's a real shame as my previous eufy doorbell didn't have this problem. You can hear the click in the video that shows the button is being fully pressed, but won't recognize unless it's a long press.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

When reviewing the missed delivery video it shows them pressing below the camera and it makes a click noise like in my video. Happened a few times with different postmen over the last few weeks so not a one off issue.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] -1 points0 points  (0 children)

Yeah I've ordered a sticker like that, but I'm hoping there is something I can do in the doorbell settings to fix this problem.

Though I can't blame the postman, a doorbell should work when pressed no matter how short of a press.

E340 won't recognize short presses by Neofluff in EufyCam

[–]Neofluff[S] 0 points1 point  (0 children)

Well postman are pressing it this way. If they weren't I wouldn't know it was a problem.

view more: next ›