Worlds First Review - Dahua DH-IPC-HDW5849H-ASE-LED / IPC-Color4K-T - 2.8mm Turret

Maybe you can give Dahua for some feedback vs the 4Kx and also why they haven't used the same components. Maybe an ask for a true 4kT based on the 4kX internals?
 
I think the difference in internals is a result of going from a bullet to a ball. They just can't get the bullet internals into a ball and keep the overall turret form factor at an acceptable size. Even now the 4K-Tis bigger, noticeably bigger, than a 5442T-ZE. I think that's why we may never see the 4K-T in a varifocal and I really would like to see that.
 
  • Like
  • Love
Reactions: CCTVCam, looney2ns, jrbeddow and 1 other person
This is a quick pic of my 4K-T. The Folgers coffee can is about 20 ft.away. Also is my famous power line in the distance (at the v notch of the 2 tree lines between the
coffee can and backyard power pole) but, can you find it's mate? Just to the left of the power pole in the fore ground. At the base of the other power, just above the
trees in the way back-ground is found the rounded top of a water tower over 1 mile away.

For a small form factor this is a great compromise to it's big brother the 4K-X.
1666287584469.png
 
  • Like
Reactions: EMPIRETECANDY
OK so I might be making some progress on the APIs LOL. Well at least heading that way LOL.

So the utility we use was written to use the following API:

http://USER(INSERT : HERE) PASSWORD@IPADDRESS/cgi-bin/configManager.cgi?action=setConfig&VideoInDayNight[0][1].Mode=Night"

Thru playing around I found that the API for this camera changed a bit to this (Mode is now Name)

http://USER(INSERT : HERE) PASSWORD@IPADDRESS/cgi-bin/configManager.cgi?action=setConfig&VideoInDayNight[0][1].Name=Night"

When I run this it says OK, except the profile doesn't change. So the camera is getting and accepting the command, it just doesn't execute it.

I am going to do a 4 time factory reset and see if that gets it going LOL.

But if this will work, we can then send the command thru BI to change day and night profiles.
 
  • Like
Reactions: jrbeddow, garycrist, samplenhold and 1 other person
sebastiantombs said:
I think the difference in internals is a result of going from a bullet to a ball. They just can't get the bullet internals into a ball and keep the overall turret form factor at an acceptable size. Even now the 4K-Tis bigger, noticeably bigger, than a 5442T-ZE. I think that's why we may never see the 4K-T in a varifocal and I really would like to see that.
Click to expand...

In principle it's fine but in a market where cameras are judged on their performance, to not offer the same performance or better isn't really a good outcome.

Maybe Dahua need to look at other alternatives to the current components to see if they can match the performance in another way. It's a big disappointment to many to see it not matching the 4KX as this was probably the most anticipated camera of recent times.
 
Wildcat_1 said:
Thanks for the update from your system @looney2ns. What you're experiencing certainly is strange.

Quick update and thoughts from me. With a limited number of people seeing issues vs larger shipping quantity of the product plus inability to be able to replicate across multiple units, this seems (and I do mean seems, cannot stress that enough as there aren't enough data points of the issue at this time) to be pointing more to difference(s) in the environment / system(s) being used to configure and upgrade the cam IMO. As I said to @sebastiantombs I've tried a total of 5 browsers (some of those browsers of course featured in the video yesterday) across different systems (now tested on 2 different Mac's running different OS's + 2 Windows machines - 1 virtualized, 1 regular standalone) on 3x cams and multiple default and configuration setup scenarios (IVS first, settings later, IVS last, settings first, different AI options no standard IVS etc etc.) up and down the FW chain and I'm not seeing any of the issues (other than those I mentioned yesterday, already filed and with the exception of Microsoft Edge that I never recommend be used). This is across over a month of testing the cams and a week in testing them against specific scenarios. Therefore, this could point to something within the OS (Windows etc itself) and associated version, browser version, browser security/privacy config (block vs allow on page/script denial/html content blockers etc which could suggest why play back of recorded footage isn't working in a browser in @looney2ns case) or even interdependencies of other OS level, browser centric plugins (already installed for other cams on people's systems) as the issue. Just throwing out relevant ideas as like others, I don't have a system that shows these issues to dive in deeper unfortunately.

Due to the above, the only other suggestions I have at this time for those experiencing this would be the following;
  1. Uninstall Web Rec fully in case there are underlying issues with other plugins on your system - DahuaWiki
  2. Then delete the entire webrec directory (C:\Program Files\) if still in place after uninstall and reboot your system after that
  3. Look to fully factory default the camera in IE (follow the steps already provided), roll back to 8/2x FW (If you have it), factory default there and then re-upgrade to 9/22 at that point (using IE again for this continuing test). This ensures we go back down a FW level before installing new rather than just installing the same FW over the top
  4. Go back into your browser and access the camera, if prompted for plugin(s), download it BUT do NOT install the plugin(s) without first closing, exiting, force quitting the browser so its not in system memory or consuming resources along with holding any other plugins open at the time you install the plugin (downloaded from first accessing the cam through the browser)
  5. Separately, if you have access to the same versions of OS and browser that I showed and noted, test those as well.
As I mentioned, not enough data points to categorically state root cause for the few that have seen the issue but I don't believe its HW related at this time.

HTH and will continue putting the cams through their paces and see if I can find anything further
Click to expand...

OK I followed your steps above but I do not think it is completely factory resetting?

When I first open up the menu, all you get is the IP camera and the little house. I pop open a few of these to write down my settings and then do the factory reset.

When it initializes back up, it shows all these options (camera, record, etc.) that were there before I factory reset - shouldn't that have been cleared out again.

So for kicks I removed a few and factory reset and it opened up to the same screen.

I don't know if that makes sense what I am trying to say, but it keeps in the bar the "options" that I had previously opened after a factory reset.

1666293657268.png
 
  • Wow
Reactions: looney2ns and sebastiantombs
Methinks the "factory reset" isn't a true reset after all! Wonder if the reset button is, especially at power up. If that's the case it's another impossible situation after a camera is installed.
 
  • Like
Reactions: looney2ns
sebastiantombs said:
Methinks the "factory reset" isn't a true reset after all! Wonder if the reset button is, especially at power up. If that's the case it's another impossible situation after a camera is installed.
Click to expand...

Yep. I tried it on two different computers with IE. The one had never been used for a camera. Same thing.

Reset button is my next attempt to see what happens.
 
  • Like
  • Wow
Reactions: sebastiantombs and looney2ns
wittaj said:
OK I followed your steps above but I do not think it is completely factory resetting?

When I first open up the menu, all you get is the IP camera and the little house. I pop open a few of these to write down my settings and then do the factory reset.

When it initializes back up, it shows all these options (camera, record, etc.) that were there before I factory reset - shouldn't that have been cleared out again.

So for kicks I removed a few and factory reset and it opened up to the same screen.

I don't know if that makes sense what I am trying to say, but it keeps in the bar the "options" that I had previously opened after a factory reset.

View attachment 143334
Click to expand...
Wonder if clearing the browser cache affects that.
 
  • Like
Reactions: sebastiantombs
Whew! That's a load off anyway! I never noticed that whole scenario with all the defaults I've done but then I just use the gear icon unless I need to config IVS WHICH BELONGS ON THE GEAR ICON TOO!
 
OK it appears to be a cache issue (hopefully)!!

Whether I do a factory reset from the GUI or do the unplug, push and hold reset and apply power factory reset, those options still appear unless the cache is cleared.

Now to see if 8 plus factory resets gets this API executed LOL
 
  • Haha
Reactions: sebastiantombs
Sadly, I still get the invalid date when trying to setup DST and I left it in 24-hour mode:

1666297402335.png
 
That's strange! Sometimes I wonder if we have "clean" downloads of the firmware and/or if it's loading "clean" on the LAN.

4K-T time config.JPG
 
OK a few more reboots and now I can set the DST.

I was hoping the API would work but it keeps coming back OK but doesn't execute it in the camera.

So far I tried setting a full time general along with a blank schedule to see if it would allow the API to work, but nothing. Still trying LOL

But I think this is indicative of why we can't get the schedule to work either?
 
Last edited:
EMPIRETECANDY said:
which API you are using? The latest new one is 202206
View attachment 143363
Click to expand...

V2.92

Thru trial and error I figured out the API to switch the profile and it says that it went, but the camera doesn't change.

I suspect there might be another setting we have to change. Under the old GUI we would set the schedule to full time and then the API would change it. We don't have that exact setup and I have been playing with different settings to see if I can stumble on the area that is conflicting.
 
I found a bug. When changing to 12 hour from 24 hour time, the camera will change to a different setting
when going back to LIVE view. Changing back to 24 hr fixes that problem.

ver System Version:3.000.0000000.20.RBuild Date:2022-09-26
 
  • Like
  • Wow
Reactions: sebastiantombs and EMPIRETECANDY
wittaj said:
OK so I might be making some progress on the APIs LOL. Well at least heading that way LOL.
Click to expand...

Tried this API call on both the Dahua HFW-5849T1-ASE-LED 6mm and the new Dahua 180 degree camera IPC-Color4K-B180 (PFW-5849-A180-E2-ASTE) and the code works for night to day and day to night using the full time day/night camera settings.

This was used in Hubitat and the associated NVR to change modes at sunrise and sunset. The square brackets were used to list the camera channel number. They are left blank for use in BI. If removed the code will show an error.

Tested in FF and IE 11 and both perform as expected using BI. However, it seems this is not the correct way to perform this mode change but at least may lead someone to come up with a better workable solution.

Note: no spaces between any characters in API calls. For 'password' enter your camera password and change the camera "URL" to your test camera.

Color to B/W (Sunset Mode)

Code: 
http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=3&VideoInOptions[].NightOptions.DayNightColor=2

B/W to Color (Sunrise Mode)

Code: 
http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=0&VideoInOptions[].NightOptions.DayNightColor=0
 
  • Love
Reactions: EMPIRETECANDY
Alaska Country said:
Tried this API call on both the Dahua HFW-5849T1-ASE-LED 6mm and the new Dahua 180 degree camera IPC-Color4K-B180 (PFW-5849-A180-E2-ASTE) and the code works for night to day and day to night using the full time day/night camera settings.

This was used in Hubitat and the associated NVR to change modes at sunrise and sunset. The square brackets were used to list the camera channel number. They are left blank for use in BI. If removed the code will show an error.

Tested in FF and IE 11 and both perform as expected using BI. However, it seems this is not the correct way to perform this mode change but at least may lead someone to come up with a better workable solution.

Note: no spaces between any characters in API calls. For 'password' enter your camera password and change the camera "URL" to your test camera.

Color to B/W (Sunset Mode)

Code: 
http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=3&VideoInOptions[].NightOptions.DayNightColor=2

B/W to Color (Sunrise Mode)

Code: 
http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=0&VideoInOptions[].NightOptions.DayNightColor=0
Click to expand...

Interesting. Let me try those.

Did the two cameras that this API worked for using the new GUI or the old GUI?
 
  • Like
Reactions: sebastiantombs
You must log in or register to reply here.
Top Bottom