Logging out and back in or reinstall or power off/on does NOT work for me.
Tried logging out and in, uninstall reinstall, remove cam plus, remove the doorbell and add it again. Nothing. It’s working perfectly streaming live and recording, but still Error 6 trying to watch those recordings.
1 Like
Update, just tried again and it works now. The older recordings aren’t playing but new ones are. Curious if it will continue to work now or be on and off for a while. I didn’t change anything settings, it just started working
Those with the issue, which firmware does your doorbell have?
4.25.0.222
Ok, well there is a new firmware coming so hopefully that will address this issue
It works now but for new videos only. Wyze probably fixed something on their servers to make it work.
Mine is working now as well. Must have been a backend fix.
Didn’t fix any of my issues with the doorbell
I have the 07 error too. Latest firmware and did the login/out and restarted my phone … no joy.
On a positive note I can download the video and play it on my computer so clearly it’s an app issue trying to read the file. My guess is that it has to do with 90 degree video rotation.
Wyze support told me a couple days ago to:
If you have Cam Plus, please try removing it from your account and add it back. Afterward, try to access the playback feature.
Afterward, force close the app. Then, power cycle the device.
But that didn’t help. Nor has this procedure, which I have done many times:
- removing the device and adding it back
- logging out of the Wyze app and logging back in
- removing CamPlus from the Doorbell
- restarting the phone
So, one month-plus since I got the doorbell and installed it. And still no video playback of doorbell events.
Wyze support will probably, based on past experience, contact me again in 7-10 days…
…Rick…
Have the doorbell since February 6. Worked fine day 1, then error 07. Works fine on wife’s iPhone. I have android 10 on a new phone. Several tickets sent and still waiting response.
Frustrating…
FYI, similar connectivity issues here on a new install from yesterday. Worked great for about 6 hours, now it’s losing connectivity constantly, and when I can get the camera to connect Live, bit rates are all over the place until it finally drops. It’s less than 20 feet from the wifi AP, signal strength is max, 2.4 GHz network. Blue light is solid on at the unit all the time. If I go outside and trigger the motion sensing, it detects it and records a video, and that also usually brings the Live video back to life for a short period.
There’s nothing wrong with my power supply (tested 24 VAC), my wifi, and the camera is clearly functional. Signal strength is at a max, so the unit’s antenna is working fine. Tried removing then re-adding CamPlus as suggested above, no improvement. I have two other Wyze cams at this house, both work fine with zero issues on the same network. Looks like another case where we just wait until there’s a firmware update to fix the problems.
This isn’t my first early Wyze product, I’m used to the idea that we’re the beta testers. I worked in the semiconductor industry as an engineer for 30 years, gotta say that if we released a new product with as many major functional bugs as Wyze seems to think is acceptable, we’d have been OOB quickly. I don’t mind putting up with it, as they do seem to eventually fix the problems, but it spells trouble for the company in the long run.
2days ago i was getting the 07 and now it’s 09 ,i did everything from reinstalled the app 2 phones, factory reset doorbell, no dice, live stream works, and recorded events from other came work, what a waste of cam plus
1 Like
Has not worked for me since installation 2 weeks ago. Other cams, v1 & v2 work fine. Plays back on my wife’s android with her account fine. I can download the video via share and play back with vlc video player on my android but get error 07 when trying through the wyze app. Opened tickets and sent logs, Nothing but crickets from wyze. Very disappointing.
Check to see if there is a firmware update. No, it still doesn’t work BUT with the latest update the error code changes for 07 to 09.
For some people they were able to logout of the Wyze app then log back in and have everything work. My results were like ONjOlt’s and the error code number just changed.
I 'm sure Wyze is working on this and my guess is the problem is with the way the doorbell video is turned 90 degrees.
Yeah it sucks when things don’t work the way they should but these things came as a preorder deal and for $30 I really cannot complain. I know Wyze is working on it and I’d rather they have people actively fixing the problem than have customer support endlessly saying yes, we are aware of the problem and are addressing the issue, please be patient etc.
1 Like
I posted a week ago about issues with poor connectivity. Another firmware update for the doorbell was issued this week and I applied it. Since then, connectivity has significantly improved, with less variation in bitrate. I made no changes to the router or to the doorbell power supply. Hopefully, this good performance will continue, for now, performance is satisfactory.
Note that the original issue here is not with connectivity, or ‘live’ view, but with event playback causing errors. Error 07, Error 09, or a continual spinner on hitting the event’s play button (with no playback).
Connectivity, in my case, is not an issue - strong signal, and a V2 Cam is just above the doorbell cam and has no issues with event playback.
The latest firmware (including the one just released a few days ago) has been applied; app has been exited and re-started/signed in, doorbell device rebooted, but still new (and old) events do not play back.
All firmware and apps updated and error has changed from 07 to 09 for me as well,
I’ve tried every sort of update, log out, disconnect, etc., suggested so far, and nothing has eliminated the error.
Here’s the weird thing: I have four devices. Three devices are running Android 6. None of these devices work properly when it comes to viewing events. One device I have is running Android 8 – that one works fine! Go figure…