Thanks for confirming.
New G5 camera firmware V5.7.19 build 241207 available on some product pages
- Messages
- 3,603
- Points
- 113
They've changed it around and split everything over different pages - unnecessary and difficult to navigate. Events is there for Basic events such as motion, Smart Events (Intrusion, Line Crossing etc) are in the VCA menu.
Just update one of yours - it takes two mins to update and if you don't like it, two mins to downgrade again - nothing lost/no risk (unlike an NVR where you may have to reprogram from scratch)
I hope this does not affect our disks too on newer G5 firmwares:
I also found this:
ipcamtalk.com
Happy New Year to all
I also found this:
VCA search not working - No Intelligent Record File
I recently installed a new Seagate ST4000VX013 4TB SkyHawk HDD in my 7608NI/I2-8P NVR alongside the original Seagate 2TB SV2000 drive and after recommissioning the unit found that I could no longer carry out VCA Smart Event searches using iVMS4200. When trying to retrospectively review VCA...
Happy New Year to all
- Messages
- 3,603
- Points
- 113
Where did that info come from - camera or NVR release notes? It's not very clear. Point 2 refers to the table and listed models so that's fine. Point 1 "IoT model HDD not compatible" - how are we defining an"IoT model" without model codes. In my own NVR I have two Seagate Surveillance/Skyhawk drives. One is a standard ST4000VX007 (not the 013 in the table); the other is a ST10000VE0008 model which is one of the AI versions. Search "IoT HDD" on Google and all I found was a Hikvision document for their own drives.I hope this does not affect our disks too on newer G5 firmwares:
View attachment 12220 View attachment 12221
I also found this:
VCA search not working - No Intelligent Record File
I recently installed a new Seagate ST4000VX013 4TB SkyHawk HDD in my 7608NI/I2-8P NVR alongside the original Seagate 2TB SV2000 drive and after recommissioning the unit found that I could no longer carry out VCA Smart Event searches using iVMS4200. When trying to retrospectively review VCA...
Happy New Year to all
The hard drive compatibility is so specific. I've bought a stack of Seagate Surveillance drives over the years and as an example the 4TB version will always have a part code starting ST4000VX--- but there's a good chance that they will be different. I have the 007 in my system, the 005 and 013 (which will be visually identical) are in the non compatible list.
- Messages
- 3,603
- Points
- 113
Yeah I'm just going through it now. You would think they'd do it an an spreadsheet to make it searchable with a few clicks...
- Messages
- 3,603
- Points
- 113
I can see that I've installed at least one drive on an installation thats in the incompatible list...and that is a 4TB Seagate Surveillance model which would be expected to be compatible and recommended. The issue is that the compatible list is always out of date.I am on SSDs and starting to be suspicious...
To put this all into context:
1 - If you have one of the disks in the table at the start of the document (that you posted) it will not work correctly with Dual VCA in ANY model.
2 - If the disk you have in your NVR/DVR is listed in the relevant section for your NVR/DVR model it is compatible and has been tested by Hikvision.
3 - If the disk you have in your NVR/DVR is NOT listed in the relevant section for your NVR/DVR model, it doesn't necessarily mean that it's incompatible. Neither of my disks are listed for my model and I've had no issues whatsoever.
Last edited:
The other thing I've never messed around with is Advanced Configuration > False Alarm Filtering. I'm not sure what difference there is between selecting 'General Scene' or 'Distant View'
Hello. Do you know what the differences are?
- Messages
- 3,603
- Points
- 113
@alfaclvi has done most testing with these issues. It affects the searching on an NVR for VCA - searching by rule/Smart search, or enabling dual VCA search. It has no effect on events configured in the camera, it's when you're searching for something retrospectively by drawing a line or grid on screen (which should include all motion regardless of whether the Human/Vehicle filters are set in the camera event setup). The issue seems to be that the camera either no longer sends the event metadata or it's not compliant in some way with the searching - no results are found.
I've just tested (finished 10 mins ago) 5.7.19, 5.7.18, 5.7.17 and 5.7.15 with a G5 camera (DS-2CD2387G2H-LIU) that views the busy road outside my home. As alfaclvi has indicated - the function is broken with last working version being 5.7.15 (newest build of 5.7.15). When searching only that version returned any results (event markers in timeline) when a line was drawn across or a grid drawn covering the busy road. All newer versions found nothing.
I'm beginning to think the developers have rewritten some logic for the VCA. Maybe we need to be on the latest camera and NVR FW for these functions to talk properly?
- Messages
- 3,603
- Points
- 113
Funny you should say that...For the brief time I was using 5.04.020 on the M series NVR, despite the issues that forced me to roll back, I think that the VCA search with 5.7.18 of the G5 was working but I can't be 100%. So you could be right and the issues with the VCA search is that teh NVR firmware is lagging behind updates in the camera. The said these issues go back to the release of 5.7.17 on April 24th. if some change is needed to the NVRs then it's taking some time....
Yeah I would bet on it at this point... Horrible release plan and release notes if that's the case.
Honestly the same goes for Hik-Connect. They've updated it 7 times within the last month with the same releases notes. However, I've noticed changes in the app different than the release notes. Some specifically with the NVR which lead me to believe it has something to do with the new ports being opened that was mentioned the 5.04.020 thread.
Hopefully Hikvision can get these all aligned before the Chinese new year! Otherwise, I'm not going to be too happy with Hikvision... (as they are unresponsive during that time)
- Messages
- 3,603
- Points
- 113
It seems as though more effort should go into getting the firmware right. I agree regarding HK. I actually check the App Store each morning for HK and HPP updates - more often than not there's an update waiting. My phone is set to auto update but they never come through immediately.
Just to be sure once again, I installed an WD 1TB HDD in place of my previous SSDs in case of incompatibility. There is no change in Motion VCA search and in Smart VCA search by Rules. Nothing is found on my NXI-K Playback Normal or Event.
Unfortunately the same thing happens if VCA Events are set to be By NVR(NXI is Acusense) and not By Camera. But I cannot remember if this happened with previous NVR and camera firmwares. Also never used that since all cameras are Acusense.
What I cannot understand is that this is a 6 to 7 months old issue and it's impossible not to be known to them. So I believe they are never going to fix, same way they never fixed the Pre-Record issue on many NVRs. By saying this, I remember why I started to use the By Rules search which was almost perfect for me. The simple Event Playback, always bypassed the moment that the event started for about 3 to 5 seconds. So almost all times, this event was lost from the timeline marker. The only way to find was to disable Skip Normal Videos and go a few seconds back. The settings about the Pre and Post record on Schedule Continuous Recording, never worked. On the other hand, the Normal Playback did not have Motion Search...
And finally, this way of search(by rules) became a Use-habit for me, as the say on every new Release Notes : "Also, we are sorry for any possible inconvenience of use-habit changes caused by this action"
I believe they are working seriously only on iDS NVRs and the rest are for experimental purposes. Possibly by students authors. They don't care.
This way we will soon become EX-Users instead of End-Users.....
Unfortunately the same thing happens if VCA Events are set to be By NVR(NXI is Acusense) and not By Camera. But I cannot remember if this happened with previous NVR and camera firmwares. Also never used that since all cameras are Acusense.
What I cannot understand is that this is a 6 to 7 months old issue and it's impossible not to be known to them. So I believe they are never going to fix, same way they never fixed the Pre-Record issue on many NVRs. By saying this, I remember why I started to use the By Rules search which was almost perfect for me. The simple Event Playback, always bypassed the moment that the event started for about 3 to 5 seconds. So almost all times, this event was lost from the timeline marker. The only way to find was to disable Skip Normal Videos and go a few seconds back. The settings about the Pre and Post record on Schedule Continuous Recording, never worked. On the other hand, the Normal Playback did not have Motion Search...
And finally, this way of search(by rules) became a Use-habit for me, as the say on every new Release Notes : "Also, we are sorry for any possible inconvenience of use-habit changes caused by this action"
I believe they are working seriously only on iDS NVRs and the rest are for experimental purposes. Possibly by students authors. They don't care.
This way we will soon become EX-Users instead of End-Users.....
I've worked on and installed a lot if iDS cams. Especially the "iDS-2CD8A86G0-XZHSY 1050/4" and the "iDS-2CD7587G0-XZHSY." Those two I have really got to understand and they have had their fair share of FW issues last year (2024). I just had to make countless phone calls to Hikvision USA to get it sorted out. This is really frustrating because I don't get paid to do their quality assurance and it's time consuming. Especially, clients could potentially blame it on me... This is why I don't do FW upgrades until I test everything out that I need and am using.
Trust me, I'm not anti fw updates. I prefer everything to be on the latest fw for feature and security updates. It's needed in the world we live in today.
The thing that I found out from talking to Hikvision USA is that communication is poor and nothing is documented. They're having to find out everything themselves as well...
I don't believe that the specific issue it's a matter of rewritten logic. For example, the SDcard of the G5 on v5.7.17, v5.7.18 and v5.7.19 records every kind of event, motion or smart and nothing escapes. Also, if set so in Events Configuration, the Events that we want to give notifications, are precisely recorded as files and we can find them by using the Search tab on NVR GUI or by simply pressing the Play button on Event Playback tab(all of them).
It's just as, either the NVRs do not understand the "new" Dual VCA of G5s or the G5 filters what to send(only Human and Vehicle). But this is out of the VCA meaning and usage....
