Just to clarify, the symbols used says that Siren is the lowest priority, two way audio is mid-priority, and Prompt tone is the highest priority, but the wording/description I believe suggests the opposite is intended. So I believe it should be:
siren > two-way audio > prompt tone
(Siren takes the highest priority over everything, meaning it is greater than two-way audio which is greater than prompt tone [which is the lowest priority])…the “alligator mouth” of the symbol is supposed to be open toward the greater thing. But if I am assuming wrong and the symbols were correct in their original orientation, then it is the wording description that should be updated instead because it led me to believe the symbols were backward. Anyway, the descriptive wording and the symbols currently contradict each other, so one of the 2 are not correct,
I updared all devices I have with the reported Firmware. No issues at all. Thanks.
I do have a few questions on the VDBPro though:
Where is the Motion Detection Zones and the Increased Sensitivity to 5 levels? When I go to the Detection Setting Menu, I see the following and no Motion Detection Zones or increased Sensitivity Levels:
VDBPro firmware failed the first time when selected in the account tab firmware area.
Second time I went through the home tab - device - device info -firmware version and it was successful doing it that way.
After firmware update on VDBPro, none of the listed updates for VDBPro are showing in the app. I am guessing a new Beta App that hasn’t been released yet is required to view them.
Does anyone else see the 5 sensitivity levels or detection zones? Will someone check and see if it works in iOS, because it does not in Android
(Edit: Just saw Spamoni edited and updated his response to report this too)
I thought it was just me. The FW load for the VDBPro was taking a longer than expected from the FW Update location. I also updated mine from the Device Setting location
No issues updating my 4 v3’s I have hooked up right now, will test our the lamp socket once I get a chance to get back outside without it being raining or snowing lol
Cam v3 live stream and SD recording results in poor resolution and 0.5 second contrast flashing when Night Vision Mode is on (Auto or On) and Night Vision IR Lights are set to Off. Night Vision Condition settings don’t matter as long as ambient light is sufficient to automatically enable NV (non-color) mode. Problem seen under current and older production and beta iOS and Android apps on various phones and tablets running various OS versions. I.e., this is a new firmware issue. This issue is occurring on all of my v3 cams, indoor and outdoor, standalone and Lamp Socket-connected. Recreating scenario is highly dependent on just the right amount of ambient light. I flashed 2 cams back to 4.36.8.26 and issue disappeared. Reloaded 4.36.9.117 and issue resurfaced. I placed a 4.36.8.26 cam and a 4.36.9.117 cam next to each other with the same settings… 4.36.8.26 no issues, 4.36.9.117 contrast flashing.
Thank you for posting this issue. We are working on it. However, we can’t get any information from your log 51542. Do you mind submit another one after reproducing this issue? (Please choose camera instead of app when submitting log) Thank you so much.
But if I am assuming wrong and the symbols were correct in their original orientation, then it is the wording description that should be updated instead because it led me to believe the symbols were backward. Anyway, the descriptive wording and the symbols currently contradict each other, so one of the 2 are not correct,
