
You click to draw and the drawn lines are anchored at a different part of the image.

So the new firmware went in, the camera's now support Chrome, again using a plugin, but the Chrome support has a bug where the IVS zones are drawn with an offset. I decided to try it anyway, because I use presets triggered through IVS and could live without auto tracking. The loaded firmware was from 2017, and Andy only had 1 newer firmware available, and it came with a warning, auto tracking may be busted. I contacted Andy to get the latest firmware for the PTZ's. I decided that the PTZ's would be much better if their web GUI was accessible. I had updated my collection of IPC-HDW5231R-ZE units, and they now fully support Firefox and I am assuming other browsers, no plugin required. Again their browser requirements were ancient and doing any updates on them was NVR GUI only. The previous version of the NVR firmware had stable RTSP, but not this version. However the RTSP support in this version is busted in that after about 60 minutes, it freezes and sends the same unchanging frame from that point on. The GUI on the NVR did get a fair bit nicer, so that was a plus. Though the chrome support does not allow any IVS zones to be drawn using the plugin on OSX.

So after installing the latest firmware, the NVR now supports using a chrome plugin.
#Xeoma devlopment plan windows
Most of the Dahua products originally required IE, and not having a single Windows box on hand, makes it problematic when hardware requires outdated IE versions. I recently updated my NVR that I had purchased from Andy in 2017 (NVR608-32-4KS2) in attempt to get better browser support. Which begs the question, why? Dahua's core business is security, traditionally involving security cameras, so how do they roll out firmware updates that break basic features in their installed base of products? Do they not have a QA department? Have they not heard of regression testing? This is something that I have watched play out time and again in the forum as people post about their Dahua problems and people try to help guide them to a version of the firmware that does not have that particular bug, but I can assure you, comes with new and unexpected bugs. Specifically about the brokenness that seems to permeate each firmware update. I am at the point where I am so frustrated and disappointed in the Dahua equipment that I have purchased. After working in IT for 30 years, I usually was reading other people's rants about something I had worked on.

Probably my first pure rant thread I have ever posted.
