TP-Link NC450 camera and SecuritySpy
Comments
-
Yes, I have this firmware on both my cameras - 1.2.4.Build 170322 Rel.85B2CB - and I updated to this firmware the first time I fired the cameras up.
So, no update to what I reported above. No mention of ONVIF in the camera admin page when accessing the camera directly by IP address. I wonder if there is a utility that can 'test' for the presence of an ONVIF camera? Using both the admin panel and the TP-Link iCloud interface, and their Android and iOS apps, I can see the video and control the movement of the cameras, but I just can't get SecuritySpy to recognise them as ONVIF cameras.
It could still be finger trouble on my part, but I've tried all possible options in SecuritySpy options. As I have Bonjour activated rather than disabled, might that somehow disable ONVIF. I did try disabling it but it didn't seem to make any difference. I'll try again. -
Bonjour disabled, ONVIF selected with RTSP TCP (video and audio) set.
02/06/2017 14:09:43: Error communicating with the network device "NC450 Garden Cam". 4.1.4,8440,404 Failed to obtain video frame from network device. File not found. -
Searching the TP-Link support forum for ONVIF brings up lots of questions from users, but no answers from the company.
-
OK apparently the camera uses port 3702 for its ONVIF communication. So please try the ONVIF profile again, and specify 3702 as the ONVIF port. If this works, it should get pan/tilt working as well as video.
-
Ben, many thanks. I can't test this at the moment, but I'll get back to you with the results.
-
Ben, ONVIF port 3702 works with the NC450 like a charm!
IP address added manually, ONVIF port set to 3702 and RTSP TCP (video and audio) added as the format. Selecting the individual camera window brings up the PTZ button and allows directional control.
However, one of the cameras does seem a bit flakey. It ran OK with ONVIF and initially responded to the SS PTZ commands, then I tried to set presets which didn't seem to work. PTZ commands then stopped working and although I've been through the whole factory reset and setting up again in SS, whilst the video is fine in manual mode, it just won't connect in ONVIF mode. As the other camera is working OK, it's got to be a camera issue. I'll play with this some more when I have the time. Reflash the camera firmware maybe?
I had to go through the 'change framerate' process in the camera admin to get the video to show at all in SS too. Hmmm, cheap camera, you get what you pay for maybe!
-
Glad to hear it's working!
Try the latest beta version of SecuritySpy (currently 4.1.5b20) as this has some fixes for camera PTZ problems.
If that doesn't work, then try a factory reset of that problem camera again. -
Thanks, will look at this
-
Ben, Beta running OK and found a way to get my 'reluctant' second NC450 to be recognised as ONVIF. It's fine when wired and fine when connected to the wifi when you unplug the ethernet cable - however, when I powered it down to move to the operational location it just wouldn't connect via ONVIF.
The solution was to put the camera in the location, connect it by ethernet, power it up to get the ONVIF video and then unplug the ethernet cable. Works fine, go figure. I don't suppose the connection would survive a power cycle though.
The PTZ works well, but I haven't tried saving presets as yet. -
Good to hear you managed to get it working, but the WiFi connection does sounds like it's unusually fragile. Is the WiFi reception OK in the new location? You might want to ask TP-Link support if this problem is ongoing - in my experience they have been very responsive and helpful.
-
It's odd, but the actual wifi connection is as solid as a rock on both cameras, each one being no more than 15 feet from a hotspot. It's just that one of the cameras refuses to connect via ONVIF using wifi UNLESS it's connected first by ethernet cable and then the ethernet cable is disconnected to force it to wifi. Connecting in manual mode as per your instructions works for both cameras via wifi, it's just the second one than needs 'starting' in ONVIF mode before disconnecting the ethernet cable. It's such a vague issue that I'm not sure TP-Link would be able to debug it.
I'll keep an eye on it and do some more testing.
Nice to know that TP-Link are responsive. Reading the various forums suggests otherwise, but of course it's only the 'dissatisfied' customers that make all the noise
