Recent content by Glen Mark

Given that my DB keeps losing its config every few months (at times on its own while it's running (I actually have it on a UPS) and at times when I have a long power failure and the UPS dies), is it something I should try? Or, is it pointless, just an issue with the whole DB platform

You say yours is still flashing? So, are you basically using the &!%@ thing as a chime? That's it? Wow. Something's up ... I don't see a lot of people chiming in with this issue of randomly losing firmware settings and having to recover... I wonder if it's something we did. One thing I have...

Have you ever tried restoring from the config file after a reset to see if the chime setting is recovered?

Does anyone know if you use the Export Configuration option in Batch Config, will it save the chime setting, so the next time the thing goes blinking blue, I can just connect ad-hoc to the db2 and Import Configuration and be back in business? Anyone try/using that successfully?

Has anyone figured out exactly why this doorbell seems to reset/lose its configuration every so often? I have the RCA with the EZVIZ firmware -- for me it's about the 5th or 6th time in 2 years or so. Very frustrating, now that I have to fully reset it in order to get back the chime...

I like the way you're thinking. The doorbell probably teaches out to ezviz with those packets, if you figure out what the domain is you could seed your internal DNS with the address of your raspberry pi or whatever will catch those packets. It's definitely a worthy endeavor, better than some...

I just DL'd GV 4.5.1.0716 on Android. I was able to log in with my EZVIZ username, but it seems like they have now also removed the Chime Type setting! What version are you guys using, maybe I can sideload the APK and get back to a rev that supports this. EDIT: I found a version 3 of the app on...

Having a problem with my RCA running EZVIZ build 190708 recently. The doorbell is on 5ghz and is dropping off Wifi and staying dropped until I walk in front of it. The doorbell button is solid red, then turns blue in a second or two after I walk in front of it and trigger motion (which I guess...

Re: Video play failed, error code:380356 Error resolved by a reboot. :( EZVIZ firmware V5.2.4 build 190708. Must be a memory leak, the doorbell was up since end of October when I updated to this firmware.

David, thanks for your reply -- do you get this exact code? Do you think this means some kind of authentication error on the video encryption? I did try an older V3.x version of EZVIZ that I had on my tablet (forgot I had it there) and I'm getting the same error. Even videos that I know worked...

Anyone update to the latest EZVIZ android app 4.0.4.1217 and having trouble playing alert videos from the SD card? I see all the thumbnails for the Alarm messages, and live video works, but video playback fails with: Video play failed, error code:380356 Doorbell is running EZVIZ...

Hey Chad, you used to prefer the RCA app. What changed? I hate the lag in notifications on Android -- it impacts the ones I've tried -- RCA, EZVIZ, GUARDING VISION -- the last one I tried because I saw someone post under the RCA app that RCA recommended it to them. It doesn't seem to wake up...

Is anyone else finding that visitors are pressing the camera or speaker in the middle rather than the doorbell button at the bottom? :banghead: Unfortunately, they're basically all black, and the speaker is the most shiny. Aargh.

I got this from Voxx support on how to do a full reset (some of it seems overkill/depending, but take it FWIW) 1. Delete the device(camera) from the Security App. 2. Uninstall and reinstall the Security app. 3. Cut the breaker to the unit for fifteen minutes for the doorbell to successfully...

Yeah it did exactly the same to mine! Turn on WDR mode in IVMS and it will go to normal. Im going to try a hard reset from the front of the device.