Hi everyone,
I’m trying to diagnose a strange issue with two SV3C C13 cameras and I’d really appreciate some help from people who know these CamHi/CamHiPro cameras better than I do.
I have two units of the same camera model:
SV3C C13
Both report the same device type:
C6F0SgZ0N0P0L2
Both also use the same main firmware branch:
V32.1.20.11.19
The difference is the build date:
V3.0.7.1
The newer-build camera works with CamHiPro, while the older-build camera does not complete the initial adding/authentication process.
The normal setup process with the working camera is:
SSAT-013982-BCFDB
The issue happens specifically in CamHiPro.
CamHiPro can detect the camera, but when it reaches the adding/authentication stage, it just stays on:
“Adding…” / “Connecting…”
and eventually times out.
It never reaches the next setup steps that the working camera reaches.
There is also one strange behavioral difference: the working camera gives voice prompts during setup/reset, while the problem camera does not seem to give the same voice prompts. It powers on, moves normally and makes startup sounds, but the initialization behavior is different.
I also tested the networking manually through the web interface.
The working camera is correctly connected to the main home network and shows:
The web system log does not show anything particularly useful during the failed CamHiPro attempt. Local HTTP login and streaming work normally, but I do not see a clear P2P/authentication error in the log.
I also downloaded the official SV3C Upgrade Tool. It detects the problem camera correctly, including:
The public firmware files I found appear to belong to completely different branches/platforms such as V13, V19, V20, GK7102, Hi16EV, etc., so I have not flashed anything because I do not want to brick the camera.
The biggest clue for me is this:
Both cameras are:
So I’m wondering whether the older build has some known CamHiPro / P2P / authentication issue.
My main questions are:
Has anyone seen this exact device type or firmware branch before?
Does anyone have firmware V32.1.20.11.19-20241217, or a newer compatible version, for SV3C C13 / C6F0SgZ0N0P0L2?
Could the older 20240228 build have a known P2P or CamHiPro authentication problem?
Is there any safe way to extract the firmware from the working camera, or should I only flash a file supplied directly by SV3C?
Is there anything else I should compare between these two cameras before assuming this is a firmware/P2P issue?
I’m not very experienced with IP cameras, but I’ve tried to diagnose this as carefully as possible before flashing anything.
Thanks in advance for any help.
I’m trying to diagnose a strange issue with two SV3C C13 cameras and I’d really appreciate some help from people who know these CamHi/CamHiPro cameras better than I do.
I have two units of the same camera model:
SV3C C13
Both report the same device type:
C6F0SgZ0N0P0L2
Both also use the same main firmware branch:
V32.1.20.11.19
The difference is the build date:
- Working camera: V32.1.20.11.19-20241217
- Problem camera: V32.1.20.11.19-20240228
V3.0.7.1
The newer-build camera works with CamHiPro, while the older-build camera does not complete the initial adding/authentication process.
The normal setup process with the working camera is:
- Reset the camera.
- Connect the phone to the Wi-Fi hotspot created by the camera (IPCAM-xxxxxx).
- Open CamHiPro and add/scan the camera.
- Enter the camera credentials.
- The camera authenticates successfully.
- CamHiPro then continues to things like timezone setup, forcing a stronger password and selecting the home Wi-Fi.
- The camera is added successfully.
- It creates its own IPCAM-xxxxxx Wi-Fi network.
- Phone and laptop can connect to it.
- I can access its web interface at 192.168.1.88.
- admin / admin works.
- Live video works perfectly through the browser.
- PTZ/basic functions work.
- The official SV3C Upgrade Tool detects the camera correctly.
- ONVIF is enabled.
- P2P/Platform is enabled.
- Cloud Setting is enabled.
- UID is present.
- The camera has been factory reset several times.
- I also corrected the date, time and timezone because the problem camera initially had an incorrect old date.
SSAT-013982-BCFDB
The issue happens specifically in CamHiPro.
CamHiPro can detect the camera, but when it reaches the adding/authentication stage, it just stays on:
“Adding…” / “Connecting…”
and eventually times out.
It never reaches the next setup steps that the working camera reaches.
There is also one strange behavioral difference: the working camera gives voice prompts during setup/reset, while the problem camera does not seem to give the same voice prompts. It powers on, moves normally and makes startup sounds, but the initialization behavior is different.
I also tested the networking manually through the web interface.
The working camera is correctly connected to the main home network and shows:
- IP: 192.168.0.195
- Gateway: 192.168.0.1
- Primary DNS: 192.168.0.1
- Secondary DNS: 8.8.8.8
- UPnP: Off
- DDNS: Off
The web system log does not show anything particularly useful during the failed CamHiPro attempt. Local HTTP login and streaming work normally, but I do not see a clear P2P/authentication error in the log.
I also downloaded the official SV3C Upgrade Tool. It detects the problem camera correctly, including:
- IP
- MAC address
- firmware version
The public firmware files I found appear to belong to completely different branches/platforms such as V13, V19, V20, GK7102, Hi16EV, etc., so I have not flashed anything because I do not want to brick the camera.
The biggest clue for me is this:
Both cameras are:
- the same SV3C C13 model,
- the same C6F0SgZ0N0P0L2 device type,
- the same V32.1.20.11.19 main firmware branch,
- the same V3.0.7.1 webware,
So I’m wondering whether the older build has some known CamHiPro / P2P / authentication issue.
My main questions are:
Has anyone seen this exact device type or firmware branch before?
Does anyone have firmware V32.1.20.11.19-20241217, or a newer compatible version, for SV3C C13 / C6F0SgZ0N0P0L2?
Could the older 20240228 build have a known P2P or CamHiPro authentication problem?
Is there any safe way to extract the firmware from the working camera, or should I only flash a file supplied directly by SV3C?
Is there anything else I should compare between these two cameras before assuming this is a firmware/P2P issue?
I’m not very experienced with IP cameras, but I’ve tried to diagnose this as carefully as possible before flashing anything.
Thanks in advance for any help.
