I started one yesterday for every 3 hours it didn’t help but definately a good idea
Same problem.
LOG 1564207
MAC D03F27C65100
Firmware 4.51.2.0578
I wonder if the vdb.v2 issues are in any way tied to production?
Ordered my vdb.v2’s early, shortly after introduction. There have been issues I attribute to need for transformer upgrade, firmware and Wyze and AWS servers. However, as of late (several months) things are going extremely smooth. It seems the vdb.v2’s purchased in recent months are experiencing these issues.
Any validity to this statement?
I purchased my v2 December 2023 and I have the disconnect problem. I have a lot of devices on my network and power cycling the v2 brings it back online. I personally think the error has to do with the router shedding the doorbell thinking it is not being used.
Bought mine back in May of this year (2024). Worked great with the TP-Link DECO mesh wifi - but when I swapped to AT&T 5G home internet it came with a new router/AP. The Video Doorbell V2 simply will not work with this new router. If by some chance I do get it to take the QR code - it will just stay flashing orange.
I recently re-connected the TP-Link AP and setup the vdb.v2 again in the app after fully removing it. It connected and worked that night but started flashing orange the next day.
Once I get home i’ll post the MAC address to the appropriate location. Glad it’s not just me - i’ve been getting frustrated with this thing.
If ANYONE knows of the specific wifi settings required for the doorbell, please let me know. Could it be something like the broadcast strength is too high in mhz or newer security settings incompatible with the vdb.v2… I have created a specific 2.4ghz SSID to ensure the doorbell wasn’t connecting to a 2.4+5G combined network.
after suffering through this problem with the new firmware for a couple of weeks, I set up a ping monitor (uptime kuma) to ping the doorbells ip address every minute. mostly to be notified when it went offline so I could go reset it.
however it looks like this ping is also keeping it online, because it hasn’t been a problem since I set it up.
just an easy temporary solution for anyone also having this issue.
Add me to the list with this issue. Running on a TP-Link Omada network, the doorbell is connected with full signal strength to an EAP-670 about 20ft away through a wall. Firmware 4.51.2.1041 and replacement hardware did not solve the issue. Same fail-to-orange-blinking after a few hours, requiring power reset and often full device reset/reinstall to come back to life.
1 Like
As an update, I tried the ping/keep-alive suggestion from @aaronwcurtis without any luck. However, I next tried swapping to a new SD card. So far so good! Both cards are Samsung SD Pro endurance with the original card being roughly six months old. Lemon? Will update if the problem re-occurs but I thought others may want to try pulling the SD card if they are having issues.
Last update. Changing to a fresh card kept it alive for a couple of days. Resetting with no card kept it alive for a couple of days. I am giving up and going back to a button.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.