I'm catching up on this thread and the original post from Andy doesn't appear to have an attachment or link to the firmware mentioned here. His post immediately prior to this one included a Word doc with the download link, but I'm not seeing an attachment or link for this thread. Was it removed, pending verification of the problems being discussed?
IPC-HDW5231R-ZE Rhea V2.800.0000016.0.R.200430 Latest new firmware
- Thread starter EMPIRETECANDY
- Start date
Dramus
Pulling my weight
I had cameras spontaneously going off-line. Since it was all of them I assumed it was a common denominator: Either the NVR or the PoE switch. I eliminated the NVR as being the problem. Replaced the switch. Problems continued. Then it hit me: These problems started about the time I started using line-crossing detection.
Upgraded one camera, the one that had been doing it most, to DH_IPC-HX5X3X-Rhea_MultiLang_NP_Stream3_V2.800.0000016.0.R.200605. That was four weeks ago. That camera has not glitched since. The other three that have line-crossing configured-in still do.
Upgraded one camera, the one that had been doing it most, to DH_IPC-HX5X3X-Rhea_MultiLang_NP_Stream3_V2.800.0000016.0.R.200605. That was four weeks ago. That camera has not glitched since. The other three that have line-crossing configured-in still do.
Dramus
Pulling my weight
Those download links get posted in a really weird manner. I don't understand why he does it that way. You have to download the MS-Word doc, open it, then open the link from there--IIRC.
Hi Andy
A couple of weeks ago and without checking the recent threads posted, I unfortunately got round to updating the FW to version ....16... in one of the two 5231 cameras I bought from you (along with other cameras) back in November 2017. As with other guys, after updating it was OK at first but then had problems.
Taking the lead of Johnevansab, I‘ve just now downgraded it to ver ...13... 2019-12-02 which has Security Baseline =1.4 (whatever that means). It’s working again at the moment.
Are you able to say, please, what is the most recent stable version of firmware that’s compatible with the hardware version of this camera.
A couple of weeks ago and without checking the recent threads posted, I unfortunately got round to updating the FW to version ....16... in one of the two 5231 cameras I bought from you (along with other cameras) back in November 2017. As with other guys, after updating it was OK at first but then had problems.
Taking the lead of Johnevansab, I‘ve just now downgraded it to ver ...13... 2019-12-02 which has Security Baseline =1.4 (whatever that means). It’s working again at the moment.
Are you able to say, please, what is the most recent stable version of firmware that’s compatible with the hardware version of this camera.
Dramus
Pulling my weight
If we're talking about bugs in V2.800.0000016.0.R.200605: When I upgraded one of my 5231's (the only one so far) I did this:
First time in my life I've ever seen a configuration partially restore on anything.
- Saved running configuration
- Cleared camera to defaults "except network IP address, user management and so on"
- Installed upgrade
- Uploaded saved configuration
First time in my life I've ever seen a configuration partially restore on anything.
Let’s get down to specifics: -
Andy - the Camera Model your firmware update is causing uncontrollable Rebooting on is IPC-HFW5831E-ZE meaning 8MP / 4K Resolution, Wide Dynamic Range, StarVis Night Capability, Bullet Style, Motorized Zoom and Focus – that Camera Specification is not going to be Obsolete for a long time – not unless the Sabotaging, Vandalising Firmware 16 “Update” kills the camera first – or will it actually be the Firmware Downgrade that bricks the cameras first?
Wonder if the Re-Booting every 30 or so hours is due to overheating caused by the faulty 16 firmware overworking something till it resets due to overheating – have seen that happen in other electronics that run Firmware - it is winter here now BUT for cameras in summer weather conditions or indoors - how long until the overheating causing firmware kills the cameras? Thus (of course), driving sales of new Generation Dahua Cameras.
Dahua is currently still using the old Microsoft sales approach – “next generation product will solve everything you’ll love it” until one day that style of Microsoft sales terrorism just stopped working – so the Windows 10 brand had to be established pronto (with Windows 10 largely given out as a free upgrade – talk about desperate) and stuck to, so as to turn over a new leaf in the eyes of the (by now justifiably) jaded customer by effectively saying - we will fix it from now on with no more paid Windows version updates required – quite the “U” turn - it is not a question of if BUT when that sales terrorism style of selling the next generation / paid upgrade tactic ceases to be effective.
Last time I checked that same Firmware Package works on 70 something different models of Dahua Camera – strange it is causing problems on both 2MP and 8MP versions, Bullets and Domes makes no difference either.
Andy contrary to your blame shifting suggestion that these Cameras are early production run models from 5 years ago - they are in reality only 2 years old – otherwise Andy it sounds like you are surprised the cameras are still working at all!
OR Andy do you mean that once the (underspecified?) components inside Dahua cameras age a little you sound like you expect the Camera to brick itself at the next Firmware “Update” – actually due to insufficient voltage available INSIDE the camera from the slightly aged (overworked/prematurely aged due to being underspecified?) components so the camera cannot then complete writing the Firmware Update to the 32MB (in this model) Flash ROM (ROM Memory Chips are generally designed to be Read at a Lower Operating Voltage and only Written to at a Higher Programming Voltage) so as to drive sales on the next generation Cameras - tell me it is not so Andy?
Is it really that cynical and self-serving? How were Double 11 sales this year? Singles' Day - Wikipedia
Andy why not share with us your details and references for what exactly changes through a production run of a camera model?
Firmware Downgrade Risks - everyone agrees and accepts that downgrading firmware is even more risky – but bizarrely people only keep going on about Firmware Upgrade risks? How Perverse.
Why would people keep talking about downgrading cameras Firmware as if there were no risk (while simultaneously saying Firmware upgrades are risky) unless they in fact (quietly) upgraded to a disaster of a Firmware Update – are too ashamed / full of pride to admit it - and have thus become expert at downgrading firmware while pretending nothing ever happened (it’s actually quite amusing if you consider their mentality of denial) – Dahua must just love that type of customer that keeps every problem quiet and silently puts up with everything - the oriental proverb of “knowledge makes humble ignorance makes pride” comes to mind – there is no shame to admitting there is a problem and resolving it together in the open.
While also totally forgetting that there are benefits to upgrading Firmware besides (supposedly) improving security which also means not being caught out using outdated old firmware - because were there to be yet another Dahua security breach and we were to be found out using ancient massively out of date and many times superseded firmware that would be OUR fault for not staying on the ball and WE would be to blame.
It doesn’t matter what the rights or wrongs actually are – when Dahua sooner or later has yet another security breach the person responsible for running the latest firmware version cannot be blamed for failing to take timely action by staying up to date with firmware – BUT compare that to the person caught out running initial product release firmware unchanged from 5 years ago (that Andy mentioned is how long this generation of camera have been on sale for) they will get the sack for negligence or get sued for negligence i.e. failing to keep Firmware reasonably up to date due to apparent sloth/fear/laziness.
Firmware Updates are not supposed to be used to drive next generation camera sales by creating basic operating problems - like uncontrollable rebooting - that suspiciously well evade pre-mass-roll-out Firmware testing.
Andy you have said in the past that you are still testing out Firmware before posting it up on this forum – exactly what kind of tests do you carry out? For how long? What is the definition of pass or fail during these firmware tests? Exactly what tests did you do on this faulty firmware 16?
Besides in the past few generations of firmware the more memorable improvements on these cameras have been 1. Massively improved WDR performance so suddenly the same cameras in the same lighting conditions outdoors no longer change to Black and White / Monochrome mode at night – meaning full Colour Video all night long 2. Scheduler to apply different camera settings for Day and different camera settings for Night Improved and made to work properly 3. Cameras no longer entirely dependent on Browser Plug-In to view camera live images etc. in a web browser – now works with and without Plug-In which (if memory serves) somebody on this forum said is important re Microsoft etc. depreciating Flash
Now Andy specifically to Downgrade (against all the manufacturers advice) – How Exactly?
For instance if you look here IP Cam Talk Cliff Notes says “If you are unable to install older firmware, or inadvertently brick your camera” then go to Dahua IPC EASY unbricking / recovery over TFTP but what is left unsaid is what exactly were you doing that you discovered that “you are unable to install older firmware” so specifically what is that first unexplained step that failed to downgrade the cameras firmware?
BOM Firmware ? Explain BOM (Bill of Materials??? - Confirm exactly what BOM abbreviation means in this case) how does BOM affect and/or apply to the camera firmware downgrade that you are now suggesting Andy.
Cameras are complex equipment? Compared to what? A Flashlight?
Nowadays IP Cameras are so ubiquitous and not at all new – IP Cameras are very mature products by now (and after all we are talking about a very basic function i.e. not uncontrollably re-booting) and are NOT electronically complex compared to say a mobile telephone with its multiple microwave RF input and output stages for all the relevant different frequencies of Mobile radio bands (essentially a microwave SDR) plus a mobile phones separate Wi-Fi and Bluetooth Radio Transceivers and also the time division multiplexing needed to operate within mobile radio cells – and all of that has to work together without one radio signal blocking another – add to that Li-Poly Battery charging control circuitry - at surprisingly high current levels for such a small device - and associated buck and boost control to supply stable power from battery to mobile phone – add a pair of cameras (far higher resolution than most security cameras) on the mobile phone plus a pair of microphones and speakers and the A to D conversion of all of that plus the touchscreen UI and all of a sudden an IP Camera is really quite basic compared to a Mobile Phone / Smartphone of today – so following an update with faulty firmware to a relatively simple (by today’s standards) ubiquitous IP Camera – nobody is going to be impressed nor thank anyone if the updated faulty firmware suddenly cannot even perform the most basic function of keeping the camera running non-stop without (presumably crashing and) rebooting every 30 or so hours. Especially when the 30 Hour Reboot bug only first rears it ugly head after a cold reboot – talk about a (suspiciously) very well-hidden firmware bug.
Version 15 was stable on those cameras until Andy said Important Update go to 16 and after that here we all are in various different versions of camera hell – so to fix this faulty firmware - where is version 17 plus?
Andy - the Camera Model your firmware update is causing uncontrollable Rebooting on is IPC-HFW5831E-ZE meaning 8MP / 4K Resolution, Wide Dynamic Range, StarVis Night Capability, Bullet Style, Motorized Zoom and Focus – that Camera Specification is not going to be Obsolete for a long time – not unless the Sabotaging, Vandalising Firmware 16 “Update” kills the camera first – or will it actually be the Firmware Downgrade that bricks the cameras first?
Wonder if the Re-Booting every 30 or so hours is due to overheating caused by the faulty 16 firmware overworking something till it resets due to overheating – have seen that happen in other electronics that run Firmware - it is winter here now BUT for cameras in summer weather conditions or indoors - how long until the overheating causing firmware kills the cameras? Thus (of course), driving sales of new Generation Dahua Cameras.
Dahua is currently still using the old Microsoft sales approach – “next generation product will solve everything you’ll love it” until one day that style of Microsoft sales terrorism just stopped working – so the Windows 10 brand had to be established pronto (with Windows 10 largely given out as a free upgrade – talk about desperate) and stuck to, so as to turn over a new leaf in the eyes of the (by now justifiably) jaded customer by effectively saying - we will fix it from now on with no more paid Windows version updates required – quite the “U” turn - it is not a question of if BUT when that sales terrorism style of selling the next generation / paid upgrade tactic ceases to be effective.
Last time I checked that same Firmware Package works on 70 something different models of Dahua Camera – strange it is causing problems on both 2MP and 8MP versions, Bullets and Domes makes no difference either.
Andy contrary to your blame shifting suggestion that these Cameras are early production run models from 5 years ago - they are in reality only 2 years old – otherwise Andy it sounds like you are surprised the cameras are still working at all!
OR Andy do you mean that once the (underspecified?) components inside Dahua cameras age a little you sound like you expect the Camera to brick itself at the next Firmware “Update” – actually due to insufficient voltage available INSIDE the camera from the slightly aged (overworked/prematurely aged due to being underspecified?) components so the camera cannot then complete writing the Firmware Update to the 32MB (in this model) Flash ROM (ROM Memory Chips are generally designed to be Read at a Lower Operating Voltage and only Written to at a Higher Programming Voltage) so as to drive sales on the next generation Cameras - tell me it is not so Andy?
Is it really that cynical and self-serving? How were Double 11 sales this year? Singles' Day - Wikipedia
Andy why not share with us your details and references for what exactly changes through a production run of a camera model?
Firmware Downgrade Risks - everyone agrees and accepts that downgrading firmware is even more risky – but bizarrely people only keep going on about Firmware Upgrade risks? How Perverse.
Why would people keep talking about downgrading cameras Firmware as if there were no risk (while simultaneously saying Firmware upgrades are risky) unless they in fact (quietly) upgraded to a disaster of a Firmware Update – are too ashamed / full of pride to admit it - and have thus become expert at downgrading firmware while pretending nothing ever happened (it’s actually quite amusing if you consider their mentality of denial) – Dahua must just love that type of customer that keeps every problem quiet and silently puts up with everything - the oriental proverb of “knowledge makes humble ignorance makes pride” comes to mind – there is no shame to admitting there is a problem and resolving it together in the open.
While also totally forgetting that there are benefits to upgrading Firmware besides (supposedly) improving security which also means not being caught out using outdated old firmware - because were there to be yet another Dahua security breach and we were to be found out using ancient massively out of date and many times superseded firmware that would be OUR fault for not staying on the ball and WE would be to blame.
It doesn’t matter what the rights or wrongs actually are – when Dahua sooner or later has yet another security breach the person responsible for running the latest firmware version cannot be blamed for failing to take timely action by staying up to date with firmware – BUT compare that to the person caught out running initial product release firmware unchanged from 5 years ago (that Andy mentioned is how long this generation of camera have been on sale for) they will get the sack for negligence or get sued for negligence i.e. failing to keep Firmware reasonably up to date due to apparent sloth/fear/laziness.
Firmware Updates are not supposed to be used to drive next generation camera sales by creating basic operating problems - like uncontrollable rebooting - that suspiciously well evade pre-mass-roll-out Firmware testing.
Andy you have said in the past that you are still testing out Firmware before posting it up on this forum – exactly what kind of tests do you carry out? For how long? What is the definition of pass or fail during these firmware tests? Exactly what tests did you do on this faulty firmware 16?
Besides in the past few generations of firmware the more memorable improvements on these cameras have been 1. Massively improved WDR performance so suddenly the same cameras in the same lighting conditions outdoors no longer change to Black and White / Monochrome mode at night – meaning full Colour Video all night long 2. Scheduler to apply different camera settings for Day and different camera settings for Night Improved and made to work properly 3. Cameras no longer entirely dependent on Browser Plug-In to view camera live images etc. in a web browser – now works with and without Plug-In which (if memory serves) somebody on this forum said is important re Microsoft etc. depreciating Flash
Now Andy specifically to Downgrade (against all the manufacturers advice) – How Exactly?
For instance if you look here IP Cam Talk Cliff Notes says “If you are unable to install older firmware, or inadvertently brick your camera” then go to Dahua IPC EASY unbricking / recovery over TFTP but what is left unsaid is what exactly were you doing that you discovered that “you are unable to install older firmware” so specifically what is that first unexplained step that failed to downgrade the cameras firmware?
BOM Firmware ? Explain BOM (Bill of Materials??? - Confirm exactly what BOM abbreviation means in this case) how does BOM affect and/or apply to the camera firmware downgrade that you are now suggesting Andy.
Cameras are complex equipment? Compared to what? A Flashlight?
Nowadays IP Cameras are so ubiquitous and not at all new – IP Cameras are very mature products by now (and after all we are talking about a very basic function i.e. not uncontrollably re-booting) and are NOT electronically complex compared to say a mobile telephone with its multiple microwave RF input and output stages for all the relevant different frequencies of Mobile radio bands (essentially a microwave SDR) plus a mobile phones separate Wi-Fi and Bluetooth Radio Transceivers and also the time division multiplexing needed to operate within mobile radio cells – and all of that has to work together without one radio signal blocking another – add to that Li-Poly Battery charging control circuitry - at surprisingly high current levels for such a small device - and associated buck and boost control to supply stable power from battery to mobile phone – add a pair of cameras (far higher resolution than most security cameras) on the mobile phone plus a pair of microphones and speakers and the A to D conversion of all of that plus the touchscreen UI and all of a sudden an IP Camera is really quite basic compared to a Mobile Phone / Smartphone of today – so following an update with faulty firmware to a relatively simple (by today’s standards) ubiquitous IP Camera – nobody is going to be impressed nor thank anyone if the updated faulty firmware suddenly cannot even perform the most basic function of keeping the camera running non-stop without (presumably crashing and) rebooting every 30 or so hours. Especially when the 30 Hour Reboot bug only first rears it ugly head after a cold reboot – talk about a (suspiciously) very well-hidden firmware bug.
Version 15 was stable on those cameras until Andy said Important Update go to 16 and after that here we all are in various different versions of camera hell – so to fix this faulty firmware - where is version 17 plus?
Sorry I don't buy that as a general statement. A lot of the features are new. New features leads to new bugs. Fixing old features leads to new bugs. Eliminating the browser plugin requirement leads to new bugs. Revisions to the production hardware leads to new bugs. I don't like it that customers become testers. If I could change that I would. The reality is if you want to use the product you're stuck living with it.
Dramus
Pulling my weight
Written a lot of software have you? Vision software, in particular?
IAmATeaf
Known around here
Jesus why do you seem to be blaming Andy, take your gripes to Dahua direct and see how far you get!
As far as upgrading/downgrading, there’s always a risk but instead of sniping about the reboots, go back to a previous working version of the firmware that worked.
As far as upgrading/downgrading, there’s always a risk but instead of sniping about the reboots, go back to a previous working version of the firmware that worked.
New Firmware for IPC-HX5X3X-Rhea_MultiLang_PN_Stream3_V2.800.0000013.0.R.191202.zip
Hey guys, Here is the latest new firmware for these models, there has a little update for some bugs, details please check the Release Note. This new firmware is a important update for Fixing Security Vulnerabilities General one is without dahua logo DH one is with dahua logo. Models...
Use back this one.
looney2ns
IPCT Contributor
Gee, rant much?
Stop blaming Andy, he is just a seller of their product. Dahua is responsible for the state of the firmware. Andy does his best to try to get Dahua to fix things, but it's ultiimately out of his hands.
Relax.
Hello, did you find a download link in the end? Like you, I'm looking but cannot find anything.
Thank you.
Empiretecandy posted a download link for the stable version 13 in this thread on15 November. He also pointed out that it’s on Dahua’s website. Works fine in my 5231. Use that if your camera has problems.
Thank you. I've updated a couple of cameras to version 16 (I think) from the Dahua website today. All good so far. Fingers crossed.
Why do you say, "I think", rather than looking to see what you just installed? If you really got it from Dahua's website today, then I suspect you probably installed 13 (not 16). That's what I see on Dahua's website today, and is the version shown in the screenshot of Andy's post 5 messages above this one. If I'm wrong, then I apologize for calling you out on this, but I fear that your post implying that version 16 is ok could be harmful to others if your post is wrong.
Thank you for the agressive comment. Great welcome for a new user... Whatever version it was, I could not check at the time. If Dahua's website has version 13 then that's what's installed.
Given the welcome I'll be deleting my account.
Wow. Someone is a bit sensitive. You say you, "could not check at the time", yet you still posted here on a thread with numerous posts about v16 potentially being dangerous. You could have waited to post on this forum until you could check, but you chose not to.
I even apologized in advance if I was wrong, and I explicitly took time to check Dahua's website to see if v16 was public before making my post. As a new user, you probably came here because you wanted good, helpful information, and I'm simply trying to maintain that quality for all users.
I even apologized in advance if I was wrong, and I explicitly took time to check Dahua's website to see if v16 was public before making my post. As a new user, you probably came here because you wanted good, helpful information, and I'm simply trying to maintain that quality for all users.
Hi Carteriii
I think personally, that your reply to the unpleasant one! Was very helpful and indeed not aggressive in any way. Sometimes you get these twits that you try and assist, and all you get back is an ungrateful berk! Who thinks they know best, and indeed they do not.
I think personally, that your reply to the unpleasant one! Was very helpful and indeed not aggressive in any way. Sometimes you get these twits that you try and assist, and all you get back is an ungrateful berk! Who thinks they know best, and indeed they do not.
I updated my 5231R-ZE to v16.
The cam seems to be working fine, but I notice that I can no longer use Blue Iris (5.3.2.11) to adjust the varifocal zoom on the camera (which I like to do once in a while as site conditions change). See the screenshot attached. I go to, for example, "Zoom in" and the cam does not respond. Instead, I have to do the zoom adjustment by logging into the cam directly via its web interface.
At this point, I can't determine if it was the firmware upgrade that disabled Blue Iris' ability to adjust zoom, or if perhaps I unwisely changed a setting while logged into the Dahua cam to do the upgrade? (I did tweak some Dahua settings.)
Are others still able to control zoom via Blue Iris following the upgrade to v16?
The cam seems to be working fine, but I notice that I can no longer use Blue Iris (5.3.2.11) to adjust the varifocal zoom on the camera (which I like to do once in a while as site conditions change). See the screenshot attached. I go to, for example, "Zoom in" and the cam does not respond. Instead, I have to do the zoom adjustment by logging into the cam directly via its web interface.
At this point, I can't determine if it was the firmware upgrade that disabled Blue Iris' ability to adjust zoom, or if perhaps I unwisely changed a setting while logged into the Dahua cam to do the upgrade? (I did tweak some Dahua settings.)
Are others still able to control zoom via Blue Iris following the upgrade to v16?
