Agreed. The x52 works best once any version of CAM is uninstalled. I simply connected the fans to the mobo set to monitor CPU temp. Their speed increases properly when I use CPU-ID to bench. Those same fans (the ones that came with the x52) stay at the same speed when plugged into the x52 harness. I can only hope the pump knows when to spin faster because without CAM there's no way to control pump speed. I'd really like to connect the pump to the PUMP pinouts on the mobo. CAM is full of bugs that are never fixed. Temps and fan speeds are always wrong. CAM SOFTWARE IS INSULTING TRASH. A CLASS ACTION LAWSUIT IS IN ORDER HERE. nzxt needs to give the user a way to run its cooling systems directly off the appropriate mobo pinouts and bypass CAM and the firmware inside the pump housing. I'M ALWAYS AFRAID MY NEW 1950X SYSTEM WILL OVERHEAT. THIS IS UNACCEPTABLE. PLEASE FIX IT. In the very least, the horrid documentation doesn't even speak to whether the x52 will use safe parameters when (not if) CAM fails, which is almost all the time.

I think your clients would like to know what is going on with a lot of the promised or talked about features such as advanced fan controls (control fans via multiple temp readings simultaneously, be able to use other temp sensors other than just CPU/GPU/liquid), monitoring, and combining Hue+ and Grid+. I have seen some of the topics were mentioned way back in 2014 and still no news. Looking at Corsair, they are doing an awesome job combining the Cue and Link into iCue, and their software can do so much more than the basic function of Cam. I'm pretty sure that I am not the only one who is frustrated. All of my lighting and cooling including GPU are NZXT stuff but I am seriously considering replacing all of them with Corsair if I don't see that the Cam functionality and features will be improved drastically and quickly.

1. OFFLINE Mode still does NOT exist.

2. DATA is STILL being sent to NZXT WITHOUT USER CONSENT, PRODUCT IS STILL BEING SOLD WITHOUT THIS INFORMATION BEING PROVIDED UP FRONT ON THE OUTSIDE OF PACKAGING!

3. USER(S) HAVE NEVER AGREED TO ANY DATA SHARING WITH NZXT AT ANY POINT OF TIME.

4. USER(S) HAVE THE SOLE RIGHT TO SOFTWARE WHICH WILL NOT TRANSMIT DATA TO NZXT OTHER THAN TO CHECK FOR UPDATES TO THE SOFTWARE.

5. USER(S) HAVE THE RIGHT TO A CLASS ACTION SUIT!

6. FIX YOUR SOFTWARE , PROVIDE YOUR USERS WITH A COMPLETE OFFLINE VERSION.

7. ISSUE HAS BEEN CLOSED AGAIN AND AGAIN... AND IGNORED WITH VERY MINIMAL AND MINOR UPDATES TO RESOLVE THE ISSUE.

a: https://support.camwebapp.com/forums/252939-cam-ideas/suggestions/18038656-provide-offline-mode-for-cam

b: https://support.camwebapp.com/forums/252939-cam-ideas/suggestions/10987476-offline-mode

c: https://support.camwebapp.com/forums/252256-cam-bugs/suggestions/18039109-provide-offline-mode-for-cam

d: https://support.camwebapp.com/forums/252256-cam-bugs/suggestions/19538782-fully-offline-mode-for-cam-privacy

e: some requests with over 500+ votes have totally been deleted.

8. NZXT YOU DO NOT OWN OUR PERSONAL DATA, YOU DO NOT OWN OUR PRIVACY. OUR DATA IS OUR DATA.

"Per (MULTIPLE) previous requests which was claimed to be "resolved," yet it is not:
(
http://support.camwebapp.com/forums/252256-cam-bugs/suggestions/18039109-provide-offline-mode-for-cam?tracking_code=32a4364a67b73d2c130831061e16f03b
)
http://support.camwebapp.com/forums/252939-ideas/suggestions/10987476-offline-mode

That is not OFFLINE mode, GUEST mode shouldn't be broadcasting. Please resolve it.

The log I have has over 10,000 intrusion attempts made by CAM alone. I will not unblock the software as it absolutely does not need network access to your servers.

The issue is not solved or completed as you claim it to be.

----------------------------------------------------------------------------------

Table: Firewall Events

Date Created: 2017-02-11 22:08:34

Records count: 3046

Date & Time Application Action Direction Protocol Source IP Source Port Destination IP Destination Port
2017-02-11 22:08:16 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9988 13.88.145.74 443
2017-02-11 22:08:00 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9987 13.88.145.74 443
2017-02-11 22:07:52 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9986 13.88.145.74 443
2017-02-11 22:07:48 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9985 13.88.145.74 443
2017-02-11 22:07:30 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9984 13.88.145.74 443
2017-02-11 22:07:23 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9983 207.46.147.148 80
2017-02-11 22:07:22 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9982 207.46.147.148 80
2017-02-11 22:07:12 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9980 13.88.145.74 443
2017-02-11 22:07:04 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9979 13.88.145.74 443
2017-02-11 22:07:00 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9978 13.88.145.74 443
2017-02-11 22:06:41 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9973 13.88.145.74 443
2017-02-11 22:06:25 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9971 13.88.145.74 443
2017-02-11 22:06:17 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9964 13.88.145.74 443
2017-02-11 22:06:13 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9963 13.88.145.74 443
2017-02-11 22:05:55 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9962 13.88.145.74 443
2017-02-11 22:05:40 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9961 13.88.145.74 443
2017-02-11 22:05:31 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9960 13.88.145.74 443
2017-02-11 22:05:27 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9959 13.88.145.74 443
2017-02-11 22:05:09 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9958 13.88.145.74 443
2017-02-11 22:04:54 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9955 13.88.145.74 443
2017-02-11 22:04:45 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9954 13.88.145.74 443
2017-02-11 22:04:41 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9953 13.88.145.74 443
2017-02-11 22:04:23 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9944 13.88.145.74 443
2017-02-11 22:04:09 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9943 13.88.145.74 443
2017-02-11 22:04:01 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9942 13.88.145.74 443
2017-02-11 22:03:57 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9941 13.88.145.74 443
2017-02-11 22:03:39 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9940 13.88.145.74 443
2017-02-11 22:03:23 C:\Program Files (x86)\NZXT\CAM\CAM_V3.exe Blocked Out TCP 127.0.0.1 9938 13.88.145.74 443"

Got an h700i with a smart device/hue2/krakenx72 set up, all was well until I tried the adaptive noise reduction calibration.

After going through calibration I hit update and now CAM is stuck at 100% for "We are determining the optimal settings for your system".

Can't adjust fans at all anymore through CAM because it's still just hanging. I've tried uninstalling and reinstalling, as well as installing an older version of CAM, 3.5.88, and then updating and neither worked.

The last few lines of the dated log in C:\Program Files (x86)\NZXT\CAM\Logs is:

2019-01-11 11:28:22:CAMV2.Settings.DrivesPage/UpdateUI:C:\Windows\System32\drivers\SiLib.sys- at System.Diagnostics.FileVersionInfo.GetVersionInfo(String fileName)
at CAMV2.Settings.DrivesPage.UpdateUI(MyComputer data)
2019-01-11 11:28:33:initialize cloud upload process
2019-01-11 11:28:40:CAMV2.Cooling.CoolingPage/UpdateKrakenXPage:Object reference not set to an instance of an object.- at CAMV2.Cooling.CoolingPage.UpdateKrakenXPage(MyComputer data)
2019-01-11 11:28:40:CAMV2.Cooling.CoolingPage/UpdateSmartDevicePage:Object reference not set to an instance of an object.- at CAMV2.Cooling.CoolingPage.UpdateSmartDevicePage(MyComputer data)

and in the CAM titled log from the same folder has a lot of lines that look like this

{"ThreadID":24,"Time":"2019/01/11 19:01:15","Username":"@gmail.com","Exception":"URL: https://apianr.nzxt.com/v1/smartdevice/pop, Params: hostname = Camyo-PC; email = @gmail.com","InnerException":null,"StackTrace":null,"CAMVersion":"3.7.4"}

Hopefully I can get a reply as I looked through a hundred or so posts and couldn't find any solutions.