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.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.
OK I followed your steps above but I do not think it is completely factory resetting?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;
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.
- Uninstall Web Rec fully in case there are underlying issues with other plugins on your system - DahuaWiki
- Then delete the entire webrec directory (C:\Program Files\) if still in place after uninstall and reboot your system after that
- 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
- 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)
- Separately, if you have access to the same versions of OS and browser that I showed and noted, test those as well.
HTH and will continue putting the cams through their paces and see if I can find anything further
Yep. I tried it on two different computers with IE. The one had never been used for a camera. Same thing.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.
Wonder if clearing the browser cache affects that.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
Oh let me try that before the hard reset LOLWonder if clearing the browser cache affects that.
V2.92which API you are using? The latest new one is 202206
View attachment 143363
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.OK so I might be making some progress on the APIs LOL. Well at least heading that way LOL.
http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=3&VideoInOptions[].NightOptions.DayNightColor=2
http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=0&VideoInOptions[].NightOptions.DayNightColor=0
Interesting. Let me try those.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)
B/W to Color (Sunrise Mode)Code:http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=3&VideoInOptions[].NightOptions.DayNightColor=2
Code:http://admin:password@192.168.55.32/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[].NightOptions.SwitchMode=0&VideoInOptions[].NightOptions.DayNightColor=0