[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: X10 Computer Interface



"Dave" <dju@xxxxxxxxxxxxxx> wrote in message
news:1hvh41hqfmm0egibutoc75l01dtef7noug@xxxxxxxxxx
> On Tue, 29 Mar 2005 00:59:25 GMT, shb*NO*SPAM*@comporium.net
> (Si Ballenger) wrote:
>
>>Just make it so it will run one or more user specified command
>>lines when motion is detected. That way when motion is detected,
>>the user can have applications run that operate x10 gizmos, send
>>email, grab pix, or do all sorts of other things. You can add
>>other fancy stuff later after the motion detection part is
>>developed.
>
> Would a command line to launch a .CMD or .BAT file be enough
> to make it useful? That would be real easy for me to add
> something like a program (or .CMD) file launcher.
>
> Will have to think about how to avoid feedback (blink on /
> off) in case the light (outdoor lights) are in view of the
> motion detector camera.
>
> To avoid turning the lights on in the daytime, I can keep
> track of time and when the program knows that the sun is up,
> it can launch a different command line or not launch
> anything. Seems like it's getting a little dirty if I have
> to keep track of daylight, though. Will need to figure that
> one out. It turns out that the computer can't tell day or
> night by looking at the camera image, unfortunately.
>
> I'll be back here when it's done to see if I can find any
> volunteers to help test it. The program already records
> video and the motion detector are complete. It has to be
> able to support as many capture input devices as possible
> and I'm afraid right now it only supports 3 of the 4 devices
> I tried to use with it. It won't support the Adaptec capture
> cards, but I've tried 3 other brands all successfully.
> Eventually I'd like to support IP cams but it only works
> with analog or digital (firewire or USB) video capture right
> now.
>
> Dave

Another 2 cents worth......

Launching command line is absolutly essential, but let the command line be
user configurable - so instead of putting in a cmd flie to run - allow the
user to specify "cscript trigger."whatever you favourite wscript supported
language is" - and pass as much info to the command as you can - something
like

trigger "which camera" "day or night" "date/time" "date time I last
triggered" "trigger count" "%confidence (did it move a little or a lot)" -
you need to pass the state information to the command line 'cos scripts
aren't good at being stateful.

I would like to then do some logic inside the cmd/script like...

trigger....

    if day and camera triggered triggered twice in 1 minute
    then
        a lot of activity outside - no lights but maybe ring an internal
chime to go take a look

    still more activity
        take pictures - email then to remote sites.
        if house empty then send pager message

    yet more
        trigger the panic alarm in the house

    if night then all the above plus the lights.......




comp.home.automation Main Index | comp.home.automation Thread Index | comp.home.automation Home | Archives Home