As people may have read here I have had issues with the latest Hikvision I series NVR firmware causing the red check marks to stop working in the web interface of the NVR.
I have recently tried using iVMS-4200 connected to my I series NVR and using the remote playback funtion to search for motion detection events. I note that there are some motion events that iVMS-4200 picks up that are not shown in the Web interface, even though I have rolled back firmware to 4.1.64 NVR firmware, yet others appear in both. The source of data in both cases is the same NVR. in 4.1.64 red marks do work to indicate motion detection in the web interface - so I am puzzled as to why iVMS-4200 shows more events than the web interface.
Since Hikvision sells this solution as a security system, I really think it's time they took these bugs seriously and fixed them once and for all - I do not think it is acceptable that a security solution is so hap hazard in these functions, nor do I think it unreasonable to expect motion detection events to be consistent across methods of accessing the same NVR.
Would it be possible to get more updates from Hikvision on what they are doing in this area please? Is there a formal bug tracking number for this issue?
Today's point sounds different but related.
I have recently tried using iVMS-4200 connected to my I series NVR and using the remote playback funtion to search for motion detection events. I note that there are some motion events that iVMS-4200 picks up that are not shown in the Web interface, even though I have rolled back firmware to 4.1.64 NVR firmware, yet others appear in both. The source of data in both cases is the same NVR. in 4.1.64 red marks do work to indicate motion detection in the web interface - so I am puzzled as to why iVMS-4200 shows more events than the web interface.
Since Hikvision sells this solution as a security system, I really think it's time they took these bugs seriously and fixed them once and for all - I do not think it is acceptable that a security solution is so hap hazard in these functions, nor do I think it unreasonable to expect motion detection events to be consistent across methods of accessing the same NVR.
Would it be possible to get more updates from Hikvision on what they are doing in this area please? Is there a formal bug tracking number for this issue?
Today's point sounds different but related.