Wyze Video Doorbell Pro EoL?

Cameras
,
1

Hello!

I was checking the firmware on my Wyze Video doorbell Pro, and noticed something: The last update was March 2023, over three years ago (see https://support.wyze.com/hc/en-us/articles/360024852172-Release-Notes-Firmware#Accordion-wyze-video-doorbell-pro-firmware-21). Now, the End of Life policy page ( Wyze End of Life Policy – Product Support Terms ) says they’ll post end-of-life products on the Terms of Service page (and link it), but… Wyze Cam v1 went End of Life on 2022, and still isn’t noted there four years later.

As security issues are common in underlying libraries, I have to ask: Is it time to retire my doorbell and switch to a different subscription service?

2

Good catch. I will send the feedback on to an employee.

I do see that the warranty policy from April 27, 2026 does mention EOL…but only for the Wyze Sense v1:

End of Life products including Wyze Sense v1

The last time I asked an employee about EOL in an AMA, they indicated that the v1 was the only camera officially EOL because it couldn’t support the updates they needed to make. All the rest of the older cameras were considered “Discontinued” (not actively manufactured and sold anymore), but not EOL and that they would continue to provide critical security updates if they needed them. But otherwise for most of their products, once they are no longer actively sold, they tend to try to leave them in a stable state as much as possible. The more updates they do, the more surface they make to accidentally introduce new bugs, so unless something is critical, they try to leave it alone while it seems mostly stable without high-impact issues.

I am pretty certain the VDBPro is not EOL. But I agree they need to fix their EOL policy and list of devices because right now it is not consistent in the documentation. Thanks for pointing it out and I will pass that on for you.

3

Thank you.

That said… problems occur in underlying libraries regularly. If Wyze hasn’t issued a firmware update on a wireless product in over three years, that means one of a couple of things:

  1. They’re only responding to actual reports on their products, and not monitoring reports on the libraries they’re using.

  2. They’re not maintaining the product.

  3. That thing I haven’t considered.

If it’s 1, they’re not really security-conscous, and I should absolutely find another solution.

If it’s 2, they really need to get their act together on EoL notifications, because those matter for security, and I should probably find another solution.

If it’s 3, I’m really interested in hearing what’s going on.