IPC-HDW5231R-ZE Rhea V2.800.0000016.0.R.200430 Latest new firmware

zape

Getting the hang of it
Joined
Sep 21, 2017
Messages
221
Reaction score
69
I asked dahua engineer,
Hi Andy,
I didn't see if you have the answer posted here.
What was the dahua response to the question on this suspicious network activity?
 

spammenotinoz

Getting comfortable
Joined
Apr 4, 2019
Messages
345
Reaction score
274
Location
Sydney
Hi, I applied this Firmware on 1 cam, before reading the comments. I am holding off on the rest to see, but for NOW my camera is Good "NOT REBOOTING" and have not experienced any unwanted behaviour.
I do typically find that H.265 performance with VBR has improved with each firmware revision, such that now I happily have moved from CBR to VBR without artifacting. I think it was 15 that fixed VBR artifacting for me, so I try and keep the cams up-to-date even if they are isolated.

Device TypeIPC-HDW5831R-ZE
System VersionV2.800.0000016.0.R, Build Date: 2020-06-05

As standard practise though, I disable any and all features\services I am not using so perhaps this is reducing load.
This is a summary of what I have disabled in-case that helps;

Network
PPPoE
DDNS
UPnP
SNMP
Bonjour
Multicase
Auto Register
802.1x
Access Platform -> P2P
Access Platform -> RTMP

Event
IVS
Face Detection

System -> Safety
SSH
Multicast/Broadcast Search
CGI Service
Genetec Service
Audio and Video Transmission Encryption
RTSP over TLS
Mobile Push

I am running Main and Sub-Stream as shown below at 14fps. Cameras are warm running H.265 but that was always the case with the factory firmware and somewhat expected.
1611105282818.png

I check the camera logs, filtering by SYSTEM looking for the "Start Up" event, to determine if the camera has been rebooting.
I have Auto maintain disabled, and not set to daily or weekly reboots, but may go back to weekly once I know the camera is stable. But so far no issues.

Curious though, I may need to enable SNMP but does anyone know of a tool or way to check the CPU\Memory utilisation of these Cameras? Would be good to check between F\W revisions.
 
Last edited:

Wael

Getting the hang of it
Joined
May 9, 2019
Messages
125
Reaction score
33
Location
California
I believe I have confirmed an IVS bug in this firmware. Normally when a tripwire or intrusion zone is triggered, your blue tripwire or intrusion lines will flash red and green indicating they have been triggered. In this firmware it appears to not be working. Meaning that the IVS rules themselves work but the red and green flashing lines don’t, making it a bit difficult to determine the exact moment of triggering. Rolling back to a previous release has fixed the issue for me.
 

spammenotinoz

Getting comfortable
Joined
Apr 4, 2019
Messages
345
Reaction score
274
Location
Sydney
I believe I have confirmed an IVS bug in this firmware. Normally when a tripwire or intrusion zone is triggered, your blue tripwire or intrusion lines will flash red and green indicating they have been triggered. In this firmware it appears to not be working. Meaning that the IVS rules themselves work but the red and green flashing lines don’t, making it a bit difficult to determine the exact moment of triggering. Rolling back to a previous release has fixed the issue for me.
Outside of the IVS bug, any issue with the cameras rebooting\crashing as per other users here?
 

Wael

Getting the hang of it
Joined
May 9, 2019
Messages
125
Reaction score
33
Location
California
Outside of the IVS bug, any issue with the cameras rebooting\crashing as per other users here?
Personally I have not experienced any rebooting or other issues with this firmware. I have it loaded on 9 cameras and have been running it for a couple months without any other issues.
 

Dramus

Pulling my weight
Joined
May 7, 2019
Messages
323
Reaction score
229
Location
New Jersey
@EMPIRETECANDY: Will there be another firmware update for these cameras, or was 16 the last? Holding off updating the rest of my cameras as I had thought you'd written there'd be another update. Thanks!
 

tibimakai

Known around here
Joined
May 8, 2017
Messages
1,005
Reaction score
513
Location
Los Angeles
I have just bricked my wedge camera. The 5231R-Z went well(in the past, a couple more went well), but the wedge got bricked. How can I recover it?
It shows up on the network(router).
 
Last edited:

Wael

Getting the hang of it
Joined
May 9, 2019
Messages
125
Reaction score
33
Location
California
Do a search for “unbricking” in this forum. There are a couple long threads regarding UART TFTP methods of unbricking.
 

tibimakai

Known around here
Joined
May 8, 2017
Messages
1,005
Reaction score
513
Location
Los Angeles
The 13.
It did not have much to finish loading the firmware, but it got stuck there. I did not have a choice, I had to unplug it. I can't still see it on the network though. I have just updated a 5231R-z just a few minutes before it, that had the 15 version on it and that one worked perfectly. Maybe it is not a good idea, to step up from a very old firmware, to the latest.
 

Dramus

Pulling my weight
Joined
May 7, 2019
Messages
323
Reaction score
229
Location
New Jersey
The 13.
It did not have much to finish loading the firmware, but it got stuck there. I did not have a choice, I had to unplug it. I can't still see it on the network though. I have just updated a 5231R-z just a few minutes before it, that had the 15 version on it and that one worked perfectly. Maybe it is not a good idea, to step up from a very old firmware, to the latest.
My 4231 and 5231s all have 05. I've upgraded one 5231, when I started reading of people having spontaneous rebooting problems with theirs' with the 16 version, so I stopped upgrading.

Now I know not what to do. I do have a copy of 13. Maybe I'll try upgrading one to that. The only problem I have is my cameras are spontaneously occasionally rebooting when any IVS is configured, and I'd like to stop that.
 

spammenotinoz

Getting comfortable
Joined
Apr 4, 2019
Messages
345
Reaction score
274
Location
Sydney
Out of no-where, the reboot bug has hit me!! Heck, even changing firmware is going to be risky as I can't keep the camera stable.

Update: Powered down the camera for a while, and as soon as it was up I performed the update (downgrade) to V2.800.0000013.0.R, Build Date: 2019-12-02 as I didn't have v15 handy.

@EMPIRETECANDY, appreciate the effort, but you need to pull the link to this firmware down before someones cams get bricked.

Here were the Abort\reboot logs running v16. Strange this is the camera was operating fine for days then it just kicked it "wham" and was down more than a pair of honeymooners knickers.

12021-01-21 12:57:01SystemStart up
22021-01-21 12:57:01SystemAbort
32021-01-21 12:55:40SystemReboot
42021-01-21 12:48:57SystemStart up
52021-01-21 12:48:57SystemAbort
62021-01-21 11:51:16SystemStart up
72021-01-21 11:51:16SystemAbort
82021-01-21 05:44:44SystemStart up
92021-01-21 05:44:44SystemAbort
102021-01-21 05:43:22SystemReboot
112021-01-21 05:14:22SystemStart up
122021-01-21 05:14:22SystemAbort
 
Last edited:

Dramus

Pulling my weight
Joined
May 7, 2019
Messages
323
Reaction score
229
Location
New Jersey
Update: Powered down the camera for a while, and as soon as it was up I performed the update (downgrade) to V2.800.0000013.0.R, Build Date: 2019-12-02 as I didn't have v15 handy.

@EMPIRETECANDY, appreciate the effort, but you need to pull the link to this firmware down before someones cams get bricked.
Is v15 even more stable than 13?

I believe Andy has taken v16 down. IIRC, he announced that a couple weeks ago or more?
 

spammenotinoz

Getting comfortable
Joined
Apr 4, 2019
Messages
345
Reaction score
274
Location
Sydney
Is v15 even more stable than 13?

I believe Andy has taken v16 down. IIRC, he announced that a couple weeks ago or more?
The link is still in this forum and the Dropbox download still works, just tried it.
V15 was quite stable but not as V13. Ie: rebooted every few days but not every few minutes.
 

Wael

Getting the hang of it
Joined
May 9, 2019
Messages
125
Reaction score
33
Location
California
Guys, I’m not understanding this reboot issue. I ran 16 for more than a couple months and never had a single reboot on 9 cameras running this firmware. I’m running the cameras into a NVR 5216 16p 4ks2. Is this reboot issue only when running the camera standalone or through Blue Iris or something?

By the way, my cameras are:
IPC-HDW5231R-ZE
IPC-HDW5831R-ZE
IPC-HDW4830EM-AS
 
Last edited:

spammenotinoz

Getting comfortable
Joined
Apr 4, 2019
Messages
345
Reaction score
274
Location
Sydney
Guys, I’m not understanding this reboot issue. I ran 16 for more than a couple months and never had a single reboot on 9 cameras running this firmware. I’m running the cameras into a NVR 5216 16p 4ks2. Is this reboot issue maybe related to running the camera standalone or through Blue Iris or something?

By the way, my cameras are:
IPC-HDW5231R-ZE
IPC-HDW5831R-ZE
IPC-HDW4830EM-AS
I didn't understand it either, and then it just hit me, but it hit me very hard with the cams aborting every few minutes and multiple reboots.
I amusing Blue Iris, so yes it could be that, it could be the camera model I am using, but whatever I think enough have been hit hard with this it should be withdrawn.
My cams are isolated, so I will happily just stick on v13 with the rest on v15.
 

tibimakai

Known around here
Joined
May 8, 2017
Messages
1,005
Reaction score
513
Location
Los Angeles
Anybody has a previous version firmware? The 13, is removed from Andy's thread.
It seems like, Dahua removed the firmware tabs from their site.
 
Top