I have a NVR4208-4KS2 (200 Mbps BW). Since the hw is the same as NVR4216-4KS2, is there any (legal) way to upgrade to 16 channels? Maybe buying some license from Dahua or something like that? Now I need a total of 9 cams and I should dismiss my 1 year old 8ch and buy a 16ch with identical hw... I'is a non sense!
Latest new NVR4XXX-4KS2_MultiLang_ V4.001.0000005.1.R.201126
- Thread starter EMPIRETECANDY
- Start date
looney2ns
IPCT Contributor
Hi All,
I had a strange issue after upgrading from V4.001.0000003.1.R.200813 to V4.001.0000005.1.R.201126.bin... NIC card wouldn't negotiate any connection anymore. Only thing that got it working again was to "Default" settings from the local console.
For kicks, I decided to import the settings that where backed up before flashing. Same issue.
So it seems I had an incompatible entry somewhere in the configs that was preventing the NIC from connecting.
Strange.
I had a strange issue after upgrading from V4.001.0000003.1.R.200813 to V4.001.0000005.1.R.201126.bin... NIC card wouldn't negotiate any connection anymore. Only thing that got it working again was to "Default" settings from the local console.
For kicks, I decided to import the settings that where backed up before flashing. Same issue.
So it seems I had an incompatible entry somewhere in the configs that was preventing the NIC from connecting.
Strange.
I repeated several times and confirmed.
NVR update is not working at Firefox, but it works in Chrome. OK, can live with that.
NVR versions 3216 is working fine.
NVR version 4001 (both 0003 and 0005) does not recognize camera, red dots in camera list, "download certificate" in live view.
Downloading certficate didn't help either.
When I downgrade to 3216 it all work fine.
Any explanation ?
NVR update is not working at Firefox, but it works in Chrome. OK, can live with that.
NVR versions 3216 is working fine.
NVR version 4001 (both 0003 and 0005) does not recognize camera, red dots in camera list, "download certificate" in live view.
Downloading certficate didn't help either.
When I downgrade to 3216 it all work fine.
Any explanation ?
More exactly about this problem (recognizing camera)
-v3216 working
-v4000 working (including latest DH_NVR4XXX-4KS2_MultiLang_V4.000.0000001.5.R.191218.bin)
-v4001 not working (DH_NVR4XXX-4KS2_MultiLang_V4.001.0000003.1.R.200813.bin, DH_NVR4XXX-4KS2_MultiLang_V4.001.0000005.1.R.201126.bin)
Camera IPC-HDW5231R-ZE) is upgraded to last version 16.
-v3216 working
-v4000 working (including latest DH_NVR4XXX-4KS2_MultiLang_V4.000.0000001.5.R.191218.bin)
-v4001 not working (DH_NVR4XXX-4KS2_MultiLang_V4.001.0000003.1.R.200813.bin, DH_NVR4XXX-4KS2_MultiLang_V4.001.0000005.1.R.201126.bin)
Camera IPC-HDW5231R-ZE) is upgraded to last version 16.
Attachments
BruceInBright
n3wb
EDIT: Ignore me: The distributors Hills gave me a call - it was always going to be faster to factory reset and rebuild. Done. Simples. (I'm going to be mildly grumpy for a little while)
Well, bugger.
I've been called in to help a customer who has upgraded to DH_NVR4XXX-4KS2_MultiLang_V4.001.0000005.1.R.201126 on their DHI-NVR4216-16P-4KS2 and while it isn't bricked, I can't for the life of me get the cameras to talk to it now.
Status is all are red and I though that it might be a password problem but I've tried that and added addition ONVIF users (think the user password was to short) and still no joy.
I've looked but has anyone had this problem before and can point me to the path of enlightenment? The cameras appear to be: ITX Security NMD-2003P or NCD1300PR.
Is it possible to downgrade back to the orginal firmware?
Thank you
Bruce
Well, bugger.
I've been called in to help a customer who has upgraded to DH_NVR4XXX-4KS2_MultiLang_V4.001.0000005.1.R.201126 on their DHI-NVR4216-16P-4KS2 and while it isn't bricked, I can't for the life of me get the cameras to talk to it now.
Status is all are red and I though that it might be a password problem but I've tried that and added addition ONVIF users (think the user password was to short) and still no joy.
I've looked but has anyone had this problem before and can point me to the path of enlightenment? The cameras appear to be: ITX Security NMD-2003P or NCD1300PR.
Is it possible to downgrade back to the orginal firmware?
Thank you
Bruce
Last edited:
There is a risk to downgrade. See NVR4208-8p-4ks2 after Firmware downgrade - nothing works
I have a DHI-NVR4208-4KS2 NVR. I downgraded it from 4.000.0000001.5 to V3.216.0000003.0. Then I ran into boot loop. I had to follow this thread to recover:
ipcamtalk.com
My guess is the old firmware cannot recognize the new configuration file, which results in boot loop.
I have a DHI-NVR4208-4KS2 NVR. I downgraded it from 4.000.0000001.5 to V3.216.0000003.0. Then I ran into boot loop. I had to follow this thread to recover:
Help identifying Dahua OEM NVR from Speco N8NXP
Hey everyone. I’m trying to find the original Dahua version of the Speco N8NXP NVR. Based on my research, I think it’s the Dahua NVR4208-8P-4KS2. I’ve opened up the NVR and it seems to match identically both inside and on the back ports. I used the pictures on this amazon listing for reference...
My guess is the old firmware cannot recognize the new configuration file, which results in boot loop.
BruceInBright
n3wb
As I wrote, Dahua support told me you CANNOT downgrade from V4 to V3 in the user way...
MikeyTech8
Getting comfortable
Great firmware. I've noticed in the storage > schedule > Record, that they changed the coloured boxes names to intelligent and M&A. Can anyone advise which ones is IVS?
there's no mention of the obvious change
And the change was obviously introduced in V4.001.0000005.1.R.201126, as the prior release notes V4.001.0000003.1.R.200813 screen shot is without the new 'M&A', as below...
there's no mention of the change in the release notes....i'm not surprised, Dahua release notes are clearly quite sloppy....
And the change was obviously introduced in V4.001.0000005.1.R.201126, as the prior release notes V4.001.0000003.1.R.200813 screen shot is without the new 'M&A', as below...
Attachments
noob questions...
1) Does this firmware still support motion detection from ONVIF cameras? I'm presently on version DH_NVR4XXX-4KS2_MultiLang_V4.001.0000000.1.R.200319 which was a downgrade from a higher V4 firmware under which the NVR did not recognize motion from any of my cams using the ONVIF protocol. I'm hesitant to upgrade for fear of losing motion detection again.
2) Do ONVIF camera names "stick" properly under this version? I find with my current firmware version, the NVR reverts the names I assign to the ONVIF cams back to "IPC" every time a single camera disconnects and reconnects.
1) Does this firmware still support motion detection from ONVIF cameras? I'm presently on version DH_NVR4XXX-4KS2_MultiLang_V4.001.0000000.1.R.200319 which was a downgrade from a higher V4 firmware under which the NVR did not recognize motion from any of my cams using the ONVIF protocol. I'm hesitant to upgrade for fear of losing motion detection again.
2) Do ONVIF camera names "stick" properly under this version? I find with my current firmware version, the NVR reverts the names I assign to the ONVIF cams back to "IPC" every time a single camera disconnects and reconnects.
yes, my DHI-NVR4216-16P-4KS2 is running DH_NVR4XXX-4KS2_MultiLang_V4.001.0000005.1.R.201126, and reporting ONVIF server version 20.06(V2.8.1.957450), ONVIF client version V2.4.1 , and is successfully detecting motion from all IPC that have motion detection enabled.
IPC i have are:
IPC-HFW1831E F/W: 2.800.0000000.5.R,2020-01-07
IPC-HFW2831S-S-S2 F/W: 2.800.0000000.24.R,2020-10-14
IPC-HFW2831TP-ZS-27135-S2 F/W 2.800.0000000.24.R,2020-10-14
Also camera names i've never had an issue with, they've always remain unchanged.
Last edited:
Thanks for the info, but those are all Dahua cams. I’m referring to issues with other-branded cams that don’t support the private protocol and must use Onvif compatibility. Specifically, my cams primary protocol is XM protocol and they are based on the HI3516D-83H50N chipset. The Dahua Nvr manual for V4 firmware specifically states that only private protocol cameras may be renamed, so while I’m disappointed that ONVIF protocol cam names don’t stick, (because they did under V3), I’m more concerned about losing motion detection.
I’d be grateful if anyone using cams like mine, or at least any other cams that don’t support private protocol on 37777 and must use ONVIF on 8899 (or similar) would weigh in on motion detection with this firmware.
so i switched over to ONVIF Version19.12(V2.8.0.949611) protocol on the IPC, and motion detection still working just fine, camera names didn't change either
the only issue i've had using ONVIF, is the main stream date+time overlay position changed / bit messed up, the sub stream date+time overlay position remain unchanged.... look into that soon....
Last edited:
@Hazza06 That sounds promising. Thanks for your help. I was going to ask if you would mind rebooting the camera that you've changed to ONVIF and see if the name you've given it remains after the reboot or if it gets changed back to IPC, but my impatience got the better of me...
I was concerned that maybe the issue lies with my ONVIF cams. So to test that suspicion, as you have done, I just tried changing the connection from one of my private protocol cams (an Amcrest OEM'd by Dahua) from Private to Onvif and tested with that. It took me a second to realize the ONVIF port on that cam is 80.
After having named that "onvif" camera using one of my goto methods (SmartPSS on the PC, DMSS on the iPhone, or use the HTTP API via a browser), and verifying the name in the NVR console and the remote utilities, I rebooted it.
When the Amcrest camera came back online again, it's connection as an ONVIF cam reverted the camera name back to IPC, along with all the other ONVIF-connected cams - they're all named IPC again.
So... I took the plunge and upgraded. Much to my dismay, not only has the ONVIF camera name issue persisted, but now nothing is recording! I have live view, but nothing is recorded, even the Amcrest cams set to always and motion recording. I've reverted to the previous firmware and while I can tell from the camera status page that motion detection is working, still nothing is being recorded to disk.
So... I set default settings, restored a config backup and recording resumed. In the midst of all this, the newer firmware must have re-enabled the sync-device setting, and set all my ONVIF cams to Beijing timezone instead of my own. I've had to log into each one individually and correct the time zone. At least my stuff is back to the way it was, with only the ONVIF camera name issue persisting.
I can't understand why I'm the only one having this issue with the ONVIF camera names (not channel titles, camera names) that do not stick after renaming, especially when the Dahua NVR manual v1.0.3 itself states on pages 84-85 that only cameras on the private protocol can be named. (This functionality is a departure from the pre-V4 firmwares, I believe).
Last edited:
I was able to get around the "download certificate" issue by enabling https on the NVR and login using
https://ipaddress. I used chrome. I didn't need to install any certificates. I did get the big warning from chrome that the ssl certificate was untrusted but that is because it is self signed. I might import it later.i had the same issue, and also needed to enable https to workaround the issue, however i'm still not clear why this suddenly became a requirement to view live in https only ? there was no change in my NVR, previously i was able to view live via plain old http....no changes on NVR, and same F/W version etc,,strange....
Hi have a Chinese domestic NVR 4116HS-4KS2 which running a firmware version V3.216.101N000.0, Build Date: 2019-03-14 (its info capture is attached)
May I know if I can install this firmware into my NVR. I want to use an English GUI rather than the Vietnamese GUI like current version.
I read this thread Important! About dahua hacked Chinese cams and NVR issues I'd like to ask so that I will not brick the NVR.
Thanks!
May I know if I can install this firmware into my NVR. I want to use an English GUI rather than the Vietnamese GUI like current version.
I read this thread Important! About dahua hacked Chinese cams and NVR issues I'd like to ask so that I will not brick the NVR.
Thanks!
It is best to obtain any firmware updates from the vendor you purchased it from so that you do not run into issues. Any firmware you find here or elsewhere is obviously proceed at your own risk. We have many threads here where someone tried an update with a firmware they found on the internet and bricked their unit.
Many units being sold are Chinese hacked units that will either brick or go into Chinese upon updating. Some vendors will be upfront and tell consumers that as part of their website, but many do not or the consumer forgets...here is one such example....
Many units being sold are Chinese hacked units that will either brick or go into Chinese upon updating. Some vendors will be upfront and tell consumers that as part of their website, but many do not or the consumer forgets...here is one such example....