Wyze New video v2 doorbell vs Wyze doorbell pro

Cameras
,
21

I have in the past, was just sharing information as per the post. I’ll troubleshoot further later.

22

Hello,did they find a fix? I am having the same problem for 5 days now but only on the doorbell,the other cameras are fine.Thanks for any assist

23

Welcome to the Forum, @firstknight! :wave:

From your post, I’m having difficulty discerning what potential fix you’re asking about and what problem you’re experiencing. As this is an older topic, if you’re having a specific issue then I wonder if creating a new topic with a detailed description of that might help you to attract the assistance you’re seeking.

24

appolagies,I thought it was a thread just for the error 20004 on the wise doorbell v2

25

No apology is necessary! :slightly_smiling_face:

Thanks for replying with more detail. I’m not sure what’s at the root of that error message, though I’ve seen other community members report it recently. I haven’t ever seen an official explanation for that particular error code, and the Help Center isn’t providing me an answer.

If you haven’t already done so, I’d suggest creating a log the next time you’re able to reproduce the error and then following that up with a Support ticket.

This is how I prefer to submit tickets (you can tap or click to expand this):
  1. Visit the Help Center: https://go.wyze.com/help[1]
  2. Click into the “AI-powered search” box in the middle of the page and enter create ticket.
  3. Click Yes, that is correct.
  4. :point_up: Repeat Step #3. (:face_with_symbols_over_mouth: UGH! :roll_eyes:)
  5. Click No, I do not like chatbots.
  6. Click This is about a product.*
  7. Click Other.*
  8. Click Create Ticket
  9. Enter your contact details and a brief issue description (include a Log ID if you have one) and click Submit.

     * Make your own appropriate/relevant choices here.[2]

It doesn’t really matter how brief the description is. Wyze’s system will generate an e-mail message to you automatically with a Wyze Ticket number, and you can just reply to that message from your e-mail client and add as much detail as you want.

I suspect Wyze has made some back-end changes that are causing this issue, though that’s only a guess on my part based on previous observations. Letting them know via logs/tickets that this continues to be a problem is probably a good way to have this on their radar and get them to address it.

  1. This might be a good one to bookmark. ↩︎

  2. I’m demonstrating my typical path. The number of steps will likely be the same and result in the identical endpoint regardless of the choices you make. ↩︎