Yes I believe there are still browser issues. Would recommend all use IE for now. It’s not to say it won’t work in other browsers as i mentioned with my experience on browsers above BUT for those seeing issues would recommend IE for testing
Worlds First Review - Dahua DH-IPC-HDW5849H-ASE-LED / IPC-Color4K-T - 2.8mm Turret
- Thread starter Wildcat_1
- Start date
I set it up initially in Edge and then the next day went in and the parameter settings like brightness, etc. went back to default 50 settings. All my profiles reset to default as well. The time section went back to default from NTP.
Now in IE they are all holding.
Yes as I mentioned stick with IE if you are having issues for now as you’re also forced to use the separate plug-in which is different than embedded mode. I filed a couple of bugs (not related to this issue) on the embedded code for 5.0 on the A180 so definitely some work needed on it but those are being worked by Dahua engineering now. A180 has the same Taurus SOC for reference.
Last edited:
ok, I will do some setting to it and see how is going on edge, i am using WIN12 Edge.
For the record, I can’t stand Edge, terrible browser
hahah
sebastiantombs
Known around here
Don’t use Edge is my recommendation for anyone here. Use IE, Firefox and try those on that order. Edge can also cause issues in the update process with this and other cams in general so always advise against it.
For those that setup in ‘other’ browsers, would advise following my multi default steps BUT through IE then re-apply FW through IE and then configure, you guessed it, through IE. Try that test, and let me know
sebastiantombs
Known around here
Sounds good. I always advise against edge due to issues seen especially in FW updates and those with ‘sticky’ issues. I’ll do a test on Edge just for the heck of it and report back here shortly as well but like I said, for anyone having the issues and that setup the cam or upgraded it using Edge then advise the default steps I share being performed in IE then re-apply and test.
sebastiantombs
Known around here
The changes don't happen right away so let it percolate for a day or two.
Yes I’ll test initial FW upgrade through Edge for issues then will also check settings over 24 hours in Edge too. I’ve got a test that I’m thinking might help isolate the potential browser impact.
Well I can already report back 2 issues with Edge.
1) did a test build upgrade (so I could see what was going on under the hood) using Edge which reported successful completion BUT when I dived deeper it clearly hadn’t. There were remnants (the stickiness I mention) of the old FW still on (this was after hard reset). Some were easy to see such as reference to purposefully removed code AND even things like logo / image assets not being removed
2) GUI elements also not showing completely (for reference, think issues with 3.0 when using other browsers instead of IE).
Left cam ‘upgraded’ from Edge and went into IE and issues followed.
Just went through the steps I shared above, hard FULL reset multiple times using IE (even added a HW reset in for good measure) then re-upgraded using IE, the issues I mentioned above no longer exist.
The above is precisely why I recommend people stay away from Edge. I’ll re-apply with Edge and see if that impacts the settings over time as well.
In the meantime I always recommend IE (if you still have it) then Firefox (for 5.0 GUI cams but 3.0 GUI can cause issues). For 3.0 Pale Moon can work and for both 3.0 & 5.0, Chrome can work at a push but you do have to be careful with all of these RE: Rev numbers of the browser. Hence IE number 1 pick then move down the list.
Like I said above I will re-upgrade using edge and let the cam sit with specific settings and see if that will replicate the issue others have seen and isolate towards the browser.
1) did a test build upgrade (so I could see what was going on under the hood) using Edge which reported successful completion BUT when I dived deeper it clearly hadn’t. There were remnants (the stickiness I mention) of the old FW still on (this was after hard reset). Some were easy to see such as reference to purposefully removed code AND even things like logo / image assets not being removed
2) GUI elements also not showing completely (for reference, think issues with 3.0 when using other browsers instead of IE).
Left cam ‘upgraded’ from Edge and went into IE and issues followed.
Just went through the steps I shared above, hard FULL reset multiple times using IE (even added a HW reset in for good measure) then re-upgraded using IE, the issues I mentioned above no longer exist.
The above is precisely why I recommend people stay away from Edge. I’ll re-apply with Edge and see if that impacts the settings over time as well.
In the meantime I always recommend IE (if you still have it) then Firefox (for 5.0 GUI cams but 3.0 GUI can cause issues). For 3.0 Pale Moon can work and for both 3.0 & 5.0, Chrome can work at a push but you do have to be careful with all of these RE: Rev numbers of the browser. Hence IE number 1 pick then move down the list.
Like I said above I will re-upgrade using edge and let the cam sit with specific settings and see if that will replicate the issue others have seen and isolate towards the browser.
Last edited:
I also checked code changes between 9/22 and 9/26 and there are just a few small changes and those are really around branding references and removal of DH logo etc. nothing else I see there on functional changes etc
Another quick update.
I also re-flashed one of the other 4K-T's I have using IE (again following the steps I shared), then went into Safari and setup new config, changing settings etc and configuring schedules as well. I saw the schedules change correctly on each time interval I set them to on the Time Plan and saw this reflected in Live Mode as well as in Camera menu (preview screen) + also on Mobile (iDMSS) connecting to the camera too. I then repeated this exact using Firefox (both of these browsers on Mac for this test) and again successfully saw schedules change at the right time in Live & Camera views + settings did not shift or get reset.
Just making sure I kept all up to date. As mentioned above this is definitely appearing to potentially be browser related (for those seeing the issue) both in terms of initial upgrade (DO NOT USE EDGE) and potentially for the settings piece (will continue to monitor for this overnight). So to recap, I've tested on IE (PC) + Safari & Firefox on Mac, all switch the schedules when expected and retain settings. Edge is 100% a no go and as mentioned above, if you did initially upgrade via Edge (heck even if you didn't and the cam arrived with 9/26 and you see issues), then I would advise to follow the multiple FULL factory default steps I mentioned in IE, re-flash the cam using IE, setup and configure in IE for test. You could even upgrade using IE and then test in another browser if you wish (just NOT EDGE).
As I went to post this, I just re-tested the above 1 more time on the 3rd 4K-T just for sanity check, that worked too
I also re-flashed one of the other 4K-T's I have using IE (again following the steps I shared), then went into Safari and setup new config, changing settings etc and configuring schedules as well. I saw the schedules change correctly on each time interval I set them to on the Time Plan and saw this reflected in Live Mode as well as in Camera menu (preview screen) + also on Mobile (iDMSS) connecting to the camera too. I then repeated this exact using Firefox (both of these browsers on Mac for this test) and again successfully saw schedules change at the right time in Live & Camera views + settings did not shift or get reset.
Just making sure I kept all up to date. As mentioned above this is definitely appearing to potentially be browser related (for those seeing the issue) both in terms of initial upgrade (DO NOT USE EDGE) and potentially for the settings piece (will continue to monitor for this overnight). So to recap, I've tested on IE (PC) + Safari & Firefox on Mac, all switch the schedules when expected and retain settings. Edge is 100% a no go and as mentioned above, if you did initially upgrade via Edge (heck even if you didn't and the cam arrived with 9/26 and you see issues), then I would advise to follow the multiple FULL factory default steps I mentioned in IE, re-flash the cam using IE, setup and configure in IE for test. You could even upgrade using IE and then test in another browser if you wish (just NOT EDGE).
As I went to post this, I just re-tested the above 1 more time on the 3rd 4K-T just for sanity check, that worked too
CCTVCam
Known around here
- Sep 25, 2017
- 2,832
- 3,710
Dahua need to move away from IE. I'm pretty sure Win 11 and some builds of Win 10 remove it.
Don't know why Dahua don't just program for Firefox. It's widely available as a free download for anyone who doesn't have it and a well established App. If Dahua were to add Chrome support, they'd have the 2 most popular browsers covered. The only issue with Chrome is there are a lot of modded variants out there including other browsers such as Vivaldi. For that reason, Firefox being largely vanilla is a better bet overall. It's stood the test of time and rarely has any issues.
Don't know why Dahua don't just program for Firefox. It's widely available as a free download for anyone who doesn't have it and a well established App. If Dahua were to add Chrome support, they'd have the 2 most popular browsers covered. The only issue with Chrome is there are a lot of modded variants out there including other browsers such as Vivaldi. For that reason, Firefox being largely vanilla is a better bet overall. It's stood the test of time and rarely has any issues.
Last edited:
Yes, i talked with wildcat today it's time to forget IE,he told me IE always works and uses separate plug-in which allows to test properly for issues. Chrome is ok but I would say IE first then Firefox then Chrome/Safari. With cams that have sticky issues with firmware I always recommend IE.
Web 5.0 is trying to avoid IE and will better support famous browser.
Web 5.0 is trying to avoid IE and will better support famous browser.
Yes, thats what I mentioned to Andy above. IE still my primary go to if there are issues with stickiness in upgrades / weirdness with GUI etc seen afterwards (which is why I keep an old laptop around for this
). Like I said above, I would state IE, Firefox then at a push Chrome (again per @CCTVCam I agree you have to be careful of all the modded variants + rev numbers of these browser can play a big part too). With that said, be careful with Firefox as a daily driver on a Mac. The reason being is that there is a bug in GUI 5.0 that I filed where it still prompts for a Plug-In for things like Image Control / E-PTZ when it should be embedded, leads you to a Windows download (always good when you're on a Mac) and doesn't let you get past it. There are ways around this but just mentioning for completeness. Again bug filed and Dahua engineering working on the Firefox Mac piece BUT still can be used to configure etc.HTH