TP-Link CommunityTapo Smart CameraTapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup
Tapo Smart Camera

Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup

Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup

Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup
Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup
a week ago - last edited Friday
Tags: #Firmware #Device Connectivity #Installation #network unstable
Model: Tapo C320WS  
Hardware Version: V2
Firmware Version: 1.3.5 Build 250522 Rel. 45630n

Hi,

I have 4x Tapo C320WS V2 cameras on the same network. Three of them work perfectly, but one has been stuck in local-only mode for about 5–6 months.

Firmware: 1.3.5 Build 250522 Rel. 45630n Hardware: V2 Connection: Ethernet or Wi-Fi, tried both.

The problem: The camera is accessible locally via the Tapo app, but cannot connect to the cloud. The app shows "network is unstable" and remote access is not available.

What I have already tried:

  • Factory reset (multiple times)
  • Copied sys01.bin from a working identical camera to the SD card
  • Changed DNS to 8.8.8.8 and 1.1.1.1 directly on the camera
  • Removed and re-added the camera in the app, tried with an other phone, Tapo App and mobile hotspot connection.
  • Tried web emergency mode but I cannot access the loading page via 192.168.0.10 adress. The manual I found in the forums only lists V1 version suitable for emergency mode.

Key observation: When I factory reset and re-add one of the working cameras, it plays a beep sound at the end of setup, and my network security software (ESET) shows a new device joining the network. When I do the exact same process with the problematic camera, there is no beep and no network join notification — meaning the camera never completes cloud registration.

The issue started around the time firmware 1.3.5 was installed. The other three cameras have the latest firmware: 1.5.3 Build 260304 Rel.25729n

Is there any way to re-provision this device on the cloud side, or is a replacement the only option?

Thank you.

0
0
#1
3 Reply
Re:Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup
a week ago - last edited Friday

  @yoonoose 

Hello,

Thank you for your details.

If the camera shows “Local Only” and cannot be viewed remotely, follow Scenario 2 in this FAQ: Tapo/Kasa Camera Not Working: Cannot View Camera Troubleshooting Guide

 

Please try setting up the camera using a mobile hotspot to see if the issue persists. This will help rule out any network‑related factors.
If it still doesn’t work, kindly send me the camera’s MAC address via private message, and I’ll assist with further checks.

 

Best Regards,
 

2
2
#2
Re:Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup
Monday

@yoonoose 

Hi，

Thank you for sharing your device information.
Based on the details provided, we did not identify any obvious abnormalities. Could you please confirm the LED indicator status of the camera after the setup is completed (e.g., what color is the light)?
Given the current situation, we recommend contacting your local support team for further assistance, as this may involve a warranty inspection. They will be able to provide appropriate solutions.

Best Regards,

 

 

0
0
#3
Re:Tapo C320WS V2 – No cloud connection after firmware 1.3.5 Build 250522, no beep on setup
Monday

  @Hilbert-TP 

Hi Hilbert,

Thank you for your reply.

After setup is completed, the LED indicator is solid orange. (via Wi-Fi)

I have already contacted local support for assistance or warranty via e-mail last Thursday but received no response yet. 

Maybe I'll give a call to them if I get no response today.

 

Also these are the fault lines after the camera resolves DNS, establishes TCP and SSL connections to the cloud server,

 but the cloud server rejects the device with the following errors:

 

[CloudIot] no cacert or ca invalid

[CloudIot] token is invalid or token out of time

[CloudIot] req srv token err: -130010000

0
0
#4

Information

Helpful: 0

Views: 246

Replies: 3

Tags

Firmware Device Connectivity Installation
network unstable
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.