The camera itself only has two modes, On and Off. The ‘Toggle’ mode is displayed after the devicetype sends a command is awaiting a response from the camera. Once it receives a response from the camera it updates the button with the current state. This is to ensure that the button doesn’t get out of sync with the actual camera.
As for using motion detection, you need to go into your camera’s local settings to set up motion detection. In order to get any kind of output you’ll need to either set up the email option or the ftp option which will allow the camera to send a series of snapshots each time it sees motion. For me these options are under the ‘Snapshot’ menu in the local setting (the settings you get to by putting the local IP of your camera into a browser window). I do not actually have a DCS-932L camera to test so they might be under a different menu option. Once you set this option up it will automatically send a series of pictures to your email/FTP server when motion detection is enabled and it senses movement. You can also set it up to send video if that’s what you prefer.
I thought that the camera’s motion detection would be notified through the Smartthings mobile app, and the pictures would be available in the app as well (same as manual trigger). It sounds like the camera is not able to integrate with Smartthings in that way.
EDIT:
HOWEVER, I was able to integrate it with another ST motion detector, and trigger the photo burst when motion was detected. I think that’s pretty cool for now.
Unfortunately there is no way for SmartThings to ‘listen’ to the camera for a motion event. It can only send commands and receive a response. They’ve said that with at least some of the officially supported cameras they’ll be able to trigger motion events with them.
Is there any chance that this device type also works with the DCS-934L model too?
If not yet, is it possible that you’d be able/willing to modify it to work with this other one?
This is definitely not a stupid question. I’m not really sure if the DCS-934L camera would work with this devicetype or not. I would need to know what type of URL command it takes to manipulate the camera. Have you been able to pull up a still picture from the camera using a web browser? (using a command similar to: http://username:password@IP:PORT/image/jpeg.cgi)
They don’t generally list this info in the support documents, I have a list of a majority of the camera’s API commands but the DCS-934L is one of the ones that isn’t even mentioned. It makes me wonder if it is just a re-cased version of a previous camera.
You may find this (sort of hacky) method for using your D-Link DCS-932L as a motion sensor useful: IFTTT has the ability to trigger a SmartThings event when it receives an email. Of course, it won’t trigger a motion detection but it will trigger a switch - even a simulated switch.
All that is needed to turn that switch into a motion detector is 1) an app that activates a motion detector to broadcast activation when the switch is flipped (and flips the switch back automatically), and 2) a custom device type that masquerades as a motion detector that will actually accept commands (to turn its activation states on and off).
Go to “My Device Types” and create a new device from code. Paste the Device Type code (link above) into the code window.
Save the device type and publish it.
Go to the IDE and under “My Devices” create a new device.
The Name and Network ID can be whatever you like.
Under “Type”, scroll the list all the way to the bottom and select the device type you just added.
Select your location and hub and click “Create”
To Install the App:
In the IDE go to “My SmartApps” and create a new SmartApp from code. Paste in the app code from the link above.
Save the app and publish it.
To Hook it All Up:
Add a Simulated Switch under “My Devices” through the SmartThings IDE in a way similar to how you created the device above.
Create an IFTTT recipe that takes an email and triggers the Simulated Switch you just added.
Install the SmartApp from your mobile device in the SmartThings app.
During installation, select your virtual switch as the first item and your fake motion sensor as the second item.
The delay setting allows you to specify how many seconds the fake motion sensor stays active for prior to timing out. You’ll want to synchronize this with the settings you applied to the back end (web interface) of your DCS-932L: For example, if you have the camera set to send an email on motion detection every 30 seconds, you’ll want to have a delay of more than 30 seconds between the fake motion detector trigger and its timeout. This way if the camera continually senses motion, your fake motion sensor has a good chance of being continually on (though no guarantees for timing because of the nature of email and the fact that the detection signal is being lopped through IFTTT). If motion stops, it will take x seconds for the motion sensor to signal that there is no motion, where x is the value of the delay setting.
Note that when you set up your DCS-932L to send emails on motion detection, you need to specify an SMTP server. You can use gmail’s smpt.gmail.com but you have to use an app-specific password.
This is my first real attempt at coding something interesting in this ecosystem, so forks and improvements are very much welcome.
