OK, I have a fully working Device Handler I’m interested in input on how you’d want this to be set up… here are the options I’ve come up with, along with the pros/cons I can think of:
Option 1: Standalone Device Handler
(this exists now)
Pros:
Can view/change motion detector switch state manually for each camera
Motion detector setting can be automated using routines
Cons
Must manually add and configure each camera
Camera IPs must be static (I might be able to work around this)
Adds a new “device” for each camera to the list of Things; could be confused with existing SmartThings SmartCam devices
Option 2: Standalone SmartApp
(80% done)
Pros:
SmartApp can discover and manage all cameras on the network with minimal configuration per camera
Camera IPs can be dynamic
Motion detector setting can be automated (per-camera) using mode changes
Cons:
Individual camera motion detector state cannot be viewed or changed manually
Option 3: Parent SmartApp with Child Device Handler
(basically a combination of #1 and #2 - 50% done)
Pros:
SmartApp can discover and manager all cameras on the network with minimal configuration per camera
Camera IPs can be dynamic
Motion detector setting can be automated per-camera using mode changes and routines
Motion detector setting can be manually viewed/changed per camera
Cons:
More involved initial setup (must install a SmartApp and Device Handler)
Each managed camera will create another device in the “Things” list, could be confused for existing SmartThings SmartCam devices
After typing all that out, it seems that #3 is the most flexible option, but it is also the most complex in terms of initial setup and “moving parts”. There’d also be a few small quirks, such as at least part of the camera config has to be located in the SmartApp (the rest could be located in the SmartApp OR Device settings - but I’d lean towards keeping them together for consistency).
First off, You are amazing! Thank you for all your hard work!!! Can’t wait to give this a try…
Secondly, I would be happy with option 1. I already have each of my cameras set with a sticky IP (DHCP reservation) and I have no problem with each camera showing as it’s own “thing.”
Would the Parent SmartApp make it more difficult (or easier?) to manage the motion detection state via CoRE Pistons?
Don’t care, as long as we ( I ) can actually use the cams as motion detectors… The only reason I bought the cams was because they were supposed to be supported in ST. Didn’t realize " supported" meant I could manually view them live, and nothing else.
The app and web UI are next to useless. Only IP cams I have come across with no way to download video clips other than go to the camera and physically remove the SD card and copy the files.
The Parent SmartApp wouldn’t affect CoRE, because either way the control is a Switch-type Device (the SmartApp is just there to handle discovery and dynamic IP address changes). CoRE should be able to easily toggle the switch on/off in both cases.
To clarify, my device handler won’t create a new Motion Detector device in SmartThings, it is just a switch that controls whether or not the SmartCam’s local motion detection is enabled.
It’s true that the SmartThings-SmartCam integration is limited, but you can (at least) have ST automatically record video during a SHM incident, in addition to viewing the camera live. I didn’t realize there was no way to download video clips - that is pretty bad.
It’s ready! I’ve created a new topic specifically for discussion related to my Device Handler, so check it out and let me know what you think over here:
Ive been toying with my smartcam trying to turn it into a motion detector in SmartThings. I have it sending an email to ifttt from my gmail account to trigger a switch to do so now. it is good but looking to remove the delay.
Any thoughts to updating the detection switch devicehandler to also be a ‘dummy’ smtp server to capture the email sent?
from what I can tell “subscription” no longer works.
Hi,
I am doing exactly the same thing, but couldn’t get it to work. What do you put in the http port?
I tried 443, 80, and the external port listed in my router listed for the smartcam’s IP address but still doesn’t work, can you please advise? Thanks.
I would love to be able to specify the static ip addresses of my cameras. The smartthings provided device handler does not detect them unless i completely reset the camera. One of the worst integrations I’ve ever seen. Apparently once discovered, the ip address is referenced in the data field, but there is no way to edit this field with the smartthings provided device handler.
I was here trying to figure out how to setup my SNH-P6410BN through IP just because I wanted to use IP Cam Viewer. As you sad, the option for this model doesn’t work in IP Cam Viewer, but selecting SNH-E6440BN worked like a charm.
interesting not about firewalls and smartcams… i have been getting over 30,000 attempts per day to hack into my email server… so i started blocking ranges wholesale in my fireall to cut down .
first i blocked all of Brazil (sorry) then other ip ranges that were attempting to hack in.
I blocked 168.0.0.0/8 . all my smartcams on wifi interestingly still worked but apparently the one outdoor cam with ethernet cable instead of wifi stopped going green/reaching servers… apparently only when not on wifi it attemps to reach a server on the 168 subnet.
Hope this helps others… It took binary serarch/trial and error to figure out what ip range was the culprit.
Hi, I have got a couple of these IP-cams Samsung Smart Cam SNH-E6440BN but with the cables are cut (I still have about 30cms out from the camera). Does anybody know have the wires in the RJ12-connector should be sorted? It also seems that cable is shielded. Are there shielded RJ12-connectors?
Hi…did you get the cable info for J12 connector. My son cut our connector off and now can’t find it to rewire it so any help would really be appreciated. Its a SNH-E6440. Thanks.