- SECURITYSPY INDIGO PLUGIN HOW TO
- SECURITYSPY INDIGO PLUGIN INSTALL
- SECURITYSPY INDIGO PLUGIN UPDATE
- SECURITYSPY INDIGO PLUGIN PASSWORD
I've been using it in my house for many years, and am a fairly satisfied customer. Indigo and SecuritySpy have obvious shared interests.
SECURITYSPY INDIGO PLUGIN HOW TO
They both are often used to track movement through space and time, and they both have a concept of events and how to respond to them. Cynical SecuritySpy brings them together.
You will need SecuritySpy version 2.1.1 or later for this plugin to work. The plugin will work with versions 3 through 5 as well. Of course, if you use an older version of SecuritySpy, you'll only get the capabilities of that version.
SECURITYSPY INDIGO PLUGIN UPDATE
SECURITYSPY APEX FUSION UPDATEīe sure to use the latest released update for whatever version you paid for earlier versions may have bugs that interfere with Cynical SecuritySpy.
SECURITYSPY INDIGO PLUGIN INSTALL
Install and configure SecuritySpy normally. Then create a Server device to represent each SecuritySpy installation, and one Camera device for each camera of interest.
Use Indigo plugin actions to manipulate those cameras, and use Events to respond to changes.Ĭynical SecuritySpy tracks changes in SecuritySpy's state and reflects them in the state of the server and camera devices, as well as through Camera Motion events. When your Indigo scripts cause changes in SecuritySpy, they will be reflected as Indigo device changes only when SecuritySpy reports them. This means that Cynical SecuritySpy provides you with closed-loop supervision over SecuritySpy servers - what you see in Indigo state and events is what actually happened on the server, not just what you said you wanted to happen. To supplement SecuritySpy's motion sensing, use Indigo Trigger Recording actions, for example in response to an Indigo motion sensor. To respond to motion detected by SecuritySpy, write triggers for Camera Motion events. To arrange for Indigo to directly control recording in SecuritySpy, configure the camera in SecuritySpy for continuous recording, and then use the Arm Camera action in Indigo to enable and disable continuous recording as desired. To work with a SecuritySpy server, you must first tell Indigo about it by creating a Server device. This tells Indigo where the server is and how to talk to it. The server must have its web server component enabled, and the port number you enter is that of the web server (not the SecuritySpy server itself). The web server must allow http connections, not just https (secure) ones, though it's okay to allow both.Ĭynical SecuritySpy talks to SecuritySpy exclusively through its web interface. There is no need for Indigo and SecuritySpy to run on the same computer, though they certainly can.
SECURITYSPY INDIGO PLUGIN PASSWORD
If the web server is Password protected, you must also enter a name and password that can perform whatever actions you want Indigo to take. At minimum, that user must have Allow access to general settings checked, as well as View live images for all cameras you want Indigo to work with. If you want Indigo to make changes to SecuritySpy, additional checkboxes will be needed. SECURITYSPY APEX FUSION PASSWORDĭo note that the password will be stored in cleartext in the plugin's configuration file. You may wish to create a specific username/password pair just for Indigo and use that. Similarly, if the web server has Access control enabled, the computer running Indigo must be granted access to it. If they are both running on the same computer, use localhost (address 127.0.0.1). Yes, you can talk to multiple SecuritySpy servers on different computers if you like just make a different Server device for each one.
The sensitivity state is a value between 0 and 100 indicating how little the picture needs to change to trigger motion detection (when enabled). This is the same value you can set in SecuritySpy's camera configuration window. You can script changes using the Set Motion Sensitivity action. The motion, continuous, and actions states represent the arming states of the camera. They directly correspond to the SecuritySpy settings for this camera. You can use the Arm Camera action to set them from Indigo, and you can set triggers on these states to detect changes, regardless of source. If motion is on, the camera detects motion and starts recording according to its configuration in earlier versions of SecuritySpy this was called the "active" state. If motion is off, the camera will not detect motion. The continuous switch, when on, enables any continuous recording configured for the camera.
If it is off, continuous recording is disabled. The actions switch determines whether SecuritySpy's configured actions for the camera are executed when their conditions apply.
0 kommentar(er)
