Latest New 20181228 Firmware for DH_IPC-HX5X3X-Rhea

I just received IPC-HDBW4239R-ASE and I looked for the firmware what is installed. In version I see it's named 2.622.0000000.31.R, Build Date: 2018-08-13.
Is it correct that DH_IPC-HX5X3X-Rhea_MultiLang_PN_Stream3_V2.800.0000000.0.R.181226 a newer version and this can upgrade?
 
For any Mac users, here's how "no-plugin streaming" worked for me. macOS 10.14.3 here

NO:
Safari (12.0.3)

YES:
Chrome (72.0.3626.121)
Firefox (60.5.1esr)
Firefox (65.0.2)
 
  • Like
Reactions: motoolfan
snicky said:
I just received IPC-HDBW4239R-ASE and I looked for the firmware what is installed. In version I see it's named 2.622.0000000.31.R, Build Date: 2018-08-13.
Is it correct that DH_IPC-HX5X3X-Rhea_MultiLang_PN_Stream3_V2.800.0000000.0.R.181226 a newer version and this can upgrade?
Click to expand...

The model # is listed in first post so yes
 
  • Like
Reactions: snicky
Updated the firmware on my IPC-HFW4239T-ASE and one of my 5231R-Zs. Working fine so far. Great to see live view, playback and configuration working without any plugin. Also, the second sub-stream now appears to support full resolution, as well as recording a custom region at its full resolution.
 
Must....resist...temptation!


Sent from my iPhone using Tapatalk Pro
 
  • Like
Reactions: catcamstar
does it address the 'inability to focus at full zoom' issue some people have reported (mostly with the Z5 and Z12 versions...) ?
 
This firmware installed without a hitch, albeit, it took much more time than previous update. Only issue I have noticed, is it no longer displays IVS tripwire/intrusion zone lines in Live View when logged in to the camera. Not a big deal, as SmartPSS and the NVR display does show them. I'll run this for about a week, then update all my other 5231's if there are no problems.

One huge plus is the Day/Night profile actually works automatically using the built in sensor. I was able to set up a day profile with whatever parameters needed (wdr) and a night profile using (BLC). Come sundown and the lower light conditions, it automatically went to the night profile using BLC. Very happy with this finally working. This setting is under the PROFILES tab. Just select Day/Night, save it, and move on to the other camera settings.

Thanks very much, Andy!
 
Last edited:
  • Like
Reactions: giomania
Short question: I'm using a Dahua NVR5208-8P-4KS2 to which all my cams are connected.

Is it right that I can't connect to a single cam that way? The IP of my NVR is 192.168.178.xx, the cams are shown in PSS with IP-range 10.1.1.xx.
And I can't access the NVR-webfrontend without a plugin for chrome, right?

Is there any way to get direct access the each cam, even when it's connected to the NVR?
 
manwald said:
Is there any way to get direct access the each cam, even when it's connected to the NVR?
Click to expand...
If you use a web browser to access the NVR, there should be a page somewhere that lists all of your cameras. Next to each camera should be an Internet Explorer looking icon.. if you click on that, it should directly connect you to the camera. I'm not sure which browser you have to use to access the NVR though... I switched to Blue Iris.

Once you find those icons, if you hover over one, it'll show you the URL for that camera. You can bookmark that and jump directly to it next time you want direct access to the cam. A lot of the cameras latest firmware updates allows everything to work with Chrome/Firefox without having to use a plugin.
 
Last edited:
  • Like
Reactions: looney2ns
IAmATeaf said:
Is this firmware the one to go for? My cam currently has the 0813 version and I’m wondering if I should upgrade?
Click to expand...
I've only been running it for a few weeks, but I haven't had any problems with it. If the 0813 version requires a plugin in Chrome/Firefox to see video, that might be a reason to want to upgrade to this one.
 
  • Like
Reactions: IAmATeaf
looney2ns said:
Yes, no problems.
Click to expand...


TechBill said:
If you are going to update several cameras, be sure to empty your browser cache or temporary files between each camera updates.

I managed to brick one of the camera tonight but I believed I know why I bricked it
Click to expand...

Did either of you factory reset before applying the firmware update, after the firmware update, or both before AND after the firmware update?

If so, was that a software-based reset, or hardware-based via the internal button on the camera?

Thanks.

Mark


Sent from my iPhone using Tapatalk Pro
 
giomania said:
Did either of you factory reset before applying the firmware update, after the firmware update, or both before AND after the firmware update?

If so, was that a software-based reset, or hardware-based via the internal button on the camera?

Thanks.

Mark
Sent from my iPhone using Tapatalk Pro
Click to expand...
I do a factory default before an update and again after. I don't export and re-emport settings. I use the software way.
 
  • Like
Reactions: giomania
I did the factory default via software before updating. I didn't do it again after, never thought of that, but have not had any problems. I never touched the actual camera.
 
I’m thinking about applying this firmware update to my 5231’s, because it seems like this one might be worth going through the trouble, due to fixing the profile issues that have plagued previous firmware updates.

However, I need a memory refresh for when cameras are on a different subnet, since it is a best practice to factory reset before applying the firmware update...and after just for good measure. Also it’s probably best to discuss the potential issues with applying this update to installed, difficult to access cameras:

After resetting the camera, the default IP address is 192.168.108. If you use that 192.168.1.X subnet you could have a IP conflicts.

When you have your cameras on a different subnet, the Dahua Config Tool is able to see and initialize the camera regardless of the subnet.

The initialization process requires resetting the default password on the camera, and then you must login via the web interface, which is I think where the different subnet will cause a problem.

As I recall in the past, I have tried to set the IP address with the config tool and it didn’t work, but I have only ever set up cameras on the bench so it was easy to connect it to the second NIC on my computer to circumvent any issues logging in.

Any insights for this process when you have cameras on a different subnet?

Does the Config tool “Upgrade” feature work to apply the firmware update?

Thanks.

Mark


Sent from my iPhone using Tapatalk Pro
 
I have not used the Dahua Config Tool so I can't answer those questions.

My cameras are on a different subnet too. After doing a reset via the web interface, I then took my laptop,turned off it's wireless, and plugged it's ethernet into the camera's subnet ethernet switch. I set the IP address on the laptop manually to 192.168.1.100. After that I was able to access the camera via it's web interface at 192.168.1.108 again and configure it, changing it's IP back to it's private subnet and going from there.
 
  • Like
Reactions: giomania
giomania said:
I’m thinking about applying this firmware update to my 5231’s, because it seems like this one might be worth going through the trouble, due to fixing the profile issues that have plagued previous firmware updates.

However, I need a memory refresh for when cameras are on a different subnet, since it is a best practice to factory reset before applying the firmware update...and after just for good measure. Also it’s probably best to discuss the potential issues with applying this update to installed, difficult to access cameras:

After resetting the camera, the default IP address is 192.168.108. If you use that 192.168.1.X subnet you could have a IP conflicts.

When you have your cameras on a different subnet, the Dahua Config Tool is able to see and initialize the camera regardless of the subnet.

The initialization process requires resetting the default password on the camera, and then you must login via the web interface, which is I think where the different subnet will cause a problem.

As I recall in the past, I have tried to set the IP address with the config tool and it didn’t work, but I have only ever set up cameras on the bench so it was easy to connect it to the second NIC on my computer to circumvent any issues logging in.

Any insights for this process when you have cameras on a different subnet?

Does the Config tool “Upgrade” feature work to apply the firmware update?

Thanks.

Mark


Sent from my iPhone using Tapatalk Pro
Click to expand...

I use the latest version of IPconfig to change IP address's all the time and to initialize cams. Be sure to read the help file that is built into IPconfig.
As some of it's functions are not obvious.
Yes, the update works from IPconfig.
Click on the third icon from the right (the little cam symbol) in the upper right corner, then help.
upload_2019-3-29_12-3-31.png
 
  • Like
Reactions: giomania
One question: the IP-range of my cams is 10.1.1.x, but my home-network (and also the NVR) has 192.168.178.x.

Can I change the IP-addresses or the range of each cam in the web-frontend to my networks IP-range, so that I can access each cam not only over the NVR, but also directly with its IP in my browser?
 
manwald said:
One question: the IP-range of my cams is 10.1.1.x, but my home-network (and also the NVR) has 192.168.178.x.

Can I change the IP-addresses or the range of each cam in the web-frontend to my networks IP-range, so that I can access each cam not only over the NVR, but also directly with its IP in my browser?
Click to expand...
Yes, search is your friend. Discussed many times.
 
  • Like
Reactions: manwald
You must log in or register to reply here.
Top Bottom