[OBSOLETE] D-Link Camera Manager (Connect) [Requires Classic App]

The weirdness continues…but everything seems to be working now. I added a third camera, unplugged and moved the second one and now they all work. Chalking it up to Dlink’s interface or ghosts in the machine.

Got the generic camera app to work, the camera and hub are on the same network

I actually got a brief video feed from your app tonight but that happened only twice and it lasted for about two seconds, I used port 80 & 554 as well to test…

The stream working twice tells me it’s a network issue and nothing to do with the SmartApp/DTH itself. Maybe try restarting your hub/router/phone and see if anything helps?

Hi Ben - how would I go about adding a DCS 7110? I know there are generic camera apps out there but yours looks far better.

Thanks,
Richard

The first step would be using the Generic camera DTH and the Generic Video Camera SmartApp to determine the correct still image and video streaming url. Once you have those I can try to create a devicetype and add it to this SmartApp.

1 Like

Thanks. When you say Generic video camera smartapp do you mean this one:

Also - what is a ‘DTH’. Sorry to sound a bit dim…

Yes, that one for still images and this one for video streaming:

DTH = Device Type Handler which is basically the driver that makes devices work in SmartThings.

Hi,

Got there. The still format is:

http://usr:passwd@IPAddress:port/cgi-bin/viewer/video.jpg?streamid=0

and the stream is:

http://usr:passwd@IPAddress:port/video.mjpg

Thanks,
Richard

Can you try using http://username:password@IP:Port/image/jpeg.cgi for still image and rtsp://username:password@IP:Port/live.sdp for video?

Hi! I just got a new DCS-935

I got video working, but having some problems with still image. When I press the button it just says “taking” and no image appears

This is what I get in the logs:

e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug GET /image/jpeg.cgi HTTP/1.1
Accept: /
User-Agent: Linux UPnP/1.0 SmartThings
HOST: 10.0.0.141:80
Authorization: Basic **********************

e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug The method is GET
e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug The Header is [HOST:10.0.0.141:80, Authorization:Basic ***************************
e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug path is: /image/jpeg.cgi
e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug The device id configured is: 0a00008d:0050
e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug 0050
e66b1266-33af-461d-95bb-9504cb9716b2 09.11.36 CEST: debug IP address entered is 10.0.0.141 and the converted hex code is 0a00008d

Putting this in my browser gives me an image: http://username:password@IP:Port/image/jpeg.cgi

Hi - yes still url is definitely working and when I allow rtsp through the firewall this evening we should be good to go with the video address.

Cheers,
Richard

Picture may be too big. See if it’s over 30KB because the hub will have an issue with that. Try lowering the quality to 320x240

Lowering the quality did the trick. Thanks

Yes - that RTSP address also worked :slight_smile:

1 Like

One last thing to check, can you paste the following URL into a web browser (fill in the fields of course):

http://username:password@IP:Port/config/motion.cgi

Let me know if there is a page that shows and copy whatever it says into here.

##Post Updated:

Updated post to clarify custom commands. All cameras have motion on/off defaulted as their main command. This means you can use the camera in a SmartApp or Routine as a normal switch in order to toggle the motion on or off.

Hi

Going to http://username:password@IP:Port/config/motion.cgi says page not found on server. The config path in setup seems to be /setup

http://username:password@IP:Port/setup/motion.html is the page that configures motion detection.

Cheers,
Richard

Ok, can you try going to http://username:password@IP:Port/motion.cgi

Still ‘not found’

:frowning:

hmm, I don’t have any documentation on this camera so I don’t know what API it’s using. Those two motion commands are the two standard ones that their IP cameras have used, I’m not sure what else to test.