Tapo C660 not keeping correct time

Tapo C660 not keeping correct time

Tapo C660 not keeping correct time
Tapo C660 not keeping correct time
2026-01-01 07:01:21 - last edited Yesterday
Model: Tapo C660 KIT  
Hardware Version: V1
Firmware Version: 1.1.5

I have just added a C660 solar wifi camera to my house, I already have 5 other C410 solar wifi cameras. I have noticed that the C660 does not keep the correct time. I have the correct time zone set, in my case +10 Brisbane. I have done all the basic checks, firmware update, app update, router update, and they are all up to date. The issue seems to be the time seems to be the same every time I log in, and the time displays is the last time the camera was rebooted in this case 16:17:50 (no its not a recording) it then starts keeping time, I have watch it for several minutes until the time changes to say  "16:20:21" I then close the camera in the app, open the camera in the app and the time is again 16:17:50. Every recording from the C660 camera has the same time stamp. No other cameras has this issue. I have switched between 12/24hrs and its still the same issue on in 12/24 time format, anyone have any ideas?

  0      
  0      
#1
Options
1 Accepted Solution
Re:Tapo C660 not keeping correct time -Solution
2026-01-04 07:39:26 - last edited Yesterday

  @Y0BB0 

 

Generally, it takes a moment for the live stream to load when you open it in the app. Before the stream is fully loaded, the camera view and timestamp you see are cached from the last viewing session, it's not live yet.

CES 2026 Meet TP-Link AI Assistant and More New Products!
Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Tapo C660 not keeping correct time -Solution
2026-01-04 07:39:26 - last edited Yesterday

  @Y0BB0 

 

Generally, it takes a moment for the live stream to load when you open it in the app. Before the stream is fully loaded, the camera view and timestamp you see are cached from the last viewing session, it's not live yet.

CES 2026 Meet TP-Link AI Assistant and More New Products!
Recommended Solution
  0  
  0  
#2
Options