Hikvision DS-7616NI-Q2 firmware upgrade. Any risk of losing configuration?

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
Hi folks,

I'm looking to upgrade to the latest firmware; v3.4.108 to Firmware_V4.71.205. There is a 'c' and 'd' suffix posted on their page; not sure what the difference is.

But in either case, is there any risk of me losing configuration on the NVR when upgrading this firmware? Or is it literally just an upload/reboot and I'm up and running?


Thank you.

-J
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,550
Location
USA
There is a risk of losing the configuration as well as a risk of bricking the unit or losing a feature you have that is eliminated in the update.

We have DAILY threads where someone bricked a camera or NVR because they were updating just for the sake of updating

So the question is does the firmware release notes either add a feature you really need or fix a known problem you have? If not, don't fix what ain't broke.

If it does add a feature you want or need or fixes a known problem, then you have to weight the risks of updating it or not.

Further, 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.
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
Well, I was really asking if there was any known issues...not theoretical issues.

I did the update. Easy peasey. Done, no issues.
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
After some testing...the only thing this update/upgrade broke was my image access. Normally, I grab the images through another scripting tool I wrote using the following URL to the NVR:
http://<NVR-IP>/ISAPI/Streaming/channels/101/picture

But now I get the following response...:

<ResponseStatus version="1.0">
<requestURL>/ISAPI/Streaming/channels/101/picture</requestURL>
<statusCode>6</statusCode>
<statusString>Invalid XML Content</statusString>
<subStatusCode>badXmlContent</subStatusCode>
</ResponseStatus>


I get video streams just fine via RTSP, e.g.
rtsp:/<NVR-IP>:554/Streaming/channels/802

But images, no bueno now...

Did they change the URL for images?
 

Flintstone61

Known around here
Joined
Feb 4, 2020
Messages
6,587
Reaction score
10,894
Location
Minnesota USA
Hopefully somebody with HIK knowledge can help.
Of course were having a laugh in the back channels
It happens too many times.
Can you reverse course?
my HIK based ( nightowl) would stream with much fiddle fooling around, and it was just easier to get a Dahua based NVR to get the Blue Iris compatibility I desired.
My HIK based dvr seemed featureless and locked down....frustrated the hell out of me
But again,,,,you might get lucky and get an answer....
 
Last edited:

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,930
Reaction score
6,778
Location
Scotland
Did they change the URL for images?
I'm sorry, I don't know.

But maybe you could experiment around these strings from the sc_hicore main app from that firmware :

https://%s/picture/Streaming/tracks/%d/
https://%s:%d/picture/Streaming/tracks/%d/
http://%s/picture/Streaming/tracks/%d/
/picture/Streaming/tracks/
http://%s:%d/picture/Streaming/tracks/%d/
/picture
/HikCStor/Picture/Write
/ISAPI/Intelligent/FDLib/pictureUpload
http://%s:%d/picture/Streaming/tracks/%d/?
/PictureByUrl



These are the ISAPI matching strings :

/ISAPI/Security/userCheck
/ISAPI/Security/sessionLogin
/ISAPI/Security/sessionHeartbeat
/ISAPI/ContentMgmt/Storage/backup/auto
/isapiHikStor
/ISAPI/Security/sessionLogin/capabilities
/ISAPI/index
/ISAPI/Security/extern/capabilities
/ISAPI/Security/questionConfiguration
/ISAPI/Security/GUIDFileData
/ISAPI/Security/email/parameter
/ISAPI/Security/email/qrCode
/ISAPI/Security/emailCertification
/ISAPI/description
/ISAPI/Custom/SelfExt/ContentMgmt/ZeroStreaming/channels
/ISAPI/Custom/OpenPlatform/uploadApp
/ISAPI/ContentMgmt/download
/ISAPI/ContentMgmt/InputProxy/ipcConfig
/ISAPI/ContentMgmt/Advertising/importStatus
/ISAPI/PTZCtrl/channels/fisheyelink
/ISAPI/Security/serverCertificate/downloadCertSignReq
/ISAPI/Security/serverCertificate/certificate
/ISAPI/Security/deviceCertificate
/ISAPI/System/configurationData
/ISAPI/System/updateFirmware
/ISAPI/System/upgradeStatus
/ISAPI/System/TwoWayAudio/channels
/ISAPI/System/calibrationData
/ISAPI/System/diagnosedData
/ISAPI/System/Video/inputs/channels
/ISAPI/System/IOT/channelConfig
/ISAPI/Traffic/plateList
/ISAPI/Traffic/channels
/ISAPI/Security/challenge
/ISAPI/System/activate
/ISAPI/Security/questionCertification
/ISAPI/ContentMgmt/search
/ISAPI/ContentMgmt/search/index
/ISAPI/ContentMgmt/search/tracks
rtsp:/localhost/ISAPI/Streaming/channels/%d
http://localhost/ISAPI/Snapshot/channels/%d
/ISAPI/Intelligent/FDLib/pictureUpload
/ISAPI/Intelligent/analysisImage/face
/ISAPI/Intelligent/analysisImage/human
/isapiVoutChan_id
isapi/event/isapi_event.c
isapi/event/isapi_event_do.c
isapi/motded/isapi_motdet.c
isapi/motded/isapi_motdet_do.c
isapi/image/isapi_image.c
isapi/image/isapi_image_do.c
isapi/smd/isapi_smd.c
isapi/smd/isapi_smd_do.c
isapi/thermal/isapi_thermal.c
isapi/intelligent/isapi_intelligent.c
isapi/intelligent/isapi_intelligent_do.c
isapi/system/isapi_system.c
isapi/system/isapi_system_do.c
isapi/token/isapi_token.c
isapi/cloud/isapi_cloud.c
isapi/cloud/isapi_cloud_do.c
isapiStor/comm/isapiStor_root.c
isapiStor/comm/isapiStor_util.c
/ISAPI/System/TwoWayAudio/channels/%d/transData
/isapi_dynStream
/isapi_event_schedules
isapi/auxinfo/isapi_auxinfo.c
isapi/auxinfo/isapi_auxinfo_do.c
isapiStor/hikcstor/isapiStor_hikstor.c
isapiStor/hikcstor/isapiStor_hikstor_do.c
/isapiHikStor?did=%s&bid=%d&pid=%d&ptime=%d
/ISAPI/Image/channels
/ISAPI/Event/triggers/notifications/AudioAlarm
/ISAPI/Image/channels/
/ISAPI/System/TwoWayAudio/channels/
/ISAPI/PTZCtrl/channels/
/ISAPI/Thermal/channels/
/ISAPI/System/Video/inputs/channels/
/ISAPI/Intelligent/channels/
http://%s/ISAPI/Event/triggers/notifications/AudioAlarm/customAudio?format=json
GET /ISAPI/Smart/%s/%u/capabilities
GET /ISAPI/Intelligent/channels/%u/intelliTrace
PUT /ISAPI/Image/channels/%u/%s
GET /ISAPI/Image/channels/%u/%s
PUT /ISAPI/System/Video/inputs/channels/%d/motionDetection
GET /ISAPI/Intelligent/channels/%u/calibration
PUT /ISAPI/Intelligent/channels/%u/calibration
PUT /ISAPI/Intelligent/channels/%u/calibration/verify
PUT /ISAPI/Intelligent/channels/%u/humanRecognition/regions
PUT /ISAPI/Smart/%s/%u
PUT /ISAPI/Smart/%s/%u/regions/%u
GET /ISAPI/Intelligent/channels/%u/humanRecognition/regions
GET /ISAPI/Smart/%s/%u/regions/%u
GET /ISAPI/Smart/%s/%u
PUT /ISAPI/Event/schedules/%s/%s-%d
GET /ISAPI/Event/triggers/notifications/whiteLightAlarm?format=json
GET /ISAPI/Event/triggers/notifications/AudioAlarm?format=json
/ISAPI/Event/triggers/notifications/AudioAlarm?format=json
/ISAPI/Event/triggers/notifications/whiteLightAlarm?format=json
/ISAPI/Event/triggers/notifications/AudioAlarm/trigger?format=json
/ISAPI/Event/triggers/notifications/whiteLightAlarm/trigger?format=json
PUT /ISAPI/Image/channels/%d/supplementLight
GET /ISAPI/Image/channels/%d/capabilities
PUT /ISAPI/System/externalDevice
GET /ISAPI/System/externalDevice
/ISAPI/System/Network/EZVIZ
/ISAPI/System/Capabilities
/ISAPI/System/Network/EZVIZ/capabilities
GET /ISAPI/Event/triggers/notifications/AudioAlarm/customAudioInfo?format=json
GET /ISAPI/Thermal/channels/%u/thermometry/basicParam/capabilities
GET /ISAPI/Thermal/channels/%u/fireDetection/capabilities
GET /ISAPI/Smart/shipsDetection/%u/capabilities
GET /ISAPI/Intelligent/channels/%u/humanRecognition/capabilities
GET /ISAPI/System/Video/inputs/channels/%u/VCAResource/capabilities
GET /ISAPI/Intelligent/channels/%u/capabilities
GET /ISAPI/GIS/channels/%u
GET /ISAPI/Event/triggersCap
GET /ISAPI/Event/triggers/notifications/whiteLightAlarm/capabilities?format=json
GET /ISAPI/Event/triggers/notifications/AudioAlarm/capabilities?format=json
GET /ISAPI/System/Video/inputs/channels/%d/motionDetection/capabilities
GET /ISAPI/Thermal/realtimeThermometry/capabilities
GET /ISAPI/System/externalDevice/capabilities
PUT /ISAPI/Event/schedules/%s/%s-%u
GET /ISAPI/Event/schedules/%s/%s-%u
PUT /ISAPI/Event/triggers/%s-%u
GET /ISAPI/Event/triggers/%s-%u
GET /ISAPI/Streaming/channels/%d/capabilities
GET /ISAPI/System/Video/inputs/channels/%d/motionDetection
not support!GET /ISAPI/System/Video/inputs/channels/ID/motionDetection/capabilities,iRet=%d
GET /ISAPI/Intelligent/channels/%u/AlgParam
GET /ISAPI/System/deviceInfo
GET /ISAPI/System/firmwareCodeV2
not support GET /ISAPI/System/firmwareCodeV2, iRet[%d], chan[%d]
GET /ISAPI/System/firmwareCodeV2 error
GET /ISAPI/Smart/capabilities
/ISAPI/Streaming/channels/<ID>/capabilities XML info[%s]
/ISAPI/Event/notification/alertStream
/ISAPI/System/updateFirmware
/ISAPI/System/configurationData
/ISAPI/System/diagnosedData
/ISAPI/System/factoryReset
/ISAPI/System/IOT/channelConfig
/ISAPI/System/deviceConfiguration
/ISAPI/System/Network/PPPoE
/ISAPI/System/TwoWayAudio/channels
/ISAPI/ContentMgmt/InputProxy/ipcConfig
/ISAPI/Security/serverCertificate/downloadCertSignReq
/ISAPI/Security/userCheck
/ISAPI/Security/sessionLogin
/ISAPI/Security/GUIDFileData
/ISAPI/Security/questionConfiguration
/ISAPI/Security/questionCertification
/ISAPI/ContentMgmt/logSearch/dataPackage/data
/ISAPI/ContentMgmt/download
/ISAPI/Traffic/plateList

 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
Thanks for pulling the strings / paths.

I'll try some of these. But this makes a guy wonder....why in the heck would they change the URLs /paths between releases? What the heck are they thinking...especially if they don't release note it. But then again I'm assuming a lot here :rolleyes:
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
Opened up a support ticket with Hikvision. The only response from them was, who did I buy it from and who am I - installer,owner, reseller, etc.
After that crickets. Nothing from them.

I'm not sure 'who I bought it through' is relevant to my question, which is simply what is the new path/URL after the firmware update? And is this documented anywhere?
For the 30 years I've been a software developer and engineer, the companies I've worked for, we would get roasted from customers if we started randomly changing paths & APIs between software releases...especially if we didn't document it or release note it.
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,550
Location
USA
Not surprised in their response...

You have to remember that the homeowner isn't the Hikvision and Dahua target audience, it is the professional installers, so we cannot purchase directly and thus they will not take your phone call for support related questions or suggestions - they will tell you to talk to the installer you purchased from.

Many people have bought a Hikvision or Dahua from Amazon or some shady foreign website and when they call Hikvision or Dahua for support they basically tell them to go pound salt. We simply are not their intended market to sell to and they will not take your call for support...Lot's of threads here confirming this, including one from a few months ago where someone tried to call for support and they told them sorry talk to your installer....

We are just fortunate to be able to get our hands on these types of cameras and NVRs and a forum like this to help us troubleshoot when needed and ask questions.

You came here asking if there were any risks to updating and we told you there were and you updated anyway and said it was "easy peasey" no problem...then you find out it is like we said that stuff changes and breaks....

For your sake I hope you either figure it out or can rollback the firmware if this is something of importance to you...

And it doesn't help you, but this becomes yet another thread we can point people to asking about updating their firmware...you are right they should do a better job at release notes, but they don't so one shouldn't update something with no release notes for these very reasons...
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
You are right....I think "I told you so is in order". :)

But in principle, I have to disagree. One of the challenges as a software developer, is getting customers to upgrade their software. All software has bugs and vulnerabilities. Our stance (for the last 3 companies I've worked for) has always been, please upgrade, because running the old code you are exposed to a long list of documented bugs that we've already fixed. It drives me crazy when we get customers calling about an issue...and they are running on old code that the new releases have lots of bug fixes listed in the release notes - including the issue they called in about.

It makes a person wonder why they (Hikvision) are so secretive on any of the updates and the release notes just say 'Fix known defects and optimize product performance.' All the companies I've worked for we have to have a bug ID tagged in the release notes and if its a vulnerability, there is a CVE tagged to this. I just don't understand why they can't follow industry standards.

But then again...I've only worked for American software and hardware companies...so maybe that is the difference ;)
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,550
Location
USA
The biggest difference probably between your job and these cameras are the end user.

The issue is most installers are just that - installers - and are not under maintenance contracts with their clients (end user), so most of these systems are never upgraded with newer firmware. All their client cares about is that the video shows up and records.

Further, most will isolate their cameras and NVR from the internet, so usually firmware updates are to fix security vulnerabilities and take away capabilities lol. Since we are not on the internet, the security patch is a moot point.

These manufacturers would just as soon have someone buy a new system than provide fixes in firmware LOL.

It is us crazies that get our hands on these and then do firmware updates and screw up a perfectly working system lol...been there, done that LOL.
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
I was really hoping that with a firmware update I'd get out this need for IE support for the web UI. Its crazy that we are in 2022 and you have firmware that requires ActiveX controls in IE to work....crazy...But I digress...
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,550
Location
USA
Yeah we all wanna see that LOL. Sadly that will be a new model not a firmware update, at least that appears the direction Dahua is going with, so others will probably follow suit. My understanding is that some older chipsets aren't capable of running newer.

Like literally Dahua has a new model out - a bullet version and turret version of the 4K/X. Bullet is old GUI needing plugin and turret is new GUI not needing. They said the chipset differences will prevent the bullet from getting the new GUI.
 

Flintstone61

Known around here
Joined
Feb 4, 2020
Messages
6,587
Reaction score
10,894
Location
Minnesota USA
This just in.....after a reboot, I think Chrome was nagging for an update...( looks like it did it without me)
my older 4108 Amcrest NVR opens in Chrome....and some of the Amcrest 1179ew's open in chrome( not all) and my Dahua (end of Life) 3241-ZAS opens in chrome
the 5442 opened in Chrome....not IE Tab chrome....Straight no condom....Chrome
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
With the firmware update...I can actually play and use the interface with MS Edge now...I don't have to run in IE mode. So that is a good thing...at least progress in the right direction.

Trying Chrome on Mac & Linux... Live View, Playback does not work. I don't have Chrome installed on my Window VM I'm using...so not sure if that is working on this firmware update.

But the darn ISAPI path change is the only thing at this point that is driving me nuts...
 

archjeb

Young grasshopper
Joined
Jan 3, 2020
Messages
37
Reaction score
8
Location
Portland
Figured it out. Using developer tools, you can see where its posting in the configuration page through the web UI.
So instead of http://<NVR-IP>/ISAPI/Streaming/channels/801/picture

it is now (with new firmware)
http://<NVR-IP>/ISAPI/ContentMgmt/StreamingProxy/channels/801/picture

You can still get a list of legitimate channels with the following HTTP Get /ISAPI/Streaming/channels/
But if you want a current JPEG snapshot...you have to use the /ISAPI/ContentMgmt/StreamingProxy/channels/<channel#>/picture

Now why these jokers changed this...is just plain annoying. But at least I can move on to the next project now :)
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,550
Location
USA
Another crisis avoided!

Yep and who knows why they change it LOL.

Probably why the release notes are empty - because they don't even know WTF they are changing :lmao:
 
Top