- Mar 28, 2017
- 19
- 11
Probably my first pure rant thread I have ever posted. After working in IT for 30 years, I usually was reading other people's rants about something I had worked on. I am retired now, so my turn! 
I am at the point where I am so frustrated and disappointed in the Dahua equipment that I have purchased. Specifically about the brokenness that seems to permeate each firmware update. 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. 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?
Let me give you some examples. I recently updated my NVR that I had purchased from Andy in 2017 (NVR608-32-4KS2) in attempt to get better browser support. 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. So after installing the latest firmware, the NVR now supports using a chrome plugin. Though the chrome support does not allow any IVS zones to be drawn using the plugin on OSX. The GUI on the NVR did get a fair bit nicer, so that was a plus. 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 previous version of the NVR firmware had stable RTSP, but not this version.
I have some SD6AL245U-HNI PTZ cameras. Again their browser requirements were ancient and doing any updates on them was NVR GUI only. 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. I decided that the PTZ's would be much better if their web GUI was accessible. I contacted Andy to get the latest firmware for the PTZ's. 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 decided to try it anyway, because I use presets triggered through IVS and could live without auto tracking. 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. You click to draw and the drawn lines are anchored at a different part of the image. So useless for configuring IVS in the web GUI. The auto tracking is indeed broken. It looks at the sky and it's feet more than anything of interest. The real issue I have with the new firmware, is that the Idle Timer function is busted. The camera would not return to the Idle preset. This brokenness is common, so I setup a Timed Task to move to the idle preset. That worked fine ... until it doesn't. The cameras just stick on a preset and fail to move back to the idle preset. This totally breaks my chosen method of using over watch camera's IVS rules to move the PTZ's to presets. Why did my work around stop working? No idea. The only change I have made is to cut the camera's off from phoning home with a FW rule. I have been planning to move them onto their own VLAN and decided to put a FW rule in place in the meantime, and the issue started after that. Is this new bug related to not being able to phone home? No idea, but I will disable the new rule for a few days to see if the issue goes away.
I should also mention, I don't blame Andy for any of these issues. He is helpful where he can be. The real issue is that Dahua does not seem to have a good handle on basic software development processes. The whole state of Dahua support leaves me demoralized. They have to be able to do better than this.

I am at the point where I am so frustrated and disappointed in the Dahua equipment that I have purchased. Specifically about the brokenness that seems to permeate each firmware update. 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. 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?
Let me give you some examples. I recently updated my NVR that I had purchased from Andy in 2017 (NVR608-32-4KS2) in attempt to get better browser support. 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. So after installing the latest firmware, the NVR now supports using a chrome plugin. Though the chrome support does not allow any IVS zones to be drawn using the plugin on OSX. The GUI on the NVR did get a fair bit nicer, so that was a plus. 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 previous version of the NVR firmware had stable RTSP, but not this version.
I have some SD6AL245U-HNI PTZ cameras. Again their browser requirements were ancient and doing any updates on them was NVR GUI only. 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. I decided that the PTZ's would be much better if their web GUI was accessible. I contacted Andy to get the latest firmware for the PTZ's. 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 decided to try it anyway, because I use presets triggered through IVS and could live without auto tracking. 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. You click to draw and the drawn lines are anchored at a different part of the image. So useless for configuring IVS in the web GUI. The auto tracking is indeed broken. It looks at the sky and it's feet more than anything of interest. The real issue I have with the new firmware, is that the Idle Timer function is busted. The camera would not return to the Idle preset. This brokenness is common, so I setup a Timed Task to move to the idle preset. That worked fine ... until it doesn't. The cameras just stick on a preset and fail to move back to the idle preset. This totally breaks my chosen method of using over watch camera's IVS rules to move the PTZ's to presets. Why did my work around stop working? No idea. The only change I have made is to cut the camera's off from phoning home with a FW rule. I have been planning to move them onto their own VLAN and decided to put a FW rule in place in the meantime, and the issue started after that. Is this new bug related to not being able to phone home? No idea, but I will disable the new rule for a few days to see if the issue goes away.
I should also mention, I don't blame Andy for any of these issues. He is helpful where he can be. The real issue is that Dahua does not seem to have a good handle on basic software development processes. The whole state of Dahua support leaves me demoralized. They have to be able to do better than this.