Dahua NVR5216-4KS2 / NVR5216-16P-4KS2

For information:
I upgraded the firmware on my 5216-4Ks2 today from: 3.210.0003.0 to: DH_NVR5XXX-4K_Eng_V3.215.0000000.1.R.20170901

After the upgrade, I lost all local user accounts except 'admin' and my previous admin password was gone. Additionally, none of the standard passwords worked.

Very frustrating and I eventually managed to use the Dahua password reset service, so I'm back in but essentially with all settings lost.
 
Last edited:
I just got my DHL notification from Andy so I haven’t received mine yet. However, from reading I believe the process is the back up your configuration file, update the firmware, run a factory reset, and then restore your settings from the backup you made.

I’m sure one of the much more seasoned people will correct me if I’m wrong.
 
For information:
I upgraded the firmware on my 5216-4Ks2 today from: 3.210.0003.0 to: DH_NVR5XXX-4K_Eng_V3.215.0000000.1.R.20170901

After the upgrade, I lost all local user accounts except 'admin' and my previous admin password was gone. Additionally, none of the standard passwords worked.

Very frustrating and I eventually managed to use the Dahua password reset service, so I'm back in but essentially with all settings lost.
When I upgraded TO 3.210.0003.0 I was prepared for the worst, but it eventually came back up with all settings intact. I wonder if the settings loss depends on the version being installed, the old version, or something more logical like the phase of the moon?
 
So I noticed on the US site there is V3.215.0000000.4.R.180119, can we use that or should we use that on the International version 5216?
 
So on a separate note I have my 5216 for a few weeks now and really enjoying it. I have 3 of my 9 cameras mounted. 1 is defective and waiting on Andy to handle that one as well as the 3 back ordered cameras which appear to be in now. One thing I am struggling with is the quirky web interface. I am now maybe seeing the appeal of Blue Iris. I have Motion detection set up for my cameras, yet when I go to playback the MD yellow events are only showing for some cameras. They all are the new cameras that support motion detection
and I have them all set for 7x24 period with each set to record its individual channel when motion is detected. I also record 7x24 for all cameras.

MD Settings.png MD Period.png
 
So on a separate note I have my 5216 for a few weeks now and really enjoying it. I have 3 of my 9 cameras mounted. 1 is defective and waiting on Andy to handle that one as well as the 3 back ordered cameras which appear to be in now. One thing I am struggling with is the quirky web interface. I am now maybe seeing the appeal of Blue Iris. I have Motion detection set up for my cameras, yet when I go to playback the MD yellow events are only showing for some cameras. They all are the new cameras that support motion detection
and I have them all set for 7x24 period with each set to record its individual channel when motion is detected. I also record 7x24 for all cameras.

View attachment 28230 View attachment 28231

Did you also schedule this for the NVR? Have a look at „Storage“.
IMG_0859.JPG
 
  • Like
Reactions: toolazyforalogin
Yup, just checked and all channels show 7x24 for record and MD. Very odd. I think once I get all my cameras up I may factory rest everything and start from scratch, maybe too much tinkering around.
 
@Crazykiller can you explain why your the "storage" settings only have "general" "alarm" and "ivs" checked and yet @keithl posted a setup picture has "motion detection" on. I just received my NVR yesterday and am trying to understand how to implement IVS and/or MD.

Thanks!
 
Storage settings are user selectable. If you are not using point of sale or alarm aspects you can turn those off. Or, leave them on since it does not seem to impact anything other than scheduling. The orange "holiday" line is a good example. Probably would work for a business that has a holiday schedule different than routine recordings. Generally, not so much for home use though. Scheduling gives the ability to select different storage actions for different hours of the day, or everything all the time. It will only do those actions during the timeframes set. Maybe a business would only want POS recordings during business hours, rather than 24/7. Or, alarm warnings after closing. Or, motion detection turned off in a lobby during business hours so that it does not create MD related events, using general recording for the business hours instead. This allows you to tweak the recording to your needs. During a playback, if you only check "general" it will not show recordings identified as "motion detection". There will be blank spots. Same for "MD", if you only check that, it will not show the general recording in-between. If you check "all" during playback, you should see a line with different color blocks on the bottom of the screen matching the type of recording. This ties back to the storage scheduling. Don't want motion detection in the backyard 8am-4pm because spouse runs an in-home day care? Turn that period off. It will record as a general recording without the MD detection blocks. Only want MD/IVS recordings to save storage space rather than 24/7 recording of a camera? Turn off "general", or give it a schedule. DO make sure that you have sufficient pre and post recording set up though if you do to cover time before and after the MD is sensed.
 
  • Like
Reactions: toolazyforalogin
So this is a dumb question, when it does MD and I have 7x24 normal recording is it just bookmarking info or it generates a duplicate file for the MD time frame?
 
It's not a bookmark per se on the general recording. It records it in the setting type selected based on scheduling selected. If recorded as MD, and you do not playback with general AND MD selected, it will only show you the recording based on playback selection. If you pick one or the other but not both for playback, it will be blank between sections. Playback in general for an hour, the MD sections will skip and not display. Opposite is true. Generally, I use MD as a quick way to review the day in playback . Select time while away and MD/IVS only usually at x4 or x8, then note time of anything I want to see again and go back to just that timeframe. It plays through just the MD/IVS selections, skipping to the next recording. If you do 24/7 for both (I do) during playback, pick the type or types you want to see displayed. If I only want to see IVS trips, I only select that, etc. If you select MD but not IVS and they are of the same area and there is an IVS identified recording at the same time, it will skip that recording segment.
 
So this is a dumb question, when it does MD and I have 7x24 normal recording is it just bookmarking info or it generates a duplicate file for the MD time frame?
Neither. When an event is detected, the 24x7 file is closed and a new file created. When the event time frame is finished, that file is closed and a new 24x7 file is created. I sure would not have done it that way if I were doing it.
 
I like that it prevents double writing and easier than them bookmarking large files.
 
So I have 6 cameras hooked up, 2 are 8MP, 2 are 6MP and 1 is 4MP. To save space I set the 8MP cameras to encode with H265+ and notice that now when I switch back from say playback to the 9 image screen that it takes from 5-10 seconds for the 8MP cameras to show back up, I suspect it load to decode the H265+ stream may be CPU intensive.
 
Dumb question the non-POE 5216/5232 differences. Is the only difference the ability to handle 16 additional cameras, is the quad core CPU an main board the same and strictly a software thing? Is there any more processing power to the 32 camera version? I ask becasue I will wind up with 12-14 high resolution cams (most are 6-9MP) and if the 5232 will handle them better I will sell my 5216 to my buddy and get a 5232 for myself. I wound up with higher-rez cams because I want DORI Identify to range to cover as much of the 45 foot length of the back of my house without having to have a bunch of cameras to do it.

Thanks!
 
Dumb question the non-POE 5216/5232 differences. Is the only difference the ability to handle 16 additional cameras, is the quad core CPU an main board the same and strictly a software thing? Is there any more processing power to the 32 camera version? I ask becasue I will wind up with 12-14 high resolution cams (most are 6-9MP) and if the 5232 will handle them better I will sell my 5216 to my buddy and get a 5232 for myself. I wound up with higher-rez cams because I want DORI Identify to range to cover as much of the 45 foot length of the back of my house without having to have a bunch of cameras to do it.

Thanks!
Not software thing ,hardware difference for 16ch and 32ch. Processing power nearlu the same no big difference.
 
New user of NVR52XX 8 port non POE have been running Blue Iris for 9 years and wanted a Dahua NVR as a backup to the ageing i7 PC running 24/7 with no problems.
Have almost everything working but cannot figure out how to set NVR so that it can sleep the monitor when nothing is happening. With BI the monitor was set to sleep in 2 minutes and would wake up on motion and display camera triggered and would then cycle through all cams then sleep after 2 minutes. Can this be done with NVR52XX ? Have latest firmware 20171211 . 3 dahua cams connected to NVR. Connected to older Dell 2209wa monitor via vga connector. Now monitor remains on indefinitely showing 3 cams or tour
 
What particular model have you purchased for use in an attic setting?

I am currently running a V7 MPEG24S 24-port POE+ Managed switch. It is fan cooled, pretty noisy, and I actually don't recommend it if you plan on running a camera with power requirements at the high end of AT+ requirements. It would not power the PTZ1A225U-IRA-N Positioning PTZ recently installed. However, the old 8 port AT+ TP-LINK TL-SG1008PE would power it fine, even with all the ports powering other cameras.

In my mind, building the switch into the NVR, is just not a great idea with too many limitations. An external POE+ switch is alot more flexible, especially with where it can be placed.
 
  • Like
Reactions: rufunky