Model :

Hardware Version : Not Clear

Firmware Version :

ISP :

I open this thread to emphasize on the fact that NC220s go offline after being updated with the latest firmware like the NC200s do as mentioned in other threads.

For reasons of organization and easy reference I would like this thread to become a sticky, please.

I would also like to ask TP-LINK to understand how serious the situation is; It breaks the promise and purpose of the security cameras and justifies legal action against false advertisement.
Whether the product can be returned for a refund while in guarantee is something TP-LINK must clarify to the customers with a press release, online public announcement or official response in
the forums.

Nevertheless, I am sure TP-LINK is investigating on the matter. I understand every technical detail helps so I post mine below:

Problem description:
The camera goes offline every now and then (the period varies from a few hours to 3 or 4 days). The camera is inaccessible both from the android app and the browser.
The camera's web interface does not respond. The camera has to be unplugged and plugged again in order to become functional.

Camera Name: FRONT
Model: NC220 1.0
Firmware Version: 1.1.7 Build 151125 Rel.24989
Cloud Server Connection Status: connected

Network:
Connection Type: Static IP
LAN IP Address: 192.168.1.105
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1

PPPoE
Status: Disconnected


Video Profile 1

Resolution: 640*480
Frame Rate: 15 FPS
Image Quality: Medium
Light Frequency: Auto

Video Profile 2

Resolution: 320*240
Frame Rate: 15 FPS
Image Quality: Medium

UPnP Port Forward: enabled

Bonjour: disabled

The camera is configured to ftp snapshots based on motion detection.

LOG (Note: I had to unplug and plug again the camera since it had been offline already):

#################################################################
# NC220(UN) System Log
# Time = 2016-1-19 21:41:28
# H-Ver = 1.0 : S-Ver = 1.1.7 Build 151125 Rel.24989
# L = 192.168.1.105 : M = 255.255.255.0
#################################################################

DateTime Level Module Msg
[2014-08-08/00:00:08] NOTICE VideoControl VideoContrl init finished
[2014-08-08/00:00:08] INFO UserManage init module UserManage OK
[2014-08-08/00:00:08] INFO Session Load Session Config Success
[2014-08-08/00:00:08] INFO Session Init Session OK
[2014-08-08/00:00:08] NOTICE VideoControl start stream server
[2014-08-08/00:00:09] INFO NetConfig init NetConf OK.
[2014-08-08/00:00:10] INFO NetSwitch init NetSwitch OK.
[2014-08-08/00:00:10] INFO Bonjour init module Bonjour Support OK
[2014-08-08/00:00:10] INFO AudioDetection init Audio Detection OK
[2014-08-08/00:00:11] INFO MotionDetection Motion Detection, Get setting success.
[2014-08-08/00:00:12] INFO DateTime Start Sync to ntp server
[2014-08-08/00:00:12] INFO DateTime Start DLST Checking
[2014-08-08/00:00:12] INFO DateTime Start DateTime Module OK
[2014-08-08/00:00:12] INFO Button start Button Module OK
[2014-08-08/00:00:12] INFO Button Setting Led to ON
[2014-08-08/00:00:12] INFO DateTime time changed
[2016-01-19/20:57:50] INFO Button Setting Led to ON
[2016-01-19/20:57:51] NOTICE VideoControl start stream server
[2016-01-19/20:57:51] INFO UserManage start UserManage Module OK
[2016-01-19/20:57:51] NOTICE Session ttl thread started
[2016-01-19/20:57:51] INFO NetSwitch start NetSwitch OK.
[2016-01-19/20:57:51] INFO NetSwitch new lan ip : 192.168.1.105.
[2016-01-19/20:57:51] INFO NetSwitch new lan gw : 192.168.1.1.
[2016-01-19/20:57:51] INFO Bonjour start module Bonjour Support OK
[2016-01-19/20:57:51] INFO AudioDetection ADConfStart /usr/local/sbin/ad_alarm
[2016-01-19/20:57:51] INFO AudioDetection ADConfStart swADStartnew finished
[2016-01-19/20:57:51] INFO AudioDetection CreateMsgtoADNEW success
[2016-01-19/20:57:51] INFO AudioDetection Try SendingMsgtoADNEW status=0 sensitivity=2 threshold=-20

[2016-01-19/20:57:51] INFO AudioDetection Sending success
[2016-01-19/20:57:52] INFO MotionDetection Motion Detection, Get setting success.
[2016-01-19/20:57:52] INFO MotionDetection Motion Detection, Setting Succeed
[2016-01-19/20:57:52] INFO NetSwitch new link status : Wired.
[2016-01-19/20:57:53] INFO NetSwitch new lan gw : 192.168.1.1.
[2016-01-19/20:57:53] ERROR Cloud P2P dameon run failed
[2016-01-19/20:57:55] INFO MotionDetection Motion Detection, Get setting success.
[2016-01-19/21:00:23] INFO MotionDetection timestamp=1453230023, alarm_type=1
[2016-01-19/21:01:24] INFO MotionDetection timestamp=1453230084, alarm_type=1
[2016-01-19/21:14:35] INFO MotionDetection timestamp=1453230875, alarm_type=1
[2016-01-19/21:21:25] INFO MotionDetection timestamp=1453231285, alarm_type=1
[2016-01-19/21:23:40] INFO MotionDetection timestamp=1453231420, alarm_type=1
[2016-01-19/21:24:10] INFO MotionDetection timestamp=1453231450, alarm_type=1
[2016-01-19/21:28:21] INFO MotionDetection timestamp=1453231701, alarm_type=1
[2016-01-19/21:28:50] INFO MotionDetection timestamp=1453231730, alarm_type=1
[2016-01-19/21:30:37] INFO MotionDetection timestamp=1453231837, alarm_type=1
[2016-01-19/21:33:23] INFO MotionDetection timestamp=1453232003, alarm_type=1
[2016-01-19/21:36:07] INFO MotionDetection Motion Detection, Get setting success.
[2016-01-19/21:37:11] INFO MotionDetection timestamp=1453232231, alarm_type=1
[2016-01-19/21:37:42] INFO MotionDetection timestamp=1453232262, alarm_type=1
[2016-01-19/21:39:40] INFO MotionDetection timestamp=1453232380, alarm_type=1
[2016-01-19/21:40:09] INFO MotionDetection Motion Detection, Get setting success.


Last but not least, fellow users/customers must raise a voice in the forums so TP-LINK speeds its reaction.